GB2378275A - Distributed metadata processing system - Google Patents
Distributed metadata processing system Download PDFInfo
- Publication number
- GB2378275A GB2378275A GB0118603A GB0118603A GB2378275A GB 2378275 A GB2378275 A GB 2378275A GB 0118603 A GB0118603 A GB 0118603A GB 0118603 A GB0118603 A GB 0118603A GB 2378275 A GB2378275 A GB 2378275A
- Authority
- GB
- United Kingdom
- Prior art keywords
- data
- store
- tag
- item
- acquisition unit
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
- G06F16/38—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
Abstract
Metadata generation for individual data items is performed at data acquisition units 2 prior to transmission to a central data store 4. A decision unit 18 may be provided to evaluate whether to generate the metadata at the data acquisition unit 2 or to transmit the raw data item to the data store 4 for metadata generation at the data storage unit 4. Multiple levels of data storage units and data acquisition units may be provided.
Description
DISTRIBUTED 1\IETADATA PROCESSING SYSTEM
The present invention relates to a data processing system in which data tags are generated for data items at a data item acquisition unit prior to transmission to a data storage unit.
It is well known to provide data bases for the storage of individual data items. The data items may, for example, be individual photographs or other images, text documents, items of music or other audio information, personnel records, or any other such data items. The purpose of such data bases is to provide both storage for the data items and also to provide the facility to search through the stored data items in accordance with one or more criteria.
To allow such searching to be executed, the individual data items are indexed in some manner. Early systems of indexing were relatively simple and included such schemes as grouping a number of data items together within a single category, such that when a search was performed for items within that category the relevant data items could be retrieved.
However, in time, more advanced indexing schemes have been developed, with one such scheme involving the use of metadata. Metadata describes data, that is, it is data about data. The metadata associated with a data item may be as simple as a set of natural language comments referring to one or more elements of the data item. Alternatively, the metadata may equally be much more complex comments, or tags, that may refer to the structure of the data. For example, the metadata associated with a text document may include a reference to the subject matter of the document, its author, the number of words, the size of the data item etc. As a further example, metadata associated with a graphical image such as a photograph may include tags identifying different elements of the image i. e. that the image is a sunrise/sunset, it includes peoples faces, it is a landscape, and so on.
The metadata that is generated for each data item stored within a database is ordinarily much more compact thank the raw data itself. An analogy would be the use of classification cards in a public library. Each card represents a book stored in the library and contains certain items of information about the book, for example author and title. The cards themselves occupy a relevantly small amount of space compared to the space occupied by
the complete library and by searching the cards a set of books, for example by the same author, can be identified.
However, the metadata may in some circumstances be much more sizeable than the original data item. Maintaining the library analogy, a single novel, such as 'Pride and Prejudice', may have a number of books analysing it associated with it. These volumes of analysis are analogous to the metadata to the original novel, yet would take up more shelf space than the novel itself.
Powerful search tools that exploit metadata are used to augment conventional search tools.
The increased functionality of databases and their associated search engines is one of the factors in their increased usage. Another factor is the increased usage of networked systems with local or remote network stations being linked to a central database. The link may be provided by a dedicated transmission cable or a shared transmission cable or wireless connection, or other such connection means. The quality and/or speed of the connection may pose a serious restriction on the amount of data that can be transmitted between the central database and the remote stations. It is therefore a problem to provide a large database with powerful search facilities, especially when dealing with non-textual data, that is easily and quickly accessible from remote stations. It may be equally problematic for data items to be exchanged between the database and the remote stations.
A further problem is the cost in processing terms required to generate the metadata. A large centralised database may require a prohibitive amount of processing power to deal with the generation of increasing amounts of metadata. Equally, local computers, such as domestic PC's, or portable devices such as personal digital assistants or cameras may not ordinarily have the processing power available to perform the metadata generation under all circumstances or in acceptable time frames.
At least some of the above problems apply to locally held databases. The consideration then is whether to perform the metadata generation locally or request an additional remote
facility to do it even though there is no requirement or intention to transmit either the generated metadata or data item to a centralised database.
According to the present invention there is provided a data processing system comprising at least one data item acquisition unit and at least one data store, the data item acquisition unit including a data tag generator for generating a data tag associated with each data item, and the data item acquisition unit being arranged to transmit at least the data tag to the data store. Preferably the data item acquisition unit can also transmit the data item itself to the at least one data store.
Additionally, the at least one data store also includes a data tag generator.
Each data store may be connected to one or more other data stores so as to provide a hierarchical arrangement of data stores.
Preferably the data item acquisition units include a decision module that evaluates if the data tag should be generated at the data acquisition unit or if the data item should be sent to the data store and the data tag generated there. The evaluation may take into consideration the size and complexity of the data item and hence the processing power required to generate the data tag, and may also include an evaluation of the efficiency of transmitting the data item to the data store for data processing based on the size of the data item and the quality and/or speed of the connection between data acquisition unit and data store. The evaluation may also take into consideration any previously stipulated privacy requirements.
A use of the metadata is to preserve the privacy of the original data item. If the data item includes elements that it is desired to keep secret, only the metadata associated with the remaining elements need be transmitted to the data store. In a similar manner, a search query may be transmitted to the data store with only the metadata essential for the search without transmitting the original data item itself.
The data tag generator at the data acquisition unit is preferably arranged to detect a failure to generate a data tag for a data item. A failure to generate the metadata may occur due to one or more of a number of reasons. It is normal practice not to limit the amount of system memory required during metadata generation. There is therefore the possibility for a failure to occur due to the data acquisition unit running out of memory. Equally, the processing power required to generate the metadata may be greater than that available at the data acquisition unit at that time. A further cause of failure may be that the data acquisition unit is not appropriately configured with the relevant contextual data for the data item being presented.
The failure may be a 'hard' failure, in which case no metadata is generated and the data acquisition unit may transmit the data item to the data store, the data tag (metadata) generation then occurring at the data store. Alternatively, appropriate configuration information held by the data tag generator at the data stores may be transmitted to the data acquisition unit to allow successful data tag generation to occur at the data acquisition unit.
The failure may alternatively be a 'soft' failure, in which case the metadata generated prior to the failure occurring may be transmitted to the data store, or equally simplified metadata may be generated instead and transmitted to the data store.
Alternatively or additionally, the data acquisition unit may be arranged such that new data tag configuration information may be defined in relation to a presented data item and the new data tag configuration information transmitted to the data store for inclusion in the data tag generator located therein.
According to a second aspect of the present invention there is provided a method of processing data comprising generating a data tag associated with a data item, said data tag generation occurring at a data acquisition unit, and transmitting at least said data tag to a data store.
Advantageously the data item may also be transmitted to the data store. Data tag generation may also occur at the data store.
Preferably the method includes evaluating if it is appropriate to generate the data tags at the or each acquisition unit or to transmit the data item to a data store for data tag generation to occur there. Preferably the evaluation procedure includes determining the size and complexity of the data item to be processed, providing an estimate of the processing power required to generate the associated data tag in response to the determination, comparing the estimated processing power with the processing power of the available data tag generator, and in response to the comparison either generating the data tag locally or transmitting the data item to a data store.
Preferably the method further comprises transmitting configuration information from a data store to a data acquisition device and configuring a data tag generator located at the data acquisition device in accordance with the configuration information.
Additionally or alternatively, data tag generator configuration information may be transmitted from a data item acquisition device to a data store, said configuration information being defined in relation to a user presented data item.
According to a third aspect of the present invention there is provided a data item acquisition device comprising a data tag generator and being arranged to transmit a generated data tag associated with an acquired data item to a data store.
Preferably the data item acquisition device further comprises an evaluation module that is arranged to determine the processing power required to generate a data tag for a data item, compare the required processing power to the processing power available at the data tag generator, and in response to the comparison either enable the data tag generator to generate the data tag or enable the transmission of the data item to a data store.
Preferably the data item acquisition device forms an integral part of a personal computer.
Additionally one or more data capture devices, for example an electronic camera, scanner or microphone, may be connected to an input of the data acquisition device. Alternatively the data acquisition unit may be integrated within a data capture or data storage device.
According to a fourth aspect of the present invention there is provided a data store arranged to store a plurality of data tags associated with respective data items, and arranged to export, upon request, a data tag generator configuration information for use by data tag generators. Preferably the data store is arranged to store the respective data items associated with the data tags. The data store may additionally comprise a data tag generator for generating data tags associated with data items input to the store.
Additionally the data store comprises a search engine arranged to locate data tags conforming to a user search request and cause the data items associated with the located data tags to be output from the data store.
Preferably the data store is connected to one or more other data stores. Additionally the data store further comprises an evaluation module that is arranged to determine the processing power required to generate a data tag for a data item, compare the required processing power to the processing power available at the data tag generator, and in response to the comparison either enable the data tag generator to generate the data tag or enable the transmission of the data item to a data store.
According to a fifth aspect of the present invention, there is provided a computer program product for causing a data processor to execute the method according to the second aspect of the present invention.
The present invention will now be described, by way of example, with reference to the accompanying drawings, in which: Figure 1 shows a schematic representation of a data processing according to embodiment of the present invention connected to a number of data input devices: and Figure 2 shows further embodiment of the present invention having a multilayer structure.
Figure 1 shows a data acquisition unit 2 connected to a data store 4. The data acquisition unit 2 is connected to one or more data input devices. Examples of data input devices that are shown are a discrete data storage unit 6, for example a hard disk, a digital camera 8, and a document scanner 10. Other input devices such as video or sound recorders could also be provided. Located in the data acquisition unit 2 is a datatag, or metadata generator 12. The metadata generator is arranged to process data items input from one or more of the data input devices to generate datatags, or metadata for each data item. A data store 4 is connected to the data acquisition unit 2. The data store unit includes one or more data storage devices 14, such as known hard disk drives. Connected to the hard disk drives 14 is a data query and/or indexing unit that is arranged to perform conventional data searching procedures. The hard disk drives 14 are arranged to store either a plurality of data tags, a plurality of individual data items, or both data items and their associated datatags. The data acquisition unit 2 and data store 4 are connected by any suitable data transmission channel, for example by fibre optic cable, or by wireless connections.
In use, a data item will be input to the data acquisition unit 2 from one of the data input devices 6-10. On receipt of a data item the metadata generator 12 will perform known processing techniques to generate metadata associated with the input data items. The metadata may then be transmitted from the data acquisition unit 2 to the data store 4, together with, for example, a request from the data acquisition unit for the data store 4 to provide further data items that have similar metadata associated with them. This method of operation has the advantage that metadata generation is performed locally at the data acquisition unit 2 and not at the data store 4, thus freeing resources at the data store 4 that may be applied more efficiently to searching the contents of the data store 4 for requested data items. Additionally, having generated the associated metadata at the data acquisition unit 2, both the metadata and the associated data item may be transmitted to the data store 4 to be added to the data items and metadata stored there. In this way a database that is stored at the data store 4 may be expanded and updated relying solely on metadata and data items provided by remote stations without utilising the central resources at the central data store.
In a further embodiment of the present invention the data acquisition unit 2 may include a decision unit 18 connected to the metadata generator 12. The function of the decision unit 18 is to perform an evaluation of whether generation of the metadata for an input data item would be better performed either locally at the data acquisition unit 2 or centrally at the store 4. In these embodiments, the data storage unit 4 also includes a mete data generator 20. The evaluation of where to perform the metadata processing may take into account a number of parameters, for example the size and complexity of the data item and therefore the processing power required to perform the metadata processing, or the size of the data item in comparison with the transmission abilities of the connection betvveen the data acquisition unit 2 and the data store 4. The evaluation may also take into consideration any stipulated privacy requirements. For example, it may be stipulated by a user that the author or originator of a data item is not included in the metadata. This will have an impact on the complexity of the generated metadata. As a further example, if the connection between the data acquisition unit 2 and the data store 4 is of limited capacity, the decision unit 18 may evaluate that it is more efficient to generate the metadata locally at the data acquisition unit 2 using the metadata generator 12 rather than attempt to transmit the relatively large data item down the restricted transmission capacity of the connection between the data acquisition unit 2 and the central store 4. Alternatively, an evaluation may be made that it is more efficient to transmit the data item unprocessed to the data store 4 to be processed by the more powerful data generator processor 20 located at the data store 4.
In certain embodiments of the present invention the metadata generator l 2 located at the data acquisition unit 2 is arranged to report any failures to generate metadata for a data item. A failure to generate metadata for a data item may occur due to the metadata generator 12 located at the data acquisition unit 2 not being configured to with appropriate contextual data generate metadata for a particular kind of data item. Alternative or additional causes of failure may include running out of memory during generation of the metadata or insufficient processing resources being available. The available processing resources may vary depending on other tasks being performed by the data acquisition unit at any given time. When such a failure occurs, the decision unit 18 may either transmit the particular data item to the data store 4 in order for the metadata generator 20 located at the data store 4 to generate the metadata, request revised configuration information from the
metadata generator 20 located at the data store 4 to enable the metadata generator unit 12 located at the data acquisition unit 2 to be reconfigured to enable metadata to be generated for the data item at the data acquisition unit 2, generate simplified metadata that requires less system resources or configuration information, or simply transmit to the data store 4 the metadata that had been successfully generated prior to the failure occurring.
It will be appreciated by those skilled in the art that the data acquisition unit 2 may be a dedicated processing unit or may be integrated as either hardware or software within a general personal computer. In the latter case, the decision unit 18 may also take into account the demands on the computer processor when evaluating whether to generate metadata at the data acquisition unit or not. It will be appreciated that metadata processing may be performed at the data acquisition unit 2 during "idle" processing periods.
Figure 2 shows an embodiment of the present invention utilising a multilayered, hierarchical arrangement of data storage units. A number of "first layer" data stores 4 are provided. Each data storage unit includes a metadata generator 20. Connected to each first layer data store 4 are one or more data acquisition units 2. In Figure 2 the data acquisition units 2 are schematically shown as being connected to different data input sources. The sources shown include a digital camera 30, a document source 32, audio source 34 and video source 36. Each data acquisition unit 2 also includes a metadata processor 12. The data acquisition units 2 are arranged to operate in the same manner as those described in Figure 1.
Each of the first layer data stores 4 is connected to a second layer data store 3 8. Preferably, but not necessarily, the second layer data store 38 has increased storage capacity in comparison to the first layer data stores 4. Although only two layers of data stores are shown in Figure 2, it will be appreciated that any number of layers can be used. In use, the decision making process that occurs at the data acquisition units 2, as described with reference to Figure 1, also takes place at each of the levels of data stores. Thus the system is flexible enough to perform the metadata processing at whichever layer is deemed most appropriate.
In further embodiments, the data input sources, for example the digital camera 30 shown in Figure 2, may themselves include a metadata generator. This allows a further sub-layer of metadata processing and decision making to be performed.
By providing metadata processing units at the various different layers of the system the processing is distributed throughout the system. This provides the advantage that both processing power throughout the system and the use of transmission connections can be optimised. The processing power of the metadata generators at the different layers may either be identical, or may increase towards the highest layer. In the latter case, only the more complex or large data items would need to be processed by the more powerful metadata generators, with the simpler data items being processed at lower levels by individual metadata generators.
In the same manner as described with relation to Figure 1, the lower level metadata generators may be "updated" with new configuration information provided by metadata generators in the higher levels.
Claims (36)
1. A data processing system comprising at least one data item acquisition unit and at least one data store, the data item acquisition unit including a data tag generator for generating a data tag associated with each data item, and the data item acquisition unit being arranged to transmit at least the data tag to the data store.
2. A data processing system according to claim 1, wherein said data item acquisition unit is further arranged to transmit the data item to the at least one data store.
3. A data processing system according to claim 2, wherein the at least one data store includes a further data tag generator.
4. A data processing system according to claim 3, wherein said data item acquisition unit includes a decision module arranged to evaluate if the data tag should be generated at the data acquisition unit or if the data item should be sent to the data store and the data tag generated there.
5. A data processing system according to claim 4, wherein said decision module is arranged to utilise data item size and complexity information to generate an estimate of the processing power required to generate an associated data tag and determine if said estimated processing power exceeds the processing power available.
6. A data processing system according to claim 5, wherein said processing power available at said data item acquisition unit is variable.
7. A data processing system according to claim 5 or 6, wherein said decision module is further arranged to evaluate the efficiency of transmitting the data item to the data store for data processing based on the size of the data item and the quality and/or speed of the connection between the data acquisition unit and data store.
8. A data processing system according to any one of claims 5 to 7, wherein said decision module is further arranged to include one or more restrictions on data to be
included in said data tag in said evaluation.
9. A data processing system according to any preceding claim, wherein said data tag generator is arranged to detect a failure to generate a data tag for a data item.
10. A data processing system according to claim 9, wherein in response to said failure the data item is transmitted to the data store with a request for the data tag to be generated therein.
11. A data processing system according to claim 9, wherein in response to said failure any portion of said data tag generated prior to said failure is transmitted to said data store.
12. A data processing system according to claim 9, wherein in response to said failure said data tag generator attempts to generate a simplified data tag.
13. A data processing system according to clarion 9 or 12, wherein further configuration information held by the data tag generator at the data store is transmitted to the data acquisition unit to allow successful data tag generation to occur.
14. A data processing system according to any preceding claim, wherein said data tag generator is arranged such that data tag configuration information may be defined in relation to a presented data item and the data tag configuration information transmitted to the data store for inclusion in the data tag generator located therein.
15. A data processing system according to any preceding claim, wherein said data store is connected to one or more other data stores so as to provide a hierarchical arrangement of data stores.
16. A method of processing data comprising generating a data tag associated with a data item at a data acquisition unit and transmitting at least said data tag to a data store.
17. A method of processing data according to claim 16, wherein the data item is also transmitted to the data store.
18. A method of processing data according to claim 17, wherein said data tag generation can also occur at the data store.
19. A method of processing data according to claim 18, wherein said method includes evaluating if it is appropriate to generate the data tags at the or each acquisition unit or to transmit the data item to a data store for data tag generation to occur there.
20. A method of processing data according to claim 19, wherein the evaluation procedure includes determining the size and complexity of the data item to be processed, providing an estimate of the processing power required to generate the associated data tag in response to the determination, comparing the estimated processing power with the processing power of the available data tag generator, and in response to the comparison either generating the data tag locally or transmitting the data item to a data store.
21. A method of processing data according to claim 19 or 20, wherein said evaluation procedures includes evaluating the efficiency of transmitting the data item to the data store for data processing based on the size of the data item and the quality and/or speed of the connection between the data acquisition unit and data store.
22. A method of processing data according to any one of claims 16 to 21, wherein the method further comprises transmitting configuration information from a data store to a data acquisition device and configuring a data tag generator located at the data acquisition device in accordance with the configuration information.
23. A method of processing data according to any one of claims 16 to 22, wherein data tag generation configuration information is transmitted from a data item acquisition device to a data store, said configuration information being defined in relation to a user presented data item.
24. A method of processing data according to arty one of claims 19 to 23, wherein said data store is connected to at least one further data store and said evaluation step is performed at at least one of said data stores.
25. A data item acquisition device comprising a data tag generator and arranged to transmit a generated data tag associated with an acquired data item to a data store.
26. A data item acquisition device according to claim 25 further comprising an evaluation module arranged to perform any one of the evaluation procedures of claims 19 to21.
27. A data item acquisition device according to claim 25 or 26, wherein said data item acquisition device forms an integral part of a personal computer.
28. A data item acquisition device according to any one of claims 25 to 27, wherein one or more data capture devices selected from a list comprising an electronic camera, scanner and microphone is connected to an input of the data acquisition device.
29. A data item acquisition device according to any one of claims 25 to 28, wherein the data acquisition unit is integrated within a data capture or data storage device.
30. A data store arranged to store a plurality of data tags associated with respective data items, and arranged to export, upon request, data tag generator configuration information for use by data tag generators.
31. A data store according to claim 30, wherein said data store is arranged to store the respective data items associated with the data tags.
32. A data store according to claim 30 or 31, wherein said data store comprises a data tag generator for generating data tags associated with data items input to the store.
33. A data store according to any on of claims 30 to 32, wherein said data store comprises a search engine arranged to locate data tags conforming to a user search request and cause the data items associated with the located data tags to be output from the data store.
34. A data store according to any one of claims 30 to 33, wherein said data store is connected to one or more other data stores.
35. A data store according to any one of claims 30 to 34, wherein said data store further comprises an evaluation module that is arranged to determine the processing power required to generate a data tag for a data item, compare the required processing power to the processing power available at the data tag generator, and in response to the comparison either enable the data tag generator to generate the data tag or enable the transmission of the data item to a data store.
36. A computer program product arranged to cause a data processor to execute the method according to any one of claims 16 to 24.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| GB0118603A GB2378275B (en) | 2001-07-31 | 2001-07-31 | Distributed metadata processing system |
| US10/208,606 US20030069898A1 (en) | 2001-07-31 | 2002-07-30 | Data processing system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| GB0118603A GB2378275B (en) | 2001-07-31 | 2001-07-31 | Distributed metadata processing system |
Publications (3)
| Publication Number | Publication Date |
|---|---|
| GB0118603D0 GB0118603D0 (en) | 2001-09-19 |
| GB2378275A true GB2378275A (en) | 2003-02-05 |
| GB2378275B GB2378275B (en) | 2005-06-22 |
Family
ID=9919502
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| GB0118603A Expired - Fee Related GB2378275B (en) | 2001-07-31 | 2001-07-31 | Distributed metadata processing system |
Country Status (2)
| Country | Link |
|---|---|
| US (1) | US20030069898A1 (en) |
| GB (1) | GB2378275B (en) |
Families Citing this family (51)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2406808A1 (en) * | 2002-07-05 | 2004-01-05 | Nid Solutions Inc. A Division Of 2004221 Ontario Limited | System and method for the capture, storage and manipulation of remote information |
| US20060174203A1 (en) * | 2005-01-31 | 2006-08-03 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Viewfinder for shared image device |
| US20060173972A1 (en) * | 2005-01-31 | 2006-08-03 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Audio sharing |
| US9082456B2 (en) | 2005-01-31 | 2015-07-14 | The Invention Science Fund I Llc | Shared image device designation |
| US20060187230A1 (en) * | 2005-01-31 | 2006-08-24 | Searete Llc | Peripheral shared image device sharing |
| US8606383B2 (en) | 2005-01-31 | 2013-12-10 | The Invention Science Fund I, Llc | Audio sharing |
| US9325781B2 (en) | 2005-01-31 | 2016-04-26 | Invention Science Fund I, Llc | Audio sharing |
| US7876357B2 (en) | 2005-01-31 | 2011-01-25 | The Invention Science Fund I, Llc | Estimating shared image device operational capabilities or resources |
| US20060285150A1 (en) * | 2005-01-31 | 2006-12-21 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Regional proximity for shared image device(s) |
| US8902320B2 (en) | 2005-01-31 | 2014-12-02 | The Invention Science Fund I, Llc | Shared image device synchronization or designation |
| US20060221197A1 (en) * | 2005-03-30 | 2006-10-05 | Jung Edward K | Image transformation estimator of an imaging device |
| US9124729B2 (en) | 2005-01-31 | 2015-09-01 | The Invention Science Fund I, Llc | Shared image device synchronization or designation |
| US9489717B2 (en) * | 2005-01-31 | 2016-11-08 | Invention Science Fund I, Llc | Shared image device |
| US20070236505A1 (en) * | 2005-01-31 | 2007-10-11 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Resampling of transformed shared image techniques |
| US9910341B2 (en) | 2005-01-31 | 2018-03-06 | The Invention Science Fund I, Llc | Shared image device designation |
| US20060187228A1 (en) * | 2005-01-31 | 2006-08-24 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Sharing including peripheral shared image device |
| US7920169B2 (en) | 2005-01-31 | 2011-04-05 | Invention Science Fund I, Llc | Proximity of shared image devices |
| US20060170956A1 (en) | 2005-01-31 | 2006-08-03 | Jung Edward K | Shared image devices |
| US7782365B2 (en) * | 2005-06-02 | 2010-08-24 | Searete Llc | Enhanced video/still image correlation |
| US9001215B2 (en) * | 2005-06-02 | 2015-04-07 | The Invention Science Fund I, Llc | Estimating shared image device operational capabilities or resources |
| US20070098348A1 (en) * | 2005-10-31 | 2007-05-03 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Degradation/preservation management of captured data |
| US9967424B2 (en) * | 2005-06-02 | 2018-05-08 | Invention Science Fund I, Llc | Data storage usage protocol |
| US8964054B2 (en) * | 2006-08-18 | 2015-02-24 | The Invention Science Fund I, Llc | Capturing selected image objects |
| US9167195B2 (en) * | 2005-10-31 | 2015-10-20 | Invention Science Fund I, Llc | Preservation/degradation of video/audio aspects of a data stream |
| US9076208B2 (en) * | 2006-02-28 | 2015-07-07 | The Invention Science Fund I, Llc | Imagery processing |
| US7872675B2 (en) | 2005-06-02 | 2011-01-18 | The Invention Science Fund I, Llc | Saved-image management |
| US9191611B2 (en) * | 2005-06-02 | 2015-11-17 | Invention Science Fund I, Llc | Conditional alteration of a saved image |
| US9451200B2 (en) * | 2005-06-02 | 2016-09-20 | Invention Science Fund I, Llc | Storage access technique for captured data |
| US8233042B2 (en) * | 2005-10-31 | 2012-07-31 | The Invention Science Fund I, Llc | Preservation and/or degradation of a video/audio data stream |
| US20070222865A1 (en) * | 2006-03-15 | 2007-09-27 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Enhanced video/still image correlation |
| US20070008326A1 (en) * | 2005-06-02 | 2007-01-11 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Dual mode image capture technique |
| US20070139529A1 (en) * | 2005-06-02 | 2007-06-21 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Dual mode image capture technique |
| US8681225B2 (en) * | 2005-06-02 | 2014-03-25 | Royce A. Levien | Storage access technique for captured data |
| US9621749B2 (en) * | 2005-06-02 | 2017-04-11 | Invention Science Fund I, Llc | Capturing selected image objects |
| US10003762B2 (en) | 2005-04-26 | 2018-06-19 | Invention Science Fund I, Llc | Shared image devices |
| US8072501B2 (en) * | 2005-10-31 | 2011-12-06 | The Invention Science Fund I, Llc | Preservation and/or degradation of a video/audio data stream |
| US9819490B2 (en) * | 2005-05-04 | 2017-11-14 | Invention Science Fund I, Llc | Regional proximity for shared image device(s) |
| US9942511B2 (en) | 2005-10-31 | 2018-04-10 | Invention Science Fund I, Llc | Preservation/degradation of video/audio aspects of a data stream |
| US9093121B2 (en) | 2006-02-28 | 2015-07-28 | The Invention Science Fund I, Llc | Data management of an audio data stream |
| US8253821B2 (en) * | 2005-10-31 | 2012-08-28 | The Invention Science Fund I, Llc | Degradation/preservation management of captured data |
| US20070109411A1 (en) * | 2005-06-02 | 2007-05-17 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Composite image selectivity |
| US20060274153A1 (en) * | 2005-06-02 | 2006-12-07 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Third party storage of captured data |
| US20070120980A1 (en) | 2005-10-31 | 2007-05-31 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Preservation/degradation of video/audio aspects of a data stream |
| US20070203595A1 (en) * | 2006-02-28 | 2007-08-30 | Searete Llc, A Limited Liability Corporation | Data management of an audio data stream |
| US20130054356A1 (en) * | 2011-08-31 | 2013-02-28 | Jason Richman | Systems and methods for contextualizing services for images |
| US9244694B2 (en) | 2012-12-27 | 2016-01-26 | Intel Corporation | Executing a command within a transport mechanism based on a get and set architecture |
| US9686460B2 (en) * | 2012-12-27 | 2017-06-20 | Intel Corporation | Enabling a metadata storage subsystem |
| US9430465B2 (en) * | 2013-05-13 | 2016-08-30 | Facebook, Inc. | Hybrid, offline/online speech translation system |
| US20200074761A1 (en) * | 2018-08-31 | 2020-03-05 | Denso Ten Limited | On-vehicle device, data collection system, and data collection apparatus |
| US20200077292A1 (en) * | 2018-08-31 | 2020-03-05 | Denso Ten Limited | Data collection apparatus, data collection system, data collection method, and on-vehicle device |
| CN112905849A (en) * | 2021-02-18 | 2021-06-04 | 中国第一汽车股份有限公司 | Vehicle data processing method and device |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6240416B1 (en) * | 1998-09-11 | 2001-05-29 | Ambeo, Inc. | Distributed metadata system and method |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100324989B1 (en) * | 1993-11-08 | 2002-06-24 | 마츠시타 덴끼 산교 가부시키가이샤 | Input display integrated information processing device |
| US20030069968A1 (en) * | 1998-10-01 | 2003-04-10 | O'neil Kevin M. | System for balancing loads among network servers |
| CA2375688A1 (en) * | 2000-04-05 | 2001-10-11 | Sony United Kingdom Limited | Identifying and processing of audio and/or video material |
| US6804719B1 (en) * | 2000-08-24 | 2004-10-12 | Microsoft Corporation | Method and system for relocating files that are partially stored in remote storage |
-
2001
- 2001-07-31 GB GB0118603A patent/GB2378275B/en not_active Expired - Fee Related
-
2002
- 2002-07-30 US US10/208,606 patent/US20030069898A1/en not_active Abandoned
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6240416B1 (en) * | 1998-09-11 | 2001-05-29 | Ambeo, Inc. | Distributed metadata system and method |
Also Published As
| Publication number | Publication date |
|---|---|
| GB2378275B (en) | 2005-06-22 |
| US20030069898A1 (en) | 2003-04-10 |
| GB0118603D0 (en) | 2001-09-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20030069898A1 (en) | Data processing system | |
| JP5353148B2 (en) | Image information retrieving apparatus, image information retrieving method and computer program therefor | |
| US7739597B2 (en) | Interactive media frame display | |
| US10372748B2 (en) | Methods and apparatuses for presenting content | |
| US7949660B2 (en) | Method and apparatus for searching and resource discovery in a distributed enterprise system | |
| CN100452036C (en) | Contents management system, contents management method, and computer program | |
| US7716150B2 (en) | Machine learning system for analyzing and establishing tagging trends based on convergence criteria | |
| Glass et al. | Multi-level acoustic segmentation of continuous speech | |
| JP5046881B2 (en) | Information processing apparatus, display control method, and program | |
| US20100325138A1 (en) | System and method for performing video search on web | |
| US20070143298A1 (en) | Browsing items related to email | |
| US20030081145A1 (en) | Systems and methods for generating digital images having image meta-data combined with the image data | |
| US20080222142A1 (en) | Context based data searching | |
| US20110173141A1 (en) | Method and apparatus for hybrid tagging and browsing annotation for multimedia content | |
| KR20090088424A (en) | Identifying images using face recognition | |
| CN102272784A (en) | Method, apparatus and computer program product for providing analysis and visualization of content items association | |
| JP2010073114A6 (en) | Image information retrieving apparatus, image information retrieving method and computer program therefor | |
| CN102708152A (en) | Integrated management method for electronic evidence | |
| CN103827852B (en) | Assemble WEB page on search engine results page | |
| CN102077168A (en) | Library description of the user interface for federated search results | |
| US20030105880A1 (en) | Distributed processing, storage, and transmision of multimedia information | |
| JP4894253B2 (en) | Metadata generating apparatus and metadata generating method | |
| CN1991842A (en) | Apparatus and method for managing images of mobile terminal | |
| CN112860642A (en) | Court trial data processing method, server and terminal | |
| Shen et al. | The e-recall environment for cloud based mobile rich media data management |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 732E | Amendments to the register in respect of changes of name or changes affecting rights (sect. 32/1977) |
Free format text: REGISTERED BETWEEN 20120329 AND 20120404 |
|
| PCNP | Patent ceased through non-payment of renewal fee |
Effective date: 20120731 |