JP2005229569A - Uri pointer system and method for transmitting mpeg-4 data by atsc mpeg-2 transport stream file system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a means for transmitting an MPEG-4 data by an MPEG-2 by using the methodology of an existing ATSC MPEG-2. <P>SOLUTION: An MPEG-2TS equipped with a packetized ATSC TSFS is received, and a URI in a TS is discovered. In response to the URI, access is performed to an address such as a lid or an http address. MPEG-4 resources are received from the ATSC TS, and of the MPEG-4 resources are decoded. When a lid URI embedded in an initial object descriptor (IOR) is used to search resources in the TFSF such as a BIFS scene description stream and/or an object descriptor stream, the accessed lidURI provides a binding name and an access scheme to an object in the ATSC TSFS. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates generally to digital image and data transport processes, and more particularly to uniform resource indicator (URI) systems and MPEG-4 data packetized into MPEG-2 transport streams (TS). In addition, the present invention relates to a method of transmission using the American Advanced Television Systems Committee (ATSC) Transport Stream File System (TSFS).

[Related applications]
This application is filed with the Attorney Order No. SLA 1325, filed on September 25, 2003, application no. This is a continuation-in-part of a pending application, invented by Kai-Chan, whose title is a URI pointer system and a method for transmitting MPEG-4 data in an MPEG-2 transport stream.

  Most digital video broadcast systems are based on a common MPEG-2 encoding system, such as, for example, European Digital Video Broadcasting (DVB) and American Advanced Television Systems Committee (ATSC). MPEG-2 provides high resolution video, multi-channel audio, and even features such as innovative new multimedia data and interactive services.

  On the other hand, ISO and IEC have jointly developed ISO / IEC 14496 MPEG-4 as the next-generation audiovisual standard. MPEG-4 has better compression efficiency than MPEG-2, new features such as audio-visual interaction, copyright protection, and other features that can improve digital television broadcasts and realize new applications And provide. Harmonization of MPEG-2 and MPEG-4 technologies based on broadcasting standards such as DVB is important for improving future digital television broadcasting. The harmony between the MPEG-2 broadcast and the MPEG-4 standard must include the harmonization of layers such as the transport layer and the application layer.

  Transport layer alignment is the basis for this effort. Specifically, a means must be found to allow MPEG-4 data elements, including scenes and their associated streams, to be transmitted by the transport layer protocol specified by the MPEG-2 broadcast. MPEG-2 broadcast systems such as European DVB or American ATSC include MPEG-2 transport streams, DSM-CC data carousel, DSM-CC user-to-user (UU) object carousel and the Internet, to name a few. Defines transport protocols including protocols. The MPEG-2 transport stream is the underlying layer for most other protocols. Therefore, transmitting MPEG-4 data using the MPEG-2 transport is an important problem to be solved.

  ISO / IEC specifies a method (known as 4on2) for transmitting MPEG-4 content in an MPEG-2 transport stream in the ISO / IEC13818-1 specification. The MPEG-4 content includes an initial object descriptor such as an object descriptor stream, a scene description stream, an audio stream, a video stream, and an IPMP stream, and a variable number of streams. The specification (ISO / IEC 13818-1) requires that each MPEG-4 stream be included in an SL packetized stream and, optionally, multiplexed in a FlexMux stream. Both packetized streams and FlexMux streams are defined in ISO / IEC 14496-1. The SL packetized stream or FlexMux stream is encapsulated either in an MPEG-2 packetized elementary stream (PES) packet or in ISO_IEC_14496_section before being transport stream packetized and multiplexed.

  ISO / IEC 13818-1 specifies an encapsulation and signaling approach for ISO / IEC 14496 audiovisual scenes and their associated streams transmitted in ISO / IEC 13818-1 transport streams. The procedure is summarized below.

  MPEG-4 content associated with a program transmitted in a transport stream must be referenced by the program map table of that program. The program map table is shown in Table 1.

  An initial object descriptor (IOD) must be used to define an ISO / IEC 14496-1 scene. The initial object descriptor that serves as the initial access point to all associated MPEG-4 streams was placed in a descriptor loop that immediately follows the program_info_length field in the program map table of the program to which the scene is associated. Must be carried by an IOD descriptor.

  The IOD includes an ES_Descriptor that identifies the scene description and object descriptor stream that make up the program. The IOD may also include an ES_Descriptor that identifies one or more associated IPMP or OCI streams, for example.

  The elements of ISO / IEC 14496 content may be carried by one or more ISO / IEC 13818-1 MPEG-2 program elements referenced by a unique PID value in the transport stream.

  Transmitting ISO / IEC 14496 content with a PID is signaled by a stream_type value of 0x12 or 0x13 in the program map table associated with that PID value.

