Method for mapping signaling information to announcement information and broadcast receiver
First Claim
1. A method of transmitting a non-real time service, the method comprising:
- generating Reed-Solomon (RS) frames that include internet protocol (IP) datagrams containing the non-real time service that is delivered in advance of its use and stored in a receiving device and signaling data for the non-real time service;
modulating data for the RS frames using a Vestigial Side Band (VSB) method; and
transmitting a broadcast signal including the modulated data via a broadcast channel,wherein the IP datagrams are encapsulated based on a User Datagram Protocol/Internet Protocol (UDP/IP) method,wherein the non-real time service includes one or more content items, each of the one or more content items comprising one or more files delivered via File Delivery over Unidirectional Transport (FLUTE) file delivery sessions,wherein the signaling data includes first signaling data containing service-level attributes for the non-real time service and second signaling data for configuring a service guide comprising a content fragment that carries a first element identifying a content item of the one or more content items,wherein the first signaling data further contains service category information identifying the non-real time service and IP addresses, UDP ports and Transport Session Identifiers (TSIs) of the FLUTE file delivery sessions,wherein each of FLUTE file delivery sessions includes one or more FLUTE channels,wherein all of the one or more FLUTE channels in each of the FLUTE file delivery sessions have a same IP address and consecutively numbered UDP ports signaled with a single component descriptor in the first signaling data, andwherein an IP datagram carrying the first signaling data among the IP datagrams has a well-known IP address and UDP port number.
3 Assignments
0 Petitions
Accused Products
Abstract
A method of providing a Non-Real-Time (NRT) service includes receiving a file configuring the NRT service, first signaling information, and second signaling information in a state of being IP-packetized and contained in a single ensemble, configuring and displaying a service guide using the first signaling information acquired from the ensemble, acquiring a first content identifier of content selected from the displayed service guide, accessing a FLUTE session using the second signaling information acquired from the ensemble and acquiring a second content identifier matched with the first content identifier from the accessed FLUTE session, and receiving and storing at least one file configuring the content based on the acquired second content identifier.
17 Citations
10 Claims
-
1. A method of transmitting a non-real time service, the method comprising:
-
generating Reed-Solomon (RS) frames that include internet protocol (IP) datagrams containing the non-real time service that is delivered in advance of its use and stored in a receiving device and signaling data for the non-real time service; modulating data for the RS frames using a Vestigial Side Band (VSB) method; and transmitting a broadcast signal including the modulated data via a broadcast channel, wherein the IP datagrams are encapsulated based on a User Datagram Protocol/Internet Protocol (UDP/IP) method, wherein the non-real time service includes one or more content items, each of the one or more content items comprising one or more files delivered via File Delivery over Unidirectional Transport (FLUTE) file delivery sessions, wherein the signaling data includes first signaling data containing service-level attributes for the non-real time service and second signaling data for configuring a service guide comprising a content fragment that carries a first element identifying a content item of the one or more content items, wherein the first signaling data further contains service category information identifying the non-real time service and IP addresses, UDP ports and Transport Session Identifiers (TSIs) of the FLUTE file delivery sessions, wherein each of FLUTE file delivery sessions includes one or more FLUTE channels, wherein all of the one or more FLUTE channels in each of the FLUTE file delivery sessions have a same IP address and consecutively numbered UDP ports signaled with a single component descriptor in the first signaling data, and wherein an IP datagram carrying the first signaling data among the IP datagrams has a well-known IP address and UDP port number. - 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 including internet protocol (IP) datagrams via a broadcast channel, the IP datagrams containing the non-real time service that is delivered in advance of its use and stored in a receiving device and signaling data for the non-real time service; a demodulator configured to demodulate the received broadcast signal; a decoder configured to build a Reed-Solomon (RS) frame including the IP datagrams from the demodulated broadcast signal; a processor configured to process the non-real time service and the signaling data from the built RS frame; and a storage unit configured to store the processed non-real time service, wherein the IP datagrams are sequentially encapsulated based on a User Datagram Protocol/Internet Protocol (UDP/IP) method, wherein the non-real time service includes one or more content items, each of the one or more content items comprising one or more files delivered via File Delivery over Unidirectional Transport (FLUTE) file delivery sessions, wherein the signaling data includes first signaling data containing service-level attributes for the non-real time service and second signaling data for configuring a service guide comprising a content fragment that carries a first element identifying a content item of the one or more content items, wherein the first signaling data further contains service category information identifying the non-real time service and IP addresses, UDP ports and Transport Session Identifiers (TSIs) of the FLUTE file delivery sessions, wherein each of the FLUTE file delivery sessions includes one or more FLUTE channels, wherein all of the one or more FLUTE channels in each of the FLUTE file delivery sessions have a same IP address and consecutively numbered UDP ports signaled with a single component descriptor in the first signaling data, and wherein an IP datagram carrying the first signaling data among the IP datagrams has a well-known IP address and UDP port number. - View Dependent Claims (7, 8, 9, 10)
-
Specification