DE202004005445U1 - Receiver for representing static media object(s) receives coordination information in data file element of data file transmission table instance of File Delivery over Unidirectional Transport session - Google Patents

Abstract

The arrangement has a receiver for receiving a static media object and its time co-ordination information from a transmitter unit using a transmission session according to the File Delivery over Unidirectional Transport protocol. The coordination information is delivered in a data file element of a data file transmission table instance of the transmission session. A display displays the received object in a display area for a period defined by the co-ordination information. Independent claims are also included for the following: (1) a transmission arrangement for transmitting at least one static media object (2) and computer-legible medium for storing commands.

Description

The The present invention relates to a receiving device to display at least one static media object that of is delivered to a sending unit that corresponds to a transmission session the FLUTE protocol. About that In addition, a transmission device for transmitting at least one static media object supplied by a sending unit the one broadcast session provided according to the FLUTE protocol.

The 3GPP (3 ^rd Generation Partnership Project) is the IETF (Internet Engineering Task Force) standardized protocols like RTP, UDP, IP for the transport and packet switching codecs such as AMR (Adaptive Multi-Rate) and H.264 (MPEG 4 Part 10) for encoding media. The 3GPP Packet Switched Streaming Services - 3GPP PSS - (see 3GPP TS 26.234: "Universal Mobile Telecommunications System (UMTS); Transparent end-to-end streaming service; Protocols and codecs", from September 2003, available at http: // www .3gpp.org) uses the RTP / UDP protocol stack to stream audio / video / text media.

Together with streaming and downloading files are carousel services (carousel services) as one of three 3GPP MBMS user service classes (see 3GPP TS 22.246: "Multimedia Broadcast / Multicast Service (MBMS) User Services; Stage 1 (release 6) ", from March 2004 available at http://www.3gpp.org). Registrations that carousel service are numerous, like the following Examples show:

• - Live Ticker. This application delivers repeatedly and at certain times - periodically as well as on request - updated Text data for changes to reflect.
• - audio and low bit rate video. If the available bandwidth for one transport carrier (transport bearer) is rather low to make video streaming available could ask instead, still images are delivered with the carousel services become. The pictures are taken periodically or at certain times, when the content changes, brought up to date and are updated with the corresponding Audio stream synchronized.
• - General Distribution of content. The protocol used for the carousel service is specially designed to transport binary data to a transparent one Way suitable. This means, The protocol is the format of the data being transported, whether it is audio / video / text or any other application data are not known. This one keeps the described procedure these features and adds the synchronization of the data the static media.

On Carousel service combines aspects of both, downloading of files and streaming services. However, the target media could do this Service only static media (e.g. text and / or still images) his. A time synchronization with other media could also to be required. For example, text objects are delivered and updated from time to time.

unmoved Pictures could can also be combined with the display of video at low frame rates. Download files together with the service (download service) could this service also includes functional reliability. Like downloading One of the purposes of carousel service is to provide files reliably from static media objects to a user, e.g. Text or immobile pictures.

However, Unlike downloading files, the data can be up to date for the Synchronization of the static media themselves (e.g. playing, on bring up to date) and with other data objects of importance his. Therefore, typically 100% reliability not always be necessary. The one represented by a media object Content may change during change a session. As a result, delivered media objects may be required update, not necessarily periodically but also on request. Therefore, it may be desirable that the Carousel service Means for updating media and their synchronization with other media objects in a multimedia session.

REAL-TIME TRANSMISSION PROTOCOL (REAL-TIME TRANSFER PROTOCOL)

The Real-time Transmission Protocol (RTP) provides an end-to-end transmission service for data with real-time characteristics, including user data and type identification, sequence numbering and the assignment of time stamps. RTP is primarily designed (but not limited to) To meet the needs of multimedia conferences with many participants. As a result, it also supports multicast transmission.

During RTP is not limited to a special data format, that is it The format of the data it transports is known. Hence the specification and use of special user data formats required for each media format, e.g. as for MPEG-1 / MPEG-2 audio and video or 3GPP timed text such as in the Internet draft by Rey et al., "RTP Payload Format for 3GPP Timed Text", IETF AVT Working Group, February 2004 (available at http://www.ietf.org). This document guides you Overhead to the user data and complexity in the servers and the end devices.

A other limitation of RTP is the lack of any functional security means (reliability): RTP is designed to get the media in a timely manner (timely manner) to deliver without failover against transmission errors to disposal to deliver. On the other hand, static media objects such as text are required or still images a certain level of reliability of the transport service. Therefore would have to adequate Techniques such as Forward Error Correction (FEC) from the Applications available be put. basic Funds for Such protection in RTP are from Rosenberg, "An RTP Payload Format for Generic Forward Error Correction ", RFC 2733, December 1999 (available at http://www.ietf.org). A more advanced one Method around the data streams with the help of Reed-Solomon coding on the packet layer in the Internet Draft by Liebl et al., "RTP Payload Format for Erasure-Resilient Transmission of Progressive Multimedia Streams ", Work in Progress, October 2003 (available at the http://www.ietf.org) Service. However, both of these solutions still require specific ones User data formats for any medium and therefore suffer from the shortcomings previously described.

RELIABLE MULTICASTE PROTOCOLS

Basically there there are many different ways to get reliable multicast transport service to disposal as in Handley et al., "The Reliable Multicast Design Space for bulk data transfer, " RFC 2887 August 2000 (available at http://www.ietf.org). The IETF RMT working group has recently the FLUTE protocol as described in the Paila et al. Internet draft, "FLUTE - File Delivery over unidirectional transport ", December 2003 (available at http://www.ietf.org) specified this here is recorded by reference. The FLUTE protocol is for unidirectional transmission from binary Objects (files) such as text and images have been suggested.

ARIB B24 STANDARD

The Japanese ARIB standard is a series of documents covering the transmission system (Air interface), audio / video and multiplexing, data encoding and transmission, the service information and access authorization for digital Specify broadcasting systems. There are also some guidelines on recipient structure and operating guidelines for terrestrial television broadcasting.

The ARIB standard uses the MPEG2 standard for coding and multiplexing the audio and video data. It also specifies that The MPEG2 multiplex technique is to be used to package the data in packet-oriented Networks.

however The ARIB specification lacks a multitude of features that this Invention fulfills:

• - ARIB does not specify any procedures for functional reliability on the packet layer e.g. a kind of forward error correction at the application level like Forward Error Correction (FEC) or asymmetrical deletion protection schemes (UXP - unequal erasure protection schemes). A functional safety mechanism is rather on the lower layers (physical layer, Air interface).
• - ARIB requires that the audio / video encoding comply with the MPEG2 standard, which is a transcoding of a given codec, such as AMR to MPEG2, imperative.
• - ARIB was not in the 3GPP for Multicast / Broadcast Multimedia Services (MBMS) accepted.

The defects mentioned above can the ARIB standard (and any of its components) as a candidate for transmission of multicast multimedia data in 3GPP.

FLUTE has a variety of properties which make it very suitable for target application makes.

• - The Use of Forward Error Correction (FEC), an open process-coupled Scheme (open-loop scheme) to ensure functional reliability put.
• - The Definition of a file transfer session the transmission details includes.
• - In-band Signaling (in-band signaling) of the transport parameters of the session.
• - In-band Signaling properties of the delivered files.
• - In-band Signaling details involving multiplexing from a variety of files associated with the session.

however are information for time control for synchronization purposes not defined in the FLUTE specification. Poses a possible solution the use of SMIL (see "Synchronized Multimedia Integration Language (SMIL 2.0) ", W3C Recommendation, August 2001, available at http://www.w3.org/TR/smil20) on the application layer to synchronize the transported objects. However, SMIL supports not updating media objects during a session. Instead of of that the media objects used in a SMIL presentation by be known at the start of the presentation and can do not change dynamically.

Currently FLUTE is considered the most promising protocol in 3GPP for one reliable multicast service discussed. The following paragraphs will explain some of the key concepts of FLUTE for the understanding of the present invention may be necessary:

• - One File transfer session includes all objects transmitted with a single FLUTE instance.
• - The Fall Delivery Table (FDT) provides a means around a variety of attributes associated with media objects (files) that in a file transfer session to be delivered to associate. The attributes refer to the delivery of the files and the files themselves. Examples of such Attributes are (not mutually exclusive or complete): the Transport object identifier value (transport object identifier) which represents a file in the FLUTE session; the 1D of the instanced FEC building blocks; a globally unique Identifier of the file expressed as either an absolute or relative URI; the MIME media type, Size, coding the file; Etc.
• - Everyone Media object in a file transfer session is identified with the Transport Object Identifier (TOI). The The purpose of the TOI is to provide means for demultiplexing of the packages belonging to different media objects can be transported with the same FLUTE session.

FLUTE is basically suitable good as a transport protocol for reliable transmission (push) of media objects to a terminal via a to trigger unidirectional multicast channel to a terminal. However, FLUTE is currently providing just the usual Means of transporting media objects are available, the procedures for application semantics to disposal are still an unresolved issue that is being addressed must become. In particular are for The following problems have not yet been suggested solutions.

On to disposal The point to be made is the assignment of media objects. The application semantics a broadcast session according to the FLUTE protocol are for the transport layer is transparent, i.e. the transport level only the transported media objects are known.

The application semantics can be application-specific. Scene description, ie the definition of different display regions and audio channels as well as their arrangement in the application. For example, in a multimedia presentation, a rectangular region A (position [xA, yA], width wA, height hA, display level IA) could be defined for the display of a video frame or image, while an overlapping rectangular one (located in a higher display level) ) Region B (position [xB, yB], width wB, height hB, display level IB) could be defined for the display of the synchronized subtitle. In addition, a rectangular region C (position [xC, yC], width wC, height hC, display level IC) could be associated with advertising as in 1 shown. In order to be able to display the downloaded media objects in the associated application object, means for simple and efficient mapping are required.

On another problem that has not yet been solved is synchronization. Media objects can a synchronization on the application layer need something Scheduling information for each of the corresponding ones Objects required.

It may also be necessary to resolve the temporal relationships between the objects, especially if one media object updates and replaces another. This also leads to an associated nes problem with it, namely the referencing of downloaded objects. The downloaded media objects may need to be referenced in the local buffer in the end device to enable the application on the end device to load them into the display at the right time.

Therefore will improve delivery and visualization techniques Media objects available can solve at least one of the above problems.

A embodiment The present invention relates to a receiving device to display at least one static media object that of a sending unit using a transmission session after Transfer the FLUTE protocol becomes. The receiving unit can e.g. a receiver for receiving a static Media object and its temporal coordination information from one Transmitting unit on the receiving unit include the temporal Coordination information in a file element File transfer table instance (file delivery table instance) of the transmission session becomes. The receiving unit can also have a display for illustration of the received static media object in a display area for one time period defined by the time coordination information include.

A further embodiment The present invention provides a transmitting device for transmission at least one static media object to a receiving unit using a broadcast session ready according to the FLUTE protocol. The transmitter unit can be a transmitter unit to transfer one static media object and its temporal coordination information to the receiving unit, the time coordination information comprising in a file element of a file transfer table instance of the transfer session is delivered to the receiving unit.

A further embodiment The present invention relates to a computer readable Medium for storing instructions when issued by a processor accomplished will cause the processor to be a static media object, that from a sending unit to a receiving unit using a broadcast session according to the FLUTE protocol is delivered by receiving a static media object and its timing coordination information from the sending unit on the receiving unit and displaying the received static Media object in a display area for a by the temporal Coordination information represents defined presentation period. The time coordination information can be sent to, for example Receiving unit with a file element of a file transfer table instance of the transfer session to be delivered.

In a further embodiment The present invention provides a computer readable medium Store instructions when executed by a processor cause the processor to transmit at least one static media object that is sent from a sending unit to a receiving unit using a broadcast session transmitted according to the FLUTE protocol is accomplished by providing a static media object and its temporal coordination information to the receiving unit, wherein the time coordination information in a file element of a File transfer table instance the broadcasting session is delivered to the receiving unit.

The attached Drawings are included in and constitute part of the description is a variety of embodiments to explain the present invention. These drawings along with the description serves to explain the principles of the invention. The Drawings are for the purpose of illustrative examples only, such as the invention accomplished and can be used and are not intent on the invention to only the illustrated and described exemplary embodiments to restrict. Next, features and advantages are the following and more specific Description of the various embodiments of the present Invention as shown in the accompanying drawings be, whereby:

1 an exemplary arrangement of display objects is shown,

2 shows an exemplary streaming environment according to an embodiment of the present invention,

3 an exemplary flow diagram of the operation of a streaming environment that uses the FLUTE protocol,

4 an exemplary receiving device according to a further embodiment of the lying invention shows and

5 shows an exemplary transmission device according to an embodiment of the present invention.

Similar or corresponding details in the figures are the same Marked reference mark.

Data of streaming applications can in principle be divided into two classes. A class can be considered continuous Media are referred to, e.g. an audio and / or video data stream, delivered by a streaming server to a receiving unit becomes. This data is continuously delivered to the recipient and have certain time constraints on their timely delivery Delivery to the user.

The second class can be called static media that is not be delivered to the recipient in a continuous data stream and the also time restrictions in relation to their delivery to the user. On representative this class can Be pieces of data using a carousel transport mechanism (carousel transport mechanism).

On static media object may have time constraints on its timely presentation for have the user and can therefore use the continuous stream of data (i.e. which have timelines) to be synchronized. For example, has an image that syncs at a specific time be presented with an audio stream of a multimedia presentation cannot have a continuous data stream, e.g. Audio or video, but it can undoubtedly have timing constraints.

consequently The term "static media object" often used in the present application can be parts of information denote that have time constraints: e.g. a certain playing time (play-out time), an expiration time and a with associated schedule, but unlike audio and video a continuous data stream is missing.

It should be further noted that although the focus of this Document on the delivery and provision of visual objects is focused, the present application on different audio channels in a similar Way as described in the following sections will be achieved. In this context, in this Document frequently referred to display areas as display objects. However, application to different audio channels is straightforward.

The The present invention aims to synchronize static Media objects in the application layer by using the extensibility the file delivery table and by defining additional ones To allow file attributes application-specific, temporal coordination information for the to transport transported media objects.

Further The present invention aims to provide an integrated and easy to implement solution for at least to provide one of the aforementioned problems. Corresponding one embodiment the present invention can already do this in the FLUTE protocol header Defined Transport Object Field can be used to Problem and the mapping of static media objects to display objects to solve. In the prior art, the TOI field is usually open for demultiplexing purposes the transport layer, i.e. for demultiplexing various Media objects that are transmitted in the same FLUTE session become.

Furthermore The present invention aims at the two above Combine aspects, the TOI and the timing coordination information can used to relate the relationship of one media object to another updates without the introduction of any additional and resolve explicit protocol fields or payload extensions.

Furthermore solves one further embodiment of the present invention the problem of referencing downloaded Objects in the cache by providing a local URL as a value in the "Content-Location" attribute of the FLUTE File delivery table for the corresponding media object.

In front at the beginning of a session, the sending unit, e.g. a streaming server, the receiving units, e.g. the mobile devices that receive the session, with the application semantics, e.g. a session and scene description include, available put.

According to a further embodiment of the present invention, the semantics can include, for example, the arrangement of the display objects that have been defined by the application and the assignment of these objects to the media objects in the corresponding FLUTE session. For this purpose, display areas can be defined similar to those in SMIL or MPEG-4 and each of these display objects can be referenced using a unique identifier, which is referred to in this document as an Application Object Identifier (AOI). An example of the arrangement of three display objects for a multimedia session is shown in 1 and a sample definition of display objects in an XML-like syntax could look like this:

It it is noted that the above syntax is only an example Representation of an XML-like syntax to describe the arrangement of display objects is and is not intended to limit the present invention thereto.

The Illustration can be referenced as an association of any display object through its associated AOI - with a corresponding Transport Object Identifier (TOI) that within a FLUTE instance the media object that is in that particular Display area to be displayed is assigned is described become. An example figure is shown in the following table shown:

The transfer the mapping information to the devices, e.g. in the form of a table, is not limited to a single procedure or protocol. For example, you can Protocols such as HTTP GET or SAP are used to map the information transferred to.

However, if FLUTE is used for this purpose, a variety of Advantages arise: additional Overhead by using a mix of different protocols can be prevented and dynamic updates the mapping table, what an update of the static media objects allowed, can be discussed in more detail below is supported become.

Corresponding one embodiment of the present invention the mapping information as a transport object in the corresponding FLUTE session can be transported. This transport object can e.g. the first transport object that corresponds to the initial file delivery Table (FDT) follows. The term "file" can be used as a pseudonym for "object" in the context of FLUTE to be used.

Since the format of the illustration should allow simple and quick parsing, a "text / tab-separated-values"("text / tabulator-separated-values") MIME type can be used, for example, to inform onen in a matching text file. Of course, any other suitable MIME type can be used to encode the mapping information for the receiver.

alternative can in another embodiment a predefined static mapping of the present invention used by AOIs and TOIs that permanently have each AOI on one maps specific TOI. It may also be possible in the beginning a static mapping exists, which is then replaced by mapping information, available to the receiving unit be brought up to date.

The Image information - e.g. saved in the form of a file - can be in the payload of a FLUTE session how to encapsulate any other transport object and it is identified by a unique Transport Object Identifier identified. For example, the TOI value of 1 can be used for delivery be reserved by mapping information.

How in the exemplary XML schema according to another embodiment of the present invention is shown below, a file entry <File> of an FDT instance <FDT-Instance> can be used to the location of the mapping information that the TOIs and AOIs consecutively map, be identified:

The FDT can be a means of managing a variety of attributes, with files stored in a file transfer session (fite delivery session) to be delivered. The following exemplary attributes that neither intend to be mutually exclusive excluded or completely can be provided become. Attributes related to the delivery of a file which relate to the transfer can obtain a file the TOI value of the file FEC Instance 1D (file FEC Instance 1D), the FEC Object Transmission Information a size of the transport object, that conveys the file and be the aggregate transmission rate of packets on all channels. Possible You can use attributes that refer to the file itself Name, their identification and location e.g. using a URI specifies the MIME media type of the file, the size of the file, their encoding and a message digest of the file his. The FDT can have a subset of these attributes for each file include, but can always be at least the file's TOI and location contain their content.

Logical the FDT can be viewed as a set of file description entries (file description entries) for Files that are to be delivered in the session are described become. Each file description entry can be the TOI of the file which it describes contain and the URI which is the location of the File. The TOI can also be found in any data packet that corresponds the FLUTE specification is structured while the file is being transferred his. This format can be an ALC / LCT format, e.g. in Luby et al., "Asynchronous Layered Coding (ALC) Protocol Instantiation ", RFC 3450 and Luby et al.," Layered Coding Transport (LCT) Building Block ", RCF 3451, December 2002 (both available at http://www.ietf.org) be specified.

Therefore the TOI carried in the file description entry can determine which Data packets information about which file contain allow. Each file description entry can also have one or more descriptors contain, which map the above-mentioned attributes to the file at the recipient.

Each file transfer session can use an FDT valid for a given session. The FDT can also provide a file description entry for each file in the session is mapped onto a TOI. In the transmission session according to the FLUTE protocol, the FDT can be transmitted as so-called FDT instances, as shown in the example XML schema above.

A FDT instance can have one or more FDT file description entries contain. Any FDT instance can also use, a subgroup of, a superset of, or a complement to any other FDT instance. A specific FDT instance can be used during a Session can be repeated several times, even after each other following FDT instances (with higher FDT instance ID numbers) have been. Each FDT instance can have at least one file description entry and at most the complete FDT of the file transfer session include.

A Receiving unit of the file transfer session can create an FDT database for maintain received file description entries. The receiving unit can the database e.g. service on receipt of the FDT instances. Therefore, the contents of the FDT database can be changed at any time the current view of the recipient from the FDT of the file transfer session play.

There An FDT database is an abstract concept, the structure can and maintaining the FDT database in a variety of different ways Ways to be implemented. Therefore the examples serve in this document for exemplary purposes only to understand the concepts and to explain ideas underlying the present invention.

How resulting from the above deals with one of the many aspects of the present invention the mapping of transferred media objects (TOI) for application-specific display objects (AOI), such as previously described.

While the Association of TOIs with corresponding AOIs e.g. from the beginning can be determined, the association of a TOI with a specific Media object at the time of transport, i.e. dynamic, happen. If an application is a media object to be displayed in a particular display object needed the sender can use the corresponding FLUTE TOI this media object map using session mapping information. This allows the original Purpose of the TOI field - medium for demultiplexing different, in a single FLUTE instance Providing transported media objects - protected become.

This Can approach the additional Have the advantage that it is an implicit and easy to achieve Imaging mechanism supported, as described below. However, that may require that the association of TOIs not for the application is transparent, i.e. the interface of the FLUTE protocol implementation can specify the specification of the TOI used for a particular object will need to allow.

The however, does not violate the FLUTE specifications since the latter do not determine how TOIs are mapped.

With the available shown using the TOI field of the FLUTE protocol and application-specific AOI or with a predefined static Mapping of TOIs and AOIs can be known by the end device application, where each media object that transports with the associated FLUTE session is to be represented.

To the Example can be a static mapping by assigning the TOI value of 2 to the AOI value of 1, the TOI value of 3 to the AOI value of 2, etc. Another alternative can be the display objects in a list, a field (array) or the like, with the first element on one TOI value of 2, the second item in the list to a TOI value of 3, etc. is mapped. These examples are for the purpose only an illustration of how to implement a static mapping can be, and limit static mappings not on these implementations.

however can, for timely display and synchronization of media objects to support, two additional File attributes for the file delivery table from FLUTE according to a further embodiment of the present invention. These extensions fulfill the requirements of the FLUTE specifications and how can be defined as follows:

The Attributes "Content-Begin" ("Content-Beginning") and "Content-Duration" ("Content-Duration") can determine the application time display for which the corresponding media object is displayed should or the period after which it is considered invalid and removed should be. Both file attributes can be generic and fit to different media types. Also, since both are optional Attributes are can they only apply to time-lined static media) can be used. Therefore there will be no compatibility problems and additional Introduced overhead.

Corresponding a further embodiment of the present invention both concepts previously described, i.e. the use of mapping information and the use of timing coordination information in combination used to provide object update functionality without need after any additional or to provide explicit update information.

in the In the event that media objects are updated or exchanged should be the end device the new media object that is assigned to a specific TOI, received while the previous media object with the same TOI will still be valid and displayed from the display buffer of the terminal can be.

As soon as the last packet, which delivers a new object, has been received and has been stored in the local buffer, the display application can be informed about the assignment of a new object with the TOI and the start time of this object. An application process can resolve the mapping to the corresponding display object (AOI) according to the TOI. It can also be an on Show refresh event for the corresponding display area according to the value of the "Content-Begin" attribute. If the time specified in this attribute has already expired, a display refresh can be triggered immediately. The update of a media object does not necessarily have to be determined in advance; but can be generated on-fly, which makes them well suited for live sessions. In this exemplary case, a "content duration" attribute for the previous object may not be necessary and cannot normally be provided since the duration is not known from the start. Thus, objects can be valid until an update arrives.

If For some reason a "content duration" attribute is set, and its value determines that the representation of the Media object the "content begin" value of the following Media object exceeds can do the previous with the update event described to be interrupted.

How indicated above, can Media objects e.g. B. in a local buffer of the receiving unit get saved. To downloaded media objects from the cache to be able to reference that in the FLUTE specification Defined "content location" attribute used become. This field can be the location of a file using a URI (Uniform Show Resource Identifier): Some applications can use a or require multiple successive update media objects, i. H. a carousel transfer (carousel delivery) the data to be temporarily stored by the end devices Objects at the same time while the first media object is still valid. Ambiguities dissolve, if all of the above objects are assigned to the same TOI, the application can create a database of downloaded media objects entertained in the local cache. The database can e.g. B. Fields for the TOI, the presentation time interval and the content storage location include.

Another solution can be that each media object is assigned a unique TOI. The mapping between TOIs and AOIs can then be done, for example, by expanding the FDT with an additional optional parameter that provides the mapping information for the application, i.e. the Application Object Identifier (AOI) or by mapping a display area (ie its AOI) to one List of consecutive TOIs, ie [TOI _min , TOI _max ].

This can make it possible to simultaneously store a number of (TOI _min to TOI _max ) media objects on the end device side that reference the same display area. The "Content-Begin" field can e.g. B. can be used to determine the correct order of presentation.

FLUTE does not define how TOIs are assigned to individual transport objects become. Hence implementations from FLUTE regulate this in different ways. A kind and Way may be that API (Application programming Interface) to define so that the application assigning TOI values can control media objects.

A different possibility may be to implement FLUTE so that the TOI value for each Object is incremented. In this case, the TOI assignment not controlled by the application.

On further means to tell the receiving unit which AOI in connection with which TOI can be used an additional or optional attribute to the file delivery table that matches the associated AOI for the purposes of illustration indicates:

Around To prevent ambiguity, if both, use a mapping table and the "AOI" attribute one of the values, e.g. B. the "AOI" field the higher in the FDT Have priority.

Next, an exemplary embodiment of a streaming environment will be corresponding to streaming environment with reference 2 briefly described. A transmission device, e.g. B. a streaming server 200 , delivers data packets of a FLUTE transmission session to a receiving device 400 , such as B. the mobile device 202 , The data, which includes the static media objects belonging to the session, can be e.g. B. over the Internet or any other packet-switching network and over a mobile communication network, such as a UMTS Terrestrial Access Network (UTRAN 201 ) are delivered to the mobile device.

3 Figure 3 shows an example corresponding to an embodiment of the present invention Flow diagram of the operation of a streaming environment that uses the FLUTE protocol. It should be noted that, according to another embodiment, only a portion of that shown in FIGS 3 shown steps can be performed by the receiving device and / or transmitting device. The flow chart in 3 Purpose is only to describe an embodiment of the present invention and is not intended to limit the invention thereto.

In block 301 the sending device can (dynamically) determine the associations between the various presentation objects (ie presentation areas) and the media objects which are delivered in the transmission session and which are to be displayed on the receiving device.

In block 302 The sending device can generate application semantics for the transmission session, wherein the association data can either be contained directly in the semantics or can be referenced as described above. The application semantics can next be in block 303 are transmitted to the receiving device. For example, the mapping information can be transmitted in a <File> element of an FDT instance as described previously. In a further embodiment, additional fields can be defined in the <File> element which contain the mapping information.

The receiving device can use the application semantics in step 311 receive and can extract the application objects and, if they are signaled in-band (in-band), the association data. If the association data is signaled separately (out-band), the receiving device can use the association data in step 313 z. Received from the sending device or any other device referenced by the application semantics.

After this the receiving device has received the information Initialize session parameters that u. a. an illustration of the AOIs of the display objects for at least one TOI, as before has been described in more detail.

The sending device may further provide timing information for a media object sent to the receiving device in step 304 is generated. This timing coordination information can be used to generate a generated FDT instance, e.g. B. in a <File> element of it, in step 305 to be added. The block 304 further indicates that location information from which the media object can be received can also be included by the FDT instance. Usually, the media objects of a FLUTE session can be made available by the sending device. However, its location from which the sending device received the static media objects may e.g. B. are displayed by using a "content location" attribute of the <File> element. Alternatively, it may also be possible for the receiving device to use the storage location information in the “content location” attribute in order to obtain the corresponding object from the displayed storage location.

After the FDT instance has been created, it can in step 306 are transmitted to the receiving device. The FDT instance can be accessed by the receiving device in step 304 can be received, and the media object can be in step 315 can be obtained from the sending device that the media object in step 307 transferred.

How described above in an alternative embodiment the location information supplied to the receiving device have been used by her to display the media object on the display Storage location to request and receive. This alternative embodiment can e.g. B. in cases be sensible in which the service / content supplier does it alternatively allows to download media objects of the session with a pull (unicast). For example, if there are many connection breaks a recipient from a cheaper push service (multicast) to a more expensive one Change pull service (unicast).

Furthermore, the time coordination information from the FDT instance in step 316 are extracted to enable the display of the media object for a period of time indicated by the time coordination information.

Next, based on an object identifier, e.g. B. TOI, which is also included in the FDT instance, the presentation object in which the static media object is to be displayed can be based on the association data in step 317 be determined. In addition, the media object obtained can be evaluated in the correct representation by evaluating the timing coordination information and the association data be presented richly with the right timing.

Those skilled in the art will appreciate that a variety of modifications to that embodied by the embodiment of the present in FIG 3 shown invention can be made without departing from the scope of the present invention.

4 shows an exemplary receiving device 400 according to an embodiment of the present invention. The receiving device may include a receiver 401 for receiving information from many sources. Among other things, the receiver can be used to obtain static media objects from a FLUTE session in order to obtain data related to the session.

In addition, the receiving device can further include a processor 402 which can be used, among other things, by the recipient 401 process received information. For example, the processor can be used to process the timing information, resolve the associations between media objects, update their associations, etc. The variety of instructions issued by the processor 403 can be run to perform the various tasks in a memory 400 get saved. The memory 400 can also be used as a cache of the session data, e.g. B. the association data, the media objects delivered in the FLUTE session, etc. are used. In addition, the receiving device can have a display 402 include to present the received media objects to a user.

Average artisans will appreciate that, for purposes of scarcity, only a few exemplary tasks and functions of the various components of a receiving device 400 and recognize that these components can perform a variety of tasks and functions that are not explicitly mentioned here but are within the scope of the present invention. In addition, you will recognize that a receiving device 400 a variety of other components that are not in 4 shown may include.

Yourself now 5 is an exemplary sending device 500 according to an embodiment of the present invention. The sending device 500 can be a transmitter 501 include. The transmitter 501 can e.g. B. the data associated with the FLUTE session, such as application semantics or media objects.

In addition, the sending device 500 a processor 502 for processing the data associated with the FLUTE session and determining session parameters prior to transmission. The corresponding commands issued by the processor 502 can be run in a memory to perform its many different tasks 503 the transmitting device 500 get saved.

Again, those of ordinary skill in the art will appreciate that, for purposes of scarcity, only a few exemplary tasks and functions of the various components of a transmitter device 500 have been described. Those skilled in the art will recognize that the component can perform a variety of different tasks and functions, which are not explicitly listed here but are within the scope of the present invention. In addition, they will recognize that the sending device 500 a variety of other components that are not in 5 shown may include.

A further embodiment the present invention relates to implementation of the various embodiments and variations described above of which using hardware and software. It is recognized that the different solutions previously proposed as well as the different ones logical blocks, Modules, circuits that have been previously described using of computing devices such. B. general purpose processors, digital Signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or programmable Logic devices, etc. implemented or executed can be. The different embodiments of the present invention also carried out by means of a combination of these devices or be embodied.

Further can the different embodiments of the present invention also implemented with the aid of software modules that are executed by a processor or directly by hardware. A combination of software modules and a hardware solution can also possible his. The software modules can on any type of computer readable storage medium, e.g. B. RAM, EPROM, EEPROM, flash memory, registers, hard drives, CD-ROM, DVD, etc. can be saved.

While the Invention related to a variety of exemplary embodiments has been described, it will be apparent to those skilled in the art that a Variety of modifications and variations and improvements to the present invention in the light of the foregoing can be made.

In a variation of an embodiment the receiving unit can further apply semantics to the transmission sessions and at least one display area for displaying a static Describe media object received. The semantics can be one Association of each display area with a display area identifier provide. About that Furthermore, an object identifier of every static media object, that in the broadcasting session will be delivered with a viewport identifier be associated, the display area by the association the identifier of the static media object with the viewport identifier is identified.

To the For example, a static media object can be dynamic with an object identifier in be associated with the sending unit.

In Another variation can be the association of the static media object with a display area from data in an association file, that in a file transfer table instance the broadcasting session is included.

To the Example the data in the association file is made available in a format be a character that is not used to get the data encoding used as separator.

In Another variation can be the association of the static media object with a viewport on one in a file transfer table instance the broadcasting session contained information based.

Furthermore, according to another variation of an embodiment, the computer readable Medium further include means adapted to store commands, which, when executed by a processor, the deployment of location information of the static media object and the identifier of the static media object within a file element File transfer table instance the broadcasting session to the receiving unit.

Furthermore can each received static media object, its object identifier, its associated Viewport identifier and its view period be stored in a buffer of the receiving unit. In a further variation, a each of the variety of static media objects can be determined which is a variety of static media objects that are associated with a Viewport are associated in the viewport is shown.

The Presentation period can be the time at which the presentation of the static media object is started, and a display duration of the static media object or the time at which the representation of the static media object is displayed.

In another variation a variety of object identifiers with a viewport identifier be associated.

In In another variation, a receiving unit can also have a processor include an object identifier of each static Media object in the broadcast session will be delivered, associated with a viewport identifier. The recipient can be customized, application semantics, the the broadcast session and at least one display area for displaying a static Describe media object received. As previously described, the Semantics an association of each display area with create a viewport identifier.

Furthermore the display area can be identified by an association of the identifier of the static media object identified with a viewport identifier become.

In The processor can be adapted to a further variation static media object with an object identifier dynamic to associate.

According to another variation, the processor can be adapted, data from an association tion file contained in a file transfer table instance of the transfer session to associate the static media object with a viewport.

The Data in the association file can z. B. available in a format be put that a character that does not encode the data is used as a separator.

In The processor can be adapted to a further variation static media object with a display area based on Information contained in a file transfer table instance the broadcasting session are included to associate.

Furthermore, according to a further exemplary variation of the receiving device, the processor can be adapted to a location of the static Media object and the identifier of the static media object from a file element of a file transfer table instance the broadcasting session to extract.

The Receiving device can e.g. B. also a memory for storing of each static media object received, its object identifier, its associated viewport identifier and its Presentation period in a buffer of the receiving device include.

In Another variation of the receiving device can be the processor further adjusted are based on the presentation period of a determine each of the variety of static media objects a variety of static media objects with a viewport are associated in the display area.

How executed above, The presentation period can be the time at which the presentation of the static media object is started, and a display duration of the static media object or the time at which the representation of the static media object is displayed.

Furthermore, in a further variation, a transmission device can further comprise a processor that has an object identifier of a static Media object that is sent to the receiving unit in the transmission session is delivered, associated with a viewport identifier. About that in addition, the transmitter can be customized, application semantics the broadcast session and at least one display area for displaying a static one Describe, transfer, where the semantics are an association of each display area with a viewport identifier, and the display area by an association of the identifier of the static media object identified with a viewport identifier becomes.

Furthermore can the processor e.g. B. be adjusted, the static media object associate dynamically with an object identifier.

In the processor can be adapted to another variation, data to associate the static media object with a display area in an association file in a file transfer table instance the broadcasting session is included to provide, and the transmitter can be adapted to this data to the To send the receiving unit.

In In yet another variation, a computer readable medium can go further Store instructions that, when executed by a processor, a reception of application semantics covering the transmission session and at least one display area for displaying a static one Describe media object, whereby the semantics are an association of each display area with a display area identifier and an association of an object identifier of each static media object, that in the broadcasting session is supplied with a viewport identifier. The display area can e.g. B. by an association of the identifier of the static media object with a viewport identifier be identified.

The computer-readable medium can optionally further store commands which, if executed by a processor, a dynamic one Association of the static media object with an object identifier effect in the transmitter.

In another variation, the association of the static media object with a display area of data in an association file stored in a file transfer table instance of the transfer session is included.

A other alternative variation may be that the association of the static media object with a display area on information based in a file transfer table instance the broadcasting session is included.

Further can it be possible be a location of the static media object and the Identifier of the static media object of the receiving unit in a file element a file transfer table instance the broadcasting session provided.

The computer-readable medium according to another variation continue to store instructions that, when executed by a processor, the storage of each received static media object, its object identifier, its associated viewport identifier and its presentation period effect in a buffer of the receiving unit.

In another optional variation of the computer readable medium can continue to store commands that, when issued by a Processor running a determination of which of a variety of static media objects, that are associated with a display area are displayed in the display area based on the presentation period of each of the plurality of static media objects.

How has been described previously, the presentation period can be the time for which the display of the static media object is started and a presentation time for any static media object or a time at which the representation of the static media object is displayed.

Further a computer readable medium may include means that are customized are to store instructions that, when executed by a processor, an association of an object identifier of each static Media object in a broadcast session is delivered to the receiving unit with a display area identifier and a transfer of application semantics, the the broadcast session and at least one display area for displaying a static Describe media objects, cause, the semantics an association of each display area with a display area identifier provide, the viewport through the association the identifier of the static media object with a viewport identifier is identified.

Furthermore, in a further variation, the computer-readable medium can be adapted be to store instructions that, when executed by a processor, a dynamic association of the static media object with a Effect object identifier.

Claims (28)

Receiving device for presentation at least of a static media object that is transmitted from a sending unit Use a broadcast session transmitted according to the FLUTE (File Delivery over Unidirectional Transport) protocol the receiving unit comprising: a recipient to Receive a static media object and its timing information from the transmitting unit to the receiving unit, the temporal Coordination information in a file element of a file transfer table instance the broadcasting session is delivered, and a display to show the received static media object in a viewport for a through the time coordination information defined presentation period. The receiving device of claim 1, further comprising a processor holding an object identifier of each, in the broadcasting session Static media object to be delivered with a display area identifier associated being the recipient the transfer session has been adapted descriptive application semantics and at least one display area to display a static media object, the Semantics an association of each area of representation produce a viewport identifier, and in which the display area through the association the identifier of the static media object and the viewport identifier is identified. The receiving device of claim 2, wherein the processor is further adapted to the static media dynamically associate an object with an object identifier. The receiving device of claim 2, wherein the processor further adapted is data in a file transfer table instance the broadcasting session get the association file contained to the static media object to associate with a viewport. Receiving device according to claim 4, wherein the data be delivered in the association file in a format that includes a character not used to encode the data as a separator used. The receiving device of claim 2, wherein the processor the static media object with a display area is further adapted based on one in a file transfer table instance the broadcasting session associated information. The receiving device of claim 6, wherein the processor a storage location of the static media object is further adapted and the identifier of the static media object from a file element a file transfer table instance the broadcasting session to extract. Receiving device according to claim 7, further comprising a memory for storing each received media object, its object identifier, its associated viewport identifier, its Presentation period in a buffer of the receiving device. The receiving device of claim 7, wherein the processor is further adapted to decide which of a variety of static Media objects that are associated with a display area is displayed in the display area based on the display period of any static media object. The receiving device of claim 6, wherein the presentation period the time at which the static media object is displayed is started and a display duration for the static media object or a point in time at which the representation of the static media object being stopped indicates. transfer device for transmission at least one static media object attached to a receiving device using a broadcast session transmitted according to the FLUTE (File Delivery over Unidirectional Transport) protocol the transmission unit comprising: a transmitter to send one static media object and its temporal coordination information to the receiving unit, the time coordination information in a file element of a file transfer table instance the broadcasting session is delivered to the receiving unit. transfer device according to claim 11, further comprising a processor having an object identifier everyone, in the broadcasting session Static media object to be delivered with a display area identifier associated the transmitter being adapted to the broadcast session and at least one display area for displaying a static one To send media object descriptive application semantics, where the semantics are an association of each area of representation to a viewport identifier, and in which the display area through the association the identifier of the static media object and the viewport identifier is identified. transfer device of claim 12, wherein the processor is further adapted the static media object associate dynamically with an object identifier. transfer device of claim 12, wherein the processor is further adapted data to associate the static media object with a display area to deliver in an association file that is in a file transfer table instance the broadcasting session is included and the sender is adapted this data to the receiving unit to send. transfer device The claim 14, wherein the data in the association file is in one Format that is not used to encode the data Character used as separator. The transmission device of claim 11, wherein the presentation period is the time at which the presentation of the static media object is started and a presentation period for the static media object or a point in time at which the display of the static media object is stopped. A computer readable medium for storing commands, which, when executed by a processor, cause the processor displays a static media object that is from a Sending unit using a transmission session after the FLUTE (File Delivery over Unidirectional Transport) protocol is through: Receive a static media object and its temporal coordination information from the sending unit to the Receiving unit, the time coordination information in a file element of a file transfer table instance the broadcasting session is delivered, and Represent the static media object received in a display area for a presentation period defined by the time coordination information. The computer readable medium of claim 17, further Storing instructions that, when executed by the processor, a reception of the broadcast session and at least one display area for displaying a static one Media object describing application semantics cause, the semantics an association of each display area with a display area identifier produce, and being the display area through the association the identifier of the static media object and the viewport identifier is identified. The computer readable medium of claim 18, further Storing instructions that, when executed by the processor, a dynamic association of the static media object with a Effect object identifier. The computer readable medium of claim 18, wherein the association of the static media object with the display area by data in a file transfer table instance the broadcasting session Association file contained is reached. The computer readable medium of claim 18, wherein the association of the static media object with a display area on one in a file transfer table instance of the broadcast session Information based. The computer readable medium of claim 21, further Storing instructions that, when executed by the processor, a delivery of location information of the static media object and the identifier of the static media object to the receiving unit in a file element of a file transfer table instance the broadcasting session causes. The computer readable medium of claim 22, further Storing instructions that, when executed by the processor, storage of each received media object, its object identifier, its associated viewport identifier, its Presentation period in a buffer of the receiving unit cause. The computer readable medium of claim 22, further Storing instructions that, when executed by the processor, make a decision which one of a variety of static Media objects that are associated with a display area is displayed in the display area based on the display period of any static media object. The computer readable medium of claim 17, wherein the presentation period the time at which the presentation of the static media object is started and a display duration for the static media object or a point in time at which the representation of the static media object is stopped. A computer readable medium for storing commands, which, when executed by a processor, cause the processor does the transmission at least one static media object that is from a sending unit to a receiving device using a transmission session transmitted according to the FLUTE (File Delivery over Unidirectional Transport) protocol is initiated by Deploy a static media object and its timing coordination information to the sending unit, the time coordination information in a file element a file transfer table instance the broadcasting session is delivered to the receiving unit. The computer-readable medium of claim 26, further storing instructions that, when executed by the processor, are an association of an object identifier of each in the transmission site static media object to be delivered with a display area identifier and a transmission of application semantics describing the transmission session and at least one display area for displaying a static media object, the semantics establishing an association of each display area with a display area identifier, effecting and whereby the display area is identified by the association of the identifier of the static media object and the display area identifier. The computer readable medium of claim 26, further Storing instructions that, when executed by the processor, a dynamic association of the static media object with a Effect object identifier.