The SL and FMC descriptors must be used to specify an ES_ID for each encapsulated ISO / IEC 14496 stream.

  FIG. 1 is a diagram for explaining a procedure (prior art) for reproducing MPEG-4 content. The above-described procedure for reproducing MPEG-4 content received from the 13818-1 transport according to the ISO / IEC13818-1 specification will be described below.

  1. Obtain an initial object descriptor (IOD) that includes an ES_Descriptor for the BIFS scene stream, object descriptor stream, and so on.

  2. The BIFS ES_Descriptor contains an ES_ID and an optional universal resource locator (URL) for the BIFS stream to be searched. Therefore, there are two methods for searching the BIFS stream.

  a. Use ES_ID and SL_Descriptor. The ES_ID serves as a unique label for elementary streams that fall within the name, and the SL_Descriptor contains the PID for the ES_ID. The BIFS stream can be retrieved from the packet associated with the PID.

  b. Alternatively, if the ES_Descriptor includes a URL, the BIFS stream can be retrieved from the location specified by the URL. The retrieved stream is associated with the ES_ID.

  3. Repeat step 2 for the object descriptor stream.

  4). Assemble a BIFS scene using the retrieved BIFS stream.

  5). Several BIFS nodes are associated with corresponding elementary stream resources via object descriptors. This association is achieved by objectDescriptorID in the object descriptor.

  a. Use objectDescriptorID to locate the object descriptor in the object descriptor stream.

  b. The object descriptor must contain an ES_Descriptor for the elementary stream.

  Repeat step 2. That is, ES_ID or URL is used to search the elementary stream.

  Due to the complexity of specified ISO / IEC procedures, an effective and complete method that can be used, in particular, a method for transmitting MPEG-4 systems over MPEG-2 transport has been described so far. not exist. Therefore, there is a need to define a new method for delivering MPEG-4 content based on the MPEG-2 transport protocol.

  It would be advantageous if a means for transmitting MPEG-4 data in MPEG-2 TS using the existing ATSC MPEG-2 methodology was developed.

  The present invention defines a new method for transmitting MPEG-4 data in ATSC MPEG-2 TS using a uniform reference identifier (URI) and a transport stream file system (TSFS). TSFS is the same as Object Carousel (OC) and is one of the important transports used in MPEG-2 broadcasting. Uniform reference locator (URL) references are defined in the ISO / IEC 13818-1 specification as an alternative approach for transmitting MPEG-4 data, but specific means for using URLs are: It is not defined in the specification. The present invention defines the means and proposes a solution that is fully compatible with the ISO / IEC13818-1 standard. This solution is flexible and efficient in incorporating and associating MPEG-4 components within the MPEG-2 broadcast infrastructure. Furthermore, the original ISO / IEC method and the newly invented method can be used simultaneously. The receiver can also choose to cache the captured data to speed up the acquisition process and improve the playback of the data. In summary, the present invention transmits MPEG-4 data including scenes and associated streams by harmonizing the MPEG-2 and MPEG-4 standards and using the ATSC MPEG-2OC transport protocol. To achieve an approach.

  Accordingly, a URI pointer method is provided to reference MPEG-4 data resources transmitted in the American ATSC MPEG-2 TSFS. The method receives an MPEG-2 TS with a packetized ATSC TSFS; locates a URI in the TS; accesses an address such as a local identifier (lid) or http depending on the URI; In response to accessing the MPEG-4 resource from the ATSC TSFS; and decoding the MPEG-4 resource.

  The accessed lid URI is used to locate resources in the TSFS, such as the BIFS scene description stream and / or the object descriptor stream, using the embedded URI in the initial object descriptor (IOD). Provides a binding name and access scheme. Receiving an MPEG-2 TS with a packetized ATSC TSFS means that an MPEG-4 resource is formed in the hierarchical directory structure of the BIOP object including DSM :: ServiceGateway, DSM :: Directory and DSM :: File. Means.

  The retrieved MPEG-4 resource may be audio, video and / or system data. Furthermore, if the MPEG-4 audio / video stream is embedded in MPEG-2 TS according to the ISO / IEC 13818-1 encapsulation standard, the method can be used to access MPEG-4 audio / video data. . The method further uses an MPEG-2 methodology to retrieve an MPEG-4 audio / video stream from an MPEG-2 TS and is retrieved from an ATSC TSFS along with the retrieved MPEG-4 audio / video stream. Have the resources decoded.

  A receiver and broadcast apparatus using the above-described method and a URI pointer system for accessing pointers to MPEG-4 data in MPEG-2TS will be described in detail below.

  FIG. 2 is a schematic block diagram of a uniform resource identifier (URI) pointer system in accordance with the present invention for accessing MPEG-4 data from the MPEG-2 Transport Stream File System (TSFS) of the American Advanced Television Systems Committee (ATSC). is there. System 200 includes a receiver 202 having an interface for line 204 to accept MPEG-2 TS with a URI embedded with a packetized ATSC TSFS. Note that although the figure shows a single TS, multiple TSs are also received. Note also that the URI is typically not embedded in the ATSC TSFS. Address access unit 206 has an interface for line 204 to accept MPEG-2 TS from receiver 202. The address access unit 206 (AAU) locates the URI in the TS, accesses the address, and retrieves the MPEG-4 resource from the ATSC TSFS. Decoder 208 has an interface for line 210 coupled to address access unit 206 for receiving MPEG-4 resources and an interface for line 212 for supplying decoded MPEG-4 information. .

  In the context of the present invention, the address access unit 206 looks up a URI, such as an http address or a local identifier (lid). Typically, the lid address is accessed. However, it is possible to use the http address as lid. That is, if a file is indexed with an http address, http can be used to access the file in TSFS. The advantage of using an http address as the lid address is that if for some reason the ATSC TSFS is not available or inconvenient, the system 200 can choose to access the website as a backup, for example.

  As URIs are formed, they are embedded in the MPEG-2 TS. These formed URIs are used to build an MPEG-4 system. The MPEG-4 system can also include interactive scenes with all kinds of pointers to various audio / video / graphic objects (resources) such as URIs. The URI can refer to resources (audio, video, system data) that already exist in the cache, embedded in the broadcast transport using OC, or located at a remote site.

  A codec system typically includes system data resources, video resources, and audio resources. In MPEG-4, the system data portion is used to assemble an interactive audiovisual scene. A scene consists of many objects (having different shapes) such as audio, video, graphics, html, etc. One example is a house scene consisting of sofa objects, chair objects, table objects, and the like. Since the MPEG-4 system is used to assemble interactive scenes, the MPEG-4 system is needed even if the scene contains only one object.

  FIG. 3 is a diagram showing a procedure for accessing MPEG-4 resources using lid URI. The lid URI provides a binding name and access scheme for objects in the ATSC TSFS. More specifically, the address access unit uses a lid URI embedded in an initial object descriptor (IOD) to locate a resource in the ATSC TSFS. The BIFS scene description stream and the object descriptor stream are shown accessed.

  FIG. 4 is a diagram showing a BIOP directory and file objects. As can be seen in the figure, the address access unit is in the hierarchical directory of the Broadcast Inter-Object Request Broker Protocol (BIOP) including DSM :: ServiceGateway, DSM :: Directory and DSM :: File. Access MPEG-4 resources.

  FIG. 5 is a diagram illustrating a simple ATSC TSFS file structure. Note that SG is the Service Gateway, D is the Directory, and F is the File. The address access unit retrieves MPEG-4 resources from the ATSC TSFS as follows. First, a DSI message is located. DSI is DownloadServerInitiate (). DSI is a message used for TSFS (and DSMCC OC), and broadcasts IOR (a kind of pointer) of Service Gateway (file system root directory). Next, an interoperable object reference (IOR) for the Service Gateway is extracted. When the IOR of the SG is extracted from the DSI, the SG is found and searched. The Service Gateway object is parsed and the IOR for the Directory and File objects is extracted from the Service Gateway binding structure. Finally, MPEG-4 resources are obtained from the File object.

  FIG. 6 is a diagram illustrating an example of a TSFS file directory.

  Returning to FIG. 2, the address access unit searches the ATSC TSFS for MPEG-4 resources including audio data, video data, and system data. With these resources, the decoder 208 can provide MPEG-4 information, such as enhanced audio data in MPEG-2TS and / or enhanced video data in MPEG-2TS. System data is used to establish interactive audiovisual scenes and communication links. However, stream data cannot be transmitted by ATSC TSFS. In some aspects of the system, the receiver 202 further receives an MPEG-4 TS audio / visual stream embedded in MPEG-2 TS according to the ISO / IEC 13818-1 encapsulation standard. Then, the address access unit 206 supplies the audio / visual stream retrieved from the MPEG-2 TS. The MPEG-2 decoder 214 has an interface for the line 210 for accepting the retrieved MPEG-4 audio / visual stream and follows the ISO / IEC 13818-1 encapsulation method for transmitting MPEG-4 streams in MPEG-2 TS. And an interface for line 218 for supplying decoded MPEG-4 audio / visual information.

  It should be understood that URI and MPEG-4 resources do not necessarily have to be transmitted in the same TS. In some aspects, the receiver 202 receives a first MPEG-2 TS with a first MPEG-2 TS and a packetized ATSC TSFS. The address access unit 206 retrieves the lid URI from the first MPEG-2 TS and retrieves the MPEG-4 resource from the ATSC TSFS in the second MPEG-2 TS. It should be understood that the first and second TS need not be received simultaneously. In another aspect, both TSs carry ATSC TSFS packetized with embedded MPEG-4 resources. The URI in the first TS is then used to search for MPEG-4 resources in both the first and second TS.

  In other aspects, the system 200 further comprises a transmitter 220 having a transmission interface for the line 222. Transmitter 220 and receiver 202 are used to form an interactive audiovisual scene and communication link in response to decoding MPEG-4 system data.

  In another aspect, the system further includes a local cache 224 having an interface for line 210 to receive MPEG-4 resources retrieved from storage. These resources can be accessed using a subsequently received URI in the TS or a subsequently received URI in the same TS. For example, the address access unit 206 can access a local cache address or web protocol identifier instead of or in addition to a lid address. Then, the MPEG-4 resource is retrieved from the local cache 224 in response to accessing the local cache address. If ATS 206 does not have to build the entire directory each time new ATSC TSFS data is received at the TS, it will keep processing resources. Alternatively, a web protocol identifier or http address is used to access MPEG-4 resources from a web site connected to the network.

  FIG. 7 is a schematic block diagram of a URI pointer system according to the present invention for accessing MPEG-4 data in the American ATSC MPEG-2 TSFS in an MPEG-4 broadcasting apparatus. The system 600 provides a URI for accessing MPEG-4 resources embedded in the ATSC TSFS to the MPEG-2 TS, and an address having an interface for the line 604 to supply the packetized ATSC TSFS to the MPEG-2 TS. A pointer unit (APU) 602 is included. The APU 602 receives the encoded MPEG-2 TS and MPEG-4 resources via the line 605. In some aspects, the same TS transmits both URI and ATSC TSFS. The transmitter 606 has an interface for line 604 to accept MPEG-2 TS along with ATSC TSFS packetized from address pointer unit 602. The transmitter 606 has an interface related to the line 608 for broadcasting MPEG-2 TS.

  The APU 602 supplies either the http address or the lid URI to the MPEG-2 TS. As noted above, in some aspects, the http address is used as the lid to access MPEG-4 resources in the ATSC TSFS (if the resource file is properly labeled). As such, APU 602 generates a lid URI to provide the binding name and access scheme to the objects in the ATSC TSFS. That is, the APU 602 generates a lid URI embedded in the initial object descriptor (IOD) to locate the BIFS scene description stream and / or object descriptor stream resource in the ATSC TSFS (see FIG. 3).

  The APU 602 embeds MPEG-4 resources in the ATSC TSFS by forming MPEG-4 resources in the hierarchical directory structure of the BIOP object including DSM :: ServiceGateway, DSM :: Directory and DSM :: File (see FIG. 4). ). The APU 602 embeds MPEG-4 resources in the ATSC TSFS as follows: MPEG-4 resources are loaded into the File object; IORs are created for the Directory and File objects; IOR is bound in the Service Gateway An IOR is created for the Service Gateway; the Service Gateway IOR is located in the DSI message (see FIG. 5).

  Typically, APU 602 embeds MPEG-4 resources such as audio, video and system data in ATSC TSFS. When the stream data is broadcast, the APU 602 further embeds the MPEG-4 audio / video stream in the MPEG-2 TS according to the ISO / IEC13818-1 encapsulation standard. The transmitter 608 broadcasts an MPEG-2 TS with an embedded MPEG-4 audio / video stream.

  In some aspects, the APU 602 locates the lid URI in the first MPEG-2 TS and embeds the MPEG-4 resource in the ATSC TSFS packetized in the second MPEG-2 TS. Then, the transmitter 608 broadcasts the first and second MPEG-2 TS. As noted above, the transmitter 608 need not necessarily broadcast the first and second TSs simultaneously. In addition, the URI in the first TS points to a resource in one or more TSs (with packetized ATSC TSFS).

  In another aspect, the APU 602 is embedded in an MPEG-2 TS, such as an http address and a local (receiver) cache address, to access MPEG-4 resources from a web site and a local (receiver) cache, respectively. Generate additional URI addresses.

