Index structure of meta-data, method for providing indexes of meta-data, and also method for finding meta-data and device, using indexes of meta-data

FIELD: index structure of meta-data, provided for finding information about content.

SUBSTANCE: in accordance to first variant of method, information about position is determined, key search is performed, and meta-data are extracted using found key, and in accordance to second variant of method, access to list of combinations is performed, in which meta-data key is searched for, identification information of meta-data is determined, and meta-data are extracted using found identification information. Devices for realization of these methods contain input block and control block.

EFFECT: possible fast search for information about content.

4 cl, 12 dwg, 6 tbl

 

The technical field to which the invention relates

The present invention relates to an index structure of metadata provided to search for information about the content and method of providing metadata indexes, as well as to a method and apparatus for metadata search using an index structure of metadata. In particular, the present invention relates to an index structure of metadata that contains information about the key, at least part of which is encoded, in order to provide a more efficient search of information about the content, when the metadata XML (extensible markup language) content in digital form, as defined in the documents of the TV-Anytime Forum (hereinafter referred to as "TVA") (mentioned metadata hereinafter referred to as "metadata TVA") are divided into chunks in an independent unit and is transmitted in chunks; to a method for providing metadata indexes, as well as a method and apparatus for search metadata using metadata indexes. This application is based on patent applications Korea No. 2002-43097 and No. 2002-62913, the contents of which are incorporated here by reference.

Prior art

TV-Anytime Forum is a private organization for standardization, founded in September 1999 to develop standards for the provision of services related to AU jvisualvm data in a user-friendly environment, for example in the personal digital recording (PDR), with a personal storage device of large capacity. In particular, the purpose of providing these services is to enable all users to view and listen to programs of different types (for example, related to conventional broadcasting services, online interactive features and the like) in the desired time and a desired image on the basis of the personal storage device.

TV-Anytime Forum has managed working groups for business models, organizations, links to system/transmission interfaces/contents, descriptions, metadata, rights management and protection, etc. with the goal of establishing standards. With regard to metadata that are relevant to the present invention, by June 2002 was developed first draft specification metadata "1stDraft of Metadata Specification SP003v1.3".

Next, with reference to figure 1 briefly describes the configuration PDR. The PDR device 100 receives video/audio signals and metadata from the provider (service provider) 200 that provides video/audio signals through many different networks using, for example, reflected by the ionosphere signals and satellite signals, as well as via the Internet, etc. that collects watched and listened to the samples and data is e about the personal tastes of the users, if necessary, and passes them to the service provider 200, providing video/audio signals. PDR 100 includes a storage device of large capacity to store the received video/audio signal and metadata. PDR 100 further contains software tools for storing and playback of audio/video signals and Appendix e of the guide programmes (EPG) to retrieve and display metadata for the video/audio signals. The user is provided with the metadata for the video/audio data, i.e. names of programs, plays, programs, etc. through the screen guide with mesh transmission of the EPG application, shown in figure 2, selects the desired program and takes it through the network in real time or play video/audio data previously stored in a storage device of large capacity.

Metadata refers to data that describes the content (programs)such as the title and summary of the programs and are defined here as "data about data". Specifications TV-Anytime Forum for metadata TVA their structure is defined by using the language of the schema (logical patterns in databases) XML (see XML 1.0 of the W3C (World Wide Web Consortium)), a Standard from the W3C (Consortium for the advancement of standards for XML); in addition, you specify the semantics and attributes related metadata elements. The TVA metadata, including the iesa to the content, is configured via an XML document with root node "TVAMain (300), as shown in figure 3. The TVA metadata related to software, is configured, for example, using such sites as the ProgramInformation table (information about programs), table GroupInformation (group information), ProgramLocation table (location), table ServiceInformation (information and services), etc. under the node "ProgramDescription" (program description).

In the TV-Anytime Forum the TVA metadata is transmitted in fragments in the form of an independent unit to transfer a large amount of metadata TVA in streaming format. Next, with reference to figure 4 describes the concept of fragments. The fragments obtained by dividing TVA metadata that is configured via XML documents shown in figure 3, the pre-defined tree structure. For example, if all the TVA metadata is divided into a tree structure (TVAMain fragment), which includes the top node "TVAMain" and pre-defined child nodes beneath this top node, the tree structure (the ProgramInformation fragment), which includes the upper ProgramInformation table node and child nodes beneath this top node, the tree structure (fragment BroadcastEvent (event broadcast)), including the top node with information BroadcastEvent and child nodes beneath this top node, each of the selected tree structures becomes fragm Tom. These fragments can be transferred independently from the other parts, and they can be accessed separately.

For individual access to the fragments you need to know the node referenced by the passed metadata TVA, i.e. the node that corresponds to the top node of the fragment metadata TVA, in the entire tree structure, metadata, and describe appropriate ways in fragments TVA metadata keys contained in the transferred fragment metadata TVA. For this purpose, use the XPath, which is a syntax for describing paths to one or more nodes in the XML document defined by the W3C standard. The term "key" refers to a special metadata field used for indexing, and also means the child nodes of the node referenced by the fragment. These keys correspond to fields (search conditions)filled in by the user, such as "ID") services" and "Declared time."

For efficient search and access the parts will additionally need an index structure for keys included in the metadata fragments, and information about the index structure, that is, the index information is also transmitted regardless of the fragments of the metadata.

According to the terms provided by the TV-Anytime Forum, if a user wants to retrieve info is information about the program, meets a predetermined condition "Declared time", to identify the location (ID) fragment metadata satisfying the required condition "Announced time, use the index information transmitted regardless of the above-mentioned fragments, and then access an appropriate portion of the metadata location-based (ID), in order to extract the metadata that meet the condition "Declared time."

In the specification of the TV-Anytime Specification TV145, J.P. Evain, "1stDraft of Metadata Specification SP003v1.3", TV-Anytime Forum 17thmeeting, Montreal, Canada, June 2002; hereinafter referred to as the reference to the prior art for indexes, keys, offers streaming structure index data keys for the index of the slice metadata.

The description of the index structure is preceded by a description of the term "container"is defined in the documents of the TV-Anytime Forum.

TV-Anytime Forum defines the container as a storage device of the upper level, which transferred all the data related to the above-mentioned index information, and the fragments of the metadata, and such transfer call transfer upper level. If you describe briefly container, each container contains many sections, each of which stores index information or the fragments of the metadata. The container may be class is adopted to index the container and the container data depending on the information it contains, moreover, the index container contains sections with index information, such as a section of the list of index keys (key_index_list), the section of the key index (key_index)section sub-index key (sub_key_index), section of string storage (string_repository) and section data warehouse fragments (fragment_data_repository), while the data container contains sections of fragments of metadata, such as the partition table of the elements (elements_table), section of string storage (string_repository) and section data warehouse fragments (fragment_data_repository). The above classification is based on the content information stored in containers. The configuration index of the container is identical to the configuration data container.

