Meta-data index structure, method for providing meta-data indexes, method and device for finding meta-data with usage of meta-data indexes

FIELD: index structures for meta-data.

SUBSTANCE: in accordance to the invention, structure of metadata index includes values of multi-keys and identification information for metadata, corresponding to value of multi-key, while multi-keys are structured by means of a combination of predetermined metadata fields. In this structure, key is searched for, which is then used to find and extract a fragment of metadata.

EFFECT: increased meta-data searching speed.

6 cl, 15 dwg, 6 tbl

 

The technical FIELD TO WHICH the INVENTION RELATES

The present invention generally relates to the structure of the index or the index structure of metadata provided to search for information about the content and method of providing metadata indexes, and to a method and device designed to search metadata using the index structure of metadata. More specifically the present invention relates to the structure of the index metadata provided to search for information about the content and method of providing metadata indexes, and to a method and apparatus for searching metadata using metadata indexes, and metadata documents containing keys or multiclutch, with which you can more effectively search for information about the content in that case, if the metadata XML (Extensible markup language RAR) of digital content, certain Forum TV-Anytime (TV time)(later in the document referred to as "metadata TVA"), divided into fragments in as independent blocks and pass on the basis of the fragment. This patent application is based on patent applications in Korea ordinal 2002-43097 and 2002-62923, which are incorporated herein by reference.

The LEVEL of TECHNOLOGY

Forum TV-Anytime is a private organization of potentates the tion, established in September 1999 with the aim of developing standards in the provision of services relating to audio-visual, user-friendly environment such as a personal digital recorder (PCSU, PDR)containing the personal storage device of large volume. Specifically, the purpose of services is to be based on personal storage device to provide an opportunity for all users to view and listen to different types of programs (such as conventional broadcasting services, interactive dialog services online etc) at the right time and in the required manner.

Forum TV-Anytime has involved Working group on business models, access interfaces/content/transfer, descriptions, metadata, rights management and protection and the like, in order to establish standardization. As for metadata, described in the present invention, prior to June 2002 was published 1stDraft of Metadata Specification SP003vl.3" (1st Project description metadata version SP003vl.3).

The configuration PCSO will be briefly described with reference to Fig. 1. PCSO 100 receives video/audio signals and metadata through a variety of communication networks such as the signals reflected from the upper atmosphere, the signals from artificial satellites, the Internet and such, set the ICA 200, provide video/audio signals, collect if necessary, samples of viewing and listening, and personal tastes of the user, and transmits it to the provider 200 for delivery of audio/video signals. PCSO 100 includes a storage device of large capacity for storing therein the received video/audio signal and metadata. PCSO 100 further comprises software for storage and playback of audio/video signals, and application, electronic program guide (EPG EPR) to search for and display metadata for the video/audio signals. The user defines the metadata for the video/audio data, that is, the titles of the programs, the time of playback of the program and the like, by means shown in Fig. 2 screen application EPR, which is designed to guide and has a grid view, selects the desired program, and takes her through the communication network in real time or reproduces the video/audio data previously stored on a storage device of large volume.

