KR100602388B1 - Resource Reference Method of MPEG - 21 Multimedia Framework - Google Patents

Abstract

The present invention discloses a resource reference method in the MPEG-21 multimedia framework. The present invention extends the ISO file format in MPEG-21 to refer to a desired media such as audio or video of Metabox's Extended Markup Language (XML) document, thereby referring to only a part of the media or a specific part in time. Each metabox and metabox for the ISO file format in order to be able to refer to only a portion of the numerous media that can be stored in the track box of the ISO file format in order to provide a resource reference method in MPEG-21. Define the values in using XML Schema. In this state, when the consumer requests the web page and data, the server analyzes the MPEG 21 file format, finds the meta box, and if it exists, parses the digital item declaration (DID) in the meta box to audio, video, XML, etc. Stores a list of resources and sends them to the consumer, when the consumer requests a particular resource, requests the resource from the server that stores the resource, the server recognizes it, parses the URL, and if the resource exists, We propose a resource reference method in MPEG-21 for transmitting to a service.

Accordingly, since the present invention can receive and consume only a part of media provided by a server or a specific part in time, the consumer can have various effects for editing, review, or various commercial purposes.

Description

Resource Reference Method of MPEG-21 Multimedia Framework

1 is an explanatory diagram showing a conventional standardized ISO file storage format.

2 is a flowchart illustrating a resource reference method in the MPEG-21 multimedia framework according to the present invention.

The present invention relates to a resource reference method in the MPEG-21 multimedia framework.

As is well known, many elements that make up the underlying infrastructure for the delivery and consumption of multimedia content are required to refer to resources in the MPEG-21 multimedia framework for standardization of integrated technologies and element technologies necessary for e-commerce of certain digital contents. The most commonly used method is to use a universal resource locator (URL). This method is the most commonly used method with the spread of the Internet. This standardized ISO file storage format is shown in FIG. According to this, only the entire media can be referred to by the URL, and there is a problem in that it is impossible to refer to only a part of the media constituting the media or a specific part in time.

Therefore, it is necessary to play the media as a whole in order to see the necessary part, and it is impossible to refer to a certain time interval or a specific part of a specific time zone. Accordingly, there has been an inefficient problem that requires a lot of time for media editing and review in the studio.

An object of the present invention is to expand the ISO file format in MPEG-21 and refer to a desired media such as audio or video of Meta Box Extended Markup Language (XML) document in order to solve this problem. It is to provide a resource reference method in MPEG-21 that can refer to only a specific part in time.

In order to achieve this object, the present invention uses XML values in the respective metabox and metabox for the ISO file format to refer to only a part of the numerous media that can be stored in the track box of the ISO file format. Defined using schema. In this state, when the consumer requests the web page and data, the server analyzes the MPEG 21 file format, finds the meta box, and if it exists, parses the digital item declaration (DID) in the meta box to audio, video, XML, etc. Stores a list of resources and sends them to the consumer, when the consumer requests a particular resource, requests the resource from the server that stores the resource, the server recognizes it, parses the URL, and if the resource exists, In this paper, we propose a resource reference method in MPEG-21 for transmitting to a mobile service.

Accordingly, in the present invention, since a consumer can consume only a portion of media provided by a server or a specific portion in time, the consumer can easily edit or review the media.

In addition, the present invention may be utilized for commercial purposes by providing a part of the media provided by the server in a so-called "teaser", or by providing only audio or video only according to the client's terminal type, so that it can be used for a purpose. It has a useful effect.

Referring to the present invention in more detail with reference to the accompanying drawings as follows.

2 illustrates a service concept using a resource address according to the present invention.

As can be seen from the present invention, the first step of assigning the storage space to the client used by the consumer, the step of connecting to the server via the Internet or LAN (100), the client the web page or various Receiving a data request for the media (101); inputting (104) a corresponding MPEG21 file obtained from an internal database or an external server in response to the data request (104); and analyzing such MPEG21 file format Step 104 of searching for additional data such as audio, video, XML, and the like by searching for a metabox included in the file in the file format analysis step; and ending if no metabox exists (106). Parsing DID XML in the metabox (108), storing the parsed resource list (109), and storing the stored resource list. And a step 110 of transmitting a large client,