Refer to the container, defined in the documents of the TV-Anytime Forum, as shown in figure 5, where the container data field contains the ID of the container (container_id) (not shown), and a large number of sections. In each section of the content stored in the "section_body" (body section), identified in accordance with the value encoded in "section_id". For example, section 10, the encoded value in the "section_id" equal "H", is identified as the section of the list of index keys (key_index_list); section 20, the encoded value in the "section_id" equal "H", identified as partition key index (key_index); section 30, the encoded value in the "sction_id equal H", identified as section sub-index key (sub_key_index); section 40, the encoded value in the "section_id" is "0X0001", identified as partition table of the elements (elements_table), and section 50, the encoded value in the "section_id" equal "H", identified as section data warehouse fragments (fragment_data_repository).

Fragments TVA metadata stored in section 50 stores the data fragments (fragment_data_repository) data container, and then you transfer them. Information ID (handle_value) for fragments of the TVA metadata in the data container is contained in section 40 of the table elements of the data container.

In conclusion, we should say that the TVA metadata uniquely identifies information container ID (container_id) and information of the fragment identifier metadata (handle_value) container, which includes a fragment of the TVA metadata.

In the above referenced prior art for indexes key features index key structure for indexing fragments TVA metadata stored in the above data container, i.e. a structure consisting of sections 10 list of index keys (key_index_list), section 20 of the key index (key_index) and section 30 sub-index key (sub_key_index). Because the syntax for this structure is described in detail in the above referenced preds the appropriate level of technology for indexes, keys, its detailed description is omitted here. Next, with reference to Fig.6 describes the structure illustrated using a segment index information.

Section 10 list of index keys (key_index_list)defined in the index key structure, provides a list of all the transferred keys. This list includes information about the key that identifies each key, and identification information section 20 of the key index (key_index), which is described below. Key information includes: (1) the location information of the fragment metadata related to the key; (2) the location information is key in this piece of metadata. Information about the location of the fragment metadata is expressed in XPath (fragment_xpath_ptr) in TVA. Information about the location of the key is expressed in XPath (key_xpath_ptr) for relative paths in a suitable fragment of nodes that are used as key in TVA.

XPath fragment metadata is the path to the root node of the XML document TVA metadata, i.e. the absolute path and XPath nodes that are used as keys, that is, the XPath of the keys, is the relative path of the key for the relevant fragment of the metadata. For a fragment of XPath metadata and XPath for the key 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 keys (key_index_list) includes ID the th information section 20 of the key index (key_index) each key, described below (i.e. information container ID (container_id)stored in the partition 20 of the key index (key_index), and identifier information of the index key). Information container ID information and the ID of the index key stored in the segment "index_container" section 10 list of index keys (key_index_list) and the segment key_index_identifier", respectively, and then sending this information.

Section 20 of the key index (key_index)defined in the index key structure, provides a list of information that represents the ranges of key values included in corresponding section 30 sub-index key (sub_key_index), i.e. the maximum key value of the number of key values in the appropriate range (hereinafter referred to as "the representative key value"), and the identification information section 30 sub-index key (sub_key_index)related to each of the representative key value (that is, information container ID (container_id)relating to the container in which the partition is stored sub-index key, and the identifier information of the sub-index key).

Accordingly, section 20 of the key index (key_index) includes the segment "key_index_identifier" to store the information in the ID key index defined in section 10 of the list of index keys (key_index_list), the segments 13 "high_key_value to save them R the representative key values for the respective ranges of key values, included in the section 30 sub-index key (sub_key_index), as well as segments sub_index_container" segments "sub_index_identifier" for identification information section 30 sub-index key (sub_key_index) (i.e., for the information of the ID of the container (container_id)relating to the container that contains the section 30 sub-index key (sub_key_index), and the relevant information of the ID sub-index key). Section 30 sub-index key (sub_key_index)defined in the structure of the index keys, provides a list of key values. This list further includes identification information of the fragments of the metadata corresponding to the key values (i.e. information container ID (container_id) for containers that store fragments of the metadata, and information identifiers (handle_value) fragments of the metadata).

Accordingly, section 30 sub-index key (sub_key_index) includes the segment "sub_index_identifier" to store the information in the ID sub-index key, as defined in section 20 of the key index (key_index), the segments 14 "key_value" to store them in respective ranges of values of the key segments target_container" to store them in the appropriate information container ID (container_id) for containers that store the metadata fragments and segments target_handle" to store them in the relevant information of the identity e is the R fragments (handle_value). Index key structure can be easily understood, referring to Fig.7, where provides information about the indexes.

7 shows the section of the list of index keys (key_index_list), which includes the keys related to the service identifier (Service ID), the announced time (Published Time) and the declared length (Duration Published). The top node of the fragment metadata, which includes the keys related to the service ID, the announced time and the declared length, is a "BroadcastEvent" 310, as shown in figure 3 as a hatched block. Accordingly, the XPath "/TVAMain/ProgramDescription/ProgramLocation Table/BroadcastEvent" fragment "BroadcastEvent" is stored in the segment 11a "fragment_xpath_ptr", and the XPath path to the key service identifier declared time and the declared length for a fragment "BroadcastEvent", i.e. "@ServiceId" (a figure 3), "EventDescription/PublishedTime" (311b figure 3) and "EventDescription/PublishedDuration" (s figure 3) are stored in the segment 12A "key_xpath_ptr".

The index structure will become clearer when referring to Fig.7, which shows information about the indexes.

7 shows the section of the list of index keys (key_index_list), which includes keys for service identifier declared time and the declared length, where the top node metadata related to the service ID, the announced time and the declared length, isone "BroadcastEvent" 310, as shown in figure 3 as a hatched block. Accordingly, the XPath for the fragment "BroadcastEvent" "/TVAMain/ProgramDescription/ProgramLocation Table/BroadcastEvent" is stored in the segment "fragment_xpath_ptr"and the corresponding xpaths for key service identifier declared time and the declared length for a fragment "BroadcastEvent", "@ServiceId" (see a figure 3), "EventDescription/PublishedTime" (see 311b figure 3) and "EventDescription/PublishedDuration" (see s figure 3) are stored in the segment "key_xpath_ptr".

Figure 7 also shows the section 20 of the key index (key_index) and section 30 sub-index key (sub_key_index) service identifier (path XPath key: @ServiceID) among the sections of the list of index keys (key_index_list).

