Patent Grant
8214387
The described technology is directed to the field of document processing.
The present invention relates to the field of electronic data/information processing. More specifically, the present invention relates to methods and apparatuses for enhancing documents.
Paper documents have an enduring appeal, as can be seen by the proliferation of paper documents in the computer age. It has never been easier to print and publish paper documents than it is today. Paper documents prevail even though electronic documents are easier to duplicate, transmit, search and edit.
Given the popularity of paper documents and the advantages of electronic documents, it would be useful to combine the benefits of both.
Overview
In this description, reference is made to the accompanying drawings that form a part hereof wherein like numerals designate like parts throughout, and in which are shown, by way of illustration, specific embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present invention. Therefore, the following detailed description is not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.
Various embodiments include a user-friendly technique for filling forms (such as forms on paper, in catalogs, displayed on web pages, other dynamic displays, in advertisements, in books, in magazines, on signs and the like) using a graphical capture device (such as a scanner, digital camera, or other device capable of capturing at least a portion of the rendered form) or other devices. Embodiments may be practiced to engage in many forms of information gathering utilizing a device to interface with human and machine-readable materials.
In this description, various aspects of selected embodiments are described. However, it will be apparent to those of ordinary skill in the art and others that alternate embodiments may be practiced with only some or all of the aspects. For purposes of explanation, specific numbers, materials and configurations are set forth in order to provide a thorough understanding of the embodiments. However, it will be apparent to those of ordinary skill in the art and others that alternate embodiments may be practiced without the specific details. In other instances, well-known features are omitted or simplified in order not to obscure the illustrated embodiments.
Various operations may be described herein as multiple discreet steps in turn, in a manner that is helpful to understanding of the embodiments. However, the order of description should not be construed to imply that these operations are necessarily order dependent. In particular, these operations may not be performed in the order of presentation.
The phrase “in one embodiment” is used repeatedly. The phrase generally does not refer to the same embodiment, however, it may. The terms “comprising,” “having” and “including” are synonymous, unless the context dictates otherwise.
Part I—Introduction
1. Nature of the System
For every paper document that has an electronic counterpart, there exists a discrete amount of information in the paper document that can identify the electronic counterpart. In some embodiments, the system uses a sample of text captured from a paper document, for example using a handheld scanner, to identify and locate an electronic counterpart of the document. In most cases, the amount of text needed by the facility is very small in that a few words of text from a document can often function as an identifier for the paper document and as a link to its electronic counterpart. In addition, the system may use those few words to identify not only the document, but also a location within the document.
Thus, paper documents and their digital counterparts can be associated in many useful ways using the system discussed herein.
1.1. A Quick Overview of the Future
Once the system has associated a piece of text in a paper document with a particular digital entity has been established, the system is able to build a huge amount of functionality on that association.
It is increasingly the case that most paper documents have an electronic counterpart that is accessible on the World Wide Web or from some other online database or document corpus, or can be made accessible, such as in response to the payment of a fee or subscription. At the simplest level, then, when a user scans a few words in a paper document, the system can retrieve that electronic document or some part of it, or display it, email it to somebody, purchase it, print it or post it to a web page. As additional examples, scanning a few words of a book that a person is reading over breakfast could cause the audio-book version in the person's car to begin reading from that point when s/he starts driving to work, or scanning the serial number on a printer cartridge could begin the process of ordering a replacement.
The system implements these and many other examples of “paper/digital integration” without requiring changes to the current processes of writing, printing and publishing documents, giving such conventional rendered documents a whole new layer of digital functionality.
1.2. Terminology
A typical use of the system begins with using an optical scanner to scan text from a paper document, but it is important to note that other methods of capture from other types of document are equally applicable. The system is therefore sometimes described as scanning or capturing text from a rendered document, where those terms are defined as follows:
A rendered document is a printed document or a document shown on a display or monitor. It is a document that is perceptible to a human, whether in permanent form or on a transitory display.
Scanning or capturing is the process of systematic examination to obtain information from a rendered document. The process may involve optical capture using a scanner or camera (for example a camera in a cellphone), or it may involve reading aloud from the document into an audio capture device or typing it on a keypad or keyboard. For more examples, see Section 15.
2. Introduction to the System
This section describes some of the devices, processes and systems that constitute a system for paper/digital integration. In various embodiments, the system builds a wide variety of services and applications on this underlying core that provides the basic functionality.
2.1. The Processes
Text from a rendered document is captured 100, typically in optical form by an optical scanner or audio form by a voice recorder, and this image or sound data is then processed 102, for example to remove artifacts of the capture process or to improve the signal-to-noise ratio. A recognition process 104 such as OCR, speech recognition, or autocorrelation then converts the data into a signature, comprised in some embodiments of text, text offsets, or other symbols. Alternatively, the system performs an alternate form of extracting document signature from the rendered document. The signature represents a set of possible text transcriptions in some embodiments. This process may be influenced by feedback from other stages, for example, if the search process and context analysis 110 have identified some candidate documents from which the capture may originate, thus narrowing the possible interpretations of the original capture.
A post-processing 106 stage may take the output of the recognition process and filter it or perform such other operations upon it as may be useful. Depending upon the embodiment implemented, it may be possible at this stage to deduce some direct actions 107 to be taken immediately without reference to the later stages, such as where a phrase or symbol has been captured which contains sufficient information in itself to convey the user's intent. In these cases no digital counterpart document need be referenced, or even known to the system.
Typically, however, the next stage will be to construct a query 108 or a set of queries for use in searching. Some aspects of the query construction may depend on the search process used and so cannot be performed until the next stage, but there will typically be some operations, such as the removal of obviously misrecognized or irrelevant characters, which can be performed in advance.
The query or queries are then passed to the search and context analysis stage 110. Here, the system optionally attempts to identify the document from which the original data was captured. To do so, the system typically uses search indices and search engines 112, knowledge about the user 114 and knowledge about the user's context or the context in which the capture occurred 116. Search engine 112 may employ and/or index information specifically about rendered documents, about their digital counterpart documents, and about documents that have a web (internet) presence). It may write to, as well as read from, many of these sources and, as has been mentioned, it may feed information into other stages of the process, for example by giving the recognition system 104 information about the language, font, rendering and likely next words based on its knowledge of the candidate documents.
In some circumstances the next stage will be to retrieve 120 a copy of the document or documents that have been identified. The sources of the documents 124 may be directly accessible, for example from a local filing system or database or a web server, or they may need to be contacted via some access service 122 which might enforce authentication, security or payment or may provide other services such as conversion of the document into a desired format.
Applications of the system may take advantage of the association of extra functionality or data with part or all of a document. For example, advertising applications discussed in Section 10.4 may use an association of particular advertising messages or subjects with portions of a document. This extra associated functionality or data can be thought of as one or more overlays on the document, and is referred to herein as “markup.” The next stage of the process 130, then, is to identify any markup relevant to the captured data. Such markup may be provided by the user, the originator, or publisher of the document, or some other party, and may be directly accessible from some source 132 or may be generated by some service 134. In various embodiments, markup can be associated with, and apply to, a rendered document and/or the digital counterpart to a rendered document, or to groups of either or both of these documents.
Lastly, as a result of the earlier stages, some actions may be taken 140. These may be default actions such as simply recording the information found, they may be dependent on the data or document, or they may be derived from the markup analysis. Sometimes the action will simply be to pass the data to another system. In some cases the various possible actions appropriate to a capture at a specific point in a rendered document will be presented to the user as a menu on an associated display, for example on a local display 332, on a computer display 212 or a mobile phone or PDA display 216. If the user doesn't respond to the menu, the default actions can be taken.
2.2. The Components
Computer 212 may include a memory containing computer executable instructions for processing an order from scanning devices 202 and 204. As an example, an order can include an identifier (such as a serial number of the scanning device 202/204 or an identifier that partially or uniquely identifies the user of the scanner), scanning context information (e.g., time of scan, location of scan, etc.) and/or scanned information (such as a text string) that is used to uniquely identify the document being scanned. In alternative embodiments, the operating environment may include more or less components.
Also available on the network 220 are search engines 232, document sources 234, user account services 236, markup services 238 and other network services 239. The network 220 may be a corporate intranet, the public Internet, a mobile phone network or some other network, or any interconnection of the above.
Regardless of the manner by which the devices are coupled to each other, they may all may be operable in accordance with well-known commercial transaction and communication protocols (e.g., Internet Protocol (IP)). In various embodiments, the functions and capabilities of scanning device 202, computer 212, and mobile station 216 may be wholly or partially integrated into one device. Thus, the terms scanning device, computer, and mobile station can refer to the same device depending upon whether the device incorporates functions or capabilities of the scanning device 202, computer 212 and mobile station 216. In addition, some or all of the functions of the search engines 232, document sources 234, user account services 236, markup services 238 and other network services 239 may be implemented on any of the devices and/or other devices not shown.
2.3. The Capture Device
As described above, the capture device may capture text using an optical scanner that captures image data from the rendered document, or using an audio recording device that captures a user's spoken reading of the text, or other methods. Some embodiments of the capture device may also capture images, graphical symbols and icons, etc., including machine readable codes such as barcodes. The device may be exceedingly simple, consisting of little more than the transducer, some storage, and a data interface, relying on other functionality residing elsewhere in the system, or it may be a more full-featured device. For illustration, this section describes a device based around an optical scanner and with a reasonable number of features.
Scanners are well known devices that capture and digitize images. An offshoot of the photocopier industry, the first scanners were relatively large devices that captured an entire document page at once. Recently, portable optical scanners have been introduced in convenient form factors, such as a pen-shaped handheld device.
In some embodiments, the portable scanner is used to scan text, graphics, or symbols from rendered documents. The portable scanner has a scanning element that captures text, symbols, graphics, etc, from rendered documents. In addition to documents that have been printed on paper, in some embodiments, rendered documents include documents that have been displayed on a screen such as a CRT monitor or LCD display.
A microphone 310 and associated circuitry convert the sound of the environment (including spoken words) into machine-compatible signals, and other input facilities exist in the form of buttons, scroll-wheels or other tactile sensors such as touch-pads 314.
Feedback to the user is possible through a visual display or indicator lights 332, through a loudspeaker or other audio transducer 334 and through a vibrate module 336.
The scanner 302 comprises logic 326 to interact with the various other components, possibly processing the received signals into different formats and/or interpretations. Logic 326 may be operable to read and write data and program instructions stored in associated storage 330 such as RAM, ROM, flash, or other suitable memory. It may read a time signal from the clock unit 328. The scanner 302 also includes an interface 316 to communicate scanned information and other signals to a network and/or an associated computing device. In some embodiments, the scanner 302 may have an on-board power supply 332. In other embodiments, the scanner 302 may be powered from a tethered connection to another device, such as a Universal Serial Bus (USB) connection.
As an example of one use of scanner 302, a reader may scan some text from a newspaper article with scanner 302. The text is scanned as a bit-mapped image via the scanning head 308. Logic 326 causes the bit-mapped image to be stored in memory 330 with an associated time-stamp read from the clock unit 328. Logic 326 may also perform optical character recognition (OCR) or other post-scan processing on the bit-mapped image to convert it to text. Logic 326 may optionally extract a signature from the image, for example by performing a convolution-like process to locate repeating occurrences of characters, symbols or objects, and determine the distance or number of other characters, symbols, or objects between these repeated elements. The reader may then upload the bit-mapped image (or text or other signature, if post-scan processing has been performed by logic 326) to an associated computer via interface 316.
As an example of another use of scanner 302, a reader may capture some text from an article as an audio file by using microphone 310 as an acoustic capture port. Logic 326 causes audio file to be stored in memory 328. Logic 326 may also perform voice recognition or other post-scan processing on the audio file to convert it to text. As above, the reader may then upload the audio file (or text produced by post-scan processing performed by logic 326) to an associated computer via interface 316.
Part II—Overview of the Areas of the Core System
As paper-digital integration becomes more common, there are many aspects of existing technologies that can be changed to take better advantage of this integration, or to enable it to be implemented more effectively. This section highlights some of those issues.
3. Search
Searching a corpus of documents, even so large a corpus as the World Wide Web, has become commonplace for ordinary users, who use a keyboard to construct a search query which is sent to a search engine. This section and the next discuss the aspects of both the construction of a query originated by a capture from a rendered document, and the search engine that handles such a query.
3.1. Scan/Speak/Type as Search Query
Use of the described system typically starts with a few words being captured from a rendered document using any of several methods, including those mentioned in Section 1.2 above. Where the input needs some interpretation to convert it to text, for example in the case of OCR or speech input, there may be end-to-end feedback in the system so that the document corpus can be used to enhance the recognition process. End-to-end feedback can be applied by performing an approximation of the recognition or interpretation, identifying a set of one or more candidate matching documents, and then using information from the possible matches in the candidate documents to further refine or restrict the recognition or interpretation. Candidate documents can be weighted according to their probable relevance (for example, based on then number of other users who have scanned in these documents, or their popularity on the Internet), and these weights can be applied in this iterative recognition process.
3.2. Short Phrase Searching
Because the selective power of a search query based on a few words is greatly enhanced when the relative positions of these words are known, only a small amount of text need be captured for the system to identify the text's location in a corpus. Most commonly, the input text will be a contiguous sequence of words, such as a short phrase.
3.2.1. Finding Document and Location in Document from Short Capture
In addition to locating the document from which a phrase originates, the system can identify the location in that document and can take action based on this knowledge.
3.2.2. Other Methods of Finding Location
The system may also employ other methods of discovering the document and location, such as by using watermarks or other special markings on the rendered document.
3.3. Incorporation of Other Factors in Search Query
In addition to the captured text, other factors (i.e., information about user identity, profile, and context) may form part of the search query, such as the time of the capture, the identity and geographical location of the user, knowledge of the user's habits and recent activities, etc.
The document identity and other information related to previous captures, especially if they were quite recent, may form part of a search query.
The identity of the user may be determined from a unique identifier associated with a capturing device, and/or biometric or other supplemental information (speech patterns, fingerprints, etc.).
3.4. Knowledge of Nature of Unreliability in Search Query (OCR Errors etc)
The search query can be constructed taking into account the types of errors likely to occur in the particular capture method used. One example of this is an indication of suspected errors in the recognition of specific characters; in this instance a search engine may treat these characters as wildcards, or assign them a lower priority.
3.5. Local Caching of Index for Performance/Offline Use
Sometimes the capturing device may not be in communication with the search engine or corpus at the time of the data capture. For this reason, information helpful to the offline use of the device may be downloaded to the device in advance, or to some entity with which the device can communicate. In some cases, all or a substantial part of an index associated with a corpus may be downloaded. This topic is discussed further in Section 15.3.
3.6. Queries, in Whatever Form, May Be Recorded and Acted on Later
If there are likely to be delays or cost associated with communicating a query or receiving the results, this pre-loaded information can improve the performance of the local device, reduce communication costs, and provide helpful and timely user feedback.
In the situation where no communication is available (the local device is “offline”), the queries may be saved and transmitted to the rest of the system at such a time as communication is restored.
In these cases it may be important to transmit a timestamp with each query. The time of the capture can be a significant factor in the interpretation of the query. For example, Section 13.1 discusses the importance of the time of capture in relation to earlier captures. It is important to note that the time of capture will not always be the same as the time that the query is executed.
3.7. Parallel Searching
For performance reasons, multiple queries may be launched in response to a single capture, either in sequence or in parallel. Several queries may be sent in response to a single capture, for example as new words are added to the capture, or to query multiple search engines in parallel.
For example, in some embodiments, the system sends queries to a special index for the current document, to a search engine on a local machine, to a search engine on the corporate network, and to remote search engines on the Internet.
The results of particular searches may be given higher priority than those from others.
The response to a given query may indicate that other pending queries are superfluous; these may be cancelled before completion.
4. Paper and Search Engines
Often it is desirable for a search engine that handles traditional online queries also to handle those originating from rendered documents. Conventional search engines may be enhanced or modified in a number of ways to make them more suitable for use with the described system.
The search engine and/or other components of the system may create and maintain indices that have different or extra features. The system may modify an incoming paper-originated query or change the way the query is handled in the resulting search, thus distinguishing these paper-originated queries from those coming from queries typed into web browsers and other sources. And the system may take different actions or offer different options when the results are returned by the searches originated from paper as compared to those from other sources. Each of these approaches is discussed below.
4.1. Indexing
Often, the same index can be searched using either paper-originated or traditional queries, but the index may be enhanced for use in the current system in a variety of ways.
4.1.1. Knowledge About the Paper Form
Extra fields can be added to such an index that will help in the case of a paper-based search.
Index Entry Indicating Document Availability in Paper Form
The first example is a field indicating that the document is known to exist or be distributed in paper form. The system may give such documents higher priority if the query comes from paper.
Knowledge of Popularity Paper Form
In this example statistical data concerning the popularity of paper documents (and, optionally, concerning sub-regions within these documents)—for example the amount of scanning activity, circulation numbers provided by the publisher or other sources, etc—is used to give such documents higher priority, to boost the priority of digital counterpart documents (for example, for browser-based queries or web searches), etc.
Knowledge of Rendered Format
Another important example may be recording information about the layout of a specific rendering of a document.
For a particular edition of a book, for example, the index may include information about where the line breaks and page breaks occur, which fonts were used, any unusual capitalization.
The index may also include information about the proximity of other items on the page, such as images, text boxes, tables and advertisements.
Use of Semantic Information in Original
Lastly, semantic information that can be deduced from the source markup but is not apparent in the paper document, such as the fact that a particular piece of text refers to an item offered for sale, or that a certain paragraph contains program code, may also be recorded in the index.
4.1.2. Indexing in the Knowledge of the Capture Method
A second factor that may modify the nature of the index is the knowledge of the type of capture likely to be used. A search initiated by an optical scan may benefit if the index takes into account characters that are easily confused in the OCR process, or includes some knowledge of the fonts used in the document. Similarly, if the query is from speech recognition, an index based on similar-sounding phonemes may be much more efficiently searched. An additional factor that may affect the use of the index in the described model is the importance of iterative feedback during the recognition process. If the search engine is able to provide feedback from the index as the text is being captured, it can greatly increase the accuracy of the capture.
Indexing Using Offsets
If the index is likely to be searched using the offset-based/autocorrelation OCR methods described in Section 9, in some embodiments, the system stores the appropriate offset or signature information in an index.
4.1.3. Multiple Indices
Lastly, in the described system, it may be common to conduct searches on many indices. Indices may be maintained on several machines on a corporate network. Partial indices may be downloaded to the capture device, or to a machine close to the capture device. Separate indices may be created for users or groups of users with particular interests, habits or permissions. An index may exist for each filesystem, each directory, even each file on a user's hard disk. Indexes are published and subscribed to by users and by systems. It will be important, then, to construct indices that can be distributed, updated, merged and separated efficiently.
4.2. Handling the Queries
4.2.1. Knowing the Capture is from Paper
A search engine may take different actions when it recognizes that a search query originated from a paper document. The engine might handle the query in a way that is more tolerant to the types of errors likely to appear in certain capture methods, for example.
It may be able to deduce this from some indicator included in the query (for example a flag indicating the nature of the capture), or it may deduce this from the query itself (for example, it may recognize errors or uncertainties typical of the OCR process).
Alternatively, queries from a capture device can reach the engine by a different channel or port or type of connection than those from other sources, and can be distinguished in that way. For example, some embodiments of the system will route queries to the search engine by way of a dedicated gateway. Thus, the search engine knows that all queries passing through the dedicated gateway were originated from a paper document.
4.2.2. Use of Context
Section 13 below describes a variety of different factors which are external to the captured text itself, yet which can be a significant aid in identifying a document. These include such things as the history of recent scans, the longer-term reading habits of a particular user, the geographic location of a user and the user's recent use of particular electronic documents. Such factors are referred to herein as “context.”
Some of the context may be handled by the search engine itself, and be reflected in the search results. For example, the search engine may keep track of a user's scanning history, and may also cross-reference this scanning history to conventional keyboard-based queries. In such cases, the search engine maintains and uses more state information about each individual user than do most conventional search engines, and each interaction with a search engine may be considered to extend over several searches and a longer period of time than is typical today.
Some of the context may be transmitted to the search engine in the search query (Section 3.3), and may possibly be stored at the engine so as to play a part in future queries. Lastly, some of the context will best be handled elsewhere, and so becomes a filter or secondary search applied to the results from the search engine.
Data-Stream Input to Search
An important input into the search process is the broader context of how the community of users is interacting with the rendered version of the document—for example, which documents are most widely read and by whom. There are analogies with a web search returning the pages that are most frequently linked to, or those that are most frequently selected from past search results. For further discussion of this topic, see Sections 13.4 and 14.2.
4.2.3. Document Sub-Regions
The described system can emit and use not only information about documents as a whole, but also information about sub-regions of documents, even down to individual words. Many existing search engines concentrate simply on locating a document or file that is relevant to a particular query. Those that can work on a finer grain and identify a location within a document will provide a significant benefit for the described system.
4.3. Returning the Results
The search engine may use some of the further information it now maintains to affect the results returned.
The system may also return certain documents to which the user has access only as a result of being in possession of the paper copy (Section 7.4).
The search engine may also offer new actions or options appropriate to the described system, beyond simple retrieval of the text.
5. Markup, Annotations and Metadata
In addition to performing the capture-search-retrieve process, the described system also associates extra functionality with a document, and in particular with specific locations or segments of text within a document. This extra functionality is often, though not exclusively, associated with the rendered document by being associated with its electronic counterpart. As an example, hyperlinks in a web page could have the same functionality when a printout of that web page is scanned. In some cases, the functionality is not defined in the electronic document, but is stored or generated elsewhere.
This layer of added functionality is referred to herein as “markup.”
5.1. Overlays, Static and Dynamic
One way to think of the markup is as an “overlay” on the document, which provides further information about-and may specify actions associated with-the document or some portion of it. The markup may include human-readable content, but is often invisible to a user and/or intended for machine use. Examples include options to be displayed in a popup-menu on a nearby display when a user captures text from a particular area in a rendered document, or audio samples that illustrate the pronunciation of a particular phrase.
5.1.1. Several Layers, Possibly from Several Sources
Any document may have multiple overlays simultaneously, and these may be sourced from a variety of locations. Markup data may be created or supplied by the author of the document, or by the user, or by some other party.
Markup data may be attached to the electronic document or embedded in it. It may be found in a conventional location (for example, in the same place as the document but with a different filename suffix). Markup data may be included in the search results of the query that located the original document, or may be found by a separate query to the same or another search engine. Markup data may be found using the original captured text and other capture information or contextual information, or it may be found using already-deduced information about the document and location of the capture. Markup data may be found in a location specified in the document, even if the markup itself is not included in the document.
The markup may be largely static and specific to the document, similar to the way links on a traditional html web page are often embedded as static data within the html document, but markup may also be dynamically generated and/or applied to a large number of documents. An example of dynamic markup is information attached to a document that includes the up-to-date share price of companies mentioned in that document. An example of broadly applied markup is translation information that is automatically available on multiple documents or sections of documents in a particular language.
5.1.2. Personal “Plug-In” Layers
Users may also install, or subscribe to particular sources of, markup data, thus personalizing the system's response to particular captures.
5.2. Keywords and Phrases, Trademarks and Logos
Some elements in documents may have particular “markup” or functionality associated with them based on their own characteristics rather than their location in a particular document. Examples include special marks that are printed in the document purely for the purpose of being scanned, as well as logos and trademarks that can link the user to further information about the organization concerned. The same applies to “keywords” or “key phrases” in the text. Organizations might register particular phrases with which they are associated, or with which they would like to be associated, and attach certain markup to them that would be available wherever that phrase was scanned.
Any word, phrase, etc. may have associated markup. For example, the system may add certain items to a pop-up menu (e.g., a link to an online bookstore) whenever the user captures the word “book,” or the title of a book, or a topic related to books. In some embodiments, of the system, digital counterpart documents or indices are consulted to determine whether a capture occurred near the word “book,” or the title of a book, or a topic related to books—and the system behavior is modified in accordance with this proximity to keyword elements. In the preceding example, note that markup enables data captured from non-commercial text or documents to trigger a commercial transaction.
5.3. User-Supplied Content
5.3.1. User Comments and Annotations, Including Multimedia
Annotations are another type of electronic information that may be associated with a document. For example, a user can attach an audio file of his/her thoughts about a particular document for later retrieval as voice annotations. As another example of a multimedia annotation, a user may attach photographs of places referred to in the document. The user generally supplies annotations for the document but the system can associate annotations from other sources (for example, other users in a work group may share annotations).
5.3.2. Notes from Proof-Reading
An important example of user-sourced markup is the annotation of paper documents as part of a proofreading, editing or reviewing process.
5.4. Third-Party Content
As mentioned earlier, markup data may often be supplied by third parties, such as by other readers of the document. Online discussions and reviews are a good example, as are community-managed information relating to particular works, volunteer-contributed translations and explanations.
Another example of third-party markup is that provided by advertisers.
5.5. Dynamic Markup Based on Other Users' Data Streams
By analyzing the data captured from documents by several or all users of the system, markup can be generated based on the activities and interests of a community. An example might be an online bookstore that creates markup or annotations that tell the user, in effect, “People who enjoyed this book also enjoyed . . . ” The markup may be less anonymous, and may tell the user which of the people in his/her contact list have also read this document recently. Other examples of datastream analysis are included in Section 14.
5.6. Markup Based on External Events and Data Sources
Markup will often be based on external events and data sources, such as input from a corporate database, information from the public Internet, or statistics gathered by the local operating system.
Data sources may also be more local, and in particular may provide information about the user's context—his/her identity, location and activities. For example, the system might communicate with the user's mobile phone and offer a markup layer that gives the user the option to send a document to somebody that the user has recently spoken to on the phone.
6. Authentication, Personalization and Security
In many situations, the identity of the user will be known. Sometimes this will be an “anonymous identity,” where the user is identified only by the serial number of the capture device, for example. Typically, however, it is expected that the system will have a much more detailed knowledge of the user, which can be used for personalizing the system and to allow activities and transactions to be performed in the user's name.
6.1. User History and “Life Library”
One of the simplest and yet most useful functions that the system can perform is to keep a record for a user of the text that s/he has captured and any further information related to that capture, including the details of any documents found, the location within that document and any actions taken as a result.
This stored history is beneficial for both the user and the system.
6.1.1. For the User
The user can be presented with a “Life Library,” a record of everything s/he has read and captured. This may be simply for personal interest, but may be used, for example, in a library by an academic who is gathering material for the bibliography of his next paper.
In some circumstances, the user may wish to make the library public, such as by publishing it on the web in a similar manner to a weblog, so that others may see what s/he is reading and finds of interest.
Lastly, in situations where the user captures some text and the system cannot immediately act upon the capture (for example, because an electronic version of the document is not yet available) the capture can be stored in the library and can be processed later, either automatically or in response to a user request. A user can also subscribe to new markup services and apply them to previously captured scans.
6.1.2. For the System
A record of a user's past captures is also useful for the system. Many aspects of the system operation can be enhanced by knowing the user's reading habits and history. The simplest example is that any scan made by a user is more likely to come from a document that the user has scanned in the recent past, and in particular if the previous scan was within the last few minutes it is very likely to be from the same document. Similarly, it is more likely that a document is being read in start-to-finish order. Thus, for English documents, it is also more likely that later scans will occur farther down in the document. Such factors can help the system establish the location of the capture in cases of ambiguity, and can also reduce the amount of text that needs to be captured.
6.2. Scanner as Payment, Identity and Authentication Device
Because the capture process generally begins with a device of some sort, typically an optical scanner or voice recorder, this device may be used as a key that identifies the user and authorizes certain actions.
6.2.1. Associate Scanner with Phone or Other Account
The device may be embedded in a mobile phone or in some other way associated with a mobile phone account. For example, a scanner may be associated with a mobile phone account by inserting a SIM card associated with the account into the scanner. Similarly, the device may be embedded in a credit card or other payment card, or have the facility for such a card to be connected to it. The device may therefore be used as a payment token, and financial transactions may be initiated by the capture from the rendered document.
6.2.2. Using Scanner Input for Authentication
The scanner may also be associated with a particular user or account through the process of scanning some token, symbol or text associated with that user or account. In addition, scanner may be used for biometric identification, for example by scanning the fingerprint of the user. In the case of an audio-based capture device, the system may identify the user by matching the voice pattern of the user or by requiring the user to speak a certain password or phrase.
For example, where a user scans a quote from a book and is offered the option to buy the book from an online retailer, the user can select this option, and is then prompted to scan his/her fingerprint to confirm the transaction.
See also Sections 15.5 and 15.6.
6.2.3. Secure Scanning Device
When the capture device is used to identify and authenticate the user, and to initiate transactions on behalf of the user, it is important that communications between the device and other parts of the system are secure. It is also important to guard against such situations as another device impersonating a scanner, and so-called “man in the middle” attacks where communications between the device and other components are intercepted.
Techniques for providing such security are well understood in the art; in various embodiments, the hardware and software in the device and elsewhere in the system are configured to implement such techniques.
7. Publishing Models and Elements
An advantage of the described system is that there is no need to alter the traditional processes of creating, printing or publishing documents in order to gain many of the system's benefits. There are reasons, though, that the creators or publishers of a document—hereafter simply referred to as the “publishers”—may wish to create functionality to support the described system.
This section is primarily concerned with the published documents themselves. For information about other related commercial transactions, such as advertising, see Section 10 entitled “P-Commerce.”
7.1. Electronic Companions to Printed Documents
The system allows for printed documents to have an associated electronic presence. Conventionally publishers often ship a CD-ROM with a book that contains further digital information, tutorial movies and other multimedia data, sample code or documents, or further reference materials. In addition, some publishers maintain web sites associated with particular publications which provide such materials, as well as information which may be updated after the time of publishing, such as errata, further comments, updated reference materials, bibliographies and further sources of relevant data, and translations into other languages. Online forums allow readers to contribute their comments about the publication.
The described system allows such materials to be much more closely tied to the rendered document than ever before, and allows the discovery of and interaction with them to be much easier for the user. By capturing a portion of text from the document, the system can automatically connect the user to digital materials associated with the document, and more particularly associated with that specific part of the document. Similarly, the user can be connected to online communities that discuss that section of the text, or to annotations and commentaries by other readers. In the past, such information would typically need to be found by searching for a particular page number or chapter.
An example application of this is in the area of academic textbooks (Section 17.5).
7.2. “Subscriptions” to Printed Documents
Some publishers may have mailing lists to which readers can subscribe if they wish to be notified of new relevant matter or when a new edition of the book is published. With the described system, the user can register an interest in particular documents or parts of documents more easily, in some cases even before the publisher has considered providing any such functionality. The reader's interest can be fed to the publisher, possibly affecting their decision about when and where to provide updates, further information, new editions or even completely new publications on topics that have proved to be of interest in existing books.
7.3. Printed Marks with Special Meaning or Containing Special Data
Many aspects of the system are enabled simply through the use of the text already existing in a document. If the document is produced in the knowledge that it may be used in conjunction with the system, however, extra functionality can be added by printing extra information in the form of special marks, which may be used to identify the text or a required action more closely, or otherwise enhance the document's interaction with the system. The simplest and most important example is an indication to the reader that the document is definitely accessible through the system. A special icon might be used, for example, to indicate that this document has an online discussion forum associated with it.
Such symbols may be intended purely for the reader, or they may be recognized by the system when scanned and used to initiate some action. Sufficient data may be encoded in the symbol to identify more than just the symbol: it may also store information, for example about the document, edition, and location of the symbol, which could be recognized and read by the system.
7.4. Authorization Through Possession of the Paper Document
There are some situations where possession of or access to the printed document would entitle the user to certain privileges, for example, the access to an electronic copy of the document or to additional materials. With the described system, such privileges could be granted simply as a result of the user capturing portions of text from the document, or scanning specially printed symbols. In cases where the system needed to ensure that the user was in possession of the entire document, it might prompt the user to scan particular items or phrases from particular pages, e.g. “the second line of page 46.”
7.5. Documents Which Expire
If the printed document is a gateway to extra materials and functionality, access to such features can also be time-limited. After the expiry date, a user may be required to pay a fee or obtain a newer version of the document to access the features again. The paper document will, of course, still be usable, but will lose some of its enhanced electronic functionality. This may be desirable, for example, because there is profit for the publisher in receiving fees for access to electronic materials, or in requiring the user to purchase new editions from time to time, or because there are disadvantages associated with outdated versions of the printed document remaining in circulation. Coupons are an example of a type of commercial document that can have an expiration date.
7.6. Popularity Analysis and Publishing Decisions
Section 10.5 discusses the use of the system's statistics to influence compensation of authors and pricing of advertisements.
In some embodiments, the system deduces the popularity of a publication from the activity in the electronic community associated with it as well as from the use of the paper document. These factors may help publishers to make decisions about what they will publish in future. If a chapter in an existing book, for example, turns out to be exceedingly popular, it may be worth expanding into a separate publication.
8. Document Access Services
An important aspect of the described system is the ability to provide to a user who has access to a rendered copy of a document access to an electronic version of that document. In some cases, a document is freely available on a public network or a private network to which the user has access. The system uses the captured text to identify, locate and retrieve the document, in some cases displaying it on the user's screen or depositing it in their email inbox.
In some cases, a document will be available in electronic form, but for a variety of reasons may not be accessible to the user. There may not be sufficient connectivity to retrieve the document, the user may not be entitled to retrieve it, there may be a cost associated with gaining access to it, or the document may have been withdrawn and possibly replaced by a new version, to name just a few possibilities. The system typically provides feedback to the user about these situations.
As mentioned in Section 7.4, the degree or nature of the access granted to a particular user may be different if it is known that the user already has access to a printed copy of the document.
8.1. Authenticated Document Access
Access to the document may be restricted to specific users, or to those meeting particular criteria, or may only be available in certain circumstances, for example when the user is connected to a secure network. Section 6 describes some of the ways in which the credentials of a user and scanner may be established.
8.2. Document Purchase—Copyright-Owner Compensation
Documents that are not freely available to the general public may still be accessible on payment of a fee, often as compensation to the publisher or copyright-holder. The system may implement payment facilities directly or may make use of other payment methods associated with the user, including those described in Section 6.2.
8.3. Document Escrow and Proactive Retrieval
Electronic documents are often transient; the digital source version of a rendered document may be available now but inaccessible in future. The system may retrieve and store the existing version on behalf of the user, even if the user has not requested it, thus guaranteeing its availability should the user request it in future. This also makes it available for the system's use, for example for searching as part of the process of identifying future captures.
In the event that payment is required for access to the document, a trusted “document escrow” service can retrieve the document on behalf of the user, such as upon payment of a modest fee, with the assurance that the copyright holder will be fully compensated in future if the user should ever request the document from the service.
Variations on this theme can be implemented if the document is not available in electronic form at the time of capture. The user can authorize the service to submit a request for or make a payment for the document on his/her behalf if the electronic document should become available at a later date.
8.4. Association with Other Subscriptions and Accounts
Sometimes payment may be waived, reduced or satisfied based on the user's existing association with another account or subscription. Subscribers to the printed version of a newspaper might automatically be entitled to retrieve the electronic version, for example.
In other cases, the association may not be quite so direct: a user may be granted access based on an account established by their employer, or based on their scanning of a printed copy owned by a friend who is a subscriber.
8.5. Replacing Photocopying with Scan-and-Print
The process of capturing text from a paper document, identifying an electronic original, and printing that original, or some portion of that original associated with the capture, forms an alternative to traditional photocopying with many advantages:
8.6. Locating Valuable Originals from Photocopies
When documents are particularly valuable, as in the case of legal instruments or documents that have historical or other particular significance, people may typically work from copies of those documents, often for many years, while the originals are kept in a safe location.
The described system could be coupled to a database which records the location of an original document, for example in an archiving warehouse, making it easy for somebody with access to a copy to locate the archived original paper document.
9. Text Recognition Technologies
Optical Character Recognition (OCR) technologies have traditionally focused on images that include a large amount of text, for example from a flat-bed scanner capturing a whole page. OCR technologies often need substantial training and correcting by the user to produce useful text. OCR technologies often require substantial processing power on the machine doing the OCR, and, while many systems use a dictionary, they are generally expected to operate on an effectively infinite vocabulary.
All of the above traditional characteristics may be improved upon in the described system.
While this section focuses on OCR, many of the issues discussed map directly onto other recognition technologies, in particular speech recognition. As mentioned in Section 3.1, the process of capturing from paper may be achieved by a user reading the text aloud into a device which captures audio. Those skilled in the art will appreciate that principles discussed here with respect to images, fonts, and text fragments often also apply to audio samples, user speech models and phonemes.
9.1. Optimization for Appropriate Devices
A scanning device for use with the described system will often be small, portable, and low power. The scanning device may capture only a few words at a time, and in some implementations does not even capture a whole character at once, but rather a horizontal slice through the text, many such slices being stitched together to form a recognizable signal from which the text may be deduced. The scanning device may also have very limited processing power or storage so, while in some embodiments it may perform all of the OCR process itself, many embodiments will depend on a connection to a more powerful device, possibly at a later time, to convert the captured signals into text. Lastly, it may have very limited facilities for user interaction, so may need to defer any requests for user input until later, or operate in a “best-guess” mode to a greater degree than is common now.
9.2. “Uncertain” OCR
The primary new characteristic of OCR within the described system is the fact that it will, in general, examine images of text which exists elsewhere and which may be retrieved in digital form. An exact transcription of the text is therefore not always required from the OCR engine. The OCR system may output a set or a matrix of possible matches, in some cases including probability weightings, which can still be used to search for the digital original.
9.3. Iterative OCR—Guess, Disambiguate, Guess . . .
If the device performing the recognition is able to contact the document index at the time of processing, then the OCR process can be informed by the contents of the document corpus as it progresses, potentially offering substantially greater recognition accuracy.
Such a connection will also allow the device to inform the user when sufficient text has been captured to identify the digital source.
9.4. Using Knowledge of Likely Rendering
When the system has knowledge of aspects of the likely printed rendering of a document—such as the font typeface used in printing, or the layout of the page, or which sections are in italics-this too can help in the recognition process. (Section 4.1.1)
9.5. Font Caching—Determine Font on Host, Download to Client
As candidate source texts in the document corpus are identified, the font, or a rendering of it, may be downloaded to the device to help with the recognition.
9.6. Autocorrelation and Character Offsets
While component characters of a text fragment may be the most recognized way to represent a fragment of text that may be used as a document signature, other representations of the text may work sufficiently well that the actual text of a text fragment need not be used when attempting to locate the text fragment in a digital document and/or database, or when disambiguating the representation of a text fragment into a readable form. Other representations of text fragments may provide benefits that actual text representations lack. For example, optical character recognition of text fragments is often prone to errors, unlike other representations of captured text fragments that may be used to search for and/or recreate a text fragment without resorting to optical character recognition for the entire fragment. Such methods may be more appropriate for some devices used with the current system.
Those of ordinary skill in the art and others will appreciate that there are many ways of describing the appearance of text fragments. Such characterizations of text fragments may include, but are not limited to, word lengths, relative word lengths, character heights, character widths, character shapes, character frequencies, token frequencies, and the like. In some embodiments, the offsets between matching text tokens (i.e., the number of intervening tokens plus one) are used to characterize fragments of text.
Conventional OCR uses knowledge about fonts, letter structure and shape to attempt to determine characters in scanned text. Embodiments of the present invention are different; they employ a variety of methods that use the rendered text itself to assist in the recognition process. These embodiments use characters (or tokens) to “recognize each other.” One way to refer to such self-recognition is “template matching,” and is similar to “convolution.” To perform such self-recognition, the system slides a copy of the text horizontally over itself and notes matching regions of the text images. Prior template matching and convolution techniques encompass a variety of related techniques. These techniques to tokenize and/or recognize characters/tokens will be collectively referred to herein as “autocorrelation,” as the text is used to correlate with its own component parts when matching characters/tokens.
When autocorrelating, complete connected regions that match are of interest. This occurs when characters (or groups of characters) overlay other instances of the same character (or group). Complete connected regions that match automatically provide tokenizing of the text into component tokens. As the two copies of the text are slid past each other, the regions where perfect matching occurs (i.e., all pixels in a vertical slice are matched) are noted. When a character/token matches itself, the horizontal extent of this matching (e.g., the connected matching portion of the text) also matches.
Note that at this stage there is no need to determine the actual identity of each token (i.e., the particular letter, digit or symbol, or group of these, that corresponds to the token image), only the offset to the next occurrence of the same token in the scanned text. The offset number is the distance (number of tokens) to the next occurrence of the same token. If the token is unique within the text string, the offset is zero (0). The sequence of token offsets thus generated is a signature that can be used to identify the scanned text.
In some embodiments, the token offsets determined for a string of scanned tokens are compared to an index that indexes a corpus of electronic documents based upon the token offsets of their contents (Section 4.1.2). In other embodiments, the token offsets determined for a string of scanned tokens are converted to text, and compared to a more conventional index that indexes a corpus of electronic documents based upon their contents
As has been noted earlier, a similar token-correlation process may be applied to speech fragments when the capture process consists of audio samples of spoken words.
9.7. Font/Character “Self-Recognition”
Conventional template-matching OCR compares scanned images to a library of character images. In essence, the alphabet is stored for each font and newly scanned images are compared to the stored images to find matching characters. The process generally has an initial delay until the correct font has been identified. After that, the OCR process is relatively quick because most documents use the same font throughout. Subsequent images can therefore be converted to text by comparison with the most recently identified font library.
The shapes of characters in most commonly used fonts are related. For example, in most fonts, the letter “c” and the letter “e” are visually related—as are “t” and “f,” etc. The OCR process is enhanced by use of this relationship to construct templates for letters that have not been scanned yet. For example, where a reader scans a short string of text from a paper document in a previously unencountered font such that the system does not have a set of image templates with which to compare the scanned images the system can leverage the probable relationship between certain characters to construct the font template library even though it has not yet encountered all of the letters in the alphabet. The system can then use the constructed font template library to recognize subsequent scanned text and to further refine the constructed font library.
9.8. Send Anything Unrecognized (Including Graphics) to Server
When images cannot be machine-transcribed into a form suitable for use in a search process, the images themselves can be saved for later use by the user, for possible manual transcription, or for processing at a later date when different resources may be available to the system.
10. P-Commerce
Many of the actions made possible by the system result in some commercial transaction taking place. The phrase p-commerce is used herein to describe commercial activities initiated from paper via the system.
10.1. Sales of Documents from Their Physical Printed Copies.
When a user captures text from a document, the user may be offered that document for purchase either in paper or electronic form. The user may also be offered related documents, such as those quoted or otherwise referred to in the paper document, or those on a similar subject, or those by the same author.
10.2. Sales of Anything Else Initiated or Aided by Paper
The capture of text may be linked to other commercial activities in a variety of ways. The captured text may be in a catalog that is explicitly designed to sell items, in which case the text will be associated fairly directly with the purchase of an item (Section 18.2). The text may also be part of an advertisement, in which case a sale of the item being advertised may ensue.
In other cases, the user captures other text from which their potential interest in a commercial transaction may be deduced. A reader of a novel set in a particular country, for example, might be interested in a holiday there. Someone reading a review of a new car might be considering purchasing it. The user may capture a particular fragment of text knowing that some commercial opportunity will be presented to them as a result, or it may be a side-effect of their capture activities.
10.3. Capture of Labels, Icons, Serial Numbers, Barcodes on an Item Resulting in a Sale
Sometimes text or symbols are actually printed on an item or its packaging. An example is the serial number or product id often found on a label on the back or underside of a piece of electronic equipment. The system can offer the user a convenient way to purchase one or more of the same items by capturing that text. They may also be offered manuals, support or repair services.
10.4. Contextual Advertisements
In addition to the direct capture of text from an advertisement, the system allows for a new kind of advertising which is not necessarily explicitly in the rendered document, but is nonetheless based on what people are reading.
10.4.1. Advertising Based on Scan Context and History
In a traditional paper publication, advertisements generally consume a large amount of space relative to the text of a newspaper article, and a limited number of them can be placed around a particular article. In the described system, advertising can be associated with individual words or phrases, and can selected according to the particular interest the user has shown by capturing that text and possibly taking into account their history of past scans.
With the described system, it is possible for a purchase to be tied to a particular printed document and for an advertiser to get significantly more feedback about the effectiveness of their advertising in particular print publications.
10.4.2. Advertising Based on User Context and History
The system may gather a large amount of information about other aspects of a user's context for its own use (Section 13); estimates of the geographical location of the user are a good example. Such data can also be used to tailor the advertising presented to a user of the system.
10.5. Models of Compensation
The system enables some new models of compensation for advertisers and marketers. The publisher of a printed document containing advertisements may receive some income from a purchase that originated from their document. This may be true whether or not the advertisement existed in the original printed form; it may have been added electronically either by the publisher, the advertiser or some third party, and the sources of such advertising may have been subscribed to by the user.
10.5.1. Popularity-Based Compensation
Analysis of the statistics generated by the system can reveal the popularity of certain parts of a publication (Section 14.2). In a newspaper, for example, it might reveal the amount of time readers spend looking at a particular page or article, or the popularity of a particular columnist. In some circumstances, it may be appropriate for an author or publisher to receive compensation based on the activities of the readers rather than on more traditional metrics such as words written or number of copies distributed. An author whose work becomes a frequently read authority on a subject might be considered differently in future contracts from one whose books have sold the same number of copies but are rarely opened. (See also Section 7.6)
10.5.2. Popularity-Based Advertising
Decisions about advertising in a document may also be based on statistics about the readership. The advertising space around the most popular columnists may be sold at a premium rate. Advertisers might even be charged or compensated some time after the document is published based on knowledge about how it was received.
10.6. Marketing Based on Life Library
The “Life Library” or scan history described in Sections 6.1 and 16.1 can be an extremely valuable source of information about the interests and habits of a user. Subject to the appropriate consent and privacy issues, such data can inform offers of goods or services to the user. Even in an anonymous form, the statistics gathered can be exceedingly useful.
10.7. Sale/Information at Later Date (When Available)
Advertising and other opportunities for commercial transactions may not be presented to the user immediately at the time of text capture. For example, the opportunity to purchase a sequel to a novel may not be available at the time the user is reading the novel, but the system may present them with that opportunity when the sequel is published.
A user may capture data that relates to a purchase or other commercial transaction, but may choose not to initiate and/or complete the transaction at the time the capture is made. In some embodiments, data related to captures is stored in a user's Life Library, and these Life Library entries can remain “active” (i.e., capable of subsequent interactions similar to those available at the time the capture was made). Thus a user may review a capture at some later time, and optionally complete a transaction based on that capture. Because the system can keep track of when and where the original capture occurred, all parties involved in the transaction can be properly compensated. For example, the author who wrote the story—and the publisher who published the story—that appeared next to the advertisement from which the user captured data can be compensated when, six months later, the user visits their Life Library, selects that particular capture from the history, and chooses “Purchase this item at Amazon” from the pop-up menu (which can be similar or identical to the menu optionally presented at the time of the capture).
11. Operating System and Application Integration
Modern Operating Systems (OSs) and other software packages have many characteristics that can be advantageously exploited for use with the described system, and may also be modified in various ways to provide an even better platform for its use.
11.1. Incorporation of Scan and Print-Related Information in Metadata and Indexing
New and upcoming file systems and their associated databases often have the ability to store a variety of metadata associated with each file. Traditionally, this metadata has included such things as the ID of the user who created the file, the dates of creation, last modification, and last use. Newer file systems allow such extra information as keywords, image characteristics, document sources and user comments to be stored, and in some systems this metadata can be arbitrarily extended. File systems can therefore be used to store information that would be useful in implementing the current system. For example, the date when a given document was last printed can be stored by the file system, as can details about which text from it has been captured from paper using the described system, and when and by whom.
Operating systems are also starting to incorporate search engine facilities that allow users to find local files more easily. These facilities can be advantageously used by the system. It means that many of the search-related concepts discussed in Sections 3 and 4 apply not just to today's Internet-based and similar search engines, but also to every personal computer.
In some cases specific software applications will also include support for the system above and beyond the facilities provided by the OS.
11.2. OS Support for Capture Devices
As the use of capture devices such as pen scanners becomes increasingly common, it will become desirable to build support for them into the operating system, in much the same way as support is provided for mice and printers, since the applicability of capture devices extends beyond a single software application. The same will be true for other aspects of the system's operation. Some examples are discussed below. In some embodiments, the entire described system, or the core of it, is provided by the OS. In some embodiments, support for the system is provided by Application Programming Interfaces (APIs) that can be used by other software packages, including those directly implementing aspects of the system.
11.2.1. Support for OCR and Other Recognition Technologies
Most of the methods of capturing text from a rendered document require some recognition software to interpret the source data, typically a scanned image or some spoken words, as text suitable for use in the system. Some OSs include support for speech or handwriting recognition, though it is less common for OSs to include support for OCR, since in the past the use of OCR has typically been limited to a small range of applications.
As recognition components become part of the OS, they can take better advantage of other facilities provided by the OS. Many systems include spelling dictionaries, grammar analysis tools, internationalization and localization facilities, for example, all of which can be advantageously employed by the described system for its recognition process, especially since they may have been customized for the particular user to include words and phrases that he/she would commonly encounter.
If the operating system includes full-text indexing facilities, then these can also be used to inform the recognition process, as described in Section 9.3.
11.2.2. Action to be Taken on Scans
If an optical scan or other capture occurs and is presented to the OS, it may have a default action to be taken under those circumstances in the event that no other subsystem claims ownership of the capture. An example of a default action is presenting the user with a choice of alternatives, or submitting the captured text to the OS's built-in search facilities.
11.2.3. OS has Default Action for Particular Documents or Document Types
If the digital source of the rendered document is found, the OS may have a standard action that it will take when that particular document, or a document of that class, is scanned. Applications and other subsystems may register with the OS as potential handlers of particular types of capture, in a similar manner to the announcement by applications of their ability to handle certain file types.
Markup data associated with a rendered document, or with a capture from a document, can include instructions to the operating system to launch specific applications, pass applications arguments, parameters, or data, etc. 11.2.4. Interpretation of Gestures and Mapping into Standard Actions
In Section 12.1.3 the use of “gestures” is discussed, particularly in the case of optical scanning, where particular movements made with a handheld scanner might represent standard actions such as marking the start and end of a region of text.
This is analogous to actions such as pressing the shift key on a keyboard while using the cursor keys to select a region of text, or using the wheel on a mouse to scroll a document. Such actions by the user are sufficiently standard that they are interpreted in a system-wide way by the OS, thus ensuring consistent behavior. The same is desirable for scanner gestures and other scanner-related actions.
11.2.5. Set Response to Standard (and Non-Standard) Iconic/Text Printed Menu Items
In a similar way, certain items of text or other symbols may, when scanned, cause standard actions to occur, and the OS may provide a selection of these. An example might be that scanning the text “[print]” in any document would cause the OS to retrieve and print a copy of that document. The OS may also provide a way to register such actions and associate them with particular scans.
11.3. Support in System GUI Components for Typical Scan-Initiated Activities
Most software applications are based substantially on standard Graphical User Interface components provided by the OS.
Use of these components by developers helps to ensure consistent behavior across multiple packages, for example that pressing the left-cursor key in any text-editing context should move the cursor to the left, without every programmer having to implement the same functionality independently.
A similar consistency in these components is desirable when the activities are initiated by text-capture or other aspects of the described system. Some examples are given below.
11.3.1. Interface to Find Particular Text Content
A typical use of the system may be for the user to scan an area of a paper document, and for the system to open the electronic counterpart in a software package that is able to display or edit it, and cause that package to scroll to and highlight the scanned text (Section 12.2.1). The first part of this process, finding and opening the electronic document, is typically provided by the OS and is standard across software packages. The second part, however—locating a particular piece of text within a document and causing the package to scroll to it and highlight it—is not yet standardized and is often implemented differently by each package. The availability of a standard API for this functionality could greatly enhance the operation of this aspect of the system.
11.3.2. Text Interactions
Once a piece of text has been located within a document, the system may wish to perform a variety of operations upon that text. As an example, the system may request the surrounding text, so that the user's capture of a few words could result in the system accessing the entire sentence or paragraph containing them. Again, this functionality can be usefully provided by the OS rather than being implemented in every piece of software that handles text.
11.3.3. Contextual (Popup) Menus
Some of the operations that are enabled by the system will require user feedback, and this may be optimally requested within the context of the application handling the data. In some embodiments, the system uses the application pop-up menus traditionally associated with clicking the right mouse button on some text. The system inserts extra options into such menus, and causes them to be displayed as a result of activities such as scanning a paper document.
11.4. Web/Network Interfaces
In today's increasingly networked world, much of the functionality available on individual machines can also be accessed over a network, and the functionality associated with the described system is no exception. As an example, in an office environment, many paper documents received by a user may have been printed by other users' machines on the same corporate network. The system on one computer, in response to a capture, may be able to query those other machines for documents which may correspond to that capture, subject to the appropriate permission controls.
11.5. Printing of Document Causes Saving
An important factor in the integration of paper and digital documents is maintaining as much information as possible about the transitions between the two. In some embodiments, the OS keeps a simple record of when any document was printed and by whom. In some embodiments, the OS takes one or more further actions that would make it better suited for use with the system. Examples include:
11.6. My (Printed/Scanned) Documents
An OS often maintains certain categories of folders or files that have particular significance. A user's documents may, by convention or design, be found in a “My Documents” folder, for example. Standard file-opening dialogs may automatically include a list of recently opened documents.
On an OS optimized for use with the described system, such categories may be enhanced or augmented in ways that take into account a user's interaction with paper versions of the stored files. Categories such as “My Printed Documents” or “My Recently-Read Documents” might usefully be identified and incorporated in its operations.
11.7. OS-Level Markup Hierarchies
Since important aspects of the system are typically provided using the “markup” concepts discussed in Section 5, it would clearly be advantageous to have support for such markup provided by the OS in a way that was accessible to multiple applications as well as to the OS itself. In addition, layers of markup may be provided by the OS, based on its own knowledge of documents under its control and the facilities it is able to provide.
11.8. Use of OS DRM Facilities
An increasing number of operating systems support some form of “Digital Rights Management”: the ability to control the use of particular data according to the rights granted to a particular user, software entity or machine. It may inhibit unauthorized copying or distribution of a particular document, for example.
12. User Interface
The user interface of the system may be entirely on a PC, if the capture device is relatively dumb and is connected to it by a cable, or entirely on the device, if it is sophisticated and with significant processing power of its own. In some cases, some functionality resides in each component. Part, or indeed all, of the system's functionality may also be implemented on other devices such as mobile phones or PDAs.
The descriptions in the following sections are therefore indications of what may be desirable in certain implementations, but they are not necessarily appropriate for all and may be modified in several ways.
12.1. On the Capture Device
With all capture devices, but particularly in the case of an optical scanner, the user's attention will generally be on the device and the paper at the time of scanning. It is very desirable, then, that any input and feedback needed as part of the process of scanning do not require the user's attention to be elsewhere, for example on the screen of a computer, more than is necessary.
12.1.1. Feedback on Scanner
A handheld scanner may have a variety of ways of providing feedback to the user about particular conditions. The most obvious types are direct visual, where the scanner incorporates indicator lights or even a full display, and auditory, where the scanner can make beeps, clicks or other sounds. Important alternatives include tactile feedback, where the scanner can vibrate, buzz, or otherwise stimulate the user's sense of touch, and projected feedback, where it indicates a status by projecting onto the paper anything from a colored spot of light to a sophisticated display.
Important immediate feedback that may be provided on the device includes:
Many of the user interactions normally associated with the later stages of the system may also take place on the capture device if it has sufficient abilities, for example, to display part or all of a document.
12.1.2. Controls on Scanner
The device may provide a variety of ways for the user to provide input in addition to basic text capture. Even when the device is in close association with a host machine that has input options such as keyboards and mice, it can be disruptive for the user to switch back and forth between manipulating the scanner and using a mouse, for example.
The handheld scanner may have buttons, scroll/jog-wheels, touch-sensitive surfaces, and/or accelerometers for detecting the movement of the device. Some of these allow a richer set of interactions while still holding the scanner.
For example, in response to scanning some text, the system presents the user with a set of several possible matching documents. The user uses a scroll-wheel on the side of the scanner is to select one from the list, and clicks a button to confirm the selection.
12.1.3. Gestures
The primary reason for moving a scanner across the paper is to capture text, but some movements may be detected by the device and used to indicate other user intentions. Such movements are referred to herein as “gestures.”
As an example, the user can indicate a large region of text by scanning the first few words in conventional left-to-right order, and the last few in reverse order, i.e. right to left. The user can also indicate the vertical extent of the text of interest by moving the scanner down the page over several lines. A backwards scan might indicate cancellation of the previous scan operation.
12.1.4. Online/Offline Behavior
Many aspects of the system may depend on network connectivity, either between components of the system such as a scanner and a host laptop, or with the outside world in the form of a connection to corporate databases and Internet search. This connectivity may not be present all the time, however, and so there will be occasions when part or all of the system may be considered to be “offline.” It is desirable to allow the system to continue to function usefully in those circumstances.
The device may be used to capture text when it is out of contact with other parts of the system. A very simple device may simply be able to store the image or audio data associated with the capture, ideally with a timestamp indicating when it was captured. The various captures may be uploaded to the rest of the system when the device is next in contact with it, and handled then. The device may also upload other data associated with the captures, for example voice annotations associated with optical scans, or location information.
More sophisticated devices may be able to perform some or all of the system operations themselves despite being disconnected. Various techniques for improving their ability to do so are discussed in Section 15.3. Often it will be the case that some, but not all, of the desired actions can be performed while offline. For example, the text may be recognized, but identification of the source may depend on a connection to an Internet-based search engine. In some embodiments, the device therefore stores sufficient information about how far each operation has progressed for the rest of the system to proceed efficiently when connectivity is restored.
The operation of the system will, in general, benefit from immediately available connectivity, but there are some situations in which performing several captures and then processing them as a batch can have advantages. For example, as discussed in Section 13 below, the identification of the source of a particular capture may be greatly enhanced by examining other captures made by the user at approximately the same time. In a fully connected system where live feedback is being provided to the user, the system is only able to use past captures when processing the current one. If the capture is one of a batch stored by the device when offline, however, the system will be able to take into account any data available from later captures as well as earlier ones when doing its analysis.
12.2. On a Host Device
A scanner will often communicate with some other device, such as a PC, PDA, phone or digital camera to perform many of the functions of the system, including more detailed interactions with the user.
12.2.1. Activities Performed in Response to a Capture
When the host device receives a capture, it may initiate a variety of activities. An incomplete list of possible activities performed by the system after locating and electronic counterpart document associated with the capture and a location within that document follows.
12.2.2. Contextual Popup Menus
Sometimes the appropriate action to be taken by the system will be obvious, but sometimes it will require a choice to be made by the user. One good way to do this is through the use of “popup menus” or, in cases where the content is also being displayed on a screen, with so-called “contextual menus” that appear close to the content. (See Section 11.3.3). In some embodiments, the scanner device projects a popup menu onto the paper document. A user may select from such menus using traditional methods such as a keyboard and mouse, or by using controls on the capture device (Section 12.1.2), gestures (Section 12.1.3), or by interacting with the computer display using the scanner (Section 12.2.4). In some embodiments, the popup menus which can appear as a result of a capture include default items representing actions which occur if the user does not respond—for example, if the user ignores the menu and makes another capture.
12.2.3. Feedback on Disambiguation
When a user starts capturing text, there will initially be several documents or other text locations that it could match. As more text is captured, and other factors are taken into account (Section 13), the number of candidate locations will decrease until the actual location is identified, or further disambiguation is not possible without user input. In some embodiments, the system provides a real-time display of the documents or the locations found, for example in list, thumbnail-image or text-segment form, and for the number of elements in that display to reduce in number as capture continues. In some embodiments, the system displays thumbnails of all candidate documents, where the size or position of the thumbnail is dependent on the probability of it being the correct match.
When a capture is unambiguously identified, this fact may be emphasized to the user, for example using audio feedback.
Sometimes the text captured will occur in many documents and will be recognized to be a quotation. The system may indicate this on the screen, for example by grouping documents containing a quoted reference around the original source document.
12.2.4. Scanning from Screen
Some optical scanners may be able to capture text displayed on a screen as well as on paper. Accordingly, the term rendered document is used herein to indicate that printing onto paper is not the only form of rendering, and that the capture of text or symbols for use by the system may be equally valuable when that text is displayed on an electronic display.
The user of the described system may be required to interact with a computer screen for a variety of other reasons, such as to select from a list of options. It can be inconvenient for the user to put down the scanner and start using the mouse or keyboard. Other sections have described physical controls on the scanner (Section 12.1.2) or gestures (Section 12.1.3) as methods of input which do not require this change of tool, but using the scanner on the screen itself to scan some text or symbol is an important alternative provided by the system.
In some embodiments, the optics of the scanner allow it to be used in a similar manner to a light-pen, directly sensing its position on the screen without the need for actual scanning of text, possibly with the aid of special hardware or software on the computer.
13. Context Interpretation
An important aspect of the described system is the use of other factors, beyond the simple capture of a string of text, to help identify the document in use. A capture of a modest amount of text may often identify the document uniquely, but in many situations it will identify a few candidate documents. One solution is to prompt the user to confirm the document being scanned, but a preferable alternative is to make use of other factors to narrow down the possibilities automatically. Such supplemental information can dramatically reduce the amount of text that needs to be captured and/or increase the reliability and speed with which the location in the electronic counterpart can be identified. This extra material is referred to as “context,” and it was discussed briefly in Section 4.2.2. We now consider it in more depth.
13.1. System and Capture Context
Perhaps the most important example of such information is the user's capture history.
It is highly probable that any given capture comes from the same document as the previous one, or from an associated document, especially if the previous capture took place in the last few minutes (Section 6.1.2). Conversely, if the system detects that the font has changed between two scans, it is more likely that they are from different documents.
Also useful are the user's longer-term capture history and reading habits. These can also be used to develop a model of the user's interests and associations.
13.2. User's Real-world Context
Another example of useful context is the user's geographical location. A user in Paris is much more likely to be reading Le Monde than the Seattle Times, for example. The timing, size and geographical distribution of printed versions of the documents can therefore be important, and can to some degree be deduced from the operation of the system.
The time of day may also be relevant, for example in the case of a user who always reads one type of publication on the way to work, and a different one at lunchtime or on the train going home.
13.3. Related Digital Context
The user's recent use of electronic documents, including those searched for or retrieved by more conventional means, can also be a helpful indicator.
In some cases, such as on a corporate network, other factors may be usefully considered:
All of these examples might suggest that a user was more likely to be reading a paper version of those documents. In contrast, if the repository in which a document resides can affirm that the document has never been printed or sent anywhere where it might have been printed, then it can be safely eliminated in any searches originating from paper.
13.4. Other Statistics—the Global Context
Section 14 covers the analysis of the data stream resulting from paper-based searches, but it should be noted here that statistics about the popularity of documents with other readers, about the timing of that popularity, and about the parts of documents most frequently scanned are all examples of further factors which can be beneficial in the search process. The system brings the possibility of Google-type page-ranking to the world of paper.
See also Section 4.2.2 for some other implications of the use of context for search engines.
14. Data-Stream Analysis
The use of the system generates an exceedingly valuable data-stream as a side effect. This stream is a record of what users are reading and when, and is in many cases a record of what they find particularly valuable in the things they read. Such data has never really been available before for paper documents.
Some ways in which this data can be useful for the system, and for the user of the system, are described in Section 6.1. This section concentrates on its use for others. There are, of course, substantial privacy issues to be considered with any distribution of data about what people are reading, but such issues as preserving the anonymity of data are well known to those of skill in the art.
14.1. Document Tracking
When the system knows which documents any given user is reading, it can also deduce who is reading any given document. This allows the tracking of a document through an organization, to allow analysis, for example, of who is reading it and when, how widely it was distributed, how long that distribution took, and who has seen current versions while others are still working from out-of-date copies.
For published documents that have a wider distribution, the tracking of individual copies is more difficult, but the analysis of the distribution of readership is still possible.
14.2. Read Ranking—Popularity of Documents and Sub-regions
In situations where users are capturing text or other data that is of particular interest to them, the system can deduce the popularity of certain documents and of particular sub-regions of those documents. This forms a valuable input to the system itself (Section 4.2.2) and an important source of information for authors, publishers and advertisers (Section 7.6, Section 10.5). This data is also useful when integrated in search engines and search indices—for example, to assist in ranking search results for queries coming from rendered documents, and/or to assist in ranking conventional queries typed into a web browser.
14.3. Analysis of Users—Building Profiles
Knowledge of what a user is reading enables the system to create a quite detailed model of the user's interests and activities. This can be useful on an abstract statistical basis—“35% of users who buy this newspaper also read the latest book by that author”—but it can also allow other interactions with the individual user, as discussed below.
14.3.1. Social Networking
One example is connecting one user with others who have related interests. These may be people already known to the user. The system may ask a university professor, “Did you know that your colleague at XYZ University has also just read this paper?” The system may ask a user, “Do you want to be linked up with other people in your neighborhood who are also how reading Jane Eyre?” Such links may be the basis for the automatic formation of book clubs and similar social structures, either in the physical world or online.
14.3.2. Marketing
Section 10.6 has already mentioned the idea of offering products and services to an individual user based on their interactions with the system. Current online booksellers, for example, often make recommendations to a user based on their previous interactions with the bookseller. Such recommendations become much more useful when they are based on interactions with the actual books.
14.4. Marketing Based on Other Aspects of the Data-Stream
We have discussed some of the ways in which the system may influence those publishing documents, those advertising through them, and other sales initiated from paper (Section 10). Some commercial activities may have no direct interaction with the paper documents at all and yet may be influenced by them. For example, the knowledge that people in one community spend more time reading the sports section of the newspaper than they do the financial section might be of interest to somebody setting up a health club. p 14.5. Types of Data that may be Captured
In addition to the statistics discussed, such as who is reading which bits of which documents, and when and where, it can be of interest to examine the actual contents of the text captured, regardless of whether or not the document has been located.
In many situations, the user will also not just be capturing some text, but will be causing some action to occur as a result. It might be emailing a reference to the document to an acquaintance, for example. Even in the absence of information about the identity of the user or the recipient of the email, the knowledge that somebody considered the document worth emailing is very useful.
In addition to the various methods discussed for deducing the value of a particular document or piece of text, in some circumstances the user will explicitly indicate the value by assigning it a rating.
Lastly, when a particular set of users are known to form a group, for example when they are known to be employees of a particular company, the aggregated statistics of that group can be used to deduce the importance of a particular document to that group.
15. Device Features and Functions
A capture device for use with the system needs little more than a way of capturing text from a rendered version of the document. As described earlier (Section 1.2), this capture may be achieved through a variety of methods including taking a photograph of part of the document or typing some words into a mobile phone keypad. This capture may be achieved using a small hand-held optical scanner capable of recording a line or two of text at a time, or an audio capture device such as a voice-recorder into which the user is reading text from the document. The device used may be a combination of these—an optical scanner which could also record voice annotations, for example—and the capturing functionality may be built into some other device such as a mobile phone, PDA, digital camera or portable music player.
15.1. Input and Output
Many of the possibly beneficial additional input and output facilities for such a device have been described in Section 12.1. They include buttons, scroll-wheels and touch-pads for input, and displays, indicator lights, audio and tactile transducers for output. Sometimes the device will incorporate many of these, sometimes very few. Sometimes the capture device will be able to communicate with another device that already has them (Section 15.6), for example using a wireless link, and sometimes the capture functionality will be incorporated into such other device (Section 15.7).
15.2. Connectivity
In some embodiments, the device implements the majority of the system itself. In some embodiments, however, it often communicates with a PC or other computing device and with the wider world using communications facilities.
Often these communications facilities are in the form of a general-purpose data network such as Ethernet, 802.11 or UWB or a standard peripheral-connecting network such as USB, IEEE-1394 (Firewire), Bluetooth™ or infra-red. When a wired connection such as Firewire or USB is used, the device may receive electrical power though the same connection. In some circumstances, the capture device may appear to a connected machine to be a conventional peripheral such as a USB storage device.
Lastly, the device may in some circumstances “dock” with another device, either to be used in conjunction with that device or for convenient storage.
15.3. Caching and Other Online/Offline Functionality
Sections 3.5 and 12.1.4 have raised the topic of disconnected operation. When a capture device has a limited subset of the total system's functionality, and is not in communication with the other parts of the system, the device can still be useful, though the functionality available will sometimes be reduced. At the simplest level, the device can record the raw image or audio data being captured and this can be processed later. For the user's benefit, however, it can be important to give feedback where possible about whether the data captured is likely to be sufficient for the task in hand, whether it can be recognized or is likely to be recognizable, and whether the source of the data can be identified or is likely to be identifiable later. The user will then know whether their capturing activity is worthwhile. Even when all of the above are unknown, the raw data can still be stored so that, at the very least, the user can refer to them later. The user may be presented with the image of a scan, for example, when the scan cannot be recognized by the OCR process.
To illustrate some of the range of options available, both a rather minimal optical scanning device and then a much more full-featured one are described below. Many devices occupy a middle ground between the two.
15.3.1. The SimpleScanner—a Low-End Offline Example
The SimpleScanner has a scanning head able to read pixels from the page as it is moved along the length of a line of text. It can detect its movement along the page and record the pixels with some information about the movement. It also has a clock, which allows each scan to be time-stamped. The clock is synchronized with a host device when the SimpleScanner has connectivity. The clock may not represent the actual time of day, but relative times may be determined from it so that the host can deduce the actual time of a scan, or at worst the elapsed time between scans.
The SimpleScanner does not have sufficient processing power to perform any OCR itself, but it does have some basic knowledge about typical word-lengths, word-spacings, and their relationship to font size. It has some basic indicator lights which tell the user whether the scan is likely to be readable, whether the head is being moved too fast, too slowly or too inaccurately across the paper, and when it determines that sufficient words of a given size are likely to have been scanned for the document to be identified.
The SimpleScanner has a USB connector and can be plugged into the USB port on a computer, where it will be recharged. To the computer it appears to be a USB storage device on which time-stamped data files have been recorded, and the rest of the system software takes over from this point.
15.3.2. The SuperScanner—a High-End Offline Example
The SuperScanner also depends on connectivity for its full operation, but it has a significant amount of on-board storage and processing which can help it make better judgments about the data captured while offline.
As it moves along the line of text, the captured pixels are stitched together and passed to an OCR engine that attempts to recognize the text. A number of fonts, including those from the user's most-read publications, have been downloaded to it to help perform this task, as has a dictionary that is synchronized with the user's spelling-checker dictionary on their PC and so contains many of the words they frequently encounter. Also stored on the scanner is a list of words and phrases with the typical frequency of their use—this may be combined with the dictionary. The scanner can use the frequency statistics both to help with the recognition process and also to inform its judgment about when a sufficient quantity of text has been captured; more frequently used phrases are less likely to be useful as the basis for a search query.
In addition, the full index for the articles in the recent issues of the newspapers and periodicals most commonly read by the user are stored on the device, as are the indices for the books the user has recently purchased from an online bookseller, or from which the user has scanned anything within the last few months. Lastly, the titles of several thousand of the most popular publications which have data available for the system are stored so that, in the absence of other information the user can scan the title and have a good idea as to whether or not captures from a particular work are likely to be retrievable in electronic form later.
During the scanning process, the system informs user that the captured data has been of sufficient quality and of a sufficient nature to make it probable that the electronic copy can be retrieved when connectivity is restored. Often the system indicates to the user that the scan is known to have been successful and that the context has been recognized in one of the on-board indices, or that the publication concerned is known to be making its data available to the system, so the later retrieval ought to be successful.
The SuperScanner docks in a cradle connected to a PC's Firewire or USB port, at which point, in addition to the upload of captured data, its various onboard indices and other databases are updated based on recent user activity and new publications. It also has the facility to connect to wireless public networks or to communicate via Bluetooth to a mobile phone and thence with the public network when such facilities are available.
15.4. Features for Optical Scanning
We now consider some of the features that may be particularly desirable in an optical scanner device.
15.4.1. Flexible Positioning and Convenient Optics
One of the reasons for the continuing popularity of paper is the ease of its use in a wide variety of situations where a computer, for example, would be impractical or inconvenient. A device intended to capture a substantial part of a user's interaction with paper should therefore be similarly convenient in use. This has not been the case for scanners in the past; even the smallest hand-held devices have been somewhat unwieldy. Those designed to be in contact with the page have to be held at a precise angle to the paper and moved very carefully along the length of the text to be scanned. This is acceptable when scanning a business report on an office desk, but may be impractical when scanning a phrase from a novel while waiting for a train. Scanners based on camera-type optics that operate at a distance from the paper may similarly be useful in some circumstances.
Some embodiments of the system use a scanner that scans in contact with the paper, and which, instead of lenses, uses an image conduit a bundle of optical fibers to transmit the image from the page to the optical sensor device. Such a device can be shaped to allow it to be held in a natural position; for example, in some embodiments, the part in contact with the page is wedge-shaped, allowing the user's hand to move more naturally over the page in a movement similar to the use of a highlighter pen. The conduit is either in direct contact with the paper or in close proximity to it, and may have a replaceable transparent tip that can protect the image conduit from possible damage. As has been mentioned in Section 12.2.4, the scanner may be used to scan from a screen as well as from paper, and the material of the tip can be chosen to reduce the likelihood of damage to such displays.
Lastly, some embodiments of the device will provide feedback to the user during the scanning process which will indicate through the use of light, sound or tactile feedback when the user is scanning too fast, too slow, too unevenly or is drifting too high or low on the scanned line.
15.5. Security, Identity, Authentication, Personalization and Billing
As described in Section 6, the capture device may form an important part of identification and authorization for secure transactions, purchases, and a variety of other operations. It may therefore incorporate, in addition to the circuitry and software required for such a role, various hardware features that can make it more secure, such as a smartcard reader, RFID, or a keypad on which to type a PIN.
It may also include various biometric sensors to help identify the user. In the case of an optical scanner, for example, the scanning head may also be able to read a fingerprint. For a voice recorder, the voice pattern of the user may be used.
15.6. Device Associations
In some embodiments, the device is able to form an association with other nearby devices to increase either its own or their functionality. In some embodiments, for example, it uses the display of a nearby PC or phone to give more detailed feedback about its operation, or uses their network connectivity. The device may, on the other hand, operate in its role as a security and identification device to authenticate operations performed by the other device. Or it may simply form an association in order to function as a peripheral to that device.
An interesting aspect of such associations is that they may be initiated and authenticated using the capture facilities of the device. For example, a user wishing to identify themselves securely to a public computer terminal may use the scanning facilities of the device to scan a code or symbol displayed on a particular area of the terminal's screen and so effect a key transfer. An analogous process may be performed using audio signals picked up by a voice-recording device.
15.7. Integration with Other Devices
In some embodiments, the functionality of the capture device is integrated into some other device that is already in use. The integrated devices may be able to share a power supply, data capture and storage capabilities, and network interfaces. Such integration may be done simply for convenience, to reduce cost, or to enable functionality that would not otherwise be available.
Some examples of devices into which the capture functionality can be integrated include:
15.7.1. Mobile Phone Integration
As an example of the benefits of integration, we consider the use of a modified mobile phone as the capture device.
In some embodiments, the phone hardware is not modified to support the system, such as where the text capture can be adequately done through voice recognition, where they can either be processed by the phone itself, or handled by a system at the other end of a telephone call, or stored in the phone's memory for future processing. Many modern phones have the ability to download software that could implement some parts of the system. Such voice capture is likely to be suboptimal in many situations, however, for example when there is substantial background noise, and accurate voice recognition is a difficult task at the best of times. The audio facilities may best be used to capture voice annotations.
In some embodiments, the camera built into many mobile phones is used to capture an image of the text. The phone display, which would normally act as a viewfinder for the camera, may overlay on the live camera image information about the quality of the image and its suitability for OCR, which segments of text are being captured, and even a transcription of the text if the OCR can be performed on the phone.
In some embodiments, the phone is modified to add dedicated capture facilities, or to provide such functionality in a clip-on adaptor or a separate Bluetooth-connected peripheral in communication with the phone. Whatever the nature of the capture mechanism, the integration with a modern cellphone has many other advantages. The phone has connectivity with the wider world, which means that queries can be submitted to remote search engines or other parts of the system, and copies of documents may be retrieved for immediate storage or viewing. A phone typically has sufficient processing power for many of the functions of the system to be performed locally, and sufficient storage to capture a reasonable amount of data. The amount of storage can also often be expanded by the user. Phones have reasonably good displays and audio facilities to provide user feedback, and often a vibrate function for tactile feedback. They also have good power supplies.
Most significantly of all, they are a device that most users are already carrying.
Part III—Example Applications of the System
This section lists example uses of the system and applications that may be built on it. This list is intended to be purely illustrative and in no sense exhaustive.
16. Personal Applications
16.1. Life Library
The Life Library (see also Section 6.1.1) is a digital archive of any important documents that the subscriber wishes to save and is a set of embodiments of services of this system. Important books, magazine articles, newspaper clippings, etc., can all be saved in digital form in the Life Library. Additionally, the subscriber's annotations, comments, and notes can be saved with the documents. The Life Library can be accessed via the Internet and World Wide Web.
The system creates and manages the Life Library document archive for subscribers. The subscriber indicates which documents the subscriber wishes to have saved in his life library by scanning information from the document or by otherwise indicating to the system that the particular document is to be added to the subscriber's Life Library. The scanned information is typically text from the document but can also be a barcode or other code identifying the document. The system accepts the code and uses it to identify the source document. After the document is identified the system can store either a copy of the document in the user's Life Library or a link to a source where the document may be obtained.
One embodiment of the Life Library system can check whether the subscriber is authorized to obtain the electronic copy. For example, if a reader scans text or an identifier from a copy of an article in the New York Times (NYT) so that the article will be added to the reader's Life Library, the Life Library system will verify with the NYT whether the reader is subscribed to the online version of the NYT; if so, the reader gets a copy of the article stored in his Life Library account; if not, information identifying the document and how to order it is stored in his Life Library account.
In some embodiments, the system maintains a subscriber profile for each subscriber that includes access privilege information. Document access information can be compiled in several ways, two of which are: 1) the subscriber supplies the document access information to the Life Library system, along with his account names and passwords, etc., or 2) the Life Library service provider queries the publisher with the subscriber's information and the publisher responds by providing access to an electronic copy if the Life Library subscriber is authorized to access the material. If the Life Library subscriber is not authorized to have an electronic copy of the document, the publisher provides a price to the Life Library service provider, which then provides the customer with the option to purchase the electronic document. If so, the Life Library service provider either pays the publisher directly and bills the Life Library customer later or the Life Library service provider immediately bills the customer's credit card for the purchase. The Life Library service provider would get a percentage of the purchase price or a small fixed fee for facilitating the transaction.
The system can archive the document in the subscriber's personal library and/or any other library to which the subscriber has archival privileges. For example, as a user scans text from a printed document, the Life Library system can identify the rendered document and its electronic counterpart. After the source document is identified, the Life Library system might record information about the source document in the user's personal library and in a group library to which the subscriber has archival privileges. Group libraries are collaborative archives such as a document repository for: a group working together on a project, a group of academic researchers, a group web log, etc.
The life library can be organized in many ways: chronologically, by topic, by level of the subscriber's interest, by type of publication (newspaper, book, magazine, technical paper, etc.), where read, when read, by ISBN or by Dewey decimal, etc. In one alternative, the system can learn classifications based on how other subscribers have classified the same document. The system can suggest classifications to the user or automatically classify the document for the user.
In various embodiments, annotations may be inserted directly into the document or may be maintained in a separate file. For example, when a subscriber scans text from a newspaper article, the article is archived in his Life Library with the scanned text highlighted. Alternatively, the article is archived in his Life Library along with an associated annotation file (thus leaving the archived document unmodified). Embodiments of the system can keep a copy of the source document in each subscriber's library, a copy in a master library that many subscribers can access, or link to a copy held by the publisher.
In some embodiments, the Life Library stores only the user's modifications to the document (e.g., highlights, etc.) and a link to an online version of the document (stored elsewhere). The system or the subscriber merges the changes with the document when the subscriber subsequently retrieves the document.
If the annotations are kept in a separate file, the source document and the annotation file are provided to the subscriber and the subscriber combines them to create a modified document. Alternatively, the system combines the two files prior to presenting them to the subscriber. In another alternative, the annotation file is an overlay to the document file and can be overlaid on the document by software in the subscriber's computer.
Subscribers to the Life Library service pay a monthly fee to have the system maintain the subscriber's archive. Alternatively, the subscriber pays a small amount (e.g., a micro-payment) for each document stored in the archive. Alternatively, the subscriber pays to access the subscriber's archive on a per-access fee. Alternatively, subscribers can compile libraries and allow others to access the materials/annotations on a revenue share model with the Life Library service provider and copyright holders. Alternatively, the Life Library service provider receives a payment from the publisher when the Life Library subscriber orders a document (a revenue share model with the publisher, where the Life Library service provider gets a share of the publisher's revenue).
In some embodiments, the Life Library service provider acts as an intermediary between the subscriber and the copyright holder (or copyright holder's agent, such as the Copyright Clearance Center, a.k.a. CCC) to facilitate billing and payment for copyrighted materials. The Life Library service provider uses the subscriber's billing information and other user account information to provide this intermediation service. Essentially, the Life Library service provider leverages the pre-existing relationship with the subscriber to enable purchase of copyrighted materials on behalf of the subscriber.
In some embodiments, the Life Library system can store excerpts from documents. For example, when a subscriber scans text from a paper document, the regions around the scanned text are excerpted and placed in the Life Library, rather than the entire document being archived in the life library. This is especially advantageous when the document is long because preserving the circumstances of the original scan prevents the subscriber from re-reading the document to find the interesting portions. Of course, a hyperlink to the entire electronic counterpart of the paper document can be included with the excerpt materials.
In some embodiments, the system also stores information about the document in the Life Library, such as author, publication title, publication date, publisher, copyright holder (or copyright holder's licensing agent), ISBN, links to public annotations of the document, readrank, etc. Some of this additional information about the document is a form of paper document metadata. Third parties may create public annotation files for access by persons other than themselves, such the general public. Linking to a third party's commentary on a document is advantageous because reading annotation files of other users enhances the subscriber's understanding of the document.
In some embodiments, the system archives materials by class. This feature allows a Life Library subscriber to quickly store electronic counterparts to an entire class of paper documents without access to each paper document. For example, when the subscriber scans some text from a copy of National Geographic magazine, the system provides the subscriber with the option to archive all back issues of the National Geographic. If the subscriber elects to archive all back issues, the Life Library service provider would then verify with the National Geographic Society whether the subscriber is authorized to do so. If not, the Life Library service provider can mediate the purchase of the right to archive the National Geographic magazine collection.
16.2. Life Saver
A variation on, or enhancement of, the Life Library concept is the “Life Saver,” where the system uses the text captured by a user to deduce more about their other activities. The scanning of a menu from a particular restaurant, a program from a particular theater performance, a timetable at a particular railway station, or an article from a local newspaper allows the system to make deductions about the user's location and social activities, and could construct an automatic diary for them, for example as a website. The user would be able to edit and modify the diary, add additional materials such as photographs and, of course, look again at the items scanned.
17. Academic Applications
Portable scanners supported by the described system have many compelling uses in the academic setting. They can enhance student/teacher interaction and augment the learning experience. Among other uses, students can annotate study materials to suit their unique needs; teachers can monitor classroom performance; and teachers can automatically verify source materials cited in student assignments.
17.1. Children's Books
A child's interaction with a paper document, such as a book, is monitored by a literacy acquisition system that employs a specific set of embodiments of this system. The child uses a portable scanner that communicates with other elements of the literacy acquisition system. In addition to the portable scanner, the literacy acquisition system includes a computer having a display and speakers, and a database accessible by the computer. The scanner is coupled with the computer (hardwired, short range RF, etc.). When the child sees an unknown word in the book, the child scans it with the scanner. In one embodiment, the literacy acquisition system compares the scanned text with the resources in its database to identify the word. The database includes a dictionary, thesaurus, and/or multimedia files (e.g., sound, graphics, etc.). After the word has been identified, the system uses the computer speakers to pronounce the word and its definition to the child. In another embodiment, the word and its definition are displayed by the literacy acquisition system on the computer's monitor. Multimedia files about the scanned word can also be played through the computer's monitor and speakers. For example, if a child reading “Goldilocks and the Three Bears” scanned the word “bear,” the system might pronounce the word “bear” and play a short video about bears on the computer's monitor. In this way, the child learns to pronounce the written word and is visually taught what the word means via the multimedia presentation.
The literacy acquisition system provides immediate auditory and/or visual information to enhance the learning process. The child uses this supplementary information to quickly acquire a deeper understanding of the written material. The system can be used to teach beginning readers to read, to help children acquire a larger vocabulary, etc. This system provides the child with information about words with which the child is unfamiliar or about which the child wants more information.
17.2. Literacy Acquisition
In some embodiments, the system compiles personal dictionaries. If the reader sees a word that is new, interesting, or particularly useful or troublesome, the reader saves it (along with its definition) to a computer file. This computer file becomes the reader's personalized dictionary. This dictionary is generally smaller in size than a general dictionary so can be downloaded to a mobile station or associated device and thus be available even when the system isn't immediately accessible. In some embodiments, the personal dictionary entries include audio files to assist with proper word pronunciation and information identifying the paper document from which the word was scanned.
In some embodiments, the system creates customized spelling and vocabulary tests for students. For example, as a student reads an assignment, the student may scan unfamiliar words with the portable scanner. The system stores a list of all the words that the student has scanned. Later, the system administers a customized spelling/vocabulary test to the student on an associated monitor (or prints such a test on an associated printer).
17.3. Music Teaching
The arrangement of notes on a musical staff is similar to the arrangement of letters in a line of text. The same scanning device discussed for capturing text in this system can be used to capture music notation, and an analogous process of constructing a search against databases of known musical pieces would allow the piece from which the capture occurred to be identified which can then be retrieved, played, or be the basis for some further action.
17.4. Detecting Plagiarism
Teachers can use the system to detect plagiarism or to verify sources by scanning text from student papers and submitting the scanned text to the system. For example, a teacher who wishes to verify that a quote in a student paper came from the source that the student cited can scan a portion of the quote and compare the title of the document identified by the system with the title of the document cited by the student. Likewise, the system can use scans of text from assignments submitted as the student's original work to reveal if the text was instead copied.
17.5. Enhanced Textbook
In some embodiments, capturing text from an academic textbook links students or staff to more detailed explanations, further exercises, student and staff discussions about the material, related example past exam questions, further reading on the subject, recordings of the lectures on the subject, and so forth. (See also Section 7.1.)
17.6. Language Learning
In some embodiments, the system is used to teach foreign languages. Scanning a Spanish word, for example, might cause the word to be read aloud in Spanish along with its definition in English.
The system provides immediate auditory and/or visual information to enhance the new language acquisition process. The reader uses this supplementary information to acquire quickly a deeper understanding of the material. The system can be used to teach beginning students to read foreign languages, to help students acquire a larger vocabulary, etc. The system provides information about foreign words with which the reader is unfamiliar or for which the reader wants more information.
Reader interaction with a paper document, such as a newspaper or book, is monitored by a language skills system. The reader has a portable scanner that communicates with the language skills system. In some embodiments, the language skills system includes a computer having a display and speakers, and a database accessible by the computer. The scanner communicates with the computer (hardwired, short range RF, etc.). When the reader sees an unknown word in an article, the reader scans it with the scanner. The database includes a foreign language dictionary, thesaurus, and/or multimedia files (sound, graphics, etc.). In one embodiment, the system compares the scanned text with the resources in its database to identify the scanned word. After the word has been identified, the system uses the computer speakers to pronounce the word and its definition to the reader. In some embodiments, the word and its definition are both displayed on the computer's monitor. Multimedia files about grammar tips related to the scanned word can also be played through the computer's monitor and speakers. For example, if the words “to speak” are scanned, the system might pronounce the word “hablar,” play a short audio clip that demonstrates the proper Spanish pronunciation, and display a complete list of the various conjugations of “hablar.” In this way, the student learns to pronounce the written word, is visually taught the spelling of the word via the multimedia presentation, and learns how to conjugate the verb. The system can also present grammar tips about the proper usage of “hablar” along with common phrases.
In some embodiments, the user scans a word or short phrase from a rendered document in a language other than the user's native language (or some other language that the user knows reasonably well). In some embodiments, the system maintains a prioritized list of the user's “preferred⇄ languages. The system identifies the electronic counterpart of the rendered document, and determines the location of the scan within the document. The system also identifies a second electronic counterpart of the document that has been translated into one of the user's preferred languages, and determines the location in the translated document corresponding to the location of the scan in the original document. When the corresponding location is not known precisely, the system identifies a small region (e.g., a paragraph) that includes the corresponding location of the scanned location. The corresponding translated location is then presented to the user. This provides the user with a precise translation of the particular usage at the scanned location, including any slang or other idiomatic usage that is often difficult to accurately translate on a word-by-word basis.
17.7. Gathering Research Materials
A user researching a particular topic may encounter all sorts of material, both in print and on screen, which they might wish to record as relevant to the topic in some personal archive. The system would enable this process to be automatic as a result of scanning a short phrase in any piece of material, and could also create a bibliography suitable for insertion into a publication on the subject.
18. Commercial Applications
Obviously, commercial activities could be made out of almost any process discussed in this document, but here we concentrate on a few obvious revenue streams.
18.1. Fee-based Searching and Indexing
Conventional Internet search engines typically provide free search of electronic documents, and also make no charge to the content providers for including their content in the index. In some embodiments, the system provides for charges to users and/or payments to search engines and/or content providers in connection with the operation and use of the system.
In some embodiments, subscribers to the system's services pay a fee for searches originating from scans of paper documents. For example, a stockbroker may be reading a Wall Street Journal article about a new product offered by Company X. By scanning the Company X name from the paper document and agreeing to pay the necessary fees, the stockbroker uses the system to search special or proprietary databases to obtain premium information about the company, such as analyst's reports. The system can also make arrangements to have priority indexing of the documents most likely to be read in paper form, for example by making sure all of the newspapers published on a particular day are indexed and available by the time they hit the streets.
Content providers may pay a fee to be associated with certain terms in search queries submitted from paper documents. For example, in one embodiment, the system chooses a most preferred content provider based on additional context about the provider (the context being, in this case, that the content provider has paid a fee to be moved up the results list). In essence, the search provider is adjusting paper document search results based on pre-existing financial arrangements with a content provider. See also the description of keywords and key phrases in Section 5.2.
Where access to particular content is to be restricted to certain groups of people (such as clients or employees), such content may be protected by a firewall and thus not generally indexable by third parties. The content provider may nonetheless wish to provide an index to the protected content. In such a case, the content provider can pay a service provider to provide the content provider's index to system subscribers. For example, a law firm may index all of a client's documents. The documents are stored behind the law firm's firewall. However, the law firm wants its employees and the client to have access to the documents through the portable scanner so it provides the index (or a pointer to the index) to the service provider, which in turn searches the law firm's index when employees or clients of the law firm submit paper-scanned search terms via their portable scanners. The law firm can provide a list of employees and/or clients to the service provider's system to enable this function or the system can verify access rights by querying the law firm prior to searching the law firm's index. Note that in the preceding example, the index provided by the law firm is only of that client's documents, not an index of all documents at the law firm. Thus, the service provider can only grant the law firm's clients access to the documents that the law firm indexed for the client.
There are at least two separate revenue streams that can result from searches originating from paper documents: one revenue stream from the search function, and another from the content delivery function. The search function revenue can be generated from paid subscriptions from the scanner users, but can also be generated on a per-search charge. The content delivery revenue can be shared with the content provider or copyright holder (the service provider can take a percentage of the sale or a fixed fee, such as a micropayment, for each delivery), but also can be generated by a “referral” model in which the system gets a fee or percentage for every item that the subscriber orders from the online catalog and that the system has delivered or contributed to, regardless of whether the service provider intermediates the transaction. In some embodiments, the system service provider receives revenue for all purchases that the subscriber made from the content provider, either for some predetermined period of time or at any subsequent time when a purchase of an identified product is made.
18.2. Catalogs
Consumers may use the portable scanner to make purchases from paper catalogs. The subscriber scans information from the catalog that identifies the catalog. This information is text from the catalog, a bar code, or another identifier of the catalog. The subscriber scans information identifying the products that s/he wishes to purchase. The catalog mailing label may contain a customer identification number that identifies the customer to the catalog vendor. If so, the subscriber can also scan this customer identification number. The system acts as an intermediary between the subscriber and the vendor to facilitate the catalog purchase by providing the customer's selection and customer identification number to the vendor.
18.3. Coupons
A consumer scans paper coupons and saves an electronic copy of the coupon in the scanner, or in a remote device such as a computer, for later retrieval and use. An advantage of electronic storage is that the consumer is freed from the burden of carrying paper coupons. A further advantage is that the electronic coupons may be retrieved from any location. In some embodiments, the system can track coupon expiration dates, alert the consumer about coupons that will expire soon, and/or delete expired coupons from storage. An advantage for the issuer of the coupons is the possibility of receiving more feedback about who is using the coupons and when and where they are captured and used.
19. General Applications
19.1. Forms
The system may be used to auto-populate an electronic document that corresponds to a paper form. A user scans in some text or a barcode that uniquely identifies the paper form. The scanner communicates the identity of the form and information identifying the user to a nearby computer. The nearby computer has an Internet connection. The nearby computer can access a first database of forms and a second database having information about the user of the scanner (such as a service provider's subscriber information database). The nearby computer accesses an electronic version of the paper form from the first database and auto-populates the fields of the form from the user's information obtained from the second database. The nearby computer then emails the completed form to the intended recipient. Alternatively, the computer could print the completed form on a nearby printer.
Rather than access an external database, in some embodiments, the system has a portable scanner that contains the user's information, such as in an identity module, SIM, or security card. The scanner provides information identifying the form to the nearby PC. The nearby PC accesses the electronic form and queries the scanner for any necessary information to fill out the form.
19.2. Business Cards
The system can be used to automatically populate electronic address books or other contact lists from paper documents. For example, upon receiving a new acquaintance's business card, a user can capture an image of the card with his/her cellular phone. The system will locate an electronic copy of the card, which can be used to update the cellular phone's onboard address book with the new acquaintance's contact information. The electronic copy may contain more information about the new acquaintance than can be squeezed onto a business card. Further, the onboard address book may also store a link to the electronic copy such that any changes to the electronic copy will be automatically updated in the cell phone's address book. In this example, the business card optionally includes a symbol or text that indicates the existence of an electronic copy. If no electronic copy exists, the cellular phone can use OCR and knowledge of standard business card formats to fill out an entry in the address book for the new acquaintance. Symbols may also aid in the process of extracting information directly from the image. For example, a phone icon next to the phone number on the business card can be recognized to determine the location of the phone number.
19.3. Proofreading/Editing
The system can enhance the proofreading and editing process. One way the system can enhance the editing process is by linking the editor's interactions with a paper document to its electronic counterpart. As an editor reads a paper document and scans various parts of the document, the system will make the appropriate annotations or edits to an electronic counterpart of the paper document. For example, if the editor scans a portion of text and makes the “new paragraph” control gesture with the scanner, a computer in communication with the scanner would insert a “new paragraph” break at the location of the scanned text in the electronic copy of the document.
19.4. Voice Annotation
A user can make voice annotations to a document by scanning a portion of text from the document and then making a voice recording that is associated with the scanned text. In some embodiments, the scanner has a microphone to record the user's verbal annotations. After the verbal annotations are recorded, the system identifies the document from which the text was scanned, locates the scanned text within the document, and attaches the voice annotation at that point. In some embodiments, the system converts the speech to text and attaches the annotation as a textual comment.
In some embodiments, the system keeps annotations separate from the document, with only a reference to the annotation kept with the document. The annotations then become an annotation markup layer to the document for a specific subscriber or group of users.
In some embodiments, for each capture and associated annotation, the system identifies the document, opens it using a software package, scrolls to the location of the scan and plays the voice annotation. The user can then interact with a document while referring to voice annotations, suggested changes or other comments recorded either by themselves or by somebody else.
19.5. Help In Text
The described system can be used to enhance paper documents with electronic help menus. In some embodiments, a markup layer associated with a paper document contains help menu information for the document. For example, when a user scans text from a certain portion of the document, the system checks the markup associated with the document and presents a help menu to the user. The help menu is presented on a display on the scanner or on an associated nearby display.
19.6. Use with Displays
In some situations, it is advantageous to be able to scan information from a television, computer monitor, or other similar display. In some embodiments, the portable scanner is used to scan information from computer monitors and televisions. In some embodiments, the portable optical scanner has an illumination sensor that is optimized to work with traditional cathode ray tube (CRT) display techniques such as rasterizing, screen blanking, etc.
A voice capture device which operates by capturing audio of the user reading text from a document will typically work regardless of whether that document is on paper, on a display, or on some other medium.
19.6.1. Public Kiosks and Dynamic Session IDs
One use of the direct scanning of displays is the association of devices as described in Section 15.6. For example, in some embodiments, a public kiosk displays a dynamic session ID on its monitor. The kiosk is connected to a communication network such as the Internet or a corporate intranet. The session ID changes periodically but at least every time that the kiosk is used so that a new session ID is displayed to every user. To use the kiosk, the subscriber scans in the session ID displayed on the kiosk; by scanning the session ID, the user tells the system that he wishes to temporarily associate the kiosk with his scanner for the delivery of content resulting from scans of printed documents or from the kiosk screen itself. The scanner may communicate the Session ID and other information authenticating the scanner (such as a serial number, account number, or other identifying information) directly to the system. For example, the scanner can communicate directly (where “directly” means without passing the message through the kiosk) with the system by sending the session initiation message through the user's cell phone (which is paired with the user's scanner via Bluetooth™). Alternatively, the scanner can establish a wireless link with the kiosk and use the kiosk's communication link by transferring the session initiation information to the kiosk (perhaps via short range RF such as Bluetooth™, etc.); in response, the kiosk sends the session initiation information to the system via its Internet connection.
The system can prevent others from using a device that is already associated with a scanner during the period (or session) in which the device is associated with the scanner. This feature is useful to prevent others from using a public kiosk before another person's session has ended. As an example of this concept related to use of a computer at an Internet cafe, the user scans a barcode on a monitor of a PC which s/he desires to use; in response, the system sends a session ID to the monitor that it displays; the user initiates the session by scanning the session ID from the monitor (or entering it via a keypad or touch screen or microphone on the portable scanner); and the system associates in its databases the session ID with the serial number (or other identifier that uniquely identifies the user's scanner) of his/her scanner so another scanner cannot scan the session ID and use the monitor during his/her session. The scanner is in communication (through wireless link such as Bluetooth™, a hardwired link such as a docking station, etc.) with a PC associated with the monitor or is in direct (i.e., w/o going through the PC) communication with the system via another means such as a cellular phone, etc.
Part IV—System Details
In this description, reference is made to the accompanying drawings that form a part hereof wherein like numerals designate like parts throughout, and in which are shown, by way of illustration, specific embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present invention. Therefore, the following detailed description is not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.
Various embodiments include a user-friendly technique for filling forms (such as forms on paper, in catalogs, displayed on web pages, other dynamic displays, in advertisements, in books, in magazines, on signs and the like) using a graphical capture device (such as a scanner, digital camera, or other device capable of capturing at least a portion of the rendered form) or other devices. Embodiments may be practiced to engage in many forms of information gathering utilizing a device to interface with human and machine-readable materials.
In this description, various aspects of selected embodiments are described. However, it will be apparent to those of ordinary skill in the art and others that alternate embodiments may be practiced with only some or all of the aspects. For purposes of explanation, specific numbers, materials and configurations are set forth in order to provide a thorough understanding of the embodiments. However, it will be apparent to those of ordinary skill in the art and others that alternate embodiments may be practiced without the specific details. In other instances, well-known features are omitted or simplified in order not to obscure the illustrated embodiments.
Various operations may be described herein as multiple discreet steps in turn, in a manner that is helpful to understanding of the embodiments. However, the order of description should not be construed to imply that these operations are necessarily order dependent. In particular, these operations may not be performed in the order of presentation.
The phrase “in one embodiment” is used repeatedly. The phrase generally does not refer to the same embodiment, however, it may. The terms “comprising,” “having” and “including” are synonymous, unless the context dictates otherwise.
Referring now to
In various embodiments, the scanning device 302, 500, computer 212, mobile phone or PDA 210, user account services 236, document sources 234 and multimedia server 450 are coupled to each other wirelessly, i.e., they are members of a wireless network 430. In other embodiments, the scanning device 302, 500, computer 212, mobile phone or PDA 210, user account services 236, document sources 234 and multimedia server 450 are coupled to each other as members of a wire-based or mixed wireless and wire-based network (e.g., as in the Internet 410). Regardless of the manner the devices are coupled to each other, for various embodiments, scanning device 302, 500, computer 212, mobile phone or PDA 210, user account services 236, document sources 234 and multimedia server 450 are each equipped to operate in accordance with at least one communication transaction protocol. In various embodiments, scanning device 302, 500, computer 212 and mobile phone or PDA 210 may be wholly or partially integrated. Thus, the terms scanning device, computer and mobile phone or PDA, as used herein, for the purpose of this specification, including the claims, shall be interpreted with the meaning of an appropriately equipped device, operating in accordance with one or more of the scanning device 302, 500, computer 212 and mobile phone or PDA 210 roles.
Additionally, in various embodiments, computer 212, document sources 234, multimedia server 450 and user account services 236 may be wholly or partially integrated. Thus, the terms computer, document sources, and multimedia server and user account services, as used herein, for the purpose of this specification, including the claims, shall be interpreted with the meaning of an appropriately equipped device, operating in accordance with a computer, document sources, multimedia server or a user account services role. It may be useful for a user to have document enhancement data on file so that some or all of the document enhancements of a document may be invokes without a user having to initiate a remote connection when a document enhancement is encountered. This may be helpful with common document enhancements. In some embodiments, such common document enhancements may be cached at devices closer to a user. Less common document enhancements may also be stored within one or more devices within the system 400 and optionally made available to enhance documents.
The scanning device 302, 500 also includes a processing unit 510, a display 540, a graphical input 525, an optional audio output 545, an optional user input interface 535 and a memory 550, all interconnected along with the communications interface 530 via a bus 520. The memory 550 generally comprises a random access memory (“RAM”), a read only memory (“ROM”) and a permanent mass storage device, such as a disk drive, flash RAM or the like. The memory 550 stores an operating system 555, document processing routine 560, document enhancement data 565 and device identifier 570. In alternate embodiments, bus 520 may be a hierarchy of bridged buses. For ease of understanding, operating system 555, document processing routine 560, document enhancement data 565 and device identifier(s) 570 are illustrated as separate software components, in alternate embodiments, they may be comprised of multiple software components, implemented in hardware, or may be subparts of one or more integrated software components.
In one embodiment, the document processing routine 560 is adapted to process graphically captured portions of a rendered document 495. In various embodiments, a document 495 may be any rendered version of human-readable text and or images that is susceptible to graphical capture by a scanning device 302, 500. Exemplary, non-limiting example of rendered documents 495 include materials from, but not limited to, paper catalogs, magazines, books, printed text, television or computer displays, posters, signs and the like. In various embodiments, document processing routine 560 may simply be an analog to digital converter where graphically captured information from the graphical input 525 is stored as document data.
Various embodiments may employ scanning devices 302, 500 having enhanced capabilities to allow still further transactions. For example, in one such embodiment, scanning device 302, 500 comprises Global Positioning System (“GPS”) circuitry or other positioning circuitry (not shown), thereby enabling transactions based on the geographic location of the graphical capture of a rendered document.
In alternate embodiments, document processing routine 560 may include enhanced image analysis. For example, document processing routine 560 may process graphically captured information from the graphical input 525 to extract image information. One possible form of document processing may include determining the position, orientation and size of elements of a pattern in an image (such as text or other human-readable symbols).
Another form of document processing may include identifying differences between an image and a stored pattern. Methods for identifying these differences are generally referred to as pattern inspection methods and may be used for a number of purposes. One early, widely used method for pattern location and inspection is known as blob analysis. In this method, the pixels of a digital image are classified as “object” or “background,” typically by comparing pixel gray-levels to a threshold. Pixels classified as object are grouped into blobs using the rule that two object pixels are part of the same blob if they are neighbors; this is known as connectivity analysis. Each such blob is analyzed to determine properties such as area, perimeter, center of mass, principal moments of inertia, principal axes of inertia and the like. In one specific implementation, the position, orientation and size of a blob are taken to be its center of mass, angle of first principal axis of inertia, and area, respectively. These and the other blob properties can be compared against a known ideal for proposes of inspection. Blob analysis is relatively inexpensive to compute, allowing for fast operation on inexpensive hardware.
Another document processing method that may be employed by document processing routine 560 is template matching. Template matching uses one or more training images that contain examples of the patterns to be located. The subset of the training image containing the example is processed to produce a pattern and then stored in a memory. Images are presented that may contain the object to be found. The stored pattern is compared with like-sized subsets of the presented images at all or selected positions and the position(s) that best match the stored pattern may then be considered the position(s) of the object. Degree of match at a given position of the pattern is simply the proportion of pattern pixels that match their corresponding image pixel, thereby providing pattern inspection information. In some embodiments, template matching may be employed to locate electronic instances of documents as described below.
Template matching may be applied to a variety of document processing analyses. It also is able to tolerate missing or extra pattern features without severe loss of accuracy, and it is able to detect fine differences between the pattern and the object.
A further alternate form of document processing is the use of gray-level normalized correlation for pattern location and inspection. Gray-level normalized correlation and template matching are similar, except that the full range of image gray-levels are considered with gray-level normalized correlation, and the degree of match becomes the correlation coefficient between the stored pattern and the image subset at a given position.
Gray-level correlation may be used in applications where significant variation in orientation and/or size is expected. Accordingly, the stored pattern is rotated and/or scaled by digital image re-sampling methods before being matched against the image. By matching over a range of angles, sizes and x-y positions, one can locate an object in the corresponding multidimensional space.
Still further versions of document processing routine 560 may include conventional Optical Character Recognition (“OCR”) processing to extract textual and/or symbolic information from a graphically captured portion of a rendered document 495.
While the document processing routine 560 is described as residing on the scanning device 302, 500, in alternate embodiments, document processing routine 560 may optionally reside on other devices of the operating environment 400, such as the computer 212, mobile phone or PDA 210 or document sources 234.
It will be appreciated that the software components of scanning device 302, 500 may be loaded from a computer-readable medium into memory 550 of the scanning device 302, 500 using a mechanism (not shown) associated with the computer-readable medium such as a floppy, tape, DVD (Digital Versatile Disk) drive, CD (Compact Disk) drive, flash RAM or communications interface 530. In various embodiments, the loading may be performed during the manufacturing of scanning device 302, 500, or subsequently. In other embodiments, the software components may be downloaded from one or more networked servers.
In various embodiments, the communications interface 530 may facilitate the connection of remote devices to the scanning device 302, 500; for example, devices for reading and/or writing in machine-readable media, digital cameras, printers and the like. Various user-input interfaces 535 may also be coupled to the scanning device 302, 500, such as, for example, keyboards, keypads, touch-pads, mice and the like.
The computer also includes a processing unit 610, an optional display 640 and a memory 650, all interconnected along with the communications interface 630 via a bus 620. The memory 650 generally comprises RAM, ROM and a permanent mass storage device, such as a disk drive, flash RAM or the like. The memory 650 stores an operating system 655, web browser 660, dynamic response routine 1000 and game routine 1500.
In alternate embodiments, bus 620 may be a hierarchy of bridged buses. For ease of understanding, operating system 655, web browser 660, dynamic response routine 1000 and game routine 1500 are illustrated as separate software components; in alternate embodiments, they may be comprised of multiple software components, implemented in hardware, or may be subparts of one or more integrated software components.
It will be appreciated that the software components may be loaded from a computer-readable medium into memory 650 of the computer 212 using a mechanism (not shown) associated with the computer-readable medium such as a floppy, tape, DVD drive, CD drive, flash RAM or communications interface 630. In various embodiments, the loading may be performed during the manufacturing of computer 212, or subsequently. In other embodiments, the software components may be downloaded from one or more networked servers.
In various embodiments, the communications interface 630 may facilitate the connection of remote devices to the computer 212; for example, devices for reading and/or writing in machine-readable media, digital cameras, printers and the like. Various input mechanisms may also be coupled to the computer 212, such as, for example, keyboards, keypads, touch-pads, mice and the like (not shown).
In various embodiments, an electronic instance of a document may be associated with document 495. In one such embodiment, the document 495 is associated with a document identifier. A document identifier may be an explicit identifier or may be a derived identifier from the contents of the document itself. In some embodiments, various types of explicit document identifiers may be used to distinguish documents. The type of document may determine the choice of the type of identifier used. The generation and assignment of the identifiers may follow industry standard practices. Accordingly, in some embodiment it may be desirable that document identifiers are unique for a document (or group of documents). One method for generating document identifiers is to take a title and append extra characters (e.g., “Tax-Form-1040-5435873934”). Another method is to generate a Globally Unique Identifier (“GUID”) using conventional algorithms. The location of document identifier generation may be at any of a variety of devices in the operating environment 400, such as user account services 236, scanning device 302, 500, computer 212, mobile phone or PDA 210, document sources 234 and the like. The appropriate document identifier may be generated on demand or may be predetermined. Furthermore, document identifiers may comprise supplemental information associated with a specific document or even a specific instance of a document.
Derived identifiers may be determined from the contents of a document 495. One type of derived document identifier is a digest (such as a hash) of one or more fragments (e.g., title, document text, document elements, names or the like) of the document 495. In some such embodiments, electronic instances and documents 495 contain substantially the same content. However, an electronic instance may or may not be the actual source document employed to generate document 495. In other words, an electronic instance may be a copy instance or cousin descendant instance from a common ancestor of the source document employed to generate document 495. Further, in various embodiments, the document 495 may be a document of any type, and the term “document,” as used herein, includes but is not limited to, a printed version, a displayed version, a Braille version and other versions of the like of a document. The term “digest” (of a document fragment) as used herein, in the specification and later in the claims, refers to a derived result outputted from a process that includes acquiring information or knowledge of the document fragment, where the derived result comprises information about the document fragment. In other words, a digest may also be considered as a representation or specification of the document fragment. Non-limiting example algorithms for producing digests include MD5, SHA, SHA-1 and the like.
In various embodiments, each document fragment includes a number of characters, and the corresponding digest is generated based at least in part on the characters of the document fragment. The term “character” as used herein is intended to be broadly interpreted, encompassing alphabets, numerals, punctuation, symbols and glyphs of non-character based languages. As will be described in further detail below, in various embodiments, each digest may be generated without awareness of the language and/or the character/glyph set employed to express the content of the document, including the document fragment itself. Further, an electronic instance may be located employing a digest generated using a relatively short document fragment, as short as a handful of words.
In one embodiment, the scanning device 302, 500 is suitably equipped to generate at least a representation of a document fragment of the document 495. For embodiments where document 495 is a printed instance, scanning device 302, 500 may be an optical scanner unit capable of generating at least an image of the document fragment.
In other embodiments, scanning device 302, 500 may be further endowed with the ability to generate a digest of a document fragment, using the generated image of the document fragment.
In various embodiments, a document identifier or electronic instance may be located and associated with a document 495, based at least in part on the digest of a fragment of the document 495.
In further embodiments, the content/characters of a document fragment, may be determined from its digest, and may be used to cause an electronic instance or document identifier to be located.
In various embodiments, an electronic instance may be located, and associated with document 495, by providing an image of a document fragment to search service, or by causing a search query having either a digest or the determined contents/characters as the search criteria, to be submitted to a search service (not shown). Resultantly, an electronic instance or document identifier may be located, and associated with a document 495.
The process of generating a digest for a document fragment, in accordance with various embodiments may be practiced by scanning device 302, 500 or other devices such as computer 212 or mobile phone or PDA 210. Further, for these embodiments, the content, more specifically, the characters, of a document fragment may be analyzed without awareness of the language and/or the character set employed to express the content of the document 495, including the document fragment.
In one embodiment, locating an electronic instance or document identifier of a document involves abstractedly identifying the characters of document fragment. The phrase “abstractedly identifying the characters” as used herein, is intended to include in its meaning “the identification of the presence of the various characters in the document fragment, without precisely recognizing the nature of the characters.” For example, when processing a document fragment having the content “this is a string of characters”, the process identifies the presence of 25 characters (not counting spaces), of which, 12 are distinct, i.e., “t”, “h”, “i”, “s”, “a”, “n”, “g”, “o”, “f”, “c”, “e”, but, the process does not recognize the exact nature of the distinct characters, i.e., they are “s”, “t”, and so forth.
In various embodiments, the presence of the various characters is identified by comparing an image of the document fragment with a replicate of the image (also referred to as the template). In various embodiments, the process may also include pre-processing of the received image of document fragment, removing extraneous information, e.g., all or portions of the characters of the line above and/or the line below. Removal of such extraneous information may be effectuated employing anyone of a number of image/text processing techniques.
In various embodiments, identification of the presence of various characters in document fragment is effectuated by incrementally comparing the ending characters of document fragment with the beginning characters of document fragment. The process may be visualized as sliding a template along from the beginning to the end of the document fragment and comparing the overlapping sections of document fragment and the template. Resultantly, the character “s” is first compared to the letter “t”, then the letters “rs” are compared to the letters “th”, and so forth.
Eventually, when the letters “characters” are compared to the letters “this is a s”, the presence of the letter “s” is identified. Again, the fact that the character is the alphabetic “s” is not appreciated, nor is the appreciation necessary. However, in alternate embodiments, the alphabetic nature of the character may be fully appreciated.
For various embodiments, on identification of the presence of a new character (again without appreciating the nature of the new character), a token is assigned to identify the new character. Thus, for the example document fragment “This is a string of characters”, the characters are identified by corresponding token tokens or token identifiers.
For various embodiments, the presence of the characters “e”, “f”, “o”, “g” and “n” are substantially identified at the same time, when the entire document fragment is compared to template. For some embodiments, white space analysis is further performed at the end of the comparison analysis, to ensure the characters within a non-repeating pair or multiple characters, such as “o” and “f” in the case of “of”, are recognized as separate characters, although again they need not be fully recognized as the alphabet “o” or “f”. For some embodiments, tokens for the last characters detected are simply assigned tokens without recognizing the nature of each of the characters.
Thus, for the example document fragment, tokenization results in the generation of the token vector of “5261 61 4 1536CB A9 7243475831” as “this is a string of characters” is compared to it template as described above.
Next, for various embodiments, an analysis is performed using the token vector to generate a digest comprised of presence characters. A value is assigned to each presence character, based at least in part on its occurrence pattern. For the embodiments, the re-occurrence value is equal to the character distance between a token, and its first subsequent re-occurrence in the remainder of the token vector. Further, for the embodiments, a presence character is attributed with a value of zero if it does not re-occur in the remainder of the token vector. Finally, the digest is outputted for the document fragment. Accordingly, for the exemplary document fragment “this is a string of characters”, its digest is given by a vector “0, 20, 3, 3, 3, 8, 4, 7, 14, 7, 19, 15, 11, 0, 0, 0, 3, 0, 0, 0, 5, 0, 2, 5, 0, 0, 0, 0, 0, 0.”
In alternate embodiments, various modifications may be made to generate digests. For examples, the occurrence values may be attributed without first tokenizing the characters. Another value other than “0” may be attributed to a character, if the character does not reoccur in the remainder of the document fragment. Hexadecimal values A, B etc. may be employed. More complex, non-linear value attribution approach may be employed instead. The attributed value may be based on other factors beside the re-occurrence of the character. Space may be included as a character. Further, as described earlier, other techniques to recognize the nature of the characters may be employed. Yet further, the process may be modified to analyze and assign attributes to the characters, abstractedly, by groups of characters having two or more characters.
In some embodiments, the scanning device 302, 500 initiates a document enhancing transaction involving the computer 212 by scanning a portion of a rendered document 495.
In
Meanwhile, a user scans a portion of the document 495 that includes a document enhancement (such as an audio, image, video, dynamic display or other enhancement). The enhancement scan is sent 725 from the scanning device 302, 500 to the computer 212. The enhancement scan, located document identifier and the SID are sent 730 to a multimedia server 450. The multimedia server 450 determines 735 if there is any SID-specific enhancement and then locates 740 the enhancement corresponding to the enhancement scan, document identifier and SID. The located enhancement file(s) are returned 745 to the computer 212, where they are depicted 750 (displayed, played or otherwise presented). Each subsequent media scan in the same document 495 does not require a new context scan.
In some embodiments, depicting the enhancement may comprise displaying the enhancement on a dynamic display, while in other embodiments, depicting the enhancement may comprise playing an audio file, still other embodiments may combine audio and visual elements in an enhancement.
In various embodiments, the communications described above and shown in
Similarly, while the document enhancement process is shown as occurring in a series of steps, it may occur in other sequences, and the steps may occur after protracted periods. In one “asynchronous” example, a user may graphically capture a document fragment as a document context and may also capture a document fragment including a desired enhancement, but not transmit the graphically captured document fragments until a later point in time. Such asynchronous communications allow users of various embodiments to practice the embodiments, even when not connected to a network.
For example when a user is not connected to a network, and a scanning device 302, 500 does not have information about this user's context (e.g., location, time of day, recent documents viewed, recently viewed documents, occupation and any of a myriad of other contextual clues that may be used to provide context to a user's action), or when a user does not have access to a display—then resolving questions about which document was actually scanned can be resolved at a later time. Accordingly, a document enhancement process might be finished by directing a user to a web site later, or by sending them an e-mail that requests further action—possibly confirming by clicking on or otherwise following a hyperlink. Such an e-mail-based enhancement process might also include an explanation or list of data enhancements being offered.
Expanding briefly on user context, in some embodiments a user's context is tracked rigorously to aid in resolving ambiguous document selections. For example, if a user submits one positively identified document from a particular magazine, then another ambiguously matched document that also appears in the same magazine may be given a higher priority as a likely correct choice on a subsequent submission. Similarly, if a user located in London scans a document that ambiguously matches both an American document and a British document; the British document will be given precedence. Likewise, if the user owns a boat, but not an airplane, and one of the ambiguously matched documents relates to boats and another to airplanes, priority may be given to the document relating to boats when disambiguating between the two documents. These are merely illustrative and non-limiting examples of how user context may be used to resolve ambiguous matches between documents. See
In some embodiments, document submission communications are performed over connections using a Hypertext Transfer Protocol (“HTTP”) connection in communication with one or more Common Gateway Interface (“CGI”) or other HTTP-accessible applications. In other embodiments, different transmission protocols and/or connections for document submissions may be employed. Various types of document submission protocols are anticipated being employed by various embodiments.
In general, a context scan contains the information necessary to identify the document 495 and element data for enhancing one or more document elements. This may be accomplished by a variety of different document models in accordance with various embodiments.
Accordingly,
Meanwhile, a user scans a portion of the document 495 that includes a document enhancement (such as an audio, image, video, dynamic display or other enhancement). The enhancement scan is sent 850 from the scanning device 302, 500 to the computer 212. The computer then locates 855 the enhancement corresponding to the enhancement scan within the cached enhancement package and depicts the enhancement. Each subsequent media scan in the same document 495 does not require a new context scan.
Meanwhile, the scanning device 302, 500 is used to scan an enhancement region of the document and the enhancement scan is sent 930 to the computer 212. The enhancement scan, document identifier and the SID are sent 935 to a multimedia server 450. The enhancement scan, document identifier and the SID are also sent 940 to the user account services 236, where they are logged 945 as an enhancement scan. The multimedia server 450 determines 950 if there is any SID-specific enhancement and then locates 955 the enhancement corresponding to the enhancement scan, document identifier and SID. The located enhancement file(s) are returned 960 to the computer 212, where they are depicted 955. Each subsequent media scan in the same document 495 does not require a new context scan.
The communications described above and shown in
In accordance with the various above-described communications between the devices of the document enhancement system 400,
In block 1020, the document identifier is associated with the SID, thereby establishing a relationship between a scanning device 302, 500 and a current document. Next, in looping block 1025, processing iterates until the document identifier is no longer associated with the SID (e.g., a new document context is scanned, the scanning device 302, 500 is turned off, or the like). In block 1030, a new scan is processed. If in decision block 1035 it is determined that the new scan is for a new document context, looping ceases, and processing loops back to block 1010. Otherwise, processing proceed to block 1040 where document enhancement media is requested from a media repository (e.g., from multimedia server 450 or from a local repository or cache). In decision block 1045, a determination is made whether media was located for the document enhancement. If no media was located, then processing proceeds to looping block 1055 for a new iteration. Otherwise, if enhancement media was located, then in block 1050, the enhancement media is depicted and processing proceeds to looping block 1055. Once the document identifier is no longer associated with the SID, processing proceeds to block 799 where document enhancement routine 1000 ends.
Optionally, a user may request that a particular document, or a document enhancement, be presented or delivered in another fashion. For example, a user might request that a separate paper copy of a document be mailed to their home or work address, that information shown on a document be requested via an email, or that a URL identifying a web-based version of this document be sent to this user by email other methods.
In various embodiments, when a user scans a document, e.g., by scanning a document identifier or other identifying text or marking, the user may be presented with options. This presentation may occur later, for example when this user connects to a user account (e.g., on user account services 236), or when they check their email or a website. Options available to a user might include:
Furthermore, in some embodiments, a user may be presented with feedback (audible, visual, tactile or the like) while obtaining document identifiers. For example, in one exemplary embodiment, if a document 495 unambiguously matched from a document identifier, a first light emitting diode (“LED”) may light up. Additional, when a user scans a document enhancement element within the document 495, a second LED may light up once the scanning device 302, 500 (either alone or in combination with one or more other devices within the system 400) determines the scanned location within the document 495. Likewise, other indicators may be employed to indicate that a document was not unambiguously identified.
In assorted embodiments, various type of documents may be encountered by a user, and optionally processed in some way by different embodiments, a non-exclusive listing might include documents for:
Note that a scanning device 302, 500 or account might be associated with a group of people (e.g., classroom, a school, a club, a company or other association).
The description of a document enhancement transactions illustrated in
In some embodiments, there may be a fee or other financial transaction associated with various steps of enhancing a document. For example, a user might receive a charge for this service. Such a charge might be automatically billed to a credit card or deducted from a debit card or bank account or prepaid account associated with a particular user, with a scanning device 302, 500 or with a location. Alternately, such a charge might be levied on and paid by a recipient of this information or a party in association with them.
In one embodiment, a user may initiate an enhancement event for a part of a document or an entire document simply by scanning (or otherwise entering) an identifier associated with this document. In some cases a document identifier may also be readable by a human, for example as a serial number or URL, so that users who cannot or do not want to graphically capture a document may still enhance it by entering an identifier manually. In these instances, it may be helpful if a document or accompanying material includes information about how to submit data by other methods. Such methods may include going to a specific URL with a web-browser. Another may be via a phone call to a specific number and an interaction with an interactive voice response server (not shown). These last two examples indicate how it may be useful in some cases for individuals to have a way to identify themselves separately from a scanning device 302, 500. Such a user identifier may associate an individual with a collection of data so that an individual may respond to a particular enhancement data request by submitting or relating only their identifier. In one example, a user could respond to a printed document by dialing a number associated with this document and then entering their (possibly numeric) identifier via voice or DTMF or other phone commands or actions. In one embodiment, a user might be able to use their email address, social security number, or other pre-existing data item as a key associated with document enhancements to be used with a document.
In accordance with the above description and the interactions shown between a scanning device 302, 500, document sources 234, user account services 236 and multimedia server 450 in
Alternately, in block 1125, the media request and document identifier are matched with a set of media files. In looping block 1130, processing iterates through each document enhancement associated with the document identifier and in block 1135 matches the best media file(s) to the SID. In block 1140, the match media file(s) are added to a packet. Looping block 1145 then cycles back to looping block 1130 until all document enhancements have been iterated through. In block 1199, the media package is returned.
In alternate embodiments, a user with a scanning device 302, 500 may optionally select document portions or groups of portions by individually scanning portion labels (or symbols) or title text associated with a portion or portions. This might allow a user easily choose which enhancements to depict and which to skip. A suitable system may have an ability to recognize various frequently used names, titles and/or symbols. Optionally, an association between a title or other mark and a meaning of a particular portion or group of portions may be separately established by a party setting up a document.
In some cases, special marks may accompany documents, document names, document portions or other document elements that a document enhancement system 400 may want or need to recognize. These marks may be recognizable by a scanning device 302, 500 and or other device within the system 400. Optionally the special marks may have characteristics recognizable by a user. In some embodiments, only these special marks will need to be scanned to indicate an enhancement or object to file all or part of a document. In some cases it may be helpful if these marks appear next to or near a given element name.
The descriptions of document enhancement transactions illustrated in
Accordingly,
If, in decision block 1215, no document matching the explicit document identifier was available or if no unambiguous match was determined in decision block 1230, processing proceeds to block 1220 where additional document context information is obtained. For example, a user may be queried for additional information from the document in real-time, or may have a query for additional information sent to an associated user account (e.g., on user account services 236). Processing then proceeds to block 1225 for re-analysis.
If, however, in decision block 1215 a document matching the explicit document identifier was located, processing proceeds to block 1299 where the unambiguously matching document's document ID is returned and the document matching routine 1200 ends in block 1299.
In addition to enhancing documents with media representations, various embodiments provide additional enhancements. The additional enhancements may be user-specific and accordingly may have restricted access. A password, PIN or other private code may be associated with a user's identifier to permit restricted access.
Additionally, stored document enhancement data might be located on a scanning device 302, 500, or other device associated with an individual user (such as computer 212 or user account services 236). Data may be stored encrypted, and/or with other security measures to prevent theft and/or accidental release of data.
Note that in some embodiments, scanning a document identifier conveys that a user specifically wants information sent—e.g., this user is giving consent. In such a case one or more devices within a document enhancement system 400 may make a record of this scan, for example by preserving a captured image, time, date, or other meta-data, from this event as proof of consent. In some cases, a document identifier may include supplemental information that in some measure verifies that a user scanned a document. In one embodiment, the supplemental information might be a unique code associated with each individual document 495, or with a specific portion of a document. This code might be associated with a specific document mailed or otherwise delivered to a specific individual. This code might optionally only be readable by a machine programmed with specific data or a specific algorithm.
In some embodiments it may be desirable for the document sources 234 to process (or preprocess) documents when registering them for later retrieval. Such a registration might include data such as where and how to send certain data, specific document enhancements for a document, how these document enhancement services are to be paid for, security and/or privacy ratings of providers of document enhancements, a copy of a provider's privacy policy, specific instructions for handling various processes and/or circumstances in this document enhancing process (optionally as computer code or instructions) and optionally other data as well. Other data associated with or registered with a document may include information about a document identifier, a symbol or other representation of some graphical element or elements by which this document may be recognized, which individual users or groups of users or situations or contexts this document is intended for, an electronic copy of this document (for example, in printable PDF format) or where to locate such a copy, valid dates, times, or other qualifying circumstances in which this document may be submitted. Other data may be associated or submitted with a document as well, optionally including all data that is useful or necessary to various parties participating in a document enhancement process.
For example, a document may carry additional coded, machine-readable or human-readable data. This data might include a specific user for whom this document was intended. Such additional data may be incorporated in a document identifier such that this additional data is included when a user scans the document identifier. Optionally, a document or group of documents may have a unique document identifier. Data may be separately associated with this identifier. Such data might be stored in document sources 234 or stored elsewhere within the document enhancement system 100. If a document is registered with document sources 234, such data might be entered and/or associated with a document when the document is registered.
Accordingly,
In some embodiments, if a user encounters a document not known to document sources 234, they might mail, fax, email or otherwise deliver this document so that it may be registered. The document sources 234 may optionally contain expert knowledge and instructions for automatically analyzing and recognizing various elements of documents. Thus, a new document may be analyzed and made available to be automatically enhanced if subsequent users request it.
In some embodiments, the first user to submit a copy of a document previously unknown to document sources 234 may be rewarded in some way, for example by receiving a small payment when subsequent users interact with this document, or by not having to pay a fee to have the document enhanced. In some systems, these incentive payments might instead appear as credits to document authors or publishers who submit and/or register their document directly with document sources 234 before a user submits it—for example, these credits might be used to reduce a per-user charge that registered document publishers may be assessed for use of this system.
In addition, in a further exemplary embodiment, a dynamic display allows further functionality for dynamically displayed documents. In the dynamically displayed example, actions associated with ordering enhancements from a document, such as document 1400, could be reflected in a dynamically updated portion of the dynamic display. In one such example, as a user scans the double-underlined word “lions” 1420A and a document enhancement web page is activated in accordance with the above descriptions.
One example web page 1500 is shown in
In many cases when interacting with documents, it may be helpful to know the location of the user. This would be useful, for example, when the user has access to a display device and wants their document displayed there. A label or other scanning-device-readable indicator (not shown) that identifies the specific display and or device may be available to the user. Scanning this label informs document sources 234 (or a user account services) of the user's location. In some cases, the identifying label can be generated and displayed on a computer 212. Generally, only the user physically at the display device would then be able to scan this information, thereby providing an additional layer of security.
The document enhancements described above may be employed in a myriad of applications. In various embodiments, they may be employed with games and puzzles in documents. Once such exemplary game system is illustrated in
In
Meanwhile, the scanning device 302, 500 is used to scan a game event region of the document and the game scan is sent 1635 to the computer 212. The computer 212 determines 1660 if the game scan matches the correct SID-specific game event (e.g., if a game event required a scan of an animal, does a scan of the word “lion” qualify? Yes.). The result of the determination is depicted 1665 and the current game status is tallied. Eventually, once all game events have been tallied, updated game data (including the last tally) and the document identifier and SID are sent to the user account services 236 as a record of the game.
In various embodiments, the communications described above and shown in
Similarly, while the document enhancement game process is shown as occurring in a series of steps, it may occur in other sequences, and the steps may occur after protracted periods. In one “asynchronous” example, a user may graphically capture a document fragment as a document context and may also capture a document fragment including a desired game enhancement, but not transmit the graphically captured document fragments until a later point in time. Such asynchronous communications allow users of various embodiments to practice the embodiments, even when not connected to a network. Additionally, the scanning device 302, 500 may recognize portions of a document 495 while in an asynchronous mode, and may be operative to tally a score for a game in accordance with one exemplary embodiment.
Conclusion
Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art and others, that a wide variety of alternate and/or equivalent implementations may be substituted for the specific embodiment shown and described without departing from the scope of the present invention. This application is intended to cover any adaptations or variations of the embodiment discussed herein.
It will be appreciated by those skilled in the art that the above-described system may be straightforwardly adapted or extended in various ways. While the foregoing description makes reference to particular embodiments, the scope of the invention is defined solely by the claims that following and the elements recited therein.
This application is a Continuation-In-Part of U.S. patent application Ser. No. 11/004,637 filed on Dec. 3, 2004 now U.S. Pat. No. 7,707,039, which is hereby incorporated by reference in its entirety. This application is related to, and incorporates by reference in their entirety, the following U.S. Patent Applications, filed concurrently herewith: U.S. patent application Ser. No. 11/097,961, entitled METHODS AND SYSTEMS FOR INITIATING APPLICATION PROCESSES BY DATA CAPTURE FROM RENDERED DOCUMENTS, U.S. patent application Ser. No. 11/097,093, entitled DETERMINING ACTIONS INVOLVING CAPTURED INFORMATION AND ELECTRONIC CONTENT ASSOCIATED WITH RENDERED DOCUMENTS, U.S. patent application Ser. No. 11/098,038, entitled CONTENT ACCESS WITH HANDHELD DOCUMENT DATA CAPTURE DEVICES, U.S. patent application Ser. No. 11/098,014, entitled SEARCH ENGINES AND SYSTEMS WITH HANDHELD DOCUMENT DATA CAPTURE DEVICES, U.S. patent application Ser. No. 11/097,103, entitled TRIGGERING ACTIONS IN RESPONSE TO OPTICALLY OR ACOUSTICALLY CAPTURING KEYWORDS FROM A RENDERED DOCUMENT, U.S. patent application Ser. No. 11/098,043, entitled SEARCHING AND ACCESSING DOCUMENTS ON PRIVATE NETWORKS FOR USE WITH CAPTURES FROM RENDERED DOCUMENTS U.S. patent application Ser. No. 11/097,981, entitled INFORMATION GATHERING SYSTEM AND METHOD, U.S. patent application Ser. No. 11/097,835, entitled PUBLISHING TECHNIQUES FOR ADDING VALUE TO A RENDERED DOCUMENT, U.S. patent application Ser. No. 11/098,016, entitled ARCHIVE OF TEXT CAPTURES FROM RENDERED DOCUMENTS, U.S. patent application Ser. No. 11/097,828, entitled ADDING INFORMATION OR FUNCTIONALITY TO A RENDERED DOCUMENT VIA ASSOCIATION WITH AN ELECTRONIC COUNTERPART, U.S. patent application Ser No. 11/097,833, entitled AGGREGATE ANALYSIS OF TEXT CAPTURES PERFORMED BY MULTIPLE USERS FROM RENDERED DOCUMENTS, U.S. patent application Ser. No. 11/097,836, entitled ESTABLISHING AN INTERACTIVE ENVIRONMENT FOR RENDERED DOCUMENTS, U.S. patent application Ser. No. 11/098,042, entitled DATA CAPTURE FROM RENDERED DOCUMENTS USING HANDHELD DEVICE and U.S. patent application Ser. No. 11/096,704, entitled CAPTURING TEXT FROM RENDERED DOCUMENTS USING SUPPLEMENTAL INFORMATION This application claims priority to, and incorporates by reference in their entirety, the following U.S. Provisional Patent Applications: Application Ser. No. 60/559,226 filed on Apr. 1, 2004, application Ser. No. 60/558,893 filed on Apr. 1, 2004, application Ser. No. 60/558,968 filed on Apr. 1, 2004, application Ser. No. 60/558,867 filed on Apr. 1, 2004, application Ser. No. 60/559,278 filed on Apr. 1, 2004, application Ser. No. 60/559,279 filed on Apr. 1, 2004, application Ser. No. 60/559,265 filed on Apr. 1, 2004, application Ser. No. 60/559,277 filed on Apr. 1, 2004, application Ser. No. 60/558,969 filed on Apr. 1, 2004, application Ser. No. 60/558,892 filed on Apr. 1, 2004, application Ser. No. 60/558,760 filed on Apr. 1, 2004, application Ser. No. 60/558,717 filed on Apr. 1, 2004, application Ser. No. 60/558,499 filed on Apr. 1, 2004, application Ser. No. 60/558,370 filed on Apr. 1, 2004, application Ser. No. 60/558,789 filed on Apr. 1, 2004, application Ser. No. 60/558,791 filed on Apr. 1, 2004, application Ser. No. 60/558,527 filed on Apr. 1, 2004, application Ser. No. 60/559,125 filed on Apr. 2, 2004, application Ser. No. 60/558,909 filed on Apr. 2, 2004, application Ser No. 60/559,033 filed on Apr. 2, 2004, application Ser. No. 60/559,127 filed on Apr. 2, 2004, application Ser. No. 60/559,087 filed on Apr. 2, 2004, application Ser. No. 60/559,131 filed on Apr. 2, 2004, application Ser. No. 60/559,766 filed on Apr. 6, 2004, application Ser. No. 60/561,768 filed on Apr. 12, 2004, application Ser. No. 60/563,520 filed on Apr. 19, 2004, application Ser. No. 60/563,485 filed on Apr. 19, 2004, application Ser. No. 60/564,688 filed on Apr. 23, 2004, application Ser. No. 60/564,846 filed on Apr. 23, 2004, application Ser. No. 60/566,667, filed on Apr. 30, 2004, application Ser. No. 60/571,381 filed on May 14, 2004, application Ser. No. 60/571,560 filed on May 14, 2004, application Ser. No. 60/571,715 filed on May 17, 2004, application Ser. No. 60/589,203 filed on Jul. 19, 2004, application Ser. No. 60/589,201 filed on Jul. 19, 2004, application Ser. No. 60/589,202 filed on Jul. 19, 2004, application Ser. No. 60/598,821 filed on Aug. 2, 2004, application Ser. No. 60/602,956 filed on Aug. 18, 2004, application Ser. No. 60/602,925 filed on Aug. 18, 2004, application Ser. No. 60/602,947 filed on Aug. 18, 2004, application Ser. No. 60/602,897 filed on Aug. 18, 2004, application No. 60/602,896 filed on Aug. 18, 2004, application Ser. No. 60/602,930 filed on Aug. 18, 2004, application Ser. No. 60/602,898 filed on Aug. 18, 2004, application Ser. No. 60/603,466 filed on Aug. 19, 2004, application Ser. No. 60/603,082 filed on Aug. 19, 2004, application Ser. No. 60/603,081 filed on Aug. 19, 2004, application Ser. No. 60/603,498 filed on Aug. 20, 2004, application No. 60/603,358 filed on Aug. 20, 2004, application Ser. No. 60/604,103 filed on Aug. 23, 2004, application Ser. No. 60/604,098 filed on Aug. 23, 2004, application Ser. No. 60/604,100 filed on Aug. 23, 2004, application Ser. No. 60/604,102 filed on Aug. 23, 2004, application Ser. No. 60/605,229 filed on Aug. 27, 2004, application Ser. No. 60/605,105 filed on Aug. 27, 2004, application No. 60/613,243 filed on Sep. 27, 2004, application Ser. No. 60/613,628 filed on Sep. 27, 2004, application Ser. No. 60/613,632 filed on Sep. 27, 2004, application Ser. No. 60/613,589 filed on Sep. 27, 2004, application Ser. No. 60/613,242 filed on Sep. 27, 2004, application No. 60/613,602 filed on Sep. 27, 2004, application Ser. No. 60/613,340 filed on Sep. 27, 2004, application Ser. No. 60/613,634 filed on Sep. 27, 2004, application Ser. No. 60/613,461 filed on Sep. 27, 2004, application Ser. No. 60/613,455 filed on Sep. 27, 2004, application No. 60/613,460 filed on Sep. 27, 2004, application Ser. No. 60/613,400 filed on Sep. 27, 2004, application Ser. No. 60/613,456 filed on Sep. 27, 2004, application Ser. No. 60/613,341 filed on Sep. 27, 2004, application Ser. No. 60/613,361 filed on Sep. 27, 2004, application Ser. No. 60/613,454 filed on Sep. 27, 2004, application Ser. No. 60/613,339 filed on Sep. 27, 2004, application Ser. No. 60/613,633 filed on Sep. 27, 2004, application Ser. No. 60/615,378 filed on Oct. 1, 2004, application Ser. No. 60/615,112 filed on Oct. 1, 2004, application Ser. No. 60/615,538 filed on Oct. 1, 2004, application Ser. No. 60/617,122 filed on Oct. 7, 2004, application No. 60/622,906 filed on Oct. 28, 2004, application Ser. No. 60/633,452 filed on Dec. 6, 2004, application Ser. No. 60/633,678 filed on Dec. 6, 2004, application Ser. No. 60/633,486 filed on Dec. 6, 2004, application Ser. No. 60/633,453 filed on Dec. 6, 2004, application No. 60/634,627 filed on Dec. 9, 2004, application Ser. No. 60/634,739 filed on Dec. 9, 2004, application Ser. No. 60/647,684 filed on Jan. 26, 2005, application Ser. No. 60/648,746 filed on Jan. 31, 2005, application Ser. No. 60/653,372 filed on Feb. 15, 2005, application Ser. No. 60/653,663 filed on Feb. 16, 2005, application Ser. No. 60/653,669 filed on Feb. 16, 2005, application No. 60/653,899 filed on Feb. 16, 2005, application Ser. No. 60/653,679 filed on Feb. 16, 2005, application Ser. No. 60/653,847 filed on Feb. 16, 2005, application Ser. No. 60/654,379 filed on Feb. 17, 2005, application Ser. No. 60/654,368 filed on Feb. 18, 2005, application No. 60/654,326 filed on Feb. 18, 2005, application Ser. No. 60/654,196 filed on Feb. 18, 2005, application Ser. No. 60/655,279 filed on Feb. 22, 2005, application Ser. No. 60/655,280 filed on Feb. 22, 2005, application Ser. No. 60/655,987 filed on Feb. 22, 2005, application Ser. No. 60/655,697 filed on Feb. 22, 2005, application Ser. No. 60/655,281 filed on Feb. 22, 2005, and application Ser. No. 60/657,309 filed on Feb. 28, 2005.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3899687 | Jones | Aug 1975 | A |
| 4052058 | Hintz | Oct 1977 | A |
| 4358824 | Glickman et al. | Nov 1982 | A |
| 4526078 | Chadabe | Jul 1985 | A |
| 4538072 | Immler et al. | Aug 1985 | A |
| 4553261 | Froessl | Nov 1985 | A |
| 4610025 | Blum et al. | Sep 1986 | A |
| 4633507 | Cannistra et al. | Dec 1986 | A |
| 4636848 | Yamamoto et al. | Jan 1987 | A |
| 4713008 | Stocker et al. | Dec 1987 | A |
| 4716804 | Chadabe | Jan 1988 | A |
| 4748678 | Takeda et al. | May 1988 | A |
| 4776464 | Miller et al. | Oct 1988 | A |
| 4804949 | Faulkerson | Feb 1989 | A |
| 4805099 | Huber | Feb 1989 | A |
| 4829453 | Katsuta et al. | May 1989 | A |
| 4829872 | Topic et al. | May 1989 | A |
| 4890230 | Tanoshima et al. | Dec 1989 | A |
| D306162 | Faulkerson et al. | Feb 1990 | S |
| 4901364 | Faulkerson et al. | Feb 1990 | A |
| 4903229 | Schmidt et al. | Feb 1990 | A |
| 4914709 | Rudak | Apr 1990 | A |
| 4941125 | Boyne | Jul 1990 | A |
| 4947261 | Ishikawa et al. | Aug 1990 | A |
| 4949391 | Faulkerson et al. | Aug 1990 | A |
| 4958379 | Yamaguchi et al. | Sep 1990 | A |
| 4968877 | McAvinney et al. | Nov 1990 | A |
| 4985863 | Fujisawa et al. | Jan 1991 | A |
| 4988981 | Zimmerman et al. | Jan 1991 | A |
| 5010500 | Makkuni et al. | Apr 1991 | A |
| 5012349 | de Fay et al. | Apr 1991 | A |
| 5062143 | Schmitt | Oct 1991 | A |
| 5083218 | Takasu et al. | Jan 1992 | A |
| 5093873 | Takahashi et al. | Mar 1992 | A |
| 5107256 | Ueno et al. | Apr 1992 | A |
| 5109439 | Froessl | Apr 1992 | A |
| 5119081 | Ikehira et al. | Jun 1992 | A |
| 5133024 | Froessl et al. | Jul 1992 | A |
| 5133052 | Bier et al. | Jul 1992 | A |
| 5136687 | Edelman et al. | Aug 1992 | A |
| 5142161 | Brackmann | Aug 1992 | A |
| 5146404 | Calloway et al. | Sep 1992 | A |
| 5146552 | Cassorla et al. | Sep 1992 | A |
| 5157384 | Greanias et al. | Oct 1992 | A |
| 5159668 | Kaasila | Oct 1992 | A |
| 5168147 | Bloomberg | Dec 1992 | A |
| 5168565 | Morita et al. | Dec 1992 | A |
| 5179652 | Rozmanith et al. | Jan 1993 | A |
| 5185857 | Rozmanith et al. | Feb 1993 | A |
| 5201010 | Deaton et al. | Apr 1993 | A |
| 5202985 | Goyal | Apr 1993 | A |
| 5203704 | McCloud | Apr 1993 | A |
| 5212739 | Johnson | May 1993 | A |
| 5229590 | Harden et al. | Jul 1993 | A |
| 5231698 | Forcier | Jul 1993 | A |
| 5243149 | Comerford et al. | Sep 1993 | A |
| 5247285 | Yokota et al. | Sep 1993 | A |
| 5251106 | Hui | Oct 1993 | A |
| 5251316 | Anick et al. | Oct 1993 | A |
| 5252951 | Tannenbaum et al. | Oct 1993 | A |
| RE34476 | Norwood | Dec 1993 | E |
| 5272324 | Blevins | Dec 1993 | A |
| 5288938 | Wheaton | Feb 1994 | A |
| 5301243 | Olschafskie et al. | Apr 1994 | A |
| 5347295 | Agulnick et al. | Sep 1994 | A |
| 5347306 | Nitta | Sep 1994 | A |
| 5347477 | Lee | Sep 1994 | A |
| 5355146 | Chiu et al. | Oct 1994 | A |
| 5360971 | Kaufman et al. | Nov 1994 | A |
| 5367453 | Capps et al. | Nov 1994 | A |
| 5371348 | Kumar et al. | Dec 1994 | A |
| 5377706 | Huang | Jan 1995 | A |
| 5398310 | Tchao et al. | Mar 1995 | A |
| 5404442 | Foster et al. | Apr 1995 | A |
| 5404458 | Zetts | Apr 1995 | A |
| 5418684 | Koenck et al. | May 1995 | A |
| 5418717 | Su et al. | May 1995 | A |
| 5418951 | Damashek | May 1995 | A |
| 5423554 | Davis | Jun 1995 | A |
| 5430558 | Sohaei et al. | Jul 1995 | A |
| 5438630 | Chen et al. | Aug 1995 | A |
| 5452442 | Kephart | Sep 1995 | A |
| 5454043 | Freeman | Sep 1995 | A |
| 5462473 | Sheller | Oct 1995 | A |
| 5465325 | Capps et al. | Nov 1995 | A |
| 5467425 | Lau et al. | Nov 1995 | A |
| 5481278 | Shigematsu et al. | Jan 1996 | A |
| 5485565 | Saund et al. | Jan 1996 | A |
| 5488196 | Zimmerman et al. | Jan 1996 | A |
| 5499108 | Cotte et al. | Mar 1996 | A |
| 5500920 | Kupiec | Mar 1996 | A |
| 5500937 | Thompson-Rohrlich | Mar 1996 | A |
| 5502803 | Yoshida et al. | Mar 1996 | A |
| 5512707 | Ohshima | Apr 1996 | A |
| 5517578 | Altman et al. | May 1996 | A |
| 5522798 | Johnson et al. | Jun 1996 | A |
| 5532469 | Shepard et al. | Jul 1996 | A |
| 5533141 | Futatsugi et al. | Jul 1996 | A |
| 5539427 | Bricklin et al. | Jul 1996 | A |
| 5541419 | Arackellian | Jul 1996 | A |
| 5543591 | Gillespie et al. | Aug 1996 | A |
| 5550930 | Berman et al. | Aug 1996 | A |
| 5555363 | Tou et al. | Sep 1996 | A |
| 5563996 | Tchao | Oct 1996 | A |
| 5568452 | Kronenberg | Oct 1996 | A |
| 5570113 | Zetts | Oct 1996 | A |
| 5574804 | Olschafskie et al. | Nov 1996 | A |
| 5581276 | Cipolla et al. | Dec 1996 | A |
| 5581670 | Bier et al. | Dec 1996 | A |
| 5581681 | Tchao et al. | Dec 1996 | A |
| 5583542 | Capps et al. | Dec 1996 | A |
| 5583543 | Takahashi et al. | Dec 1996 | A |
| 5583980 | Anderson | Dec 1996 | A |
| 5590219 | Gourdol | Dec 1996 | A |
| 5590256 | Tchao et al. | Dec 1996 | A |
| 5592566 | Pagallo et al. | Jan 1997 | A |
| 5594469 | Freeman et al. | Jan 1997 | A |
| 5594640 | Capps et al. | Jan 1997 | A |
| 5594810 | Gourdol | Jan 1997 | A |
| 5595445 | Bobry | Jan 1997 | A |
| 5596697 | Foster et al. | Jan 1997 | A |
| 5600765 | Ando et al. | Feb 1997 | A |
| 5602570 | Capps et al. | Feb 1997 | A |
| 5608778 | Partridge, III | Mar 1997 | A |
| 5612719 | Beernink et al. | Mar 1997 | A |
| 5624265 | Redford | Apr 1997 | A |
| 5625833 | Levine et al. | Apr 1997 | A |
| 5627960 | Clifford et al. | May 1997 | A |
| 5638092 | Eng et al. | Jun 1997 | A |
| 5649060 | Ellozy et al. | Jul 1997 | A |
| 5652849 | Conway et al. | Jul 1997 | A |
| 5656804 | Barkan et al. | Aug 1997 | A |
| 5659638 | Bengtson | Aug 1997 | A |
| 5663514 | Usa | Sep 1997 | A |
| 5663808 | Park et al. | Sep 1997 | A |
| 5668573 | Favot et al. | Sep 1997 | A |
| 5677710 | Thompson-Rohrlich | Oct 1997 | A |
| 5682439 | Beernink et al. | Oct 1997 | A |
| 5684873 | Tiilikainen | Nov 1997 | A |
| 5684891 | Tanaka et al. | Nov 1997 | A |
| 5687254 | Poon et al. | Nov 1997 | A |
| 5692073 | Cass | Nov 1997 | A |
| 5699441 | Sagawa et al. | Dec 1997 | A |
| 5701424 | Atkinson | Dec 1997 | A |
| 5701497 | Yamauchi et al. | Dec 1997 | A |
| 5708825 | Sotomayor | Jan 1998 | A |
| 5710831 | Beernink et al. | Jan 1998 | A |
| 5713045 | Berdahl | Jan 1998 | A |
| 5714698 | Tokioka et al. | Feb 1998 | A |
| 5717846 | Iida et al. | Feb 1998 | A |
| 5724521 | Dedrick | Mar 1998 | A |
| 5724985 | Snell et al. | Mar 1998 | A |
| 5732214 | Subrahmanyam | Mar 1998 | A |
| 5732227 | Kuzunuki et al. | Mar 1998 | A |
| 5734923 | Sagawa et al. | Mar 1998 | A |
| 5737507 | Smith | Apr 1998 | A |
| 5745116 | Pisutha-Arnond | Apr 1998 | A |
| 5748805 | Withgott et al. | May 1998 | A |
| 5748926 | Fukuda et al. | May 1998 | A |
| 5752051 | Cohen | May 1998 | A |
| 5754308 | Lopresti et al. | May 1998 | A |
| 5754939 | Herz et al. | May 1998 | A |
| 5756981 | Roustaei et al. | May 1998 | A |
| 5764794 | Perlin | Jun 1998 | A |
| 5767457 | Gerpheide et al. | Jun 1998 | A |
| 5768418 | Berman et al. | Jun 1998 | A |
| 5768607 | Drews et al. | Jun 1998 | A |
| 5774357 | Hoffberg et al. | Jun 1998 | A |
| 5774591 | Black et al. | Jun 1998 | A |
| 5777614 | Ando et al. | Jul 1998 | A |
| 5781662 | Mori et al. | Jul 1998 | A |
| 5781723 | Yee et al. | Jul 1998 | A |
| 5784061 | Moran et al. | Jul 1998 | A |
| 5784504 | Anderson et al. | Jul 1998 | A |
| 5796866 | Sakurai et al. | Aug 1998 | A |
| 5798693 | Engellenner | Aug 1998 | A |
| 5798758 | Harada et al. | Aug 1998 | A |
| 5799219 | Moghadam et al. | Aug 1998 | A |
| 5805167 | Van Cruyningen | Sep 1998 | A |
| 5809172 | Melen | Sep 1998 | A |
| 5809267 | Moran et al. | Sep 1998 | A |
| 5809476 | Ryan | Sep 1998 | A |
| 5818965 | Davies | Oct 1998 | A |
| 5821925 | Carey et al. | Oct 1998 | A |
| 5822539 | Van Hoff | Oct 1998 | A |
| 5825943 | DeVito et al. | Oct 1998 | A |
| 5832474 | Lopresti et al. | Nov 1998 | A |
| 5837987 | Koenck et al. | Nov 1998 | A |
| 5838326 | Card et al. | Nov 1998 | A |
| 5838889 | Booker | Nov 1998 | A |
| 5845301 | Rivette et al. | Dec 1998 | A |
| 5848187 | Bricklin et al. | Dec 1998 | A |
| 5852676 | Lazar | Dec 1998 | A |
| 5861886 | Moran et al. | Jan 1999 | A |
| 5862256 | Zetts et al. | Jan 1999 | A |
| 5862260 | Rhoads | Jan 1999 | A |
| 5864635 | Zetts et al. | Jan 1999 | A |
| 5864848 | Horvitz et al. | Jan 1999 | A |
| 5867150 | Bricklin et al. | Feb 1999 | A |
| 5867597 | Peairs et al. | Feb 1999 | A |
| 5867795 | Novis et al. | Feb 1999 | A |
| 5880411 | Gillespie et al. | Mar 1999 | A |
| 5880731 | Liles et al. | Mar 1999 | A |
| 5880743 | Moran et al. | Mar 1999 | A |
| 5884267 | Goldenthal et al. | Mar 1999 | A |
| 5889236 | Gillespie et al. | Mar 1999 | A |
| 5889523 | Wilcox et al. | Mar 1999 | A |
| 5889896 | Meshinsky et al. | Mar 1999 | A |
| 5890147 | Peltonen et al. | Mar 1999 | A |
| 5893095 | Jain et al. | Apr 1999 | A |
| 5893126 | Drews et al. | Apr 1999 | A |
| 5893130 | Inoue et al. | Apr 1999 | A |
| 5895470 | Pirolli et al. | Apr 1999 | A |
| 5905251 | Knowles | May 1999 | A |
| 5907328 | Brush, II et al. | May 1999 | A |
| 5913185 | Martino et al. | Jun 1999 | A |
| 5917491 | Bauersfeld | Jun 1999 | A |
| 5920477 | Hoffberg et al. | Jul 1999 | A |
| 5920694 | Carleton et al. | Jul 1999 | A |
| 5932863 | Rathus et al. | Aug 1999 | A |
| 5933829 | Durst et al. | Aug 1999 | A |
| 5937422 | Nelson et al. | Aug 1999 | A |
| 5946406 | Frink et al. | Aug 1999 | A |
| 5949921 | Kojima et al. | Sep 1999 | A |
| 5952599 | Dolby et al. | Sep 1999 | A |
| 5953541 | King et al. | Sep 1999 | A |
| 5956423 | Frink et al. | Sep 1999 | A |
| 5960383 | Fleischer | Sep 1999 | A |
| 5963966 | Mitchell et al. | Oct 1999 | A |
| 5966126 | Szabo | Oct 1999 | A |
| 5970455 | Wilcox et al. | Oct 1999 | A |
| 5982853 | Liebermann | Nov 1999 | A |
| 5982928 | Shimada et al. | Nov 1999 | A |
| 5982929 | Ilan et al. | Nov 1999 | A |
| 5983171 | Yokoyama et al. | Nov 1999 | A |
| 5983295 | Cotugno | Nov 1999 | A |
| 5986200 | Curtin | Nov 1999 | A |
| 5986655 | Chiu et al. | Nov 1999 | A |
| 5990878 | Ikeda et al. | Nov 1999 | A |
| 5990893 | Numazaki | Nov 1999 | A |
| 5991441 | Jourjine | Nov 1999 | A |
| 5995643 | Saito | Nov 1999 | A |
| 5999664 | Mahoney et al. | Dec 1999 | A |
| 6002798 | Palmer et al. | Dec 1999 | A |
| 6002808 | Freeman | Dec 1999 | A |
| 6003775 | Ackley | Dec 1999 | A |
| 6011905 | Huttenlocher et al. | Jan 2000 | A |
| 6012071 | Krishna et al. | Jan 2000 | A |
| 6018342 | Bristor | Jan 2000 | A |
| 6018346 | Moran et al. | Jan 2000 | A |
| 6021218 | Capps et al. | Feb 2000 | A |
| 6021403 | Horvitz et al. | Feb 2000 | A |
| 6025844 | Parsons | Feb 2000 | A |
| 6026388 | Liddy et al. | Feb 2000 | A |
| 6028271 | Gillespie et al. | Feb 2000 | A |
| 6029141 | Bezos et al. | Feb 2000 | A |
| 6029195 | Herz | Feb 2000 | A |
| 6031525 | Perlin | Feb 2000 | A |
| 6036086 | Sizer et al. | Mar 2000 | A |
| 6038342 | Bernzott et al. | Mar 2000 | A |
| 6040840 | Koshiba et al. | Mar 2000 | A |
| 6042012 | Olmstead et al. | Mar 2000 | A |
| 6044378 | Gladney | Mar 2000 | A |
| 6049034 | Cook | Apr 2000 | A |
| 6049327 | Walker et al. | Apr 2000 | A |
| 6052481 | Grajski et al. | Apr 2000 | A |
| 6053413 | Swift et al. | Apr 2000 | A |
| 6055333 | Guzik et al. | Apr 2000 | A |
| 6055513 | Katz et al. | Apr 2000 | A |
| 6057844 | Strauss | May 2000 | A |
| 6057845 | Dupouy | May 2000 | A |
| 6061050 | Allport et al. | May 2000 | A |
| 6064854 | Peters et al. | May 2000 | A |
| 6066794 | Longo | May 2000 | A |
| 6069622 | Kurlander | May 2000 | A |
| 6072494 | Nguyen | Jun 2000 | A |
| 6072502 | Gupta | Jun 2000 | A |
| 6075895 | Qiao et al. | Jun 2000 | A |
| 6078308 | Rosenberg et al. | Jun 2000 | A |
| 6081621 | Ackner | Jun 2000 | A |
| 6081629 | Browning | Jun 2000 | A |
| 6085162 | Cherny | Jul 2000 | A |
| 6088484 | Mead | Jul 2000 | A |
| 6088731 | Kiraly et al. | Jul 2000 | A |
| 6092038 | Kanevsky et al. | Jul 2000 | A |
| 6092068 | Dinkelacker | Jul 2000 | A |
| 6094689 | Embry et al. | Jul 2000 | A |
| 6095418 | Swartz et al. | Aug 2000 | A |
| 6097392 | Leyerle | Aug 2000 | A |
| 6098106 | Philyaw et al. | Aug 2000 | A |
| 6104401 | Parsons | Aug 2000 | A |
| 6104845 | Lipman et al. | Aug 2000 | A |
| 6107994 | Harada et al. | Aug 2000 | A |
| 6108656 | Durst et al. | Aug 2000 | A |
| 6111580 | Kazama et al. | Aug 2000 | A |
| 6111588 | Newell | Aug 2000 | A |
| 6115053 | Perlin | Sep 2000 | A |
| 6115482 | Sears et al. | Sep 2000 | A |
| 6115724 | Booker | Sep 2000 | A |
| 6118888 | Chino et al. | Sep 2000 | A |
| 6118899 | Bloomfield et al. | Sep 2000 | A |
| D432539 | Philyaw | Oct 2000 | S |
| 6128003 | Smith et al. | Oct 2000 | A |
| 6134532 | Lazarus et al. | Oct 2000 | A |
| 6138915 | Danielson et al. | Oct 2000 | A |
| 6140140 | Hopper | Oct 2000 | A |
| 6144366 | Numazaki et al. | Nov 2000 | A |
| 6147678 | Kumar et al. | Nov 2000 | A |
| 6151208 | Bartlett | Nov 2000 | A |
| 6154222 | Haratsch et al. | Nov 2000 | A |
| 6154723 | Cox et al. | Nov 2000 | A |
| 6154737 | Inaba et al. | Nov 2000 | A |
| 6154758 | Chiang | Nov 2000 | A |
| 6157465 | Suda et al. | Dec 2000 | A |
| 6157935 | Tran et al. | Dec 2000 | A |
| 6164534 | Rathus et al. | Dec 2000 | A |
| 6167369 | Schulze | Dec 2000 | A |
| 6169969 | Cohen | Jan 2001 | B1 |
| 6175772 | Kamiya et al. | Jan 2001 | B1 |
| 6175922 | Wang | Jan 2001 | B1 |
| 6178261 | Williams et al. | Jan 2001 | B1 |
| 6178263 | Fan et al. | Jan 2001 | B1 |
| 6181343 | Lyons | Jan 2001 | B1 |
| 6181778 | Ohki et al. | Jan 2001 | B1 |
| 6184847 | Fateh et al. | Feb 2001 | B1 |
| 6192165 | Irons | Feb 2001 | B1 |
| 6192478 | Elledge | Feb 2001 | B1 |
| 6195104 | Lyons | Feb 2001 | B1 |
| 6195475 | Beausoleil, Jr. et al. | Feb 2001 | B1 |
| 6199048 | Hudetz et al. | Mar 2001 | B1 |
| 6201903 | Wolff et al. | Mar 2001 | B1 |
| 6204852 | Kumar et al. | Mar 2001 | B1 |
| 6208355 | Schuster | Mar 2001 | B1 |
| 6208435 | Zwolinski | Mar 2001 | B1 |
| 6215890 | Matsuo et al. | Apr 2001 | B1 |
| 6218964 | Ellis | Apr 2001 | B1 |
| 6219057 | Carey et al. | Apr 2001 | B1 |
| 6222465 | Kumar et al. | Apr 2001 | B1 |
| 6226631 | Evans | May 2001 | B1 |
| 6229137 | Bohn | May 2001 | B1 |
| 6229542 | Miller | May 2001 | B1 |
| 6233591 | Sherman et al. | May 2001 | B1 |
| 6240207 | Shinozuka et al. | May 2001 | B1 |
| 6243683 | Peters | Jun 2001 | B1 |
| 6244873 | Hill et al. | Jun 2001 | B1 |
| 6249292 | Christian et al. | Jun 2001 | B1 |
| 6249606 | Kiraly et al. | Jun 2001 | B1 |
| 6252598 | Segen | Jun 2001 | B1 |
| 6256400 | Takata et al. | Jul 2001 | B1 |
| 6265844 | Wakefield | Jul 2001 | B1 |
| 6269187 | Frink et al. | Jul 2001 | B1 |
| 6269188 | Jamali | Jul 2001 | B1 |
| 6270013 | Lipman et al. | Aug 2001 | B1 |
| 6285794 | Georgiev et al. | Sep 2001 | B1 |
| 6289304 | Grefenstette et al. | Sep 2001 | B1 |
| 6292274 | Bohn | Sep 2001 | B1 |
| 6304674 | Cass et al. | Oct 2001 | B1 |
| 6307952 | Dietz | Oct 2001 | B1 |
| 6307955 | Zank et al. | Oct 2001 | B1 |
| 6310971 | Shiiyama et al. | Oct 2001 | B1 |
| 6310988 | Flores et al. | Oct 2001 | B1 |
| 6311152 | Bai et al. | Oct 2001 | B1 |
| 6312175 | Lum | Nov 2001 | B1 |
| 6313853 | Lamontagne et al. | Nov 2001 | B1 |
| 6314406 | O'Hagan et al. | Nov 2001 | B1 |
| 6314457 | Schena et al. | Nov 2001 | B1 |
| 6316710 | Lindemann | Nov 2001 | B1 |
| 6317132 | Perlin | Nov 2001 | B1 |
| 6318087 | Baumann et al. | Nov 2001 | B1 |
| 6321991 | Knowles | Nov 2001 | B1 |
| 6323846 | Westerman et al. | Nov 2001 | B1 |
| 6326962 | Szabo | Dec 2001 | B1 |
| 6330976 | Dymetman et al. | Dec 2001 | B1 |
| 6335725 | Koh et al. | Jan 2002 | B1 |
| 6341280 | Glass et al. | Jan 2002 | B1 |
| 6341290 | Lombardo et al. | Jan 2002 | B1 |
| 6344906 | Gatto et al. | Feb 2002 | B1 |
| 6346933 | Lin | Feb 2002 | B1 |
| 6347290 | Bartlett | Feb 2002 | B1 |
| 6349308 | Whang et al. | Feb 2002 | B1 |
| 6351222 | Swan et al. | Feb 2002 | B1 |
| 6356281 | Isenman | Mar 2002 | B1 |
| 6356899 | Chakrabarti et al. | Mar 2002 | B1 |
| 6360951 | Swinehart | Mar 2002 | B1 |
| 6363160 | Bradski et al. | Mar 2002 | B1 |
| RE37654 | Longo | Apr 2002 | E |
| 6366288 | Naruki et al. | Apr 2002 | B1 |
| 6369811 | Graham et al. | Apr 2002 | B1 |
| 6377296 | Zlatsin et al. | Apr 2002 | B1 |
| 6377712 | Georgiev et al. | Apr 2002 | B1 |
| 6377986 | Philyaw et al. | Apr 2002 | B1 |
| 6378075 | Goldstein et al. | Apr 2002 | B1 |
| 6380931 | Gillespie et al. | Apr 2002 | B1 |
| 6381602 | Shoroff et al. | Apr 2002 | B1 |
| 6384744 | Philyaw et al. | May 2002 | B1 |
| 6384829 | Prevost et al. | May 2002 | B1 |
| 6393443 | Rubin et al. | May 2002 | B1 |
| 6396523 | Segal et al. | May 2002 | B1 |
| 6396951 | Grefenstette et al. | May 2002 | B1 |
| 6400845 | Volino | Jun 2002 | B1 |
| 6404438 | Hatlelid et al. | Jun 2002 | B1 |
| 6408257 | Harrington et al. | Jun 2002 | B1 |
| 6409401 | Petteruti et al. | Jun 2002 | B1 |
| 6414671 | Gillespie et al. | Jul 2002 | B1 |
| 6417797 | Cousins et al. | Jul 2002 | B1 |
| 6418433 | Chakrabarti et al. | Jul 2002 | B1 |
| 6421453 | Kanevsky et al. | Jul 2002 | B1 |
| 6421675 | Ryan et al. | Jul 2002 | B1 |
| 6427032 | Irons et al. | Jul 2002 | B1 |
| 6429899 | Nio et al. | Aug 2002 | B1 |
| 6430554 | Rothschild | Aug 2002 | B1 |
| 6430567 | Burridge | Aug 2002 | B2 |
| 6433784 | Merrick et al. | Aug 2002 | B1 |
| 6434561 | Durst, Jr. et al. | Aug 2002 | B1 |
| 6434581 | Forcier | Aug 2002 | B1 |
| 6438523 | Oberteuffer et al. | Aug 2002 | B1 |
| 6448979 | Schena et al. | Sep 2002 | B1 |
| 6449616 | Walker et al. | Sep 2002 | B1 |
| 6454626 | An | Sep 2002 | B1 |
| 6459823 | Altunbasak et al. | Oct 2002 | B2 |
| 6460036 | Herz | Oct 2002 | B1 |
| 6466198 | Feinstein | Oct 2002 | B1 |
| 6466336 | Sturgeon et al. | Oct 2002 | B1 |
| 6476830 | Farmer et al. | Nov 2002 | B1 |
| 6476834 | Doval et al. | Nov 2002 | B1 |
| 6477239 | Ohki et al. | Nov 2002 | B1 |
| 6483513 | Haratsch et al. | Nov 2002 | B1 |
| 6484156 | Gupta et al. | Nov 2002 | B1 |
| 6486874 | Muthuswamy et al. | Nov 2002 | B1 |
| 6486892 | Stern | Nov 2002 | B1 |
| 6489970 | Pazel | Dec 2002 | B1 |
| 6490553 | Van Thong et al. | Dec 2002 | B2 |
| 6491217 | Catan | Dec 2002 | B2 |
| 6493707 | Dey et al. | Dec 2002 | B1 |
| 6498970 | Colmenarez et al. | Dec 2002 | B2 |
| 6504138 | Mangerson | Jan 2003 | B1 |
| 6507349 | Balassanian | Jan 2003 | B1 |
| 6508706 | Sitrick et al. | Jan 2003 | B2 |
| 6509707 | Yamashita et al. | Jan 2003 | B2 |
| 6509912 | Moran et al. | Jan 2003 | B1 |
| 6510387 | Fuchs et al. | Jan 2003 | B2 |
| 6510417 | Woods et al. | Jan 2003 | B1 |
| 6518950 | Dougherty et al. | Feb 2003 | B1 |
| 6520407 | Nieswand et al. | Feb 2003 | B1 |
| 6522333 | Hatlelid et al. | Feb 2003 | B1 |
| 6525749 | Moran et al. | Feb 2003 | B1 |
| 6526395 | Morris | Feb 2003 | B1 |
| 6526449 | Philyaw et al. | Feb 2003 | B1 |
| 6532007 | Matsuda | Mar 2003 | B1 |
| 6537324 | Tabata et al. | Mar 2003 | B1 |
| 6538187 | Beigi | Mar 2003 | B2 |
| 6539931 | Trajkovic et al. | Apr 2003 | B2 |
| 6540141 | Dougherty et al. | Apr 2003 | B1 |
| 6542933 | Durst, Jr. et al. | Apr 2003 | B1 |
| 6543052 | Ogasawara | Apr 2003 | B1 |
| 6545669 | Kinawi et al. | Apr 2003 | B1 |
| 6546385 | Mao et al. | Apr 2003 | B1 |
| 6546405 | Gupta et al. | Apr 2003 | B2 |
| 6549751 | Mandri | Apr 2003 | B1 |
| 6549891 | Rauber et al. | Apr 2003 | B1 |
| 6554433 | Holler | Apr 2003 | B1 |
| 6560281 | Black et al. | May 2003 | B1 |
| 6564144 | Cherveny | May 2003 | B1 |
| 6570555 | Prevost et al. | May 2003 | B1 |
| 6571193 | Unuma et al. | May 2003 | B1 |
| 6571235 | Marpe et al. | May 2003 | B1 |
| 6573883 | Bartlett | Jun 2003 | B1 |
| 6577329 | Flickner et al. | Jun 2003 | B1 |
| 6577953 | Swope et al. | Jun 2003 | B1 |
| 6587835 | Treyz et al. | Jul 2003 | B1 |
| 6593723 | Johnson | Jul 2003 | B1 |
| 6594616 | Zhang et al. | Jul 2003 | B2 |
| 6594705 | Philyaw | Jul 2003 | B1 |
| 6597443 | Boman | Jul 2003 | B2 |
| 6597812 | Fallon et al. | Jul 2003 | B1 |
| 6599130 | Moehrle | Jul 2003 | B2 |
| 6600475 | Gutta et al. | Jul 2003 | B2 |
| 6610936 | Gillespie et al. | Aug 2003 | B2 |
| 6611598 | Hayosh | Aug 2003 | B1 |
| 6615136 | Swope et al. | Sep 2003 | B1 |
| 6615268 | Philyaw et al. | Sep 2003 | B1 |
| 6616038 | Olschafskie et al. | Sep 2003 | B1 |
| 6617369 | Parfondry et al. | Sep 2003 | B2 |
| 6618504 | Yoshino et al. | Sep 2003 | B1 |
| 6618732 | White et al. | Sep 2003 | B1 |
| 6622165 | Philyaw | Sep 2003 | B1 |
| 6624833 | Kumar et al. | Sep 2003 | B1 |
| 6625335 | Kanai | Sep 2003 | B1 |
| 6625581 | Perkowski | Sep 2003 | B1 |
| 6628295 | Wilensky | Sep 2003 | B2 |
| 6629133 | Philyaw et al. | Sep 2003 | B1 |
| 6630924 | Peck | Oct 2003 | B1 |
| 6631404 | Philyaw | Oct 2003 | B1 |
| 6636763 | Junker et al. | Oct 2003 | B1 |
| 6636892 | Philyaw | Oct 2003 | B1 |
| 6636896 | Philyaw | Oct 2003 | B1 |
| 6638314 | Meyerzon et al. | Oct 2003 | B1 |
| 6638317 | Nakao et al. | Oct 2003 | B2 |
| 6640145 | Hoffberg et al. | Oct 2003 | B2 |
| 6641037 | Williams | Nov 2003 | B2 |
| 6643692 | Philyaw et al. | Nov 2003 | B1 |
| 6643696 | Davis et al. | Nov 2003 | B2 |
| 6650761 | Rodriguez et al. | Nov 2003 | B1 |
| 6651053 | Rothschild | Nov 2003 | B1 |
| 6658151 | Lee et al. | Dec 2003 | B2 |
| 6661919 | Nicholson et al. | Dec 2003 | B2 |
| 6664991 | Chew et al. | Dec 2003 | B1 |
| 6669088 | Veeneman | Dec 2003 | B2 |
| 6671684 | Hull et al. | Dec 2003 | B1 |
| 6677969 | Hongo | Jan 2004 | B1 |
| 6678075 | Tsai et al. | Jan 2004 | B1 |
| 6678664 | Ganesan | Jan 2004 | B1 |
| 6678687 | Watanabe et al. | Jan 2004 | B2 |
| 6681031 | Cohen et al. | Jan 2004 | B2 |
| 6686844 | Watanabe et al. | Feb 2004 | B2 |
| 6687612 | Cherveny | Feb 2004 | B2 |
| 6688081 | Boyd | Feb 2004 | B2 |
| 6688522 | Philyaw et al. | Feb 2004 | B1 |
| 6688523 | Koenck | Feb 2004 | B1 |
| 6688525 | Nelson et al. | Feb 2004 | B1 |
| 6690358 | Kaplan | Feb 2004 | B2 |
| 6691107 | Dockter et al. | Feb 2004 | B1 |
| 6691123 | Gulliksen | Feb 2004 | B1 |
| 6691151 | Cheyer et al. | Feb 2004 | B1 |
| 6691194 | Ofer | Feb 2004 | B1 |
| 6691914 | Isherwood et al. | Feb 2004 | B2 |
| 6692259 | Kumar et al. | Feb 2004 | B2 |
| 6694356 | Philyaw | Feb 2004 | B1 |
| 6697838 | Jakobson | Feb 2004 | B1 |
| 6697949 | Philyaw et al. | Feb 2004 | B1 |
| H2098 | Morin | Mar 2004 | H |
| 6701354 | Philyaw et al. | Mar 2004 | B1 |
| 6701369 | Philyaw | Mar 2004 | B1 |
| 6704024 | Robotham et al. | Mar 2004 | B2 |
| 6704699 | Nir et al. | Mar 2004 | B2 |
| 6707581 | Browning | Mar 2004 | B1 |
| 6708208 | Philyaw | Mar 2004 | B1 |
| 6714677 | Stearns et al. | Mar 2004 | B1 |
| 6714969 | Klein et al. | Mar 2004 | B1 |
| 6718308 | Nolting | Apr 2004 | B1 |
| 6720984 | Jorgensen et al. | Apr 2004 | B1 |
| 6721921 | Altman | Apr 2004 | B1 |
| 6725125 | Basson et al. | Apr 2004 | B2 |
| 6725203 | Seet et al. | Apr 2004 | B1 |
| 6725260 | Philyaw | Apr 2004 | B1 |
| 6728000 | Lapstun et al. | Apr 2004 | B1 |
| 6735632 | Kiraly et al. | May 2004 | B1 |
| 6738519 | Nishiwaki | May 2004 | B1 |
| 6741745 | Dance et al. | May 2004 | B2 |
| 6744938 | Rantze et al. | Jun 2004 | B1 |
| 6745234 | Philyaw et al. | Jun 2004 | B1 |
| 6745937 | Walsh et al. | Jun 2004 | B2 |
| 6747632 | Howard | Jun 2004 | B2 |
| 6748306 | Lipowicz | Jun 2004 | B2 |
| 6750852 | Gillespie et al. | Jun 2004 | B2 |
| 6752498 | Covannon et al. | Jun 2004 | B2 |
| 6753883 | Schena et al. | Jun 2004 | B2 |
| 6754632 | Kalinowski et al. | Jun 2004 | B1 |
| 6754698 | Philyaw et al. | Jun 2004 | B1 |
| 6757715 | Philyaw | Jun 2004 | B1 |
| 6757783 | Koh | Jun 2004 | B2 |
| 6758398 | Philyaw et al. | Jul 2004 | B1 |
| 6760661 | Klein et al. | Jul 2004 | B2 |
| 6766494 | Price et al. | Jul 2004 | B1 |
| 6766956 | Boylan, III et al. | Jul 2004 | B1 |
| 6772047 | Butikofer | Aug 2004 | B2 |
| 6772338 | Hull | Aug 2004 | B1 |
| 6773177 | Denoue et al. | Aug 2004 | B2 |
| 6775422 | Altman | Aug 2004 | B1 |
| 6778988 | Bengtson | Aug 2004 | B2 |
| 6783071 | Levine et al. | Aug 2004 | B2 |
| 6785421 | Gindele et al. | Aug 2004 | B1 |
| 6786793 | Wang | Sep 2004 | B1 |
| 6788809 | Grzeszczuk et al. | Sep 2004 | B1 |
| 6788815 | Lui et al. | Sep 2004 | B2 |
| 6791536 | Keely et al. | Sep 2004 | B2 |
| 6791588 | Philyaw | Sep 2004 | B1 |
| 6792112 | Campbell et al. | Sep 2004 | B1 |
| 6792452 | Philyaw | Sep 2004 | B1 |
| 6798429 | Bradski | Sep 2004 | B2 |
| 6801637 | Voronka et al. | Oct 2004 | B2 |
| 6801658 | Morita et al. | Oct 2004 | B2 |
| 6801907 | Zagami | Oct 2004 | B1 |
| 6804396 | Higaki et al. | Oct 2004 | B2 |
| 6804659 | Graham et al. | Oct 2004 | B1 |
| 6813039 | Silverbrook et al. | Nov 2004 | B1 |
| 6816894 | Philyaw et al. | Nov 2004 | B1 |
| 6820237 | Abu-Hakima et al. | Nov 2004 | B1 |
| 6822639 | Silverbrook et al. | Nov 2004 | B1 |
| 6823075 | Perry | Nov 2004 | B2 |
| 6823388 | Philyaw et al. | Nov 2004 | B1 |
| 6824044 | Lapstun et al. | Nov 2004 | B1 |
| 6824057 | Rathus et al. | Nov 2004 | B2 |
| 6825956 | Silverbrook et al. | Nov 2004 | B2 |
| 6826592 | Philyaw et al. | Nov 2004 | B1 |
| 6827259 | Rathus et al. | Dec 2004 | B2 |
| 6827267 | Rathus et al. | Dec 2004 | B2 |
| 6829650 | Philyaw et al. | Dec 2004 | B1 |
| 6830187 | Rathus et al. | Dec 2004 | B2 |
| 6830188 | Rathus et al. | Dec 2004 | B2 |
| 6832116 | Tillgren et al. | Dec 2004 | B1 |
| 6833936 | Seymour | Dec 2004 | B1 |
| 6834804 | Rathus et al. | Dec 2004 | B2 |
| 6836799 | Philyaw et al. | Dec 2004 | B1 |
| 6845913 | Madding et al. | Jan 2005 | B2 |
| 6850252 | Hoffberg | Feb 2005 | B1 |
| 6862046 | Ko | Mar 2005 | B2 |
| 6868193 | Gharbia et al. | Mar 2005 | B1 |
| 6877001 | Wolf et al. | Apr 2005 | B2 |
| 6879957 | Pechter et al. | Apr 2005 | B1 |
| 6880122 | Lee et al. | Apr 2005 | B1 |
| 6880124 | Moore | Apr 2005 | B1 |
| 6886104 | McClurg et al. | Apr 2005 | B1 |
| 6892264 | Lamb | May 2005 | B2 |
| 6898592 | Peltonen et al. | May 2005 | B2 |
| 6917722 | Bloomfield | Jul 2005 | B1 |
| 6917724 | Seder et al. | Jul 2005 | B2 |
| 6922725 | Lamming et al. | Jul 2005 | B2 |
| 6925182 | Epstein | Aug 2005 | B1 |
| 6931592 | Ramaley et al. | Aug 2005 | B1 |
| 6938024 | Horvitz | Aug 2005 | B1 |
| 6947571 | Rhoads et al. | Sep 2005 | B1 |
| 6947930 | Anick et al. | Sep 2005 | B2 |
| 6957384 | Jeffery et al. | Oct 2005 | B2 |
| 6970915 | Partovi et al. | Nov 2005 | B1 |
| 6978297 | Piersol | Dec 2005 | B1 |
| 6985169 | Deng et al. | Jan 2006 | B1 |
| 6990548 | Kaylor | Jan 2006 | B1 |
| 6991158 | Munte | Jan 2006 | B2 |
| 6992655 | Ericson et al. | Jan 2006 | B2 |
| 6993580 | Isherwood et al. | Jan 2006 | B2 |
| 7001681 | Wood | Feb 2006 | B2 |
| 7006881 | Hoffberg | Feb 2006 | B1 |
| 7010616 | Carlson et al. | Mar 2006 | B2 |
| 7016084 | Tsai | Mar 2006 | B2 |
| 7020663 | Hay et al. | Mar 2006 | B2 |
| 7043489 | Kelley | May 2006 | B1 |
| 7047491 | Schubert et al. | May 2006 | B2 |
| 7051943 | Leone et al. | May 2006 | B2 |
| 7057607 | Mayoraz et al. | Jun 2006 | B2 |
| 7058223 | Cox | Jun 2006 | B2 |
| 7062437 | Kovales et al. | Jun 2006 | B2 |
| 7062706 | Maxwell et al. | Jun 2006 | B2 |
| 7069240 | Spero et al. | Jun 2006 | B2 |
| 7069272 | Sndyer | Jun 2006 | B2 |
| 7079713 | Simmons | Jul 2006 | B2 |
| 7093759 | Walsh | Aug 2006 | B2 |
| 7096218 | Schirmer et al. | Aug 2006 | B2 |
| 7103848 | Barsness et al. | Sep 2006 | B2 |
| 7110576 | Norris, Jr. et al. | Sep 2006 | B2 |
| 7111787 | Ehrhart | Sep 2006 | B2 |
| 7117374 | Hill et al. | Oct 2006 | B2 |
| 7121469 | Dorai et al. | Oct 2006 | B2 |
| 7124093 | Graham et al. | Oct 2006 | B1 |
| 7130885 | Chandra et al. | Oct 2006 | B2 |
| 7131061 | MacLean et al. | Oct 2006 | B2 |
| 7133862 | Hubert et al. | Nov 2006 | B2 |
| 7136814 | McConnell | Nov 2006 | B1 |
| 7137077 | Iwema et al. | Nov 2006 | B2 |
| 7139445 | Pilu et al. | Nov 2006 | B2 |
| 7151864 | Henry et al. | Dec 2006 | B2 |
| 7165268 | Moore et al. | Jan 2007 | B1 |
| 7167586 | Braun et al. | Jan 2007 | B2 |
| 7174054 | Manber et al. | Feb 2007 | B2 |
| 7174332 | Baxter et al. | Feb 2007 | B2 |
| 7185275 | Roberts et al. | Feb 2007 | B2 |
| 7188307 | Ohsawa | Mar 2007 | B2 |
| 7190480 | Sturgeon et al. | Mar 2007 | B2 |
| 7197716 | Newell et al. | Mar 2007 | B2 |
| 7203158 | Oshima et al. | Apr 2007 | B2 |
| 7216224 | Lapstun et al. | May 2007 | B2 |
| 7224480 | Tanaka et al. | May 2007 | B2 |
| 7224820 | Inomata et al. | May 2007 | B2 |
| 7225979 | Silverbrook et al. | Jun 2007 | B2 |
| 7234645 | Silverbrook et al. | Jun 2007 | B2 |
| 7240843 | Paul et al. | Jul 2007 | B2 |
| 7242492 | Currans et al. | Jul 2007 | B2 |
| 7246118 | Chastain et al. | Jul 2007 | B2 |
| 7260534 | Gandhi et al. | Aug 2007 | B2 |
| 7262798 | Stavely et al. | Aug 2007 | B2 |
| 7263521 | Carpentier et al. | Aug 2007 | B2 |
| 7275049 | Clausner et al. | Sep 2007 | B2 |
| 7283992 | Liu et al. | Oct 2007 | B2 |
| 7284192 | Kashi et al. | Oct 2007 | B2 |
| 7289806 | Morris et al. | Oct 2007 | B2 |
| 7295101 | Ward et al. | Nov 2007 | B2 |
| 7299186 | Kuzunuki et al. | Nov 2007 | B2 |
| 7299969 | Paul et al. | Nov 2007 | B2 |
| 7331523 | Meier et al. | Feb 2008 | B2 |
| 7339467 | Lamb | Mar 2008 | B2 |
| 7349552 | Levy et al. | Mar 2008 | B2 |
| 7353199 | DiStefano, III | Apr 2008 | B1 |
| 7376581 | DeRose et al. | May 2008 | B2 |
| 7383263 | Goger | Jun 2008 | B2 |
| 7392287 | Ratcliff, III | Jun 2008 | B2 |
| 7392475 | Leban et al. | Jun 2008 | B1 |
| 7404520 | Vesuna | Jul 2008 | B2 |
| 7409434 | Lamming et al. | Aug 2008 | B2 |
| 7412158 | Kakkori | Aug 2008 | B2 |
| 7415670 | Hull et al. | Aug 2008 | B2 |
| 7421155 | King et al. | Sep 2008 | B2 |
| 7424543 | Rice, III | Sep 2008 | B2 |
| 7426486 | Treibach-Heck et al. | Sep 2008 | B2 |
| 7433068 | Stevens et al. | Oct 2008 | B2 |
| 7433893 | Lowry | Oct 2008 | B2 |
| 7437023 | King et al. | Oct 2008 | B2 |
| 7487112 | Barnes, Jr. | Feb 2009 | B2 |
| 7493487 | Phillips et al. | Feb 2009 | B2 |
| 7496638 | Philyaw | Feb 2009 | B2 |
| 7505785 | Callaghan et al. | Mar 2009 | B2 |
| 7505956 | Ibbotson | Mar 2009 | B2 |
| 7512254 | Vollkommer et al. | Mar 2009 | B2 |
| 7523067 | Nakajima | Apr 2009 | B1 |
| 7533040 | Perkowski | May 2009 | B2 |
| 7536547 | Van Den Tillaart | May 2009 | B2 |
| 7552075 | Walsh | Jun 2009 | B1 |
| 7552381 | Barrus | Jun 2009 | B2 |
| 7587412 | Weyl et al. | Sep 2009 | B2 |
| 7591597 | Pasqualini et al. | Sep 2009 | B2 |
| 7593605 | King et al. | Sep 2009 | B2 |
| 7596269 | King et al. | Sep 2009 | B2 |
| 7599580 | King et al. | Oct 2009 | B2 |
| 7599844 | King et al. | Oct 2009 | B2 |
| 7606741 | King et al. | Oct 2009 | B2 |
| 7613634 | Siegel et al. | Nov 2009 | B2 |
| 7616840 | Erol et al. | Nov 2009 | B2 |
| 7660813 | Milic-Frayling et al. | Feb 2010 | B2 |
| 7664734 | Lawrence et al. | Feb 2010 | B2 |
| 7672543 | Hull et al. | Mar 2010 | B2 |
| 7680067 | Prasad et al. | Mar 2010 | B2 |
| 7689712 | Lee et al. | Mar 2010 | B2 |
| 7689832 | Talmor et al. | Mar 2010 | B2 |
| 7698344 | Sareen et al. | Apr 2010 | B2 |
| 7702624 | King et al. | Apr 2010 | B2 |
| 7706611 | King et al. | Apr 2010 | B2 |
| 7707039 | King et al. | Apr 2010 | B2 |
| 7710598 | Harrison, Jr. | May 2010 | B2 |
| 7742953 | King et al. | Jun 2010 | B2 |
| 7788248 | Forstall et al. | Aug 2010 | B2 |
| 7796116 | Salsman et al. | Sep 2010 | B2 |
| 7806322 | Brundage et al. | Oct 2010 | B2 |
| 7812860 | King et al. | Oct 2010 | B2 |
| 7818215 | King et al. | Oct 2010 | B2 |
| 7831912 | King et al. | Nov 2010 | B2 |
| 7872669 | Darrell et al. | Jan 2011 | B2 |
| 7894670 | King et al. | Feb 2011 | B2 |
| 20010001854 | Schena et al. | May 2001 | A1 |
| 20010003176 | Schena et al. | Jun 2001 | A1 |
| 20010003177 | Schena et al. | Jun 2001 | A1 |
| 20010032252 | Durst et al. | Oct 2001 | A1 |
| 20010034237 | Garahi | Oct 2001 | A1 |
| 20010049636 | Hudda et al. | Dec 2001 | A1 |
| 20010053252 | Creque | Dec 2001 | A1 |
| 20010056463 | Grady et al. | Dec 2001 | A1 |
| 20020002504 | Engel et al. | Jan 2002 | A1 |
| 20020012065 | Watanabe | Jan 2002 | A1 |
| 20020013781 | Petersen | Jan 2002 | A1 |
| 20020016750 | Attia | Feb 2002 | A1 |
| 20020020750 | Dymetman et al. | Feb 2002 | A1 |
| 20020022993 | Miller et al. | Feb 2002 | A1 |
| 20020023158 | Polizzi et al. | Feb 2002 | A1 |
| 20020023215 | Wang et al. | Feb 2002 | A1 |
| 20020023957 | Michaelis et al. | Feb 2002 | A1 |
| 20020023959 | Miller et al. | Feb 2002 | A1 |
| 20020029350 | Cooper et al. | Mar 2002 | A1 |
| 20020038456 | Hansen et al. | Mar 2002 | A1 |
| 20020049781 | Bengtson | Apr 2002 | A1 |
| 20020051262 | Nuttall et al. | May 2002 | A1 |
| 20020052747 | Sarukkai | May 2002 | A1 |
| 20020055906 | Katz et al. | May 2002 | A1 |
| 20020055919 | Mikheev | May 2002 | A1 |
| 20020067308 | Robertson | Jun 2002 | A1 |
| 20020073000 | Sage | Jun 2002 | A1 |
| 20020075298 | Schena et al. | Jun 2002 | A1 |
| 20020076110 | Zee | Jun 2002 | A1 |
| 20020087598 | Carro | Jul 2002 | A1 |
| 20020090132 | Boncyk et al. | Jul 2002 | A1 |
| 20020091569 | Kitaura et al. | Jul 2002 | A1 |
| 20020091928 | Bouchard et al. | Jul 2002 | A1 |
| 20020099812 | Davis et al. | Jul 2002 | A1 |
| 20020102966 | Lev et al. | Aug 2002 | A1 |
| 20020133725 | Roy et al. | Sep 2002 | A1 |
| 20020135815 | Finn | Sep 2002 | A1 |
| 20020139859 | Catan | Oct 2002 | A1 |
| 20020161658 | Sussman | Oct 2002 | A1 |
| 20020191847 | Newman et al. | Dec 2002 | A1 |
| 20020194143 | Banerjee et al. | Dec 2002 | A1 |
| 20020199198 | Stonedahl | Dec 2002 | A1 |
| 20030001018 | Hussey et al. | Jan 2003 | A1 |
| 20030004724 | Kahn et al. | Jan 2003 | A1 |
| 20030009495 | Adjaoute | Jan 2003 | A1 |
| 20030019939 | Sellen | Jan 2003 | A1 |
| 20030028889 | McCoskey et al. | Feb 2003 | A1 |
| 20030040957 | Rodriguez et al. | Feb 2003 | A1 |
| 20030043042 | Moores, Jr. et al. | Mar 2003 | A1 |
| 20030046307 | Rivette et al. | Mar 2003 | A1 |
| 20030050854 | Showghi et al. | Mar 2003 | A1 |
| 20030065770 | Davis et al. | Apr 2003 | A1 |
| 20030093384 | Durst et al. | May 2003 | A1 |
| 20030093400 | Santosuosso | May 2003 | A1 |
| 20030093545 | Liu et al. | May 2003 | A1 |
| 20030098352 | Schnee et al. | May 2003 | A1 |
| 20030106018 | Silverbrook et al. | Jun 2003 | A1 |
| 20030130904 | Katz et al. | Jul 2003 | A1 |
| 20030132298 | Swartz et al. | Jul 2003 | A1 |
| 20030144865 | Lin et al. | Jul 2003 | A1 |
| 20030150907 | Metcalf et al. | Aug 2003 | A1 |
| 20030152293 | Bresler et al. | Aug 2003 | A1 |
| 20030160975 | Skurdal et al. | Aug 2003 | A1 |
| 20030173405 | Wilz, Sr. et al. | Sep 2003 | A1 |
| 20030179908 | Mahoney et al. | Sep 2003 | A1 |
| 20030187751 | Watson et al. | Oct 2003 | A1 |
| 20030187886 | Hull et al. | Oct 2003 | A1 |
| 20030195851 | Ong | Oct 2003 | A1 |
| 20030200152 | Divekar | Oct 2003 | A1 |
| 20030214528 | Pierce et al. | Nov 2003 | A1 |
| 20030218070 | Tsikos et al. | Nov 2003 | A1 |
| 20030220835 | Barnes, Jr. | Nov 2003 | A1 |
| 20030223637 | Simske et al. | Dec 2003 | A1 |
| 20030225547 | Paradies | Dec 2003 | A1 |
| 20040001217 | Wu | Jan 2004 | A1 |
| 20040015437 | Choi et al. | Jan 2004 | A1 |
| 20040015606 | Philyaw | Jan 2004 | A1 |
| 20040036718 | Warren et al. | Feb 2004 | A1 |
| 20040042667 | Lee et al. | Mar 2004 | A1 |
| 20040044576 | Kurihara et al. | Mar 2004 | A1 |
| 20040044627 | Russell et al. | Mar 2004 | A1 |
| 20040044952 | Jiang et al. | Mar 2004 | A1 |
| 20040052400 | Inomata et al. | Mar 2004 | A1 |
| 20040059779 | Philyaw | Mar 2004 | A1 |
| 20040064453 | Ruiz et al. | Apr 2004 | A1 |
| 20040068483 | Sakurai et al. | Apr 2004 | A1 |
| 20040073708 | Warnock | Apr 2004 | A1 |
| 20040073874 | Poibeau et al. | Apr 2004 | A1 |
| 20040075686 | Watler et al. | Apr 2004 | A1 |
| 20040078749 | Hull et al. | Apr 2004 | A1 |
| 20040098165 | Butikofer | May 2004 | A1 |
| 20040121815 | Fournier et al. | Jun 2004 | A1 |
| 20040122811 | Page | Jun 2004 | A1 |
| 20040128514 | Rhoads | Jul 2004 | A1 |
| 20040139400 | Allam et al. | Jul 2004 | A1 |
| 20040158492 | Lopez et al. | Aug 2004 | A1 |
| 20040181688 | Wittkotter | Sep 2004 | A1 |
| 20040186766 | Fellenstein et al. | Sep 2004 | A1 |
| 20040186859 | Butcher | Sep 2004 | A1 |
| 20040193488 | Khoo et al. | Sep 2004 | A1 |
| 20040199615 | Philyaw | Oct 2004 | A1 |
| 20040205534 | Koelle | Oct 2004 | A1 |
| 20040206809 | Wood et al. | Oct 2004 | A1 |
| 20040208369 | Nakayama | Oct 2004 | A1 |
| 20040208372 | Boncyk et al. | Oct 2004 | A1 |
| 20040210943 | Philyaw | Oct 2004 | A1 |
| 20040217160 | Silverbrook et al. | Nov 2004 | A1 |
| 20040220975 | Carpentier et al. | Nov 2004 | A1 |
| 20040229194 | Yang | Nov 2004 | A1 |
| 20040230837 | Philyaw et al. | Nov 2004 | A1 |
| 20040243601 | Toshima | Dec 2004 | A1 |
| 20040250201 | Caspi | Dec 2004 | A1 |
| 20040254795 | Fujii et al. | Dec 2004 | A1 |
| 20040256454 | Kocher | Dec 2004 | A1 |
| 20040258274 | Brundage et al. | Dec 2004 | A1 |
| 20040258275 | Rhoads | Dec 2004 | A1 |
| 20040260470 | Rast | Dec 2004 | A1 |
| 20040260618 | Larson | Dec 2004 | A1 |
| 20040267734 | Toshima | Dec 2004 | A1 |
| 20040268237 | Jones et al. | Dec 2004 | A1 |
| 20050005168 | Dick | Jan 2005 | A1 |
| 20050033713 | Bala et al. | Feb 2005 | A1 |
| 20050076095 | Mathew et al. | Apr 2005 | A1 |
| 20050086309 | Galli et al. | Apr 2005 | A1 |
| 20050097335 | Shenoy et al. | May 2005 | A1 |
| 20050136949 | Barnes, Jr. | Jun 2005 | A1 |
| 20050139649 | Metcalf et al. | Jun 2005 | A1 |
| 20050144074 | Fredregill et al. | Jun 2005 | A1 |
| 20050149516 | Wolf et al. | Jul 2005 | A1 |
| 20050149538 | Singh et al. | Jul 2005 | A1 |
| 20050154760 | Bhakta et al. | Jul 2005 | A1 |
| 20050220359 | Sun et al. | Oct 2005 | A1 |
| 20050222801 | Wulff et al. | Oct 2005 | A1 |
| 20050228683 | Saylor et al. | Oct 2005 | A1 |
| 20050231746 | Parry et al. | Oct 2005 | A1 |
| 20050278179 | Overend et al. | Dec 2005 | A1 |
| 20050288954 | McCarthy et al. | Dec 2005 | A1 |
| 20050289054 | Silverbrook et al. | Dec 2005 | A1 |
| 20060023945 | King et al. | Feb 2006 | A1 |
| 20060036462 | King et al. | Feb 2006 | A1 |
| 20060041484 | King et al. | Feb 2006 | A1 |
| 20060041538 | King et al. | Feb 2006 | A1 |
| 20060041605 | King et al. | Feb 2006 | A1 |
| 20060045374 | Kim et al. | Mar 2006 | A1 |
| 20060053097 | King et al. | Mar 2006 | A1 |
| 20060069616 | Bau | Mar 2006 | A1 |
| 20060075327 | Sriver et al. | Apr 2006 | A1 |
| 20060080314 | Hubert et al. | Apr 2006 | A1 |
| 20060081714 | King et al. | Apr 2006 | A1 |
| 20060085477 | Phillips et al. | Apr 2006 | A1 |
| 20060098900 | King et al. | May 2006 | A1 |
| 20060104515 | King et al. | May 2006 | A1 |
| 20060119900 | King et al. | Jun 2006 | A1 |
| 20060122983 | King et al. | Jun 2006 | A1 |
| 20060126131 | Tseng et al. | Jun 2006 | A1 |
| 20060136629 | King et al. | Jun 2006 | A1 |
| 20060138219 | Brzezniak et al. | Jun 2006 | A1 |
| 20060146169 | Segman | Jul 2006 | A1 |
| 20060173859 | Kim et al. | Aug 2006 | A1 |
| 20060195695 | Keys | Aug 2006 | A1 |
| 20060200780 | Iwema et al. | Sep 2006 | A1 |
| 20060224895 | Mayer | Oct 2006 | A1 |
| 20060229940 | Grossman | Oct 2006 | A1 |
| 20060239579 | Ritter | Oct 2006 | A1 |
| 20060256371 | King et al. | Nov 2006 | A1 |
| 20060259783 | Work et al. | Nov 2006 | A1 |
| 20070005570 | Hurst-Hiller et al. | Jan 2007 | A1 |
| 20070009245 | Ito | Jan 2007 | A1 |
| 20070061146 | Jaramillo et al. | Mar 2007 | A1 |
| 20070099636 | Roth | May 2007 | A1 |
| 20070170248 | Brundage et al. | Jul 2007 | A1 |
| 20070173266 | Barnes, Jr. | Jul 2007 | A1 |
| 20070208561 | Choi et al. | Sep 2007 | A1 |
| 20070208732 | Flowers et al. | Sep 2007 | A1 |
| 20070233806 | Asadi | Oct 2007 | A1 |
| 20070238076 | Burstein et al. | Oct 2007 | A1 |
| 20070249406 | Andreasson | Oct 2007 | A1 |
| 20070279711 | King et al. | Dec 2007 | A1 |
| 20070300142 | King et al. | Dec 2007 | A1 |
| 20080046417 | Jeffery et al. | Feb 2008 | A1 |
| 20080071775 | Gross | Mar 2008 | A1 |
| 20080072134 | Balakrishnan et al. | Mar 2008 | A1 |
| 20080082903 | McCurdy et al. | Apr 2008 | A1 |
| 20080091954 | Morris et al. | Apr 2008 | A1 |
| 20080137971 | King et al. | Jun 2008 | A1 |
| 20080141117 | King et al. | Jun 2008 | A1 |
| 20080170674 | Ozden et al. | Jul 2008 | A1 |
| 20080172365 | Ozden et al. | Jul 2008 | A1 |
| 20080177825 | Dubinko et al. | Jul 2008 | A1 |
| 20080235093 | Uland | Sep 2008 | A1 |
| 20080313172 | King et al. | Dec 2008 | A1 |
| 20090012806 | Ricordi et al. | Jan 2009 | A1 |
| 20090077658 | King et al. | Mar 2009 | A1 |
| 20100092095 | King et al. | Apr 2010 | A1 |
| 20100177970 | King et al. | Jul 2010 | A1 |
| 20100182631 | King et al. | Jul 2010 | A1 |
| 20100183246 | King et al. | Jul 2010 | A1 |
| 20100185538 | King et al. | Jul 2010 | A1 |
| 20100278453 | King et al. | Nov 2010 | A1 |
| 20100318797 | King et al. | Dec 2010 | A1 |
| 20110019020 | King et al. | Jan 2011 | A1 |
| 20110019919 | King et al. | Jan 2011 | A1 |
| 20110022940 | King et al. | Jan 2011 | A1 |
| 20110025842 | King et al. | Feb 2011 | A1 |
| 20110026838 | King et al. | Feb 2011 | A1 |
| 20110029443 | King et al. | Feb 2011 | A1 |
| 20110029504 | King et al. | Feb 2011 | A1 |
| 20110033080 | King et al. | Feb 2011 | A1 |
| 20110035289 | King et al. | Feb 2011 | A1 |
| 20110035656 | King et al. | Feb 2011 | A1 |
| 20110035662 | King et al. | Feb 2011 | A1 |
| 20110043652 | King et al. | Feb 2011 | A1 |
| 20110044547 | King et al. | Feb 2011 | A1 |
| 20110209191 | Shah | Aug 2011 | A1 |
| 20110295842 | King et al. | Dec 2011 | A1 |
| 20110299125 | King et al. | Dec 2011 | A1 |
| Number | Date | Country |
|---|---|---|
| 0424803 | May 1991 | EP |
| 0544434 | Jun 1993 | EP |
| 0596247 | May 1994 | EP |
| 0697793 | Feb 1996 | EP |
| 0887753 | Dec 1998 | EP |
| 1054335 | Nov 2000 | EP |
| 1087305 | Mar 2001 | EP |
| 1141882 | Oct 2001 | EP |
| 1318659 | Jun 2003 | EP |
| 1398711 | Mar 2004 | EP |
| 2366033 | Feb 2002 | GB |
| 3260768 | Nov 1991 | JP |
| 10-133847 | May 1998 | JP |
| H11-213011 | Aug 1999 | JP |
| 2001-345710 | Dec 2001 | JP |
| 2003216631 | Jul 2003 | JP |
| 2004-500635 | Jan 2004 | JP |
| 2004-050722 | Feb 2004 | JP |
| 10-2000-0054339 | Sep 2000 | KR |
| 10-2000-0054268 | Oct 2002 | KR |
| 10-2004-0029895 | Apr 2004 | KR |
| 10-2007-0051217 | May 2007 | KR |
| 10-0741368 | Jul 2007 | KR |
| 10-0761912 | Sep 2007 | KR |
| 9419766 | Sep 1994 | WO |
| WO9803923 | Jan 1998 | WO |
| 0056055 | Sep 2000 | WO |
| WO-0067091 | Nov 2000 | WO |
| 0103017 | Jan 2001 | WO |
| 0124051 | Apr 2001 | WO |
| 0133553 | May 2001 | WO |
| WO-0211446 | Feb 2002 | WO |
| 02061730 | Aug 2002 | WO |
| WO-02091233 | Nov 2002 | WO |
| WO-2004084109 | Sep 2004 | WO |
| WO-2005071665 | Aug 2005 | WO |
| 2005096750 | Oct 2005 | WO |
| 2005096755 | Oct 2005 | WO |
| 2005098596 | Oct 2005 | WO |
| 2005098597 | Oct 2005 | WO |
| 2005098598 | Oct 2005 | WO |
| 2005098599 | Oct 2005 | WO |
| 2005098600 | Oct 2005 | WO |
| 2005098601 | Oct 2005 | WO |
| 2005098602 | Oct 2005 | WO |
| 2005098603 | Oct 2005 | WO |
| 2005098604 | Oct 2005 | WO |
| 2005098605 | Oct 2005 | WO |
| 2005098606 | Oct 2005 | WO |
| 2005098607 | Oct 2005 | WO |
| 2005098609 | Oct 2005 | WO |
| 2005098610 | Oct 2005 | WO |
| 2005101192 | Oct 2005 | WO |
| 2005101193 | Oct 2005 | WO |
| 2005106643 | Nov 2005 | WO |
| 2005114380 | Dec 2005 | WO |
| 2006014727 | Feb 2006 | WO |
| 2006023715 | Mar 2006 | WO |
| 2006023717 | Mar 2006 | WO |
| 2006023718 | Mar 2006 | WO |
| 2006023806 | Mar 2006 | WO |
| 2006023937 | Mar 2006 | WO |
| 2006026188 | Mar 2006 | WO |
| 2006029259 | Mar 2006 | WO |
| 2006036853 | Apr 2006 | WO |
| 2006037011 | Apr 2006 | WO |
| 2006093971 | Sep 2006 | WO |
| 2006124496 | Nov 2006 | WO |
| 2007141020 | Dec 2007 | WO |
| 2008014255 | Jan 2008 | WO |
| WO-2008002074 | Jan 2008 | WO |
| 2008028674 | Mar 2008 | WO |
| 2008031625 | Mar 2008 | WO |
| 2008072874 | Jun 2008 | WO |
| 2010096191 | Aug 2010 | WO |
| 2010096192 | Aug 2010 | WO |
| 2010096193 | Aug 2010 | WO |
| 2010105244 | Sep 2010 | WO |
| 2010105245 | Sep 2010 | WO |
| 2010105246 | Sep 2010 | WO |
| 2010108159 | Sep 2010 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20060041590 A1 | Feb 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60559226 | Apr 2004 | US | |
| 60558893 | Apr 2004 | US | |
| 60558968 | Apr 2004 | US | |
| 60558867 | Apr 2004 | US | |
| 60559278 | Apr 2004 | US | |
| 60559279 | Apr 2004 | US | |
| 60559265 | Apr 2004 | US | |
| 60559277 | Apr 2004 | US | |
| 60558969 | Apr 2004 | US | |
| 60558892 | Apr 2004 | US | |
| 60558760 | Apr 2004 | US | |
| 60558717 | Apr 2004 | US | |
| 60558499 | Apr 2004 | US | |
| 60558370 | Apr 2004 | US | |
| 60558789 | Apr 2004 | US | |
| 60558791 | Apr 2004 | US | |
| 60558527 | Apr 2004 | US | |
| 60559125 | Apr 2004 | US | |
| 60558909 | Apr 2004 | US | |
| 60559033 | Apr 2004 | US | |
| 60559127 | Apr 2004 | US | |
| 60559087 | Apr 2004 | US | |
| 60559131 | Apr 2004 | US | |
| 60559766 | Apr 2004 | US | |
| 60561768 | Apr 2004 | US | |
| 60563520 | Apr 2004 | US | |
| 60563485 | Apr 2004 | US | |
| 60564688 | Apr 2004 | US | |
| 60564846 | Apr 2004 | US | |
| 60566667 | Apr 2004 | US | |
| 60571381 | May 2004 | US | |
| 60571560 | May 2004 | US | |
| 60571715 | May 2004 | US | |
| 60589203 | Jul 2004 | US | |
| 60589201 | Jul 2004 | US | |
| 60589202 | Jul 2004 | US | |
| 60598821 | Aug 2004 | US | |
| 60602956 | Aug 2004 | US | |
| 60602925 | Aug 2004 | US | |
| 60602947 | Aug 2004 | US | |
| 60602897 | Aug 2004 | US | |
| 60602896 | Aug 2004 | US | |
| 60602930 | Aug 2004 | US | |
| 60602898 | Aug 2004 | US | |
| 60603466 | Aug 2004 | US | |
| 60603082 | Aug 2004 | US | |
| 60603081 | Aug 2004 | US | |
| 60603498 | Aug 2004 | US | |
| 60603358 | Aug 2004 | US | |
| 60604103 | Aug 2004 | US | |
| 60604098 | Aug 2004 | US | |
| 60604100 | Aug 2004 | US | |
| 60604102 | Aug 2004 | US | |
| 60605229 | Aug 2004 | US | |
| 60605105 | Aug 2004 | US | |
| 60613243 | Sep 2004 | US | |
| 60613628 | Sep 2004 | US | |
| 60613632 | Sep 2004 | US | |
| 60613589 | Sep 2004 | US | |
| 60613242 | Sep 2004 | US | |
| 60613602 | Sep 2004 | US | |
| 60613340 | Sep 2004 | US | |
| 60613634 | Sep 2004 | US | |
| 60613461 | Sep 2004 | US | |
| 60613455 | Sep 2004 | US | |
| 60613460 | Sep 2004 | US | |
| 60613400 | Sep 2004 | US | |
| 60613456 | Sep 2004 | US | |
| 60613341 | Sep 2004 | US | |
| 60613361 | Sep 2004 | US | |
| 60613454 | Sep 2004 | US | |
| 60613339 | Sep 2004 | US | |
| 60613633 | Sep 2004 | US | |
| 60615378 | Oct 2004 | US | |
| 60615112 | Oct 2004 | US | |
| 60615538 | Oct 2004 | US | |
| 60617122 | Oct 2004 | US | |
| 60622906 | Oct 2004 | US | |
| 60633452 | Dec 2004 | US | |
| 60633678 | Dec 2004 | US | |
| 60633486 | Dec 2004 | US | |
| 60633453 | Dec 2004 | US | |
| 60634627 | Dec 2004 | US | |
| 60634739 | Dec 2004 | US | |
| 60647684 | Jan 2005 | US | |
| 60648746 | Jan 2005 | US | |
| 60653372 | Feb 2005 | US | |
| 60653663 | Feb 2005 | US | |
| 60653669 | Feb 2005 | US | |
| 60653899 | Feb 2005 | US | |
| 60653679 | Feb 2005 | US | |
| 60653847 | Feb 2005 | US | |
| 60654379 | Feb 2005 | US | |
| 60654368 | Feb 2005 | US | |
| 60654326 | Feb 2005 | US | |
| 60654196 | Feb 2005 | US | |
| 60655279 | Feb 2005 | US | |
| 60655280 | Feb 2005 | US | |
| 60655987 | Feb 2005 | US | |
| 60655697 | Feb 2005 | US | |
| 60655281 | Feb 2005 | US | |
| 60657309 | Feb 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11004637 | Dec 2004 | US |
| Child | 11097089 | US |