The client requests a specific resource (111) by viewing a list of transmitted resources, redirects (redirection) a request for a resource to another server storing the requested specific resource, or receives a URL of the specific resource directly requested by the server. Parsing (113), determining whether the resource exists (114); if the resource does not exist, transmitting (115) an absent message to the client; and wherein the resource exists In this case, step 116 is transmitted to the resource data corresponding to the client.

In the process as shown above, when the web page and the media data is requested, the format analysis of the MPEG21 file is performed by the server, and if the meta box exists by searching for the meta box included therein, the DID in the meta box is present. By parsing the XML to obtain a list of resources and sending them to the client, the consumer can see what is displayed on the client's monitor and request the resource to be provided with that type of resource.

At this time, the list for requesting the resource is transmitted to the client as described above.

According to the requested specific resource list, the server requests a resource, parses a URL, and if the resource exists, provides a service to a client requesting the specific resource.

For example, an example of requesting a desired resource using an XML path (XPath) in a URL is as follows.

Domain name / resource pathoffset = number & xpath = XPath

Where domain name is the address of the server, resource path is the location of the resource on the server, offset is the starting number of the mp4 stream in the media file, and xpath is mp4 Represents an XPath when interpreting a stream into the schema given earlier.

Therefore, in the case of requesting the entire resource in the mp4 stream with offset of 100 in the stream whose domain name is www.pixtree.com and the resource path is example.mp21, it can be expressed as in the following example 1).

 www.pixtree.com/example.mp21?offset=100 ---- Example 1)

In addition, when a first track in an mp4 stream having an offset of 100 is requested in a stream having a domain name of www.pixtree.com and a resource path of example.mp21, it can be expressed as in the following example 2).

www.pixtree.com/example.mp21?offset=100&xpath=/moov/track[1] ---- Example 2)

In addition, in the case where the domain name is www.pixtree.com and the resource path is example.mp21, only the video in the mp4 stream having an offset of 100 may be expressed as in Example 3).

www.pixtree.com/example.mp21?offset/100&xpath=/moov/track/mdia/hdlr[@handlertype="vide "] ---- Example 3)

When only the audio in the mp4 stream having an offset of 100 is requested in the stream whose domain name is www.pixtree.com and the resource path is example.mp21, it can be expressed as in the following example 4).

www.pixtree.com/example.mp21?offset/100&xpath=/moov/track/mdia/hdlr[@handlertype="soun "] ---- Example 4)

You can also request a track using Track ID. In this case,

Domain name / resource path? Trackid = number.

In the Authority, a URL address (domain name) that identifies the subject who owns the media is entered, and the resource path registers the path of the resource in the URL address (Domain name). In addition, Box means the basic processing unit used in ISO File Format, and box type is the value of this box type. trackid means the ID of the track in the ISO file format and indicates the ID value of the number.

That is, for example, if a domain name wants to refer to a track whose trackid is 3 in the /example.mp4 content from the root of the web server of www.pixtree.com, the request can be made as in Example 5).

www.pixtree.com/example.mp4?trackid=3 ---- Example 5)

You can also request Media in a Track using the Track ID.

In this way, when a track is serviced, the style of the stream in the actual track varies depending on the edit box in the track. Therefore, in order not to be affected by the edit box, it is necessary to directly access the media information in the track. In this case, the media can be requested in the same manner as in Example 6).

Domain name / resource path? Trackid = 3 & boxtype = mdia ---- Example 6)

In addition, when requesting a DataRefence Box in a track using the Track ID

In order to service a track, the form in which the stream in the actual track is displayed depends on the Edit Box in the track. Therefore, in order not to be affected by the edit box, it is necessary to directly access the media information in the track. In this case, the media can be requested in the same manner as in Example 7).

Domain name / resource path? Trackid = number & boxtype = dref & index = number ---- Example 7)