In such an index structure when the input conditions for searching metadata, determining location information fields for the search terms entered in the metadata and comparing certain thus location information with information about the keys in the index list of keys, in order to find the key, having defined above location information in the index list of keys, inevitably excessive expenditure of resources because of the need to compare both ways XPath. A similar problem occurs when a key that specifies the relative path from the pieces of key information are compared against the location information. In particular, this problem becomes special is serious, when compared against the location information fragments that are more complex than the keys. Because the XPath fragment representing the location information among key information that describes the path to the relevant node from the root node in the XML document, transmission costs are not effective, and the costs of interpretation of XPath in the terminal are high. For example, the XPath fragment events broadcast indicating the location information of the program among the fragments of TV-Anytime, can be represented in the form "/TVAMain/ProgramDescription/ProgramLocation Table/BroadcastEvent". Meanwhile, in order to represent one node in the XML document, the XPath can be expressed in an alternative way. In the case for event broadcasting, in addition to the aforementioned normal view, in an alternative embodiment, the XPath can be expressed as "/TVAMain//BroadcastEvent" or "//BroadcastEvent" etc. Here "//" means a child node in the structure of the XML document. Therefore, the operation for checking whether the fragments are the same, by using the XPath is not a simple operation, where only matched with each other a simple line. In particular in the analysis/comparison-relevant way will require the expenditure of resources, if the XPath is expressed in an abbreviated format.

The invention

Thus, the objective of this izaberete the Oia is the creation of an index structure of metadata, includes information about the key that is encoded in such a way as to provide the possibility of fast search of information about the content.

Another objective of the present invention is to provide a method for providing index metadata, able to quickly find information on the content and manner of the search metadata using the metadata index and search using the index metadata. Additional tasks and/or advantages of the present invention in part will be set forth in the following description and in part will be obvious from the description, or can be obtained in the practical implementation of the invention.

To solve the above and/or other objectives of the present invention is an index structure for metadata divided into fragments, containing a list of keys corresponding to fields of the metadata, and location information to determine the key, and at least part of the location information is expressed as a predetermined code.

This index structure can additionally contain key values and identification information of the metadata corresponding to these key values. The index structure may further comprise a subsection that includes ranges of values of the key and ID the th information of those fragments of the metadata, which match the above key values; section, which includes a representative key values representing the respective ranges of key values.

The list may include identification information of the section and the section may further include identification information of the subsection. Each of the representative key value can be a value from the corresponding range of values of the key.

Another part of the location information may be expressed in the form of another predetermined code or Xpath.

Location information may include location information of the fragment, which includes the key, and the location information of the key in this fragment.

One of the location information of the fragment and the location information of the key can be expressed as a predetermined code.

Remaining one of the location information of the fragment and the location information of the key can be expressed in the form of another predetermined code or Xpath.

Preset code may be assigned in advance to the location information, which is often referred to. Predefined code can contain Xpath as additional information, while the corresponding segment/key corresponds to the type of determination is conducted by the user.

To solve the above and/or other objectives of the present invention provides another index structure for metadata divided into fragments, which includes the section of the list of index keys that contains a list of keys corresponding to fields of the metadata, and location information for defining the keys, and at least part of the location information is expressed as a predetermined code; section index key; section sub-index key for a key from a list of index keys section sub-index key contains the ranges of values of the key and identification information of those fragments of metadata that match the above key values, and the index partition key contains a representative key values representing the respective ranges of key values.

A representative value of the key may include at least one of the following values: maximum value, minimum value or an intermediate value among the values of the appropriate range.

Metadata can be structured metadata defined by the TVA organization Forum. The index structure may further comprise an appropriate section of the index key and the appropriate section comprise a key for another key from the list of index keys.

Information about the place is ulozhenie may contain information about the location of the fragment, includes keys, and information about the location of the keys in this fragment. Section list of index keys may further comprise identifying information section of the index key and index partition key may further comprise identification information section sub-index key.

To solve the above and/or other objectives of the present invention provides another index structure for metadata divided into fragments, containing a list of keys corresponding to fields of the metadata, and location information for defining the keys, and at least part of the location information is expressed as a predetermined code, as well as key values and identification metadata information corresponding to said key values.

Identification information may include identification information of the fragments of the metadata corresponding to the values of the keys.

To solve the above and/or other objectives of the present invention, a method of providing an index structure for metadata divided into fragments, containing the list of keys corresponding to fields of the metadata, and location information to determine the key, at least part of the location information is expressed as is Aranea given code.

The method may further comprise providing key values and identification information of the metadata corresponding to said key values.

The method may further comprise providing subsection, including ranges of values of the key and identification information of those fragments of metadata that match the above key values, and providing section includes a representative key values representing the respective ranges of key values.

Location information may include location information of the fragment, which includes the key, and the location information of the key in this fragment.

The list can contain a list that includes one of the location information of the fragment and the location information of the key is encoded with a predetermined code.

Predefined code can contain Xpath as additional information, while the corresponding segment/key matches the type specified by the user.

To solve the above and/or other objectives of the present invention there is another method of providing an index structure for metadata divided into fragments, containing a provision of sections list of indexes CL is whose, contains a list of keys corresponding to fields of the metadata, and location information defining the keys, and at least part of the location information is expressed as a predetermined code; providing a partition of the index key; provision of sections comprise key when this key from the list of index keys section sub-index key contains the ranges of values of the key and identification information of those fragments of metadata that match the above key values, and the section of the index key contains a representative key values representing the respective ranges of key values.

To solve the above and/or other objectives of the present invention developed another method of providing an index structure for metadata divided into fragments, containing the list of keys corresponding to fields of the metadata, and location information for defining the keys, and at least part of the location information is expressed as a predetermined code, and the provision of key values and identification information of the metadata corresponding to said key values.

Identification information may include identification information of the fragments of the metadata corresponding to the values of the keys.

For the solutions of the above and/or other objectives of the present invention, a method of search is divided into fragments of metadata using index contains a list of keys corresponding to fields of the metadata, and location information for defining the keys, the method includes searching, based on the metadata index, key corresponding to the search condition of a metadata field, at least part of the location information defining the key, expressed as a value of a preset code, and extracting a fragment of the metadata by using the found key.

The search key may contain identifying information about the location of the corresponding field of search terms in relation to metadata, and search key corresponding to the location information in the field of search terms.

The fragment contains the search key values satisfy the search condition, among the key values from the index, and extracting a fragment of the metadata using the identification information of the metadata corresponding to the key value.