Metadata are data that describe the content such as headers and summaries of programs, and is defined as "data about data". Technical descriptions metadata TVA forum TV-Anytime their structure is defined using the XML schema language (see XML 1.0 of the W3C (WWW consortium), the W3C (the consortium for the advancement of XML standards), Opredelenie also semantics and attributes related metadata elements. The TVA metadata, relevant content broadcasting, is determined using an XML document with root node "TVAMain (300), as shown in Fig. 3. The TVA metadata, relevant programs that define, for example, using such sites as "ProgramInformation Table" (table of information about programs), "GroupInformation Table" (a table of groups of information), "ProgramLocation Table" (table location programs), "ServiceInformation" (table service information) and the like, below the node "ProgramDescription" (program Description).

Forum TV-Anytime metadata TVA passed on the basis of the fragment as an independent unit to transfer a large amount of metadata TVA in stream format. The concept of fragments will be briefly described with reference to Fig. 4. Fragments of form, structuring or separating the TVA metadata defined by XML documents, as shown in Fig. 3, at a predetermined tree structure. For example, if you share the full TVA metadata in a tree structure (TVAMain fragment), including the node "TVAMain" top-level and pre-installed child nodes below the top node, the tree structure (the ProgramInformation fragment), including site ProgramInformation Table top level and child nodes below the top node of the tree structure (BroadcastEvent fragment), including the top-level node BroadcastEvent Information and the child nodes below the top node, then ka is the Mae of the split tree structures becomes a fragment. Fragments can be transferred independently of the other fragments, and the fragments can be accessed individually.

For individual access to the fragments you need to know the node referenced by the passed metadata TVA, i.e. a node in a complete tree structure metadata corresponding to the top-level node for a fragment of metadata TVA, and describe the relative path to the fragments of the metadata TVA keys contained in the transmitted metadata TVA. Used for this purpose is the XPath language (paths in XML documents, APRAR), which is defined by the W3C syntax description path to one or more nodes in an XML document. The term "key" refers to a specific metadata field used for indexing, and also means the child nodes of the node referenced by the fragment. Field (search terms)entered by the user, for example 'Service ID' (ID service) and 'Published Time' (Published time), correspond to the keys.

To ensure effective search of fragments and access to fragments, an additional index structure for keys included in the metadata fragments, and information about the index structure, that is, the index information also transmit regardless of the fragments of the metadata.

In the environment provided by Forum TV-Anytime, if the same user is AET to get information about the program, satisfying a predetermined condition Published Time, use transmitted for this purpose regardless of the fragments of the index information to identify the location (ID) fragment metadata that satisfies the desired condition of the Published Time, and then based on the location (ID) access to the relevant metadata to retrieve metadata that satisfy the condition Published Time.

Technical description of TV-Anytime TV145, J.P. Evain, "1stDraft of Metadata Specification SP003vl.3", 17th meeting, Montreal, Canada, June 2002; the document referred to as "Single key index art reference" (Reference to the prior art indexing single-key) provides for indexing of the metadata structure of the single index key (hereinafter the structure odnoglazovogo index).

Note that the term "single key" is used herein to distinguish it from the concept of the term "multicloud in the embodiment of the present invention, which will be described later. The index structure multicouche (hereinafter the structure mnogoluchevogo index), in accordance with the embodiment of the present invention, allows the user to access the metadata in many keys, using multiple keys simultaneously, and structuredfinanceeurope index according to the prior art allows you to use only one key for accessing the metadata.

The concept of a container or object that contains other objects, a specific Forum TV-Anytime, will be described before the description of the structure of the index.

Forum TV-Anytime defines a container as the top-level store, which transfer all the data, covering the above-mentioned index information and the fragments of the metadata, which is called the type of high-level gear. Describing briefly container, each container contains a set of sections, each of which stores the index information or the fragments of the metadata. The container can be classified into the container index and the data container in accordance with the information which it lies: container index contains sections index information such as the section of the list of index keys (key_index_list), partition key index (key_index)section index of the subkey (sub_key_index), section string storage (string_repository) and section store pieces of data (fragment_data_repository), and the data container comprises the sections of the fragments of the metadata such as the partition table of the elements (elements_table), section string storage section and stores pieces of data. The above classification is done based on the contents of the information conveyed in containers. As the container index, and the data container of identical construction.

As for the pin is of inera, a certain Forum TV-Anytime Forum, as illustrated in Fig. 5, the container contains a data field for the ID of the container (container_id) (not shown), and a few sections. In each section, the contents stored in the body section (section_body)identified in accordance with the encoded value of the ID section (section ID) (section_id). For example, section 10, coded value for which the ID section is "0X0004", identified as section 20 list of index keys, section 20, an encoded value for which the ID section is "0X0005", identified as partition key index, section 30, an encoded value for which the ID section is "0X0006", identified as partition index data, section 40, an encoded value for which the ID section is "0X0001", identified as partition table of the elements, and section 50, coded value for which the ID topic is "0X0003", identified as section store pieces of data.

Fragments TVA metadata stored in the data container section 50 stores pieces of data and then transmit. Information about the ID for fragments of the metadata TVA (handle_value) in the data container included in section 40 of the table elements of the data container.

In conclusion, the fragment metadata TVA unique identifier the Ute through information about the container ID and the information about the fragment identifier metadata of the container, which includes a fragment of the TVA metadata.

Described above in reference to the prior art using a single index key, provides the structure of the single-key index for indexing fragments TVA metadata, stored in the above data container, that is, a structure composed of section 10 of the list of index keys, section 20 of the index key and section 30 of the index data. Because the syntax of patterns is described in detail in the above reference to the index of the single key, its detailed description will be omitted. Later in the document structure will be described with reference to Fig. 6, in which is illustrated the structure of the segment index information.

Section 10 of the list of index keys defined in the structure of the single-key index provides a list of all transferred to single keys. The list includes information about a single key that identifies every single key, and information about the identity or identifying information, section 20 of the index key, which will be described later in the document.

Information about a single key contains (1), the location information of the fragment metadata relevant to a single key, and (2) the location information of a single key in the metadata. The location information of the fragment metadata expressed in XPath (fragmentxpath_ptr) in TVA. The location information of a single key expressed in XPath (key_xpath_ptr)corresponding to a relative path in the relevant fragment of the node is used as a single key in TVA.

XPath fragment metadata is the path to the root node of the XML document representing the TVA metadata, i.e. the absolute path and XPath nodes used as single keys, i.e. single XPath keys, represents the relative path to a single key for the relevant fragment of the metadata. For a fragment of XPath metadata and XPath for a single key is stored in the segment 11 "fragment_xpath_ptr" and the segment 12 "key_xpath_ptr" respectively.

In addition, section 10 of the list of index key includes identifying information about the section 20 of the index key for each single key, which will be described later in the document (that is, information about the container ID of the container that stores the section 20 of the index key, and the ID information of the index key). Information about the container ID and the ID information of the index key stored in the segment "index_container" section 10 of the list of index keys and the segment ID of the index key (ID key index) (key_index_identifier), respectively, and then passed in.

Section 20 of the index key that is defined in the structure of the single-key index, provide the supports list information, representing the ranges of key values included in the relevant sections 30 index data, i.e. the highest key value from the key values in the appropriate range (hereinafter referred to as "representative key value"), and identifying information in section 30 of the index data relevant to each of the representative key value (that is, information about the container ID of the container that stores the section 30 of the index data, and information about the index ID of the connection).

Accordingly, section 20 of the index key includes a segment ID of the index key to store the information about the ID key index defined in section 10 of the list of index keys, the segments 13 of the highest key value "high_key_value to save them representative key values for the respective ranges of key values included in section 30 of the index data, and segments "sub_index_container" segments "sub_index_identifier for identifying information about section 30 of the index data (i.e. information about the container ID of the container in which retain section 30 of the index data, and relevant information about the ID index data). Section 30 of the index key that is defined for the structure of single-key index, pepper provides the key values. The list also includes identifying information about the fragments of the metadata corresponding to the key values (that is, information about the identity of the container of those containers that preserve the fragments of the metadata and the ID information of the fragments of the metadata).

Accordingly, section 30 of the index data includes the segment "sub_index_identifier" to store information about the index ID of the connection defined in section 20 of the index key, the segments 14 key value (key_value) to store them in respective ranges of values of the key segments target_container to store relevant information about the container ID of the container in which the fragments are stored metadata, and segments "target_handle", which contain relevant information about the fragment identifier data. Structure odnoglazovogo index may be more readily understood by reference to Fig. 7, which illustrates information about the index.

In Fig. 7a and 7b shows a section of the list of index keys, which includes a single key, relevant Service Id, Published, Time and Duration Published. The top node of the fragment metadata, including single key, relevant Service Id, Published, Time and Duration Published, is "BroadcastEvent" 310, as shown in Fig. 3, highlighted by a shaded block. Accordingly, the XPath"/TVAMain/ProgramDescription/ProgramLocation Table/BroadcastEvent" fragment "BroadcastEvent" is stored in the segment "fragment_xpath_ptr" 11a, and xpaths to single keys "Service Id", "Published " Time" and "Duration Published" fragment "BroadcastEvent" fragment "BroadcastEvent", that is, "@ServiceId" (311a in Fig. 3), "EventDescription/PublishedTime" 3l1b in Fig. 3) and "EventDescription/PublishedDuration" (s in Fig. 3) stored in the segment 12a "key_xpath_ptr".

In Fig. 7a shows illustrative section 20a of the index key and section 30A of the index of the subkey to "Service Id" (the XPath for a single key: @ServiceId) of section 10a of the list of index keys. In Fig. 7b shows a section 20b of the index key and section 30b of the index of the subkey to "Published Time" (the XPath for a single key: EventDescription/PublishedTime).

This structure single-key index is disadvantageous because inefficient to search with a composite condition, i.e. the search one or more search terms, because according to the technical description of the TV-Anytime, it can support the search to only one or a single key, that is, the index search using the key corresponding to the specific field of the metadata. For example, to display the list of programs broadcast on a grid view screen guide, as shown in Fig. 2, the required search operations based on two fields, that is, "Service Id" and "Published Time".

In order to explain the search for the combined condition with normal usage patterns single-key index, below the document as example b the children explained option that list of programs "Service Id" is in the range from 507 to 514, and Published Time" - from 09:30 to 10:00. Technical metadata description of the TV-Anytime search terms to retrieve metadata related to the list of programs, expressed as set forth below.

- Target fragment to search (BroadcastEvent): /TVAmain/ProgramDescription/ProgramLocationTable/BroadcastEvent

- List search criteria:

507<=ServiceId<=514

09:30<=EventDescription/PublishedTime<= 10:00.

For normal patterns of single-key index there are two ways to obtain fragments that meet the specified search criteria. The methods will be described in detail with reference to Fig. 8a and 8b.

(1) the First way to search using an index with a single key

By the first method, as shown in Fig. 8a, search sets of fragments as an intermediate result that satisfy the relevant conditions independently using appropriate single keys for ServiceId and EventDescription/PublishedTime. Then get the fragments that are common in both sets independently found fragments of which get the final result set of fragments that satisfy the conditions.

Later in the document, this method will be described in detail with reference to Fig. 7a and 8a.

First point (S11) information about a single key and value of a single key to search ervice Id" and "Published Time". Information about a single key contains XPath to target the desired fragment metadata as information about the location of the target of the desired fragment metadata, and XPath for a single key as information about the location of a single key in the metadata.

- For a fragment of XPath metadata: /TVAMain/ProgramDescription/ProgramLocationTable/BroadcastEvent,

- XPath for Service Id: @ServiceId,

The key value for Service Id: 507<=ServiceId<=514.

Then a single key corresponding XPath 11a to slice-and-XPath 12a for the Service Id, extracted from section 10A of the list of index keys and retrieve identifying information in section 20A of the index key. On this basis, a representative key value "509" 13a and "519" 13a, that is representative of key values, which indicate the ranges (500-509, 510-519) key values and key values (507-514)subject to search, extract from section 20A of the index key with this extracted identifying information. Then remove identifying information in section 30A of the index data for the segments 14a, with corresponding ranges of key values (500-509, 510-519)associated with representative key values "509" and "519". Identifying information for fragments of the metadata (information about the container ID and the ID information piece of data stored in a segment on the e target_container" and the segment "target_handle," respectively), the corresponding key values 507-514, extracted from section 30A of the index data and extract relevant fragments of the metadata using the extracted identifying information (S12, S14).

To search for Published Time as an example, information about a single key, that is, information about XPath to target the desired fragment metadata and information about XPath for a single key, and the value of a single key is expressed as set forth below.

- For a fragment of XPath:

/TVAMain/ProgramDescription/ProgramLocationTable/BroadcastEvent,

- XPath for Published Time: EventDescription/PublishedTime,

- Key value for the Published Time: 09:30<=EventDescription/PublishedTime<=10:00.

The fragments of the metadata corresponding to the values of the key 09:30-10:00, pull through essentially the same steps as in the search (S13, S15) Service Id. Perform the intersection of the extracted fragments of the metadata for the Service Id and the Published Time, and the metadata of common fragments of metadata as the final result (S16) put on having a grid view screen guide shown in Fig. 2.

(2) the Second way of searching using the index with a single key.

The second way to search for fragments with only one (e.g., Service Id) of the two single keys associated with the search conditions, as illustrated in Fig. 8b (S21-S23), and only those fragments for which Published Time as other search condition, finds the I between 09:30 and 10:00, choose from found fragments (S24).

Since the intermediate result fragments, obtained by searching using relevant single keys are usually significant, these search methods using the structure of the single-key index, are not effective. By the first method, because all programs in a range of relevant Service Id get as a result of the search, regardless of the range of Published Time, and programs in the relevant time range for all values of Service Id get as a result of the search, the search result can be substantial. In addition, because the calculation is also complicated in the processing of combining the two intermediate search results, which is substantial in size, the overhead in the receiving device increases significantly. In the second method one intermediate result must be further filtered by another search condition. Therefore, the search for a compound condition using patterns single-key index can cause significant overhead in the receiver. Additionally, if the search condition for a single key is input, the metadata define the location information for the field of search terms, and ODA is divided by the location information is compared with information about the key from the list of index key to locate the corresponding key. In this case, the overhead caused by the fact that you compare both ways XPath.

The INVENTION

Accordingly, the present invention is to create a structure mnogoluchevogo index metadata used to search for a compound condition information about the content.

Another objective of the present invention is to create a method of providing metadata indexes applicable for compound terms, asked for information about the content, the way search metadata using metadata indexes and searching device that uses such. Another objective of the present invention is to create a structure mnogoluchevogo index, in which at least part of the key information, that is, the location information that identifies the key that is expressed according to a predetermined code. Additional tasks and/or advantages of the present invention will be formulated in part in the description which follows and in part will be obvious from the description or may be learned by practicing the invention in practice.

In order to solve the above and/or other objectives of the present invention, the proposed index structure for metadata divided into fragments, containing a list of mult is key which correspond to the combination of metadata fields and the location information to determine multiclutch from the list. The index structure may further comprise values multiclutch and identifying information of the metadata corresponding to the values of multiclutch. Identifying the metadata information may include identifying information of some fragments of the metadata corresponding to the values of multiclutch.

The index structure may further comprise a subsection that includes ranges of values of multiclutch and identifying information of some fragments of the metadata corresponding to the values of multiclutch, and section, including representative key values representing the respective ranges of values of multiclutch.

The list may include identifying information about the section, and the section can optionally include identifying information about the topic. At least part of the location information can be expressed as a predetermined code. Location information may include the location information of the fragment, which includes multiclutch, and the location information of multiclutch in the fragment. In another aspect information location can be expressed in XPath.

Each is OE of the representative key value can be a value from the corresponding range of values of multiclutch. Representative key value may be at least one maximum value, minimum value or an intermediate value of the values in a predetermined range. The metadata may be metadata according to the definitions of the Forum TVA.

In order to solve the above and/or other objectives of the present invention, proposed another index structure for metadata divided into fragments, containing the values of multilocal and identifying information of the metadata corresponding to the values of multiclone, and multiclutch combinations of metadata fields. The index structure can optionally contain a list of multiclone. The index structure may further comprise the location information to determine multiclone, and at least part of the information location is expressed pre-established code. Identifying the metadata information may include identifying information of some fragments of the metadata corresponding to the values of multiclone.

As for the comparison of values multiclutch in size, multicloud may contain fields (k1, k2, k3... kn) metadata, which are in accordance with the priority (k1>k2>k3>... kn), and a field can be compared placenta is therefore starting with the first field having the highest priority, and the values are compared arithmetically, if the values of multiclutch are numeric, or appreciate in lexicographical order, if the values of multiclutch are literal. The first and second values multiclutch can match (a1, a2, a3...an) and (b1, b2, b3... bn), respectively, and first and second values (a1, a2, a3...an) and (bl, b2, b3...bn) multiclutch can be defined as having the same size, if there is no field that has a different size.

In order to solve the above and/or other objectives of the present invention, proposed another index structure for metadata divided into fragments containing section of the list of index keys, which contains a list of multilocal, each multicloud corresponds to the combination of metadata fields section of the index key and index partition key, and for multiclutch from the list of index keys index partition subkey contains the value ranges multiclutch and identifying information of some fragments of the metadata corresponding to the values of multiclutch, and the section of the index key contains representative key values representing the respective ranges of values of multiclutch.

Section of the list of index keys can optionally contain information months is omolojeniya to determine multiclone, moreover, at least part of the location information is expressed pre-established code.

In order to solve the above and/or other objectives of the present invention, a computer-readable storage medium containing a data structure for storing the index metadata divided into fragments, and the index is available for searching the metadata.

In order to solve the above and/or other objectives of the present invention, a method for providing index structure for metadata divided into fragments, containing provision of the list of multilocal corresponding to the combination of metadata fields and the information of the location to determine multiclutch from the list.

The method may further comprise providing values multiclutch and identifying information of the metadata corresponding to the values of multiclutch.

Location information can be expressed in XPath. At least part of the information location is expressed pre-established code. The metadata may be metadata according to the definitions of the Forum TVA.

The method may further comprise providing subsection, including the value ranges multiclutch and identifying information of some fragments of the metadata corresponding to the values of multiclutch, and both the cookies section, including representative key values representing the respective ranges of values of multiclutch.

Each of the representative key value is the value of the corresponding range of values of multiclutch. Representative key value can be one of the values is the maximum value, minimum value or an intermediate value of the values in a predetermined range.

In order to solve the above and/or other objectives of the present invention, proposed another method of securing the index structure for metadata divided into fragments, containing ensuring values multiclone and providing identifying information for the metadata corresponding to the values of multiclone, and multiclutch combinations of metadata fields.

The method may further comprise the list of multiclone.

The method may further comprise providing information of the location to determine multiclone, and at least part of the information of the location of the Express pre-established code.

Identifying the metadata information may include identifying information of some fragments of the metadata corresponding to the values of multiclone.

As for the comparison of values multiclutch on R is smeru, multicloud may contain fields (k1, k2, k3... kn) metadata, which are in accordance with the priority (k1>k2>k3>... kn), and a field can be compared sequentially, starting with the first field having the highest priority, and the values are compared arithmetically, if the values of multiclutch are numeric, or appreciate in lexicographical order, if the values of multiclutch are literal.

In order to solve the above and/or other objectives of the present invention, proposed another method of securing the index structure for metadata divided into fragments, which contains the software section index list of keys, including a list of multilocal, each multicloud corresponds to the combination of metadata fields, providing index partition key, and the software section index data, and for multiclutch from the list of index keys index partition subkey contains the value ranges multiclutch and identifying information of some fragments of the metadata corresponding to the values of multiclutch, and the section of the index key contains representative key values representing the respective ranges of values of multiclutch.

Section of the list of index keys can optionally contain the location information for the distribution of multilocal, moreover, at least some of the information location is expressed pre-established code.

In order to solve the above and/or other objectives of the present invention, a method for searching metadata divided into fragments, using an index having a list of multilocal and the location information to determine multiclone containing the search index metadata multiclutch corresponding to the search conditions from the combination of metadata fields and extracting a fragment of the metadata using the found multiclutch.

Search multiclutch may contain identifying information location corresponding to the fields in the search criteria metadata, and search multiclutch corresponding to the information of the locations that correspond to the fields in the search criteria.

Search multiclutch may contain the search value multiclutch that satisfy the search condition.

Search values can contain the search value from the values of multiclutch in the index, and the fragment can include removing a fragment of the metadata using the identifying information of the fragment corresponding to the value of multiclutch.

In response to the set of values of multiclutch that satisfy the search conditions, the fragment may contain izvlecheny is some of the fragments of the metadata, the corresponding values multiclutch that satisfy the search condition.

Search values can contain the search of representative key values satisfy the search conditions from a representative of the index key values corresponding to the ranges of values of multiclutch, and search for a value in the range of values corresponding to the representative key value.

In order to solve the above and/or other objectives of the present invention is proposed another method of searching for metadata divided into fragments, using an index having a list of multilocal and the location information to determine multiclone containing the search index metadata values multiclutch satisfying the search conditions from the combination of metadata fields, and retrieving metadata corresponding to the found value.

In response to the plurality of values multiclutch that satisfy the search conditions, the fragment may include removing some of the fragments of the metadata corresponding to the values of multiclutch that satisfy the search condition.

In order to solve the above and/or other objectives of the present invention is proposed another method of searching for metadata divided into fragments, containing the access list containing nab the R combinations of data location of the fragment and information location, defining at least two keys in the fragment, and search in the list of combinations corresponding to the search conditions for at least two keys metadata.

The method may further comprise removing one or more pieces of metadata corresponding to the identifying information about the metadata identified by the selected combination.

By the way, one of the data location of the fragment and information location, determining at least two keys, can be expressed as a predetermined code.

In order to solve the above and/or other objectives of the present invention, an apparatus for searching for metadata divided into fragments, using an index having a list of multilocal and the location information to determine multiclone containing the block data input that receives a search condition, and a control unit which searches the index metadata multiclutch corresponding to the search conditions from the combination of metadata fields and extracting a fragment of the metadata using the found key.

The control unit may search for values multiclutch that satisfy the search condition, among the values of multiclutch from the index, and retrieve the fragment corresponding to the value of the cartoon is UCA, using the identifying information of the fragment.

In response to the set of values of multiclutch that satisfy the search conditions, the control unit may allocate some of the fragments of the metadata corresponding to the values of multiclutch that satisfy the search condition.

The control unit may search for representative values that satisfy the search conditions from among the representative values of the index corresponding to ranges of values of multiclutch, and to search for a value from a range of values corresponding to the representative key value.

Information location can be expressed in XPath.

At least part of the information of the location can be expressed as a predetermined code.

The metadata may be metadata according to the definitions of the Forum TVA.

In order to solve the above and/or other objectives of the present invention proposed another device to search for metadata divided into fragments, using an index having a list of multilocal and the location information to determine multiclone containing the block data input that receives a search condition, and a control unit which searches the index metadata multiclutch corresponding to the search conditions from the combination of fields IU is acceptable, and extracting a fragment of the metadata using the found values.

The control unit may search for values multiclutch that satisfy the search condition, among the values of multiclutch from the index, and select the fragment corresponding to the value of multiclutch, using the identifying information of the fragment.

The control unit may search for representative values that satisfy the search condition, among a representative index values corresponding to the ranges of values of multiclutch, and to search for values in the range of values corresponding to the representative key.

In response to the set of values of multiclutch that satisfy the search conditions, the control unit may allocate the fragments of the metadata corresponding to the values of multiclutch that satisfy the search condition.

At least part of the information of the location can be expressed as a predetermined code.

The device may further comprise a block input that receives the metadata and the metadata index, a storage device that stores the metadata and the metadata index, and an output unit that generates a search result using the control unit.

In order to solve the above and/or other tasks of this izobreteny is, proposed the following device to search for metadata divided into fragments, using an index having a list of multilocal and the location information to determine multiclone containing the block data input, which accepts search criteria in at least two metadata keys, and a control unit that selects a combination corresponding to the search condition from the list containing the set of combinations of data location of the fragment and information location, determining at least two keys in the fragment.

The control unit may further extract one or more fragments of the metadata corresponding to the identifying information for the metadata identified by the selected combination.

One of the data location of the fragment and information location, determining at least two keys, can be expressed as a predetermined code.

BRIEF DESCRIPTION of DRAWINGS

The foregoing and/or other features and characteristics of the present invention will be more apparent from the following description of preferred embodiments, are given together with the accompanying drawings, in which:

Fig. 1 is a schematic diagram view normal PCSO;

Fig. 2 - screen guide as with the TCI in the usual application of EPR;

Fig. 3 is a block diagram of the structure of conventional metadata, certain Forum TV-Anytime;

Fig. 4 is a schematic representation of the normal fragment specific Forum TV-Anytime;

Fig. 5 is a schematic view of a conventional container, a specific Forum TV-Anytime;

Fig. 6 is a block diagram of the structure of the metadata index that uses the traditional concept of a single key;

Fig. 7a and 7b is a block diagram of the structure of the metadata index and search algorithm using the traditional scheme with a single key;

Fig. 8a and 8b is a schematic methods of search metadata using the traditional scheme with a single key;

Fig. 9 is a block diagram of the structure of the index metadata on the basis of a scheme with multiclutch in accordance with the embodiment of the present invention;

Fig. 10 is a block diagram of the structure of the metadata index and search algorithm that uses a schema multilocal in accordance with the embodiment of the present invention;

Fig. 11 is a block diagram of a method of providing metadata indexes in accordance with the embodiment of the present invention;

Fig. 12 is a diagram of a method of searching metadata in accordance with the embodiment of the present invention; and

Fig. 13 is a schematic representation of a device designed to search for metadata in accordance with a variant osushestvlyaetsya of the invention.

The BEST OPTION of carrying out the INVENTION

Later in the document with reference to the accompanying drawings will be described in detail an embodiment of an index structure of metadata provided to search for information about the content, methods of securing indexes, metadata, and method and device for searching metadata using metadata indexes.

The embodiment of this description will be presented based on the metadata TVA for the purpose characteristics; however, this should not be interpreted or construed as a limitation of the framework of protection of the present invention.

In Fig. 9 shows the syntax structure determination mnogoluchevogo index in accordance with the embodiment of the present invention. First, with reference to Fig. 9 the structure of the metadata index that is designed to search for information about the content, structure will be described, including section 110 of the list of index keys, section 120 of the key index, and section 130 of the index data intended for the indexing of metadata fragments TVA transferred and stored in the data container, and then will describe the structure mnogoluchevogo index defined by syntax.

Compared to the syntax defined in reference to the prior art indexing with a single key, the syntax that defines the structures of the index metadata that is, the structure mnogoluchevogo index in accordance with the embodiment of the present invention contains the structure, re-presented for the scheme mnogoluchevogo index, which includes key descriptor (key_descriptor), the descriptor for the highest key value (high_key_value_descriptor) and a handle to the key value (key_value_descriptor), and changed the partition structure of the list of index keys index partition key, and index partition key.

1. Section of the list of index keys

Section of the list of indexes of the keys provides a list of all transmitted multiclone. In each structure the list of index keys included (key_descriptor), to allow indexing by many keys, as shown in Table 1.

Table 1.
SyntaxCol. Bits (mutable)
key_index_list() {
for(j=0; j<key_index_count;j++) {
fragment_xpath_ptr16
key_descriptor()
index_container16
key_index_identifier8
}
}

Key_index_count: specifies the number is all transmitted multiclone, that is, the number of indexes for a complete XML document.

Fragment_xpath_ptr(): describes the XPath for the target fragment of the metadata that should be indexed, that is, the location information of the target fragment of the metadata that should be indexed. Information of the location of the fragment can be expressed according to a predetermined code. That is, if the fragment has, for example, frequently used type, provide the encoded value that represents the XPath for a fragment with a predetermined code. Since XPath fragment can be expressed simply as the encoded value, the overhead when searching metadata can be reduced. For example, encode values can be "0X01", "0X02", "0X03", and so forth, and of 8 bits, 16 bits, and so on, in accordance with applications. Information location for a fragment encoded as "0X07" can mean, for example, for a fragment of XPath BroadcastEvent (broadcast event). If the code value is "0X00FF", it can refer to a user-defined fragment, and thus, the XPath for the relevant user-defined fragment can be added as additional information.

Key_descriptor(): describes the position of the XPath multiclutch XPath target group of fragments of metadata that must be ind Tserovani, that is, the location information of multiclutch in the fragment metadata and information about the indicator coding in each element/characteristic forming multiclutch. Like the above, information of the location for multiclutch, which is often used type, can be expressed as a predetermined code. The code value for frequently used types of multiclutch may have a structure similar to a fragment encoding. Coding for a fragment of XPath and XPath encoding for multiclutch can be used together or independently.

Index_container (container, index): identifies the container in which is (present) specified partition key index.

Key_index_identifier: section identifies the key index in the container specified by index_container. Section 20 of the index key can be identified uniquely by a combination of index_container and key_index_identifier.

2. Key descriptor (key_descriptor)

Multiclutch is merged or composite key. With respect to the set of keys that compose multiclutch, key_descriptor describes the characteristics of a key such as XPath for the key. Table 2 below shows key_descriptor.

Table 2
SyntaxCol. Bits (mutable)
key_descriptor() {
key_attribute_count8
for (j=0; j<key_attribute_count; j++) {
key_xpath_ptr16
}
}

Key_attribute_count: determines the number of keys that make up multiclutch.

Key_xpath_ptr: specifies the path relating to fragment_xpath_ptr, for a node (key), used as multiclutch.

3. Re-presents high_key_value_descriptor() partition key index.

In this embodiment high_key_value_descriptor() indicates a value representative of a key representing a range of values of multiclutch in the search section index section index plug, the number of which is specified index partition key. The handle high_key_value_descriptor() specifies, for example, the highest value of the values of multiclutch in the appropriate section of the index data. But can any link value to use, because it represents values multiclutch in a predetermined range of values within the relevant sections of the index data, including the minimum value or an intermediate value, and so on, as another embodiment of the present invention.

Table 3
Syntax Col. Bits (mutable)
key_index() {
key_index_identifier8
sub_index_count8
for (j=0; j<sub_index_count; j++) {
high_key_value_descriptor()16*

key_attribute_count
sub_index_container16
sub_index_identifier8
}
}

Key_index_identifler: section identifies the key index in the container specified by index_container. Index partition key can be identified uniquely by a combination of index_container and key_index_identifier. It's defined in the list of index keys.

Sub_index_container: identifies the container that contains the specified index key.

Sub_index_identifier: section identifies the index of the subkey in the container specified by sub_index_container. Section index data can be identified uniquely by the combination sub_index_container and sub_index_identifier.

In the following Table 4 presents high_key_value_descriptor().

Table 4
SyntaxCol. Bits (mutable)
high_key_value_descriptor() {
for (j=0 j< key_attribute_count; j++) {
key_attribute_value16
}
}

Key_attribute_count: specifies the number of keys that compose multiclutch. It is defined in the section of the list of index keys.

Key_attribute_value: is a representative key value for each key. The encoding format of the values corresponds to the value key_value schema indexing with a single key.

If high_key_value_descriptor() contains the value of multiclutch, comparing values of multiclutch size perform as set forth below. If the values of multiclutch are numeric, they are compared arithmetically; if the values of multiclutch is literal, and evaluate them in lexicographical order. As multiclutch (k1, k2,..., kn), which consists of keys k1, k2,..., kn, assume that k1 has the highest priority, and kn is the lowest priority. According to this assumption by considering two values of multiclutch (a1, a2,..., an) and (bl, b2,..., bn),

* the value of multiclutch (a1, a2,..., an) is greater than the value of multiclutch (b1, b2,..., bn)if and only if, there exists an integer i (0<=i<=n-l) such that for each j, (0<=j<=i-l), aj=bj and ai>bi;

* the value of multiclutch (a1, a2,..., an) is less than the value of multiclutch (b1, b2,..., bn)if and only if, there exists an integer i (0<=i&l; =n-l) such that for each j (0<=j<=i-l), aj = bj and ai< bi;

* the value of multiclutch (a1, a2,..., an) is equal to the value of multiclutch (b1, b2,..., bn)if and only if, for each i (1<=i<=n), ai= bj.

4. Section index data

Re-presents the descriptor key_value_descriptor() scheme mnogoluchevogo indexing. The handle key_value_descriptor() represents the value of multiclutch target fragment specified in this way.

Table 5
SyntaxCol. Bits (mutable)
sub_key_index() {
sub_index_identifier8
reference_count8
for (j=0; j<reference_count; j++) {
key_value_descriptor()16*

key_attribute_count
target_container16
target_handle16
}
}

Sub_index_identifier: identifies the container identified by sub_index_container, section of index data. Section index data can be identified uniquely by a combination of sub_index_container and sub_index_identifier. It's defined in the index key.

Reference_count: specifies the number of multilocal included in sub_key_idex().

Target_container: identifies the container that contains the specified metadata.

Target_handle: identifies a section of a fragment of the metadata in the container identified by target_container. Section of a fragment of metadata can be identified uniquely by a combination of target_container and target_handle.

Table 6 below shows key_value_descriptor().

Table 6
SyntaxCol. Bits (mutable)
key_value_descriptor() {
for (j=0; j<key_attribute_count; j++) {
key_attribute_value16
}
}

Key_attribute_count: specifies the number of keys that compose multiclutch. It is defined in the section of the list of index keys.

Key_attribute_value: represents the value for each key. The format corresponds to the value key_value in reference to the prior art indexing with a single key.

Comparing values key_value_descriptor() perform the same as comparing values high_key_value_descriptor() in the structure section of the index key.

Later in the document, with reference to Fig. 9 will be discussed defined by the above-described structure syntax of the metadata, which Provillus is recorded using a segment index information.

Section 110 of the list of index keys defined in the structure of the metadata, provides a list of all transmitted multiclone. The list contains information about multislice that defines each multiclutch, and identifying information for section 120 of the index key, which will be described later in this document. Information about multislice contains (1), the location information of the fragment metadata relevant to multiclutch (expressed in TVA XPath (fragment_xpath_ptr) for a fragment of metadata relevant to multiclutch), and (2) the location information of multiclutch in the fragment metadata (expressed in TVA XPath (key_descriptor) for nodes that are used as multilocal, that is relevant path in the XPath location of the fragment metadata that are relevant sites that are used as multiclone). Like index structure with a single key, for a fragment of XPath metadata refers to the path for the root node of the XML document that contains metadata TVA, i.e. the absolute path and XPath for the node, used as multiclutch, that is, the XPath for multiclutch, refers to the relative path of multiclutch for a fragment of metadata. For a fragment of XPath metadata and XPath for multiclutch stored in the segment 111 "fragment_xpath_ptr", and the segment 112 "key_descriptor" respectively.

Section 110 of the list of index keys also includes identifying in the ormatio of section 120 of the index key for each multiclutch, which will be described later in the document (that is, information about the container ID of the container where you saved section 120 of the index key, and the ID information of the index key). Information about the container ID and the ID information of the key index retain, respectively, in the segment "index_container" and the segment "key_index_identifier" in section 110 of the list of index keys and then passed.

Section 120 of the index key that is defined in the structure of the data stream mnogoluchevogo index provides a list of information about the values of multiclutch included in the appropriate section of the index data, that is, the representative key value representing a predetermined range of values of multiclutch included in each section 130 index data (in this embodiment, the highest value of multiclutch), and identifying information for the section 130 index data associated with each of the representative key value (that is, information about the container ID of the container that stores section 130 of the index data, and information about the index ID of the connection). How to compare values multiclutch in this embodiment is identical to that of the comparison values multiclutch described in connection with Table 4.

Section 120 of the index key includes himself segment "key_index_identifier", stores the information about the ID key index defined in section 110 of the list of index keys, the segments 113 "high_key_value_descriptor"preserving representative key values for the respective ranges of values of multiclutch included in section 130 of the index data, and information identifying section 130 index of the subkey that contains the value of multiclutch. Information identifying section 130 of the index data includes segments sub_index_container", in which information is stored about the identity of the container as the containers in which the saved section 130 of the index data, and segments "sub_index_identifier", in which is stored information about the index ID of the connection.

Section 130 of the index of the subkey specified in the index structure, provides the list of values multiclutch. The list also includes identifying information about the fragments of the metadata corresponding to the values of multiclutch (i.e. information about the container ID of the container in which you saved the fragment metadata, and identification information of the fragment metadata).

Accordingly, section 130 of the index data includes the segment "sub_index_identifier", in which is stored information about the ID key index defined in section 120 of the index key segment 114 "key_value_decriptor for storing therein respective ranges of values of multiclutch, and identifying information about the fragments of the metadata corresponding to the values of multiclutch. Identifying information includes segments of the target container (target_container)in which is stored the corresponding identifying the container information for those containers that contain the fragments of the metadata, and the segments target_handle"storing relevant information about the fragment identifier data (handle_value).

The structure of the metadata will be more easily understood through Fig. 10, which illustrates the information about the index.

In Fig. 10 shows a section of the list of indices multiclone containing multiclutch for the Service Id and Published Time. The top-level node for a fragment of metadata, including multislice associated with the Service Id and the Published Time is "BroadcastEvent" 310, as indicated by the shaded area in Fig. 3. Therefore, XPath, "/TVAMain/ProgramDescription/ProgramLocationTable/BroadcastEvent" fragment "BroadcastEvent" is stored in the segment 111 "fragment_xpath_ptr", and the path XPath multiclone for the Service Id and the Published Time for the fragment "BroadcastEvent", which are "@ServiceId" 311a, and "EventDescription/PublishedTime" 311b, stored in the segment 112 "key_descriptor".

This structure metadata stream enables efficient search and access to the fragments of the metadata, if the search is carried out on the basis of more than one condition, that is, when the search item is a compound conditions.

Despite the fact that as an example, in the present embodiment, the above-mentioned multiclutch for the Service Id and the Published Time, in combination can also be used a variety of multiclone. For example, can be used multiclutch for the start and end of the program in connection with the broadcast schedule, multiclutch for surnames and names of the person (actor, Director or similar)included in the program, and so forth.

When using multiclutch for the start and end of the program in connection with the broadcast schedule, the top node of the fragment metadata, including multislice for the start and end of the program, can be "Schedule" (Schedule) (not shown). Therefore, XPath "TVAMain/ProgramDescription/ProgramLocationTable/Schedule" for the words "Schedule" can be stored in the segment 111 "fragment_xpath_ptr", and the path XPath, "@start and@end" multilocal for the start and end of the program for fragment 'Schedule' can be stored in the segment 112 "key_descriptor".

If you use multiclutch for surnames and names of the person (actor, Director or similar)included in the program, then the top node of the fragment metadata, including multislice for surnames and names of the person (actor, Director or similar), can be "PersonName" (not shown), and therefore, XPath "TVAMain/ProgramDescription/CreditsInformation Table/PersonName" fragment "PersonName" can be stored in the segment 111 "fragment_xpath_ptr",and XPaths "Go" and "GivenName" multilocal for surname and name of the person in the program for a fragment "PersonName" can be stored in the segment 112 "key_descriptor".

In Fig. 11 depicts a method of providing the metadata index that contains a structure corresponding to a variant of implementation of the present invention. Index metadata may be generated by the provider 200, which supplies audio/visual signals.

Information about the content, metadata, process blocks corresponding to the fragment, as described above (SI00). Multicloud provide a combination of keys associated with information about the fragments, for example, 'Service ID' and 'Published Time' (S200). Then provide section 130 index (sub_key_index) connection, in which segments, such as 114a, 114b and s etc. that contain ranges of values multiclutch provide, as described above (S300). Section 130 index data additionally includes identifying information of the metadata corresponding to the values of multiclutch (i.e. information about the container ID and the ID information piece of data respectively stored in the segments "target_container and segments "target_handle"shown in Fig. 9).

Provide (S400) section 120 of the index key contains representative key values representing the ranges of values of multiclutch. For example, with reference to Fig. 9, it includes a representative key value "509/10:00" and "519/10:00" (113a and 113b), representing a pre-determined ranges 500˜509/09:10-10:0 and 510˜ 519/09:10-10:00 (114a and 114b) values multiclutch for 'Service ID'/'Published Time', as combined. In this embodiment, the Service ID has a higher priority relative to the Published Time. Section 120 of the key index additionally includes identifying information about the section 130 index of the subkey that contains the value of multiclutch (i.e. information about the identity of the container relative to the container in which is stored an index partition of the connection according to Fig. 9, and the information about the index ID of the connection). It is clear that there may be provided other multiclutch and the relevant sections of the index keys and/or index partitions plug as described above.

Provide (S500) section 110 of the list of index keys, in which information about multicouche, that is, the location information of the fragment metadata belongs to each field constituting provide multiclutch, and the location information for each field in the metadata, feature-based multiclutch. For example, if the keys 'Service ID' and 'Published Time' United, information about multislice for the combined 'Service ID' and 'Published Time', for example, the XPath for the target fragment metadata for indexing (/TVAMain/ProgramDescription/Program LocationTable/BroadcastEvent) and XPath multiclutch for a fragment of metadata (XPath "@ServiceID" for the Service ID and XPath "EventDescription/PublishedTime" for Pubished Time) are included under section 110 of the list of index keys.

The above steps can be processed in reverse order, in other embodiments, implementation of the present invention. Additionally, according to some embodiments of the present invention can be deleted step of providing section 120 of the index key, including representative key value (S400), or the stage of the section (S500) list of index keys.

Later in the document with reference to Fig. 12 will be described the above search method designed to retrieve metadata that satisfy more than one search condition, implemented using patterns mnogoluchevogo index in accordance with the embodiment of the present invention.

A search condition for searching enters, for example, a user (S1100). In the index metadata (S1200) search values multiclutch that meet the entered search criteria. The desired fragment metadata is extracted using the identifying information for a fragment of metadata corresponding to the value of multiclutch, using the obtained values of multiclutch (S1300). Through these steps, remove metadata matching the search criteria. In the search terms entered by the user, can be included fields and value fields or ranges, which are subject to search.

This is the p value of multiclutch (S1200) includes the steps of identifying information location for a fragment of metadata, to which belong all the fields are entered search criteria, and information location for the fields in the fragment metadata (S1210), the search section 110, intended for list of indexes, keys, multiclutch consisting of fields containing the location information identical to the specific information, the location made using certain information location and retrieval in section 120, designed for index key found multiclutch (SI220), the search section 120, intended for an index of key, representative key value consists of the values of the fields you entered as search criteria, and search section 130 index of the subkey that contains the values of multiclutch in the range indicated by the representative key value found above (S1230), and search values multiclutch that satisfy the search criteria, found in the above section 130 index of the subkey (S1240).

The above steps S1220, S1230 and S1300, the stages of the search section 120 of the key index, index partition key and retrieve metadata respectively performed by using the identifying information section 120 of the index key, the identifying information section of the index data and the identifying information of the slice metadata. It is clear that, for example, if the range what zones metadata fields included in the search condition, there can be found several values multiclutch, and extracted more than one fragment, as described below in the document.

The search method as shown in Fig. 12, can be used when searching for a Service ID and Published Time described with reference to Fig. 10, as follows.

If the user enters the search terms '507-514' for the Service ID and a '9:30˜10:00' for Published Time (S1100), the location information for the desired fragment metadata define the fields of a combination of the Service ID in the range 507-514" and from Published Time in the range of "9:30-10:00", and define the location information fields in the fragment metadata (S1210).

Entered as search criteria, the Service ID and the Published Time, respectively, we have (values) "@ServiceId" and "EventDescription/PublishedTime" as information of the location in the fragment metadata. On this basis determine the location information for the desired fragment metadata as attribute of the desired fragment, i.e. XPath (S1210).

To summarize, according to the above steps, you can get the following:

For a fragment of XPath:

/TVAMain/ProgramDescription/ProgramLocationTable/BroadcastEvent

- XPath for Service Id: @ServiceId,

- XPath for Published Time: EventDescription/PublishedTime

- The value of the Service Id: 507<=ServiceId<=514,

- The value of the Published Time: 9:30<=EventDescription/PublishedTime<= 10:00.

Then in section 110 of the list of index keys search of multiclutch, suitable what about the XPath 111 for a fragment of metadata and XPath 112 for Service Id/Published Time, and extract (S1220) identifying information section 120 of the index key, which is found multiclutch. In the present embodiment, the Service Id is a higher priority than the Published Time. Search for in section 120 of the index key of the representative key values "509/10:00" 113a and 519/10:00" 113b, that is representative of key values that indicate the ranges (500-509/09:10-10:00 114a, 510-519/09:10-10:00 114b) values multiclutch to which they belong values multiclutch (507-514/09:30-10:00)that correspond to the search criteria, and retrieve section 120 index key (S1230) identifying information about the section 130 index of the subkey that contains representative values. Search values multiclone having key values "507/09:30", "507/09:40"... "509/10:00" and "510/09:30", "510/09:40"... "514/10:00"corresponding to the values of multiclutch (507˜514/09:30-10:00), corresponding to the search conditions, in section 130 of the index data, that is, segments 114a and 114b (S1240).

Extract from section 130 index data identifying information of the metadata corresponding to the values found multicouche (information about the container ID and the ID information of the fragment data stored in the segment "target_container" and the segment "target_handle," respectively), and then extract relevant fragments of the metadata extracted using identificarea information (S1300).

In Fig. 13 shows a device for searching metadata in accordance with the embodiment of the present invention. Device performing a search in the present invention is a device that performs the method of search metadata in accordance with the embodiment of the present invention described above with reference to Fig. 12.

The device 1000 includes the 1100 block of input data, which allows the user to enter search criteria, the receiving unit 1200, which adopts the content, metadata about the contents or index metadata, the storage device 1300, and stores the received content, metadata about the content or the metadata index, 1400 block management, which searches for values/values multiclutch corresponding to the input search condition from module 1100 data entry, and retrieval of desired metadata by using the obtained values/values multiclutch, and the 1500 block of output that outputs the result of the search performed by the control unit 1400.

The control unit 1400 compares the search terms entered from the 1100 block of input data, with values of multiclutch included in the index metadata stored on the storage device.

Stage of the search values multiclutch in accordance with one embodiment of the present and the gain, stage of the search multiclutch corresponding to the input search conditions (S1200), or the stage of extraction of the desired fragment(s) using the identifying information of the fragment corresponding to the found multiclutch, be interpreted with reference to the description made above in connection with Fig. 12.

In accordance with the present invention provided with the structure of the index metadata, allowing for more efficient search and access to information about the content, the method of providing the metadata index with such a structure, and method and device for identifying metadata using the metadata index.

INDUSTRIAL APPLICABILITY

As described above, the present invention enables simultaneous searches metadata Forum TV-Anytime Forum on compound conditions. When conducting searches metadata Forum TV-Anytime composite conditions overhead device search is reduced, thus allowing to reduce the search time and improve the efficiency of the device search. However, it is clear that while the illustrative non-limiting embodiments of the present invention overcome the above disadvantages and other disadvantages not described above, the present invention is not required to overcome the disadvantages described above, and illustrative is s, non-limiting embodiments of the present invention may not overcome any of the disadvantages described above. It is also clear that a system that uses the present invention also includes permanent or removable storage media such as magnetic and optical discs, RAM, ROM, a carrier wave, etc. on which the processing method and the data structure of the present invention can be stored and distributed. Operations can also be distributed via, for example, to boot from a network such as the Internet.

Although the present invention has been described in connection with the preferred embodiment shown in the drawings, this is merely illustrative. Specialists in the art will understand that various modifications and equivalents can be made without going beyond the scope and essence of the invention. Therefore, the scope of the present invention should be defined only in accordance with the accompanying claims.

1. The index structure multicouche designed to search for metadata divided into fragments, and this structure contains a list of multilocal, which correspond to the combination of metadata fields and the location information to determine multiclutch from the list, with an index structure m is sticluta determine the location information, the corresponding fields of the search terms in relation to metadata in the list of multilocal search multiclutch corresponding to the information of the location in relation to the search conditions from the combination of metadata fields and extract the fragment of the metadata using the found multiclutch.

2. The index structure according to claim 1, characterized in that it further contains the values of multiclutch and identifying information of the metadata corresponding to the values of multiclutch.

3. The index structure according to claim 2, wherein identifying the metadata information includes identifying information of some fragments of the metadata corresponding to the values of multiclutch.

4. The index structure according to claim 1, characterized in that the information location is expressed in XPath.

5. The index structure according to claim 1, characterized in that at least part of the information location is expressed pre-established code.

6. The index structure according to claim 1, characterized in that the information of the location contains the location information of the fragment, which includes multiclutch, and the location information of multiclutch in the fragment.

7. The index structure according to claim 1, characterized in that the metadata are the metadata definitions of the Forum TVA.

8. The index structure according to claim 1, characterized in that the addition contains a subkey, includes ranges of values of multiclutch and identifying information of some fragments of the metadata corresponding to the values of multiclutch, and section, including representative key values representing the respective ranges of values of multiclutch.

9. The index structure of claim 8, wherein each of the representative key value is the value of the corresponding range of values of multiclutch.

10. The index structure of claim 8, wherein the list includes identifying information about the section and the section additionally includes identifying information about the topic.

11. The index structure multicouche designed to search for metadata divided into fragments, containing the values of multilocal and identifying information of the metadata corresponding to the values of multiclone, and multiclutch combinations of metadata fields in this index structure multicouche search values multiclutch that satisfy the search conditions, and at a specified index structure to determine identifying information of the metadata corresponding to the detected value of multiclutch, extract the metadata found on the identifying information metadata.

12. The index is the structure according to claim 11, characterized in that it further contains the list of multiclone.

13. The index structure according to item 12, characterized in that it further comprises the location information to determine multiclone, and at least part of the information location is expressed pre-established code.

14. The index structure according to claim 11, wherein identifying the metadata information includes identifying information of some fragments of the metadata corresponding to the values of multiclone.

15. The index structure according to claim 11, characterized in that for multiclutch from multiclone index structure further comprises a representative value representing a predetermined range of values of multiclutch.

16. The index structure according to claim 11, characterized in that for multiclutch from multiclone index structure further comprises a subkey that contains the value ranges multiclutch and identifying information of some fragments of the metadata that correspond to the values of multiclutch, and a section containing representative key values representing the respective ranges of values of multiclutch.

17. The index structure according to claim 11, characterized in that respect comparisons multiclutch size, multicloud contains fields (k1, k2, k3 ... kn metadata with in accordance with the priority (k1>k2>k3>...kn), and a field is compared in sequence, starting with the first field having the highest priority, while values are compared arithmetically, if the values of multiclutch are numeric, or appreciate in lexicographical order, if the values of multiclutch are literal.

18. The index structure 17, wherein the first and second values multiclutch match (A1, A2, A3 ... an) and (b1, b2, b3 ... bn), respectively, and first and second values (A1, A2, A3 ... an) and (b1, b2, b3 ... bn) multiclutch defined as having the same size, if there is no field that has a different size.

19. The index structure multicouche designed to search for metadata divided into fragments containing section of the list of index key contains a list of multilocal, each multicloud corresponds to the combination of metadata fields section of the index key and index partition key of multiclutch contained in the list of index keys, and the partition index of the subkey contains the value ranges multiclutch and identifying information of some fragments of the metadata that correspond to the values of multiclutch, and the section of the index key contains representative key values representing for the matter of ranges of values of multiclutch, the list of index keys search of multiclutch that satisfy the search criteria in the section of the index data on detected multiclutch, the value of which corresponds to the range of values of multiclutch, search for the identifying information of the fragments of the metadata, and retrieve metadata found on the identifying information corresponding to the value found multiclutch.

20. The index structure according to claim 19, characterized in that section of the list of indexes of keys further comprises the location information to determine multiclone, and at least part of the information location is expressed pre-established code.

21. The computer-readable storage medium that is designed to search for metadata divided into fragments, and containing a data structure containing a list of multilocal, which correspond to the combination of metadata fields and the location information to determine multiclutch from the list, with the data structure, determine the location information corresponding to the fields in the search criteria in relation to metadata, and search a list of multilocal of multiclutch corresponding to the information of the location in relation to the search conditions from the combination of metadata fields, then remove the fra is ment metadata using found multiclutch.

22. The computer-readable storage medium that is designed to search for metadata divided into fragments, and containing a data structure containing the values of multilocal and identifying information of the metadata corresponding to the values of multiclone, and multiclutch combinations of metadata fields in this data structure search values multiclutch that satisfy the search conditions, the data structure, a search for identifying information metadata corresponding to the detected value of multiclutch, and retrieve metadata found on the identifying information metadata.

23. The computer-readable storage medium that is designed to search for metadata divided into fragments, and containing a data structure containing section of the list of index key contains a list of multilocal, each multicloud corresponds to the combination of metadata fields section of the index key and index partition key of multiclutch contained in the list of index keys, and the partition index of the subkey contains the value ranges multiclutch and identifying information of some fragments of the metadata that correspond to the values of multiclutch, and the section of the index key contains representative key values representing the ratio is eastwoodiae ranges of values of multiclutch, the list of index keys search of multiclutch that satisfy the search criteria in the section of the index data on detected multiclutch, the value of which corresponds to the range of values of multiclutch, search for the identifying information of the fragments of the metadata, and retrieve metadata found on the identifying information corresponding to the value found multiclutch.



 

Same patents:

FIELD: index structure of metadata.

SUBSTANCE: in accordance to the invention, structure of metadata index includes a list of multi-keys and position information for defining multi-keys, while information is determined, which corresponds to search condition fields, and multi-key, corresponding to position information, is searched for, after that, metadata fragment is extracted using the found multi-key.

EFFECT: increased index search speed.

2 cl, 15 dwg, 6 tbl

FIELD: technology for providing audio and visual services.

SUBSTANCE: in accordance to invention, signal has structure for transferring index with encoded multi-component key for determining position of component key of meta-data index of digital content, transported on basis of independent data unit, containing key index list section (index list), including multi-component key data, used in search for component key of index, while the data of multi-component key is encoded by single code value.

EFFECT: possible transfer of data stream structure with encoded multi-component key, useable for determining position of component keys of meta-data index of digital content.

2 cl, 5 tbl

FIELD: computer engineering.

SUBSTANCE: in accordance to invention, file version watermarks are included in source data file of an application. File version watermarks may indicate various properties of original data file. File version watermarks may include older version watermark, last version watermark, lesser version watermark, creation version watermark and object version watermark. In accordance to invention, file version watermarks are used to determine whether file or certain information in file correspond with previous, active or future version of an application. Respectively, invention allows to load or save original data file on basis of determined results.

EFFECT: creation of expandable file format, compatible with previous, current and future versions of an application; possible use of previous versions of applications for working with a file.

20 cl, 9 dwg

FIELD: medical information technologies.

SUBSTANCE: in accordance to method, medical databases are created and regularly updated; informative characteristics of patients health condition are formed on basis of case histories in medical databases; on basis of detected informative coefficients, deciding rules are created, considering cause-effect connections between pieces of medical information and biological age and health condition of patients; client units of practical doctors are equipped with software means for using formed deciding rules for information support of practical doctors; data pertaining to research and patient examination are recorded in client unit; appropriate deciding rules are used in client unit to determine biological age and to evaluate health condition of patient by groups: healthy, belongs to risk group or sick; to predict, when patient is included in risk group, the course of disease or pathological process; to provide, when patient is included in "sick" group, the clinical diagnosis with consideration of nature and severity degree of changes in main life support systems, individual features of organism and constitution factor of patient.

EFFECT: increased precision of diagnostics.

1 tbl

FIELD: systems for selling goods and services to population, using network technologies.

SUBSTANCE: in accordance to invention, in unified informational consolidating center, data input/output and identification block is meant for identification of user being buyer, seller, manufacturer, activation of controlling software block, for access to blocks of unified informational consolidating center depending on its user status. If user is buyer, then block for controlling personal account of buyer is initiated, if user is seller, then sales block is initiated for charging personal account of buyer with a part of price of product, and seller terminal is meant for, during purchases, to receiver payment of part of product price from buyer, and remaining part of price is received from virtual bank block.

EFFECT: creation of new software-hardware complex for selling goods with compensation of consumer losses.

2 dwg

FIELD: metadata searching means.

SUBSTANCE: in accordance to invention, in a carrier, containing indexing metadata structure, in first variant, indexing structure includes a list of keys, consisting of predetermined metadata fields, where at least part of information about position is expressed in form of predetermined code. In second variant, indexing structure contains section of list of key indexes, section of key index, section of key sub-index. In accordance to third variant, contains a list of keys and information about position for determining keys, key values and metadata identification information.

EFFECT: decreased metadata searching time.

3 cl, 12 dwg, 6 tbl

FIELD: information technologies, possible use for optimizing storage and selection of data.

SUBSTANCE: in accordance to method, spatial data structure is formed with elements in form of original n-dimensional intervals; lens is determined, being a 2n-dimensional interval of interval request operator, representing an instruction about selection of data of required n-dimensional intervals with description of given interval and positioning conditions of required ones relatively to it, while lens is determined in accordance to rose of intervals, representing virtual two-dimensional geometric diagram of areas such as 2n-dimensional points in axes xp and yp of their space, coordinates {xp,yp} of which are appropriate coordinates of p-projections of n-dimensional intervals appropriate for these points, where p-projection of n-dimensional interval is its projection on p-axis of its space basis; built and stored on physical data carrier is interval request operator about selection from data structure of such points, which are enveloped by this lens, by means of this operator interval request to structure is performed, resulting in a set of data of 2n-dimensional points, simultaneously being the data of sought after intervals corresponding to the data.

EFFECT: possible efficient execution of any interval requests in one spatial data structure.

10 dwg, 1 tbl, 8 ex

FIELD: information extraction systems engineering.

SUBSTANCE: system contains data storage, analysis mechanism of lower level, analysis mechanisms of higher level, indexer. In accordance to method, on basis of first set of rules, appropriate for first analysis mechanism, first key is connected, which is sent output second analysis mechanism, in which second key is generated based on second set of rules, first and second keys are connected to objects and keys and key values are indexed.

EFFECT: decreased time and computing resources spent on processing of large data arrays to extract required information.

2 cl, 5 dwg

FIELD: criminalistics and forensic examination.

SUBSTANCE: automated workplace consists of stand for researching electronic information carriers and personal computer. Stand featured in invention consists of controllable commutation device, ensuring possible mating of electronic information carrier and personal computer, and a source of controllable voltage. Controllable commutation device has m+n inputs/outputs and is represented by a set of m·n controlled rectifying cells, forming a commutation matrix of m×n dimensions, connecting 1÷m and (m+1)÷(m+n) inputs/outputs, while m=k+1, numbers k and n corresponding to maximal values of numbers of contacts of sockets of personal computer and electronic information carrier, respectively. Controllable rectifying cell is in turn represented by device, providing controllable capability of one-direction commutation with controllable transfer coefficient.

EFFECT: no limitations on types of electronic information carriers being connected, increased quality and speed of reviews of electronic information carriers, in other words, suggested automated workplace allows highly reliable fast access to information, stored in memory of electronic information carrier received for review, while quantitative and qualitative characteristics of electronic information carriers are not changed.

3 dwg

FIELD: informatics; computer technology.

SUBSTANCE: device can be used for soling tasks of composing dictionaries, manual as well as for creation of new databases. Device has entrance memory unit, processed words memory unit, unit for analyzing search, substitution memory unit, substitution unit, result storage unit, control unit.

EFFECT: widened functional abilities; improved reliability of operation; simplified algorithm of operation.

16 dwg

FIELD: data access technologies.

SUBSTANCE: method includes assignment of simplified network address, recording URL and converting numbers into storage system with net access, inputting assigned number into computer, transferring inputted number to storage system, converting number to URL, receiving page matching URL, and displaying it. Method for use in operation systems for message transfer include intercepting system level messages to certain objects and forming pseudonym messages during that. Systems realize said methods.

EFFECT: broader functional capabilities.

12 cl, 30 dwg

FIELD: computers.

SUBSTANCE: system has entries memory block, words memory block, control block, substitutions block, n blocks for searching and replacing.

EFFECT: broader functional capabilities.

17 dwg

FIELD: computers.

SUBSTANCE: system has nine registers, four address selectors, triggers, AND elements, OR elements and delay elements.

EFFECT: higher speed.

8 dwg

FIELD: computers.

SUBSTANCE: system has operation mode setting block, first and second blocks for selecting records addresses, block for forming addresses for reading records, data output block, first and second record codes comparison blocks, records quality comparison block, year intervals comparison block, records selection control block, register, adder and OR elements.

EFFECT: higher speed of operation.

10 dwg

FIELD: computers.

SUBSTANCE: system has memory for programs, including browser, display block, database for storing documents, addressing control block, while each document of base has at least one link with indicator of its unique number and indicator with address of program for control stored in addressing control block, system contains also, connected by data buses and control of other blocks of system, memory for links of couples of unique numbers of links and forming means for lists of unique numbers of documents links, which are interconnected.

EFFECT: higher efficiency.

2 cl, 1 dwg

FIELD: telecommunication networks.

SUBSTANCE: messages, sent by cell phones, are formed by means of printed and public-distributed classifier, wherein at least one category is made with possible detection of at least one identifier of individual mark of object, identifier is sent by sender via at least one message to computer server with software, which transfers such message into database record at server for its transfer to at least one receiver, or searches for such record in database at server in accordance to received message and transfers to sender of such message at least one found database record.

EFFECT: broader functional capabilities.

2 dwg

FIELD: web technologies.

SUBSTANCE: method for integration of printed business documents, requiring original signature, with electronic data concerning these documents and later extraction of data, inputted for forming documents, is characterized by steps for forcing end user or agent to input all necessary data for forming of required document, saving collected data in database, linking saved data to unique ID code and printing unique ID code on printed document during printing. Printed documents is signed by end user and sent together with supporting documentation. When document is received by business-client, business-client inputs ID code, which is then used for access to saved data, and updates private database of business-client with all data, used for creation of original documents.

EFFECT: higher efficiency.

2 cl, 7 dwg

FIELD: computer science.

SUBSTANCE: device has string memory block, comparator, memory block for words and substitutes, block for analysis and forming of displacement results, block for storing string address, control block.

EFFECT: broader functional capabilities, higher reliability.

10 dwg

FIELD: data bases.

SUBSTANCE: method includes presenting operations at all levels of company in form typical product life cycle tree, wherein existing objective functional-technological connections of each manufacture stage are decomposed, and forming information system in form of pertinent-relevant complex information system and search, for which typical structure-information modules of information system are formed, system objective information requirements of data consumers, being a result of decompositions by levels of operations and problems, are determined as precisely as possible, data base of found documents in form of files is formed of key nodes with set of elementary data block for each system information requirement and files of information system modules, starting from lower levels of current stage and then upwards, while each data block has a list of pertinent documents ordered by determined information requirements.

EFFECT: higher search efficiency.

13 cl, 11 dwg

FIELD: computer science.

SUBSTANCE: system has first, second, third, fourth and fifth registers, first and second memory blocks, first, second and third decoders, triggers, elements AND, OR and delay elements.

EFFECT: higher speed of operation.

1 dwg

Up!