In addition, when requesting a resource referenced by a DataEntryUrl Box or a DataEntryUrn Box in a DataRefence Box, when the Data Reference Box in a Data Information Box in a Track has n> = 1 data input URLs or data input URNs, the following example 7) , You can request media in the same way.

 www.pixtree.com/example.mp4?trackid=3&box=dref&index=1---Example 8)

 www.pixtree.com/example.mp4?trackid=3&boxtype=url --- Example 9)

If the data information box has a data input URL box as a lower box, the media can be requested in the same manner as in Example 9).

That is, when the data information box in the track has only the data input URL, when the resource referred to by this data URL is requested, the media can be requested in the following manner.

 www.pixtree.com/example.mp4?trackid=3&boxtype=urn---- Example 10)

In addition, when the data information box has a data input URN box as a lower box, when the data information box in Track has only a data input URN, a resource referred to by the data input URN is requested in the same manner as in Example 10).

 ? offset = number & trackid = number & boxtype = box type ---- Example 11)

Finally, when referring to an mp4 stream stored together in an MPEG-21 file, the MPEG-21 file can also be stored using the ISO file format. At this time, a resource referenced by MPEG-21 DID meta information can be stored in the media data box.

In this case, if you want to refer to MP4, define URL as in the following example 11).

? offset = 100 & trackid = 3 & boxtype = mdia ---- Example 12)

In Example 11), Offset represents the number of BYTEs from the start of the file to the start of the MP4 stream included.

If you want to refer to the media whose track id is 3 in the mp4 stream included in the mdat box in mpeg-21 xml in www.pixtree.com/example.mp21, record as in Example 12).

 This type of URL changes the parsing of a wide variety of web pages and media data, for example, at the beginning of the video, at the beginning, at the end, or at regular intervals, or at specific intervals. In this case, the server receives the request and requests a resource from the server storing the resource. For this purpose, the server parses the URL. If the resource exists, the server transmits the resource to the client. As described above, the media data selected in various forms can be taken from the pre-stored space and the media of the requested content can be played.

For reference, the process of requesting a resource with an XML Path (XPath) in the URL shown in Examples 1) to 13) relating to a series of requests and parsing is a preliminary protocol stored in the client and server respectively. It can be implemented by the XML schema, which is illustrated below, and the technical scope of the present invention is not limited by these examples.

<? xml version = "1.0" encoding = "EUC-KR"?>