In response to many of the key values that satisfy the search condition, the fragment may contain extract the fragments of the metadata that match the key values that satisfy the search condition.

Search values may include the search of representative key values satisfy the search condition, among the representative of the values of the index key, the respective ranges of key values, and the search for values in the range of values corresponding to the representative key value.

The index may contain a section for list of indexes of the keys contains the list section of the sub-index of the key that contains the ranges of values of the key and identification information of those fragments of metadata that match the above key values, and the index partition key that contains a representative key values representing the respective ranges of key values.

Location information may include location information of the fragment, which includes the key, and the location information of the key in this fragment.

To solve the above and/or other objectives of the present invention there is another method of search is divided into fragments of metadata, which includes access to a list containing many combinations of location information of the fragment and the location information defining at least one key in this fragment, with one of the location information of the fragment and the location information of the key is expressed as a predetermined code, and search in the list of combinations corresponding to the entered search condition of at least one key metadata.

The remaining information about octopole the situation can be expressed in the form of another predetermined code or Xpath.

The method may further include removing one or more fragments of the metadata corresponding to the identification information of the metadata identified by the selected combination.

To solve the above and/or other objectives of the present invention is a device for finding a sliced metadata using an index that contains a list of keys corresponding to fields of the metadata, and location information defining the keys, which includes the input block for receiving search conditions containing the metadata field as a search parameter, and a control unit for searching, based on the metadata index, key matching said search condition, at least part of the location information defining the key, expressed as a value of a preset code, and retrieve metadata by use the found key.

The value of the predetermined code can be an Xpath as additional information, while the corresponding segment/key matches the type specified by the user.

The control unit may search for a key meeting the search condition, among the key values from the index, and retrieve identification information of the fragment metadata that meet the corresponding key value.

The device may further comprise a receiving unit for receiving metadata block data storage to store the received metadata and output unit to output the results of the search conducted by the control unit. In response to many of the key values that satisfy the search conditions, the control unit may extract the fragments of the metadata that match the key values that satisfy the search condition.

The control unit may search for a representative key values satisfy the search condition, among a representative of the index key values corresponding to the ranges of key values, and the search for values in the range of values corresponding to the representative key value. Metadata can be structured metadata defined by the organization TV-Anytime Forum.

To solve the above and/or other objectives of the present invention provides another device for searching divided into fragments of metadata that contains the input block for receiving search criteria in at least one of the metadata key and a control unit for selecting from a list containing many combinations of location information of the fragment and the location information defining at least one key in this fragment, the combination that satisfies the condition of p is the claim, this is one of the location information of the fragment and the location information defining at least one key, expressed as a predetermined code.

The remaining information about the location can be expressed in the form of another predetermined code or Xpath. The control unit may extract one or more fragments of the metadata corresponding to the identification information of the metadata identified by the selected combination.

To solve the above and/or other objectives of the present invention is provided a machine-readable medium containing a data structure for storing the index is divided into fragments of metadata used to search metadata, and the data structure contains a list of keys corresponding to fields of the metadata, and location information to determine the key, and at least part of the location information is expressed as a predetermined code.

To solve the above and/or other objectives of the present invention is provided a machine-readable medium containing a data structure for storing the index is divided into fragments of metadata used to search metadata, while the structure of the data section contains the list of indexes of keys containing a list of keys corresponding to fields of the metadata, and location information for defining the keys, moreover, at least part of the location information is expressed as a predetermined code; section index key; section sub-index key for a key from a list of index keys section sub-index key contains the ranges of values of the key and identification information of those fragments of metadata that match the above key values, and the section of the index key contains a representative key values representing the respective ranges of key values.

To solve the above and/or other objectives of the present invention is provided a machine-readable medium containing a data structure for storing the index is divided into fragments of metadata used to search metadata, and the data structure contains a list of keys corresponding to fields of the metadata, and location information for defining the keys, and at least part of the location information is expressed as a predetermined code, and key values and identification metadata information corresponding to said key values.

To solve the above and/or other objectives of the present invention for each of the above methods is provided a machine-readable medium containing Mashinostroenie commands to perform operations suitable the way.

List of figures

The above and other objectives and features of the present invention will become more apparent from the following description of preferred options together with references to the accompanying drawings, in which:

1 is a diagram illustrating the concept of conventional PDR;

figure 2 - screen guide with mesh gear in the usual application, EPG;

figure 3 is a block diagram illustrating the structure of a conventional metadata defined TV-Anytime Forum;

4 is a diagram illustrating the concept of the normal fragment defined by TV-Anytime Forum;

5 is a diagram illustrating the concept of a conventional container defined by TV-Anytime Forum;

6 is a block diagram illustrating an index structure of metadata using a standard schema keys;

7 is a block diagram illustrating an index structure of metadata and the search process using standard circuit switches;

Fig is a block diagram illustrating an index structure of metadata according to a variant of the present invention;

Fig.9 is a block diagram illustrating an index structure of metadata and the search process according to a variant implementation of the present invention;

figure 10 is a schematic illustration of a method of providing metadata indexes according to a variant implementation of the present invention;

11 is a block diagram showing pic is b postamerican according to a variant implementation of the present invention;

Fig diagram illustrating a device for searching metadata according to a variant implementation of the present invention.

The best option of carrying out the invention

Next, with reference to the accompanying drawings describes the index structure of metadata, proposed to search for information about the content and method of providing indexes, metadata, and method and apparatus for metadata search using an index structure of metadata.

In this description of embodiments of the invention in order to simplify describes metadata-based TVA; however, this should not be interpreted or construed as restricting the scope of protection of the present invention.

On Fig shows the index structure of metadata for searching metadata according to a variant implementation of the present invention, while the index structure includes information for determining a key for the purpose of indexing fragments TVA metadata stored in the data container, as described above. Below are described the section 110 list of index keys (key_index_list), section 120 of the key index (key_index) and section 130 comprise key (sub_key_index), and then describes the index structure that includes encoded information about the keys, some mentioned syntax.

The syntax for specifying an index with which ructure metadata corresponds to one variant of implementation of the present invention and includes, in particular, the coded information about the keys differs conceptually from the syntax defined in reference to the prior art for the standard indices of keys, in that it contains the new structures introduced to the concept of encoding key information, such as fragment_descriptor() (handle fragment) and key_descriptor() (key descriptor), and reorganizes the structure of the partition 110 list of index keys (key_index_list), section 120 of the key index (key_index) and section 130 comprise key (sub_key_index).

Section 110 of the list of index keys (key_index_list) contains information about the keys, determining the appropriate keys and identification information section 120 of the key index (key_index), which are described below.