[Feature Description]
Returning to FIG. 3, it should be noted that although not shown, an object descriptor may have a URI pointing to another object descriptor somewhere else. The new object descriptor is referenced and associated with the objectDescriptorID of the original object descriptor that carries the URI string. This technique can be applied to both elementary streams and object descriptors. In the following description, an elementary stream is used as an example. However, the same analysis applies equally well to object descriptors. As explained above, two methods have been promoted to retrieve elementary streams: (1) via the ES_ID for packets transmitted on the transport and the PID associated with it; 2) The process of the present invention that uses a URI to reference a stream transmitted elsewhere, such as over an IP network. However, the URI means is not defined in ISO / IEC13818-1. The present invention defines URL reference means for accessing resources in a broadcast file system over the Internet and resources in local memory.

[URI, URL and local identifier (lid :) URI scheme]
The Universal Resource Identifier (URI) document defines a simple, unified, and extensive mechanism for identifying resources. The URI is a superset of URLs and is not limited to existing Internet protocols. The present invention uses a lid scheme for URI reference. The lid scheme was originally designed to identify HTML pages and graphic files transmitted by unidirectional means such as television broadcast, as defined in SMPTE 343M-2002. Using the lid scheme with broadcast transport, the return channel does not need to access resources (MPEG-4 scenes and associated streams) over the Internet. It becomes easier for the receiver to associate the relevant program elements from time to time. More specifically, the present invention uses a lid scheme with an ATSC TSFS broadcast system.