<!-edited with XMLSPY v5 rel. 4 U (http://www.XMLSPY.com) by Application S / W Team (Pixtree Technologies, Inc.)->

<xs: schema xmlns: x = "http://www.w3.org/XML/1998/namespace" xmlns: xs = "http://www.w3.org/2001/XMLSchema" elementFormDefault = "qualified" attributeFormDefault = "unqualified">

<xs: import namespace = "http://www.w3.org/XML/1998/namespace" schemaLocation = "http://www.w3.org/2001/xml.xsd" />

<xs: complexType name = "UserDataType">

<xs: annotation>

<xs: documentation> Part of adding user's information </ xs: documentation>

</ xs: annotation>

<xs: sequence>

<xs: element name = "CopyRight" minOccurs = "0">

<xs: annotation>

<xs: documentation> Entering information about intellectual property </ xs: documentation> </ xs: annotation>

<xs: complexType>

<xs: sequence>

<xs: element name = "language" type = "xs: string" />

<xs: element name = "notice" type = "xs: string" minOccurs = "0" />

</ xs: sequence>

<xs: attribute name = "language" />

</ xs: complexType>

</ xs: element>

<xs: element name = "HintInformation" minOccurs = "0">

<xs: annotation>

<xs: documentation> Part of recording information needed to stream content </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: choice>

<xs: element name = "MovieHintInformation">

<xs: complexType>

<xs: sequence>

<xs: element name = "data" type = "xs: string" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "RtpMovieHintInformation">

<xs: complexType>

<xs: sequence>

<xs: element name = "sdptext" type = "xs: string" minOccurs = "0" />

</ xs: sequence>

<xs: attribute name = "descriptionformat" type = "xs: string" />

</ xs: complexType>

</ xs: element>

<xs: element name = "TrackHintInformation">

<xs: complexType>

<xs: sequence>

<xs: element name = "data" type = "xs: string" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "RtpTrackSdpHintInformation">

<xs: complexType>

<xs: sequence>

<xs: element name = "sdptext" type = "xs: string" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

</ xs: choice>

</ xs: complexType>

</ xs: element>

</ xs: sequence>

</ xs: complexType>

<xs: element name = "isofileformat">

<xs: annotation>

<xs: documentation> ISO File Format Meta Schema </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence>

<xs: element name = "FileType">

<xs: annotation>

<xs: documentation> records basic information about this file. Version information and supported content type information are recorded.

</ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: attribute name = "major_brand" type = "xs: string" />

<xs: attribute name = "minor_version" type = "xs: string" />

<xs: attribute name = "compatible_brands" type = "xs: string" />

</ xs: complexType>

</ xs: element>

<xs: element name = "Movie">

<xs: annotation>

<xs: documentation> All information about the content is recorded. </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence>

<xs: element name = "MovieHeader">

<xs: annotation>

<xs: documentation> Information about creation, modification and running time of the entire content is recorded. </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: attribute name = "creation_time" type = "xs: string" />

<xs: attribute name = "modification_time" type = "xs: string" />

<xs: attribute name = "tilescale" type = "xs: unsignedLong" />

<xs: attribute name = "duration" type = "xs: unsignedLong" />

<xs: attribute name = "next_track_id" type = "xs: unsignedLong" />

</ xs: complexType>

</ xs: element>

<xs: element name = "IODS" type = "xs: base64Binary" minOccurs = "0" />

<xs: element name = "Track" minOccurs = "0" maxOccurs = "unbounded">

<xs: annotation>

<xs: documentation> Movie consists of several tracks. Information about each track is recorded here. </ Xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence>

<xs: element name = "TrackHeader">

<xs: annotation> <xs: documentation> Create, modify, track ID, running time, etc. for a track </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: attribute name = "creation_time" type = "xs: string" />

<xs: attribute name = "modification_time" type = "xs: string" />

<xs: attribute name = "track_id" type = "xs: unsignedLong" />

<xs: attribute name = "duration" type = "xs: unsignedLong" />

</ xs: complexType>

</ xs: element>

<xs: element name = "Media">

<xs: annotation>

<xs: documentation> Record information about the media making up the track. </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence>

<xs: element name = "MediaHeader">

<xs: annotation>

<xs: documentation> Record information such as the creation, modification and running time of the media. </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: attribute name = "creation_time" type = "xs: string" />

<xs: attribute name = "modification_time" type = "xs: string" />

<xs: attribute name = "timescale" type = "xs: unsignedLong" />

<xs: attribute name = "duration" type = "xs: unsignedLong" />

<xs: attribute name = "language" type = "xs: string" />

</ xs: complexType>

</ xs: element>

<xs: element name = "Handler">

<xs: annotation>

<xs: documentation> indicates what kind of stream this media is. </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: attribute name = "handlertype" type = "xs: string" />

<xs: attribute name = "name" type = "xs: string" />

</ xs: complexType>

</ xs: element>

<xs: element name = "MediaInformation">

<xs: annotation>

<xs: documentation> Includes information about the media </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence>

<xs: choice minOccurs = "0">

<xs: element name = "VideoMediaHeader">

<xs: annotation>

<xs: documentation> Write information about the video if the media is video. </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence>

<xs: element name = "graphicsmode" type = "xs: unsignedLong" minOccurs = "0" />

<xs: element name = "opcolor" type = "xs: unsignedLong" minOccurs = "0" maxOccurs = "3" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "SoundMediaHeader">

<xs: annotation>

<xs: documentation> Write information about the audio if the media is audio. </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: attribute name = "balance" type = "xs: string" />

</ xs: complexType>

</ xs: element>

<xs: element name = "HintMediaHeader">

<xs: annotation>

<xs: documentation> Record information about the hint if the media is hint information. The hint information is used to stream the media. </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: attribute name = "maxpdusize" type = "xs: unsignedLong" />

<xs: attribute name = "avgpdusize" type = "xs: unsignedLong" />

<xs: attribute name = "maxbitrate" type = "xs: unsignedLong" />

<xs: attribute name = "avgbitrate" type = "xs: unsignedLong" />

</ xs: complexType>

</ xs: element>

<xs: element name = "Mpeg4MediaHeader">

<xs: annotation>

<xs: documentation> Records information about MPEG4 when the media is in MPEG4 format. </ xs: documentation>

</ xs: annotation>

</ xs: element>

</ xs: choice>

<xs: element name = "DataInformation" minOccurs = "0">

<xs: annotation>

<xs: documentation> If the stream comprising the media is configured with reference to other content, information about the original stream is recorded here. </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence>

<xs: choice>

<xs: element name = "DataEntryUrl" type = "DataEntryUrlType" minOccurs = "0">

<xs: annotation>

<xs: documentation> Write the content reference as a URL </ xs: documentation>

</ xs: annotation>

</ xs: element>

<xs: element name = "DataEntryUrn" type = "DataEntryUrnType" minOccurs = "0">

<xs: annotation>

<xs: documentation> Record content reference as URN </ xs: documentation>

</ xs: annotation>

</ xs: element>

<xs: element name = "DataReference" minOccurs = "0">

<xs: annotation>

<xs: documentation> Stores reference information in content as an array </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: choice minOccurs = "0" maxOccurs = "unbounded">

<xs: element name = "DataEntryUrl" type = "DataEntryUrlType" />

<xs: element name = "DataEntryUrn" type = "DataEntryUrnType" />

</ xs: choice>

</ xs: complexType>

</ xs: element>

</ xs: choice>

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "SampleTable">

<xs: annotation>

<xs: documentation> Records information about each sample (each frame in the case of video) that makes up the media.

</ xs: annotation>

<xs: complexType>

<xs: sequence>

<xs: element name = "SampleDescription">

<xs: annotation>

<xs: documentation> Write basic information about the sample. </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: choice maxOccurs = "unbounded">

<xs: element name = "HintSampleEntry" minOccurs = "0">

<xs: annotation>

<xs: documentation> Information about the hint sample. </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: attribute name = "data_reference_index" type = "xs: unsignedLong" />

<xs: attribute name = "data" type = "xs: base64Binary" />

</ xs: complexType>

</ xs: element>

<xs: element name = "RtpHintSampleEntry" minOccurs = "0">

<xs: annotation>

<xs: documentation> Information about the RTP hint sample </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: attribute name = "hinttrackversion" type = "xs: string" />

<xs: attribute name = "highestcompatibleversion" type = "xs: string" />

<xs: attribute name = "maxpacketsize" type = "xs: unsignedLong" />

</ xs: complexType>

</ xs: element>

<xs: element name = "VisualSampleEntry" minOccurs = "0">

<xs: annotation>

<xs: documentation> Information about visual samples </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: attribute name = "data_reference_index" type = "xs: unsignedLong" />

<xs: attribute name = "width" type = "xs: unsignedLong" />

<xs: attribute name = "height" type = "xs: unsignedLong" />

<xs: attribute name = "horizresolution" type = "xs: unsignedLong" />

<xs: attribute name = "vertresolution" type = "xs: unsignedLong" />

<xs: attribute name = "compressorname" type = "xs: string" />

<xs: attribute name = "depth" type = "xs: unsignedLong" />

</ xs: complexType>

</ xs: element>

<xs: element name = "AudioSampleEntry" minOccurs = "0">

<xs: annotation>

<xs: documentation> Information about audio samples </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: attribute name = "data_reference_index" type = "xs: unsignedLong" />

<xs: attribute name = "channelcount" type = "xs: unsignedLong" />

<xs: attribute name = "samplesize" type = "xs: unsignedLong" />

<xs: attribute name = "sampleratehi" type = "xs: unsignedLong" />

<xs: attribute name = "sampleratelo" type = "xs: unsignedLong" />

</ xs: complexType>

</ xs: element>

</ xs: choice>

</ xs: complexType>

<xs: element name = "TimeToSample" minOccurs = "0">

<xs: annotation>

<xs: documentation> Record time information about when to decode each sample </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence minOccurs = "0" maxOccurs = "unbounded">

<xs: element name = "sample_count" />

<xs: element name = "sample_delta" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "CompositionOffset" minOccurs = "0">

<xs: annotation>

<xs: documentation> Information on when to play the decoded information </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence minOccurs = "0" maxOccurs = "unbounded">

<xs: element name = "sample_count" />

<xs: element name = "sample_offset" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "SampleSize" minOccurs = "0">

<xs: annotation>

<xs: documentation> Information about the size of the sample </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence>

<xs: element name = "sample_size" type = "xs: unsignedLong" />

<xs: element name = "sample_count" type = "xs: unsignedLong" />

<xs: element name = "entry_size" minOccurs = "0" maxOccurs = "unbounded" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "SampleToChunk" minOccurs = "0">

<xs: annotation>

Chunks that contain multiple <xs: documentation> samples are called chunks. Information about chunks of the same nature is recorded here. </ Xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence minOccurs = "0" maxOccurs = "unbounded">

<xs: element name = "first_chunk" type = "xs: unsignedLong" />

<xs: element name = "samples_per_chunk" type = "xs: unsignedLong" />

<xs: element name = "sample_description_index" type = "xs: unsignedLong" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "ChunkOffset" minOccurs = "0">

<xs: annotation>

<xs: documentation> Write location information in each chunk's file </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence minOccurs = "0" maxOccurs = "unbounded">

<xs: element name = "chunkoffset" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "SyncSample" minOccurs = "0">

<xs: annotation>

<xs: documentation> Records the index of the sample used to synchronize. In the case of video, there is a frame that can be decoded only when there is a frame different from the frame to be independently decoded. The index information of the frame that can be independently decoded is recorded here. </ Xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence minOccurs = "0" maxOccurs = "unbounded">

<xs: element name = "sample_number" type = "xs: unsignedLong" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "ShadowSyncSample" minOccurs = "0">

<xs: annotation>

<xs: documentation> Records the index of the sample used to synchronize. The difference from SyncSample is that if you want to synchronize a sample, if it cannot be decoded independently, it contains information about the sample to use instead. </ Xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence minOccurs = "0" maxOccurs = "unbounded">

<xs: element name = "shadowed_sample_number" type = "xs: unsignedLong" />

<xs: element name = "sync_sample_number" type = "xs: unsignedLong" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "DegradationPriority" minOccurs = "0">

<xs: complexType>

<xs: sequence minOccurs = "0" maxOccurs = "unbounded">

<xs: element name = "priority" type = "xs: unsignedLong" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "PaddingBits" minOccurs = "0">

<xs: complexType>

<xs: sequence minOccurs = "0" maxOccurs = "unbounded">

<xs: element name = "pad2" type = "xs: unsignedLong" />

<xs: element name = "pad1" type = "xs: unsignedLong" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

</ xs: sequence>

<xs: attribute name = "sample_count" type = "xs: unsignedLong" use = "optional" default = "1" />

<xs: attribute name = "isCompact" type = "xs: boolean" use = "optional" default = "false" />

<xs: attribute name = "isChunkLargeOffset" type = "xs: boolean" use = "optional" default = "false" />

</ xs: complexType>

</ xs: element>

</ xs: sequence>

</ xs: complexType>

</ xs: element>

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "TrackReference" minOccurs = "0">

<xs: annotation>

<xs: documentation> Reference information about the track associated with this track </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence>

<xs: element name = "TrackReferenceType" minOccurs = "0" maxOccurs = "unbounded">

<xs: complexType>

<xs: sequence>

<xs: element name = "type" type = "xs: string" />

<xs: element name = "track_id" type = "xs: unsignedLong" minOccurs = "0" maxOccurs = "unbounded" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "Edit" minOccurs = "0">

<xs: annotation>

<xs: documentation> Record information about how the media is to be displayed, unlike edited media at the display stage, as if edited. </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence minOccurs = "0">

<xs: element name = "EditList">

<xs: annotation>

<xs: documentation> Record information about each editing effect </ xs: documentation>

</ xs: annotation>

<xs: complexType>

<xs: sequence maxOccurs = "unbounded">

<xs: element name = "segment_duration" type = "xs: unsignedLong" />

<xs: element name = "media_time" type = "xs: unsignedLong" />

<xs: element name = "media_rate_integer" type = "xs: unsignedLong" />

<xs: element name = "media_rate_fraction" type = "xs: unsignedLong" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "UserData" type = "UserDataType" minOccurs = "0" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "MovieExtends" minOccurs = "0">

<xs: complexType>

<xs: sequence>

<xs: element name = "TrackExtends">

<xs: complexType>

<xs: attribute name = "track_id" type = "xs: unsignedLong" />

<xs: attribute name = "default_sample_description_index" type = "xs: unsignedLong" />

<xs: attribute name = "default_sample_duration" type = "xs: unsignedLong" />

<xs: attribute name = "default_sample_size" type = "xs: unsignedLong" /> <xs: attribute name = "default_sample_flags" type = "xs: unsignedLong" />

</ xs: complexType>

</ xs: element>

</ xs: sequence>

</ xs: complexType>

</ xs: element>

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "MovieFragment" minOccurs = "0">

<xs: complexType>

<xs: sequence>

<xs: element name = "MovieFragmentHeader">

<xs: complexType>

<xs: attribute name = "sequence_number" type = "xs: unsignedLong" />

</ xs: complexType>

</ xs: element>

<xs: element name = "TrackFragment">

<xs: complexType>

<xs: sequence>

<xs: element name = "TrackFragmentHeader">

<xs: complexType>

<xs: sequence>

<xs: element name = "track_id" type = "xs: unsignedLong" />

<xs: element name = "base_data_offset" type = "xs: unsignedLong" />

<xs: element name = "sample_description_index" type = "xs: unsignedLong" />

<xs: element name = "default_sample_duration" type = "xs: unsignedLong" />

<xs: element name = "default_sample_size" type = "xs: unsignedLong" />

<xs: element name = "default_sample_flags" type = "xs: unsignedLong" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: element name = "TrackRun" minOccurs = "0" maxOccurs = "unbounded">

<xs: complexType>

<xs: sequence>

<xs: element name = "sample_count" type = "xs: unsignedLong" />

<xs: element name = "data_offset" type = "xs: unsignedLong" />

<xs: element name = "first_sample_flags" type = "xs: unsignedLong" />

<xs: element name = "sample_duration" type = "xs: unsignedLong" minOccurs = "0" />

<xs: element name = "sample_size" type = "xs: unsignedLong" minOccurs = "0" />

<xs: element name = "sample_flags" type = "xs: unsignedLong" minOccurs = "0" />

<xs: element name = "sample_composition_time_offset" minOccurs = "0" />

</ xs: sequence>

</ xs: complexType>

</ xs: element>

</ xs: sequence>

xs: complexType>

</ xs: element>

</ xs: sequence>

</ xs: complexType>

</ xs: element>

</ xs: sequence>

</ xs: complexType>

</ xs: element>

<xs: complexType name = "DataEntryUrlType">

<xs: attribute name = "location" type = "xs: string" />

</ xs: complexType>

<xs: complexType name = "DataEntryUrnType">

<xs: attribute name = "name" type = "xs: string" />

<xs: attribute name = "location" type = "xs: string" />

</ xs: complexType>

</ xs: schema>

In this way, the present invention can receive and consume the media data in a wide variety of forms, such as consumers can receive only a portion of the media provided by the server or a specific range of time, or can be extracted and provided at regular intervals. It can be used very conveniently for work such as reviewing.

In addition, the present invention is to be provided only audio or video in the media data, for example, by receiving only the video data from the video device installed in the subway, it may not cause unnecessary noise pollution,

On the contrary, the terminal may be provided in a driving vehicle that cannot view an image or may be provided only with audio data in a terminal carried by a walking person, and thus may be very useful.

In addition, in the present invention, there is an effect that a part of the media provided by the server may be usefully used for commercial purposes by providing a part of the so-called "teaser".

Claims (12)

 In addition to assigning storage space to a client used by a consumer, connecting to a server via the Internet or a LAN (100), and receiving a data request for a web page or various media of a website ( 101), the server inputting a corresponding MPEG21 file obtained from an internal database or an external server in response to a data request (104), analyzing the MPEG21 file format (104), and analyzing the file format. In step 105, search for additional data such as audio, video, XML, and the like by searching for a metabox included in the file, and if the metabox does not exist, terminating 106 and, if there is a metabox, Parsing (108) the DID XML in the metabox; storing (109) the parsed resource list; transmitting (110) the stored resource list to the client; The client requests a specific resource (111) by viewing a list of transmitted resources, redirects (redirection) a request for a resource to another server storing the requested specific resource, or receives a URL of the specific resource directly requested by the server. Parsing (113), determining whether the resource exists (114); if the resource does not exist, transmitting (115) an absent message to the client; and wherein the resource exists And transmitting (116) the resource data corresponding to the client in the case of a resource reference method in MPEG-21. The method of claim 1, In step 111, when the client views a list of transmitted resources and requests a specific resource, When referring to a stream stored in the same file or another file in an MPEG-21 file, the offset information is optionally added, and the name and value of the name used in the format of the stream's storage format are listed. Resource reference method in MPEG-21. The method of claim 2, In step 111, the client views a list of transmitted resources and requests a specific resource. The domain name, the location of the resource on the domain server, the resource Define the location value and mp4 specification of the mp4 stream within the XML Schema to define the XPath Resource request method in MPEG-21, wherein a portion of the mp4 stream is requested. The method of claim 2, If the client wants a specific stream in step 111 when viewing a list of transmitted resources and requests a specific resource, the MPEG-21 may be expressed by adding a domain name and a #stream type to a pass of a file storing the stream. How resources are referenced in. The method of claim 3, wherein The stream type to be used is the major type of the international standard Mime Media Type. Resource reference method in MPEG-21 characterized by using application, audio, image, message, model, multipart, text, video). The method of claim 3, wherein  Along with #stream type, it also adds Mimetyp's minor type. Resource reference method in MPEG-21. The method of claim 2, The method of claim 1, wherein if there are several videos, video is appended and indexed in the order in which the videos appear in the file so that the index values of the desired video are attached together. The method of claim 2, In referring to an MPEG-4 stream stored in another file in an MPEG-21 file,  Offset from the beginning of the file containing the MPEG-4 stream to the MPEG-4 stream If you fill in the information and refer to the track in the MPEG-4 stream, you append the track's unique ID. When referencing the media information in the track, the method of writing the box type information of the media together with the Track ID and the DataReference in the DataInformation Box in the Track In the case of using a box, the resource reference method of MPEG-21 characterized by zooming in by writing index information together with box type information. The method of claim 3, wherein A resource reference method in MPEG-21, characterized by zooming in by writing index information of a desired track when a track is provided in box type information and indexing according to the order in which the stream appears. The method of claim 3, wherein  When referring to a media format other than an MPEG-4 stream, the resource reference method in MPEG-21 characterized by zooming in by writing a pair of parameter names and their values correspondingly. The method of claim 3, wherein  When referring to a specific time interval, the resource reference method in MPEG-21, characterized by writing the beginning and end of time together with the track ID or index. The method of claim 3, wherein Using URI notation as a way of referring to resources in MPEG-4, Resource reference method in MPEG-21 characterized by the fact that

Images