Method of processing non-real time service and broadcast receiver
First Claim
1. A method of transmitting a non-real time service, the method comprising:
- generating a broadcast signal which carries internet protocol (IP) datagrams, the IP datagrams containing the non-real time service that is delivered in advance of its use and stored in a receiving device, and first signaling data which contains a content fragment for a content item of the non-real time service; and
transmitting the broadcast signal,wherein the non-real time service is associated with one or more content items, each of which consists of one or more files,wherein the one or more files are delivered via a File Delivery over Unidirectional Transport (FLUTE) file delivery session, the FLUTE file delivery session transmitting a FLUTE Description Table (FDT) that includes a transfer object identifier (TOI) identifying a transport object which includes a file transmitted through the FLUTE file delivery session, content location information identifying a location of the file and content linkage information linking with the content fragment included in the first signaling data,wherein the content fragment includes a content linkage element mapping the content linkage information included in the FDT to identify that the one or more files carried on the FLUTE file delivery session belong to content items for the non-real time service,wherein the IP datagrams further include second signaling data which contains service-level attributes for the non-real time service,wherein each of the FLUTE file delivery sessions includes one or more FLUTE channels, andwherein all of the FLUTE channels in each of the FLUTE file delivery sessions have a same IP address and numbered user datagram protocol (UDP) ports signaled with a single component descriptor in the second signaling data.
1 Assignment
0 Petitions
Accused Products
Abstract
A method of receiving and processing a Non-Real Time (NRT) service and a broadcast receiver are disclosed herein. A method of processing an NRT service in a broadcast receiver includes receiving and processing a signaling information table including detail information of each content in the NRT service and indication information indicating whether the content is available on internet, acquiring internet access information of each file belonging to content available on the internet through File Delivery Table (FDT) of File Delivery over Unidirection Transport (FLUTE) based on the indication information, and downloading files belonging to the content by accessing the internet based on the acquired internet access information.
-
Citations
10 Claims
-
1. A method of transmitting a non-real time service, the method comprising:
-
generating a broadcast signal which carries internet protocol (IP) datagrams, the IP datagrams containing the non-real time service that is delivered in advance of its use and stored in a receiving device, and first signaling data which contains a content fragment for a content item of the non-real time service; and transmitting the broadcast signal, wherein the non-real time service is associated with one or more content items, each of which consists of one or more files, wherein the one or more files are delivered via a File Delivery over Unidirectional Transport (FLUTE) file delivery session, the FLUTE file delivery session transmitting a FLUTE Description Table (FDT) that includes a transfer object identifier (TOI) identifying a transport object which includes a file transmitted through the FLUTE file delivery session, content location information identifying a location of the file and content linkage information linking with the content fragment included in the first signaling data, wherein the content fragment includes a content linkage element mapping the content linkage information included in the FDT to identify that the one or more files carried on the FLUTE file delivery session belong to content items for the non-real time service, wherein the IP datagrams further include second signaling data which contains service-level attributes for the non-real time service, wherein each of the FLUTE file delivery sessions includes one or more FLUTE channels, and wherein all of the FLUTE channels in each of the FLUTE file delivery sessions have a same IP address and numbered user datagram protocol (UDP) ports signaled with a single component descriptor in the second signaling data. - View Dependent Claims (2, 3, 4, 5)
-
-
6. An apparatus for receiving a non-real time service, the apparatus comprising:
-
a tuner configured to receive a broadcast signal which carries internet protocol (IP) datagrams, the IP datagrams containing the non-real time service that is delivered in advance of its use and stored in a receiving device, and first signaling data which contains a content fragment for a content item for the non-real time service; a processor configured to parse first signaling data from the IP datagrams; and a storage configured to store a non-real time content item based on the parsed signaling data, wherein the non-real time service is associated with one or more content items, each of which consists of one or more files, wherein the one or more files are delivered via a File Delivery over Unidirectional Transport (FLUTE) file delivery session, the FLUTE file delivery session transmitting a FLUTE Description Table (FDT) that includes a transfer object identifier (TOI) identifying a transport object which includes a file transmitted through the FLUTE file delivery session, content location information identifying a location of the file and content linkage information linking with the content fragment included in the first signaling data, wherein the content fragment includes a content linkage element mapping the content linkage information included in the FDT to identify that the one or more files carried on the FLUTE file delivery session belong to content items for the non-real time service, wherein the IP datagrams further include second signaling data which contains service-level attributes for the non-real time service, wherein each of the FLUTE file delivery sessions includes one or more FLUTE channels, and wherein all of the FLUTE channels in each of the FLUTE file delivery sessions have a same IP address and numbered user datagram protocol (UDP) ports signaled with a single component descriptor in the second signaling data. - View Dependent Claims (7, 8, 9, 10)
-
Specification