Information about the keys used to identify keys, that is, the location information in the metadata, which are metadata fields that make up the keys. The key information contains information about the location of the fragment metadata, which owns the fields that form the key in metadata (hereinafter this is called "information about the location of the fragment, which is expressed in the way XPath fragment in TVR (fragment_xpath_ptr), and information about the location of the fields that comprise the keys that are in the corresponding fragment metada the data (hereinafter this is referred to as "location information of the key, that is, the XPath for the relative path of the node in the appropriate fragment used as a key in TVA, in which TVA is expressed in the form of XPath key (i.e. key_xpath_ptr).

1. Section list of index keys (key_index_list)

Section list of index keys (key_index_list) provides a list of all the transferred keys.

In the embodiment of the present invention "fragment_xpath_ptr"indicating the location information of the fragment in the standard section of the list of index keys (key_index_list) (expressed in XPath fragment in TVA)is replaced with fragment_descriptor().

Table 1
SyntaxNo. of bits (replaceable)
key_index_list() {
for (j=0; j<key_index_count;

j++) {
fragment_descriptor()16
key_descriptor()16
Index_container16
key_index_identifier8
}
}

key_index_count: specifies the number of transmitted key, i.e. the number of indices for the entire XML document.

fragment_descriptor(): corresponds to the XPath location for the target track (target fragments), subject to indexation. According to a variant implementation in the present invention, information about the location of the fragment is expressed as a predetermined code, as shown below in table 3 for the standard type of fragment. The type of the fragment is not limited to the standard type of the fragment on table 3, and the fragment can be formed quite randomly, as far as its shape can specify XPath fragment to determine the keys.

key_descriptor(): corresponds to the XPath key in the XPath location of the target fragment to be indexed. If information about the location of the key represented as a predetermined code, the same as the above type of the fragment can be described by the standard type of key. As described above with reference to fragment_descriptor(), the key type is not reduced to the standard key type.

index_container: identifies the container in which is specified partition key index (key_index).

key_index_identifier: section identifies the key index (key_index) in the container specified by index_container. Section the key index (key_index) can be identified uniquely in combination index_container and key_index_identifier.

2. Handle fragment (fragment_descriptor)

"fragment_descriptor()" provides the structure to encode the special bits (which may be encoded with an arbitrary number of bits, for example, 8 bits, 16 bits, and so on) in relation to a commonly used type of standard fragment, and at the same time ensure Ecevit structure, able to describe XPath as additional information in relation to the type of metadata defined by the user. That is, if fragment_descriptor equal to "0xFF", it indicates a user-defined fragment, and thus immediately describes the XPath for the corresponding fragment defined by the user.

Table 2
SyntaxNo. of bits (replaceable)
fragment_descriptor() {
fragment_type8
if (fragment_type == 0xFF)

{
fragment_xpath_ptr16
}
}

fragment_type: represents the type of fragments to be indexed. The encoded values are assigned to frequently used standard types of fragments. If fragment_type is encoded 0xFF, then as more information is added fragment_xpath_ptr.

Table 3 presents the encoded value for position information of frequently used types of fragments when the search is conducted in the TV-Anytime. However, the types of fragments and the encoded value in this embodiment of the invention is not limited to the shown in the table and can be extended in accordance with applications.

Table 3
ValueDescription
HNot defined
HThe ProgramInformation fragment
HGroupInformation fragment
HFragment CreditsInformation
HFragment ProgramReview
HFragment SegmentInformation
HFragment ServiceInformation
HBroadcastEvent fragment
0FFThe fragment indicated by the user
0x08-0x0E

0x10-0xFF
Reserved

3. Key descriptor (key_descriptor)

"key_descriptor()" provides the structure for encoding information about the location of the keys that have a high frequency of use, for special bits when a search is performed and, at the same time, the structure of the description key type user-defined XPath. For example, if key_descriptor equal to "0xFF", it indicates the key defined by the user. Thus, XPath is described as additional information for the key defined by the user.

Table 4
SyntaxNo. of bits (replaceable)
key_descriptor() {
key_type8
if (key_type == 0xFF) {
key_xpath_ptr16
}
}

key_type: represents the type of keys to be indexed. Information about the location of commonly used types of standard keys when searching assign the encoded value. If key_type is the encoded value of "0xFF", key_xpath_ptr is added as additional information.

key_xpath_ptr: refers to a relative path, included in the XPath fragment for node used as the key.

Although the encoded value for standard keys have not been set, it is obvious that the encoded value for standard types of keys have a structure similar to the structure of the encoding types of the fragments in table 3.

Because the definitions section of the key index (key_index) and sections comprise key (sub_key_index) is similar to that defined in the reference to the prior art for indexes, keys, and their detailed description is omitted.

4. Section the key index (key_index)

Table 5
SyntaxNo. of bits (replaceable)
key_index() {
key_index_identifier8
for (j=0; j<sub_index_count;

j++){
high_key_value16
sub_index_container16
sub_index_identifier8
}
}

5. Section sub-index key (sub_key_index)

Table 6
SyntaxNo. of bits (replaceable)
sub_key_index() {
sub_index_identifier8
for (j=0; j<reference_count; j++)

{
key_value16
target_container16
target_handle16
}
}

Next, with reference to Fig describes the structure of the metadata defined by the above syntax, where the metadata is presented in the form of segments of the index information.

Section 110 of the list of index keys (key_index_list)defined in the index structure, provides a list of all sent messages the x key. This list includes information about the key that identifies each key (that is, location information of the fragment (fragment_descriptor) and/or information about the location of the key (key_descriptor); information about the location of the fragment and the location information of the key can be selectively encoded, or the data can be encoded simultaneously depending on the embodiments of the present invention) and the identification information section 120 of the key index (key_index), described below. XPath fragment metadata is the path to the root node of the XML document with metadata TVA, that is an absolute path, by analogy with the standard index structure, and the XPath of the node, used as the key, i.e XPath key is the relative path of the key for the metadata. The combination of the XPath fragment metadata and XPath key represents the location information of the key to the entire XML document.

In the present invention the encoded value corresponding to the XPath for a fragment of metadata (i.e. information about the location of the group of fragments), and the encoded value corresponding to the XPath key (that is, information about the location of the key)are stored respectively in the segment 111 "fragment_descriptor and segment 112 "key_descriptor".

As described above, if the location information of the fragment, costal is the one part of the key information, is a type of standard fragment, which is often used, is a coded value (fragment_descriptor)expressing XPath for a fragment of metadata (fragment_xpath_ptr) with predetermined codes. Examples of commonly used types of standard fragments are information about programs (ProgramInformation), information about group programs (GroupInformation), information on loans (CreditsInformation), program review (ProgramReview), segment information (SegmentInformation), the event is broadcast (BroadcastEvent), service information (ServiceInformation), etc. If the XPath fragment metadata for these types of fragments can be simply expressed in the form of coded values, it is possible to reduce the consumption of resources for searching metadata.

Thus, in the index structure according to the present invention XPath standard piece of metadata is encoded in a predetermined coded value, after which it is stored. In addition, these fragments are not assigned all coded values, and some of the coded values (e.g., "0XFF") assigns the fragments of the metadata defined by the user, to thereby allow the user to optionally specify the location information of the fragment metadata via XPath. In this regard, the additional area ("fragment_xpath_ptr"), which, for example, can be the is defined for a fragment of XPath metadata.

In the embodiment, where fragments of code in accordance with table 3, the location information of the fragment of the metadata included in the key information that has such coded values, as h", "h" and "h". Information about the location of the fragment data, encoded in "h", specifies the XPath to "pieces of information about programs (ProgramInformation)". In addition, if the location information of the fragment metadata is a "0FF", it means that the fragment metadata defined by the user, and therefore provides an additional area to identify the XPath fragment metadata.

Although the above-mentioned variant has been described with reference only to the fragment metadata, it can be used in relation to the key (or keys) for a fragment of metadata. That is, the encoded value can be set and used as frequently used keys instead of the standard XPath path for keys. In addition, if the encoded value is a predetermined value, the user can optionally specify the XPath for the key. The encoding of XPath for the above piece of data and the encoding of XPath for the key can be used simultaneously or independently.

In addition, section 110 of the list of index keys (key_index_list) contains identificatio the information section 120 of the key index (key_index) for each key, which is described below (i.e. information container ID (container_id)relating to the container, where the partition is stored 120 key index (key_index), and information with the ID of the index key). The information container ID information and the ID of the index key are stored, respectively, in the segment "index_container" and the segment "key_index_identifier" in section 110 of the list of index keys (key_index_list).

Because section 120 of the key index (key_index) and section 130 comprise key (sub_key_index) are similar to the corresponding sections described in reference to prior art for indexes, keys, and their description is omitted.

Next, with reference to Fig.9, which shows the index information, describes in detail the index structure, which includes the encoded key information according to a variant implementation of the present invention.

Figure 9 shows the section 110 list of indexes of the keys, in which the XPath fragment "BroadcastEvent" to identifier (ID) of the service coded in the "h". Here section 120 of the key index (key_index) and section 130 comprise key (sub_key_index) are similar to the corresponding sections described with reference to Fig.7.

The above index structure is very effective when using keys pertaining to frequently used types of fragments, for example ProgramInformation, GrpoupInformation, BroadcastEvent etc. in CEG the reduced overall consumption of resources in the device to search for metadata.

Figure 10 shows the method of providing the metadata index, having a structure according to one of the above-described variant of implementation of the present invention.

Indexes metadata according to one variant of implementation of the present invention can be created by the provider 200, providing, for example, audio/visual signals.

Information about the content, metadata, is first processed in chunks, as described above (S100). At step S200 is encoded by at least part of the information about the location of the fragment and the location information of the key information in the fields that will be included in the index metadata, i.e. information about the key (for example, location information of the fragment or information about the location of the key). In other words, if the location information of the fragment metadata, which owns the fields that form the key or information about the location of the key is of type standard fragment or standard type of key, and the other information can be encoded, the information about the location of the fragment metadata or information about the location of the key, i.e. the XPath fragment metadata or XPath key is encoded in a predetermined code value (for example, the fragment "event broadcast (BroadcastEvent)" encode "h") figure 9. If the information is about the location of the fragment metadata or information about the location of the key is not identified with the help of coded values, the key information expressed by XPath is defined, as is done in prior art.

The key is provided through the use of information, forming fragments, for example, information about "service ID" (Service ID) (S300). Then is section 130 comprise key (sub_key_index) for key provided above (S400). Section 130 comprise key (sub_key_index) includes segments 114, containing the ranges of key values, identification information of the fragments of the metadata corresponding to the key values (i.e. information container ID (container_id) and identifier information of the data fragment (handle_value), stored, respectively, in the segment "target_container" and the segment "target_container" Fig).

Section 120 of the key index (key_index)containing representative key values representing the respective ranges of key values, is provided at step S500. For example, enter the representative key value (e.g., 509), indicating pre-specified range (for example, 500-509) ID services. Section 120 of the key index (key_index) includes identification information for the partition 130 comprise key (sub_key_index), and identification information contains information container ID (container_id)relating to the container in which the partition is stored comprise key (sub_key_index), and Jn is ormatio ID sub-index key, as shown in Fig.

Section 110 of the list of index keys (key_index_list), organizing key information obtained above, that is, the location information of the fragment and the location information of the key is provided on the basis of the key at step S600. At the same time, if the encoded location information of the fragment or encoded information about the location of the key in step S200 exists, the above-mentioned position information are encoded in the code, when provided by section 110 of the list of index keys (key_index_list). In other words, for example, the fragment "event broadcast (BroadcastEvent)" figure 9 presents as "H". If the location information of the fragment and the location information of the key cannot be distinguished using coded values, you can use the key information expressed in XPath, as is done in prior art.

Section 110 of the list of index keys (key_index_list) in addition to the key information further comprises identification information section 120 of the key index (key_index).

The above stages in other embodiments, the implementation can be performed in reverse order, and the step S500, the provision of section 120 of the key index (key_index), which includes a representative value of the key, depending on the variant (variants) OS the implement of the present invention may be omitted.

Below with reference to 11 describes how search metadata that match the search conditions by using the metadata index, having a structure according to one of the above-described variant of implementation of the present invention.

The search condition is entered, for example, by the user at step S1100, and at step S1210 is determined location information metadata related to the field of the search terms entered. The search key corresponding to the location information, is performed in section 110 of the list of index keys (key_index_list) (step S1300), and at least part of the location information, for example, location information of the fragment, which includes the key or information about the location of the key in this section is defined using a predetermined code, and the appropriate metadata is retrieved by using the found key (S1400).

Step S1400 extract relevant metadata contains a representative search key values satisfy the search condition, by comparison with representative key value and range of values for key search terms in section 120 of the key index (key_index) and the search section 130 comprise key (sub_key_index) segment 114 that includes a key value in the range represented by the found representative key value (S1410), the search key value, satisfying the search condition in the segment 114 section 130 comprise key (sub_key_index), searched (S1420), and extracting the relevant metadata by using identification information of the metadata corresponding to the key value (S1430), resulting extract metadata that satisfy the search condition. For example in figure 2, and 9, enter the search condition corresponding to the key service ID Service Id in the range 507-514, searches representative key values 509 and 519, and the fragments corresponding to the search condition is extracted by using the identification information of the fragments corresponding to key values.

Information about the location of the fragment refers to the absolute path of the fragment metadata keys must be indexed, as described above, that is, the XPath fragment metadata (fragment_xpath_ptr), and information about the location of the key refers to the relative path of the key for a fragment of metadata (path relative to the location of the XPath fragment), i.e. XPath (key_descriptor) nodes that are used as keys.

On the steps S1410, S1420 and S1430 searches the corresponding section 120 of the key index (key_index) and section 130 comprise key (sub_key_index) and retrieve the corresponding slice through the use of identification, the availability of information section 120 of the key index (key_index), section sub-index key (sub_key_index) and metadata, respectively.

On Fig shows a device for searching metadata according to one variant of implementation of the present invention. The device implements the method of the search metadata corresponding to the present invention and described with reference to 11.

The device contains the 1100 block of input, allowing the user to enter a search condition receiving unit 1200, the host content, metadata about the content or the metadata index, 1300 block of data storage that retains the received content, the metadata of contents or index metadata block 1400 control determining information about the location of the metadata corresponding field search conditions entered from the 1100 block of input, performing a search key that contains the code that is set in advance as the location information, at least part of the location information is defined as a predetermined code, and extract the appropriate metadata by using found key, as well as the 1500 block of output that outputs the result of the search executed by the 1400 block of management.

Block 1400 control compares the input data defining the search condition and coming from the 1100 block of input, with the key value contained in the index metadata, which is stored in the loc 1300 data storage.

The number of stages of the search metadata according to one variant of implementation of the present invention the step of determining the location information field the search terms entered in the metadata (S1210), the stage of the search key that contains the code that is set in advance as information about the location, where at least part of the location information is defined as a predetermined code (S1300), and the step of extracting the relevant metadata by using the found key (S1400) are performed in the 1400 block of management. These steps are described with reference to 11.

In the present invention proposes an index structure, which provides a simple indexing of the fragments of the metadata for a quick search of the fragments of the metadata when the metadata is structured on the basis of fragments, and the method for searching the index information, and a device for searching the index information.

Industrial applicability

According to the present invention is implemented quick search metadata while reducing the cost of resources for the device to search for metadata, which reduces the search time and increases the efficiency of the device to search for metadata. However, it should be understood that although the illustrative non-limiting embodiments of the present invention allow izbavites is from the above disadvantages and other disadvantages, which have not been described, the present invention is not necessarily to overcome the above disadvantages, and illustrative non-limiting embodiments of the present invention may not allow any of the above problems. You should also understand that the system that uses the present invention also includes a non-volatile or a removable storage device such as magnetic and optical disks, ROM, RAM, or a transmission medium with a carrier, where the steps of the method and data structure of the present invention can store and distribute. You can also extend, for example, by downloading from a network such as the Internet.

Although the present invention has been described in connection with the preferred embodiment illustrated in the drawings, this description is for illustrative purpose only. Specialists in the art it is obvious that can be offered to various modifications and equivalents within the scope and essence of the invention. Thus, the scope of the present invention should be defined only by the attached claims.

1. The way the search is divided into fragments of metadata using an index that contains a list of keys corresponding to fields of the metadata, and location information the La definition keys the method contains the steps that define the location information corresponding to the search condition in relation to the metadata at least part of the location information is expressed as a value of a preset code, search, index-based metadata, key corresponding to the aforementioned predetermined value code, and retrieve metadata by using the found key.

2. The method according to claim 1, wherein the fragment contains the stages on which the search key values satisfy the search condition, among the key values from the index, and retrieve a fragment of the metadata using the identification information of the fragment corresponding to the key value.

3. The method according to claim 2, in which in response to the set of key values that satisfy a search condition, the fragment contains the stage at which retrieve the fragments of the metadata that match the key values that satisfy the search condition.

4. The method according to claim 2, in which the search value comprises the steps on which search representative key values satisfy the search condition, among the representative values of the index key corresponding to the key ranges, and search for a value in di is the range of values corresponding to the representative key value.

5. The method according to claim 1, in which the index section contains the list of indexes of the keys contains the list section of the sub-index of the key that contains the ranges of values of the key and identification information of those fragments of metadata that match the above key values, and the index partition key that contains a representative key values representing the respective ranges of key values.

6. The method according to claim 1, wherein the location information includes location information of the fragment metadata that includes the key, and the location information of the key in this fragment.

7. The way the search is divided into fragments of metadata, including the stages at which the access list that contains many combinations of location information of the fragment and the location information defining at least one key in this fragment, with one of the location information of the fragment and the location information defining at least one key, expressed as a predetermined code, search this list of combinations corresponding to the search condition of at least one key metadata, determine identification information metadata, identified found in combination on the basis of a predetermined code, corresponding to this combination, and extract one or more fragments of the metadata corresponding to the aforementioned identification information.

8. The method according to claim 7, in which the remaining information about the location can be expressed in the form of another predetermined code or Xpath.

9. The finder is divided into fragments of metadata using an index that contains a list of keys corresponding to fields of the metadata, and location information defining the keys, including the block I made with the possibility of receiving a search condition containing metadata field as a search parameter, and a control unit configured to determine location information corresponding to the search condition, at least part of the location information is expressed as a value of a preset code search based on the metadata index key corresponding to said predetermined value code, and retrieve metadata by use the found key.

10. The device according to claim 9, in which the location information includes location information of the fragment metadata that includes the key, and the location information of the key in this fragment.

11. The device according to claim 10, in which one of the information about the location of the fra is ment and information about the location of the key is expressed as a predetermined code.

12. The device according to claim 11, in which the remainder of the information about the location of the fragment and information about the location of the key is expressed as the value of another predetermined code or Xpath.

13. The device according to claim 11, in which the value of the predetermined code includes Xpath as additional information, while the corresponding segment/key matches the type specified by the user.

14. The device according to claim 9, in which the control unit is configured to search for key values that satisfy the search condition, among the key values from the index, and retrieve identification information of the metadata corresponding to the key value.

15. The device according to 14, in which in response to the set of key values that satisfy a search condition, the control unit is arranged to extract the fragments of the metadata that match the key values that satisfy the search condition.

16. The device according to 14, in which the control unit is configured to search for a representative key values satisfy the search condition, among a representative of the index key values corresponding to the ranges of key values, and the search for values in the range of values corresponding to the representative key value.

17. The device p is 9, optionally containing a receiving unit, configured to receive metadata block data storage configured to store the received metadata, and output unit, configured to output results of the search conducted by the control unit.

18. The device according to claim 9, in which the metadata on the metadata defined by the organization TV-Anytime Forum.

19. The device according to claim 9, in which the index section contains the list of indexes of the keys contains the list section of the sub-index of the key that contains the ranges of values of the key and identification information of those fragments of metadata that match the above key values, and the index partition key that contains a representative key values representing the respective ranges of key values.

20. The finder is divided into fragments of metadata that contains the block I made with the possibility of receiving search criteria in at least one key metadata, and the control unit is configured to select from a list containing many combinations of location information of the fragment and the location information defining at least one key in this fragment, the combination which matches the search condition, where one of location information of the fragment and in the information about the location, defining at least one key, expressed as a predetermined code, determining identification information metadata, identified found in combination on the basis of a predetermined code corresponding to this combination, and retrieve one or more fragments of the metadata corresponding to the aforementioned identification information.

21. The device according to claim 20, in which the remaining location information expressed in the form of another predetermined code or Xpath.



 

Same patents:

FIELD: index structure of meta-data, provided for finding information about content.

SUBSTANCE: in accordance to first variant of method, a list of keys is provided, appropriate for fields of meta-data, and information about position for determining key; in accordance to second variant, section of key index list is provided, section of key index and section of key sub-index. In accordance to third variant, a list of keys and values of keys is provided, and in accordance to fourth variant, values of keys and identification information of meta-data is provided as well as list of keys.

EFFECT: provision of simplified indexation of data fragments, realization of fast search and decreased search time.

4 cl, 12 dwg, 6 tbl

FIELD: computer engineering, possible use in devices for controlling informational streams to monitor informational traffic.

SUBSTANCE: method includes preliminarily forming a base of standard informational signs, receiving informational stream, serially selecting and recording fragments of informational stream, selecting identification signs from these, comparing them to standard ones. Base of standard informational signs is formed by computing morphological coefficient d of identification sign and its address A with utilization of hash-function. For identification signs received from informational stream, morphological coefficients d and identification addresses A are additionally computed, after that on basis of computed address, identification sign selected from informational stream is compared to standard one.

EFFECT: increased information processing speed due to shorter time needed for identification of addresses of signs in base of standard informational signs.

4 cl, 2 dwg, 2 tbl

FIELD: computer engineering, in particular, informational-reference system of industrial-economical characteristics of airlifts.

SUBSTANCE: system contains two registers, data commutation block, block for selecting automated workplace of user, block for identification of type of data being requested, block for selection of viewing direction of reference data, block for commutation of synchronization signals, reverse counter, block for receiving database update files, block for identification of type of data being updated, two blocks for comparing codes.

EFFECT: increased speed of system operation due to no need for searching information across whole volume of server database.

10 dwg, 1 app

FIELD: computer science, in particular, engineering of automatic system for controlling routing of text documents in data processing network.

SUBSTANCE: system contains first, second, third, fourth, fifth and sixth registers, first and second blocks for identification of text documents, block for integration of control signals, two counters, adder, block for forming base address for recording finished documents and commutator.

EFFECT: increased speed of system operation by localizing range of data search addresses in server database by means of identifiers of text documents.

6 dwg

FIELD: computer engineering, possible use as device for structural-statistical analysis of information arrays.

SUBSTANCE: device contains generator of signals of current estimate, discriminator of zones of estimate values, distributor of impulses, counter of temporal intervals, commutator, first and second generators of search variable, first and second adding counters, first and second memory blocks, division block, classification device, register of search strategy, signals generator, timer of current day, block for generation of cutting threshold, structural analyzer and third memory block.

EFFECT: possible recognition of target determined combinations, representing n-digit binary numbers.

2 cl, 2 dwg

FIELD: engineering of automated libraries for data storage with loading, unloading and movement of data carriers.

SUBSTANCE: library contains robotized transporting device, for moving data carriers, and multiple universal sockets with means for connecting accumulators positioned in sockets or other devices to transporting device, to which commands from main computer are sent for moving data carriers. Robotized device is programmed for recognition, whether each socket is free or occupied with a certain component, such as an accumulator or command port, and following realization of appropriate communication with component occupying the socket.

EFFECT: decreased hardware costs with adjustable configuration and use of different system components.

6 cl, 5 dwg

FIELD: computer science, in particular, automated identification of data of voting sheets of voters in national automatic system "Elections".

SUBSTANCE: system contains block for receiving data from voting sheets, block for receiving records of server database, block for setting type of signatures, block for selecting supporting addresses of server database, counter of signatures number, comparators, blocks for selecting supporting addresses of signature types, blocks for modification of addresses for recording and reading signatures, block for selecting types of signatures, block for selecting number of checked signatures of voters and block for forming signals for recording and reading signatures of voters.

EFFECT: increased speed of operations due to localization of addresses of documentary data of civilians in database of system by identifiers of their surname, name and patronymic.

12 dwg

FIELD: radio engineering, possible use as mobile communication system for realizing contact with a celebrity in form of a game.

SUBSTANCE: system contains at least two receiving-transmitting personal devices, local control device, and central control device. At least one additional transmitting-receiving device of a celebrity is provided. Receiving-transmitting personal devices are made in form of mobile communication terminals of users, local control device - in form of station of mobile cell phone communications operator, and central control device - in form of a server.

EFFECT: increased efficiency, realized game effect during making of contacts.

6 cl, 3 dwg, 2 tbl

FIELD: computer science, in particular, engineering of internet-banking system for information-marketing electronic trading center.

SUBSTANCE: system contains user identification block, block for identification of user requests, block for selecting bearing addresses of information-marketing center database, block for selection of user workplace addresses, register, block for selection of transaction addresses, block for selecting addresses of payments, block for forming signals for recording and reading for database, data dispensing block, block for identification of transactions, block for receiving dialogue messages, block for providing notifications to suppliers, block for providing notifications to buyers.

EFFECT: increased reliability of financial payments by excluding possible receipt of payment by goods supplier before warehouse of buyer receives goods.

13 dwg

FIELD: computer science, in particular, engineering of system for controlling selection and processing of governmental population register data.

SUBSTANCE: system contains registers, address selectors, adders, counters, data receipt block, block for generating temporal strobes, comparator, decoder, block for predicting quantities, data dispensing block, OR element and delay elements.

EFFECT: increased speed of operation of system due to localization of search only by supporting addresses of database of Russian Federation subjects.

10 dwg, 2 tbl

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!