[ATSC TSFS]
First, MPEG-4 resources must be organized into a broadcast transport, with each resource having a unique URI. The ATSC Transport Stream File System (TSFS) provides such a means. Specifically, ATSC TSFS provides a file system in transport so that URI schemes can reference specific resources. TSFS is based on the object carousel protocol defined in ISO / IEC 13818-6 DSM-CC.

  TSFS uses BISM objects of the types DSM :: ServiceGateway, DSM :: Directory and DSM :: File shown in FIG. Each BIOP object has its own object key and type information (directory, file or service gateway) in the header. Each BIOP object has an additional objectInfo structure that provides information such as a file size, a content type (MIME type), and a time stamp according to the type of the BIOP object. The body of the DSM :: File object is file content. The body of a DSM :: ServiceGateway or DSM :: Directory object consists of a list of bindings. The binding includes a binding name, an object type (directory, file, or service gateway) of the referenced object, and an IOP :: IOR (Common Object Reference) that provides the location of the referenced object. IOP :: IOR is often referred to as IOR.

  The DSM :: ServiceGateway object is similar to the DSM :: Directory object. The only difference between the two objects is the binding name syntax. For DSM :: ServiceGateway objects, the name is always the base URI, and for DSM :: Directory objects, the name is a relative path. Each TSFS always has one service gateway object that serves as the top-level directory of the TSFS. Starting from the service gateway, an object in TSFS can be reached by following a directory path, ie a series of directory links. Objects in TSFS can be referenced from multiple directories, so there may be multiple paths from the service gateway to the object.

  FIG. 5 shows an example of a procedure for acquiring all objects in TSFS with a simple hierarchical directory structure. First, the IOR of the service gateway object is extracted from the DSI message. Given the service gateway IOR, the service gateway object is parsed from the data module carrying the IOR. The IOR of the directory object D0 and the file object F2 is extracted from the binding structure inside the service gateway object. When the IOR of F2 is given, the file data of F2 is acquired from the data module transmitting the F2 object. Given the IOR of D0, the directory object D0 can be extracted, and the IORs of F0 and F1 can be obtained from the directory object D0. Similarly, when the IOR of F0 and the IOR of F1 are given, the file data of F0 and F1 are acquired. Therefore, the IOR of the objects in the directory structure is obtained in the order of IOR-SG, IOR-D0, IOR-F2, IOR-F0, and IOR-F1. Once the IOR of the object is obtained, the object is then retrieved from the corresponding data module.

  Note that TSFS objects are usually transmitted on a single virtual channel. However, it is possible to have bindings that contain references to objects in other TSFS (often referred to as “soft links”) that may exist in the same or different virtual channels. These other TSFSs may be on the same or different virtual channels. If the TSFS is in a different virtual channel, it may be in the same transport stream or not in the same transport stream. Thus, the TSFS logical name space can span multiple virtual channels and may even span multiple transport streams. An IOP :: IOR that references an object that exists in a different TSFS must identify the TSFS that contains the object and provide a directory path in that TSFS that leads from the TSFS service gateway to the object.

