EP3046304B1 - Vorrichtungen zum senden/empfangen eines broadcast-signals - Google Patents

Vorrichtungen zum senden/empfangen eines broadcast-signals Download PDF

Info

Publication number
EP3046304B1
EP3046304B1 EP15811631.9A EP15811631A EP3046304B1 EP 3046304 B1 EP3046304 B1 EP 3046304B1 EP 15811631 A EP15811631 A EP 15811631A EP 3046304 B1 EP3046304 B1 EP 3046304B1
Authority
EP
European Patent Office
Prior art keywords
information
signaling
link layer
packet
broadcast
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
EP15811631.9A
Other languages
English (en)
French (fr)
Other versions
EP3046304A1 (de
EP3046304A4 (de
Inventor
Woosuk Kwon
Sejin OH
Minsung KWAK
Kyoungsoo Moon
Jangwon Lee
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
LG Electronics Inc
Original Assignee
LG Electronics Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by LG Electronics Inc filed Critical LG Electronics Inc
Publication of EP3046304A1 publication Critical patent/EP3046304A1/de
Publication of EP3046304A4 publication Critical patent/EP3046304A4/de
Application granted granted Critical
Publication of EP3046304B1 publication Critical patent/EP3046304B1/de
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • 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/04—Protocols for data compression, e.g. ROHC
    • 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/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/235—Processing of additional data, e.g. scrambling of additional data or processing content descriptors
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/236—Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
    • H04N21/2362—Generation or processing of Service Information [SI]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/238—Interfacing the downstream path of the transmission network, e.g. adapting the transmission rate of a video stream to network bandwidth; Processing of multiplex streams
    • H04N21/2381—Adapting the multiplex stream to a specific network, e.g. an Internet Protocol [IP] network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/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/434—Disassembling of a multiplex stream, e.g. demultiplexing audio and video streams, extraction of additional data from a video stream; Remultiplexing of multiplex streams; Extraction or processing of SI; Disassembling of packetised elementary stream
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/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/434—Disassembling of a multiplex stream, e.g. demultiplexing audio and video streams, extraction of additional data from a video stream; Remultiplexing of multiplex streams; Extraction or processing of SI; Disassembling of packetised elementary stream
    • H04N21/4345—Extraction or processing of SI, e.g. extracting service information from an MPEG stream
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/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/435—Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/438—Interfacing the downstream path of the transmission network originating from a server, e.g. retrieving encoded video stream packets from an IP network
    • H04N21/4381—Recovering the multiplex stream from a specific network, e.g. recovering MPEG packets from ATM cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/488—Data services, e.g. news ticker
    • H04N21/4882—Data services, e.g. news ticker for displaying messages, e.g. warnings, reminders
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/60—Network structure or processes for video distribution between server and client or between remote clients; Control signalling between clients, server and network components; Transmission of management data between server and client, e.g. sending from server to client commands for recording incoming content stream; Communication details between server and client 
    • H04N21/63—Control signaling related to video distribution between client, server and network components; Network processes for video distribution between server and clients or between remote clients, e.g. transmitting basic layer and enhancement layers over different transmission paths, setting up a peer-to-peer communication via Internet between remote STB's; Communication protocols; Addressing
    • H04N21/643—Communication protocols
    • H04N21/64322—IP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/81—Monomedia components thereof
    • H04N21/8126—Monomedia components thereof involving additional data, e.g. news, sports, stocks, weather forecasts
    • H04N21/814—Monomedia components thereof involving additional data, e.g. news, sports, stocks, weather forecasts comprising emergency warnings
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/668—Internet protocol [IP] address subnets

Definitions

  • the present invention relates to a method and apparatus for transmitting/receiving a media signal. More specifically, the present invention relates to a method and apparatus for processing data about media transmitted respectively through a broadband network and a broadcast network in a broadcast system in which the broadband and broadcast networks are combined.
  • IP-based broadcast signals Transmission/reception of IP-based broadcast signals has been extended in digital broadcast systems. Specifically, the importance of Internet protocol (IP)-based broadcast signal transmission/reception environments has been emphasized in the mobile digital broadcast schemes, for example, DVB-NGH from among European broadcast standards or ATSC-MH from among North American standards. In addition, it is expected that a hybrid broadcast system designed to be interoperable with a broadcast network or an Internet network will be constructed in the next generation broadcast system.
  • IP Internet protocol
  • an emergency alert message needs to be transmitted through a broadcast network.
  • a method for transmitting the emergency alert message has not been obviously defined.
  • US 2012/0063455 A1 discloses a method of processing broadcast data in a system using a Vestigial Sideband (VSB) transmission mode such as the mobile pedestrian handheld (MPH) standard for digital broadcasting adopted in North America and the Republic of Korea.
  • VSB Vestigial Sideband
  • MPH mobile pedestrian handheld
  • a technical object to be achieved by the present invention is to solve the aforementioned problems and provides a proper method and apparatus for processing data when a data transmission scheme via an existing broadcast network and a data transmission scheme via a broadband network coexist in a hybrid broadcast system.
  • Another object of the present invention is to provide a method and apparatus for efficiently transmitting an emergency alert message via a broadcast system.
  • Another object of the present invention is to provide a method and apparatus for enabling a viewer to efficiently search for a desired broadcast service.
  • Another object of the present invention is to provide a method for performing an initialization procedure for data processing in a link layer.
  • Another object of the present invention is to provide an efficient signaling method when a transmission session based protocol is applied to a broadcast system.
  • a broadcast transmitter for transmitting a broadcast signal in accordance with claim 1.
  • Embodiments of the broadcast transmitter are further defined in claims 2-5.
  • a broadcast receiver for receiving a broadcast signal in accordance with claim 6.
  • Embodiments of the broadcast receiver are further defined in claims 7-10.
  • both data transmitted through an existing broadcast network and data transmitted through a broadband network can be efficiently processed.
  • an emergency alert message can be efficiently transmitted through a broadcast system.
  • a viewer can efficiently search for a desired broadcast service.
  • processing of a link layer that can operate independently of change of a higher layer with respect to an IP layer, an MPEG-2 TS layer, and other protocol layers corresponding to the IP layer and the MPEG-2 TS layer can be performed.
  • data can be processed in a link layer that can independently operate without being influenced by a physical layer through which broadcast content is to be transmitted.
  • a layer that can be easily expanded later can be configured through organization of functional blocks constituting a link layer.
  • signaling transmission can be performed via multiple paths through a link layer, thereby acquiring efficiency of signaling transmission.
  • bandwidth of a broadcast system and a processing time of broadcast data can be efficiently used through a control function of a link layer.
  • the term "signaling" in the present invention may indicate that service information (SI) that is transmitted and received from a broadcast system, an Internet system, and/or a broadcast/Internet convergence system.
  • the service information (SI) may include broadcast service information (e.g., ATSC-SI and/or DVB-SI) received from the existing broadcast systems.
  • broadcast signal may conceptually include not only signals and/or data received from a terrestrial broadcast, a cable broadcast, a satellite broadcast, and/or a mobile broadcast, but also signals and/or data received from bidirectional broadcast systems such as an Internet broadcast, a broadband broadcast, a communication broadcast, a data broadcast, and/or VOD (Video On Demand).
  • bidirectional broadcast systems such as an Internet broadcast, a broadband broadcast, a communication broadcast, a data broadcast, and/or VOD (Video On Demand).
  • PGP may indicate a predetermined unit for transmitting data contained in a physical layer. Therefore, the term “PLP” may also be replaced with the terms 'data unit' or 'data pipe' as necessary.
  • a hybrid broadcast service configured to interwork with the broadcast network and/or the Internet network may be used as a representative application to be used in a digital television (DTV) service.
  • the hybrid broadcast service transmits, in real time, enhancement data related to broadcast A/V (Audio/Video) contents transmitted through the terrestrial broadcast network over the Internet, or transmits, in real time, some parts of the broadcast A/V contents over the Internet, such that users can experience a variety of contents.
  • A/V Audio/Video
  • FIG. 1 is a view showing a protocol stack for a next generation broadcasting system according to an embodiment of the present invention.
  • the broadcasting system according to the present invention may correspond to a hybrid broadcasting system in which an Internet Protocol (IP) centric broadcast network and a broadband are coupled.
  • IP Internet Protocol
  • the broadcasting system according to the present invention may be designed to maintain compatibility with a conventional MPEG-2 based broadcasting system.
  • the broadcasting system according to the present invention may correspond to a hybrid broadcasting system based on coupling of an IP centric broadcast network, a broadband network, and/or a mobile communication network (or a cellular network).
  • a physical layer may use a physical protocol adopted in a broadcasting system, such as an ATSC system and/or a DVB system.
  • a transmitter/receiver may transmit/receive a terrestrial broadcast signal and convert a transport frame including broadcast data into an appropriate form.
  • an IP datagram is acquired from information acquired from the physical layer or the acquired IP datagram is converted into a specific frame (for example, an RS Frame, GSE-lite, GSE, or a signal frame).
  • the frame main include a set of IP datagrams.
  • the transmitter include data processed from the physical layer in a transport frame or the receiver extracts an MPEG-2 TS and an IP datagram from the transport frame acquired from the physical layer.
  • a fast information channel includes information (for example, mapping information between a service ID and a frame) necessary to access a service and/or content.
  • the FIC may be named a fast access channel (FAC).
  • the broadcasting system may use protocols, such as an Internet Protocol (IP), a User Datagram Protocol (UDP), a Transmission Control Protocol (TCP), an Asynchronous Layered Coding / Layered Coding Transport (ALC/LCT), a Rate Control Protocol / RTP Control Protocol (RCP/RTCP), a Hypertext Transfer Protocol (HTTP), and a File Delivery over Unidirectional Transport (FLUTE).
  • IP Internet Protocol
  • UDP User Datagram Protocol
  • TCP Transmission Control Protocol
  • ALC/LCT Asynchronous Layered Coding / Layered Coding Transport
  • RCP/RTCP Rate Control Protocol / RTP Control Protocol
  • HTTP Hypertext Transfer Protocol
  • FLUTE File Delivery over Unidirectional Transport
  • data may be transported in the form of an ISO based media file format (ISOBMFF).
  • ISOBMFF ISO based media file format
  • An Electrical Service Guide (ESG), Non Real Time (NRT), Audio / Video (A/V), and/or general data may be transported in the form of the ISOBMFF.
  • Transport of data through a broadcast network may include transport of a linear content and/or transport of a non-linear content.
  • Transport of RTP/RTCP based A/V and data may correspond to transport of a linear content.
  • An RTP payload may be transported in the form of an RTP/AV stream including a Network Abstraction Layer (NAL) and/or in a form encapsulated in an ISO based media file format.
  • Transport of the RTP payload may correspond to transport of a linear content.
  • Transport in the form encapsulated in the ISO based media file format may include an MPEG DASH media segment for A/V, etc.
  • Transport of a FLUTE based ESG, transport of non-timed data, transport of an NRT content may correspond to transport of a non-linear content. These may be transported in an MIME type file form and/or a form encapsulated in an ISO based media file format. Transport in the form encapsulated in the ISO based media file format may include an MPEG DASH media segment for A/V, etc.
  • Transport through a broadband network may be divided into transport of a content and transport of signaling data.
  • Transport of the content includes transport of a linear content (A/V and data (closed caption, emergency alert message, etc.)), transport of a non-linear content (ESG, non-timed data, etc.), and transport of a MPEG DASH based Media segment (A/V and data).
  • A/V and data closed caption, emergency alert message, etc.
  • ESG non-linear content
  • MPEG DASH based Media segment A/V and data
  • Transport of the signaling data may be transport including a signaling table (including an MPD of MPEG DASH) transported through a broadcasting network.
  • a signaling table including an MPD of MPEG DASH
  • synchronization between linear/non-linear contents transported through the broadcasting network or synchronization between a content transported through the broadcasting network and a content transported through the broadband may be supported.
  • the receiver may adjust the timeline dependent upon a transport protocol and synchronize the content through the broadcasting network and the content through the broadband to reconfigure the contents as one UD content.
  • An applications layer of the broadcasting system according to the present invention may realize technical characteristics, such as Interactivity, Personalization, Second Screen, and automatic content recognition (ACR). These characteristics are important in extension from ATSC 2.0 to ATSC 3.0.
  • HTML5 may be used for a characteristic of interactivity.
  • HTML and/or HTML5 may be used to identify spatial and temporal relationships between components or interactive applications.
  • signaling includes signaling information necessary to support effective acquisition of a content and/or a service.
  • Signaling data may be expressed in a binary or XMK form.
  • the signaling data may be transmitted through the terrestrial broadcasting network or the broadband.
  • a real-time broadcast A/V content and/or data may be expressed in an ISO Base Media File Format, etc.
  • the A/V content and/or data may be transmitted through the terrestrial broadcasting network in real time and may be transmitted based on IP/UDP/FLUTE in non-real time.
  • the broadcast A/V content and/or data may be received by receiving or requesting a content in a streaming mode using Dynamic Adaptive Streaming over HTTP (DASH) through the Internet in real time.
  • DASH Dynamic Adaptive Streaming over HTTP
  • the received broadcast A/V content and/or data may be combined to provide various enhanced services, such as an Interactive service and a second screen service, to a viewer.
  • a link layer may be used to transmit data having a TS or IP stream type.
  • the link layer may convert the data into a format supported by the physical layer and deliver the converted data to the physical layer.
  • the various types of data may be transmitted through the same physical layer.
  • the physical layer may correspond to a step of transmitting data using an MIMO/MISO scheme or the like by interleaving, multiplexing, and/or modulating the data.
  • the link layer needs to be designed such that an influence on an operation of the link layer is minimized even when a configuration of the physical layer is changed.
  • the operation of the link layer needs to be configured such that the operation may be compatible with various physical layers.
  • the present invention proposes a link layer capable of independently operating irrespective of types of an upper layer and a lower layer.
  • the upper layer may refer to a layer of a data stream such as a TS stream, an IP stream, or the like.
  • the lower layer may refer to the physical layer.
  • the present invention proposes a link layer having a correctable structure in which a function supportable by the link layer may be extended/added/deleted.
  • the present invention proposes a scheme of including an overhead reduction function in the link layer such that radio resources may be efficiently used.
  • protocols and layers such as IP, UDP, TCP, ALC/LCT, RCP/RTCP, HTTP, FLUTE, and the like are as described above.
  • a link layer t88010 may be another example of the above-described data link (encapsulation) part.
  • the present invention proposes a configuration and/or an operation of the link layer t88010.
  • the link layer t88010 proposed by the present invention may process signaling necessary for operations of the link layer and/or the physical layer.
  • the link layer t88010 proposed by the present invention may encapsulate TS and IP packets and the like, and perform overhead reduction in this process.
  • the link layer t88010 proposed by the present invention may be referred to by several terms such as data link layer, encapsulation layer, layer 2, and the like. According to a given embodiment, a new term may be applied to the link layer and used.
  • FIG. 2 is a conceptual diagram illustrating an interface of a link layer according to an embodiment of the present invention.
  • the transmitter may consider an exemplary case in which IP packets and/or MPEG-2 TS packets mainly used in the digital broadcasting are used as input signals.
  • the transmitter may also support a packet structure of a new protocol capable of being used in the next generation broadcast system.
  • the encapsulated data of the link layer and signaling information may be transmitted to a physical layer.
  • the transmitter may process the transmitted data (including signaling data) according to the protocol of a physical layer supported by the broadcast system, such that the transmitter may transmit a signal including the corresponding data.
  • the receiver may recover data and signaling information received from the physical layer into other data capable of being processed in a higher layer.
  • the receiver may read a header of the packet, and may determine whether a packet received from the physical layer indicates signaling information (or signaling data) or recognition data (or content data).
  • the signaling information (i.e., signaling data) received from the link layer of the transmitter may include first signaling information that is received from an upper layer and needs to be transmitted to an upper layer of the receiver; second signaling information that is generated from the link layer and provides information regarding data processing in the link layer of the receiver; and/or third signaling information that is generated from the upper layer or the link layer and is transferred to quickly detect specific data (e.g., service, content, and/or signaling data) in a physical layer.
  • specific data e.g., service, content, and/or signaling data
  • FIG. 3 illustrates an operation in a normal mode corresponding to one of operation modes of a link layer according to an embodiment of the present invention.
  • the link layer proposed by the present invention may have various operation modes for compatibility between an upper layer and a lower layer.
  • the present invention proposes a normal mode and a transparent mode of the link layer. Both the operation modes may coexist in the link layer, and an operation mode to be used may be designated using signaling or a system parameter. According to a given embodiment, one of the two operation modes may be implemented. Different modes may be applied according to an IP layer, a TS layer, and the like input to the link layer. In addition, different modes may be applied for each stream of the IP layer and for each stream of the TS layer.
  • a new operation mode may be added to the link layer.
  • the new operation mode may be added based on configurations of the upper layer and the lower layer.
  • the new operation mode may include different interfaces based on the configurations of the upper layer and the lower layer. Whether to use the new operation mode may be designated using signaling or a system parameter.
  • data may be processed through all functions supported by the link layer, and then delivered to a physical layer.
  • each packet may be delivered to the link layer from an IP layer, an MPEG-2 TS layer, or another particular layer t89010.
  • an IP packet may be delivered to the link layer from an IP layer.
  • an MPEG-2 TS packet may be delivered to the link layer from the MPEG-2 TS layer, and a particular packet may be delivered to the link layer from a particular protocol layer.
  • Each of the delivered packets may go through or not go through an overhead reduction process t89020, and then go through an encapsulation process t89030.
  • the IP packet may go through or not go through the overhead reduction process t89020, and then go through the encapsulation process t89030. Whether the overhead reduction process t89020 is performed may be designated by signaling or a system parameter. According to a given embodiment, the overhead reduction process t89020 may be performed or not performed for each IP stream. An encapsulated IP packet may be delivered to the physical layer.
  • the MPEG-2 TS packet may go through the overhead reduction process t89020, and go through the encapsulation process t89030.
  • the MPEG-2 TS packet may not be subjected to the overhead reduction process t89020 according to a given embodiment.
  • a TS packet has sync bytes (0x47) and the like at the front and thus it may be efficient to eliminate such fixed overhead.
  • the encapsulated TS packet may be delivered to the physical layer.
  • a packet other than the IP or TS packet may or may not go through the overhead reduction process t89020, and then go through the encapsulation process t89030. Whether or not the overhead reduction process t89020 is performed may be determined according to characteristics of the corresponding packet. Whether the overhead reduction process t89020 is performed may be designated by signaling or a system parameter.
  • the encapsulated packet may be delivered to the physical layer.
  • a size of an input packet may be reduced through an appropriate scheme.
  • particular information may be extracted from the input packet or generated.
  • the particular information is information related to signaling, and may be transmitted through a signaling region.
  • the signaling information enables a receiver to restore an original packet by restoring changes due to the overhead reduction process t89020.
  • the signaling information may be delivered to a link layer signaling process t89050.
  • the link layer signaling process t89050 may transmit and manage the signaling information extracted/generated in the overhead reduction process t89020.
  • the physical layer may have physically/logically divided transmission paths for signaling, and the link layer signaling process t89050 may deliver the signaling information to the physical layer according to the divided transmission paths.
  • the above-described FIC signaling process t89060, EAS signaling process t89070, or the like may be included in the divided transmission paths. Signaling information not transmitted through the divided transmission paths may be delivered to the physical layer through the encapsulation process t89030.
  • Signaling information managed by the link layer signaling process t89050 may include signaling information delivered from the upper layer, signaling information generated in the link layer, a system parameter, and the like.
  • the signaling information may include signaling information delivered from the upper layer to be subsequently delivered to an upper layer of the receiver, signaling information generated in the link layer to be used for an operation of a link layer of the receiver, signaling information generated in the upper layer or the link layer to be used for rapid detection in a physical layer of the receiver, and the like.
  • Data going through the encapsulation process t89030 and delivered to the physical layer may be transmitted through a data pipe (DP) t89040.
  • the DP may be a physical layer pipe (PLP).
  • Signaling information delivered through the above-described divided transmission paths may be delivered through respective transmission paths.
  • an FIC signal may be transmitted through an FIC t89080 designated in a physical frame.
  • an EAS signal may be transmitted through an EAC t89090 designated in a physical frame.
  • Information about presence of a dedicated channel such as the FIC, the EAC, or the like may be transmitted to a preamble area of the physical layer through signaling, or signaled by scrambling a preamble using a particular scrambling sequence.
  • FIC signaling/EAS signaling information may be transmitted through a general DP area, PLS area, or preamble rather than a designated dedicated channel.
  • the receiver may receive data and signaling information through the physical layer.
  • the receiver may restore the received data and signaling information into a form processable in the upper layer, and deliver the restored data and signaling information to the upper layer. This process may be performed in the link layer of the receiver.
  • the receiver may verify whether a received packet is related to the signaling information or the data by reading a header of the packet and the like.
  • the receiver may restore a packet, overhead of which has been reduced through the overhead reduction process, to an original packet. In this process, the received signaling information may be used.
  • FIG. 4 illustrates an operation in a transparent mode corresponding to one of operation modes of a link layer according to an embodiment of the present invention.
  • data may not be subjected to functions supported by the link layer or may be subjected to some of the functions, and then delivered to a physical layer.
  • a packet delivered to an upper layer may be delivered to a physical layer without going through a separate overhead reduction and/or encapsulation process.
  • Other packets may go through the overhead reduction and/or encapsulation process as necessary.
  • the transparent mode may be referred to as a bypass mode, and another term may be applied to the transparent mode.
  • some packets may be processed in the normal mode and some packets may be processed in the transparent mode based on characteristics of the packets and a system operation.
  • a packet to which the transparent mode may be applied may be a packet having a type well known to a system.
  • the transparent mode may be used.
  • a well-known TS or IP packet may go through separate overhead reduction and input formatting processes in the physical layer and thus the transparent mode may be used in a link layer step.
  • an operation such as the above-described TS header compression may be performed in the physical layer.
  • a processed link layer packet may be treated as a GS packet and processed in the physical layer.
  • a link layer signaling module may be included when signal transmission needs to be supported.
  • the link layer signaling module may transmit and manage signaling information.
  • the signaling information may be encapsulated and transmitted through a DP, and FIC signaling information and EAS signaling information having divided transmission paths may be transmitted through an FIC and an EAC, respectively.
  • whether information corresponds to signaling information may be displayed using a fixed IP address and port number.
  • the signaling information may be filtered to configure a link layer packet, and then transmitted through the physical layer.
  • FIG. 5 illustrates a configuration of a link layer at a transmitter according to an embodiment of the present invention (normal mode).
  • the present embodiment is an embodiment presuming that an IP packet is processed.
  • the link layer at the transmitter may largely include a link layer signaling part for processing signaling information, an overhead reduction part, and/or an encapsulation part from a functional perspective.
  • the link layer at the transmitter may further include a scheduler t91020 for a control of the entire operation of the link layer and scheduling, input and output parts of the link layer, and/or the like.
  • upper layer signaling information and/or system parameter t91010 may be delivered to the link layer.
  • an IP stream including IP packets may be delivered to the link layer from an IP layer t91110.
  • the scheduler t91020 may determine and control operations of several modules included in the link layer.
  • the delivered signaling information and/or system parameter t91010 may be filtered or used by the scheduler t91020.
  • Information corresponding to a part of the delivered signaling information and/or system parameter t91010 and necessary for a receiver may be delivered to the link layer signaling part.
  • information corresponding to a part of the signaling information and necessary for an operation of the link layer may be delivered to an overhead reduction control block t91120 or an encapsulation control block t91180.
  • the link layer signaling part may collect information to be transmitted as signaling in the physical layer, and transform/configure the information in a form suitable for transmission.
  • the link layer signaling part may include a signaling manager t91030, a signaling formatter t91040, and/or a buffer for channels t91050.
  • the signaling manager t91030 may receive signaling information delivered from the scheduler t91020, signaling delivered from the overhead reduction part, and/or context information. The signaling manager t91030 may determine paths for transmission of the signaling information with respect to delivered data. The signaling information may be delivered through the paths determined by the signaling manager t91030. As described in the foregoing, signaling information to be transmitted through divided channels such as an FIC, an EAS, and the like may be delivered to the signaling formatter t91040, and other signaling information may be delivered to an encapsulation buffer t91070.
  • the signaling formatter t91040 may format associated signaling information in forms suitable for respective divided channels so that the signaling information may be transmitted through separately divided channels.
  • the physical layer may include physically/logically divided separate channels.
  • the divided channels may be used to transmit FIC signaling information or EAS-related information.
  • the FIC or EAS-related information may be divided by the signaling manager t91030 and input to the signaling formatter t91040.
  • the signaling formatter t91040 may format information such that the information is suitable for respective separate channels.
  • a signaling formatter for the particular signaling information may be added. Through this scheme, the link layer may be compatible with various physical layers.
  • the buffer for channels t91050 may deliver signaling information delivered from the signaling formatter t91040 to designated dedicated channels t91060.
  • the number and content of the dedicated channels t91060 may vary depending on an embodiment.
  • the signaling manager t91030 may deliver signaling information which is not delivered to a dedicated channel to the encapsulation buffer t91070.
  • the encapsulation buffer t91070 may function as a buffer that receives the signaling information not delivered to the dedicated channel.
  • An encapsulation for signaling information t91080 may encapsulate the signaling information not delivered to the dedicated channel.
  • a transmission buffer t91090 may function as a buffer that delivers the encapsulated signaling information to a DP for signaling information t91100.
  • the DP for signaling information t91100 may refer to the above-described PLS area.
  • the overhead reduction part may allow efficient transmission by eliminating overhead of packets delivered to the link layer. It is possible to configure overhead reduction parts, the number of which is the same as the number of IP streams input to the link layer.
  • An overhead reduction buffer t91130 may receive an IP packet delivered from an upper layer.
  • the delivered IP packet may be input to the overhead reduction part through the overhead reduction buffer t91130.
  • An overhead reduction control block t91120 may determine whether to perform overhead reduction on a packet stream input to the overhead reduction buffer t91130.
  • the overhead reduction control block t91120 may determine whether to perform overhead reduction for each packet stream.
  • packets When overhead reduction is performed on the packet stream, packets may be delivered to an RoHC compressor t91140 and overhead reduction may be performed.
  • packets When overhead reduction is not performed on the packet stream, packets may be delivered to the encapsulation part and encapsulation may be performed without overhead reduction.
  • Whether to perform overhead reduction on packets may be determined by signaling information t91010 delivered to the link layer.
  • the signaling information t91010 may be delivered to the encapsulation control block t91180 by the scheduler t91020.
  • the RoHC compressor t91140 may perform overhead reduction on a packet stream.
  • the RoHC compressor t91140 may compress headers of packets.
  • Various schemes may be used for overhead reduction. Overhead reduction may be performed by schemes proposed in the present invention.
  • the present embodiment presumes an IP stream and thus the compressor is expressed as the RoHC compressor. However, the term may be changed according to a given embodiment.
  • an operation is not restricted to compression of an IP stream, and overhead reduction may be performed on all types of packets by the RoHC compressor t91140.
  • a packet stream configuration block t91150 may divide IP packets having compressed headers into information to be transmitted to a signaling region and information to be transmitted to a packet stream.
  • the information to be transmitted to the packet stream may refer to information to be transmitted to a DP area.
  • the information to be transmitted to the signaling region may be delivered to a signaling and/or context control block t91160.
  • the information to be transmitted to the packet stream may be transmitted to the encapsulation part.
  • the signaling and/or context control block t91160 may collect signaling and/or context information and deliver the collected information to the signaling manager t91030. In this way, the signaling and/or context information may be transmitted to the signaling region.
  • the encapsulation part may encapsulate packets in suitable forms such that the packets may be delivered to the physical layer.
  • the number of configured encapsulation parts may be the same as the number of IP streams.
  • An encapsulation buffer t91170 may receive a packet stream for encapsulation. Packets subjected to overhead reduction may be received when overhead reduction is performed, and an input IP packet may be received without change when overhead reduction is not performed.
  • An encapsulation control block t91180 may determine whether to perform encapsulation on an input packet stream. When encapsulation is performed, the packet stream may be delivered to segmentation/concatenation t91190. When encapsulation is not performed, the packet stream may be delivered to a transmission buffer t91230. Whether to perform encapsulation of packets may be determined based on the signaling information t91010 delivered to the link layer. The signaling information t91010 may be delivered to the encapsulation control block t91180 by the scheduler t91020.
  • the above-descried segmentation or concatenation operation may be performed on packets.
  • one IP packet may be divided into several segments to configure a plurality of link layer packet payloads.
  • several IP packets may be combined to configure one link layer packet payload.
  • a packet configuration table t91200 may have information about a configuration of segmented and/or concatenated link layer packets.
  • a transmitter and a receiver may have the same information of the packet configuration table t91200. The transmitter and the receiver may refer to the information of the packet configuration table t91200.
  • An index value of the information of the packet configuration table t91200 may be included in headers of the link layer packets.
  • a link layer header information block t91210 may collect header information generated in an encapsulation process.
  • the link layer header information block t91210 may collect information included in the packet configuration table t91200.
  • the link layer header information block t91210 may configure header information according to a header configuration of a link layer packet.
  • a header attachment block t91220 may add headers to payloads of the segmented and/or concatenated link layer packets.
  • the transmission buffer t91230 may function as a buffer for delivering a link layer packet to a DP t91240 of the physical layer.
  • Each block or module and parts may be configured as one module/protocol or a plurality of modules/protocols in the link layer.
  • FIG. 6 illustrates a configuration of a link layer at a receiver according to an embodiment of the present invention (normal mode).
  • the present embodiment is an embodiment presuming that an IP packet is processed.
  • the link layer at the receiver may largely include a link layer signaling part for processing signaling information, an overhead processing part, and/or a decapsulation part from a functional perspective.
  • the link layer at the receiver may further include a scheduler for a control of the entire operation of the link layer and scheduling, input and output parts of the link layer, and/or the like.
  • information received through a physical layer may be delivered to the link layer.
  • the link layer may process the information to restore the information to an original state in which the information is not yet processed by a transmitter, and deliver the information to an upper layer.
  • the upper layer may be an IP layer.
  • the link layer signaling part may distinguish signaling information received from the physical layer, and deliver the distinguished signaling information to each part of the link layer.
  • a buffer for channels t92040 may function as a buffer that receives signaling information transmitted through the dedicated channels. As described above, when physically/logically divided separate channels are present in the physical layer, it is possible to receive signaling information transmitted through the channels. When the information received from the separate channels is in a divided state, the divided information may be stored until the information is in a complete form.
  • a signaling decoder/parser t92050 may check a format of signaling information received through a dedicated channel, and extract information to be used in the link layer.
  • decoding may be performed.
  • a signaling manager t92060 may integrate signaling information received through several paths. Signaling information received through a DP for signaling t92070 to be described below may be integrated by the signaling manager t92060.
  • the signaling manager t92060 may deliver signaling information necessary for each part in the link layer. For example, context information for recovery of a packet and the like may be delivered to the overhead processing part. In addition, signaling information for control may be delivered to a scheduler t92020.
  • General signaling information not received through a separate dedicated channel may be received through the DP for signaling t92070.
  • the DP for signaling may refer to a PLS or the like.
  • a reception buffer t92080 may function as a buffer for receiving the signaling information received from the DP for signaling t92070.
  • the received signaling information may be decapsulated in a decapsulation for signaling information block t92090.
  • the decapsulated signaling information may be delivered to the signaling manager t92060 through a decapsulation buffer t92100.
  • the signaling manager t92060 may collect signaling information and deliver the collected signaling information to a desired part in the link layer.
  • the scheduler t92020 may determine and control operations of several modules included in the link layer.
  • the scheduler t92020 may control each part of the link layer using receiver information t92010 and/or information delivered from the signaling manager t92060.
  • the scheduler t92020 may determine an operation mode and the like of each part.
  • the receiver information t92010 may refer to information previously stored by the receiver.
  • the scheduler t92020 may use information changed by a user such as a channel change and the like for control.
  • the decapsulation part may filter a packet received from a DP t92110 of the physical layer, and separate the packet based on a type of the packet.
  • the number of configured decapsulation parts may be the same as the number of DPs that may be simultaneously decoded in the physical layer.
  • a decapsulation buffer t92120 may function as a buffer that receives a packet stream from the physical layer to perform decapsulation.
  • a decapsulation control block t92130 may determine whether to decapsulate the received packet stream. When decapsulation is performed, the packet stream may be delivered to a link layer header parser t92140. When decapsulation is not performed, the packet stream may be delivered to an output buffer t92220. The signaling information delivered from the scheduler t92020 may be used to determine whether to perform decapsulation.
  • the link layer header parser t92140 may identify a header of a received link layer packet.
  • the header is identified, it is possible to identify a configuration of an IP packet included in a payload of the link layer packet.
  • the IP packet may be segmented or concatenated.
  • a packet configuration table t92150 may include payload information of link layer packets configured through segmentation and/or concatenation.
  • the transmitter and the receiver may have the same information as information of the packet configuration table t92150.
  • the transmitter and the receiver may refer to the information of the packet configuration table t92150.
  • a value necessary for reassembly may be found based on index information included in the link layer packets.
  • a reassembly block t92160 may configure payloads of the link layer packets configured through segmentation and/or concatenation as packets of an original IP stream.
  • the reassembly block t92160 may reconfigure one IP packet by collecting segments, or reconfigure a plurality of IP packet streams by separating concatenated packets.
  • the reassembled IP packets may be delivered to the overhead processing part.
  • the overhead processing part may perform a reverse process of overhead reduction performed by the transmitter.
  • the reverse process an operation of returning packets experiencing overhead reduction to original packets is performed. This operation may be referred to as overhead processing.
  • the number of configured overhead processing parts may be the same as the number of DPs that may be simultaneously decoded in the physical layer.
  • a packet recovery buffer t92170 may function as a buffer that receives an RoHC packet or an IP packet decapsulated for overhead processing.
  • An overhead control block t92180 may determine whether to perform packet recovery and/or decompression of decapsulated packets. When the packet recovery and/or decompression are performed, the packets may be delivered to a packet stream recovery t92190. When the packet recovery and/or decompression are not performed, the packets may be delivered to the output buffer t92220. Whether to perform the packet recovery and/or decompression may be determined based on the signaling information delivered by the scheduler t92020.
  • the packet stream recovery t92190 may perform an operation of integrating a packet stream separated from the transmitter and context information of the packet stream.
  • the operation may correspond to a process of restoring the packet stream such that the packet stream may be processed by an RoHC decompressor t92210.
  • signaling information and/or context information may be delivered from a signaling and/or context control block t92200.
  • the signaling and/or context control block t92200 may distinguish signaling information delivered from the transmitter and deliver the signaling information to the packet stream recovery t92190 such that the signaling information may be mapped to a stream suitable for a context ID.
  • the RoHC decompressor t92210 may recover headers of packets of a packet stream. When the headers are recovered, the packets of the packet stream may be restored to original IP packets. In other words, the RoHC decompressor t92210 may perform overhead processing.
  • the output buffer t92220 may function as a buffer before delivering an output stream to an IP layer t92230.
  • the link layer of the transmitter and the receiver proposed in the present invention may include the blocks or modules described above.
  • the link layer may independently operate irrespective of the upper layer and the lower layer, and efficiently perform overhead reduction.
  • a function which is supportable depending on the upper and lower layers may be easily extended/added/deleted.
  • FIG. 7 is a diagram illustrating definition according to link layer organization type according to an embodiment of the present invention.
  • a link layer When a link layer is actually embodied as a protocol layer, a broadcast service can be transmitted and received through one frequency slot.
  • an example of one frequency slot may be a broadcast channel that mainly has a specific bandwidth.
  • a compatible link layer in a broadcast system in which a configuration of a physical layer is changed or in a plurality of broadcast systems with different physical layer configurations, a compatible link layer may be defined.
  • the physical layer may have a logical data path for an interface of a link layer.
  • the link layer may access the logical data path of the physical layer and transmit information associated with the corresponding data path to the logical data path.
  • the following types may be considered as the data path of the physical layer interfaced with the link layer.
  • a normal data pipe may exist as a type of data path.
  • the normal data pipe may be a data pipe for transmission of normal data and may include one or more data pipes according to a configuration of a physical layer.
  • a base data pipe may exist as a type of data path.
  • the base data pipe may be a data pipe used for specific purpose and may transmit signaling information (entire or partial signaling information described in the present invention) and/or common data in a corresponding frequency slot.
  • signaling information encoded in the present invention
  • common data common data in a corresponding frequency slot.
  • data that is generally transmitted through a normal data pipe may be transmitted through a base data pipe.
  • the base data pipe may perform a complementary function. That is, data that exceeds the processing capacity of the corresponding channel may be transmitted through the base data pipe.
  • the base data pipe continuously uses one designated data pipe.
  • one or more data pipes may be dynamically selected for the base data pipe among a plurality of data pipes using a method such as physical layer signaling, link layer signaling, or the like in order to effectively manage a data pipe.
  • a dedicated channel may exist as a type of data path.
  • the dedicated channel may be a channel used for signaling in a physical layer or a similar specific purpose and may include a fast information channel (FIC) for rapidly acquiring matters that are mainly served on a current frequency slot and/or an emergency alert channel (EAC) for immediately transmitting notification of emergency alert to a user.
  • FIC fast information channel
  • EAC emergency alert channel
  • a logical data path is embodied in a physical layer in order to transmit the normal data pipe.
  • a logical data path for the base data pipe and/or the dedicated channel may not be embodied in a physical layer.
  • a configuration of data to be transmitted in the link layer may be defined as illustrated in the drawing.
  • Organization Type 1 may refer to the case in which a logical data path includes only a normal data pipe.
  • Organization Type 2 may refer to the case in which a logical data path includes a normal data pipe and a base data pipe.
  • Organization Type 3 may refer to the case in which a logical data path includes a normal data pipe and a dedicated channel.
  • Organization Type 4 may refer to the case in which a logical data path includes a normal data pipe, a data base pipe, and a dedicated channel.
  • the logical data path may include a base data pipe and/or a dedicated channel.
  • a transmission procedure of signaling information may be determined according to configuration of a logical data path. Detailed information of signaling transmitted through a specific logical data path may be determined according to a protocol of a higher layer of a link layer defined in the present invention. Regarding a procedure described in the present invention, signaling information parsed through a higher layer may also be used and corresponding signaling may be transmitted in the form of an IP packet from the higher layer and transmitted again after being encapsulated in the form of a link layer packet.
  • a receiver may extract detailed signaling information from session information included in an IP packet stream according to protocol configuration.
  • a database DB
  • a shared memory may be used.
  • the extracted signaling information may be stored in a DB, a buffer, and/or a shared memory of the receiver.
  • the signaling information may be obtained from the above storage device.
  • FIG. 8 is a diagram illustrating processing of a broadcast signal when a logical data path includes only a normal data pipe according to an embodiment of the present invention.
  • the diagram illustrates a structure of a link layer when the logical of the physical layer includes only a normal data pipe.
  • the link layer may include a link layer signaling processor, an overhead reduction processor, and an encapsulation (decapsulation) processor. Transmission of information output from each functional module (which may be embodied as hardware or software) to an appropriate data path of the physical layer may be one of main functions of the link layer.
  • a plurality of packet streams may be transmitted according to a data rate at which data is to be transmitted, and overhead reduction and encapsulation procedures may be performed for each respective corresponding packet stream.
  • a physical layer may include a data pipe (DP) as a plurality of logical data paths that a link layer can access in one frequency band and may transmit a packet stream processed in a link layer for each respective packet stream.
  • DP data pipe
  • some of the packet streams may be multiplexed and input to a DP in consideration of a data rate.
  • the signaling processor may check transmission system information, related parameters, and/or signaling transmitted in a higher layer and collect information to be transmitted via signaling. Since only a normal data pipe is configured in a physical layer, corresponding signaling needs to be transmitted in the form of packet. Accordingly, signaling may be indicated using a header, etc. of a packet during link layer packet configuration. In this case, a header of a packet including signaling may include information for identifying whether signaling data is contained in a payload of the packet.
  • a packet including signaling may be found using a filtering method of an IP address.
  • IANA designates an IP address of 224.0.23.60 as ATSC service signaling
  • the receiver may check an IP packet having the corresponding IP address use the IP packet for configuration of link layer signaling.
  • the corresponding packet needs to also be transmitted to a receiver, processing for the IP packet is performed without change.
  • the receiver may parse an IP packet transmitted to a predetermined IP address and acquire data for signaling in a link layer.
  • the receiver When a plurality of broadcast services are transmitted through one frequency band, the receiver does not have to decode all DPs, and it is efficient to pre-check signaling information and to decode only a DP associated with a required service. Accordingly, with regard to an operation for a link layer of the receiver, the following procedures may be performed.
  • the receiver tunes a corresponding frequency and reads information of the receiver, stored in a DB, etc. with regard to a corresponding channel.
  • the receiver checks information about a DP that transmits link layer signaling and decodes the corresponding DP to acquire a link layer signaling packet.
  • the receiver parses the link layer signaling packet and acquires information about a DP that transmits data associated with a service selected by the user among one or more DPs transmitted through a current channel and overhead reduction information about a packet stream of the corresponding DP.
  • the receiver may acquire information for identification of a DP that transmits the data associated with the service selected by the user from a link layer signaling packet and obtain a corresponding DP based on the information.
  • the link layer signaling packet may include information indicating overhead reduction applied to the corresponding DP, and the receiver may restore a DP to which overhead reduction is applied, using the information.
  • the receiver transmits DP information to be received, to a physical layer processor that processes a signal or data in a physical layer and receives a packet stream from a corresponding DP.
  • the receiver performs encapsulation and header recovery on the packet stream decoded by the physical layer processor.
  • the receiver performs processing according to a protocol of a higher layer and provides a broadcast service to the user.
  • FIG. 9 is a diagram illustrating processing of a broadcast signal when a logical data path includes a normal data pipe and a base data pipe according to an embodiment of the present invention.
  • the diagram illustrates a structure of a link layer when the logical data path of the physical layer includes a base data pipe and a normal data pipe.
  • the link layer may include a link layer signaling part, an overhead reduction part, and an encapsulation (decapsulation) part.
  • a link layer processor for processing a signal and/or data in a link layer may include a link layer signaling processor, an overhead reduction processor, and an encapsulation (decapsulation) processor.
  • Transmission of information output from each functional module (which may be embodied as hardware or software) to an appropriate data path of the physical layer may be one of main functions of the link layer.
  • a plurality of packet streams may be transmitted according to a data rate at which data is to be transmitted, and overhead reduction and encapsulation procedures may be performed for each respective corresponding packet stream.
  • a physical layer may include a data pipe (DP) as a plurality of logical data paths that a link layer can access in one frequency band and may transmit a packet stream processed in a link layer for each respective packet stream.
  • DP data pipe
  • the signaling processor may check transmission system information, related parameters, higher layer signaling, etc. and collect information to be transmitted via signaling. Since a broadcast signal of the physical layer includes a base DP and a normal DP, signaling may be transmitted to the base DP and signaling data may be transmitted in the form of packet appropriate for transmission of the base DP in consideration of a data rate. In this case, signaling may be indicated using a header, etc. of a packet during link layer packet configuration. For example, a header of a link layer packet may include information indicating that data contained in a payload of the packet is signaling data.
  • a logical data path such as a base DP exists
  • service signaling that is transmitted in the form of IP packet in a higher layer may be transmitted to the base DP using a method such as IP address filtering, etc.
  • IANA designates an IP address of 224.0.23.60 as ATSC service signaling
  • an IP packet stream with the corresponding IP address may be transmitted to the base DP.
  • the IP packet streams may be transmitted to one base DP using a method such as multiplexing, etc.
  • a packet about different service signaling may be divided into field values such as a source address and/or a port. In this case, information required for configuration of link layer signaling can also be read from the corresponding service signaling packet.
  • the receiver may not have to decode all DPs, may pre-check signaling information, and may decode only a DP that transmits data and/or a signal about a corresponding service. Accordingly, the receiver may perform the following operation with regard to data and/or processing in a link layer.
  • the receiver tunes a corresponding frequency and reads information of the receiver, stored in a DB, etc. with regard to a corresponding channel.
  • the information stored in the DB, etc. may include information for identification of the base DP.
  • the receiver decodes the base DP and acquires a link layer signaling packet included in the base DP.
  • the receiver parses the link layer signaling packet to acquire DP information for reception of the service selected by the user and overhead reduction information about a packet stream of the corresponding DP among a plurality of DPs transmitted through a current channel and overhead reduction information about a packet stream of the corresponding DP.
  • the link layer signaling packet may include information for identification of a DP that transmits a signal and/or data associated with a specific service, and/or information for identification of a type of overhead reduction applied to a packet stream transmitted to the corresponding DP.
  • the receiver may access one or more DPs or restore the packet included in the corresponding DP using the above information.
  • the receiver is a physical layer processor that processes a signal and/or data according to a protocol of a physical layer, transmits information about a DP to be received for a corresponding service, and receives a packet stream from the corresponding DP.
  • the receiver performs decapsulation and header recovery on the packet stream decoded in the physical layer and transmits the packet stream to a higher layer of the receiver in the form of IP packet stream.
  • the receiver performs processing according to a higher layer protocol and provides a broadcast service to the user.
  • information about the base DP may be acquired during previous channel scan and then stored in a DB and the receiver may use the stored base DP.
  • the receiver may acquire the base DP by first seeking a DP that the receiver has pre-accessed.
  • the receiver may acquire corresponding information from the DB, the buffer, and/or the shared memory as described above and use the acquired information as information about a DP requiring decoding.
  • higher layer signaling e.g., a layer higher than a link layer, or an IP layer
  • link layer signaling (link layer signaling information) and normal data (e.g., broadcast content data) is transmitted through the same DP or if only a DP of one type is used in a broadcast system
  • the normal data transmitted through the DP may be temporarily stored in the buffer or the memory while the signaling information is decoded and parsed.
  • the receiver may transmit a command for extracting a DP that should be obtained according to the corresponding signaling information to a device for extracting and processing the DP by a method using interior command words of the system.
  • FIG. 10 is a diagram illustrating processing of a broadcast signal when a logical data path includes a normal data pipe and a dedicated channel according to an embodiment of the present invention.
  • the diagram illustrates a structure of a link layer when the logical data path of the physical layer includes a dedicated channel and a normal data pipe.
  • the link layer may include a link layer signaling part, an overhead reduction part, and an encapsulation (decapsulation) part.
  • a link layer processor to be included in the receiver may include a link layer signaling processor, an overhead reduction processor, and/or an encapsulation (decapsulation) processor. Transmission of information output from each functional module (which may be embodied as hardware or software) to an appropriate data path of the physical layer may be one of main functions of the link layer.
  • a plurality of packet streams may be transmitted according to a data rate at which data is to be transmitted, and overhead reduction and encapsulation procedures may be performed for each respective corresponding packet stream.
  • a physical layer may include a data pipe (DP) as a plurality of logical data paths that a link layer can access in one frequency band and may transmit a packet stream processed in a link layer for each respective packet stream.
  • DP data pipe
  • some of the packet streams may be multiplexed and input to a DP in consideration of a data rate.
  • the signaling processor may check transmission system information, related parameters, higher layer signaling, etc. and collect information to be transmitted via signaling.
  • a logical data path such as a dedicate channel exists
  • a bandwidth for the dedicated channel corresponding to the amount of the dedicated channel needs to be occupied, and thus it is general to set a high data rate of the dedicated channel.
  • a dedicated channel is generally received and decoded at higher speed than a DP, it is more efficient to signaling data in terms of information that needs to be rapidly acquired from the receiver.
  • signaling data such as the aforementioned link layer signaling packet may be transmitted through the normal DP
  • signaling data transmitted through the dedicated channel may include information for identification of the corresponding link layer signaling packet.
  • a plurality of dedicated channels may exist as necessary and a channel may be enable/disable according to a physical layer.
  • IP packet including signaling may be found using a filtering method of an IP address.
  • IANA designates an IP address of 224.0.23.60 as ATSC service signaling
  • the receiver may check an IP packet having the corresponding IP address use the IP packet for configuration of link layer signaling.
  • the corresponding packet needs to also be transmitted to a receiver, processing for the IP packet is performed without change.
  • the IP packet streams may be transmitted to one DP together with audio/video data using a method such as multiplexing, etc.
  • a packet about service signaling and audio/video data may be divided into field values of an IP address, a port, etc.
  • the receiver When a plurality of broadcast services are transmitted through one frequency band, the receiver does not have to decode all DPs, and it is efficient to pre-check signaling information and to decode only a DP that transmit signal and/or data associated with a required service.
  • the receiver may perform processing according to a protocol of a link layer as the following procedure.
  • the receiver tunes a corresponding frequency and reads information stored in a DB, etc. with regard to a corresponding channel.
  • the information stored in the DB may include information for identification of a dedicated channel and/or signaling information for acquisition of channel/service/program.
  • the receiver decodes data transmitted through the dedicated channel and performs processing associated with signaling appropriate for purpose of the corresponding channel.
  • a dedicated channel for transmission of FIC may store and update information such as a service and/or a channel
  • a dedicated channel for transmission of EAC may transmit emergency alert information.
  • the receiver may acquire information of DP to be decoded using information transmitted to the dedicated channel.
  • the receiver may pre-decode a DP that transmits signaling and transmit the DP to a dedicated channel in order to pre-acquire signaling information.
  • a packet for link layer signaling may be transmitted through a normal DP, and in this case, the signaling data transmitted through the dedicated channel may include information for identification of a DP including a packet for link layer signaling.
  • the receiver acquires DP information for reception of a service selected by a user among a plurality of DPs that are transmitted to a current channel and overhead reduction information about a packet stream of the corresponding DP using the link layer signaling information.
  • the link layer signaling information may include information for identification of a DP for transmission of a signal and/or data associated with a specific service, and/or information for identification of a type of overhead reduction applied to a packet stream transmitted to the corresponding DP.
  • the receiver may access one or more DPs for a specific service or restore a packet included in the corresponding DP using the information.
  • the receiver transmits information for identification of a DP to be received by a physical layer to a physical layer processor that processes a signal and/or data in a physical layer and receives a packet stream from the corresponding DP.
  • the receiver performs decapsulation and header recovery on a packet stream decoded in a physical layer and transmits the packet stream to a higher layer of the receiver in the form of IP packet stream.
  • the receiver performs processing according to a protocol of a higher layer and provides a broadcast service to the user.
  • FIG. 11 is a diagram illustrating processing of a broadcast signal when a logical data path includes a normal data pipe, a base data pipe, and a dedicated channel according to an embodiment of the present invention.
  • the diagram illustrates a structure of a link layer when the logical data path of the physical layer includes a dedicated channel, a base data pipe, and a normal data pipe.
  • the link layer may include a link layer signaling part, an overhead reduction part, and an encapsulation (decapsulation) part.
  • a link layer processor to be included in the receiver may include a link layer signaling processor, an overhead reduction processor, and/or an encapsulation (decapsulation) processor. Transmission of information output from each functional module (which may be embodied as hardware or software) to an appropriate data path of the physical layer may be one of main functions of the link layer.
  • a plurality of packet streams may be transmitted according to a data rate at which data is to be transmitted, and overhead reduction and encapsulation procedures may be performed for each respective corresponding packet stream.
  • a physical layer may include a data pipe (DP) as a plurality of logical data paths that a link layer can access in one frequency band and may transmit a packet stream processed in a link layer for each respective packet stream.
  • DP data pipe
  • some of the packet streams may be multiplexed and input to a DP in consideration of a data rate.
  • the signaling processor may check transmission system information, related parameters, higher layer signaling, etc. and collect information to be transmitted via signaling. Since a signal of the physical layer includes a base DP and a normal DP, it may be efficient to transmit signaling to the base DP in consideration of a data rate. In this case, the signaling data needs to be transmitted in the form of packet appropriate for transmission through the base DP. Signaling may be indicated using a header, etc. of a packet during link layer packet configuration. That is, a header of a link layer signaling packet including signaling data may include information indicating that signaling data is contained in a payload of the corresponding packet.
  • signaling information may be divided and transmitted to the dedicated channel and the base DP.
  • signaling information since a high data rate of the dedicated channel is not set, signaling information that has a small amount of signaling and needs to be rapidly acquired may be transmitted to the dedicated channel and signaling with a high amount of signaling to the base DP.
  • a plurality of dedicated channels may exist and a channel may be enable/disable according to a physical layer.
  • the base DP may be configured with a separate structure from a normal DP.
  • Service signaling that is transmitted in the form of IP packet in a higher layer may be transmitted to the base DP using a method such as IP address filtering, etc.
  • An IP packet stream with a specific IP address and including signaling information may be transmitted to the base DP.
  • the IP packet streams may be transmitted to one base DP using a method such as multiplexing, etc.
  • a packet about different service signaling may be divided into field values such as a source address and/or a port.
  • the receiver may read information required for configuration of the link layer signaling in the corresponding service signaling packet.
  • the receiver may not have to decode all DPs, and it may be efficient to pre-check the signaling information and to decode only a DP that transmits a signal and/or data associated with a required service.
  • the receiver may perform the following processors as processing according to a protocol of a link layer.
  • the receiver tunes a corresponding frequency and reads information stored in a database DB, etc. with regard to a corresponding channel.
  • the information stored in the DB may include information for identification of a dedicated channel, information for identification of a base data pipe, and/or signaling information for acquisition of channel/service/program.
  • the receiver decodes data transmitted through the dedicated channel and performs processing associated with signaling appropriate for purpose of the corresponding channel.
  • a dedicated channel for transmission of FIC may store and update information such as a service and/or a channel
  • a dedicated channel for transmission of EAC may transmit emergency alert information.
  • the receiver may acquire information of the base DP using information transmitted to the dedicated channel.
  • the information transmitted to the dedicated channel may include information for identification of the base DP (e.g., an identifier of the base DP and/or an IP address of the base DP).
  • the receiver may update signaling information pre-stored in a DB of the receiver and related parameters to information transmitted in the dedicated channel.
  • the receiver may decode the base DP and acquire a link layer signaling packet. As necessary, the link layer signaling packet may be combined with signaling information received from the dedicated channel. The receiver may find the base DP using the dedicate channel and the signaling information pre-stored in the receiver.
  • the receiver acquires DP information for reception of a service selected by a user among a plurality of DPs that are transmitted to a current channel and overhead reduction information about a packet stream of the corresponding DP using the link layer signaling information.
  • the link layer signaling information may include information for identification of a DP for transmission of a signal and/or data associated with a specific service, and/or information for identification of a type of overhead reduction applied to a packet stream transmitted to the corresponding DP.
  • the receiver may access one or more DPs for a specific service or restore a packet included in the corresponding DP using the information.
  • the receiver transmits information for identification of a DP to be received by a physical layer to a physical layer processor that processes a signal and/or data in a physical layer and receives a packet stream from the corresponding DP.
  • the receiver performs decapsulation and header recovery on a packet stream decoded in a physical layer and transmits the packet stream to a higher layer of the receiver in the form of IP packet stream.
  • the receiver performs processing according to a protocol of a higher layer and provides a broadcast service to the user.
  • the IP packet streams may be multiplexed and transmitted as one base DP.
  • the receiver may distinguish between packets for different service signaling through a field of a source address and/or a port.
  • the receiver may read out information for acquiring/configuring link layer signaling from a service signaling packet.
  • the receiver may obtain version information of the dedicated channel or information identifying whether update has been performed and, if it is judged that there is no change in the signaling information in the dedicated channel, the receiver may omit processing (decoding or parsing) of the signaling information transmitted through the dedicated channel. If it is confirmed that the dedicated channel has not been updated, the receiver may acquire information of a base DP using prestored information.
  • the receiver may acquire the corresponding information from the DB, the buffer, and/or the shared memory as described above and use the acquired information as information about a DP requiring decoding.
  • higher layer signaling e.g., a layer higher than a link layer, or an IP layer
  • link layer signaling (link layer signaling information) and normal data (e.g., broadcast content data)
  • normal data e.g., broadcast content data
  • the normal data transmitted through the DP may be temporarily stored in the buffer or the memory while the signaling information is decoded and parsed.
  • the receiver may transmit a command for extracting a DP that should be obtained according to the corresponding signaling information to a device for extracting and processing the DP by a method using system interior command words.
  • FIG. 12 is a diagram illustrating a detailed processing operation of a signal and/or data in a link layer of a receiver when a logical data path includes a normal data pipe, a base data pipe, and a dedicated channel according to an embodiment of the present invention.
  • the present embodiment considers a situation in which one or more services provided by one or more broadcasters are transmitted in one frequency band. It may be considered that one broadcaster transmits one or more broadcast services, one service includes one or more components and a user receives content in units of broadcast services. In addition, some of one or more components included in one broadcast service may be replaced with other components according to user selection.
  • a fast information channel (FIC) and/or emergency alert channel (EAC) may be transmitted to a dedicated channel.
  • a base DP and a normal DP may be differentiated in a broadcast signal and transmitted or managed.
  • Configuration information of the FIC and/or the EAC may be transmitted through physical layer signaling so as to notify the receiver of the FIC and/or the EAC, and the link layer may format signaling according to the characteristic of the corresponding channel. Transmission of data to a specific channel of a physical layer is performed from a logical point of view and an actual operation may be performed according to the characteristic of a physical layer.
  • Information about a service of each broadcaster, transmitted in a corresponding frequency, and information about a path for reception of the service may be transmitted through the FIC. To this end, the following information may be provided (signaled) via link layer signaling.
  • Link layer - which includes context information associated with IP header compression and/or ID of a DP to which corresponding context is applied.
  • a receiver may not have to decode all DPs, and it may be efficient to pre-check signaling information and to decode only a DP about a required service.
  • a transmitter may transmit information for identification of only a required DP through an FIC, and the receiver may check a DP to be accessed for a specific serviced, using the FIC.
  • an operation associated with the link layer of the receiver may be performed as follows.
  • the receiver tunes a corresponding frequency and reads information of a receiver, stored in a DB, etc. in regard to a corresponding channel.
  • the information stored in the DB of the receiver may be configured by acquiring an FIC during initial channel scan and using information included in the FIC.
  • the receiver may receive an FIC and update a pre-stored DB or acquire information about a component about a service selected by the user and information about a mapping relation for DPs that transmit components from the FIC.
  • the information about a base DP that transmits signaling may be acquired from the FIC.
  • the receiver may acquire the initialization information and prepare header recovery.
  • RoHC robust header compression
  • the receiver decodes a base DP and/or a DP that transmits a service selected by a user based on information transmitted through the FIC.
  • the receiver acquires overhead reduction information about a DP that is being received, included in the base DP, performs decapsulation and/or header recovery on a packet stream received in a normal DP using the acquired overhead information, and transmits the packet stream to a higher layer of the receiver in the form of IP packet stream.
  • the receiver may receive service signaling transmitted in the form of IP packet with a specific address through a base DP and transmit the packet stream to the higher layer with regard to a received service.
  • the receiver receives signaling information included in a CAP message through signaling, parses the signaling information, and immediately transmits the signaling information to a user, and finds a path for reception of a corresponding service and receives service data when information of a path through which an audio/video service can be received via signaling can be confirmed.
  • an NRT service and additional information are received using corresponding uniform resource identifier (URI) information and so on.
  • URI uniform resource identifier
  • the receiver processes the emergency alert as follows.
  • the receiver recognizes a situation in which an emergency alert message is transmitted through a preamble and so on of a physical layer.
  • the preamble of the physical layer may be a signaling signal included in a broadcast signal and may correspond to signaling in the physical layer.
  • the preamble of the physical layer may mainly include information for acquisition of data, a broadcast frame, a data pipe, and/or a transmission parameter that are included in a broadcast signal.
  • the receiver checks configuration of an emergency alert channel (EAC) through physical layer signaling of the receiver and decodes the EAC to acquire EAT.
  • EAC emergency alert channel
  • the EAC may correspond to the aforementioned dedicated channel.
  • the receiver checks the received EAT, extracts a CAP message, and transmits the CAP message to a CAP parser.
  • the receiver decodes a corresponding DP and receives service data when service information associated with the emergency alert is present in the EAT.
  • the EAT may include information for identification of a DP for transmitting a service associated with the emergency alert.
  • the receiver When information associated with NRT service data is present in the EAT or the CAP message, the receiver receives the information through a broadband.
  • FIG. 13 is a diagram illustrating syntax of a fast information channel (FIC) according to an embodiment of the present.
  • FIC fast information table
  • Information included in the FIT may be transmitted in the form of XML and/or section table.
  • the FIT may include table_id information, FIT_data_version information, num_broadcast information, broadcast_id information, delivery_system_id information, base_DP_id information, base_DP_version information, num_service information, service_id information, service_category information, service_hidden_flag information, SPindicator information, num_component information, component id information, DP id information, context id information, RoHC_init_descriptor, context_profile information, max_cid information, and/or large_cid information.
  • the table_id information indicates that a corresponding table section refers to fast information table.
  • the FIT_data_version information may indicate version information about syntax and semantics contained in the fast information table.
  • the receiver may determine whether signaling contained in the corresponding fast information table is processed, using the FIT_data_version information.
  • the receiver may determine whether information of pre-stored FIC is updated, using the information.
  • the num_broadcast information may indicate the number of broadcasters that transmit a broadcast service and/or content through a corresponding frequency or a transmitted transport frame.
  • the broadcast_id information may indicate a unique identifier of a broadcaster that transmits a broadcast service and/or content through a corresponding frequency or a transmitted transport frame.
  • broadcast id may have a value such as transport_stream_id of MPEG-2 TS.
  • the delivery_system id information may indicate an identifier for a broadcast transmission system that applies and processes the same transmission parameter on a broadcast network that performs transmission.
  • the base DP id information is information for identification of a base DP in a broadcast signal.
  • the base DP may refer to a DP that transmits service signaling including overhead reduction and/or program specific information/system information (PSI/SI) of a broadcaster corresponding to broadcast_id.
  • PSI/SI program specific information/system information
  • the base_DP_id information may refer to a representative DP that can decode a component included in a broadcast service in the corresponding broadcaster.
  • the base_DP_version information may refer to version information about data transmitted through a base DP. For example, when service signaling such as PSI/SI and so on is transmitted through the base DP, if service signaling is changed, a value of the base_DP_version information may be increased one by one.
  • the num_service information may refer to the number of broadcast services transmitted from a broadcaster corresponding to the broadcast_id in a corresponding frequency or a transport frame.
  • the service_id information may be used as an identifier for identification of a broadcast service.
  • the service_category information may refer to a category of a broadcast service. According to a value of a corresponding field, the service_category information may have the following meaning.
  • the service_category information may refer to a basic TV
  • the service_category information may refer to a basic radio
  • the service_category information may refer to an RI service
  • the service_category information may refer to a service guide
  • the service_category information may refer to emergency alerting.
  • the service_hidden_flag information may indicate whether a corresponding broadcast service is hidden.
  • the broadcast service may be a test service or a self-used service and may be processed to be disregarded or hidden from a service list by a broadcast receiver.
  • the SP_indicator information may indicate whether service protection is applied to one or more components in a corresponding broadcast service.
  • the num component information may indicate the number of components included in a corresponding broadcast service.
  • the component_id information may be used as an identifier for identification of a corresponding component in a broadcast service.
  • the DP id information may be used as an identifier indicating a DP that transmits a corresponding component.
  • the RoHC_init_descriptor may include information associated with overhead reduction and/or header recovery.
  • the RoHC_init_descriptor may include information for identification of a header compression method used in a transmission terminal.
  • the context_id information may represent a context corresponding to a following RoHC related field.
  • the context_id information may correspond to a context identifier (CID).
  • the context_profile information may represent a range of a protocol for compression of a header in RoHC.
  • a compressor and a decompressor have the same profile, it is possible to compress and restore a stream in the RoHC.
  • the max_cid information is used for indicating a maximum value of a CID to a decompressor.
  • the large_cid information has a boolean value and indicates whether a short CID (0 to 15) or an embedded CID (0 to 16383) is used for CID configuration. Accordingly, the sized of byte for representing the CID is determined together.
  • FIG. 14 is a diagram illustrating syntax of an emergency alert table (EAT) according to an embodiment of the present invention.
  • the EAC may correspond to the aforementioned dedicated channel.
  • the EAT may include EAT_protocol_version information, automatic_tuning_flag information, num_EAS_messages information, EAS_message_id information, EAS_IP_version_flag information, EAS_message_transfer_type information, EAS_message_encoding_type information, EAS_NRT_flag information, EAS_message_length information, EAS_message_byte information, IP_address information, UDP_port_num information, DP_id information, automatic_tuning_channel_number information, automatic_tuning_DP_id information, automatic_tuning_service_id information, and/or EAS_NRT_service_id information.
  • the EAT_protocol_version information indicates a protocol version of received EAT.
  • the automatic_tuning_flag information indicates whether a receiver automatically performs channel conversion.
  • the num_EAS_messages information indicates the number of messages contained in the EAT.
  • the EAS_message_id information is information for identification of each EAS message.
  • the EAS_IP_version_flag information indicates IPv4 when a value of the EAS_IP_version_flag information is 0, and indicates IPv6 when a value of the EAS_IP_version_flag information is 1.
  • the EAS_message_transfer_type information indicates the form in which an EAS message is transmitted.
  • the EAS_message_transfer_type information indicates a not specified state
  • the EAS_message_transfer_type information indicates a no alert message (only AV content)
  • the EAS_message_transfer_type information indicates that an EAS message is contained in corresponding EAT. To this end, a length field and a field about the corresponding EAS message are added.
  • the EAS_message_transfer_type information indicates that the EAS message is transmitted through a data pipe.
  • the EAS may be transmitted in the form of IP datagram in a data pipe.
  • IP address, UDP port information, and DP information of a transmitted physical layer may be added.
  • the EAS_message_encoding_type information indicates information about an encoding type of an emergence alert message. For example, when a value of the EAS_message_encoding_type information is 000, the EAS_message_encoding_type information indicates a not specific state, when a value of the EAS_message_encoding_type information is 001, the EAS_message_encoding_type information indicates No Encoding, when a value of the EAS_message_encoding_type information is 010, the EAS_message_encoding_type information indicates DEFLATE algorithm (RFC1951), and 001 to 111 among values of the EAS_message_encoding_type information may be reserved for other encoding types.
  • RRC1951 DEFLATE algorithm
  • the EAS_NRT_flag information indicates whether NRT contents and/or NRT data associated with a received message is present. When a value of the EAS_NRT_flag information is 0, the EAS_NRT_flag information indicates that NRT contents and/or NRT data associated with a received emergency message is not present, and when a value of the EAS_NRT_flag information is 1, the EAS_NRT_flag information indicates that NRT contents and/or NRT data associated with a received emergency message is present.
  • the EAS_message_length information indicates a length of an EAS message.
  • the EAS_message_byte information includes content of an EAS message.
  • the IPaddress information indicates an IP address of an IP address for transmission of an EAS message.
  • the UDP_port_num information indicates a UDP port number for transmission of an EAS message.
  • the DP id information identifies a data pipe that transmits an EAS message.
  • the automatic_tuning_channel_number information includes information about a number of a channel to be converted.
  • the automatic_tuning_DP_id information is information for identification of a data pipe that transmits corresponding content.
  • the automatic_tuning_service_id information is information for identification of a service to which corresponding content belongs.
  • the EAS_NRT_service_id information is information for identification of an NRT service corresponding to the case in which NRT contents and data associated with a received emergency alert message and transmitted, that is, the case in which an EAS_NRT_flag is enabled.
  • FIG. 15 is a diagram illustrating a packet transmitted to a data pipe according to an embodiment of the present invention.
  • configuration of a packet in a link layer is newly defined so as to generate a compatible link layer packet irrespective of change in protocol of a higher layer or the link layer or a lower layer of the link layer.
  • the link layer packet according to an embodiment of the present invention may be transmitted to a normal DP and/or a base DP.
  • the link layer packet may include a fixed header, an expansion header, and/or a payload.
  • the fixed header is a header with a fixed size and the expansion header is a header, the size of which can be changed according to configuration of the packet of the higher layer.
  • the payload is a region in which data of the higher layer is transmitted.
  • a header (the fixed header or the expansion header) of a packet may include a field indicating a type of the payload of the packet.
  • first 3 bits (packet type) of 1 byte may include data for identification of a packet type of the higher layer, and the remaining 5 bits may be used as an indicator part.
  • the indicator part may include data for identification of a configuring method of a payload and/or configuration information of the expansion header and may be changed according to a packet type.
  • a table shown in the diagram represents a type of a higher layer included in a payload according to a value of a packet type.
  • an IP packet and/or an RoHC packet of the payload may be transmitted through a DP, and a signaling packet may be transmitted through a base DP. Accordingly, when a plurality of packets are mixed and transmitted, packet type values may also be applied so as to differentiate a data packet and a signaling packet.
  • IP packet of IPv4 is included in a payload.
  • IP packet of IPv6 is included in a payload.
  • a compressed IP packet is included in a payload.
  • the compressed IP packet may include an IP packet to which header compression is applied.
  • a packet including signaling data is included in a payload.
  • a packet type value is 111
  • a framed packet type is included in a payload.
  • FIG. 16 is a diagram illustrating a detailed processing operation of a signal and/or data in each protocol stack of a transmitter when a logical data path of a physical layer includes a dedicated channel, a base DP, and a normal data DP, according to another embodiment of the present invention.
  • one or more broadcasters may provide broadcast services.
  • a broadcaster transmits multiple broadcast services and one broadcast service may include one or more components.
  • a user may receive content in units of broadcast services.
  • a session-based transmission protocol may be used to support IP hybrid broadcast and the contents of signaling delivered to each signaling path may be determined according to the structure of the corresponding transmission protocol.
  • data related to the FIC and/or the EAC may be transmitted/received over the dedicated channel.
  • a base DP and a normal DP may be used to distinguish therebetween.
  • Configuration information of the FIC and/or EAC may be included in physical layer signaling (or a transmission parameter).
  • a link layer may format signaling according to characteristics of a corresponding channel. Transmission of data to a specific channel of a physical layer may be performed from a logical point of view and actual operation may be performed according to characteristics of a physical layer.
  • the FIC may include information about services of each broadcaster, transmitted in a corresponding frequency and information about paths for receiving the services.
  • the FIC may include information for service acquisition and may be referred to as service acquisition information.
  • the FIC and/or the EAC may be included in link layer signaling.
  • Link layer signaling may include the following information.
  • System Parameter - A parameter related to a transmitter or a parameter related to a broadcaster that provides a service in a corresponding channel.
  • Link layer - Context information associated with IP header compression and an ID of a DP to which a corresponding context is applied.
  • IP address and UDP port number service and component information, emergency alert information, and a mapping relationship between an IP address, a UDP port number, a session ID, and a DP of a packet stream and signaling transmitted in an IP layer.
  • one or more broadcast services are transmitted in one frequency band, the receiver does not need to decode all DPs and it is efficient to pre-check signaling information and to decode only a DP related to a necessary service.
  • the broadcast system may provide and acquire information for mapping a DP and a service, using the FIC and/or the base DP.
  • One or more broadcasters may process component signaling and/or data for one or more broadcast services so as to be transmitted through one or more sessions.
  • One broadcast service may be transmitted through one or more sessions.
  • the broadcast service may include one or more components included in the broadcast service and/or signaling information for the broadcast service.
  • Component signaling may include information used to acquire components included in the broadcast service in a receiver.
  • Service signaling, component signaling, and/or data for one or more broadcast services may be transmitted to a link layer through processing in an IP layer.
  • the transmitter performs overhead reduction when overhead reduction for an IP packet is needed and generates related information as link layer signaling.
  • Link layer signaling may include a system parameter specifying the broadcast system, in addition to the above-described information.
  • the transmitter may process an IP packet in a link layer processing procedure and transmit the processed IP packet to a physical layer in the form of one or more DPs.
  • the transmitter may transmit link layer signaling to the receiver in the form or configuration of an FIC and/or an EAC. Meanwhile, the transmitter may also transmit link layer signaling to the base DP through an encapsulation procedure of the link layer.
  • FIG. 17 is a diagram illustrating a detailed processing operation of a signal and/or data in each protocol stack of a receiver when a logical data path of a physical layer includes a dedicated channel, a base DP, and a normal data DP, according to another embodiment of the present invention.
  • a receiver tunes to a corresponding frequency.
  • the receiver reads information stored in a DB etc. in association with a corresponding channel.
  • the information stored in the DB etc. of the receiver may be information included upon acquiring an FIC and/or an EAC during initial channel scan. Alternatively, the receiver may extract transmitted information as described above in this specification.
  • the receiver may receive the FIC and/or the EAC, receive information about a channel that the receiver desires to access, and then update information pre-stored in the DB.
  • the receiver may acquire components for a service selected by a user and information about a mapping relationship of a DP transmitted by each component or acquire a base DP and/or a normal DP through which signaling necessary to obtain such information is transmitted. Meanwhile, when it is judged that there is no change in corresponding information using version information of the FIC or information identifying whether to require additional update of a dedicated channel, the receiver may omit a procedure of decoding or parsing the received FIC and/or EAC.
  • the receiver may acquire a link layer signaling packet including link layer signaling information by decoding a base DP and/or a DP through which signaling information is transmitted, based on information transmitted through the FIC.
  • the receiver may use, when necessary, the received link layer signaling information by a combination with signaling information (e.g., receiver information in the drawing) received through the dedicated channel.
  • the receiver may acquire information about a DP for receiving a service selected by the user among multiple DPs that are being transmitted over a current channel and overhead reduction information about a packet stream of the corresponding DP, using the FIC and/or the link layer signaling information.
  • the receiver may acquire signaling information stored in the DB and/or the shared memory as described above and then acquire information about a DP to be decoded, indicated by the corresponding signaling information.
  • the receiver may temporarily store the normal data transmitted through the DP in a device such as a buffer while the signaling information is decoded and/or parsed.
  • the receiver may acquire the base DP and/or the DP through which the signaling information is transmitted, acquire overhead reduction information about a DP to be received, perform decapsulation and/or header recovery for a packet stream received in a normal DP, using the acquired overhead information, process the packet stream in the form of an IP packet stream, and transmit the IP packet stream to a higher layer of the receiver.
  • FIG. 18 is a diagram illustrating a syntax of an FIC according to another embodiment of the present invention.
  • Information included in the FIC described in this drawing may be selectively combined with other information included in the FIC and may configure the FIC.
  • the receiver may rapidly acquire information about a channel, using the information included in the FIC.
  • the receiver may acquire bootstrap related information using the information included in the FIC.
  • the FIC may include information for fast channel scan and/or fast service acquisition.
  • the FIC may be referred to by other names, for example, a service list table or service acquisition information.
  • the FIC may be transmitted by being included in an IP packet in an IP layer according to a broadcast system. In this case, an IP address and/or a UDP port number, transmitting the FIC, may be fixed to specific values and the receiver may recognize that the IP packet transmitted with the corresponding IP address and/or UDP port number includes the FIC, without an additional processing procedure.
  • the FIC may include FIC_protocol_version information, transport_stream_id information, num_partitions information, partition_id information, partition_protocol_version information, num_services information, service_id information, service_data_version_information, service_channel_number information, service_category information, service_status information, service_distribution information, sp_indicator information, IP_version_flag information, SSC_source_IP_address_flag information, SSC_source_IP_address information, SSC_destination_IP_address information, SSC_destination_UDP_port information, SSC_TSI information, SSC_DP_ID information, num_partition_level_descriptors information, partition_level_descriptor() information, num_FIC_level_descriptors information, and/or FIC_level_descriptor() information.
  • FIC_protocol_version information represents a version of a protocol of an FIC.
  • transport_stream_id information identifies a broadcast stream.
  • transport_stream_id information may be used as information for identifying a broadcaster.
  • num_partitions information represents the number of partitions in a broadcast stream.
  • the broadcast stream may be transmitted after being divided into one or more partitions.
  • Each partition may include one or more DPs.
  • the DPs included in each partition may be used by one broadcaster.
  • the partition may be defined as a data transmission unit allocated to each broadcaster.
  • partition_id information identifies a partition.
  • partition_id information may identify a broadcaster.
  • partition_protocol_version information represents a version of a protocol of a partition.
  • num_services information represents the number of services included in a partition.
  • a service may include one or more components.
  • service_id information identifies a service.
  • service_data_version information represents change when a signaling table (signaling information) for a service is changed or a service entry for a service signaled by an FIC is changed.
  • service_data_version information may increment a value thereof whenever such change is present.
  • service_channel_number information represents a channel number of a service.
  • service_category information represents a category of a service.
  • the category of a service includes A/V content, audio content, an electronic service guide (ESG), and/or content on demand (CoD).
  • service_status information represents a state of a service.
  • a state of a service may include an active or suspended state and a hidden or shown state.
  • the state of a service may include an inactive state. In the inactive state, broadcast content is not currently provided but may be provided later. Accordingly, when a viewer scans a channel in a receiver, the receiver may not show a scan result for a corresponding service to the viewer.
  • service_distribution information represents a distribution state of data for a service.
  • service_distribution information may represent that entire data of a service is included in one partition, partial data of a service is not included in a current partition but content is presentable only by data in this partition, another partition is needed to present content, or another broadcast stream is needed to present content.
  • sp_indicator information identifies whether service protection has been applied. sp_indicator information may identify, for example, for meaningful presentation, whether one or more necessary components are protected (e.g., a state in which a component is encrypted).
  • IP_version_flag information identifies whether an IP address indicated by SSC_source_IP_address information and/or SSC_destination_IP_address information is an IPv4 address or an IPv6 address.
  • SSC_source_IP_address_flag information identifies whether SSC_source_IP_address information is present.
  • SSC_source_IP_address information represents a source IP address of an IP datagram that transmits signaling information for a service.
  • the signaling information for a service may be referred to as service layer signaling.
  • Service layer signaling includes information specifying a broadcast service.
  • service layer signaling may include information identifying a data unit (a session, a DP, or a packet) that transmits components constituting a broadcast service.
  • SSC_destination_IP_address information represents a destination IP address of an IP datagram (or channel) that transmits signaling information for a service.
  • SSC_destination_UDP_port information represents a destination UDP port number for a UDP/IP stream that transmits signaling information for a service.
  • SSC_TSI information represents a transport session identifier (TSI) of an LCT channel (or session) that transmits signaling information (or a signaling table) for a service.
  • TSI transport session identifier
  • SSC_DP_ID information represents an ID for identifying a DP including signaling information (or a signaling table) for a service. As a DP including the signaling information, the most robust DP in a broadcast transmission process may be allocated.
  • num_partition_level_descriptors information identifies the number of descriptors of a partition level for a partition.
  • partition_level_descriptor() information includes zero or more descriptors that provide additional information for a partition.
  • num_FIC_level_descriptors information represents the number of descriptors of an FIC level for an FIC.
  • FIC_level_descriptor() information includes zero or more descriptors that provide additional information for an FIC.
  • FIG. 19 is a diagram illustrating signaling_Information_Part() according to an embodiment of the present invention.
  • a broadcast system may add additional information to an extended header part in the case of a packet for transmitting signaling information in a structure of a packet transmitted through the above-described DP.
  • additional information will be referred to as Signaling_Information_Part().
  • Signaling_Information_Part() may include information used to determine a processing module (or processor) for received signaling information.
  • the broadcast system may adjust the number of fields indicating information and the number of bits allocated to each field, in a byte allocated to Signaling_Information_Part().
  • a receiver may use information included in Signaling_Information_Part() to determine whether corresponding signaling information is processed and determine to which signaling processing module signaling information should be transmitted.
  • Signaling_Information_Part() may include Signaling_Class information, Information Type information, and/or signaling format information.
  • Signaling_Class information may represent a class of transmitted signaling information.
  • Signaling information may correspond to an FIC, an EAC, link layer signaling information, service signaling information, and/or higher layer signaling information. Mapping for a class of signaling information indicated by each value of configuration of the number of bits of a field of Signaling_Class information may be determined according to system design.
  • Information_Type information may be used to indicate details of signaling information identified by signaling class information. Meaning of a value indicated by Information Type information may be additionally defined according to class of signaling information indicated by Signaling_Class information.
  • Signaling format information represents a form (or format) of signaling information configured in a payload.
  • the signaling format information may identify formats of different types of signaling information illustrated in the drawing and identify a format of additionally designated signaling information.
  • Signaling_Information_Part() of (a) and (b) illustrated in the drawing is one embodiment and the number of bits allocated to each field thereof may be adjusted according to characteristics of the broadcast system.
  • Signaling_Information_Part() as in (a) of the drawing may include signaling class information and/or signaling format information.
  • Signaling_Information_Part() may be used when a type of signaling information need not be designated or an information type can be judged in signaling information.
  • only one signaling format is used or when an additional protocol for signaling is present so that signaling formats are always equal, only a 4-bit signaling class field may be used without configuring a signaling field and the other fields may be reserved for later use or an 8-bit signaling class maybe configured to support various types of signaling.
  • Signaling_Information_Part() as in (b) of the drawing may further include information type information for indicating a type or characteristic of more detailed information in a signaling class when the signaling class is designated and may also include signaling format information.
  • Signaling class information and information type information may be used to determine decapsulation of signaling information or a processing procedure of corresponding signaling.
  • a detailed structure or processing of link layer signaling may refer to the above description and a description which will be given below.
  • FIG. 20 is a diagram illustrating a procedure for controlling an operation mode of a transmitter and/or a receiver in a link layer according to an embodiment of the present invention.
  • the method of controlling the link layer mode proposed according to the present invention can dynamically convert a mode of a link layer in order to efficiently manage a system bandwidth and processing time.
  • the method of controlling the link layer mode according to the present invention may easily cope with the case in which a specific mode needs to be supported due to change in a physical layer or on the other hand, the specific mode does not have to be changed any more.
  • the method of controlling the link layer mode according to the present invention may also allow a broadcast system to easily satisfy requirements of a corresponding broadcaster when a broadcaster providing a broadcast service intends to designate a method of transmitting a corresponding service.
  • the method of controlling the mode of the link layer may be configured to be performed only in a link layer or to be performed via change in data configuration in the link layer. In this case, it is possible to perform an independent operation of each layer in a network layer and/or a physical layer without embodiment of a separate function.
  • the mode of the link layer proposed according to the present invention it is possible to control the mode with signaling or parameters in a system without changing a system in order to satisfy configuration of a physical layer.
  • a specific mode may be performed only when processing of corresponding input is supported in a physical layer.
  • the diagram is a flowchart illustrating processing of signal and/or data in an IP layer, a link layer, and a physical layer by a transmitter and/or a receiver.
  • a function block (which may be embodied as hardware and/or software) for mode control may be added to the link layer and may manage parameter and/or signaling information for determination of whether a packet is processed.
  • the link layer may determine whether a corresponding function is performed during processing of a packet stream using information of a mode control functional block.
  • the transmitter determines whether overhead reduction (j16020) is performed using a mode control parameter (j16005).
  • the mode control parameter may be generated by a service provider in the transmitter. The mode control parameter will be described below in detail.
  • link layer signaling (j16060) information When the overhead reduction (j16020) is performed, information about overhead reduction is generated and is added to link layer signaling (j16060) information.
  • the link layer signaling (j16060) information may include all or some of mode control parameters.
  • the link layer signaling (j16060) information may be transmitted in the form of link layer signaling packet.
  • the link layer signaling packet may be mapped to a DP and transmitted to the receiver, but may not be mapped to the DP and may be transmitted to the receiver in the form of link layer signaling packet through a predetermined region of a broadcast signal.
  • a packet stream on which the overhead reduction (j16020) is performed is encapsulated (j16030) and input to a DP of a physical layer (j16040).
  • a packet stream on which the overhead reduction (j16020) is performed is encapsulated (j16030) and input to a DP of a physical layer (j16040).
  • whether encapsulation is performed is re-determined (j 16050).
  • a packet stream on which the encapsulation (j16030) is performed is input to a DP (j16040) of a physical layer.
  • the physical layer performs an operation for processing a general packet (a link layer packet).
  • an IP packet is transmitted directly to a physical layer.
  • the physical layer performs an operation for processing the IP packet.
  • a parameter may be applied to perform the operation only when the physical layer support IP packet input. That is, a value of a mode control parameter may be configured to be adjusted such that a process of transmitting an IP packet directly to a physical layer is not performed when the physical layer does not support processing of an IP packet.
  • the transmitter transmits a broadcast signal on which this process is performed, to the receiver.
  • the receiver may check a mode in which a packet is generated, using a header and/or signaling information of the packet stream (j16120).
  • decapsulation (j16130) and overhead reduction (j16140) processes are performed through a receiving operating process of a link layer and then an IP packet is transmitted to a higher layer.
  • the overhead reduction (j 16140) process may include an overhead recovery process.
  • FIG. 21 is a diagram illustrating an operation in a link layer according to a value of a flag and a type of a packet transmitted to a physical layer according to an embodiment of the present invention.
  • the aforementioned signaling method may be used. Signaling information associated with the method may be transmitted directly to a receiver.
  • the aforementioned signaling data or link layer signaling packet may include mode control that will be described below and related information.
  • an operation mode of the link layer may be indirectly indicated to the receiver.
  • the following two flags may be configured with regard to control of an operation mode.
  • a value mapped to each flag may be applied according to system configuration as long as the value represents Enable and Disable, and a bit number allocated to each flag can be changed.
  • an enable value may be mapped to 1 and a disable value may be mapped to 0.
  • the diagram shows whether header compression and encapsulation included in a link layer are performed according to values of HCF and EF and in this case, a packet format transmitted to a physical layer. That is, according to an embodiment of the present invention, the receiver can know a type of a packet input to the physical layer as information about the HCF and the EF.
  • FIG. 22 is a diagram a descriptor for signaling a mode control parameter according to an embodiment of the present invention.
  • Flags as information about mode control in a link layer may be signaling information, generated by the transmitter in the form of descriptor, and transmitted to the receiver. Signaling including a flag as information about mode control may be used to control an operation mode in a transmitter of a headend terminal, and whether a flag as information about mode control is included in signaling transmitted to the receiver may be optionally selected.
  • the receiver may directly select an operation mode about a corresponding DP and perform a packet decapsulation operation.
  • the receiver can determine a mode in which the signaling is transmitted, using physical layer signaling or field information of a packet header, which is transmitted to the receiver.
  • the link layer mode control description may include DP_id information, HCF information, and/or EF information.
  • the link layer mode control description may be included in a transmission parameter in the aforementioned FIC, link layer signaling packet, signaling via a dedicated channel, PSI/SI, and/or physical layer.
  • the DP_id information identifies a DP to which a mode in a link layer is applied.
  • the HCF information identifies whether header compression is applied in the DP identified by the DP_id information.
  • the EF information identifies whether encapsulation is performed on the DP identified by the DP_id information.
  • FIG. 23 is a diagram illustrating an operation of a transmitter for controlling a operation mode according to an embodiment of the present invention.
  • a transmitter may perform processing in a higher layer (e.g., an IP layer).
  • the transmitter may generate an IP packet including broadcast data for a broadcast service.
  • the transmitter parses or generates a system parameter (JS19010).
  • the system parameter may correspond to the aforementioned signaling data and signaling information.
  • the transmitter may receive or set mode control related parameter or signaling information during a broadcast data processing process in a link layer and sets a flag value associated with operation mode control (JS19020).
  • the transmitter may perform this operation after the header compression operation or the encapsulation operation. That is, the transmitter may perform the header compression or encapsulation operation and generate information associated with this operation.
  • the transmitter acquires a packet of a higher layer that needs to be transmitted through a broadcast signal (JS19030).
  • the packet of the higher layer may correspond to an IP packet.
  • the transmitter checks HCF in order to determine whether header compression is applied to the packet of the higher layer (JS 19040).
  • the transmitter applies the header compression to the packet of the higher layer (JS19050). After header compression is performed, the transmitter may generate the HCF. The HCF may be used to signal whether header compression is applied, to the receiver.
  • the transmitter performs encapsulation on the packet of the higher layer to which header compression is applied to generate a link layer packet (JS 19060). After the encapsulation process is performed, the transmitter may generate an EF. The EF may be used to signal whether encapsulation is applied to the higher layer packet, to the receiver.
  • the transmitter transmits the link layer packet to a physical layer processor (JS 19070). Then the physical layer processor generates a broadcast signal including the link layer packet and transmits the broadcast signal to the receiver.
  • a physical layer processor JS 19070
  • the transmitter checks the EF in order to determine whether encapsulation is applied (JS 19080).
  • the transmitter When the EF is enabled, the transmitter performs encapsulation on the higher layer packet (JS 19090). When the EF is disabled, the transmitter does not perform separate processing on the corresponding packet stream.
  • the transmitter transmits the packet stream (link layer packet) on which processing is completed in the link layer, to a physical layer (JS 19070). Header compression, encapsulation, and/or generation of link layer may be performed by a link layer packet generator (i.e. link layer processor) in the transmitter.
  • the transmitter may generate service signaling channel (SCC) data.
  • the service signaling channel data may be generated by a service signaling data encoder.
  • the service signaling data encoder may be included in a link layer processor and may present separately from the link layer processor.
  • the service signaling channel data may include the aforementioned FIC and/or EAT.
  • the service signaling channel data may be transmitted to the aforementioned dedicated channel.
  • FIG. 24 is a diagram illustrating an operation of a receiver for processing a broadcast signal according to an operation mode according to an embodiment of the present invention.
  • a receiver may receive information associated with an operation mode in a link layer together with a packet stream.
  • the receiver receives signaling information and/or channel information (JS20010).
  • JS20010 signaling information and/or channel information
  • the receiver selects a DP for receiving and processing according to the signaling information and/or the channel information (JS20020).
  • the receiver performs decoding of a physical layer on the selected DP and receives a packet stream of a link layer (JS20030).
  • the receiver checks whether link layer mode control related signaling is included in the received signaling (JS20040).
  • the receiver When the receiver receives the link layer mode related information, the receiver checks an EF (JS20050).
  • the receiver When the EF is enabled, the receiver performs a decapsulation process on a link layer packet (JS20060).
  • the receiver checks an HCF after decapsulation of the packet, and performs a header decompression process when the HCF is enabled (JS20080).
  • the receiver transmits the packet on which header decompression is performed, to a higher layer (e.g., an IP layer) (JS20090).
  • a higher layer e.g., an IP layer
  • JS20090 a higher layer
  • the receiver recognizes the processed packet stream as an IP packet and transmits the corresponding packet to the IP layer.
  • the receiver When the receiver does not receive link layer mode related information or a corresponding system does not transmit the link layer mode related information to the receiver, the following operation is performed.
  • the receiver receives signaling information and/or channel information (JS20010) and selects a DP for reception and processing according to corresponding information (JS20020).
  • the receiver performs decoding of the physical layer on the selected DP to acquire a packet stream (JS20030).
  • the receiver checks whether the received signaling includes link layer mode control related signaling (JS20040).
  • the receiver Since the receiver does not receive link layer mode related signaling, the receiver checks a format of the packet transmitted using physical layer signaling, etc. (JS20100).
  • the physical layer signaling information may include information for identification of a type of the packet included in a payload of the DP.
  • the receiver transmits the packet to the IP layer without a separate process in a link layer.
  • the receiver When a packet transmitted from a physical layer is a packet on which encapsulation is performed, the receiver performs a decapsulation process on the corresponding packet (JS20110).
  • the receiver checks the form of a packet included in a payload using information such as a header, etc. of the link layer packet during the decapsulation process (JS20120), and the receiver transmits the corresponding packet to the IP layer processor when the payload is an IP packet.
  • the receiver When the payload of the link layer packet is a compressed IP, the receiver performs a decompression process on the corresponding packet (JS20130).
  • the receiver transmits the IP packet to an IP layer processor (JS20140).
  • JS20140 IP layer processor
  • FIG. 25 is a diagram illustrating information for identifying an encapsulation mode according to an embodiment of the present invention.
  • a procedure for determining as which mode processing in the link layer operates may be needed.
  • the transmitter and/or the receiver may confirm configuration information of the link layer. This case may correspond to the case in which the receiver is initially set up or performs a scan procedure for a service or a mobile receiver newly enters an area within a transmission radius of the transmitter.
  • This procedure may be referred to as an initialization procedure or a bootstrapping procedure.
  • This procedure may be configured as a partial process of a procedure supported by the system without being configured by an additional procedure. In this specification, this procedure will be referred to as an initialization procedure.
  • Parameters needed in the initialization procedure may be determined according to functions supported by a corresponding link layer and types of operating modes possessed by each function. A description will be given hereinafter of the parameters capable of determining functions constituting the link layer and operation modes according to the functions.
  • indexes are assigned to respective encapsulation modes and a proper field value may be allocated to each index.
  • the drawing illustrates an embodiment of a field value mapped to each encapsulation mode. While it is assumed that a 2-bit field value is assigned in this embodiment, the field value may be expanded within a range permitted by the system in actual implementation, when more supportable encapsulation modes are present.
  • the corresponding information may represent that encapsulation in a link layer is bypasses and not performed. If a field of information indicating an encapsulation mode is set to '01', the corresponding information may represent that data is processed by a first encapsulation scheme in the link layer. If a field of information indicating an encapsulation mode is set to '10', the corresponding information may represent that data is processed by a second encapsulation scheme in the link layer. If a field of information indicating an encapsulation mode is set to '11', the corresponding information may represent that data is processed by a third encapsulation scheme in the link layer.
  • FIG. 26 is a diagram illustrating information for identifying a header compression mode according to an embodiment of the present invention.
  • Processing in a link layer may include a function of header compression of an IP packet. If a few IP header compression schemes are capable of being supported in the link layer, a transmitter may determine which scheme the transmitter is to use.
  • Determination of a header compression mode generally accompanies an encapsulation function. Therefore, when the encapsulation mode is disabled, the header compression mode may also be disabled.
  • the above-described drawing illustrates an embodiment of a field value mapped to each header compression mode. While it is assumed that a 3-bit field value is assigned in this embodiment, the field value may be expanded or shortened within a range permitted by the system in actual implementation according to a supportable header compression mode.
  • the corresponding information may indicate that header compression processing for data is not performed in a link layer. If a field of information indicating the header compression mode is set to '001', the corresponding information may indicate that header compression processing for data in the link layer uses an RoHC scheme. If a field of information indicating the header compression mode is set to '010', the corresponding information may indicate that header compression processing for data in the link layer uses a second RoHC scheme. If a field of information indicating the header compression mode is set to '011', the corresponding information may indicate that header compression processing for data in the link layer uses a third RoHC scheme. If a field of information indicating the header compression mode is set to '100' to '111', the corresponding information may indicate that header compressing for data is reserved as a region for identifying a new header compression processing scheme for data in the link layer.
  • FIG. 27 is a diagram illustrating information for identifying a packet reconfiguration mode according to an embodiment of the present invention.
  • the broadcast system transmitter and/or receiver
  • the broadcast system may transmit/receive a packet stream after a header compression procedure in an out-of-band form through reconfiguration of partial compressed packets and/or extraction of context information.
  • a mode for reconfiguring a packet or performing processing such as addition of information capable of identifying the structure of the packet may be referred to as a packet reconfiguration mode.
  • the packet reconfiguration mode may use a few schemes and the broadcast system may designate a corresponding scheme in an initialization procedure of a link layer.
  • the above-described drawing illustrates an embodiment of an index and a field value mapped to the packet reconfiguration mode. While it is assumed that a 2-bit field value is assigned in this embodiment, the field value may be expanded or shortened within a range permitted by the system in actual implementation according to a supportable packet reconfiguration mode.
  • corresponding information may represent that reconfiguration for a packet transmitting data is not performed in a link layer. If a field of information indicating the packet reconfiguration mode is set to '01', corresponding information may represent that a first reconfiguration scheme is performed for a packet transmitting data in the link layer. If a field of information indicating the packet reconfiguration mode is set to '10', corresponding information may represent that a second reconfiguration scheme is performed for a packet transmitting data in the link layer. If a field of information indicating the packet reconfiguration mode is set to '11', corresponding information may represent that a third reconfiguration scheme is performed for a packet transmitting data in the link layer.
  • FIG. 28 is a diagram illustrating a context transmission mode according to an embodiment of the present invention.
  • a transmission scheme of the above-described context information may include one or more transmission modes. That is, the broadcast system may transmit the context information in many ways.
  • a context transmission mode may be determined according to the system and/or a transmission path of a logical physical layer and information for identifying the context transmission scheme may be signaled.
  • the above-described drawing illustrates an embodiment of an index and a field value mapped to the context transmission mode. While it is assumed that a 3-bit field value is assigned in this embodiment, the field value may be expanded or shortened within a range permitted by the system in actual implementation according to a supportable context transmission mode.
  • corresponding field information may represent that context information is transmitted as a first transmission mode. If a field of information indicating the context transmission mode is set to '001', corresponding information may represent that context information is transmitted as a second transmission mode. If a field of information indicating the context transmission mode is set to '010', corresponding information may represent that context information is transmitted as a third transmission mode. If a field of information indicating the context transmission mode is set to '011', corresponding information may represent that context information is transmitted as a fourth transmission mode.
  • corresponding information may represent that context information is transmitted as a fifth transmission mode. If a field of information indicating a context transmission mode is set to '101' to '111', corresponding information may represent that context information is reserved to identify a new transmission mode.
  • FIG. 29 is a diagram illustrating initialization information when RoHC is applied by a header compression scheme according to an embodiment of the present invention.
  • Initialization information suitable for a corresponding compression scheme according to a header compression mode may be needed.
  • an initialization parameter for the case in which a header compression mode is set to RoHC is described.
  • Initialization information for RoHC may be used to transmit information about configuration of an RoHC channel which is a link between a compressor and a decompressor.
  • One RoHC channel may include one or more context information and information commonly applied to all contexts in the RoHC channel may be transmitted/received by being included in the initialization information.
  • a path through which related information is transmitted by applying RoHC may be referred to as an RoHC channel and, generally, the RoHC channel may be mapped to a link.
  • the RoHC channel may be generally transmitted through one DP and, in this case, the RoHC channel may be expressed using information related to the DP.
  • the initialization information may include link_id information, max_cid information, large_cids information, num_profiles information, profiles() information, num_IP_stream information, and/or IP_address() information.
  • link_id information represents an ID of a link (RoHC channel) to which corresponding information is applied.
  • link_id information may be replaced with DP_id.
  • max_cid information represents a maximum value of a CID.
  • max_cid information may be used to inform a decompressor of the maximum value of the CID.
  • large_cids information has a Boolean value and identifies whether a short CID (0 to 15) is used or an embedded CID (0 to 16383) is used in configuring a CID. Therefore, a byte size expressing the CID may also be determined.
  • num_profiles information represents the number of profiles supported in an identified RoHC channel.
  • profiels() information represents a range of a protocol header-compressed in RoHC. Since a compressor and a decompressor should have the same profile in RoHC to compress and recover a stream, a receiver may acquire a parameter of RoHC used in a transmitter from profiles() information.
  • num_IP_stream information represents the number of IP streams transmitted through a channel (e.g., an RoHC channel).
  • IP_address information represents an address of an IP stream.
  • IP_address information may represent a destination address of a filtered IP stream which is input to an RoHC compressor (transmitter).
  • FIG. 30 is a diagram illustrating information for identifying link layer signaling path configuration according to an embodiment of the present invention.
  • a path through which signaling information is delivered is designed not to be changed.
  • information about configuration of a physical layer in which link layer signaling information rather than an IP packet is transmitted needs to be signaled.
  • link layer signaling path information should be transmitted may occur.
  • the above-described drawing illustrates information for identifying a signaling path which is a path through which the link layer signaling information is transmitted/received. Indexes may be expanded or shortened with respect to the link layer signaling information according to a signaling transmission path configured in a physical layer. Separately from configuration in a link layer, operation of a corresponding channel may conform to a procedure of the physical layer.
  • the above-described drawing illustrates an embodiment in which information about signaling path configuration is allocated to a field value.
  • indexes may be mapped to signaling paths having great importance in order of small values. Signaling paths having priority prioritized according to an index value may also be identified.
  • the broadcast system may use all signaling paths having higher priority than signaling paths indicated by the information about signaling path configuration. For example, when a signaling path configuration index value is 3, a corresponding field value may be '011' indicating that all of a dedicated data path, a specific signaling channel (FIC), and a specific signaling channel (EAC), priorities of which are 1, 2, and 3, are being used.
  • a signaling path configuration index value is 3
  • a corresponding field value may be '011' indicating that all of a dedicated data path, a specific signaling channel (FIC), and a specific signaling channel (EAC), priorities of which are 1, 2, and 3, are being used.
  • Signaling of the above scheme can reduce the amount of data that transmits signaling information.
  • FIG. 31 is a diagram illustrating information about signaling path configuration by a bit mapping scheme according to an embodiment of the present invention.
  • the above-described information about signaling path configuration may be transmitted/received through definition of a bit mapping scheme.
  • allocation of 4 bits to the information about signaling path configuration is considered and signaling paths corresponding to respective bits b1, b2, b3, and b4 may be mapped. If a bit value of each position is 0, this may indicate that a corresponding path is disabled and, if a bit value of each position is 1, this may indicate that a corresponding path is enabled.
  • a 4-bit signaling path configuration field value is '1100', this may indicate that the broadcast system is using a dedicated DP and a specific signaling channel (FIC) in a link layer.
  • FIC specific signaling channel
  • FIG. 32 is a flowchart illustrating a link layer initialization procedure according to an embodiment of the present invention.
  • the receiver may perform an initialization procedure for all or some system configurations.
  • an initialization procedure for a link layer may also be performed.
  • Initial setup of the link layer in the receiver, using the above-described initialization parameters may be performed as illustrated in the drawing.
  • the receiver enters an initialization procedure of a link layer (JS32010).
  • the receiver Upon entering the initialization procedure of the link layer, the receiver selects an encapsulation mode (JS32020). The receiver may select the encapsulation mode using the above-described initialization parameters in this procedure.
  • the receiver determines whether encapsulation is enabled (JS32030).
  • the receiver may determine whether encapsulation is enabled using the above-described initialization parameters in this procedure.
  • the receiver may determine that a header compression mode is disabled (JS32080). In this case, since it is not necessary for the receiver to proceed to the initialization procedure any more, the receiver may immediately transmit data to another layer or transition to a data processing procedure.
  • the receiver selects a header compression mode (JS32040) when the encapsulation mode is enabled. Upon selecting the header compression mode, the receiver may determine a header compression scheme applied to a packet, using the above-described initialization parameter.
  • JS32040 header compression mode
  • the receiver may determine a header compression scheme applied to a packet, using the above-described initialization parameter.
  • the receiver determines whether header compression is enabled (JS32050). If header compression is disabled, the receiver may immediately transmit data or transition to a data processing procedure.
  • the receiver selects a packet stream reconfiguration mode and/or a context transmission mode (JS32060 and JS32070) with respect to a corresponding header compression scheme.
  • the receiver may select respective modes using the above-described information in this procedure.
  • the receiver may transmit data for another processing procedure or perform the data processing procedure.
  • FIG. 33 is a flowchart illustrating a link layer initialization procedure according to another embodiment of the present invention.
  • the receiver enters an initialization procedure of a link layer (JS33010).
  • the receiver identifies link layer signaling path configuration (JS33020).
  • the receiver may identify a path through which link layer signaling information is transmitted, using the above-described information.
  • the receiver selects an encapsulation mode (JS33030).
  • the receiver may select the encapsulation mode using the above-described initialization parameter.
  • the receiver determines whether encapsulation is enabled (JS33040).
  • the receiver may determine whether encapsulation is enabled, using the above-described initialization parameter in this procedure.
  • the receiver may determine that a header compression mode is disabled (JS34100). In this case, since it is not necessary for the receiver to proceed to the initialization procedure any more, the receiver may immediately transmit data to another layer or transition to a data processing procedure.
  • the receiver selects a header compression mode (JS33050) when the encapsulation mode is enabled. Upon selecting the header compression mode, the receiver may determine a header compression scheme applied to a packet, using the above-described initialization parameter.
  • JS33050 header compression mode
  • the receiver may determine a header compression scheme applied to a packet, using the above-described initialization parameter.
  • the receiver determines whether header compression is enabled (JS33060). If header compression is disabled, the receiver may immediately transmit data or transition to the data processing procedure.
  • the receiver selects a packet stream reconfiguration mode and/or a context transmission mode (JS33070 and JS32080) with respect to a corresponding header compression scheme.
  • the receiver may select respective modes using the above-described information in this procedure.
  • the receiver performs header compression initialization (JS33090).
  • the receiver may use the above-described information in a procedure of performing header compression initialization.
  • the receiver may transmit data for another processing procedure or perform the data processing procedure.
  • FIG. 34 is a diagram illustrating a signaling format for transmitting an initialization parameter according to an embodiment of the present invention.
  • the broadcast system may transmit/receive corresponding information in the form of a descriptor.
  • link_id information capable of identifying the respective links may be assigned and different parameters may be applied according to link_id information. For example, if a type of data transmitted to the link layer is an IP stream, when an IP address is not changed in the corresponding IP stream, configuration information may designate n IP address transmitted by a higher layer.
  • the link layer initialization descriptor for transmitting the initialization parameter may include descriptor_tag information, descriptor_length information, num_link information, link_id information, encapsulation_mode information, header_compression_mode information, packet_reconfiguration_mode information, context_transmission_mode information, max_cid information, large_cids information, num_profiles information, and/or profiles() information.
  • descriptor_tag information may include descriptor_tag information, descriptor_length information, num_link information, link_id information, encapsulation_mode information, header_compression_mode information, packet_reconfiguration_mode information, context_transmission_mode information, max_cid information, large_cids information, num_profiles information, and/or profiles() information.
  • FIG. 35 is a diagram illustrating a signaling format for transmitting an initialization parameter according to another embodiment of the present invention.
  • the drawing illustrates a descriptor of another form to actually transmit the above-described initialization parameter to a receiver.
  • the above-described initial configuration information of header compression is excluded.
  • the link layer initialization descriptor for transmitting the initialization parameter may include descriptor_tag information, descriptor_length information, num_link information, link_id information, encapsulation_mode information, header compression mode information, packet_reconfiguration_mode information, and/or context_transmission_mode information.
  • descriptor_tag information may include descriptor_tag information, descriptor_length information, num_link information, link_id information, encapsulation_mode information, header compression mode information, packet_reconfiguration_mode information, and/or context_transmission_mode information.
  • FIG. 36 is a diagram illustrating a signaling format for transmitting an initialization parameter according to another embodiment of the present invention.
  • a descriptor for transmitting the initialization parameter includes configuration information about a signaling transmission path without including initial configuration information of header compression.
  • the configuration parameter about the signaling transmission path may use a 4-bit mapping scheme as described above.
  • a link layer signaling transmission scheme or the contents of link layer signaling may differ.
  • the initialization parameter may be used even in the case of change of link layer signaling.
  • the link layer initialization descriptor for transmitting the initialization parameter may include descriptor_tag information, descriptor_length information, num_link information, signaling_path_configuration information, dedicated_DP_id information, link_id information, encapsulation_mode information, header_compression_mode information, packet_reconfiguration_mode information, and/or context_transmission_mode information.
  • dedicated_DP_id information is information identifying the corresponding DP.
  • DP_id may be designated to include DP_id information in the descriptor for transmitting the initialization parameter.
  • FIG. 37 is a diagram illustrating a receiver according to an embodiment of the present invention.
  • the receiver may include a tuner JS21010, an ADC JS21020, a demodulator JS21030, a channel synchronizer & equalizer JS21040, a channel decoder JS21050, an L1 signaling parser JS21060, a signaling controller JS21070, a baseband controller JS21080, a link layer interface JS21090, an L2 signaling parser JS21100, packet header recovery JS21110, an IP packet filter JS21120, a common protocol stack processor JS21130, an SSC processing buffer and parser JS21140, a service map database (DB) JS21150, a service guide (SG) processor JS21160, a SG DB JS21170, an AV service controller JS21180, a demultiplexer JS21190, a video decoder JS21200, a video renderer JS21210, an audio decoder JS21220, an audio render
  • the tuner JS21010 receives a broadcast signal.
  • the ADC JS21020 converts the broadcast signal to a digital signal.
  • the demodulator JS21030 demodulates the broadcast signal.
  • the channel synchronizer & equalizer JS21040 performs channel synchronization and/or equalization.
  • the channel decoder JS21050 decodes a channel in the broadcast signal.
  • the L1 signaling parser JS21060 parses L1 signaling information from the broadcast signal.
  • the L1 signaling information may correspond to physical layer signaling information.
  • the L1 signaling information may include a transmission parameter.
  • the signaling controller JS21070 processes the signaling information or the broadcast receiver transmits the signaling information to an apparatus that requires the corresponding signaling information.
  • the baseband controller JS21080 controls processing of the broadcast signal in a baseband.
  • the baseband controller JS21080 may perform processing in the physical layer on the broadcast signal using the L1 signaling information.
  • the baseband controller JS21080 may transmit the processed broadcast signal or broadcast data to another apparatus in the receiver.
  • the link layer interface JS21090 accesses the link layer packet and acquires the link layer packet.
  • the L2 signaling parser JS21100 parses L2 signaling information.
  • the L2 signaling information may correspond to information included in the aforementioned link layer signaling packet.
  • the packet header recovery JS21110 When header compression is applied to a packet of a higher layer (e.g., an IP packet) than a link layer, the packet header recovery JS21110 performs header decompression on the packet.
  • the packet header recovery JS21110 may restore a header of the packet of the higher layer using information for identification of whether the aforementioned header compression is applied.
  • the IP packet filter JS21120 filters the IP packet transmitted to a specific IP address and/or UDP number.
  • the IP packet transmitted to the specific IP address and/or UDP number may include signaling information transmitted through the aforementioned dedicated channel.
  • the IP packet transmitted to the specific IP address and/or UDP number may include the aforementioned FIC, FIT, EAT, and/or emergency alert message (EAM).
  • the common protocol stack processor JS21130 processes data according to a protocol of each layer. For example, the common protocol stack processor JS21130 decodes or parses the corresponding IP packet according to a protocol of an IP layer and/or a higher layer than the IP layer.
  • the SSC processing buffer and parser JS21140 stores or parses signaling information transmitted to a service signaling channel (SSC).
  • SSC service signaling channel
  • the specific IP packet may be designated as an SSC and the SSC may include information for acquisition of a service, attribute information included in the service, DVB-SI information, and/or PSI/PSIP information.
  • the service map DB JS21150 stores a service map table.
  • the service map table includes attribute information about a broadcast service.
  • the service map table may be included in the SSC and transmitted.
  • the SG processor JS21160 parses or decodes a service guide.
  • the SG DB JS21170 stores the service guide.
  • the AV service controller JS21180 performs overall control for acquisition of broadcast AV data.
  • the demultiplexer JS21190 divides broadcast data into video data and audio data.
  • the video decoder JS21200 decodes video data.
  • the video renderer JS21210 generates video provided to a user using the decoded video data.
  • the audio decoder JS21220 decodes audio data.
  • the audio renderer JS21230 generates audio provided to the user using the decoded audio data.
  • the network switch JS21240 controls an interface with other networks except for a broadcast network.
  • the network switch JS21240 may access an IP network and may directly receive an IP packet.
  • the IP packet filter JS21250 filters an IP packet having a specific IP address and/or a UDP number.
  • TCP/IP stack processor JS21260 decapsulates an IP packet according to a protocol of TCP/IP.
  • the data service controller JS21270 controls processing of a data service.
  • the system processor JS21280 performs overall control on the receiver.
  • FIG. 38 is a diagram illustrating a broadcast system according to an embodiment of the present invention.
  • the broadcast system may include a broadcast transmitter J38010 and/or a broadcast receiver J38110.
  • the broadcast transmitter J38010 includes an IP packet generator J38020, a link layer packet generator J38030, a broadcast signal generator J38040, and/or a signaling encoder J38050.
  • the IP packet generator J38020 generates and processes IP packets. For example, the IP packet generator J38020 generates first IP packets including broadcast data for a broadcast service and a second IP packet including service acquisition information including information necessary for fast acquisition of the broadcast service.
  • the link layer packet generator J38030 generates and processes link layer packets. For example, the link layer packet generator J38030 may generate first link layer packets including the first IP packets.
  • the IP packet generator and the link layer packet generator may be implemented through one device.
  • the broadcast signal generator J38040 generates a broadcast signal for transmitting broadcast data through a physical layer.
  • the broadcast signal generator J38040 generates the broadcast signal including the first link layer packets and the second IP packet.
  • the signaling encoder J38050 generates signaling information.
  • the signaling encoder J38050 may generate all or some of the signaling information.
  • the signaling encoder J38050 may transmit signaling information that is necessary to be transmitted through an IP layer to the IP packet generator and transmit signaling information that is necessary to be transmitted through a link layer to the link layer packet generator.
  • the broadcast receiver J38110 may include a receiving unit J38120, a link layer processing unit J38130, an IP layer processing unit J38140, a signaling processing unit J38150, and/or a processor J38160.
  • the receiving unit J38120 receives the broadcast signal.
  • the receiving unit J38120 may receive the broadcast signal including the first link layer packets and the second IP packet.
  • the second IP packet may include service acquisition information including information necessary to rapidly acquire a broadcast service.
  • the receiving unit J38120 may include a tuner and/or a network interface.
  • the network interface may receive a broadcast signal of each type according to a property of a broadcast network. For example, the network interface may receive a broadcast signal transmitted over an IP network.
  • the link layer processing unit J38130 processes data in a link layer.
  • the link layer processing unit J38130 may obtain the first IP packets including broadcast data for a broadcast service by decapsulating the first link layer packets.
  • the IP layer processing unit J38140 processes data in an IP layer.
  • the IP layer processing unit J38140 may acquire the broadcast data by decapsulating the first IP packets, using the service acquisition information.
  • the signaling processing unit J38150 parses signaling information.
  • the signaling processing unit J38150 may parse signaling information transmitted through a physical layer, a link layer, and/or an IP layer.
  • the signaling processing unit J38150 may acquire signaling information and transmit the signaling information to a device and/or a module of the receiver requiring this signaling information.
  • the signaling processing unit J38150 may acquire the service acquisition information by decapsulating the second IP packet.
  • the processor J38160 processes broadcast data.
  • the processor J38160 may decode audio and/or video from the broadcast data.
  • the processor J38160 may include the above-described link layer processing unit J38130, the IP layer processing unit J38140, and/or the signaling processing unit J38150.
  • the processor J38160 reproduces and processes broadcast content using the broadcast data.
  • Modules, processing units, devices, or units may be processors for performing consecutive execution procedures stored in a memory (or a storage unit). Steps described in the above-described embodiments may be performed by hardware/processors. The modules/blocks/units described in the above-described embodiments may operate as hardware/processors. In addition, methods proposed in the present invention may be executed by code. This code may be written in a processor-readable storage medium and, therefore, read by a processor provided by an apparatus.
  • the methods according to the present invention may be implemented as program instructions that can be executed by various computer means and written in a computer-readable recording medium.
  • the computer-readable recording medium may include a program instruction, a data file, a data structure, etc. alone or in combination.
  • the program instruction written in the medium may be designed or configured especially for the present invention or known to those skilled in computer software.
  • Examples of the computer-readable recording medium include magnetic media such as a hard disk, a floppy disk, and a magnetic tape, optical media such as a CD-ROM and a DVD, magneto-optical media such as a floptical disk, and a hardware device configured especially to store and execute a program instruction, such as a ROM, a RAM, and a flash memory.
  • Examples of the program instruction include a high-level language code executable by a computer using an interpreter as well as a machine language code generated by a compiler.
  • the hardware device may be configured to operate as one or more software modules to implement an operation of the present invention or vice versa.
  • the present invention is applicable to all broadcast industries.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Business, Economics & Management (AREA)
  • Emergency Management (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Claims (10)

  1. Rundfunksender zum Übertragen eines Rundfunksignals, wobei der Rundfunksender (J38010) aufweist:
    einen Internetprotokoll, IP-, Paketgenerator (J38020), der dafür konfiguriert ist, IP-Pakete zu erzeugen, die Rundfunkdaten für einen oder mehrere Rundfunkdienste enthalten;
    einen Verbindungsschichtpaketgenerator (J38030), der dafür konfiguriert ist, mindestens ein erstes Verbindungsschichtpaket mit den IP-Paketen zu erzeugen, mindestens ein zweites Verbindungsschichtpaket mit Verbindungsschichtsignalisierungsdaten zu erzeugen, und mindestens ein drittes Verbindungsschichtpaket zu erzeugen, das Dienstabrufinformation enthält, die Information zum schnellen Erhalten des einen oder der mehreren Rundfunkdienste enthält, wobei die Verbindungsschichtsignalisierungsdaten aufweisen:
    Header-Komprimierungsinformation, die ein Header-Komprimierungsschema identifiziert, das auf die IP-Pakete angewendet wird; und
    Abbildungsinformation zwischen IP-Adressen der IP-Pakete und Physical Layer Pipes, PLPs; und
    einen Rundfunksignalgenerator (J38040), der dafür konfiguriert ist, das Rundfunksignal zu erzeugen und das Rundfunksignal über eine physikalische Schicht zu übertragen, die derart konfiguriert ist, dass sie eine oder mehrere PLPs enthält, die auf das mindestens eine erste, zweite oder dritte Verbindungsschichtpaket abgebildet werden und den einen oder mehrere Rundfunkdienste transportieren.
  2. Rundfunksender nach Anspruch 1, wobei die Dienstabrufinformation Information enthält, die eine IP-Adresse eines Kanals für die Übertragung einer Dienstschichtsignalisierung identifiziert, die Information enthält, die den einen oder die mehreren Rundfunkdienste spezifiziert.
  3. Rundfunksender nach Anspruch 2, wobei die Dienstabrufinformation Information enthält, die eine PLP identifiziert, die die Dienstschichtsignalisierung enthält.
  4. Rundfunksender nach Anspruch 1, wobei die Header-Komprimierungsinformation eine PLP-Identifizierung, die eine PLP unter den PLPs identifiziert, und einen für die PLP zu verwendenden Maximalwert einer Kontextidentifizierung enthält.
  5. Rundfunksender nach Anspruch 1, wobei der Verbindungsschichtpaketgenerator (J38030) ferner dafür konfiguriert ist, mindestens ein Verbindungsschichtpaket zu erzeugen, das einen Signalisierungsinformationsteil aufweist, der zusätzliche Information enthält, die zum Identifizieren eines Verarbeitungsverfahrens der Verbindungsschichtsignalisierungsdaten verwendet wird, die in dem mindestens einen zweiten Verbindungsschichtpaket enthalten sind, und wobei der Signalisierungsinformationsteil Signalisierungsklasseninformation enthält, die identifiziert, ob die Verbindungsschichtsignalisierungsdaten, die über das mindestens eine zweite Verbindungsschichtpaket übertragen werden, der Dienstabrufinformation entsprechen.
  6. Rundfunkempfänger zum Empfangen eines Rundfunksignals, wobei der Rundfunkempfänger (J38110) aufweist:
    einen Empfänger (J38120), der dafür konfiguriert ist, das Rundfunksignal über eine physikalische Schicht zu empfangen, die dafür konfiguriert ist, eine oder mehrere Physical Layer Pipes, PLPs, zu enthalten, die Verbindungsschichtpaketen zugeordnet sind und einen oder mehrere Rundfunkdienste transportieren, wobei die Verbindungsschichtpakete mindestens ein erstes Verbindungsschichtpaket mit IP-Paketen, die Rundfunkdaten für den einen oder die mehreren Rundfunkdienste enthalten, mindestens ein zweites Verbindungsschichtpaket mit Verbindungsschichtsignalisierungsdaten und mindestens ein drittes Verbindungsschichtpaket mit Dienstabrufinformation enthalten, die Information zum schnellen Erhalten des einen oder der mehreren Rundfunkdienste enthält, wobei die Verbindungsschichtsignalisierungsdaten aufweisen:
    Header-Komprimierungsinformation, die ein Header-Komprimierungsschema identifiziert, das auf die IP-Pakete angewendet wird; und
    Abbildungsinformation zwischen IP-Adressen der IP-Pakete und den PLPs;
    eine Verbindungsschichtverarbeitungseinheit (J38130) zum Erhalten der IP-Pakete durch Entkapseln des mindestens einen ersten Verbindungsschichtpakets;
    eine Signalisierungsverarbeitungseinheit (J38150) zum Decodieren der Verbindungsschichtsignalisierungsdaten und zum Erhalten der Dienstabrufinformation;
    eine IP-Paketverarbeitungseinheit (J38140) zum Erhalten der Rundfunkdaten durch Entkapseln der IP-Pakete unter Verwendung der Dienstabrufinformation; und
    einen Prozessor (J38160) zum Wiedergeben und Verarbeiten von Rundfunkinhalt unter Verwendung der Rundfunkdaten.
  7. Rundfunkempfänger nach Anspruch 6, wobei die Dienstabrufinformation Information enthält, die eine IP-Adresse eines Kanals für die Übertragung einer Dienstschichtsignalisierung identifiziert, die Information enthält, die einen oder mehrere Rundfunkdienste spezifiziert.
  8. Rundfunkempfänger nach Anspruch 7, wobei die Dienstabrufinformation Information enthält, die eine PLP identifiziert, die die Dienstschichtsignalisierung enthält.
  9. Rundfunkempfänger nach Anspruch 6, wobei die Header-Komprimierungsinformation eine PLP-Identifizierung, die eine PLP unter den PLPs identifiziert, und einen für die PLP zu verwendenden Maximalwert einer Kontextidentifizierung enthält.
  10. Rundfunkempfänger nach Anspruch 6, wobei die Verbindungsschichtpakete ferner einen Signalisierungsinformationsteil enthalten, der zusätzliche Information enthält, die zum Identifizieren eines Verarbeitungsverfahrens der Verbindungsschichtsignalisierungsdaten verwendet wird, die in dem mindestens einen zweiten Verbindungsschichtpaket enthalten sind, und wobei der Signalisierungsinformationsteil Signalisierungsklasseninformation enthält, die identifiziert, ob die über das mindestens eine zweite Verbindungsschichtpaket übertragenen Verbindungsschichtsignalisierungsdaten der Dienstabrufinformation entsprechen.
EP15811631.9A 2014-06-26 2015-06-25 Vorrichtungen zum senden/empfangen eines broadcast-signals Active EP3046304B1 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201462017798P 2014-06-26 2014-06-26
US201462054358P 2014-09-23 2014-09-23
PCT/KR2015/006506 WO2015199468A1 (ko) 2014-06-26 2015-06-25 방송 신호 송/수신 처리 방법 및 장치

Publications (3)

Publication Number Publication Date
EP3046304A1 EP3046304A1 (de) 2016-07-20
EP3046304A4 EP3046304A4 (de) 2017-04-19
EP3046304B1 true EP3046304B1 (de) 2019-04-10

Family

ID=54938465

Family Applications (1)

Application Number Title Priority Date Filing Date
EP15811631.9A Active EP3046304B1 (de) 2014-06-26 2015-06-25 Vorrichtungen zum senden/empfangen eines broadcast-signals

Country Status (5)

Country Link
US (4) US9998572B2 (de)
EP (1) EP3046304B1 (de)
KR (1) KR101797503B1 (de)
CN (1) CN105723682B (de)
WO (1) WO2015199468A1 (de)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015199468A1 (ko) 2014-06-26 2015-12-30 엘지전자 주식회사 방송 신호 송/수신 처리 방법 및 장치
EP3522548B1 (de) 2014-10-21 2022-02-23 Sony Group Corporation Empfangsvorrichtung, empfangsverfahren, sendevorrichtung und sendeverfahren
WO2016117939A1 (ko) * 2015-01-21 2016-07-28 엘지전자 주식회사 방송 신호 송신 장치, 방송 신호 수신 장치, 방송 신호 송신 방법, 및 방송 신호 수신 방법
KR101991192B1 (ko) * 2015-02-11 2019-06-19 브이아이디 스케일, 인크. Http를 통한 동적 적응형 스트리밍(dash)에서의 일반화된 http 헤더를 위한 시스템 및 방법
JPWO2016140088A1 (ja) * 2015-03-04 2017-12-14 ソニー株式会社 受信装置、受信方法、送信装置、及び、送信方法
KR102245605B1 (ko) * 2015-07-01 2021-04-28 삼성전자주식회사 링크 계층 프로토콜을 지원하는 멀티미디어 시스템에서 신호 송/수신 장치 및 방법
TW201725878A (zh) * 2015-09-14 2017-07-16 Sony Corp 受訊裝置、送訊裝置及資料處理方法
JP7054673B2 (ja) * 2016-07-08 2022-04-14 ソニーセミコンダクタソリューションズ株式会社 受信装置、及び、データ処理方法
MX2020004441A (es) * 2017-11-09 2020-08-06 Lg Electronics Inc Dispositivo de transmisión de señal de radiodifusión, método de transmisión de señal de radiodifusión, dispositivo de recepción de señal de radiodifusión, y método de recepción de señal de radiodifusión.
US10848345B2 (en) * 2018-12-31 2020-11-24 Hughes Network Systems, Llc Multi-protocol encapsulation traffic acceleration and optimization
CN112312587A (zh) * 2019-07-30 2021-02-02 夏普株式会社 用户设备及其执行的方法和基站及其执行的方法

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20070079275A (ko) * 2006-02-01 2007-08-06 삼성전자주식회사 디지털 멀티미디어 방송 시스템에서의 데이터 송수신 방법및 그에 따른 시스템
US20080130561A1 (en) * 2006-12-04 2008-06-05 Samsung Electronics Co., Ltd. System and method for wireless communication
US7912057B2 (en) * 2007-01-12 2011-03-22 Wi-Lan Inc. Convergence sublayer for use in a wireless broadcasting system
KR101486372B1 (ko) * 2007-07-25 2015-01-26 엘지전자 주식회사 디지털 방송 시스템 및 데이터 처리 방법
US20100296450A1 (en) * 2008-01-04 2010-11-25 Antonella Faniuolo Transmission methods, network equipment, user equipment and telecommunication system
US8248910B2 (en) 2008-01-29 2012-08-21 Nokia Corporation Physical layer and data link layer signalling in digital video broadcast preamble symbols
CN101729371B (zh) 2008-10-31 2012-01-25 华为技术有限公司 一种业务传输的方法、及用于业务传输的装置
CN102100067B (zh) * 2009-02-13 2013-04-24 Lg电子株式会社 用于发送和接收信号的装置以及用于发送和接收信号的方法
CA2819405C (en) * 2010-02-23 2017-06-27 Lg Electronics Inc. Broadcasting signal transmission device, broadcasting signal reception device, and method for transmitting/receiving broadcasting signal using same
EP2566156A4 (de) * 2010-04-28 2015-04-29 Lg Electronics Inc Rundfunksignalsender, rundfunksignalempfänger sowie verfahren zum senden und empfangen von rundfunksignalen mit vorrichtungen zum senden und empfangen von rundfunksignalen
US9055392B2 (en) * 2010-08-03 2015-06-09 Samsung Electronics Co., Ltd. Method and apparatus of communicating packet data units in a wireless network environment and system using thereof
CA2824464C (en) * 2010-09-14 2016-07-12 Lg Electronics Inc. Apparatus for transmitting broadcasting signal, apparatus for receiving broadcasting signal, and method for transmitting/receiving broadcasting signal through apparatus for transmitting/receiving broadcasting signal
KR101874433B1 (ko) * 2011-06-16 2018-07-06 삼성전자주식회사 디지털 방송 시스템에서 방송 서비스 수신을 위한 시그널링 정보를 송수신하는 방법 및 장치
WO2013129781A1 (ko) 2012-03-02 2013-09-06 엘지전자 주식회사 모바일 방송을 통하여 긴급 경보 서비스를 제공하는 장치 및 방법
CN104247436A (zh) * 2012-04-25 2014-12-24 三星电子株式会社 在数字广播系统中用于发送和接收的信令信息的装置和方法
BR112015013761B1 (pt) * 2012-12-20 2022-12-06 Lantiq Israel Ltd Dispositivo de fonte, método para transmitir datagramas de um dispositivo de fonte para um dispositivo de destino e estrutura de pacote agregado
KR101294695B1 (ko) * 2013-01-16 2013-08-09 (주)에이투유정보통신 근거리 무선 통신 접속 장치, 근거리 무선 통신 접속 장치를 발견하기 위한 휴대형 단말기, 및 근거리 무선 통신 시스템
MX350242B (es) * 2013-10-28 2017-08-31 Lg Electronics Inc Aparato para transmitir señales de difusion, aparato para recibir señales de difusion, metodo para transmitir señales de difusion y metodo para recibir señales de difusion.
WO2015199468A1 (ko) * 2014-06-26 2015-12-30 엘지전자 주식회사 방송 신호 송/수신 처리 방법 및 장치

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
CN105723682B (zh) 2019-08-23
KR20160040550A (ko) 2016-04-14
US20190327349A1 (en) 2019-10-24
US10582029B2 (en) 2020-03-03
US20160198023A1 (en) 2016-07-07
US11032400B2 (en) 2021-06-08
US20200169622A1 (en) 2020-05-28
US20180270334A1 (en) 2018-09-20
EP3046304A1 (de) 2016-07-20
CN105723682A (zh) 2016-06-29
WO2015199468A1 (ko) 2015-12-30
US9998572B2 (en) 2018-06-12
EP3046304A4 (de) 2017-04-19
US10389855B2 (en) 2019-08-20
KR101797503B1 (ko) 2017-11-15

Similar Documents

Publication Publication Date Title
US11032400B2 (en) Method and device for transmitting/receiving broadcast signal
US10887277B2 (en) Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal
US11019186B2 (en) Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal
KR101823481B1 (ko) 방송 신호를 송신 및 수신하기 위한 장치 및 방법
US11057586B2 (en) Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal
US10856021B2 (en) Broadcast signal transmission apparatus, broadcast signal reception apparatus, broadcast signal transmission method, and broadcast signal reception method
EP3242457B1 (de) Rundfunksignalsendevorrichtung, rundfunksignalempfangsvorrichtung, rundfunksignalsendeverfahren und rundfunksignalempfangsverfahren
EP3242456A1 (de) Rundfunksignalübertragungsvorrichtung, rundfunksignalempfangsvorrichtung, rundfunksignalübertragungsverfahren und rundfunksignalempfangsverfahren
CA2920067C (en) Apparatus for transmitting broadcast signal, apparatus for receiving broadcast signal, method for transmitting broadcast signal and method for receiving broadcast signal

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20160412

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

A4 Supplementary search report drawn up and despatched

Effective date: 20170321

RIC1 Information provided on ipc code assigned before grant

Ipc: H04N 21/434 20110101ALI20170315BHEP

Ipc: H04L 29/08 20060101ALI20170315BHEP

Ipc: H04W 4/06 20090101ALI20170315BHEP

Ipc: H04N 21/235 20110101ALI20170315BHEP

Ipc: H04L 29/06 20060101AFI20170315BHEP

DAV Request for validation of the european patent (deleted)
DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20180209

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

INTG Intention to grant announced

Effective date: 20181210

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

Ref country code: AT

Ref legal event code: REF

Ref document number: 1120250

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190415

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 602015028192

Country of ref document: DE

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20190410

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

REG Reference to a national code

Ref country code: AT

Ref legal event code: MK05

Ref document number: 1120250

Country of ref document: AT

Kind code of ref document: T

Effective date: 20190410

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: ES

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: LT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190910

Ref country code: AL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: NO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190710

Ref country code: HR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190711

Ref country code: LV

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: RS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: BG

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190710

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: IS

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190810

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 602015028192

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: RO

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: CZ

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: EE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: MC

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: SK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: SM

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

26N No opposition filed

Effective date: 20200113

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20190710

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20190630

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190625

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190710

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190630

Ref country code: SI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190625

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190630

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190630

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20190630

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HU

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT; INVALID AB INITIO

Effective date: 20150625

Ref country code: MT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 602015028192

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0029060000

Ipc: H04L0065000000

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20190410

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230508

Year of fee payment: 9