WO2010058958A2 - Procédé de traitement d'un service en temps non réel et récepteur de radiodiffusion - Google Patents

Procédé de traitement d'un service en temps non réel et récepteur de radiodiffusion Download PDF

Info

Publication number
WO2010058958A2
WO2010058958A2 PCT/KR2009/006794 KR2009006794W WO2010058958A2 WO 2010058958 A2 WO2010058958 A2 WO 2010058958A2 KR 2009006794 W KR2009006794 W KR 2009006794W WO 2010058958 A2 WO2010058958 A2 WO 2010058958A2
Authority
WO
WIPO (PCT)
Prior art keywords
content
field
information
nrt
service
Prior art date
Application number
PCT/KR2009/006794
Other languages
English (en)
Korean (ko)
Other versions
WO2010058958A3 (fr
Inventor
서종렬
토마스고머
송재형
김진필
홍호택
이준휘
Original Assignee
엘지전자 주식회사
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 엘지전자 주식회사 filed Critical 엘지전자 주식회사
Priority to KR1020167021383A priority Critical patent/KR101727049B1/ko
Priority to KR1020177009361A priority patent/KR101759958B1/ko
Publication of WO2010058958A2 publication Critical patent/WO2010058958A2/fr
Publication of WO2010058958A3 publication Critical patent/WO2010058958A3/fr

Links

Images

Classifications

    • E—FIXED CONSTRUCTIONS
    • E04—BUILDING
    • E04B—GENERAL BUILDING CONSTRUCTIONS; WALLS, e.g. PARTITIONS; ROOFS; FLOORS; CEILINGS; INSULATION OR OTHER PROTECTION OF BUILDINGS
    • E04B2/00—Walls, e.g. partitions, for buildings; Wall construction with regard to insulation; Connections specially adapted to walls
    • E04B2/72—Non-load-bearing walls of elements of relatively thin form with respect to the thickness of the wall
    • E04B2/721—Non-load-bearing walls of elements of relatively thin form with respect to the thickness of the wall connections specially adapted therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/08—Systems for the simultaneous or sequential transmission of more than one television signal, e.g. additional information signals, the signals occupying wholly or partially the same frequency band, e.g. by time division
    • 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
    • E—FIXED CONSTRUCTIONS
    • E04—BUILDING
    • E04B—GENERAL BUILDING CONSTRUCTIONS; WALLS, e.g. PARTITIONS; ROOFS; FLOORS; CEILINGS; INSULATION OR OTHER PROTECTION OF BUILDINGS
    • E04B1/00—Constructions in general; Structures which are not restricted either to walls, e.g. partitions, or floors or ceilings or roofs
    • E04B1/38—Connections for building structures in general
    • E04B1/388—Separate connecting elements
    • E—FIXED CONSTRUCTIONS
    • E04—BUILDING
    • E04B—GENERAL BUILDING CONSTRUCTIONS; WALLS, e.g. PARTITIONS; ROOFS; FLOORS; CEILINGS; INSULATION OR OTHER PROTECTION OF BUILDINGS
    • E04B1/00—Constructions in general; Structures which are not restricted either to walls, e.g. partitions, or floors or ceilings or roofs
    • E04B1/38—Connections for building structures in general
    • E04B1/61—Connections for building structures in general of slab-shaped building elements with each other
    • E04B1/6108—Connections for building structures in general of slab-shaped building elements with each other the frontal surfaces of the slabs connected together
    • E04B1/612—Connections for building structures in general of slab-shaped building elements with each other the frontal surfaces of the slabs connected together by means between frontal surfaces
    • E04B1/6125—Connections for building structures in general of slab-shaped building elements with each other the frontal surfaces of the slabs connected together by means between frontal surfaces with protrusions on the one frontal surface co-operating with recesses in the other frontal surface
    • E04B1/6141—Connections for building structures in general of slab-shaped building elements with each other the frontal surfaces of the slabs connected together by means between frontal surfaces with protrusions on the one frontal surface co-operating with recesses in the other frontal surface the connection made by an additional locking key
    • E—FIXED CONSTRUCTIONS
    • E04—BUILDING
    • E04F—FINISHING WORK ON BUILDINGS, e.g. STAIRS, FLOORS
    • E04F13/00—Coverings or linings, e.g. for walls or ceilings
    • E04F13/07—Coverings or linings, e.g. for walls or ceilings composed of covering or lining elements; Sub-structures therefor; Fastening means therefor
    • E04F13/08—Coverings or linings, e.g. for walls or ceilings composed of covering or lining elements; Sub-structures therefor; Fastening means therefor composed of a plurality of similar covering or lining elements
    • E04F13/0801—Separate fastening elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the 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
    • 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/47—End-user applications
    • H04N21/482—End-user interface for program selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/85—Assembly of content; Generation of multimedia applications
    • H04N21/854—Content authoring
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N5/00—Details of television systems
    • H04N5/44—Receiver circuitry for the reception of television signals according to analogue transmission standards
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/015—High-definition television systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/08—Systems for the simultaneous or sequential transmission of more than one television signal, e.g. additional information signals, the signals occupying wholly or partially the same frequency band, e.g. by time division
    • H04N7/081—Systems for the simultaneous or sequential transmission of more than one television signal, e.g. additional information signals, the signals occupying wholly or partially the same frequency band, e.g. by time division the additional information signals being transmitted by means of a subcarrier
    • E—FIXED CONSTRUCTIONS
    • E04—BUILDING
    • E04B—GENERAL BUILDING CONSTRUCTIONS; WALLS, e.g. PARTITIONS; ROOFS; FLOORS; CEILINGS; INSULATION OR OTHER PROTECTION OF BUILDINGS
    • E04B1/00—Constructions in general; Structures which are not restricted either to walls, e.g. partitions, or floors or ceilings or roofs
    • E04B1/38—Connections for building structures in general
    • E04B1/388—Separate connecting elements
    • E04B2001/389—Brackets
    • E—FIXED CONSTRUCTIONS
    • E04—BUILDING
    • E04B—GENERAL BUILDING CONSTRUCTIONS; WALLS, e.g. PARTITIONS; ROOFS; FLOORS; CEILINGS; INSULATION OR OTHER PROTECTION OF BUILDINGS
    • E04B2/00—Walls, e.g. partitions, for buildings; Wall construction with regard to insulation; Connections specially adapted to walls
    • E04B2/02—Walls, e.g. partitions, for buildings; Wall construction with regard to insulation; Connections specially adapted to walls built-up from layers of building elements
    • E04B2002/0202—Details of connections
    • E04B2002/0243—Separate connectors or inserts, e.g. pegs, pins or keys
    • F—MECHANICAL ENGINEERING; LIGHTING; HEATING; WEAPONS; BLASTING
    • F16—ENGINEERING ELEMENTS AND UNITS; GENERAL MEASURES FOR PRODUCING AND MAINTAINING EFFECTIVE FUNCTIONING OF MACHINES OR INSTALLATIONS; THERMAL INSULATION IN GENERAL
    • F16B—DEVICES FOR FASTENING OR SECURING CONSTRUCTIONAL ELEMENTS OR MACHINE PARTS TOGETHER, e.g. NAILS, BOLTS, CIRCLIPS, CLAMPS, CLIPS OR WEDGES; JOINTS OR JOINTING
    • F16B5/00—Joining sheets or plates, e.g. panels, to one another or to strips or bars parallel to them
    • F16B5/0004—Joining sheets, plates or panels in abutting relationship
    • F16B5/0032—Joining sheets, plates or panels in abutting relationship by moving the sheets, plates, or panels or the interlocking key parallel to the abutting edge
    • F16B5/0036—Joining sheets, plates or panels in abutting relationship by moving the sheets, plates, or panels or the interlocking key parallel to the abutting edge and using hook and slot or keyhole-type connections
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10T—TECHNICAL SUBJECTS COVERED BY FORMER US CLASSIFICATION
    • Y10T403/00—Joints and connections
    • Y10T403/55—Member ends joined by inserted section
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10T—TECHNICAL SUBJECTS COVERED BY FORMER US CLASSIFICATION
    • Y10T403/00—Joints and connections
    • Y10T403/70—Interfitted members

Definitions

  • the present invention relates to a method and a broadcast receiver for receiving and processing a service transmitted in non real time.
  • Digital television is able to provide a variety of services in addition to video, audio, which is a unique feature of television (TV).
  • broadcast information Electronic Program Guide: EPG
  • EPG Electronic Program Guide
  • broadcast services received from two or more channels may be simultaneously provided.
  • the receiving system is equipped with a large-capacity storage device and is connected to the Internet or a data communication channel capable of bidirectional communication, there are many services that can be provided using broadcast signals.
  • An object of the present invention is to provide a non-real-time service processing method and a broadcast receiver for receiving and processing a non-real-time service.
  • Another object of the present invention is to provide a method and a broadcast receiver for processing a non-real-time service, which makes it easy to check a change in content constituting the non-real-time service at an IP level.
  • Still another object of the present invention is to provide a non-real-time service processing method and a broadcast receiver that make it easy to check whether the content is updated by including update information of the content in a signaling information table.
  • a non-real-time service processing method of a broadcast receiver receiving and processing signaling information including the detailed information and update information of the content, including at least one file Receiving and storing the content in non-real time; checking whether the content is updated based on update information of the content included in the signaling information; and if the update of the content is confirmed, transmitting the content. Connecting to a FLUTE session and receiving at least one file of updated content.
  • the update information of the content includes a first field indicating whether a version number of the content is included in the signaling information, and a second field indicating a version number of the content according to the first field value.
  • the update checking step confirms an update of the content by comparing a version number of the content displayed in the second field with a previous version number of the content.
  • the update information of the content further includes a third field indicating whether the content is updated content.
  • a method of processing a non-real-time service by a broadcast receiver receiving and processing first signaling information including content connection information and second signaling information including detailed information of the content.
  • Receiving and processing third signaling information including update information of the content receiving and storing content including at least one file based on the first and second signaling information in real time, and storing the third signal
  • Receiving one file receiving one file.
  • the access information of the first to third signaling information may be configured with the same preset IP address and the same UDP port number.
  • the access information of the first and second signaling information may be configured with the same preset IP address and the same UDP port number, and the access information of the third signaling information may be included in the first signaling information.
  • the update information of the content includes a first field indicating identification information of the content, and a second field indicating a version number of the content.
  • the update checking step confirms an update of the content by comparing a version number of the content displayed in the second field with a previous version number of the content.
  • the broadcast receiver includes first to third processing units.
  • the first processor receives and processes first signaling information including access information of content, second signaling information including detailed information of the content, and third signaling information including update information of the content.
  • the second processor receives the content including at least one file in real time based on the first and second signaling information and stores the content in a storage medium.
  • the third processor determines whether to update the content based on the update information of the content included in the third signaling information, and when the update of the content is confirmed, accesses to a flute session for transmitting the content. Receive at least one file of updated content.
  • the access information of the first to third signaling information may be configured with the same preset IP address and the same UDP port number.
  • the access information of the first and second signaling information may be configured with the same preset IP address and the same UDP port number, and the access information of the third signaling information may be included in the first signaling information.
  • the update information of the content includes a first field indicating identification information of the content, and a second field indicating a version number of the content.
  • the third processing unit confirms the update of the content by comparing the version number of the content displayed in the second field with the previous version number of the content.
  • the present invention can know whether the content item is updated without constantly checking the header of every packet of the FLUTE sessions transmitting the files constituting the content item. Only when the content item is updated, the FLUTE session is accessed to download files included in the content item. As described above, the present invention can determine whether the content item is changed at the IP level and can reduce the burden on the broadcast receiver since the FLUTE session is accessed only when the content item is changed.
  • the present invention allows the signaling and data changes to be easily synchronized since the NRT-IT for the NRT service and the FLUTE sessions for the NRT service are generated by the same server. signaling with the data changes easily, since the NRT-IT instances for a service and the FLUTE sessions for the service will typically be generated by the same server.). It also makes it easier to synchronize NRT-IT changes and content changes.
  • FIG. 1 illustrates a concept of providing a real-time service RT and a non-real time service (NRT) according to the present invention.
  • FIG. 2 is a diagram illustrating a relationship between an NRT service, a content item, and a file according to the present invention.
  • FIG. 3 illustrates an embodiment of a protocol stack for a fixed NRT service according to the present invention.
  • FIG. 4 illustrates an embodiment of a bit stream syntax structure of a virtual channel table according to the present invention
  • FIG. 5 is a diagram illustrating an embodiment of a service type field value and meaning of the value in the virtual channel table of FIG. 4.
  • FIG. 6 illustrates another embodiment of a value assigned to a service type field in the virtual channel table of FIG. 4 and the meaning of the value.
  • FIG. 7 illustrates an embodiment of a bit stream syntax structure of a data service table according to the present invention
  • FIG. 8 illustrates an embodiment of a process of acquiring access information of an IP stream for transmitting an NRT service signaling channel using a PSI / PSIP table according to the present invention.
  • FIG. 9 is a flowchart illustrating an embodiment of a process of acquiring access information of an IP stream for transmitting an NRT service signaling channel using a PSI / PSIP table according to the present invention.
  • 10 and 11 illustrate an embodiment of a bit stream syntax structure of an NST section according to the present invention.
  • component_descriptor () illustrates an embodiment of a bit stream syntax structure of component_descriptor () according to the present invention.
  • FIG. 13 is a diagram illustrating an embodiment of a bit stream syntax structure of FLUTE file delivery data using component_descriptor () of FIG. 12.
  • 16 is a flowchart illustrating an embodiment of a process of checking and processing an update of a content item using an NRT-IT section according to the present invention.
  • FIG. 17 illustrates an embodiment of a bit stream syntax structure of a CVT section according to the present invention.
  • FIG. 18 is a flow diagram illustrating one embodiment of a process for identifying and processing an update of a content item using a CVT section in accordance with the present invention.
  • FIG. 19 illustrates an embodiment of a bit stream syntax structure of CVT_location_descriptor () included in a service level descriptor of an NST according to the present invention.
  • FIG. 20 is a flowchart illustrating another embodiment of a process of confirming and processing an update of a content item using a CVT section according to the present invention.
  • FIG. 21 illustrates an embodiment of a syntax structure of a content fragment of OMA BCAST according to the present invention.
  • FIG. 22 is a block diagram showing an embodiment of a receiving system for a fixed NRT service according to the present invention.
  • a real time (RT) service literally means a real time service. In other words, it is a time-bound service.
  • non-real time (NRT) service means non-real time service other than the RT service.
  • non-real-time services are services that are not bound by time. Data for the NRT service will be referred to as NRT service data.
  • the broadcast receiver according to the present invention may receive NRT service through a medium such as terrestrial, cable, or the Internet.
  • the NRT service is stored in the storage medium of the broadcast receiver and then displayed on the display device according to a preset time or a user's request.
  • the NRT service is received in a file form and stored in a storage medium.
  • the storage medium is an internal HDD mounted inside a broadcast receiver.
  • the storage medium may be a USB (Universal Serial Bus) memory or an external HDD connected to the outside of the broadcast receiving system.
  • NRT service signaling information In order to receive files constituting the NRT service, store them in a storage medium, and service the user, signaling information is required. In the present invention, this is referred to as NRT service signaling information or NRT service signaling data.
  • the NRT service according to the present invention may be classified into a fixed NRT service and a mobile NRT service according to a method of obtaining an IP datagram.
  • the fixed NRT service is provided to a fixed broadcast receiver
  • the Mobile NRT service is provided to a mobile broadcast receiver.
  • the present invention will be described as an embodiment of a fixed NRT service. However, it is a matter of course that the present invention can be applied to a mobile NRT service.
  • 1 illustrates a concept of providing an RT service and an NRT service.
  • the broadcasting station transmits the RT service according to the existing scheme, that is, like the current terrestrial broadcasting.
  • the broadcasting station may transmit the RT service and use the remaining bandwidth in the process or provide the NRT service using the dedicated bandwidth. That is, the RT service and the NRT service are transmitted through the same channel or different channels.
  • NRT service signaling information (or NRT service signaling data) is required to distinguish RT service from NRT service in a broadcast receiver, store the divided NRT service, and provide the same to a user when necessary.
  • the NRT service signaling information (or NRT service signaling data) will be described in detail later.
  • a broadcast station may transmit broadcast service data in real time, and may transmit news clips, weather information, advertisements, Push VODs, and the like in non real time.
  • the NRT service may be news clips, weather information, advertisements, Push VOD, as well as specific scenes of a real time broadcast stream, detailed information of a specific program, and the like.
  • Conventional broadcast receivers can receive and process real-time services, but cannot receive and process non-real-time services. That is, the conventional broadcast receiver (ie, legacy device) is the principle that the operation is not affected by the NRT stream included in the channel for transmitting the real-time service. In other words, the conventional broadcast receiver cannot process the received NRT service because the conventional broadcast receiver is not provided with a means capable of properly processing the NRT service.
  • the broadcast receiver that is, the NRT device
  • the broadcast receiver can receive and properly process the NRT service combined with the RT service, it can provide a variety of functions to the viewer than the conventional broadcast receiver.
  • one NRT service includes one or more content items (or content or NRT content) as shown in FIG. 2, and one content item includes one or more files.
  • content items or content or NRT content
  • files and objects are used in the same sense.
  • the content item is a minimum unit that can be played independently.
  • the news includes economic news, political news, and life news
  • the news may be referred to as an NRT service. It may be referred to as a content item.
  • Each of the economic news, political news, and life news is composed of one or more files.
  • the NRT service may be transmitted in the form of an MPEG-2 transport stream (TS) packet through the same broadcast channel or dedicated broadcast channel as the RT service.
  • TS transport stream
  • IP-based NRT service data is transmitted through MPEG-2 TS packetization.
  • NRT service signaling data necessary for receiving the NRT service data is transmitted through an NRT service signaling channel.
  • the NRT service signaling channel is transmitted through a specific IP stream on an IP layer.
  • the IP stream is also transmitted in an MPEG-2 TS packet.
  • NRT service signaling data transmitted through the NRT service signaling channel includes an NST and an NRT-IT.
  • the NST provides at least one NRT service running in an IP layer and access information of content items / files constituting the NRT service.
  • the NRT-IT provides detailed information of content items / files constituting an NRT service.
  • the NST and NRT-IT may be referred to as a signaling information table.
  • FIG. 3 illustrates a protocol stack for an NRT service configured according to an embodiment of the present invention.
  • the file-type NRT service is IP packetized in an IP layer and then transmitted in a MPEG-2 TS format through a specific virtual channel.
  • MPEG-2 based Program Specific Information (PSI) / Program and System Information Protocol (PSIP) table for example, whether a NRT service exists in a virtual channel through a virtual channel table (VCT), and According to an embodiment of the present invention, signaling identification information of the NRT service is performed.
  • PSI Program Specific Information
  • PSIP Program and System Information Protocol
  • an NRT service signaling channel for transmitting NRT service signaling data for signaling access information of an IP-based NRT service is IP packetized to a specific IP stream in an IP layer and then transmitted in an MPEG-2 TS form. Shall be.
  • the broadcasting station packetizes NRT content items / files according to a file transfer protocol scheme as shown in FIG. 3, and packetizes them again according to ALC / LCT (Asynchronous Layered Coding / Layered Coding Transport) scheme.
  • the packetized ALC / LCT data is again packetized according to the UDP scheme, and the packetized ALC / LCT / UDP data is again packetized according to the IP scheme to be ALC / LCT / UDP / IP data.
  • the ALC / LCT / UDP / IP data includes a file description table (FDT) including information on a FLUTE session.
  • the packetized ALC / LCT / UDP / IP data is referred to as an IP datagram for convenience of description in the present invention.
  • NRT service signaling data necessary for receiving the NRT content / files is transmitted through an NRT service signaling channel, wherein the NRT service signaling channel is packetized according to a User Datagram protocol (UDP) scheme, and the packetized UDP data. Is again packetized according to the IP method to become UDP / IP data.
  • UDP User Datagram protocol
  • the UDP / IP data is also called an IP datagram for convenience of explanation.
  • the NRT service signaling channel is encapsulated in an IP datagram having a well-known IP desiccation address and a well-known desiccation UDP port number and multicasted.
  • IP datagrams of the NRT service and the NRT service signaling channel are encapsulated in an addressable section structure, and packetized into an MPEG-2 TS format. That is, one addressable section structure has a form in which a section header and a CRC checksum are additionally added to one IP datagram.
  • the form of the addressable section structure is a structure that conforms to the Digital Storage Media Command and Control (DSM-CC) section format for private data transmission. Therefore, the addressable section may also be referred to as a DSM-CC addressable section.
  • DSM-CC Digital Storage Media Command and Control
  • the addressable section may also be referred to as a DSM-CC addressable section.
  • a 4-byte MPEG header is added to each of 184 bytes, thereby producing 188 bytes of MPEG-2 TS packets.
  • the value assigned to the PID of the MPEG header is a unique value for identifying the TS packet for transmitting the NRT service and the NRT service signaling channel.
  • program specific information (PSI) and program and system information protocol (PSIP) table section data are also MPEG-2 TS packets.
  • the PSI table includes a Program Map Table (PMT), a Program Association Table (PAT), and the like
  • the PSIP table includes, in an embodiment, a virtual channel table (VCT), a system time table (STT), and an RRT.
  • VCT virtual channel table
  • STT system time table
  • RRT RRT
  • ETT Extended Text Table
  • DCCT Direct Channel Change Table
  • DCCSCT Direct Channel Change Selection Code Table
  • EIT Event Information Table
  • MTT Master Guide Table
  • the MPEG-2 TS packets are modulated by a predetermined transmission scheme, for example, a VSB transmission scheme, in a physical layer and transmitted to a receiving system.
  • a predetermined transmission scheme for example, a VSB transmission scheme
  • whether or not to transmit an NRT service is signaled through a PSI / PSIP table.
  • a PSI / PSIP table For example, signaling whether to transmit the NRT service to a virtual channel table (VCT) is an embodiment.
  • VCT virtual channel table
  • VCT virtual channel table
  • the VCT section transmits information on a virtual channel, for example, channel information for channel selection and packet identifier (PID) for receiving audio and / or video.
  • PID packet identifier
  • the syntax of the VCT section includes at least one of table_id field, section_syntax_indicator field, private_indicator field, section_length field, transport_stream_id field, version_number field, current_next_indicator field, section_number field, last_section_number field, protocol_version field, num_channels_in_section field.
  • the syntax of the VCT section further includes a first loop of a 'for' loop (that is, a virtual channel loop) that is repeated by the value of the num_channels_in_section field, in which the short_name field, major_channel_number field, minor_channel_number field, modulation_mode field a second loop with a 'for' loop that repeats as many times as the number of descriptors included in the first loop, carrier_frequency field, channel_TSID field, program_number field, ETM_location field, access_controlled field, hidden field, service_type field, source_id field, descriptor_length field, and this first loop. It comprises at least one of.
  • the second loop is referred to as a first descriptor loop for convenience of description.
  • Descriptor descriptors () included in the first descriptor loop are descriptors individually applied to each virtual channel.
  • the VCT section syntax may further include an additional_descriptor_length field and a third loop that is a 'for' loop that is repeated by the number of descriptors added to the VCT section.
  • the third loop is called a second descriptor loop.
  • the descriptor additional_descriptors () included in the second descriptor loop is a descriptor commonly applied to all virtual channels described in the VCT section.
  • the table_id field indicates a unique identifier (ID) for recognizing that information transmitted to the table is a VCT. That is, the table_id field indicates a value indicating that the table to which this section belongs is a VCT. For example, 0xC8 may be assigned.
  • the version_number field indicates a version value of the VCT
  • the section_number field indicates a number of this section
  • the last_section_number field indicates a number of the last section of the complete VCT.
  • the num_channels_in_section field designates the number of all virtual channels existing in the VCT section.
  • the short_name field in the first loop of the 'for' loop indicates a virtual channel name
  • the major_channel_number field indicates a 'major' channel number associated with a virtual channel defined in the first loop
  • the minor_channel_number field is' Minor 'channel number. That is, each virtual channel number should be connected to major and minor channel numbers, and the major and minor channel numbers serve as a user reference number for the corresponding virtual channel.
  • the program_number field indicates to connect a virtual channel in which an MPEG-2 Program Association Table (PAT) and a Program Map Table (PMT) are defined, and corresponds to a program number in the PAT / PMT.
  • PAT describes the components of the program for each program number, and indicates the PID of the transport packet for transmitting the PMT.
  • the PMT describes a PID list and accessory information of a transport packet to which a program identification number and individual bit strings such as video and audio constituting the program are transmitted.
  • the service_type field is a field indicating a service type in a corresponding virtual channel.
  • the virtual channel may include both at least one RT service and at least one NRT service including audio and / or video.
  • a service type value may be allocated as shown in FIG. 5, and may indicate that an NRT service is transmitted through the virtual channel using 0x04 indicating an ATSC data only service.
  • the virtual channel may include only one or more NRT services.
  • 0x08 may be newly defined as a service_type field value and may indicate that an NRT service is transmitted to the virtual channel.
  • the source_id field represents a program source connected to the corresponding virtual channel.
  • the source refers to one specific source such as image, text, data or sound.
  • the source_id field value has a unique value in the transport stream for transmitting the VCT.
  • the DST may be received through a PID included in the service_location_descriptor of the VCT, and the type of application and detailed information of the data broadcast stream transmitted through this channel may be known through the data service table (DST).
  • DST data service table
  • the present invention uses the DST to identify an NRT application (ie, NRT service).
  • NRT application ie, NRT service
  • FIG. 7 illustrates an embodiment of a syntax structure of the DST section.
  • the sdf_protocol_version field (8 bits) describes the version of the Service Description Framework protocol.
  • the application_count_in_section field (8 bits) describes the number of applications listed in the DST section.
  • the compatibility_descriptor () field indicates that the structure includes a DSM-CC compatibility descriptor.
  • the purpose is to signal the compatibility requirements of the application in the receiving platform to determine its ability to use that data service.
  • An app_id_byte_length field (16 bits) describes the number of bytes used to identify an application.
  • the app_id_description field (16 bits) describes the format and semantics of the following application identification bytes.
  • '0x0003' is newly allocated and used to identify that the corresponding application is an NRT application.
  • the above-described numerical values are merely examples, and the scope of the present invention is not limited to the numerical values.
  • Table 1 Value Application Identifier Format 0x0000 DASE application 0x0001 ATSC reserved 0x0002 ATSC A / 92 Application 0x0003 NRT Application 0x0004-0x7FFF ATSC reserved 0x8000-0xFFFF User private
  • the app_id_byte field (8 bits) represents a byte of an application identifier.
  • a tap_count field (8 bits) describes the number of Tap () structures used by the corresponding application.
  • the protocol_encapsulation field (8 bits) describes the type of protocol encapsulation used to transmit the specific data element referenced by the Tap () field.
  • An action_type field (7 bits) indicates the nature of the data referred to by the Tap () field.
  • a resource_location field (1 bit) describes the location of the association_tag field that matches the association_tag value listed in the next Tap structure. If this field is set to '0', the matching association_tag exists in the PMT of the current MPEG-2 program. Unlike this, if it is set to '1', the matching association_tag exists in the DSM-CC Resource Descriptor in the Network Resources Table of the corresponding data service.
  • the Tap () field is defined as a specific structure, including, for example, the following fields.
  • the tap_id field (16 bits) is used by the application to identify data elements.
  • the value of tap_id is ranged by the value of app_id_byte fields related to Tap () in DST.
  • the tap_id value is selected by the data service provider. It is also used in applications to manipulate data elements.
  • the Use field (16 bits) is used to specify the communication channel referenced by the association_tag.
  • association_tag field (16 bits) uniquely identifies either the DSM-CC resource descriptor listed in the Network Resource Table or the data elementary stream listed in the PMT. The value of this field shall match the association_tag value of association_tag_descriptor in PMT of data service.
  • the Selector () field describes the specific data element available in the communication channel or data elementary stream referenced by the association_tag field.
  • the selector structure may indicate the protocol required for that data element.
  • a tap_info_length field (16 bits) describes the number of bytes of descriptors of the field following the field.
  • the descriptor () field follows the descriptor format.
  • An app_info_length field (8 bits) describes the number of bytes of descriptors following the field.
  • the descriptor () field follows the descriptor format.
  • An app_data_length field (16 bits) describes the length in bytes of the app_data_byte fields.
  • app_data_byte (8 bits) represents input parameters related to the application and other private data fields in one byte.
  • a service_info_length field (8 bits) describes the number of byte units of the following descriptors.
  • the descriptor () field follows the descriptor format.
  • the service_private_data_length field (16 bits) describes the length in bytes of the private fields.
  • the service_private_data_byte field (8 bits) represents a private field in 1 byte.
  • FIG. 8 is a diagram illustrating a system for receiving and servicing an NRT service using an ATSC A / 90 standard for delivering a data broadcast stream and an ATSC A / 92 standard for transmitting an IP multicast stream in a reception system according to the present invention. The method is explained.
  • information on the streams constituting each virtual channel is signaled to the service location descriptor of the VCT or the ES_loop of the PMT.
  • the service type of the VCT is 0x02 (i.e., digital A / V / Data) or 0x04 (i.e., data only) as in FIG. 5 or 6, or 0x08 (i.e., NRT Only). service
  • an NRT service stream may be transmitted through the virtual channel.
  • 0x95 that is, DST transmission
  • the DST is used to identify an NRT application (ie, an NRT service).
  • the App_id_descrption field of the DST defines the format and interpretation of subsequent application identification bytes.
  • '0x0003' is allocated to the App_id_descrption field to identify an NRT application.
  • the next Application_id_byte value becomes a Service ID value of the NRT application.
  • the service ID for the NRT application may have a URI value that uniquely identifies the service.
  • the PID of the MPEG-2 TS packet divided from the IP datagram of the NRT service signaling channel is found through the tap information. Then, an IP datagram transmitting an NRT service signaling channel can be obtained from MPEG-2 TS packets having PIDs found through the tap information, and NRT service signaling data can be obtained from the obtained IP datagram. .
  • the IP access information of the NRT service signaling channel well-known IP access information, that is, a well-known IP address and a well-known UDP port number may be used.
  • an IP stream that is, an IP packet is received by accessing the IP multicast address (or address range), and NRT service signaling data is extracted from the received IP packet.
  • NRT service data that is, NRT content items / files may be received and stored in a storage medium or displayed on a display device.
  • the NRT service may be signaled using a new value, for example, 0x96 instead of 0x95 in the Stream Type field value of the DST.
  • a new value for example, 0x96 instead of 0x95 in the Stream Type field value of the DST.
  • FIG. 9 is a flowchart illustrating a process of extracting the NRT service signaling data and the NRT service data.
  • 0x08 is allocated to a service_type field value in a VCT to indicate that one or more NRT services are transmitted to a corresponding virtual channel.
  • the VCT and the PMT are obtained from the broadcast signal received through the selected channel (S1002).
  • the obtained VCT is parsed to determine whether there is an NRT service (S1003). This can be known by checking the value of the service_type field in the virtual channel loop of the VCT.
  • the S1001 is performed in a tuner, and the S1002 and S1003 are performed in a PSI / PSIP section handler.
  • the corresponding virtual channel does not transmit the NRT service.
  • the virtual channel since the virtual channel transmits an existing service (that is, legacy ATSC service), the receiver performs an appropriate operation according to the information included in the virtual channel.
  • the corresponding virtual channel transmits an NRT service.
  • the service location descriptor in the virtual channel loop of the VCT is parsed to extract the PID of the DST (S1004).
  • the DST is received using the extracted PID (S1005).
  • S1004 and S1005 are performed in the demultiplexer under the control of a service manager.
  • the NRT service can be confirmed from the value of the App_id_descrption field.
  • '0x0003' is allocated to the App_id_descrption field to identify an NRT application (ie, an NRT service).
  • NRT application ie, an NRT service.
  • the next Application_id_byte value becomes a Service ID value of an NRT application (ie, an NRT service). Therefore, after identifying the NRT application (ie, NRT service) as described above, the Tap is extracted to find the PID of the MPEG-2 TS packet divided from the IP datagram of the NRT service signaling channel (S1007). Subsequently, the stream PID including the association_tag of the extracted Tap is extracted from the PMT (S1008). S1006 to S1008 are performed by a service manager or a PSI / PSIP section handler.
  • the access information of the IP datagram transmitting the NRT service signaling channel is a well-known destination IP address and a well-known destination UDP port number.
  • an IP stream that is, an IP packet is received by accessing the IP multicast address (or address range), and NRT service signaling data is extracted from the received IP packet.
  • NRT service data that is, NRT content items / files may be received and stored in a storage medium or displayed on a display device.
  • the NRT service signaling data transmitted through the NRT service signaling channel includes an NRT service map table (NST) and an NRT information table (NRT-IT). do.
  • the IP datagrams of the NST and NRT-IT have the same well-known IP address and a well-known UDP port number. Therefore, the NST and the NRT-IT included in the NRT service signaling data are distinguished by a table identifier. That is, the table identifier may be table_id existing in the header of the table or the table section, and may be distinguished by further referring to table_id_extension if necessary.
  • the NST provides access information of an NRT service.
  • the NST has a table form similar to the MPEG-2 private section form.
  • the NST may provide access information of IP-based NRT services included in one virtual channel.
  • the NST may provide access information of each FLUTE sessions configuring one NRT service.
  • one NST consists of one section or a plurality of sections may be known through a table_id field, a section_number field, a last_section_number field, and the like in the NST section.
  • a corresponding table may be completed. For example, collecting sections with table identifiers assigned to the NST can complete the NST.
  • the syntax is written in the form of MPEG-2 private section for the sake of understanding, but the format of the data may be in any form.
  • other methods such as signaling in the form of a Session Description Protocol (SDP) and signaling through a Session Announcement Protocol (SAP) may be used.
  • SDP Session Description Protocol
  • SAP Session Announcement Protocol
  • the table_id field (8 bits) is a field for identifying the type of the corresponding table section.
  • the table section is a table section constituting the NST (An 8-bit unsigned integer number). that indicates the type of table section being defined in NRT Service Table (NST).
  • the section_syntax_indicator field (1 bit) is an indicator for defining the section format of the NST.
  • the section format may be, for example, a short-form syntax ('0') of MPEG (section_syntax_indicator: This 1-bit field shall be be). set to '0' to always indicate that this table is derived from the “short” form of the MPEG-2 private section table).
  • the private_indicator field (1 bit) indicates whether the section type follows the private section type (private_indicator: This 1-bit field shall be set to '1').
  • section_length A 12-bit field.It specifies the number of remaining bytes this table section immediately following this field.The value in this field shall not exceed 4093 (0xFFD)).
  • table_id_extension This is a 16-bit field and is table-dependent.It shall be considered to be logically dependent on the table. part of the table_id field providing the scope for the remaining fields).
  • the table_id_extension field includes an NST_protocol_version field.
  • the NST_protocol_version field (8 bits) indicates a protocol version for allowing NST transmitted by parameters having a structure different from those defined in the current protocol (NST_protocol_version: An 8-bit unsigned integer field whose function is to allow, in the future, this NST to carry parameters that may be structured differently than those defined in the current protocol.At present, the value for the NST_protocol_version shall be zero.Non-zero values of NST_protocol_version may be used by a future version of this standard to indicate structurally different tables).
  • a version_number field (5 bits) represents the version number of the NST.
  • current_next_indicator A one-bit indicator, which when set to '1' shall indicate that the NST sent is currently applicable.When the bit is set to '0', it shall indicate that the table sent is not yet applicable and will be the next table to become valid. This standard imposes no requirement that “next” tables (those with current_next_indicator set to '0') must be sent. An update to the currently applicable table shall be signaled by incrementing the version_number field).
  • a section_number field (8 bits) indicates the number of the current NST section. (section_number: This 8-bit field shall give the section number of this NST section. The section_number of the first section in an NST shall be '0x00'. The section_number shall be incremented by 1 with each additional section in the NST.
  • last_section_number This 8-bit field shall give the number of the last section (ie, the section with the highest section_number) of the NST of which this section is a part).
  • a num_NRT_services field (8 bits) indicates the number of NRT services in the NST section (num_services: This 8 bit field specifies the number of services in this NST section).
  • a 'for' loop (or NRT service loop) is performed as many as the number of NRT services corresponding to the num_NRT_services field value to provide signaling information for a plurality of NRT services. That is, signaling information of the corresponding NRT service is displayed for each NRT service included in the NST section. In this case, the following field information may be provided for each NRT service.
  • the NRT_service_id field (16 bits) indicates a value that uniquely identifies this NRT service (A 16-bit unsigned integer number that shall uniquely identify this NRT service within the scope of this NRT section.). The value of the NRT_service_id field of one service does not change while the service is maintained.
  • the NRT_service_id field value of that service may not be used until a certain amount of time has elapsed (The NRT_service_id of a service shall not change throughout the life of the service.To avoid confusion , it is recommended that if a service is terminated, then the NRT_service_id for the service should not be used for another service until after a suitable interval of time has elapsed.).
  • NRT_service_status field (2 bits) identifies the state of the corresponding NRT service.
  • the MSB indicates whether the corresponding NRT service is active ('1') or inactive ('0'), and the LSB indicates whether the corresponding NRT service is hidden ('1') or not ('0').
  • NRT_service_status A 2-bit enumerated field that shall identify the status of this NRT Service. The most significant bit shall indicate whether this NRT Service is active (when set to '1') or inactive (when set to '0') and the least significant bit shall indicate whether this NRT Service is hidden (when set to '1') or not (when set to '0').
  • Hidden services are normally used for proprietary applications, and ordinary receiving devices should ignore them).
  • An SP_indicator field (1 bit) represents whether service protection of a corresponding NRT service is performed. If the value of the SP_indicator field is 1, service protection is applied to at least one of the components required to provide a meaningful presentation of the NRT service (A 1-bit field that indicates, when set to 1, service). protection is applied to at least one of the components needed to provide a meaningful presentation of this NRT Service).
  • the Short_NRT_service_name_length field (3 bits) indicates the number of byte pairs in the Short_NRT_service_name field.
  • a Short_NRT_service_name field (16 * m bits) indicates a short name of the NRT service. If there is no short name of the NRT service, the field may be filled with a null value (eg, 0x00).
  • NRT_service_category (6 bits) identifies a type of service transmitted in the corresponding NRT service (NRT_service_category: A 6-bit enumerated type field that shall identify the type of service carried in this NRT).
  • a num_components field (5 bits) indicates the number of IP stream components included in the NRT service (num_components: This 5-bit field specifies the number of IP stream components in this NRT Service).
  • the IP_version_flag field (1 bit) indicates that the source_IP_address field, the NRT_service_destination_IP_address field, and the component_destination_IP_address field are IPv4 addresses when set to '0', and the source_IP_address field, NRT_service_destination_IP_address field, and component_destination_IP_address field when the value is set to '1'.
  • IP_version_flag A 1-bit indicator, which when set to '0' shall indicate that source_IP_address, NRT_service_destination_IP_address, and component_destination_IP_address fields are IPv4 addresses. The value of '1' for this field is reserved for possible future indication that source_IP_address, NRT_service_destination_IP_address, and component_destination_IP_address fields are for IPv6).
  • the source_IP_address_flag field (1 bit) indicates that a source IP address value for the corresponding NRT service exists to indicate source specific multicast (source_IP_address_flag: A 1-bit Boolean flag that shall indicate, when set , that a source IP address value for this NRT Service is present to indicate a source specific multicast).
  • NRT_service_destination_IP_address_flag A 1-bit Boolean flag that indicates, when set to '1', that a NRT_service_destination_IP_address value is present, to serve as the default IP address for the components of this NRT Service).
  • a source_IP_address field (32 or 128 bits) has a corresponding field when source_IP_address_flag is set to '1', but a corresponding field will not exist when source_IP_address_flag is set to '0'. If this field is present, this field will contain the source IP address of all IP datagrams carrying the components of the NRT service. The limited use of the 128-bit long address in this field is intended to enable future use of IPv6, although the use of IPv6 is currently undefined.
  • Source_IP_address becomes the source IP address of the same server transmitting all channels of the FLUTE session (source_IP_address: This field shall be present if the source_IP_address_flag is set to '1' and shall not be present if the source_IP_address_flag is set to '0'.If present, this field shall contain the source IP address of all the IP datagrams carrying the components of this NRT Service. The conditional use of the 128 bit-long address version of this field is to facilitate possible use of IPv6 in the future, although use of IPv6 is not currently defined).
  • the NRT_service_destination_IP_address field (32 or 128 bits) is set to '1' in the NRT_service_destination_IP_address_flag field, the corresponding NRT_service_destination_IP_address field exists, but if the NRT_service_destination_IP_address_flag field is set to '0', the corresponding NRT_service_destination_IP_address field will not exist. If the corresponding NRT_service_destination_IP_address field does not exist, the component_destination_IP_address field will exist for each component in the num_components loop.
  • NRT_service_destination_IP_address This field shall be present if the NRT_service_destination_IP_address_flag is set to '1' and shall not be present if the NRT_service_destflag is set '0'. If this NRT_service_destination_IP_address is not present, then the component_destination_IP_address field shall be present for each component in the num_components loop. The conditional use of the 128 bit-long address version of this field is to facilitate possible use of IPv6 in the future , although use of IPv6 is not currently defined).
  • a 'for' loop (or a component loop) is performed as many as the number of components corresponding to the num_components field value to provide access information for a plurality of components. That is, it provides connection information of each component included in the NRT service. In this case, the following field information may be provided for each component.
  • one component corresponds to one FLUTE session.
  • the essential_component_indicator field (1 bit) indicates that the component is an essential component for the NRT service when the value of the corresponding field is set to '1'. Otherwise_component_indicator: A one-bit indicator which, when set to '1', shall indicate that this component is an essential component for the NRT Service.Otherwise, this field indicates that this component is an optional component).
  • a port_num_count field (6 bits) indicates the number of UDP ports associated with the corresponding UDP / IP stream component.
  • component_destination_IP_address_flag field (1 bit) is a flag indicating that a component_destination_IP_address field exists for the component when it is set to '1'. component_destination_IP_address is present for this component).
  • the component_destination_IP_address field (32 or 128 bits) has a corresponding field when component_destination_IP_address_flag is set to '1', but the corresponding field will not exist when component_destination_IP_address_flag is set to '0'. If this field is present, this field will contain the source IP address of all IP datagrams carrying the components of the NRT service.
  • the limited use of the 128-bit long address in this field is intended to enable future use of IPv6, although the current use of IPv6 is undefined (component_destination_IP_address: This field shall be present if the component_destination_IP_address_flag is set to '1' and shall not be present if the component_destination_IP_address_flag is set to '0'.
  • the destination address of the IP datagrams carrying this component of the NRT Service shall match the address in this field.
  • the destination address of the IP datagrams carrying this component shall match the address in the NRT_service_destination_IP_address field.
  • the conditional use of the 128 bit-long address version of this field is to facilitate possible use of IPv6 in the future, although use of IPv6 is not currently defined).
  • a component_destination_UDP_port_num field (16 bits) indicates a destination UDP port number for a corresponding UDP / IP stream component (component_destination_UDP_port_num: A 16-bit unsigned integer field, that represents the destination UDP port number for this UDP / IP stream component).
  • a num_component_level_descriptors field (4 bits) indicates the number of descriptors that provide additional information of the component level.
  • the component_level_descriptor () is included in the component loop as many as the number corresponding to the num_component_level_descriptors field value, thereby providing additional information about the component.
  • a num_NRT_service_level_descriptors field (4 bits) indicates the number of descriptors that provide additional information of the NRT service level.
  • NRT_service_level_descriptor () is included in the NRT service loop as many as the number corresponding to the num_NRT_service_level_descriptors field value, thereby providing additional information about the NRT service.
  • the num_virtual_channel_level_descriptors field (4 bits) is the number of descriptors that provide additional information of the virtual channel level.
  • virtual_channel_level_descriptor () is included in the virtual channel loop to provide additional information about the virtual channel.
  • component_descriptor () is used as one of the component level descriptor_level_descriptors () of the NST, and describes additional signaling information of the component.
  • a descriptor_tag field (8 bits) is a descriptor identifier, and an identifier for identifying component_descriptor () may be set.
  • a descriptor_length field (8 bits) indicates the remaining length of the descriptor in byte units from the descriptor_length field to the end of this descriptor.
  • a component_type field (7 bits) indicates a value for identifying an encoding format of a component.
  • the identification value may be one of values assigned for payload_type of the RTP / AVP stream. Or it may be one of the values predetermined by the appointment of the transmitting / receiving side, or may be a dynamic value between 96-127.
  • the value of the component_type field must match the value in payload_type in the RTP header of the IP stream carrying the component (component_type: This 7-bit field shall identify the encoding format of the component.
  • the value may be any of the values assigned by IANA for the payload_type of an RTP / AVP stream, or it may be any of the values assigned by ATSC, or it may be a “dynamic value” in the range 96-127
  • the value of this field shall match the value in the payload_type field in the RTP header of the IP stream carrying this component.Note that additional values of the component_type field in the range of 43-71 can be defined in future versions of this standard).
  • a component_encryption_flag field (1 bit) indicates presence or absence of encryption of the corresponding component.
  • a num_STKM_streams field (8 bits) indicates the number of STKM streams associated with the component when the component_encryption_flag field indicates encryption (num_STKM_streams: An 8-bit unsigned integer field that shall identify the number of STKM streams associated with this component).
  • An STKM_stream_id field (8 bits) indicates a value for identifying a SKTM stream which can be repeated by the value of the Num_STKM_streams field to obtain a key required for decryption.
  • the NRT_component_data (component_type) field provides encoding parameters and / or other parameters necessary for rendering the component.
  • the structure of the component_data element is determined by the value of the component_type field (component_data (component_type):
  • the component_data () element provides the encoding parameters and / or other parameters necessary for rendering this component.
  • the structure of the component_data is determined by the value of component_type field).
  • the component_data (component_type) field provides component data for an H.264 / AVC video stream.
  • the component_data (component_type) field provides data for FLUTE file delivery as shown in FIG.
  • One NRT service may be included in multiple FLUTE sessions. That is, one NRT service may be composed of a plurality of FLUTE sessions. Each FLUTE session may be signaled using NRT_component_data () of FIG. 13.
  • NRT_component_data () that provides data for FLUTE file delivery according to the present invention.
  • Description of each field of the NRT_component_data () is as follows.
  • the TSI field (16 bits) indicates the TSI of the FLUTE session. That is, the TSI is an identifier capable of uniquely identifying a FLUTE session (A 16-bit unsigned integer field, which shall be the Transport Session Identifier (TSI) of FLUTE session).
  • TSI Transport Session Identifier
  • a session_start_time field (16 bits) indicates the time at which the FLUTE session starts. If the values of the corresponding fields are all '0', the FLUTE session may be interpreted as already started.
  • a session_end_time field (16 bits) indicates the time when the FLUTE session ends. If all of the values of the corresponding fields are '0', the FLUTE session may be interpreted to continue indefinitely.
  • a tias_bandwidth_indicator field (1 bit) indicates whether TIAS (Transport Independent Application Specific) bandwidth information is included. If the TIAS bandwidth field is indicated to exist, the bit must be set to '1', and if the TIAS bandwidth field is indicated to not exist, the bit must be set to '0' (A 1-bit field that flags the inclusion of TIAS bandwidth information.This bit shall be set to '1' to indicate the TIAS bandwidth field is present, and it shall be set to '0' to indicate the TIAS bandwidth field is absent).
  • TIAS Transport Independent Application Specific
  • An as_bandwidth_indicator field (1 bit) indicates whether or not Application Specific (AS) bandwidth information is included. If the AS bandwidth field is present, the corresponding bit must be set to '1'. If the AS bandwidth field is indicated that it is not present, this bit must be set to '0' (A 1-bit field that flags). the inclusion of AS bandwidth information.This bit shall be set to '1' to indicate the AS bandwidth field is present, and it shall be set to '0' to indicate the AS bandwidth field is absent).
  • AS Application Specific
  • An FEC_OTI_indicator field (1 bit) indicates whether or not the FEC object transmission information (OTI) is provided (A 1-bit indicator that indicates whether FEC Object Transmission Information is provided).
  • a tias_bandwidth field (16 bits) is present when the as_bandwidth_indicator field is set to '1' and indicates a TIAS maximum bandwidth (This value shall be one one-thousandth of the Transport Independent Application Specific maximum bandwidth as defined in RFC 3890, rounded up to the next highest integer if necessary.This gives the TIAS bandwidth in kilobits per second).
  • An as_bandwidth field (16 bits) is present when the as_bandwidth_indicator field is set to '1' and indicates an AS maximum bandwidth (This value shall be the Application Specific maximum bandwidth as defined in RFC 4566. This gives the AS bandwidth in kilobits per second).
  • the FEC_encoding_id field exists when the FEC_OTI_indicator field is set to '1' and indicates an FEC encoding ID used in the FLUTE session (FEC encoding ID used in this FLUTE session, as defined in RFC 3926).
  • the FEC_instance_id field exists when the FEC_OTI_indicator field is set to '1' and indicates an FEC instance ID used in the FLUTE session (FEC instance ID used in this FLUTE session, as defined in RFC 3926).
  • files constituting the NRT service by opening the corresponding FLUTE session according to the time information set by the session_start_time field and the session_end_time field, and a FDT (File Description Table) describing signaling information of the files may be received.
  • the FDT is used to convey lists of all content items and also provides the information needed to obtain the content item and the files contained in the content item.
  • the FDT includes a file ID for uniquely distinguishing files included in a content item and an instance ID for uniquely identifying the FDT.
  • a content linkage for identifying the corresponding content item is allocated for each file level or instance level of the FDT.
  • each file constituting a content item is identified using the content linkage, TOI and Content-Location fields specified in the FDT within the FLUTE session.
  • the content linkage, TOI and Content-Location fields are called file identifiers.
  • One NRT service according to the present invention includes one or more content items (or content, or NRT content) as shown in FIG. 2, and one content item includes one or more files.
  • the content item may not be updated, may be updated at regular time intervals, or may be updated very frequently.
  • a content item called economic news may no longer be serviced after it has been serviced once, may be updated every 2-3 hours, or may be updated frequently at 1-2 second intervals.
  • the updated content item means that at least one file has been added to the content item, at least one of the files belonging to the content item has been deleted, and / or the content of the currently existing file has been changed.
  • the NRT service identifier and content identifier eg, content linkage information
  • the same content may be periodically transmitted and update may occur.
  • the broadcast receiver may not know when the content item is updated. Accordingly, the broadcast receiver should always open (or join) the FLUTE session in which the content item is transmitted to continuously monitor the FDT included in the FLUTE session. For example, it is necessary to continuously monitor whether the file identifier and the instance identifier of the FDT are changed.
  • the present invention is to provide a broadcast receiver with update information of a content item.
  • the broadcast receiver according to the present invention opens the corresponding FLUTE session and configures the files composing the content item based on the FDT included in the FLUTE session only when the update information of the content item indicates that the corresponding content item has been updated.
  • Receive In this case, all files constituting the content item may be received, or only updated files may be received.
  • the updated file also corresponds to a file added to the content item.
  • the update information of the content item may be included in an existing table, for example, an NRT-IT, or may be included in a newly defined table.
  • a newly defined table will be referred to as a content version table (CVT).
  • CVT content version table
  • the NRT-IT, NST, CVT, etc. may be referred to as a signaling information table.
  • Update information of the content item may be included in the NRT-IT or CVT in the form of a field or in the form of a descriptor.
  • the present invention is included in the form of a field.
  • the update information of the content item according to the present invention includes information indicating the version number of the corresponding content item.
  • this field will be referred to as a content_version_number field.
  • the content_version_number field value is changed. Yes.
  • the update information of the content item according to the present invention may further include information for distinguishing whether the corresponding content item is rapidly or at a high rate updated content item or content updated at regular intervals. In other words, it is more effective to continuously update content items (e.g., 2-3 seconds intervals) that are updated quickly by always opening the corresponding FLUTE session.
  • this field will be referred to as a content_version_available field.
  • the content_version_available field corresponding to a quickly (or very frequently) updated content item among the updated content items is set to 0, and the content_version_available field corresponding to the content item that is not updated is set to 1 according to an embodiment. .
  • an update time period for distinguishing between a quickly updated content item and an otherwise unsatisfied content item is determined in advance by a broadcasting station. For example, it may be determined that a content item that is updated in a cycle of 10 minutes or less is a content item that is quickly updated.
  • NRT Information Table (NRT-IT)
  • FIG. 14 and 15 illustrate an embodiment of a bit stream syntax structure for an NRT-IT section including update information of a content item according to the present invention.
  • bit stream syntax of the NRT-IT section is written in the form of MPEG-2 private section to facilitate understanding, but the format of the data may be in any form.
  • other methods such as signaling in the form of a Session Description Protocol (SDP) and signaling through a Session Announcement Protocol (SAP) may be used.
  • SDP Session Description Protocol
  • SAP Session Announcement Protocol
  • the NRT-IT includes information describing a downloadable content item in order to store the content item in the broadcast receiver.
  • the information provided in the NRT_IT includes the title of the content
  • One item of content may consist of one or more files.
  • an audio / video clip may come with a JPEG thumbnail image that can be used to represent it in on-screen displays.
  • the NRT-IT is used to provide information for virtual channels of service_type values 0x08.
  • An instance of the NRT-IT can include data corresponding to an arbitrarily defined time period, or can describe NRT content starting at a specified time and into the indefinite future.
  • Each NRT-IT instance indicates the start time of the period it covers and the length of the period it covers (which may be indefinite).
  • Each NRT-IT instance may be segmented into as many as 256 sections. One section may contain information for multiple content items, but the information for any given content item shall not be segmented and put into two or more sections.
  • any content item to be made available for download for a time interval that extends beyond the time period covered one or more NRT-IT instances shall be described only in the first of these NRT-ITs.
  • Content item descriptions are placed within the NRT_information_table_section () in the order of their first availability. Therefore, when last_section_number is greater than zero (meaning the NRT-IT is delivered in multiple sections), for sections other than the first (sections for which the value of section_number is greater than zero), all the content item descriptions within a given section shall have first availability times that are greater than or equal to all first availability times of content item descriptions in the immediately preceding section (the section whose value of section_number is one lower than the given section).
  • Each NRT-IT identifies NRT services associated with the given value of service_id available on a particular virtual channel sometime during the time period it covers.
  • NRT-IT whether one NRT-IT consists of one section or a plurality of sections may be known through a table_id field, a section_number field, a last_section_number field, and the like in the NRT-IT section.
  • a corresponding table After removing the IP header and the UDP header of the IP datagrams of the NRT service signaling channel and collecting sections having the same table identifier, a corresponding table may be completed. For example, collecting sections with table identifiers assigned to the NRT-IT can complete the NRT-IT.
  • table_id field (8-bit) is set to 0xTBD to identify this table section as belonging to the Non-Real-Time Information Table.
  • service_id field (16-bit) specifies the service_id field associated with the NRT service offering content items described in this section.
  • NRT_IT_version_number field (5-bit) indicates the version number of this NRT-IT instance, where NRT-IT instance is defined as the set of one or more NRT_information_table_section () having common values for service_id field, current_next_indicator field, protocol_version field, and time_span_start field.
  • the version number is incremented by 1 modulo 32 when any field in the NRT-IT instance changes.
  • current_next_indicator (1-bit) field is always set to ‘1’ for NRT-IT sections; the NRT-IT sent is always currently applicable.
  • protocol_version field (8-bit) is set to zero.
  • the function of protocol_version field is to allow, in the future, this table type to carry parameters that may be structured differently than those defined in the current protocol. At present, the only valid value for protocol_version field is zero. Non-zero values of protocol_version field may be used by a future version of this standard to indicate structurally different tables.
  • time_span_start field (32-bit) represents the start of the time span covered by this instance of the NRT-IT, expressed as the number of GPS seconds since 00:00:00 UTC, January 6, 1980.
  • the time of day of time_span_start field is aligned to minute 00 of the hour.
  • the value zero for time_span_start field indicates the time period covered by his NRT-IT instance began in the indefinite past.
  • the value of time_span_start field is the same for each section of a multi-sectioned NRT-IT instance.
  • the values of time_span_start field and time_span_length field are set such that the specified time span does not overlap with any other NRT-IT instance in this IP subnet.
  • time_span_length field (11-bit) indicates the number of minutes, starting at the time indicated by time_span_start field, covered by this instance of the NRT-IT. Once established, the value of time_span_length field for a given value of time_span_start field does not change. A value of time_span_length field of zero means this NRT-IT instance covers all time starting at time_span_start field into the indefinite future. If the value of time_span_start is zero, time_span_length field has no meaning. The value of time_span_length field is the same for each section of a multi-sectioned NRT-IT instance. The values of time_span_start field and time_span length field are set such that the specified time span does not overlap with any other NRT-IT instance in this IP subnet.
  • num_items_in_section field (8-bit) indicates the number of content items described in this NRT-IT section.
  • a 'for' loop (or a content item loop) is performed as many as the number of content items corresponding to the num_items_in_section field value to provide signaling information for a plurality of content items. That is, signaling information of the corresponding content item is displayed for each content item included in the NRT service corresponding to the service_id field value. In this case, the following field information may be provided for each content item.
  • the content_linkage field (32-bit) in the range 0x0001 to 0xFFFF specifies the identification number of the content (or content item) described. Value 0x0000 is not used.
  • the content_linkage field performs two linkage functions: it links metadata in the NRT-IT to one or more files in the FLUTE FDT associated with this NRT service; it also forms the TF_id field (identifier for Text Fragment in Text Fragment Table).
  • the value of the content_linkage field corresponds to either the value of one of the FDT-Content-Linkage elements or the value of one of the File-Content-Linkage elements in the FLUTE FDT for each file associated with the content item.
  • the precedence rules may be applied when matching each content_linkage value with the corresponding content linkage elements in the FLUTE FDT.
  • An update_available field (1 bit) indicates whether a corresponding content item is an updated content item. For example, if the content item is a content item included in an NRT service that is serviced and terminated once, an update_available field value is set to '0'. If the content item is a content item that is updated more than once, the updates_available field value is set to '1'. That is, this field specifies, when set to ‘1’, that the referenced content item (s) will be updated. When the updates_available field is set to ‘0’, updates are not expected to be provided for the associated content item (s), and broadcast receivers are not expected to look for them.
  • content_version_available-A 1-bit field that indicates whether content version number is included in the current section of NRT-IT .
  • the content_version_available field value is '1', the content_version_number field is included in the current content item loop, and if the content_version_available field value is '0', the content_version_number field is not included in the current content item loop.
  • the corresponding content item loop does not include the content_version_number field even though the updates_available field value is '1'.
  • the updates_available field value is '1' and the content_version_available field value is '0'.
  • the FLUTE session for transmitting the content item is always or joined, and the FDT included in the FLUTE session is continuously monitored.
  • the content item loop includes a content_version_number field.
  • the updates_available field value and the content_version_available field value are both '1'.
  • the FLUTE session for transmitting the corresponding content item is opened or downloaded, and the files of the corresponding content item are downloaded with reference to the FDT included in the FLUTE session.
  • TF_available field is Boolean flag, this field specifies, when set to ‘1’ that a Text Fragment is present in a Text Fragment Table in the service signaling channel. When the field is set to ‘0’, no Text Fragment is included in the service signaling channel for this content item.
  • low_latency field is Boolean flag, this field specifies, when set to ‘1’, that the content is available within the current digital transport with a low enough latency that its retrieval should be attempted while the user waits. When the field is set to ‘0’, retrieval latency is longer and the user interface should suggest to the user to return later for viewing.
  • playback_length_in_seconds field (20-bit) specifies the duration of playback of the content, in seconds. For content consisting only of text and / or still images, the value zero is used. For content that includes audio or audio / video content, the playback_length_in_seconds field indicates the playback length of the audio or audio / video content.
  • content_version_number field (32-bit) indicates the version of the content item identified by the content_linkage field. The value of this field is incremented whenever one or more files belonging to the content item are added, deleted or updated.
  • the content_version_number field is present when the content_version_available field value is '1', and is not present when '0'.
  • the content_version_number field is the most recent version number of the corresponding content item. At this time, to confirm whether the content item has been updated, it is to be compared with the immediately previous version number of the corresponding content item. To this end, the present invention stores the content_linkage field value for identifying the content item and the content_version_number field value immediately before the content item identified by the content_linkage field value.
  • the broadcast receiver of the present invention can detect a change in the FLUTE session of the corresponding content item by using the updates_available field, the content_version_available field, and the content_version_number field of the current content item loop. That is, the update_available field may be used to determine whether the corresponding content item is updated. The content_version_available field may be used to determine whether the corresponding content item is updated quickly. In addition, by using the content_version_number field, it is possible to know whether a change has occurred in files belonging to the corresponding content item.
  • update_available field value is '0'
  • updates_available field is '0'
  • the broadcast receiver when the updates_available field value is '1' and the content_version_available field value is '0', this means that the corresponding content item is updated too frequently.
  • the broadcast receiver must check the FDT instances by joining the corresponding FLUTE session to check if there is a change in the NRT service (When updates_available field is '1' and content_version_available field is '0', the implication is that the contents are being updated too frequently to be signaled properly by NRT-IT.In this case, the broadcast receiver has to join the FLUTE session and check the FDT instances to find out what has changed in the NRT service of interest.). That is, it is detected whether a change occurs in the FLUTE session of the corresponding content item at the FLUTE session level.
  • the broadcast receiver detects whether a change has occurred in the FLUTE session of the corresponding content item at the IP level. For example, if the content_version_number field value of the corresponding content item has changed, it is determined that the corresponding content item has been updated. Only in this case, it joins the corresponding FLUTE session and checks the FDT instances included in the FLUTE session. As a result of the check, if the files of the content item have been changed, the files constituting the content item are downloaded.
  • the receiver can detect that the changes have occurred in the FLUTE session. If the receiver sees that the version number of a content item has changed, it can join the FLUTE session, check the FDT instances, and see which files of that content item have changed new files added, previous files deleted, and / or new versions of existing files.). In this case, new files of the files added to the content item and existing files are downloaded (Then it only has to download the new files and the new versions of existing files.). In practice, this means it just needs to download any files with new TOI values for that content item. It can check the Content-Location field of each such file to see whether it is a new file or an update to an existing file.
  • content_length_included field is Boolean flag, this field indicates, when set to ‘1’, that the content_length field is present in this iteration of the “for” loop. Setting this field to ‘0’ indicates the content_length field is not present in this iteration of the “for” loop.
  • playback_delay_included field is Boolean flag, this field indicates, when set to ‘1’, that the playback_delay field is present in this iteration of the “for” loop. Setting this field to ‘0’ indicates the playback_delay field is not present in this iteration of the “for” loop.
  • expiration_included field is Boolean flag, this field indicates, when set to ‘1’, that the expiration field is present in this iteration of the “for” loop. Setting this field to ‘0’ indicates the expiration field is not present in this iteration of the “for” loop.
  • duration field (12-bit) in the range 1 to 2880 specifies the expected cycle time, in minutes, of the carousel containing the referenced content item.
  • a broadcast receiver is expected to use the duration parameter to determine the amount of time needed to capture the referenced content.
  • content_length field (40-bit), when present, represents the total size in bytes of the content item or items. This item is used by the broadcast receiver to determine if enough memory is available to store it before downloading is attempted.
  • playback_delay field (20-bit) counts of the number of seconds following reception of the first byte of the associated content the broadcast receiver waits before playback may start, while buffering the incoming stream. A value of zero indicates playback may commence immediately.
  • playback_delay field is not provided, the broadcast receiver is expected to retrieve the complete file or file set prior to playback.
  • expiration field (32-bit) represents the expiration time of the content, expressed as the number of GPS seconds since 00:00:00 UTC, January 6, 1980. Following expiration, the content is deleted from memory. If an expiration time is not specified, broadcast receivers are expected to use methods of their own choosing to manage memory resources.
  • content_name_length field (8-bit) specifies the length (in bytes) of the content_name_text ().
  • content_name_text () field specifies the content item title in the format of a multiple string structure.
  • content_descriptors_length field (12-bit) indicates the total length (in bytes) of the content_descriptor ().
  • content_descriptor () is separately applied to each content item.
  • descriptors_length field (10-bit) indicates the total length (in bytes) of the descriptor ().
  • descriptor () is commonly applied to all content items described in the current NRT-IT section.
  • FIG. 16 is a flowchart summarizing a process of checking and processing an update of a content item using the NRT-IT sections of FIGS. 14 and 15. That is, IP / UDP packets related to the NRT service signaling channel are parsed (S1201). An NRT-IT is obtained from the parsed IP / UDP packets and analyzed for each field (S1202).
  • IP datagrams of NST and NRT-IT included in the NRT service signaling channel have the same well-known IP address and well-known UDP port number. Therefore, the classification of the NRT-IT included in the NRT service signaling channel is made by a table identifier.
  • Subsequent processes are performed separately for the content items included in the NRT-IT section. That is, by checking whether the update_available field value is '0' with respect to the corresponding content item (S1203), if the content item is '0', there is no update of the corresponding content item, and therefore, whether to update the corresponding content item is not checked (S1204).
  • the update_available field value is '1' in S1203, it is checked whether the content_version_available field value is '0' (S1205). If the content_version_available field value is '0', this means that the content item is updated too often. In this case, in order to check whether there is a change in the NRT service, the FUTE instance is continuously monitored by accessing the corresponding FLUTE session (S1206). If the file identifier or the instance identifier of the FDT is changed during the monitoring, it is determined that the corresponding content item has been updated, and the files included in the content item are downloaded (S1207). That is, when the updates_available field value is '1' and the content_version_available field value is '0', the update of the corresponding content item is determined using FDT instances.
  • both of the updates_available field value and the content_version_available field value are determined to be '1', the previously stored previous content version number of the corresponding content item is compared with a content version number included in the NRT-IT (S1208). ). If the two content version numbers are different, it is determined that the corresponding content item has been updated. Only in this case, the FLUTE session is accessed and the files of the content item are downloaded based on the FDT included in the FLUTE session (S1209). That is, when both the updates_available field value and the content_version_available field value are '1', the update of the corresponding content item is determined using the NRT-IT.
  • the update information of the content item according to the present invention may be included in the form of a field or a descriptor in the CVT instead of the NRT-IT.
  • the present invention is included in the form of a field.
  • the reserved field is allocated to the content_version_available field position in the NRT-ITs of FIGS. 14 and 15, and the content_version_number field is not allocated.
  • 17 is a diagram illustrating an embodiment of a bit stream syntax structure for a CVT section including update information of a content item according to the present invention.
  • bit stream syntax of the CVT section according to the present invention is written in the form of MPEG-2 private section to facilitate understanding, but the format of the data may be in any form.
  • other methods such as signaling in the form of a Session Description Protocol (SDP) and signaling through a Session Announcement Protocol (SAP) may be used.
  • SDP Session Description Protocol
  • SAP Session Announcement Protocol
  • one CVT consists of one section or a plurality of sections may be known through a table_id field, a section_number field, a last_section_number field, and the like in the CVT section.
  • a table_id field (8 bits) is a unique identifier of a table and indicates a value indicating that the table to which this section belongs is a CVT.
  • a section_syntax_indicator field (1 bit) is an indicator defining a section format of a CVT.
  • the private_indicator field (1 bit) indicates whether the corresponding CVT follows the private section.
  • a section_length field (12 bits) indicates the section length of the CVT.
  • service_id field (16-bit) specifies the service_id field associated with the NRT service offering content items described in this section.
  • the CVT_version_number field (5 bits) indicates the version number of the CVT.
  • a current_next_indicator field (1 bit) indicates whether information included in the corresponding CVT section is applicable information currently or in the future.
  • a section_number field (8 bits) indicates the section number of the current CVT section.
  • the last_section_number field (8 bits) indicates the last section number of the CVT.
  • the CVT_protocol_version field (8 bits) tells the protocol version to allow CVT to transfer parameters with different structures than those defined in the current protocol (An 8-bit unsigned integer field whose function is to allow, in the future, this CVT to carry parameters that may be structured differently than those defined in the current protocol.At present, the value for the CVT_protocol_version shall be zero.Non-zero values of CVT_protocol_version may be used by a future version of this standard to indicate structurally different tables.)
  • a num_items_in_section field (8 bits) indicates the number of content items in the CVT section.
  • a 'for' loop (or a content item loop) is performed as many as the number of content items corresponding to the num_items_in_section field value to provide version information for the plurality of content items. That is, version information of the corresponding content item is provided for each content item included in the CVT section. In this case, the following field information may be provided for each content item.
  • the content_linkage field (16-bit) in the range 0x0001 to 0xFFFF specifies the identification number of the content (or content item) described. Value 0x0000 is not used.
  • the content_linkage field links metadata in the CVT to one or more files in the FLUTE FDT associated with this NRT service.
  • the value of the content_linkage field corresponds to either the value of one of the FDT-Content-Linkage elements or the value of one of the File-Content-Linkage elements in the FLUTE FDT for each file associated with the content item.
  • the precedence rules may be applied when matching each content_linkage value with the corresponding content linkage elements in the FLUTE FDT.
  • content_version_number field (32-bit) indicates the version of the content item identified by the content_linkage field. The value of this field shall be incremented whenever one or more files belonging to the content item are added, deleted or updated.
  • the CVT according to the present invention does not include update information of content items that are not updated.
  • the CVT would not contain content items that are never updated, nor content items that are constantly updated at a high rate. More specifically, for fixed broadcasts, the CVT will contain the content items that are in the instance of the NRT-IT covering the current time, except for those for which updates_available is false and those that are constantly updated at a high rate.
  • the updates_available field of the NRT-IT can be used to distinguish the above two cases.
  • the NRT service identified by the service_id field in the NRT-IT includes content item 1, content item 2, content item 3, and content item 4. And suppose that content item 1 is updated too often (or quickly), content item 2 and content item 4 are updated but not too often, and content item 3 has no update.
  • the updates_available field value in the content item loop corresponding to the content items 1,2 and 4 in the NRT-IT is '1'
  • the updates_available field value in the content item loop corresponding to the content item 3 is '0'
  • the CVT includes only the update information of the content item 2 and the content item 4.
  • the broadcast receiver does not confirm the update of the content item 3.
  • the broadcast receiver should always open the FLUTE session for transmitting the content item 1 and continuously monitor the FDT included in the FLUTE session to confirm whether the content item 1 has been updated. If the update is confirmed during monitoring, the updated file is downloaded with reference to the FDT.
  • the broadcast receiver checks whether the corresponding content item is updated by using a content_linkage field and a content_version_number field in each content item loop of the CVT. Only when the update is confirmed, a join is made to the corresponding FLUTE session, and the file added or updated to the content item is found and downloaded based on the FDT instance included in the FLUTE session.
  • the present invention stores the content_linkage field value for identifying the content item and the content_version_number field value immediately before the content item identified by the content_linkage field value.
  • the CVT is included in the NRT service signaling channel and received according to an embodiment.
  • the CVT, NRT-IT, and NST have the same well-known IP address and well-known UDP port number.
  • the NRT service signaling channel may be received without additional IP access information.
  • the CVT included in the NRT service signaling data is determined by a table identifier. That is, the table identifier may be table_id existing in the header of the table or the table section, and may be distinguished by further referring to table_id_extension if necessary.
  • the CVT may be received by packetizing an IP packet with a well-known IP address and a well-known UDP port number different from a well-known IP address and a well-known UDP port number of the NRT service signaling channel. Can be.
  • the CVT may be received without additional IP access information.
  • the IP address of the CVT and the UDP port number may be included in another table, for example, NST.
  • NST another table
  • a CVT is obtained using an IP address and a UDP port number included in the NST.
  • FIG. 18 is a flowchart illustrating a process of checking and processing an update of a content item using the CVT when the CVT is included in the NRT service signaling channel and received.
  • IP / UDP packets related to the NRT service signaling channel are parsed (S1301).
  • a CVT section is obtained from the parsed IP / UDP packets and the fields are analyzed (S1302).
  • the subsequent steps are performed separately for the content items included in the CVT section. That is, the previously stored previous content version number of the corresponding content item is compared with the content version number included in the CVT section (S1303). If the two content version numbers are different, it is determined that the corresponding content item has been updated. Only in this case, the FLUTE session is accessed to download files of the content item based on the FDT included in the FLUTE session (S1304). That is, the update of the corresponding content item is determined using the CVT.
  • FIG. 19 illustrates an embodiment of a bit stream syntax structure of a CVT location descriptor CVT_location_descriptor () according to the present invention.
  • this corresponds to a case where a well-known IP address and a well-known UDP port number are not used without transmitting a CVT through an NRT service signaling channel.
  • CVT_location_descriptor () is transmitted as one of the service level descriptor service_level_descriptors () of the NST of FIGS. 10 and 11.
  • a descriptor_tag field (8 bits) is a descriptor identifier, and an identifier for identifying a CVT location descriptor CVT_location_descriptor () may be set.
  • a descriptor_length field (8 bits) indicates the remaining length of the descriptor in byte units from the descriptor_length field to the end of this descriptor.
  • a CVT_UDP_port field (16 bits) indicates the UDP port number of the UDP / IP stream for transmitting the CVT.
  • the CVT_IP_address field (32 or 128 bits) indicates the IP address of the IP datagrams carrying the CVT.
  • the CVT_IP_address field value may be 32 bits or 128 bits depending on the IP version (ie, IPv4 or IPv6).
  • FIG. 20 receives the CVT IP address and the UDP port number from the NST, receives the CVT from the NST, and receives the CVT using the received CVT as shown in FIG. 19.
  • This is a flow chart illustrating the process of checking for and processing an update of a content item.
  • NST is obtained by parsing IP / UDP packets related to the NRT service signaling channel (S1401).
  • IP access information of the CVT section that is, the IP address and the UDP port number are extracted from the obtained NST (S1402), and the CVT is received based on the extracted IP address and the UDP port number, and the respective fields are analyzed (S1403).
  • the subsequent steps are performed separately for the content items included in the CVT section. That is, the previously stored previous content version number of the corresponding content item is compared with a content version number included in the CVT section (S1404). If the two content version numbers are different, it is determined that the corresponding content item has been updated. Only in this case, the FLUTE session is accessed to download files of the content item based on the FDT included in the FLUTE session (S1405). That is, the update of the corresponding content item is determined using the CVT.
  • the present invention should be applicable to Mobile NRT service.
  • the signaling information table for the mobile NRT service includes a service map table (SMT).
  • SMT service map table
  • the SMT provides real-time or non-real-time services included in a mobile broadcast and access information of components (or content items) included in each service.
  • the SMT is a signaling information table corresponding to the NST of the fixed NRT service. If the service included in the mobile broadcast is an NRT service, signaling information including access information of a FLUTE session for transmitting content items / files constituting an NRT service may be extracted from the SMT. Further, detailed information of content items configuring the NRT service may be extracted from OMA BCAST Service Guide (SG) information. That is, signaling for the mobile NRT service uses an SMT (Service Map Table) and an OMA BCAST SG according to an embodiment.
  • SMT Service Map Table
  • OMA BCAST SG OMA BCAST Service Guide
  • the Mobile NRT service allocates an “UpdatesAvailable” element, which is a Boolean-valued, to the PrivateExt area of the SG content fragment of OMA BCAST.
  • the "UpdatesAvailable” element has the same semantics as the updates_available field of the Fixed NRT service.
  • the update information of the content item may be included in the SG content fragment of OMA BCAST or may be included in the CVT according to the present invention.
  • FIG. 21 shows an example of allocating an "UpdatesAvailable” element to an SG content fragment of OMA BCAST according to the present invention. That is, the "UpdatesAvailable” element is included in the PrivateExt area of the SG content fragment.
  • the "UpdatesAvailable” element is represented by UpdatesAvailableType.
  • the UpdatesAvailableType is a restriction base of boolean.
  • the UpdatesAvailableType has an UpdatesAvailableType as a simpleType name.
  • the CVT may be included in the NRT service signaling channel for the mobile NRT service.
  • the CVT and the SMT have the same well-known IP address and the well-known UDP port number.
  • the CVT may be received in an IP packetized manner with a well-known IP address and a well-known UDP port number different from a well-known IP address and a well-known UDP port number of the NRT service signaling channel.
  • the IP address and the UDP port number of the CVT may be received as the service level descriptor of the SMT.
  • a CVT is obtained using an IP address and a UDP port number included in the SMT.
  • the CVT will contain the content items for which the current time lies within a DistributionWindow of the Content fragment in a Schedule, except for those for which UpdatesAvailable is false and those that are constantly updated at a high rate.
  • a new version of a content item Whenever a new version of a content item is to be transmitted, it will be signaled by a new version of the CVT.
  • the new CVT version will appear after the last transmission of the previous version of the content item is completed, and before the first transmission of the new version of the content item is started.
  • FIG. 22 is a block diagram illustrating an embodiment of a broadcast receiver for a fixed NRT service according to the present invention.
  • the broadcast receiver of FIG. 22 includes an operation controller 100, a baseband processor 110, a service demultiplexer 120, a stream component handler 130, a media handler 140, a file handler 150, and a service manager 160. , PVR manager 170, first storage unit 180, SG handler 190, EPG handler 200, NRT service manager 210, application manager 220, middleware engine 230, presentation manager ( 240, and a UI manager 250.
  • the baseband processor 110 may include a tuner 111 and a demodulator 112.
  • the service demultiplexer 120 uses the MPEG-2 TP handler 121, the PSI / PSIP handler 122, the MPEG-2 TP demultiplexer 123, the descrambler 124, and the second storage unit 125. It may include.
  • the stream component handler 130 may include a packetized elementary stream (PES) decoder 131, an elementary stream (ES) decoder 132, a PCR handler 133, an STC handler 134, and a DSM-CC addressable section handler ( 135), IP datagram handler 136, descrambler 137, UDP handler 138, service signaling section handler 138-1, and CAS (Conditional Access System 139).
  • PES packetized elementary stream
  • the media handler 140 may include an A / V decoder 141.
  • the file handler 150 may include an ALC / LCT stream handler 151, a file reconstruction buffer 152, an XML parser 153, an FDT handler 154, a decompressor 155, and a third storage unit ( 156, and file decoder 157.
  • the first processing unit for receiving and processing the NST, NRT-IT, and CVT includes at least a service manager 160 and a service demultiplexer 120.
  • the second processing unit for receiving a non-real time content item including at least one file in a storage medium may include at least the baseband processing unit 110, the service demultiplexer 120, the stream component handler 130, and the media handler. 140.
  • the storage medium may be any one of the first to third storage units.
  • a third processing unit for checking whether the content is updated and accessing a flute session for transmitting the content to receive at least one file of the updated content includes at least a service manager 160 and an NRT service manager 210. ), Stream component handler 3130, and media handler 140.
  • the tuner 111 tunes a broadcast signal of a desired channel among broadcast signals received through terrestrial waves, for example, by controlling the service manager 160 to generate an intermediate frequency (IF) signal. Down conversion is performed to the demodulator 112.
  • the tuner 111 may receive a real time stream and a non real time stream. In the present invention, the non-real time stream will be referred to as an NRT stream.
  • the demodulator 112 performs automatic gain control, carrier recovery, and timing recovery on the digital IF signal of the passband input from the tuner 111, converts it into a baseband signal, and performs channel equalization. For example, when the broadcast signal is a VSB modulated signal, a VSB demodulation process is performed to perform automatic gain control, carrier recovery, and timing recovery. Data demodulated and channel-equalized by the demodulator 112 is output to the MPEG-2 TP handler 121 in the form of an MPEG-2 Transport Stream (TS) packet.
  • TS MPEG-2 Transport Stream
  • the MPEG-2 Transport Stream Packet (121) handler 121 is composed of an MPEG-2 TP buffer and an MPEG-2 TP parser, and temporarily stores the output of the demodulator 112 and analyzes a TS header. If the output of 112 is a real-time A / V TS packet or an NRT TS packet, the output is output to the demultiplexer 123. If the output of the PSI / PSIP table TS packet is output to the PSI / PSIP handler 122.
  • the PSI / PSIP handler 122 includes a PSI / PSIP section buffer and a PSI / PSIP parser, and temporarily stores TS packets output from the MPEG-2 TP handler 121 and then refers to the TS by referring to a table identifier.
  • the table is restored from the PSI / PSIP section data included in the payload of the packet and parsed.
  • whether a table is composed of one section or a plurality of sections can be known through a table_id field, a section_number field, and a last_section_number field in the corresponding section. Collecting sections with the same table identifier completes the corresponding table.
  • the parsed table information is collected by the service manager 160 and stored in the first storage unit 180.
  • Table information such as VCT, PAT, PMT, DST, etc. according to the present invention is stored in the first storage unit 180 through the above process.
  • the service manager 160 stores the table information in the first storage unit 180 in the form of a service map and guide data.
  • the demultiplexer 123 divides the audio TS packet into a video TS packet and outputs the same to the PES decoder 131. 135). In addition, the demultiplexer 123 outputs the TS packet including the PCR (Program Clock Reference) to the PCR handler 133 and outputs the CAS packet to the CAS 139 if the TS packet includes the CA (Conditional Access) information.
  • the NRT TS packet is divided into a TS packet including NRT service data and a TS packet including an NRT service signaling channel.
  • the TS packet of the NRT service data is assigned a unique PID to identify the NRT service, and the PID of the TS packet including the NRT service signaling channel is extracted using DST and PMT.
  • the demultiplexer 123 outputs the descrambler 124 to the descrambler 124, and the descrambler 124 is required to descramble information from the CAS 139 (eg, scramble). And a control word used for the decode).
  • the demultiplexer 123 stores an A / V packet of a real time input by one of a temporary recording, a scheduled recording, and a time shift in the second storage unit 125.
  • the second storage unit 125 is a mass storage medium and may be, for example, an HDD. Download (ie, storage) and upload (ie, playback) in the second storage unit 125 are controlled by the PVR manager 170.
  • the demultiplexer 123 divides the audio TS packet and the video TS packet from the A / V TS packet uploaded from the second storage unit 125 and outputs the PTS decoder 131 according to a reproduction request.
  • the demultiplexer 123 is controlled by the service manager 160 and / or the personal Vedeo recorder (PVR) manager 170 for the above-described processing.
  • PVR personal Vedeo recorder
  • the service manager 160 extracts the PID of the DST from the service location descriptor (or the ES loop of the PMT) of the VCT to receive the DST.
  • the NRT service is identified from the received DST, and the PID of the MPEG-2 TS packet including the NRT service signaling channel is extracted using the DST and PMT to receive the identified NRT service.
  • the extracted PID is output to the demultiplexer 123.
  • the demultiplexer 123 outputs MPEG-2 TS packets corresponding to the PID output from the service manager 160 to the addressable section handler 135.
  • the PCR is a time reference value used for time synchronization of the audio ES and the video ES in the A / V decoder 141.
  • the PCR handler 133 restores the PCR included in the payload of the input TS packet and outputs the PCR to the STC handler 134.
  • the STC handler 134 restores the STC (System Time Clock), which becomes the reference clock of the system, from the PCR and outputs the STC (System Time Clock) to the A / V decoder 141.
  • the PES decoder 131 includes a PES buffer and a PES handler.
  • the PES decoder 131 temporarily stores the audio TS packet and the video TS packet, and then removes the TS header from each TS packet to restore the audio PES and the video PES.
  • the reconstructed audio PES and video PES are output to the ES decoder 132.
  • the ES decoder 132 includes an ES buffer and an ES handler.
  • the ES decoder 132 removes each PES header from the audio PES and the video PES and restores the pure data to the audio ES and the video ES.
  • the reconstructed audio ES and video ES are output to the A / V decoder 141.
  • the A / V decoder 141 decodes the audio ES and the video ES with respective decoding algorithms, restores them to a state before compression, and outputs them to the presentation manager 240. At this time, time synchronization is performed when decoding the audio ES and the video ES according to the STC.
  • the audio decoding algorithm may be an AC-3 decoding algorithm, an MPEG 2 audio decoding algorithm, an MPEG 4 audio decoding algorithm, an AAC decoding algorithm, an AAC + decoding algorithm, an HE AAC decoding algorithm, an AAC SBR decoding algorithm, an MPEG surround decoding algorithm, or a BSAC decoding.
  • At least one of the algorithm may be applied, and the video decoding algorithm may apply at least one of an MPEG 2 video decoding algorithm, an MPEG 4 video decoding algorithm, an H.264 decoding algorithm, an SVC decoding algorithm, and a VC-1 decoding algorithm.
  • the CAS 139 is composed of a CA stream buffer and a CA stream handler, and temporarily stores service protection data restored and output from the TS packet output from the MPEG-2 TP handler 121 or the UDP datagram handler 138. Thereafter, information necessary for descrambling (for example, a control word used for scramble) is restored from the stored TS packet or service protection data. That is, an EMM (Entitlement Management Message), an ECM (Entitlement Control Message), etc., included in the payload of the TS packet are extracted, and the extracted EMM, ECM, etc. are analyzed to obtain information necessary for descramble.
  • the ECM may include a control word (CW) used for scramble. In this case, the control word may be encrypted with an authentication key.
  • the EMM may include an authentication key and entitlement information of the corresponding data. Information necessary for descrambling obtained by the CAS 139 is output to the descramblers 124 and 137.
  • the DSM-CC section handler 135 includes a DSM-CC section buffer and a DSM-CC section parser, and temporarily stores TS packets output from the demultiplexer 123 and is included in the payload of the TS packets.
  • the addressable section is restored, the header and the CRC checksum of the addressable section are removed to restore the IP datagram, and then output to the IP datagram handler 136.
  • the IP datagram handler 136 is composed of an IP datagram buffer and an IP datagram parser. After buffering the IP datagram received from the DSM-CC section handler 135, the IP datagram handler 136 stores the header of the buffered IP datagram. After extracting and analyzing the UDP datagram, the UDP datagram is recovered from the payload of the IP datagram and output to the UDP datagram handler 138.
  • the scrambled UDP datagram is descrambled by the descrambler 137 and then output to the UDP datagram handler 138.
  • the descrambler 137 receives information necessary to descramble (eg, a control word used for scramble) from the CAS 139 to descramble the UDP datagram, and then performs a UDP datagram. Output to handler 138.
  • the UDP datagram handler 138 is composed of a UDP datagram buffer and a UDP datagram parser, and buffers UDP datagrams output from the IP datagram handler 136 or the descrambler 137 and then buffers the UDP.
  • the header of the datagram is extracted and analyzed to restore data included in the payload of the UDP datagram. In this case, if the restored data is service protection data, the data is output to the CAS 139, if the NRT service signaling data is output to the service signaling section handler 138-1, and if the NRT service data is output to the ALC / LCT stream handler 151. .
  • the access information of the IP datagram transmitting the NRT service signaling channel is a well-known destination IP address and a well-known destination UDP port number.
  • the IP datagram handler 136 and the UDP datagram handler 138 have a well-known destination IP multicast address and a well-known destination UDP port number, and transmit an NRT service signaling channel.
  • a cast stream, that is, NRT service signaling data is extracted and output to the service signaling section handler 138-1.
  • the service signaling section handler 138-1 includes a service signaling section buffer and a service signaling section parser. From the NRT service signaling data, the NRT- as shown in FIGS. 10 and 11 and the NRT- as shown in FIGS. Restore and parse IT and output it to the service manager 160. Parsing the NST may obtain access information of a FLUTE session for transmitting content items / files constituting an NRT service. If the CVT according to the present invention is received included in the NRT service signaling channel, the service signaling section handler 138-1 restores and parses the CVT as shown in FIG. 17 from the NRT service signaling data to the service manager 160.
  • the IP access information of the CVT is included in the NST and received, the IP from the CVT_location_descripto () of the NST in any one of the service signaling section handler 138-1, the service manager 160, and the NRT service manager 210. Obtain an address and a UDP port number, and receive a CVT based on the UDP port number other than the obtained IP address.
  • Information parsed from the NST, NRT-IT and / or CVT is collected by the service manager 160 and stored in the first storage unit 180.
  • the service manager 160 stores the information extracted from the NST, NRT-IT and / or CVT in the first storage unit 180 in the form of a service map and guide data.
  • the role of the service manager 160 may be performed by the NRT service manager 210. That is, information parsed from the NST, NRT-IT and / or CVT may be collected by the NRT service manager 210 and stored in the first storage unit 180.
  • the service manager 160 or the NRT service manager 210 confirms whether or not each content item included in the NRT service described in the NRT-IT is updated by using NST, NRT-IT and / or CVT. Perform the action according to the result.
  • the ALC / LCT stream handler 151 is composed of an ALC / LCT stream buffer and an ALC / LCT stream parser. After buffering the data of the ALC / LCT structure output from the UDP datagram handler 138, the buffered data Analyze the header and header extension of the ALC / LCT session. As a result of analyzing the header and header extension of the ALC / LCT session, if the data transmitted to the ALC / LCT session is an XML structure, the data is output to the XML parser 153, and if the file structure is a file reconstruction buffer 152 After the temporary storage, the data is output to the file decoder 157 or stored in the third storage unit 156.
  • the ALC / LCT stream handler 151 is controlled by the NRT service manager 210 when data transmitted through the ALC / LCT session is data for an NRT service. In this case, if data transmitted to the ALC / LCT session is compressed, the data is decompressed by the decompressor 155 and then output to at least one of the XML parser 153, the file decoder 157, and the third storage unit 156.
  • the XML parser 153 analyzes the XML data transmitted through the ALC / LCT session, outputs the analyzed data to the FDT handler 154 if the analyzed data is data for a file-based service, and if the data is for service guide, the SG handler. Output to 190.
  • the FDT handler 154 analyzes and processes a file description table of the FLUTE protocol through an ALC / LCT session. If the received file is a file for NRT service, the FDT handler 154 is controlled by the NRT service manager 210.
  • the SG handler 190 collects and analyzes data for a service guide transmitted in an XML structure and outputs the data to the EPG manager 200.
  • the file decoder 157 decodes a file output from the file reconstruction buffer 152 or a file output from the decompressor 155 or a file uploaded from the third storage unit 156 using a predetermined algorithm to decode the middleware engine ( 230, or to the A / V decoder 141.
  • the middleware engine 230 interprets and executes data of a file structure, that is, an application.
  • the application may be output to an output device such as a screen or a speaker through the presentation manager 240.
  • the middleware engine 230 is a Java-based middleware engine.
  • the EPG manager 200 receives the service guide data from the SG handler 190 according to the user's input, converts the service guide data into the display format, and outputs it to the presentation manager 240.
  • the application manager 220 performs overall management on the processing of the application data received in the form of the file or the like.
  • the service manager 160 collects and analyzes PSI / PSIP table data or NRT service signaling data transmitted through an NRT service signaling channel to generate a service map and stores the service map in the first storage unit 125. In addition, the service manager 160 controls access information on the NRT service desired by the user, and controls the tuner 111, the demodulator 112, the IP datagram handler 136, and the like.
  • the operation controller 100 is the service manager 160, PVR manager 170, EPG manager 200, NRT service manager 210, the application manager according to the user's command input through the UI manager 250 ( 220, at least one of the presentation manager 240 is controlled to perform a function according to the user's command.
  • the NRT service manager 210 performs overall management of the NRT service transmitted in the form of content / file through a FLUTE session on the IP layer.
  • the UI manager 250 transmits the user's input to the operation controller 100 through the UI.
  • the presentation manager 240 may include at least one of audio and video data output from the A / V decoder 141, file data output from the middleware engine 230, and service guide data output from the EPG manager 210. And / or to the user via the screen.
  • Embodiments of a method for transmitting and receiving a signal and an apparatus for transmitting and receiving a signal according to the present invention may be used in broadcasting and communication fields.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Architecture (AREA)
  • Civil Engineering (AREA)
  • Structural Engineering (AREA)
  • Physics & Mathematics (AREA)
  • Electromagnetism (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Human Computer Interaction (AREA)
  • Computer Security & Cryptography (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)

Abstract

La présente invention concerne un récepteur de radiodiffusion utilisé pour recevoir un service en temps non réel et un procédé de traitement d'un service transmis en temps non réel. Le procédé comprend les étapes suivantes: la réception et le traitement de premières et de secondes informations de signalisation, lesdites premières informations de signalisation comprenant des informations d'accès à du contenu et les secondes informations de signalisation comprenant des informations de contenu détaillé; le traitement de troisièmes informations de signalisation comprenant des informations d'actualisation de contenu; la réception et le stockage de contenu en temps non réel sur la base des premières et des secondes informations de signalisation, ledit contenu comprenant au moins un fichier; la confirmation de l'état actualisé ou non actualisé du contenu sur la base du contenu des informations actualisées, lesdites informations actualisées étant incluses dans les troisièmes informations de signalisation; et la réception d'au moins un fichier du contenu actualisé par le biais d'un accès à une session FLUTE de transmission du contenu, si l'actualisation du contenu est confirmée.
PCT/KR2009/006794 2008-11-18 2009-11-18 Procédé de traitement d'un service en temps non réel et récepteur de radiodiffusion WO2010058958A2 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
KR1020167021383A KR101727049B1 (ko) 2008-11-18 2009-11-18 비실시간 서비스 처리 방법 및 방송 수신기
KR1020177009361A KR101759958B1 (ko) 2008-11-18 2009-11-18 비실시간 서비스 처리 방법 및 방송 수신기

Applications Claiming Priority (20)

Application Number Priority Date Filing Date Title
US11588808P 2008-11-18 2008-11-18
US61/115,888 2008-11-18
US12118108P 2008-12-09 2008-12-09
US12117808P 2008-12-09 2008-12-09
US61/121,181 2008-12-09
US61/121,178 2008-12-09
US13849408P 2008-12-17 2008-12-17
US61/138,494 2008-12-17
US15398509P 2009-02-20 2009-02-20
US15397309P 2009-02-20 2009-02-20
US61/153,973 2009-02-20
US61/153,985 2009-02-20
US17900509P 2009-05-17 2009-05-17
US61/179,005 2009-05-17
US23613809P 2009-08-23 2009-08-23
US61/236,138 2009-08-23
US23685909P 2009-08-25 2009-08-25
US61/236,859 2009-08-25
US25859609P 2009-11-06 2009-11-06
US61/258,596 2009-11-06

Publications (2)

Publication Number Publication Date
WO2010058958A2 true WO2010058958A2 (fr) 2010-05-27
WO2010058958A3 WO2010058958A3 (fr) 2010-07-29

Family

ID=42198660

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2009/006794 WO2010058958A2 (fr) 2008-11-18 2009-11-18 Procédé de traitement d'un service en temps non réel et récepteur de radiodiffusion

Country Status (3)

Country Link
US (4) US8874683B2 (fr)
KR (3) KR101759958B1 (fr)
WO (1) WO2010058958A2 (fr)

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6554798B1 (en) 1998-08-18 2003-04-29 Medtronic Minimed, Inc. External infusion device with remote programming, bolus estimator and/or vibration alarm capabilities
EP2229879A1 (fr) 1998-10-08 2010-09-22 Medtronic MiniMed, Inc. Système de surveillance par télémesure d'une caractéristique
US8849183B2 (en) * 2007-10-05 2014-09-30 Qualcomm Incorporated Location and time based filtering of broadcast information
US9280778B2 (en) 2008-12-15 2016-03-08 Qualcomm Incorporated Location logging and location and time based filtering
US8782725B2 (en) * 2009-01-15 2014-07-15 Lg Electronics Inc. Method of processing non-real time service and broadcast receiver
US9003450B2 (en) 2009-01-15 2015-04-07 Lg Electronics Inc. Method of processing non-real time service and broadcast receiver
TWI410870B (zh) * 2010-03-26 2013-10-01 Novatek Microelectronics Corp 電腦系統架構
US20110302599A1 (en) 2010-06-07 2011-12-08 Mark Kenneth Eyer TV-Centric Actions in Triggered Declarative Objects
US8898723B2 (en) 2010-08-20 2014-11-25 Sony Corporation Virtual channel declarative script binding
US8893210B2 (en) 2010-08-20 2014-11-18 Sony Corporation Server load balancing for interactive television
US8918801B2 (en) 2010-08-30 2014-12-23 Sony Corporation Transmission apparatus, transmission method, reception apparatus, reception method, program, and broadcasting system
US9485108B2 (en) 2011-03-14 2016-11-01 Qualcomm Incorporated System and apparatus for using multichannel file delivery over unidirectional transport (“FLUTE”) protocol for delivering different classes of files in a broadcast network
US9451401B2 (en) * 2011-05-27 2016-09-20 Qualcomm Incorporated Application transport level location filtering of internet protocol multicast content delivery
US20130282870A1 (en) * 2012-04-18 2013-10-24 Sony Corporation Reception apparatus, reception method, transmission apparatus, transmission method, and program
CA2874714A1 (fr) * 2012-08-15 2014-02-20 Sony Corporation Livraison a large bande d'informations de personnalisation pour des services tv avances
US9781181B2 (en) * 2013-06-17 2017-10-03 Qualcomm Incorporated Multiple file delivery over unidirectional transport protocol sessions for a service
JP2015043484A (ja) * 2013-08-26 2015-03-05 ソニー株式会社 コンテンツ供給装置、コンテンツ供給方法、プログラム、端末装置、およびコンテンツ供給システム
US10110541B2 (en) * 2013-10-17 2018-10-23 International Business Machines Corporation Optimization of posting in social networks using content delivery preferences comprising hashtags that correspond to geography and a content type associated with a desired time window
WO2016067989A1 (fr) * 2014-10-28 2016-05-06 ソニー株式会社 Dispositif de réception, dispositif de transmission, et procédé de traitement de données
US9654755B2 (en) * 2015-01-09 2017-05-16 Vixs Systems, Inc. Dynamic range converter with logarithmic conversion and methods for use therewith
US9860504B2 (en) 2015-01-09 2018-01-02 Vixs Systems, Inc. Color gamut mapper for dynamic range conversion and methods for use therewith
US9589313B2 (en) * 2015-01-09 2017-03-07 Vixs Systems, Inc. Dynamic range converter with pipelined architecture and methods for use therewith
KR102499231B1 (ko) * 2015-04-30 2023-02-13 소니그룹주식회사 수신 장치, 송신 장치 및 데이터 처리 방법
US9936055B2 (en) * 2016-01-27 2018-04-03 Dell Products L.P. Using multicasting to concurrently image multiple client devices
US10187678B2 (en) * 2016-11-17 2019-01-22 Rovi Guides, Inc. Systems and methods for displaying segments of media guidance data
US11159833B2 (en) * 2018-11-23 2021-10-26 Sony Corporation Buffer management for storing files of a received packet stream

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050042377A (ko) * 2003-11-03 2005-05-09 주식회사 이머텍 저속채널의 스트리밍 서비스를 위한 데이터 분할 전송방법 및 시스템
US20060059267A1 (en) * 2004-09-13 2006-03-16 Nokia Corporation System, method, and device for downloading content using a second transport protocol within a generic content download protocol
WO2008084441A1 (fr) * 2007-01-10 2008-07-17 Nokia Corporation Système et procédé pour la mise en oeuvre d'un transfert mbms pendant la distribution d'un téléchargement

Family Cites Families (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7096487B1 (en) * 1999-10-27 2006-08-22 Sedna Patent Services, Llc Apparatus and method for combining realtime and non-realtime encoded content
US7017175B2 (en) * 2001-02-02 2006-03-21 Opentv, Inc. Digital television application protocol for interactive television
US20050238316A1 (en) * 2002-09-19 2005-10-27 Thomson Licensing S,A, Hybrid video on demand using mpeg2 transport
US20050129042A1 (en) * 2003-12-16 2005-06-16 Nokia Corporation System and associated terminal, method and computer program product for controlling memory for storage of content
EP1555808A1 (fr) * 2004-01-19 2005-07-20 Alcatel Système de télécommunication multimédia avec dispositif multimédia polivalant
US8141118B2 (en) * 2004-07-26 2012-03-20 Microsoft Corporation Data broadcasting receiver power management
KR20060082014A (ko) * 2005-01-11 2006-07-14 삼성전자주식회사 매니페스트 파일 자료구조, 이를 이용한 컨텐츠 다운로드방법 및 그 재생장치
CN101180875B (zh) * 2005-01-12 2010-11-03 英维迪技术公司 广播网络资产交付的定向印象模型
US8351363B2 (en) * 2005-04-08 2013-01-08 Qualcomm Incorporated Method and apparatus for enhanced file distribution in multicast or broadcast
US20060293077A1 (en) * 2005-06-27 2006-12-28 Nokia Corporation System, terminal, method, and computer program product for allocating memory for storage of content
US7738863B2 (en) * 2005-08-25 2010-06-15 Nokia Corporation IP datacasting middleware
US7565506B2 (en) * 2005-09-08 2009-07-21 Qualcomm Incorporated Method and apparatus for delivering content based on receivers characteristics
KR20070106325A (ko) * 2006-04-28 2007-11-01 엘지전자 주식회사 디지털 방송 신호와 상기 신호를 처리하는 장치 및 방법
US7992175B2 (en) * 2006-05-15 2011-08-02 The Directv Group, Inc. Methods and apparatus to provide content on demand in content broadcast systems
US8051193B2 (en) * 2006-09-29 2011-11-01 Sap Ag Communications between content and presentation players
EP1944944A1 (fr) * 2007-01-12 2008-07-16 Thomson Licensing Système et procédé de combinaison de modes réversibles
KR101276842B1 (ko) * 2007-02-09 2013-06-18 엘지전자 주식회사 방송 신호 송수신 장치 및 방법
US8181206B2 (en) 2007-02-28 2012-05-15 Time Warner Cable Inc. Personal content server apparatus and methods
KR101328948B1 (ko) * 2007-03-30 2013-11-13 엘지전자 주식회사 방송 신호 처리 방법 및 방송 수신기
US20080301750A1 (en) * 2007-04-13 2008-12-04 Robert Denton Silfvast Networked antenna and transport system unit
KR100958653B1 (ko) * 2007-08-07 2010-05-20 한국전자통신연구원 디지털 방송 송수신 장치 및 방법
US9462020B2 (en) * 2008-01-16 2016-10-04 Qualcomm Incorporated Intelligent client: multiple channel switching over a digital broadcast network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20050042377A (ko) * 2003-11-03 2005-05-09 주식회사 이머텍 저속채널의 스트리밍 서비스를 위한 데이터 분할 전송방법 및 시스템
US20060059267A1 (en) * 2004-09-13 2006-03-16 Nokia Corporation System, method, and device for downloading content using a second transport protocol within a generic content download protocol
WO2006030309A1 (fr) * 2004-09-13 2006-03-23 Nokia Corporation Systeme, procede et dispositif pour telecharger un contenu en utilisant un deuxieme protocole de transport a l'interieur d'un protocole de telechargement de contenu generique
WO2008084441A1 (fr) * 2007-01-10 2008-07-17 Nokia Corporation Système et procédé pour la mise en oeuvre d'un transfert mbms pendant la distribution d'un téléchargement

Also Published As

Publication number Publication date
US20170275875A1 (en) 2017-09-28
US20140366076A1 (en) 2014-12-11
US10676922B2 (en) 2020-06-09
US20100180007A1 (en) 2010-07-15
US8874683B2 (en) 2014-10-28
KR20110112807A (ko) 2011-10-13
US9699498B2 (en) 2017-07-04
KR20170042807A (ko) 2017-04-19
US20140366067A1 (en) 2014-12-11
KR101727049B1 (ko) 2017-04-14
KR101759958B1 (ko) 2017-07-20
KR101647379B1 (ko) 2016-08-10
WO2010058958A3 (fr) 2010-07-29
KR20160095210A (ko) 2016-08-10

Similar Documents

Publication Publication Date Title
WO2010058958A2 (fr) Procédé de traitement d'un service en temps non réel et récepteur de radiodiffusion
WO2010068033A2 (fr) Procédé de traitement de service en temps différé et récepteur de diffusion
WO2010068040A2 (fr) Procédé de traitement de services en temps non réel et récepteur de radiodiffusion
WO2010082783A2 (fr) Procédé de traitement de service en temps non réel et récepteur de diffusion
WO2011049278A1 (fr) Procédé pour traiter des informations de programme de diffusion et récepteur de diffusion
WO2009151265A2 (fr) Procédé et système pour recevoir des signaux de radiodiffusion
WO2014025207A1 (fr) Procédé et appareil pour traiter un signal de diffusion contenant un service de radiodiffusion interactive
WO2009151267A2 (fr) Procédé de prestation de service et récepteur de diffusion
WO2009151266A2 (fr) Procédé de prestation de service et récepteur de diffusion mobile
WO2015008986A1 (fr) Procédé et appareil de transmission/réception de signal de radiodiffusion dans un système de radiodiffusion hybride
WO2010068034A2 (fr) Procédé de traitement de services en temps non réel et récepteur de radiodiffusion
WO2010021525A2 (fr) Procédé de traitement d'un service web dans un service en temps non réel et un récepteur de diffusion
WO2012144867A2 (fr) Procédé de transmission pour service de radiodiffusion, procédé de réception associé, et appareil de réception associé
WO2011112053A2 (fr) Système de traitement de service de diffusion non en temps réel et son procédé de traitement
WO2014209057A1 (fr) Procédé et dispositif pour émettre et recevoir un service de diffusion dans un système de diffusion hybride sur la base d'une connexion d'un réseau de diffusion terrestre et d'un réseau à protocole internet
WO2011122838A2 (fr) Procédé de traitement de service sans contrainte temps réel et récepteur de diffusion
WO2010068043A2 (fr) Procédé de traitement d'un descripteur de ciblage dans un récepteur en temps différé
WO2011074844A2 (fr) Procédé de traitement de service non temps réel et récepteur de diffusion
WO2012091371A1 (fr) Procédés d'émission et de réception de service de diffusion et appareil de réception du service de diffusion
WO2012091370A1 (fr) Procédé de transmission de service de diffusion, et procédé et appareil pour le recevoir
WO2011056025A9 (fr) Procede de reception de service mobile et recepteur de service mobile
WO2016171496A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2017007224A1 (fr) Dispositif d'émission de signal de radiodiffusion, dispositif de réception de signal de radiodiffusion, procédé d'émission de signal de radiodiffusion, et procédé de réception de signal de radiodiffusion
WO2012099427A2 (fr) Procédé permettant de transmettre un service de diffusion, procédé permettant de recevoir un service de diffusion et appareil permettant de recevoir un service de diffusion
WO2015133770A1 (fr) Appareil et procédés pour émettre/recevoir un signal de diffusion

Legal Events

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

Ref document number: 09827723

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20117013811

Country of ref document: KR

Kind code of ref document: A

122 Ep: pct application non-entry in european phase

Ref document number: 09827723

Country of ref document: EP

Kind code of ref document: A2