[Save ATSC TSFS]
The receiver can choose to cache all or part of the directory and file objects in its local storage and set up a URI index to the objects. Then, any object can be obtained very quickly from local memory without having to examine all TSFS in the broadcast transport. The URI can also refer to resources in the local file system that do not originate from the downloaded TSFS.

[Integrated lidURI scheme and ATSC TSFS]
The lidURI scheme can be used to access a broadcast transport or memory resource in the receiver. ATSC TSFS is used to provide a unique URI for each resource transmitted. Thus, both reference and carriage MPEG-4 program elements in the organized file system of the MPEG-2 transport can be accomplished. The following possibilities exist:

Resources (MPEG-4 scenes and associated streams) can be carried in the same TSFS. In general, stream type resources are not supported by TSFS. However, it is possible to carry a short stream like a file in MPEG-4 system data. Large, continuous streams are not included in relatively small system data files.
• Resources in different TSFS can be carried on the same virtual channel.
-Resources in TSFS of different virtual channels may or may not be carried in the same transport stream.
• Resources can be stored in a local cache.

[Other URI schemes in TSFS]
The present invention mainly uses the lid scheme for reference resources in the broadcast transport, but can also be used to access URI scheme http addresses. Only the binding name of DSM :: ServiceGateway is required as the base (absolute) URI, like the DCM-CC object carousel to which the ATFS TSFS is related. The base URI can be either lid or http. However, the base URI can be other address types. However, there are some differences when using and analyzing different URI schemes. If only the lid URI is available in the broadcast stream, the lid URI is “should” be used to label the broadcast resource. If an http URI can also be obtained at the web server, the http URI should be used to label the broadcast resource. If httpURI is used, a receiver with limited cache space and Internet connection can save resources labeled with lidURI, but not resources labeled with httpURI.

  When parsing a lid reference, the receiver can first look for a resource in the cache. If the resource is not found, the receiver may simply notify that the resource is not available or wait for the resource to appear in the broadcast stream. If a resource does not appear after a certain period of time, the receiver may time out and notify that no resource is available.

  When parsing an httpURI reference, the receiver can first look for a resource in the cache. If a resource is not found and the receiver has an Internet connection, it can look for resources on the Internet and monitor the appearance of resources in the broadcast stream at the same time. If the receiver cannot find the resource in any case, the receiver may time out after a certain period of time and notify that the resource cannot be obtained.

  FIG. 8 is a flowchart illustrating the URI pointer method of the present invention for referring to MPEG-4 data resources transmitted in American ATSC MPEG-2 TSFS. The method is shown as a series of numbered steps for clarity, but the order should not be inferred from the numbers unless explicitly stated. It should be understood that some of these steps may be skipped, performed in parallel, or performed without maintaining a strict order. The method starts at step 700.

  Step 702 receives an MPEG-2 TS comprising a packetized ATSC TSFS. Step 704 locates the URI in the TS. Step 706 accesses the address according to the URI. Typically, access to the address in step 706 includes access to a local identifier (lid) and / or an http address. Step 708 retrieves MPEG-4 resources from the ATSC TSFS in response to access to the address. Step 710 decodes the MPEG-4 resource. In one aspect, step 712 caches the retrieved MPEG-4 resource.

  In some aspects of the method, access to the address in step 706 includes access to a lid URI that provides a binding name and access scheme to objects in the ATSC TSFS. More specifically, the lid URI embedded in the initial object descriptor (IOD) is used to locate resources in the TSFS, such as a BIFS scene description stream and / or an object descriptor stream.

  Receiving the MPEG-2 TS with the ATSC TSFS packetized at step 702 includes forming MPEG-4 resources in the hierarchical directory structure. That is, the hierarchical directory structure is formed of BIOP objects including DSM :: ServiceGateway, DSM :: Directory, and DSM :: File.

  In some aspects, retrieving MPEG-4 resources from the ATSC TSFS in step 708 includes substeps. Step 708a locates the DSI message. Step 708b extracts the IOR for the Service Gateway. Step 708c parses the Service Gateway object. Step 708d extracts the IOR for the Directory object and the File object from the Service Gateway binding structure. Step 708e obtains MPEG-4 resources from the File object.

  Typically, retrieving MPEG-4 resources from the ATSC TSFS in step 708 includes retrieving selected MPEG-4 resources from the grame including audio data, video data, and system data. Also, the decoding of MPEG-4 resources in step 710 can enhance audio data in MPEG-2TS, enhance video data in MPEG-2TS, or establish an interactive audiovisual scene and communication link. Including operations such as using system data to In one aspect, an additional step 714 establishes an interactive audiovisual scene and communication link in response to the decoded MPEG-4 system data.

  To receive the stream data, step 702 further receives an MPEG-4 audio / video stream embedded in the MPEG-2 TS according to the ISO / IEC 13818-1 encapsulation standard. The method then further comprises a step 709 of retrieving an MPEG-4 audio / video stream from the MPEG-2 TS. In this case, decoding the MPEG-4 resource at step 710 includes decoding the retrieved resource from the ATSC TSFS along with the retrieved MPEG-4 audio / video stream.

  In some aspects, receiving the MPEG-2 TS with the packetized ATSC TSFS at step 702 includes the first MPEG-2 TS and the second MPEG-2 TS with the packetized ATSC TSFS. Including receiving. And locating the URI in the TS at step 704 includes retrieving the lid URI in the first MPEG-2 TS, and retrieving the MPEG-4 resource from the ATSC TSFS at step 708 includes: Including retrieving MPEG-4 resources from the second MPEG-2TS ATSC TSFS.

  In one aspect, accessing the address in response to the URI in step 704 further includes accessing an address, such as a local cache address and / or a web protocol identifier. A further step 716 then retrieves MPEG-4 resources from a source selected from the group including the local cache and / or website in response to access to that address.

  FIG. 9 is a flow chart illustrating the URI pointer method of the present invention for broadcasting a pointer to MPEG-4 data present in the American ATSC MPEG-2 TSFS. The method starts at step 800. Step 802 embeds MPEG-4 resources in the ATSC TSFS. Step 804 packetizes the ATSC TSFS into MPEG-2 TS. Step 806 generates a URI for accessing an MPEG-4 resource located at an address in the ATSC TSFS. Step 808 embeds the URI in the MPEG-2 TS. Step 810 broadcasts the MPEG-2 TS along with the packetized ATSC TSFS.

  Typically, step 806 generates a URI, such as an http address and / or a local identifier (lid). In one aspect, an additional step 807 generates additional URI addresses, such as each http address and local (receiver) cache address for accessing MPEG-4 resources from the website and local (receiver) cache. To do.

  In one example of step 806, a lid URI may be generated to supply a binding name or access scheme to an object in the ATSC TSFS. In addition, the generated lid URI can be embedded in an Initial Object Descriptor (IOR) to locate resources in the ATSC TSFS, such as a BIFS scene description stream and / or an object description stream.

  Embedding the MPEG-4 resource in step 802 into the ATSC TSFS includes forming an MPEG-4 resource hierarchy directory structure for the BIOP object that includes DSM :: ServiceGateway, DSM :: Directory and DSM :: File. . In some aspects, step 802 includes substeps. Step 802a loads the MPEG-4 resource into the File object. Step 802b generates an IOR for the DirectoryObject and FileObject. Step 802c binds the IOR to ServiceGateway. Step 802d generates an IOR for the ServiceGateway. Step 802e locates that ServiceGatewayIOR in the DSI message.

  In one aspect, embedding MPEG-4 resources in the ATSC TSFS (step 802), enhancing audio data in MPEG-2 TS, enhancing video data in MPEG-2 TS, and / or Including embedding MPEG-4 resources such as audio data, video data and / or system data that may be used for purposes such as system data to establish a communication link with an interactive audiovisual scene.

  In another aspect, step 803 embeds an MPEG-4 audio / video stream in MPEG-2 TS according to the ISO / IEC 13818-1 encapsulation standard. Step 810 then broadcasts the MPEG-2 TS along with the embedded MPEG-4 audio / video stream.

  In another aspect, embedding that URI in the MPEG-2 TS in step 808 includes locating the lid URI in the first MPEG-2 TS, and in the MPEG-2 TS in step 808 Packetizing the ATFS TSFS includes packetizing MPEG-4 resources in the ATSC TSFS transmitted in the second MPEG-2 TS. Step 810 broadcasts the first and second MPEG-2 TS.

  Systems and methods have been provided for using URIs embedded in MPEG-2 TS to access MPEG-4 resources with ATSC TSFS. Several examples have been presented to illustrate how URIs can be used, but these examples are not exhaustive. Similarly, some examples have been given to illustrate locating MPEG-4 resources, but other ways are possible. Those skilled in the art can devise various other embodiments.

It is a figure explaining the procedure which reproduces | regenerates MPEG-4 content (prior art). FIG. 2 is a schematic block diagram of a URI pointer system according to the present invention for accessing MPEG-4 data from the American Advanced Television Systems Committee (ATSC) MPEG-2 Transport Stream File System (TSFS). It is a figure which shows the procedure which accesses MPEG-4 resource using lid URI. It is a figure which shows a BIOP directory and a file object. It is a figure explaining simple ATSC TSFS file structure. It is a figure which shows the example of a TSFS file directory. 1 is a schematic block diagram of a URI pointer system according to the present invention for accessing MPEG-4 data in American ATSC MPEG-2 TSFS in an MPEG-4 broadcast device. FIG. 6 is a flowchart illustrating a URI pointer method according to the present invention for referring to MPEG-4 data resources transmitted in the American ATSC MPEG-2 TSFS. FIG. 6 is a flowchart illustrating a URI pointer method according to the present invention for broadcasting a pointer to MPEG-4 data in the American ATSC MPEG-2 TSFS.

Claims (51)

A Uniform Resource Identifier (URI) pointer method for referring to MPEG-4 data resources transmitted in the MPEG-2 Transport Stream File System (TSFS) of the American Advanced Television Systems Committee (ATSC),
Receive MPEG-2 TS with packetized ATSC TSFS,
Find the URI in the TS,
According to the URI, access the address,
In response to accessing the address, retrieve an MPEG-4 resource from the ATSC TSFS;
Decoding the MPEG-4 resource;
A method that has that.   The method of claim 1, wherein accessing an address in response to the URI comprises accessing an address selected from a group including a local identifier (lid) and an http address.   3. The method of claim 2, wherein accessing an address includes accessing a lid URI that provides a binding name and access scheme for objects in the ATSC TSFS.   Using lid URIs to provide binding names and access schemes for objects in the ATSC TSFS uses lid URIs embedded in the initial object descriptor (IOD) to generate BIFS scene description streams and object description streams. 4. The method of claim 3, comprising locating resources in the previous TSFS selected from the containing group.   5. The method of claim 4, wherein receiving an MPEG-2 TS with a packetized ATSC TSFS includes forming MPEG-4 resources in a hierarchical directory structure.   6. The method of claim 5, wherein forming a hierarchical directory structure includes forming a hierarchical directory structure of a BIOP object that includes DSM :: ServiceGateway, DSM :: Directory, and DSM :: File. In response to accessing the address, retrieve an MPEG-4 resource from the ATSC TSFS;
Search for DSI messages
Extract the IOR for the Service Gateway,
Parses the Service Gateway object,
Extract the IOR for the Directory and File objects from the Service Gateway binding structure;
The method of claim 6, wherein an MPEG-4 resource is obtained from the file object. The method of claim 6, comprising:
Receiving an MPEG-2 TS with a packetized ATSC TSFS includes receiving an MPEG-4 audio / video stream embedded in the MPEG-2 TS in accordance with the ISO / IEC 13818-3 encapsulation standard;
The method further comprises:
Retrieving the MPEG-4 audio / video stream from the MPEG-2 TS;
7. The method of claim 6, wherein decoding the MPEG-4 resource comprises decoding a resource retrieved from an ATSC TSFS along with the retrieved MPEG-4 audio / video stream. Receiving an MPEG-2 TS with a packetized ATSC TSFS includes receiving a first MPEG-2 TS and a second MPEG-2 TS with a packetized ATSC TSFS;
Locating a URI in the TS includes retrieving a lid URI in the first MPEG-2 TS;
4. The method of claim 3, wherein retrieving MPEG-4 resources from an ATSC TSFS in response to accessing the lidURI comprises retrieving MPEG-4 resources from a second MPEG-2TS ATSC TSFS.   Retrieving MPEG-4 resources from an ATSC TSFS in response to accessing the address includes retrieving MPEG-4 resources selected from a group including audio data, video data, and system data. The method according to 1.   Decoding the MPEG-4 resource can enhance audio data in the MPEG-2 TS, enhance video data in the MPEG-2 TS, and use system data to create an interactive audiovisual scene and The method of claim 10, comprising processing selected from a group that includes establishing a communication link.   12. The method of claim 11, further comprising establishing an interactive audiovisual scene and communication link in response to decoding the MPEG-4 system data.   The method of claim 1, further comprising caching the retrieved MPEG-4 resource. The method of claim 3, comprising:
Responsive to the URI, accessing an address further comprises accessing an address selected from a group including a local cache address and a web protocol identifier;
The method further comprises:
4. The method of claim 3, comprising retrieving MPEG-4 resources from a source selected from a group including a local cache and a website in response to accessing the address. A Uniform Resource Identifier (URI) pointer method for broadcasting a pointer to MPEG-4 data in the MPEG-2 Transport Stream File System (TSFS) of the American Advanced Television Systems Committee (ATSC), comprising:
Embed MPEG-4 resources in ATSC TSFS,
Packetize the ATSC TSFS into MPEG-2TS;
Generating a URI to access MPEG-4 resources present at an address in the ATSC TSFS;
Embed the URI in MPEG-2TS,
Broadcasting MPEG-2 TS with packetized ATSC TSFS.   The method of claim 15, wherein generating a URI for accessing the MPEG-4 resource comprises generating a URI selected from a group including an http address and a local identifier (lid).   Generating a URI to access an MPEG-4 resource residing at an address in the ATSC TSFS includes generating a lid URI to provide a binding name and access scheme for an object in the ATSC TSFS. Item 17. The method according to Item 16.   To find a resource in the ATSC TSFS, wherein generating a lid URI to supply a binding name and access scheme to an object in the ATSC TSFS is selected from a group including a BIFS scene description stream and an object descriptor stream 18. The method of claim 17, comprising generating a lid URI embedded in the initial object descriptor (IOD).   19. The method of claim 18, wherein embedding MPEG-4 resources in the ATSC TSFS includes forming an MPEG-4 resource hierarchy directory structure.   20. The method of claim 19, wherein forming a hierarchical directory structure includes forming a hierarchical directory structure of BIOP objects including DSM :: ServiceGateway, DSM :: Directory, and DSM :: File. Embedding MPEG-4 resources in the ATSC TSFS
Loading the MPEG-4 resource into a file object;
Creating an IOR for the Directory and File objects;
Binding the IOR in a Service Gateway;
21. The method of claim 20, comprising creating an IOR for the Service Gateway and locating the Service Gateway IOR in a DSI message. 21. The method of claim 20, wherein the method is
Further comprising embedding an MPEG-4 audio / video stream in MPEG-2TS according to ISO / IEC13818-1 encapsulation standard;
21. The method of claim 20, wherein broadcasting an MPEG-2 TS includes broadcasting the MPEG-2 TS with the embedded MPEG-4 audio / video stream. Embedding the URI in the MPEG-2 TS includes locating the lid URI in the first MPEG-2 TS;
Packetizing the ATSC TSFS in MPEG-2 TS includes packetizing the MPEG-4 resource in the ATSC TSFS transmitted by a second MPEG-2 TS;
19. The method of claim 18, wherein broadcasting the MPEG-2 TS includes broadcasting the first and second MPEG-2 TS.   16. The method of claim 15, wherein embedding an MPEG-4 resource in an ATSC TSFS includes embedding an MPEG-4 resource selected from a group including audio data, video data, and system data.   Embedding MPEG-4 resources in the ATSC TSFS is a system for establishing enhanced audio data in the MPEG-2TS, enhanced video data in the MPEG-2TS and interactive audiovisual scenes and communication links 25. The method of claim 24, comprising resources used for a purpose selected from a group that includes data.   Further comprising generating an additional URI address selected from a group including an http address and a local (receiver) cache address for accessing MPEG-4 resources from a web site and a local (receiver) cache, respectively. 15. The method according to 15. A Uniform Resource Identifier (URI) pointer system for accessing MPEG-4 data from the MPEG-2 Transport Stream File System (TSFS) of the American Advanced Television Systems Committee (ATSC), the system comprising:
A receiver having an interface for accepting an MPEG-2 TS with an embedded URI and a packetized ATSC TSFS;
An address access unit having an interface for accepting the MPEG-2 TS from the receiver, the address access unit finds a URI in the TS, accesses an address, and sends an MPEG-4 resource from the ATSC TSFS. The address access unit to search;
A decoder having an interface connected to the address access unit for receiving the MPEG-4 resource and an interface for supplying decoded MPEG-4 information;
Having a system.   28. The system of claim 27, wherein the address access unit locates a selected URI from a group including an http address and a local identifier (lid).   29. The system of claim 28, wherein the address access unit accesses a lid URI that provides a binding name and an access scheme for objects in the ATSC TSFS.   The address access unit uses a lid URI embedded in an initial object descriptor (IOD) to locate a resource in the ATSC TSFS selected from a group including a BIFS scene description stream and an object descriptor stream. 30. The system according to 29.   The system of claim 30, wherein the address access unit accesses MPEG-4 resources in a hierarchical directory.   32. The system of claim 31, wherein the address access unit forms a hierarchical directory structure of BIOP objects including DSM :: ServiceGateway, DSM :: Directory, and DSM :: File. The system of claim 32, wherein the address access unit retrieves MPEG-4 resources from the ATSC TSFS as follows:
Search for DSI messages
Extracting the IOR for the Service Gateway;
Analyzing the Service Gateway object;
Extracting IORs for the Directory and File objects from the Service Gateway binding structure;
The system of claim 32, wherein MPEG-4 resources are obtained from the file object. The receiver further receives an MPEG-4 audio / video stream embedded in the MPEG-2 TS according to the ISO / IEC13818-1 encapsulation standard;
The address access unit provides the audio / visual stream retrieved from the MPEG-2 TS;
Interface for accepting the retrieved MPEG-4 audio / visual stream and decoded MPEG-4 audio / visual stream information according to ISO / IEC13818-1 encapsulation method for transmitting MPEG-4 stream in MPEG-2TS 33. The system of claim 32, comprising an MPEG-2 TS decoder having an interface for providing a signal. The receiver receives a first MPEG-2 TS and a second MPEG-2 TS with packetized ATSC TSFS;
30. The system of claim 29, wherein the address access unit retrieves a lid URI from the first MPEG-2 TS and retrieves an MPEG-4 resource from the ATSC TSFS in the second MPEG-2 TS.   28. The system of claim 27, wherein the address access unit retrieves an MPEG-4 resource selected from a group including audio data, video data, and system data.   The decoder uses the system data to enhance audio data in the MPEG-2TS, enhance video data in the MPEG-2TS, and establish an interactive audiovisual scene and communication link. 37. The system of claim 36, wherein the system supplies MPEG-4 information selected from a group comprising: Furthermore, it has a transmitter having a transmission interface,
38. The system of claim 37, wherein the transmitter and receiver form an interactive audiovisual scene and communication link in response to decoding MPEG-4 system data.   28. The system of claim 27, further comprising a local cache having an interface for receiving retrieved MPEG-4 resources for storage.   The address access unit accesses an address selected from a group including a local cache address and a web protocol identifier, and is selected from a group including a local cache and a network-connected web site in response to accessing the address. 30. The system of claim 28, wherein MPEG-4 resources are retrieved from different sources. A uniform resource identifier (URI) pointer system for accessing MPEG-4 data in the MPEG-2 Transport Stream File System (TSFS) of the American Advanced Television Systems Committee (ATSC) in an MPEG-4 broadcasting apparatus, The system
An address pointer unit (APU) having an interface for supplying MPEG-2 TS with a URI for accessing MPEG-4 resources embedded in ATSC TSFS and supplying the packetized ATSC TSFS to MPEG-2 TS; ,
A transmitter having an interface for accepting the MPEG-2 TS with the packetized ATSC TSFS from the address pointer unit and an interface for broadcasting the MPEG-2 TS;
Having a system.   42. The system of claim 41, wherein the APU provides an MPEG-2 TS with a URI selected from a group including an http address and a local identifier (lid).   43. The system of claim 42, wherein the APU generates a lid URI for providing a binding name and access scheme to objects in the ATSC TSFS.   44. The APU generates a lid URI embedded in an initial object descriptor (IOD) to locate a resource in the ATSC TSFS selected from a group including a BIFS scene description stream and an object descriptor stream. The described system.   45. The system of claim 44, wherein the APU embeds MPEG-4 resources in the ATSC TSFS by forming MPEG-4 resources in a hierarchical directory structure.   46. The method of claim 45, wherein the APU forms a hierarchical directory structure of BIOP objects including DSM :: ServiceGateway, DSM :: Directory, and DSM :: File. The system of claim 46, wherein the AUP embeds MPEG-4 resources in the ATSC TSFS as follows:
Load the MPEG-4 resource into a file object,
Create an IOR for the Directory and File objects,
Bind the IOR in the Service Gateway,
Create an IOR for the Service Gateway,
47. The system of claim 46, wherein the system locates the Service Gateway IOR in a DSI message. The AUP further embeds an MPEG-4 audio / video stream in MPEG-2TS according to ISO / IEC13818-1 encapsulation standard,
49. The system of claim 46, wherein the transmitter broadcasts the MPEG-2 TS with the embedded MPEG-4 audio / video stream. The AUP locates the lid URI in the first MPEG-2 TS, embeds the MPEG-4 resource in the ATSC TSFS packetized in the second MPEG-2 TS,
43. The system of claim 42, wherein the transmitter broadcasts the first and second MPEG-2 TS.   42. The system of claim 41, wherein the AUP embeds MPEG-4 resources in an ATSC TSFS selected from a group including audio, video and system data.   The AUP is embedded in the MPEG-2 TS, selected from a group including an http address and a local (receiver) cache address for accessing MPEG-4 resources from a web site and a local (receiver) cache, respectively. 42. The system of claim 41, wherein the system generates an additional URI address.

Images