Patent Grant
9311336
1. Field of the Invention
The invention relates to techniques for creating a mixed media document that is formed from at least two media types, and more particularly, to registering an image and other data in a Mixed Media Reality (MMR) system that uses printed media in combination with electronic media to retrieve mixed media documents and associated advertisements.
2. Background of the Invention
Document printing and copying technology has been used for many years in many contexts. By way of example, printers and copiers are used in commercial office environments, in home environments with personal computers, and in document printing and publishing service environments. However, printing and copying technology has not been thought of previously as a means to bridge the gap between static printed media (i.e., paper documents), and the “virtual world” of interactivity that includes the likes of digital communication, networking, information provision, advertising, entertainment and electronic commerce.
Printed media has been the primary source of communicating information, such as newspapers and advertising information, for centuries. The advent and ever-increasing popularity of personal computers and personal electronic devices, such as personal digital assistant (PDA) devices and cellular telephones (e.g., cellular camera phones), over the past few years has expanded the concept of printed media by making it available in an electronically readable and searchable form and by introducing interactive multimedia capabilities, which are unparalleled by traditional printed media.
Unfortunately, a gap exists between the electronic multimedia-based world that is accessible electronically and the physical world of print media. For example, although almost everyone in the developed world has access to printed media and to electronic information on a daily basis, users of printed media and of personal electronic devices do not possess the tools and technology required to form a link between the two (i.e., for facilitating a mixed media document).
Moreover, there are particular advantageous attributes that conventional printed media provides such as tactile feel, no power requirements, and permanency for organization and storage, which are not provided with virtual or digital media. Likewise, there are particular advantageous attributes that conventional digital media provides such as portability (e.g., carried in storage of cell phone or laptop) and ease of transmission (e.g., email).
One particular problem is that a publisher cannot allow access to electronic versions of content using printed versions of the content. For example, for the publisher of a newspaper there is no mechanism that allows its users who receive the printed newspaper on a daily basis to use images of the newspaper to access the same online electronic content as well as augmented content. Moreover, while the publisher typically has the content for the daily newspaper in electronic form prior to printing, there currently does not exist a mechanism to easily migrate that content into an electronic form with augmented content.
A second problem is that there currently does not exist mechanisms for capturing symbolic information from documents upon printing.
The present invention overcomes the deficiencies of the prior art with an MMR system that is particularly advantageous because it provides an automatic mechanism for capturing symbolic information from documents upon printing. The MMR system is also advantageous because it has a unique architecture adapted to respond to image queries formed of image portions or pages of a printed publication.
In one embodiment, the MMR system comprises a plurality of mobile devices, a computer, an MMR gateway, an MMR matching unit, and an MMR publisher, as well as a computer with a document authoring application, a plug-in, and a printer driver. The mobile devices are communicatively coupled to the MMR gateway to send retrieval requests including image queries and other contextual information. The MMR gateway is able to couple to hundreds if not millions of mobile computing devices and service their retrieval requests. In one embodiment, the MMR gateway processes retrieval requests from mobile devices and performs user authentication, accounting, analytics and other communication and then generates an image query that is passed on to the MMR matching unit. The MMR matching unit includes a dispatcher, a plurality of recognition units, and index tables as well as an image registration unit. The MMR matching unit receives an image query from the MMR gateway and sends it to one or more of the recognition units to identify a result including a document, the page and the location on the page corresponding to the image query. The image registration unit of the MMR matching unit is also coupled to the MMR publisher to receive new content.
The present invention also includes a number of novel methods including a method for capturing symbolic information from documents and for capturing printer dll functions.
The features and advantages described herein are not all-inclusive and many additional features and advantages will be apparent to one of ordinary skill in the art in view of the figures and description. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and not to limit the scope of the inventive subject matter.
The invention is illustrated by way of example, and not by way of limitation in the figures of the accompanying drawings in which like reference numerals are used to refer to similar elements.
An architecture for a mixed media reality (MMR) system 100 capable of receiving the query images and returning document pages and location as well as receiving images, hot spots and other data and adding such information to the MMR system is described. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the invention. It will be apparent, however, to one skilled in the art that the invention can be practiced without these specific details. In other instances, structures and devices are shown in block diagram form in order to avoid obscuring the invention. For example, the present invention is described in one embodiment below with reference to use with a conventional mass media publisher, in particular a newspaper publisher. However, the present invention applies to any type of computing system and data processing in which multiple types of media including electronic media and print media are used.
Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment. In particular the present invention is described below in the context of two distinct architectures and some of the components are operable in both architectures while others are not.
Some portions of the detailed descriptions that follow are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the means used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers or the like.
It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussion, it is appreciated that throughout the description, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar electronic computing device, that manipulates and transforms data represented as physical (electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
The present invention also relates to an apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards, or any type of media suitable for storing electronic instructions, each coupled to a computer system bus.
Finally, the algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatuses to perform the required method steps. The required structure for a variety of these systems will appear from the description below. In addition, the present invention is described without reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the invention as described herein.
System Overview
The mobile devices 102a-102n are communicatively coupled by signal lines 132a-132n, respectively, to the MMR gateway 104 to send a “retrieval request.” A retrieval request includes one or more of “image queries,” other contextual information, and metadata. In one embodiment, an image query is an image in any format, or one or more features of an image. Examples of image queries include still images, video frames, and sequences of video frames. The mobile devices 102a-102n are mobile phones including a camera to capture images. It should be understood that the MMR system 100 will be utilized by hundreds or even millions of users that receive a traditional publication such as a daily newspaper. Thus, even though only two mobile devices 102a, 102n are shown, those skilled in the art will appreciate that the MMR gateway 104 may be simultaneously coupled to, receive and respond to retrieval requests from numerous mobile devices 102a-102n. Alternate embodiments for the mobile devices 102a-102n are described in more detail below with reference to
As noted above, the MMR gateway 104 is able to couple to hundreds if not millions of mobile computing devices 102a-102n and service their retrieval requests. The MMR gateway 104 also is communicatively coupled to the computer 110 by signal line 130 for administration and maintenance of the MMR gateway 104 and running business applications. In one embodiment, the MMR gateway 104 creates and presents a web portal for access by the computer 110 to run business applications as well as access logs of use of the MMR system 100. The computer 110 can be any conventional computing device such as a personal computer, including a processor and other standard components known in the art. The main function of the MMR gateway 104 is processing retrieval requests from the mobile devices 102a-102n and returning recognition results back to the mobile devices 102a-102n. In one embodiment, the recognition results include one or more of a Boolean value (true/false) and if true, a page ID and a location on the page. In other embodiments, the recognition results also include one or more from the group of actions, a message acknowledging that the recognition was successful (or not), and consequences of that decision, such as the sending of an email message, a document, actions defined within a portable document file, addresses such as URLs, binary data such as video, information capable of being rendered on the mobile device 102, menus with additional actions, raster images, image features, etc. The MMR gateway 104 processes received retrieval requests by performing user authentication, accounting, analytics, and other communication. The MMR gateway 104 also generates image query and recognition parameters from the retrieval request, and passes them on to the MMR matching unit 106 via signal line 134. Embodiments and operation of the MMR gateway 104 are described in greater detail below with reference to
The MMR matching unit 106 receives the image query from the MMR gateway 104 on signal line 134 and sends it to one or more of recognition units to identify a result including a document, page, and location on the page corresponding to the image query, referred to generally throughout this application as the “retrieval process.” The result is returned from the MMR matching unit 106 to the MMR gateway 104 on signal line 134. In addition to the result, the MMR matching unit 106 may also return other related information such as hotspot data, including advertising content. The MMR matching unit 106 also includes components for receiving new content and updating and reorganizing index tables used in the retrieval process. The process of adding new content to the MMR matching unit 106 is referred to generally throughout this application as the “registration process.” In one embodiment, the MMR matching unit 106 is coupled to the output of the MMR publisher 108 via signal lines 138 and 140 to provide new content used to update index tables of the MMR matching unit 106. In alternate embodiment, the MMR publisher 108 is coupled to the MMR gateway 104 by signal line 138 and the MMR gateway 104 is in turn coupled by signal line 136 to the MMR matching unit 106. In this alternate environment, MMR gateway 104 extracts augmented data such as hotspot information, stores it and passes the images, page references and other information to the MMR matching unit 106 for updating of the index tables. Various embodiments of the MMR matching unit 106 and its components are described in more detail below with reference to
The MMR publisher 108 includes a conventional publishing system used to generate newspapers or other types of periodicals. In one embodiment, the MMR publisher 108 also includes components for generating additional information needed to register images of printed documents with the MMR system 100. The information provided by the MMR publisher 108 to the MMR matching unit 106 includes an image file, bounding box data, hotspot data, and a unique page identification number. In one exemplary embodiment, this is a document in portable document format by Adobe Corp. of San Jose, Calif. and bounding box information. The publisher 108 also may provide information about the hierarchical structure associated with a publication, e.g., what documents are in the collection, what pages are in each document, and what zones are on each page, as well as a neighborhood preference function for pages and/or documents for publications typically read in a specific order. An embodiment for the MMR publisher 108 is described in more detail below with reference to
Mobile Device 102
Referring now to
Referring now to
It should be noted that regardless of whether the first embodiment or the second embodiment of the mobile device 102 is used, the mobile device 102 generates the retrieval request that includes: a query image, a user or device ID, a command and other contact information such as device type, software, plug-ins, location (for example if the mobile device includes a GPS capability), device and status information (e.g., device model, macro lens on/off status, autofocus on/off, vibration on/off, tilt angle, etc), context-related information (weather at the phone's location, time, date, applications currently running on the phone), user-related information (e.g., id number, preferences, user subscriptions, user groups and social structures, action and action-related meta data such as email actions and emails waiting to be sent), etc.
Referring now to
MMR Gateway 104
Referring now to
As noted above, one of the primary functions of the MMR gateway 104 is to communicate with many mobile devices 102 to receive retrieval requests and send responses including a status indicator (true=recognized/false=not recognized), a page identification number, a location on the page and other information such as hotspot data. A single MMR gateway 104 can respond to hundreds or millions of retrieval requests. For convenience and ease of understanding only a single MMR gateway 104 is shown in
The server 302 is also coupled to signal line 130 for communication with the computer 110. Again, for convenience and ease of understanding only a single computer 110 and signal line 130 are shown in
The server 302 processes the retrieval request and generates an image query and recognition parameters that are sent via signal line 134 to the MMR matching unit 106 for recognition. The server 302 also receives recognition responses from the MMR matching unit 106 via signal line 134. The server 302 also processes the retrieval request and sends information via signal line 330 to the other components of the MMR gateway 104 as will be described below. The server 302 is also adapted for communication with the MMR publisher 108 by signal line 138 and the MMR matching unit 106 via signal line 136. The signal line 138 provides a path for the MMR publisher 108 to send Web content for hotspots to the Web server 304 and to provide other information to the server 302. In one embodiment, the server 302 receives information from the MMR publisher 108 and sends that information via signal line 136 for registration with the MMR matching unit 106.
The web server 304 is a conventional type and is responsible for accepting requests from clients and sending responses along with data contents, such as web pages, documents and linked objects (images, etc.) The Web server 304 is coupled to data store 306 such as a conventional database. The Web server 304 is adapted for communication via signal line 234 to receive HTTP requests from any communication device across a network such as the Internet. The Web server 304 is also coupled to signal line 138 as described above to receive Web content associated with hotspots for storage in the data store 306 and then for later retrieval and transmission in response to HTTP requests. Those skilled in the art will understand that inclusion of the Web server 304 and data store 306 as part of the MMR gateway 104 is merely one embodiment and that the Web server 304 and the data store 306 may be operational in any number of alternate locations or configuration so long as the Web server 304 is accessible to mobile devices 102 and computers 110 via the Internet.
In one embodiment, the portal module 308 is software or routines operational on the server 302 for creation and presentation of the Web portal. The portal module 308 is coupled to signal line 330 for communication with the server 302. In one embodiment, the web portal provides an access point for functionality including administration and maintenance of other components of the MMR gateway 104. In another embodiment, the web portal provides an area where users can share experiences related to MMR documents. In yet another embodiment, the web portal is an area where users can access business applications and the log 310 of usage.
The log 310 is a memory or storage area for storing a list of the retrieval requests received by the server 302 from mobile devices 102 and all corresponding responses sent by the server 302 to the mobile devices. In another embodiment, the log 310 also stores a list of the image queries generated and sent to the MMR matching unit 106 and the recognition responses received from the MMR matching unit 106. The log 310 is coupled to signal line 330 for access by the server 302.
The one or more business applications 312 are software and routines for providing functionality related to the processing of MMR documents. In one embodiment the one or more business applications 312 are executable on the server 302. The business applications 312 can be any one of a variety of types of business applications adapted to utilize information related to the processing of retrieval quests and delivery of recognition responses such as but not limited to accounting, groupware, customer relationship management, human resources, outsourcing, loan origination, customer care, service relationships, etc.
The authentication module 314 is software and routines for maintaining a list of authorized users and granting access to the MMR system 110. In one embodiment, the authentication module 314 maintains a list of user IDs and passwords corresponding to individuals who have created an account in the system 100, and therefore, are authorized to use MMR gateway 104 and the MMR matching unit 106 to process retrieval requests. The authentication module 314 is communicatively coupled by signal line 330 to the server 302. But as the server 302 receives retrieval requests they can be processed and compared against information in the authentication module 314 before generating and sending the corresponding image query on signal line 134. In one embodiment, the authentication module 314 also generates messages for the server 302 to return to the mobile device 102 instances when the mobile device is not authorized, the mobile device has not established an account, or the account for the mobile device 102 is locked such as due to abuse or lack of payment.
The accounting module 316 is software and routines for performing accounting related to user accounts and use of the MMR system 100. In one embodiment, the retrieval services are provided under a variety of different economic models such as but not limited to use of the MMR system 100 under a subscription model, a charge per retrieval request model or various other pricing models. In one embodiment, the MMR system 100 provides a variety of different pricing models and is similar to those currently offered for cell phones and data networks. The accounting module 316 is coupled to the server 302 by signal line 330 to receive an indication of any retrieval request received by the server 302. In one embodiment, the accounting module 316 maintains a record of transactions (retrieval request/recognition responses) processed by the server 302 for each mobile device 102. Although not shown, the accounting module 316 can be coupled to a traditional billing system for the generation of an electronic or paper bill.
The mail module 318 is software and routines for generating e-mail and other types of communication. The mail module 318 is coupled by signal at 330 to the server 302. In one embodiment, the mobile device 102 can issue retrieval requests that include a command to deliver a document or a portion of a document or other information via e-mail, facsimile or other traditional electronic communication means. The mail module 318 is adapted to generate and send such information from the MMR gateway 104 to an addressee as prescribed by the user. In one embodiment, each user profile has associated addressees which are potential recipients of information retrieved.
The analytics module 320 is software and routines for measuring the behavior of users of the MMR system 100 according to one embodiment. The analytics module 320 is also software and routines for measuring the effectiveness and accuracy of feature extractors and recognition performed by the MMR matching unit 106. The analytics module 320 measures use of the MMR system 100 including which images are most frequently included as part of retrieval requests, which hotspot data is most often accessed, the order in which images are retrieved, the first image in the retrieval process, and other key performance indicators used to improve the MMR experience and/or a marketing campaign's audience response. In one embodiment, the analytics module 320 measures metrics of the MMR system 100 and analyzes the metrics used to measure the effectiveness of hotspots and hotspot data. The analytics module 320 is coupled to the server 302, the authentication module 314 and the accounting module 316 by signal line 330. The analytics module 320 is also coupled by the server 302 to signal line 134 and thus can access the components of the MMR matching unit 106 to retrieve recognition parameters, images features, quality recognition scores and any other information generated or used by the MMR matching unit 106. The analytics module 320 can also perform a variety of data retrieval and segmentation based upon parameters or criteria of users, mobile devices 102, page IDs, locations, etc.
In one embodiment, the MMR gateway 104 also includes a hotspot database 404. The hotspot database 404 is shown in
MMR Matching Unit 106
Referring now to
The dispatcher 402 is coupled to signal line 134 for receiving an image query from and sending recognition results to the MMR gateway 104. The dispatcher 402 is responsible for assigning and sending an image query to respective recognition units 410a-410n. In one embodiment, the dispatcher 402 receives an image query, generates a recognition unit identification number and sends the recognition unit identification number and the image query to the acquisition unit 406 for further processing. The dispatcher 402 is coupled to signal line 430 to send the recognition unit identification number and the image query to the recognition units 410a-410n. The dispatcher 402 also receives the recognition results from the acquisition unit 406 via signal line 430. The dispatcher 402 also retrieves hotspot content from hotspot database 404 corresponding to the recognition results. One embodiment for the dispatcher 402 will be described in more detail below with reference to
An alternate embodiment for the hotspot database 404 has been described above with reference to
Referring again to
Those skilled in the art will understand that there are a variety of configurations for the plurality of recognition units 410a-410n and the plurality of index tables 412a-412n. Example embodiments for the acquisition unit 406 will be described in more detail below with reference to
The image registration unit 408 comprises the indexing unit 414 and the master index table 416. The image registration unit 408 has an input coupled to signal on 136 to receive updated information from the MMR publisher 108 and broker 112 and an input coupled to signal line 438 to receive updated information from the dynamic load balancer 418. The image registration unit 408 is responsible for maintaining the master index table 416 and migrating all or portions of the master index table 416 to the index tables 412a-412n (slave tables) of the acquisition unit 406. In one embodiment, the indexing unit 414 receives images, unique page IDs, and other information, and converts it into index table information that is stored in the master index table 416. The indexing unit 414 also cooperates with the MMR publisher 108 to maintain a unique page identification numbering system that is consistent across image pages generated by the MMR publisher 108, the image pages stored in the master index table 416, and the page numbers used in referencing data in the hotspot database 404.
One embodiment for the image registration unit 408 is shown and described in more detail below with reference to
The dynamic load balancer 418 has an input coupled to signal line 430 to receive the query image from the dispatcher 402 and the corresponding recognition results from the acquisition unit 406. The output of the dynamic load balancer 418 is coupled by signal line 438 to an input of the image registration unit 408. The dynamic load balancer 418 provides input to the image registration unit 408 that is used to dynamically adjust the index tables 412a-412n of the acquisition unit 406. In particular, the dynamic load balancer 418 monitors and evaluates the image queries that are sent from the dispatcher 402 to the acquisition unit 406 for a given period of time. Based on the usage, the dynamic load balancer 418 provides input to adjust the index tables 412a-412n. For example, the dynamic load balancer 418 may measure the image queries for a day. Based on the measured usage for that day, the index tables are modified and configured in the acquisition unit 406 to match the usage measured by the dynamic load balancer 418.
Dispatcher 402
Referring now to
The dispatcher 402 also receives the recognition results from the recognition units 410 on signal line 530. The recognition results include a Boolean value (true/false) and if true, a page ID and a location on the page. In one embodiment, the dispatcher 402 merely receives and retransmits the data to the MMR gateway 104.
Referring again to
The image feature order unit 504 receives image queries and outputs an ordering signal. The image feature order unit 504 analyzes an input image query and predicts the time required to recognize an image by analyzing the image features it contains. The difference between the actual recognition time and the predicted time is used to adjust future predictions thereby improving accuracy. In the simplest of embodiments, simple images with few features are assigned to lightly loaded recognition units 410 so that they will be recognized quickly and the user will see the answer immediately. In one embodiment, the features used by the image order feature unit 504 to predict the time are different than the features used by recognition units 410 for actual recognition. For example, the number of corners detected in an image is used to predict the time required to analyze the image. The feature set used for prediction need only be correlated with the actual recognition time. In one embodiment, several different features sets are used and the correlations to recognition time measured over some period. Eventually, the feature set that is the best predictor and lowest cost (most efficient) would be determined and the other feature sets could be discarded.
Acquisition Unit 406
Referring now to
As shown in
It should be noted that the use of four recognition units 410 and index tables 412 as the first group 612 is merely be by way example and used demonstrate a relative proportion as compared with the number of recognition units 410 and index tables 412 in the second group 614 and the third group 616. The number of recognition units 410 and index tables 412 in any particular group 612, 614 and 616 may be scaled the modified based on the total number of recognition units 410 and index tables 412. Furthermore, the number of recognition units 410 and index tables 412 in any particular group 612, 614 and 616 may be adapted so that it matches the profile of all users sending retrieval request to the acquisition unit 406 for a given publication.
The second embodiment of the acquisition unit 406 includes a plurality of recognition units 410a-410e, a plurality of the index tables 412a-412e and a result combiner 610. In this embodiment, the recognition units 410a-410e each utilizes a different type of recognition algorithm. For example, recognition units 410a, 410b and 410c use an invisible junction algorithm; recognition unit 410d uses a brick wall coding algorithm; and recognition unit 410e uses a path coding algorithm for recognition and retrieval of page numbers and locations. Recognition units 410a, 410d and 410e each have an input coupled signal line 430 by signal line 630 for receiving the image query. The recognition results from each of the plurality of recognition units 410a-410e are sent via signal lines 636, 638, 640, 642 and 644 to the result combiner 610. The output of the result combiner 610 is coupled to signal line 430.
In one embodiment, the recognition units 410a, 410b and 410c cooperate together with index tables 1, 2 and 3, 412a-412c each storing image features corresponding to the same pages but with differing levels of blur caused by device and environmental factors. For example, index table 1412a may store image features for pristine images of pages such as from a PDF document, while index table 2412b stores images of the same pages but with a first level of blur and index table 3412c stores images of the same pages but with the second level of blur. In one embodiment, the index tables 1, 2 and 3, 412a-412c are quantization trees. The first recognition unit 410a receives the image query via signal line 630. The first recognition unit 410a comprises an invisible junction feature extractor 602 and a retriever 604a. The invisible junction feature extractor 602 receives the image query, extracts the invisible junction features and provides them to the retriever 604a. The retriever 604a uses the extracted invisible junction features and compares them to the index table 1412a. If the retriever 604a identifies a match, the retriever 604a sends the recognition results via signal line 636 to the result combiner 610. If however, the retriever 604a was unable to identify a match or identifies a match with low confidence, the retriever 604a sends the extracted invisible junction features to the retriever 604b of the second recognition unit 410b via signal line 632. It should be noted that since the invisible junction features have already been extracted, the second recognition unit 410b does not require an invisible junction feature extractor 602. The second recognition unit 410b performs retrieval functions similar to the first recognition unit 410a, but cooperates with index table 2412b that has invisible junction features for slightly blurry images. If the retriever 604b identifies a match, the retriever 604b sends the recognition results via signal line 638 to the result combiner 610. If the retriever 604b of the second recognition unit 410b is unable to identify a match or identifies a match with low confidence, the retriever 604b sends the extracted invisible junction features to the retriever 604c of the third recognition unit 410c via signal line 634. The retriever 604c then performs a similar retrieval function but on index table 3412c. Those skilled in the art will understand that while one pristine set of images and two levels of blur are provided, this is only by way of example and that any number of additional levels of blur from 0 to n may be used.
The recognition units 410d and 410e operate in parallel with the other recognition units 410a-c. The fourth recognition unit 410d comprises a brick wall coding feature extractor 606 and a retriever 604d. The brick wall coding feature extractor 606 receives the image query and bounding boxes, parses the bounding boxes and generates brick wall coding features. These brick wall coding features are provided to the retriever 604d and the retriever 604d compares them to the features stored in index table 4412d. In one embodiment, index table 4412d is a hash table. The retriever 604d identifies any matching pages and returns the recognition results to the result combiner 610 via signal line 642. The fifth recognition unit 410e operates in a similar manner but for path coding. The fifth recognition unit 410e comprises a path coding feature extractor 608 and a retriever 604e. The path coding feature extractor 608 receives the image query and bounding boxes, parses the image and generates path coding features that are provided to the retriever 604e and the retriever 604e compares them to features stored in the index table 5412e. In one embodiment, the index table 5412e is a SQL database of character strings. The retriever 604e identifies any matching strings and returns the recognition results to the result combiner 610 via signal line 644.
The result combiner 610 receives recognition results from the plurality of recognition units 410a-e and produces one or a small list of matching results. In one embodiment, each of the recognition results includes an associated confidence factor. In another embodiment, context information such as date, time, location, personal profile or retrieval history are provided to the result combiner 610. These confidence factors along with other information are used by the result combiner 610 to select the recognition results most likely to match the input image query.
Image Registration Unit 408
The blurry generator 702 has an input coupled in signal line 730 to receive an image and a page identification number. The blurry generator 702 has a plurality of outputs and each output is coupled by signal lines 732, 734 and 736 to invisible junction feature extractors 704a-c, respectively. The blurry generator 702 passes a pristine image and the page identification number to the output and signal line 732. The blurry generator 702 then generates an image with a first level of blurriness and outputs it and the page identification number on signal line 734 to invisible junction feature extractor 704b, and another image with a second level of blurriness and outputs it and page identification number on signal line 736 to invisible junction feature extractor 704c.
The invisible junction feature extractors 704 receive the image and page ID, extract the invisible junction features from the image and send them along with the page ID to a respective invisible junction index table updater 706. The outputs of the plurality of invisible junction feature extractors 704a-c are coupled to input of the plurality of invisible junction index table updaters 706a-c. For example, the output of invisible junction feature extractor 704a is coupled to an input of invisible junction index table updater 706a. The remaining invisible junction feature extractors 704b-c are similarly coupled to respective invisible junction index table updaters 706b-c. The invisible junction index table updaters 706 are responsible for formatting the extracted features and storing them in a corresponding master index table 416. While the master index table 416 is shown as five separate master index tables 416a-e, those skilled in the art will recognize that all the master index tables could be combined into a single master index table or into a few master index tables. Once the invisible junction index table updaters 706 have stored the extracted features in the index table 416, they issue a confirmation signal that is sent via signal lines 740 and 136 back to the MMR publisher 108.
The brick wall coding feature extractor 708 and the path coding feature extractor 712 operate in a similar fashion and are coupled to signal line 738 to receive the image, a page identification number and bounding box information. The brick wall coding feature extractor 708 extracts information from the input needed to update its associated index table 416d. The brick wall coding index table updater 710 receives the extracted information from the brick wall coding feature extractor 708 and stores it in the index table 416d. The path coding feature extractor 712 and the path coding index table updater 714 operate in a like manner but for path coding. The path coding feature extractor 712 also receives the image, a page number and bounding box information via signal line 738. The path coding feature extractor 712 extracts path coding information and passes it to the path coding index table updater 714. The path coding index table updater 714 stores the information in index table 5416e. The architecture of the registration unit 408 is particularly advantageous because it provides an environment in which the MMR publisher 108 can automatically update the index tables simply by providing images and page numbers to the image registration unit 408 and the index tables are updated automatically.
MMR Publisher 108
An embodiment of the MMR publisher 108 is shown in
The conventional publishing software 802 is software for creating digital content including text, graphics, and pictures. Examples of the conventional publishing software used in the production and distribution of newspapers include Adobe Acrobat manufactured and sold by Adobe Inc. of San Jose, Calif. or QuarkXPress manufactured and sold by Quark, Inc. of Denver, Colo. The conventional publishing software 802 may be other types of proprietary software owned by large publishing companies.
The pre-press plug-in for registration and annotation 804 is software and routines for interfacing with the conventional publishing software 802 and generating additional information used by the image registration unit 408 so that the content can be automatically uploaded to the acquisition unit 406. For example, the prepress plug-in for registration and annotation communicates and interfaces with the image registration unit 408 to maintain a unique page identification numbering system that is consistent across image pages generated by the conventional publishing software 802, the image pages stored in the master index table 416, and the page numbers used in referencing data in the hotspot database 404. The prepress plug-in for registration 804 also generates bounding boxes for image pages generated by the conventional publishing software 802; the bounding boxes are subsequently used by the image registration unit 408 for certain types of encoding. The pre-press plug-in for registration and annotation 804 also analyzes the images provided by the conventional publishing software 802 and ensures that the files are of a type usable by the feature extractors 704, 708, 712.
The hotspot creator 806 is an authoring tool for creating hotspots. Hotspots identify the (x,y) coordinates of polygons on a document image and links to electronic data such as URLs that are associated with each polygon. In one embodiment, hotspots are annotations in Acrobat PDF files that include the (x,y) coordinates of polygons on a document and links to electronic data such as URLs. The hotspot creator 806 can be used to create a hotspot (a “hotspot” is a polygon on an image), associate the hotspot with a particular page in a document, and a particular location on the page, associate zero or more links with each hotspot, and generate and send the hotspot files to the server 302 for storage in the hotspot database 404. A hotspot file lists each hotspot, the coordinates of its polygon, and any links associated with it. The hotspot file can be saved as a separate file or equivalently the same data can be embedded in the document source file. The hotspot creator 806 can be a stand-alone software application that reads a source document such as Word, PDF, or an image format such as tiff, and provides a user interface that lets the user draw polygons on the document, add links to each of the hotspots, and save the hotspot files. The hotspot creator 806 can also be packaged as a plug-in for existing document authoring applications such as Word, Acrobat, Quark Express, etc. and can be designed so that the user can define polygons on the document, add links, and save the hotspot files (or, equivalently the source file with the hotspot data embedded in it). The hotspot creator 806 can also be packaged as a software application that extracts links from existing documents and saves them in the hotspot file. For example, annotations in PDF files that include polygon coordinates and links to electronic data can be removed from the PDF and saved separately in a hotspot file. The hotspot creator 806 also allows the publisher 108 to allow preferences to be associated with the hotspot locations.
Methods
Referring now to
The computer 1102 is any standard desktop, laptop, or networked computer, as is known in the art. In one embodiment, the computer is associated with publisher 108 as described in conjunction with to
The computer 1102 further comprises a variety of components, some or all of which are optional according to various embodiments. In one embodiment, the computer 1102 comprises source files 1108, document authoring application 1110, plug-in 1112, GDI 1114, printer driver 1116, data store 1118, and MMR printing software 1120.
Source files 1108 are representative of any source files that are an electronic representation of a document. Example source files 1108 include hypertext markup language (HTML) files, Microsoft® Word® files, Microsoft® PowerPoint® files, QuarkXpress files, simple text files, portable document format (PDF) files, and the like. As described herein, documents received at document authoring application 1110 originate from source files 1108 in many instances. In one embodiment, source files 1108 are stored on the hard drive of computer 1102.
Document authoring application 1110 is an application that provides for authoring and editing of documents. Document authoring application 1110 may be any application that allows for authoring and editing of documents, such as Microsoft Word, Adobe Acrobat, Internet Explorer, and Quark Xpress. In one embodiment, the document authoring application 1110 may be used to retrieve documents from the source files 1108.
Plug-in 1112 is a software application that provides an authoring function. Plug-in 1112 may run in document authoring application 1110, or alternatively may be a standalone software application. Plug-in 1112 performs various transformations and other modifications to documents or web pages displayed by document authoring application 1110 according to various embodiments. For example, plug-in 1112 may surround symbolic data, or hotspot, designations with uniquely identifiable fiducial marks in a special, invisible font.
In one embodiment in which the document authoring application 1110 is the Internet Explorer browser, the plug-in 1112 modifies the Document Object Model (DOM) for a web page in the browser by adding SPAN element fiducial marks to the .html document associated with the web page that do not affect the layout of the web page. An example of a fiducial mark 1202 is shown in
Although this example uses Internet Explorer (browser) as the document authoring application 1110. However, in other embodiments, other document authoring applications 1110 may be used, with similar processes. For example, many such document authoring applications 1110 provide the ability to incorporate custom-designed plug-ins that run in conjunction with the existing software. Such as plug-in could be sued to add instructions that embed font change commands that add “bn” and “en” tags at the beginning and end of each word in the invisible font as described in the Internet Explorer example above. As in the example, the intermediate .xml files would be produced including unique identifiers that could be matched to their locations as provided by the print driver as described herein, to determine the locations of bounding boxes around words.
Plug-in 1112 also may perform other functions, such as creating symbolic hotspot descriptions (symb_hotspot.xml) as described herein.
Printer driver 1116 is software and routines for performing a feature extraction and/or coordinate capture on the printed representation of documents, so that the layout of characters and graphics on the printed pages can be retrieved. The layout, i.e., the two-dimensional arrangement of text on the printed page, may be captured automatically at the time of printing by the printer driver 1116. For example, printer driver 1116 executes all the text and drawing print commands and, in addition, intercepts and records the x,y coordinates and other characteristics of every character and/or image in the printed representation. According to one embodiment, printer driver 1116 includes a Printcapture DLL as described herein, a forwarding Dynamically Linked Library (DLL) that forwards calls of an existing DLL while capturing information from the calls. A more detailed description of the functionality of the print capture DLL is described in reference to
Data store 1118 is any database known in the art for storing files, modified for use with the methods described herein. For example, according to one embodiment data store 1118 stores source files 1108, symb_hotspot.xml, page_desc.xml, rendered page layouts, imaged documents, hot spot definitions, and feature representations.
MMR printing software 1120 is software and routines that facilitate the MMR printing operations described herein, for example as performed by the components of computer 1102 as previously described. MMR printing software 1120 is described below in greater detail with reference to
Conversion module 1130 is software and routines for conversion of a source document, e.g. from source files 1108, into an imaged document from which a feature representation can be extracted.
Embed module 1132 is software and routines for enabling embedding of fiducial marks, e.g., as described above, corresponding to a designation for a hotspot in an electronic document. In one particular embodiment, the embedded fiducial marks indicate a beginning point for the hotspot and an ending point for the hotspot.
Parse module 1134 is software and routines for enabling parsing an electronic document (that has been sent to the printer 1104) for a fiducial mark indicating a beginning point for a hotspot.
Transformation module 1136 is software and routines for enabling application of a transformation rule to a portion of an electronic document. In one particular embodiment, the portion is a stream of characters between a fiducial mark indicating a beginning point for a hotspot and a fiducial mark indicating an ending point for the hotspot.
Feature extraction module 1138 is software and routines for enabling the extraction of features and capture of coordinates corresponding to a printed representation of a document and a hotspot. Coordinate capture includes tapping, or intercepting, print commands using a forwarding dynamically linked library and parsing the printed representation for a subset of the coordinates corresponding to a hotspot or transformed characters. Feature extraction module 1138 enables the functionality of printer driver 1116 according to one embodiment.
Hotspot module 1140 is software and routines for enabling association of one or more clips with one or more hotspots. Hotspot module 1140 also enables formulation of a hotspot definition by first designating a location for a hotspot within a document and defining a clip to associate with the hotspot.
Render/display module 1142 is software and routines for enabling a document or a printed representation of a document to be rendered or displayed.
Storage module 1144 is software and routines for enabling storage of various files, including a page layout, an imaged document, a hotspot definition, and a feature representation.
The software portions 1130-1144 need not be discrete software modules. The software configuration shown is meant only by way of example; other configurations are contemplated by and within the scope of the present invention, as will be apparent in light of this disclosure.
Referring now to
Referring to
In response to a print command, coordinates corresponding the printed representation and the hotspot are captured. In one embodiment, a printer driver 1116 “taps” text and drawing commands within a print command. The printer driver 1116 executes all the text and drawing commands and, in addition, intercepts and records 1304 the x,y coordinates and other characteristics of every character and/or image in the printed representation. This step is described in greater detail in conjunction with
The locations are saved 1306 as a page description file (page_desc.xml). page_desc.xml 1304 is an XML file created by the printer driver 1115 to which text-related output is written for function calls that are text related. page_desc.xml 1304 includes coordinate information for a document for all printed text by word and by character, as well as hotspot information, printer port name, browser name, date and time of printing, and dots per inch (dpi) and resolution (res) information. page_desc.xml 1304 is stored, e.g., in data store 1118.
Finally, page_desc.xml and symb_hotspot.xml are merged 1310 into hotspot.xml, which is an XML file that is created when a document is printed. hotspot.xml includes hotspot identifier information such as hotspot number, coordinate information, dimension information, and the content of the hotspot. An example of a hotspot.xml file is illustrated in
Next, the GDI calls the printer graphics DLL's DrvEnablePDEV function so the driver can create a physical device instance and return device characteristics. GDI uses the returned information to create an internal description of the device instance.
The GDI then calls the printer graphics DLL's DrvCompletePDEV function to supply a GDI handle to the device instance. The graphics DLL must use this handle as input to some of the Eng-prefixed callbacks provided by the GDI drawing engine.
After the GDI receives the device instance handle, it then makes a call to the graphics DLL's DrvEnableSurface function, which sets up the surface for drawing, and associates it with the physical device instance.
After this, for each document to be printed, the GDI calls DrvStartDoc in the printer graphics DLL. Then for each physical page, it calls DrvStartPage at the beginning of each page and follows that with a number of Dry-prefixed calls that render text, graphics and bitmap images on the page. At the end of the page, the GDI calls DrvSendPage and DrvEndDoc. A number of other Eng-prefixed commands are also provided.
Note that in
When the Print Capture DLL 1802 receives a DrvEnablePDEV call, in addition to passing it on to the printer graphics DLL 1804, it creates a PDEVMonitorDoc object. The PDEVMonitorDoc object contains raster images that are written to when certain DrvXXX calls are received and it maintains symbolic descriptions of certain page content, such as the positions of objects on the page. When a command is received by the printer driver that indicates the page should be printed, the Print Capture DLL 1802 calls a function that saves the raster image of the page.
A Printer Device Context (PDEV) encapsulates a target for drawing as well as drawing settings like font, color, etc. In the Print Capture DLL 1802, the function that creates a PDEV also creates the PDEVMonitorDoc. The PDEVMonitorDoc creates memory buffers and attaches them to the associated PDEV as secondary surfaces. Whenever a command (DrvTextOut( ), DrvBitBlt( ) etc. is received by the Print Capture DLL 1802, the command is not only forwarded to the printer graphics DLL 1804, but also performed upon the memory buffers owned by the PDEVMonitorDoc. This means that whatever is being drawn to the printer also gets drawn to a memory buffer on the local computer. When a command is received by the printer driver that indicates the page should be printed, the contents of the memory buffer are compressed and written out in JPG and PNG format.
The Print Capture DLL 1802 includes code for all text drawing functions. This means for applications that use the text-drawing GDI functions coordinate information for all printed text can also be captured. This information is recorded in an XML file that is stored with the JPGs/PNGs of the print operation.
If it is a monitored function call, the method next determines 1906 whether the function call specifies a new printer device context. This is determined by checking the PDEV against an internal device context table. A PDEV encapsulates a target for drawing (which could be a printer, a memory buffer, etc.), as previously noted, as well as drawing settings like font, color, etc. All drawing operations (e.g., LineTo( ), DrawText( ) etc) are performed upon a device context. If the PDEV is not new, then a memory buffer already exists that corresponds with the printer DC, and step 1908 is skipped. If the PDEV is new, a memory buffer of the same dimensions is created 1908 and attached to the PDEV as a secondary surface.
The print capture DLL next determines 1910 whether the call is a text-related function call. If it is not, step 1912 is skipped. If the function call is text-related, the text-related output is written 4430 to an xml file, referred to herein as page_desc.xml.
Referring again to
The foregoing description of the embodiments of the present invention has been presented for the purposes of illustration and description. It is not intended to be exhaustive or to limit the present invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. It is intended that the scope of the present invention be limited not by this detailed description, but rather by the claims of this application. As will be understood by those familiar with the art, the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Likewise, the particular naming and division of the modules, routines, features, attributes, methodologies and other aspects are not mandatory or significant, and the mechanisms that implement the present invention or its features may have different names, divisions and/or formats. Furthermore, as will be apparent to one of ordinary skill in the relevant art, the modules, routines, features, attributes, methodologies and other aspects of the present invention can be implemented as software, hardware, firmware or any combination of the three. Also, wherever a component, an example of which is a module, of the present invention is implemented as software, the component can be implemented as a standalone program, as part of a larger program, as a plurality of separate programs, as a statically or dynamically linked library, as a kernel loadable module, as a device driver, and/or in every and any other way known now or in the future to those of ordinary skill in the art of computer programming. Additionally, the present invention is in no way limited to implementation in any specific programming language, or for any specific operating system or environment. Accordingly, the disclosure of the present invention is intended to be illustrative, but not limiting, of the scope of the present invention, which is set forth in the following claims.
This application is a divisional of U.S. patent application Ser. No. 12/253,815, titled “Capturing Symbolic Information From Documents Upon Printing,” filed Oct. 17, 2008, which is a continuation in part of U.S. patent application Ser. No. 11/461,017, titled “System And Methods For Creation And Use Of A Mixed Media Environment,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,279, titled “Method And System For Image Matching In A Mixed Media Environment,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,286, titled “Method And System For Document Fingerprinting Matching In A Mixed Media Environment,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,294, titled “Method And System For Position-Based Image Matching In A Mixed Media Environment,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,300, titled “Method And System For Multi-Tier Image Matching In A Mixed Media Environment,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,126, titled “Integration And Use Of Mixed Media Documents,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,143, titled “User Interface For Mixed Media Reality,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,268, titled “Authoring Tools Using A Mixed Media Environment,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,272, titled “System And Methods For Creation And Use Of A Mixed Media Environment With Geographic Location Information,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,064, titled “System And Methods For Portable Device For Mixed Media System,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,075, titled “System And Methods For Use Of Voice Mail And Email In A Mixed Media Environment,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,090, titled “System And Method For Using Individualized Mixed Document,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,037, titled “Embedding Hot Spots In Electronic Documents,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,085, titled “Embedding Hot Spots In Imaged Documents,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,091, titled “Shared Document Annotation,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,095, titled “Visibly-Perceptible Hot Spots In Documents,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/466,414, titled “Mixed Media Reality Brokerage Network and Methods of Use,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,147, titled “Data Organization and Access for Mixed Media Document System,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,164, titled “Database for Mixed Media Document System,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,024, titled “Triggering Actions With Captured Input In A Mixed Media Environment,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,032, titled “Triggering Applications Based On A Captured Text In A Mixed Media Environment,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,049, titled “Triggering Applications For Distributed Action Execution And Use Of Mixed Media Recognition As A Control Input,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/461,109, titled “Searching Media Content For Objects Specified Using Identifiers,” filed Jul. 31, 2006; U.S. patent application Ser. No. 11/827,530, titled “User Interface For Three-Dimensional Navigation,” filed Jul. 11, 2007; U.S. patent application Ser. No. 12/060,194, titled “Document-Based Networking With Mixed Media Reality,” filed Mar. 31, 2008; U.S. patent application Ser. No. 12/059,583, titled “Invisible Junction Feature Recognition For Document Security Or Annotation,” filed Mar. 31, 2008; U.S. patent application Ser. No. 12/060,198, titled “Document Annotation Sharing,” filed Mar. 31, 2008; U.S. patent application Ser. No. 12/060,200, titled “Ad Hoc Paper-Based Networking With Mixed Media Reality,” filed Mar. 31, 2008; U.S. patent application Ser. No. 12/060,206, titled “Indexed Document Modification Sharing With Mixed Media Reality,” filed Mar. 31, 2008; U.S. patent application Ser. No. 12/121,275, titled “Web-Based Content Detection In Images, Extraction And Recognition,” filed May 15, 2008; U.S. patent application Ser. No. 11/776,510, titled “Invisible Junction Features For Patch Recognition,” filed Jul. 11, 2007; U.S. patent application Ser. No. 11/776,520, titled “Information Retrieval Using Invisible Junctions and Geometric Constraints,” filed Jul. 11, 2007; U.S. patent application Ser. No. 11/776,530, titled “Recognition And Tracking Using Invisible Junctions,” filed Jul. 11, 2007; U.S. patent application Ser. No. 11/777,142, titled “Retrieving Documents By Converting Them to Synthetic Text,” filed Jul. 12, 2007; U.S. patent application Ser. No. 11/624,466, titled “Synthetic Image and Video Generation From Ground Truth Data,” filed Jan. 18, 2007; U.S. patent application Ser. No. 12/210,511, titled “Architecture For Mixed Media Reality Retrieval Of Locations And Registration Of Images,” filed Sep. 15, 2008; U.S. patent application Ser. No. 12/210,519, titled “Automatic Adaption Of An Image Recognition System To Image Capture Devices,” filed Sep. 15, 2008; U.S. patent application Ser. No. 12/210,532, titled “Computation Of A Recognizability Score (Quality Predictor) For Image Retrieval,” filed Sep. 15, 2008; and U.S. patent application Ser. No. 12/210,540, titled “Combining Results Of Image Retrieval Processes” filed Sep. 15, 2008; all of which are incorporated by reference herein in their entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5010581 | Kanno | Apr 1991 | A |
| 5579471 | Barber et al. | Nov 1996 | A |
| 5754772 | Leaf | May 1998 | A |
| 5757953 | Jang | May 1998 | A |
| 5848184 | Taylor et al. | Dec 1998 | A |
| 5867597 | Peairs et al. | Feb 1999 | A |
| 5889886 | Mahoney | Mar 1999 | A |
| 5907835 | Yokomizo et al. | May 1999 | A |
| 5933823 | Cullen | Aug 1999 | A |
| 6006240 | Handley | Dec 1999 | A |
| 6026411 | Delp | Feb 2000 | A |
| 6067369 | Kamei | May 2000 | A |
| 6121969 | Jain et al. | Sep 2000 | A |
| 6404925 | Foote et al. | Jun 2002 | B1 |
| 6430312 | Huang et al. | Aug 2002 | B1 |
| 6445834 | Rising, III | Sep 2002 | B1 |
| 6470094 | Lienhart et al. | Oct 2002 | B1 |
| 6625311 | Zhu | Sep 2003 | B1 |
| 6686970 | Windle | Feb 2004 | B1 |
| 6693649 | Lipscomb et al. | Feb 2004 | B1 |
| 6781694 | Nahum et al. | Aug 2004 | B2 |
| 6874131 | Blumberg | Mar 2005 | B2 |
| 6874420 | Lewis et al. | Apr 2005 | B2 |
| 6958821 | McIntyre | Oct 2005 | B1 |
| 6981224 | Gardner | Dec 2005 | B1 |
| 6999204 | Mortenson et al. | Feb 2006 | B2 |
| 7013289 | Horn | Mar 2006 | B2 |
| 7035467 | Nicponski | Apr 2006 | B2 |
| 7054489 | Yamaoka et al. | May 2006 | B2 |
| 7150021 | Vajjhala et al. | Dec 2006 | B1 |
| 7213101 | Srinivasan et al. | May 2007 | B1 |
| 7281199 | Nicol et al. | Oct 2007 | B1 |
| 7362323 | Doyle | Apr 2008 | B2 |
| 7379627 | Li et al. | May 2008 | B2 |
| 7403642 | Zhang et al. | Jul 2008 | B2 |
| 7457825 | Li et al. | Nov 2008 | B2 |
| 7463790 | Shepherd | Dec 2008 | B2 |
| 7620254 | Hahn et al. | Nov 2009 | B2 |
| 7623259 | Tojo | Nov 2009 | B2 |
| 7647331 | Li et al. | Jan 2010 | B2 |
| 7702681 | Brewer | Apr 2010 | B2 |
| 7725508 | Lawarence et al. | May 2010 | B2 |
| 7742953 | King et al. | Jun 2010 | B2 |
| 7765231 | Rathus et al. | Jul 2010 | B2 |
| 7787655 | Cohen | Aug 2010 | B1 |
| 7801845 | King et al. | Sep 2010 | B1 |
| 7809192 | Gokurk et al. | Oct 2010 | B2 |
| 7894684 | Monobe et al. | Feb 2011 | B2 |
| 7930292 | Nakajima | Apr 2011 | B2 |
| 8036441 | Frank et al. | Oct 2011 | B2 |
| 8212832 | Stefanidis | Jul 2012 | B2 |
| 8276088 | Ke et al. | Sep 2012 | B2 |
| 8326037 | Abitz et al. | Dec 2012 | B1 |
| 8332401 | Hull et al. | Dec 2012 | B2 |
| 8335789 | Hull et al. | Dec 2012 | B2 |
| 8369655 | Moraleda et al. | Feb 2013 | B2 |
| 8385589 | Erol et al. | Feb 2013 | B2 |
| 8385660 | Moraleda et al. | Feb 2013 | B2 |
| 8386336 | Fox et al. | Feb 2013 | B1 |
| 8600989 | Hull et al. | Dec 2013 | B2 |
| 8612475 | Graham et al. | Dec 2013 | B2 |
| 8676810 | Moraleda | Mar 2014 | B2 |
| 8825682 | Kishi et al. | Sep 2014 | B2 |
| 8838591 | Hull et al. | Sep 2014 | B2 |
| 8856108 | Erol et al. | Oct 2014 | B2 |
| 8868555 | Erol et al. | Oct 2014 | B2 |
| 8892595 | Graham et al. | Nov 2014 | B2 |
| 8949287 | Hull et al. | Feb 2015 | B2 |
| 8965145 | Moraleda et al. | Feb 2015 | B2 |
| 8989431 | Erol et al. | Mar 2015 | B1 |
| 9020966 | Erol et al. | Apr 2015 | B2 |
| 9058331 | Graham et al. | Jun 2015 | B2 |
| 9063952 | Moraleda et al. | Jun 2015 | B2 |
| 9063953 | Hull et al. | Jun 2015 | B2 |
| 9087104 | Graham et al. | Jul 2015 | B2 |
| 9092423 | Moraleda | Jul 2015 | B2 |
| 9171202 | Hull et al. | Oct 2015 | B2 |
| 9176984 | Hull et al. | Nov 2015 | B2 |
| 20010019636 | Slatter | Sep 2001 | A1 |
| 20010037454 | Botti et al. | Nov 2001 | A1 |
| 20010047373 | Jones | Nov 2001 | A1 |
| 20020008697 | Deering | Jan 2002 | A1 |
| 20020029232 | Bobrow et al. | Mar 2002 | A1 |
| 20020069418 | Philips | Jun 2002 | A1 |
| 20020126905 | Suzuki et al. | Sep 2002 | A1 |
| 20020129057 | Spielberg | Sep 2002 | A1 |
| 20020131641 | Luo et al. | Sep 2002 | A1 |
| 20020145746 | Mortenson et al. | Oct 2002 | A1 |
| 20020146176 | Meyers | Oct 2002 | A1 |
| 20020161673 | Lee | Oct 2002 | A1 |
| 20020161747 | Li et al. | Oct 2002 | A1 |
| 20020198789 | Waldman | Dec 2002 | A1 |
| 20030012428 | Syeda-Mahmood | Jan 2003 | A1 |
| 20030026457 | Nahum | Feb 2003 | A1 |
| 20030063319 | Umeda et al. | Apr 2003 | A1 |
| 20030063673 | Riemens et al. | Apr 2003 | A1 |
| 20030069932 | Hall et al. | Apr 2003 | A1 |
| 20030115481 | Baird et al. | Jun 2003 | A1 |
| 20030169910 | Reisman et al. | Sep 2003 | A1 |
| 20030169922 | Kamon | Sep 2003 | A1 |
| 20030179230 | Seidman | Sep 2003 | A1 |
| 20030190094 | Yokota | Oct 2003 | A1 |
| 20030195883 | Mojsilovic et al. | Oct 2003 | A1 |
| 20040012569 | Hara | Jan 2004 | A1 |
| 20040015495 | Kim et al. | Jan 2004 | A1 |
| 20040047499 | Shams | Mar 2004 | A1 |
| 20040190791 | Oyabu et al. | Sep 2004 | A1 |
| 20040198396 | Fransioli | Oct 2004 | A1 |
| 20040205466 | Kuppinger et al. | Oct 2004 | A1 |
| 20040220898 | Eguchi et al. | Nov 2004 | A1 |
| 20040264780 | Zhang | Dec 2004 | A1 |
| 20050021478 | Gautier et al. | Jan 2005 | A1 |
| 20050069291 | Voss et al. | Mar 2005 | A1 |
| 20050080627 | Hennebert et al. | Apr 2005 | A1 |
| 20050080871 | Dinh et al. | Apr 2005 | A1 |
| 20050084154 | Li et al. | Apr 2005 | A1 |
| 20050088684 | Naito et al. | Apr 2005 | A1 |
| 20050097435 | Prakash et al. | May 2005 | A1 |
| 20050108406 | Lee et al. | May 2005 | A1 |
| 20050111738 | Iizuka | May 2005 | A1 |
| 20050169511 | Jones | Aug 2005 | A1 |
| 20050187768 | Godden | Aug 2005 | A1 |
| 20050244059 | Turski | Nov 2005 | A1 |
| 20050256866 | Lu et al. | Nov 2005 | A1 |
| 20050259866 | Jacobs et al. | Nov 2005 | A1 |
| 20050262240 | Drees | Nov 2005 | A1 |
| 20060014317 | Farnworth | Jan 2006 | A1 |
| 20060047639 | King et al. | Mar 2006 | A1 |
| 20060053101 | Stuart et al. | Mar 2006 | A1 |
| 20060079214 | Mertama et al. | Apr 2006 | A1 |
| 20060080286 | Svendsen | Apr 2006 | A1 |
| 20060114485 | Sato | Jun 2006 | A1 |
| 20060140614 | Kim et al. | Jun 2006 | A1 |
| 20060147107 | Zhang et al. | Jul 2006 | A1 |
| 20060173560 | Widrow | Aug 2006 | A1 |
| 20060192997 | Matsumoto et al. | Aug 2006 | A1 |
| 20060200347 | Kim et al. | Sep 2006 | A1 |
| 20060253491 | Gokturk et al. | Nov 2006 | A1 |
| 20060264209 | Atkinson et al. | Nov 2006 | A1 |
| 20060294094 | King | Dec 2006 | A1 |
| 20070006129 | Cieslak et al. | Jan 2007 | A1 |
| 20070041642 | Romanoff et al. | Feb 2007 | A1 |
| 20070063050 | Attia et al. | Mar 2007 | A1 |
| 20070078846 | Gulli et al. | Apr 2007 | A1 |
| 20070118794 | Hollander et al. | May 2007 | A1 |
| 20070236712 | Li | Oct 2007 | A1 |
| 20070237426 | Xie et al. | Oct 2007 | A1 |
| 20070242626 | Altberg | Oct 2007 | A1 |
| 20070300142 | King | Dec 2007 | A1 |
| 20080004944 | Calabria | Jan 2008 | A1 |
| 20080009268 | Ramer et al. | Jan 2008 | A1 |
| 20080059419 | Auerbach et al. | Mar 2008 | A1 |
| 20080071929 | Motte et al. | Mar 2008 | A1 |
| 20080120321 | Liu | May 2008 | A1 |
| 20080141117 | King | Jun 2008 | A1 |
| 20080177541 | Satomura | Jul 2008 | A1 |
| 20080317383 | Franz et al. | Dec 2008 | A1 |
| 20090059922 | Appelman | Mar 2009 | A1 |
| 20090228126 | Spielberg et al. | Sep 2009 | A1 |
| 20090248665 | Garg et al. | Oct 2009 | A1 |
| 20100013615 | Hebert et al. | Jan 2010 | A1 |
| 20100040296 | Ma et al. | Feb 2010 | A1 |
| 20100042511 | Sundaresan et al. | Feb 2010 | A1 |
| 20100046842 | Conwell | Feb 2010 | A1 |
| 20100057556 | Rousso et al. | Mar 2010 | A1 |
| 20100211567 | Abir | Aug 2010 | A1 |
| 20100239175 | Bober et al. | Sep 2010 | A1 |
| 20100306273 | Branigan et al. | Dec 2010 | A1 |
| 20110035384 | Qiu | Feb 2011 | A1 |
| 20110093492 | Sull et al. | Apr 2011 | A1 |
| 20110125727 | Zou et al. | May 2011 | A1 |
| 20110167064 | Achtermann et al. | Jul 2011 | A1 |
| 20110173521 | Horton et al. | Jul 2011 | A1 |
| 20110314031 | Chittar et al. | Dec 2011 | A1 |
| 20120166435 | Graham | Jun 2012 | A1 |
| 20120173504 | Moraleda | Jul 2012 | A1 |
| 20130027428 | Graham et al. | Jan 2013 | A1 |
| 20130031100 | Graham et al. | Jan 2013 | A1 |
| 20130031125 | Graham et al. | Jan 2013 | A1 |
| 20150139540 | Moraleda et al. | May 2015 | A1 |
| 20150287228 | Moraleda et al. | Oct 2015 | A1 |
| 20150324848 | Graham et al. | Nov 2015 | A1 |
| 20150350151 | Graham et al. | Dec 2015 | A1 |
| Number | Date | Country |
|---|---|---|
| 09-006961 | Jan 1997 | JP |
| 9134372 | May 1997 | JP |
| 10-0240765 | Sep 1998 | JP |
| 11-234560 | Aug 1999 | JP |
| 2001-265811 | Sep 2001 | JP |
| 2002521752 | Jul 2002 | JP |
| 2003-178081 | Jun 2003 | JP |
| 2004-055658 | Feb 2004 | JP |
| 2004234656 | Aug 2004 | JP |
| 2005-011005 | Jan 2005 | JP |
| 2005100274 | Apr 2005 | JP |
| 2005157931 | Jun 2005 | JP |
| 2005-242579 | Sep 2005 | JP |
| 2006-229465 | Aug 2006 | JP |
| 2007-072573 | Mar 2007 | JP |
| 2007-140613 | Jun 2007 | JP |
| 2007-174270 | Jul 2007 | JP |
| 2007264992 | Oct 2007 | JP |
| 2008-158823 | Jul 2008 | JP |
| WO0005663 | Feb 2000 | WO |
| WO2006092957 | Sep 2006 | WO |
| 2007023994 | Mar 2007 | WO |
| Entry |
|---|
| Non-Final Office Action for U.S. Appl. No. 12/060,198, dated Nov. 7, 2013, 55 pages. |
| Final Office Action for U.S. Appl. No. 12/060,200, dated Nov. 8, 2013, 58 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/273,186, dated Dec. 5, 2013, 25 pages. |
| Final Office Action for U.S. Appl. No. 11/461,085, dated Dec. 10, 2013, 16 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/729,458, dated Dec. 17, 2013, 8 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/253,715, dated Dec. 19, 2013, 38 pages. |
| Notice of Allowance for U.S. Appl. No. 12/240,596, dated Dec. 23, 2013, 10 pages. |
| Final Office Action for U.S. Appl. No. 11/461,164, dated Dec. 26, 2013, 17 pages. |
| Final Office Action for U.S. Appl. No. 13/330,492, dated Jan. 2, 2014, 15 pages. |
| Final Office Action for U.S. Appl. No. 12/719,437, dated Jan. 16, 2014, 22 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/789,669, dated Jan. 17, 2014, 6 pages. |
| Final Office Action for U.S. Appl. No. 13/192,458, dated Jan. 27, 2014, 13 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/340,124, dated Jan. 29, 2014, 24 pages. |
| JP Office Action for JP Patent Application No. 2009-119205 dated Feb. 19, 2013, 2 pages. |
| U.S. Appeal Decision, U.S. Appl. No. 11/461,164, dated Feb. 27, 2013, 10 pages. |
| U.S. Appeal Decision, U.S. Appl. No. 11/461,147, dated Mar. 4, 2013, 11 pages. |
| U.S. Appeal Decision, U.S. Appl. No. 11/461,109, dated Mar. 13, 2013, 23 pages. |
| US Non-Final Office Action for U.S. Appl. No. 12/060,200, dated Mar. 22, 2013, 47 pages. |
| US Final Office Action for U.S. Appl. No. 11/461,279 dated Mar. 25, 2013, 36 pages. |
| US Non-Final Office Action for U.S. Appl. No. 12/060,198 dated Apr. 2, 2013, 56 pages. |
| US Notice of Allowance for U.S. Appl. No. 13/415,228 dated Apr. 30, 2013, 10 pages. |
| US Notice of Allowance for U.S. Appl. No. 12/210,519 dated May 1, 2013, 24 pages. |
| US Notice of Allowance for U.S. Appl. No. 13/273,189 dated May 9, 2013, 11 pages. |
| US Notice of Allowance for U.S. Appl. No. 11/461,300 dated May 15, 2013, 13 pages. |
| US Final Office Action for U.S. Appl. No. 13/273,186, dated Jun. 12, 2013, 24 pages. |
| US Non-Final Office Action for U.S. Appl. No. 11/461,037, dated Jun. 24, 2013, 25 pages. |
| US Non-Final Office Action for U.S. Appl. No. 12/719,437, dated Jun. 25, 2013, 22 pages. |
| US Notice of Allowance for U.S. Appl. No. 11/461,279, dated Jul. 31, 2013, 14 pages. |
| JP Office Action for JP Application No. 2009212242 dated Jul. 16, 2013, 2 pages. |
| US Non-Final Office Action for U.S. Appl. No. 11/461,085, dated Jul. 9, 2013, 11 pages. |
| European Office Action for Application No. 08 252 377.0, dated Aug. 9, 2013, 5 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/330,492, dated Aug. 27, 2013, 14 pages. |
| Non-Final Office Action for U.S. Appl. No. 11/461,164, dated Aug. 30, 2013, 19 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/240,596, dated Sep. 5, 2013, 17 pages. |
| Non-Final Office Action for U.S. Appl. No. 11/461,109, dated Sep. 9, 2013, 14 pages. |
| European Search Report for Application No. 12159375.0, dated Sep. 12, 2013, 9 pages. |
| Notice of Allowance for U.S. Appl. No. 13/273,189, dated Sep. 13, 2013, 15 pages. |
| Non-Final Office Action for U.S. Appl. No. 11/461,147, dated Sep. 27, 2013, 15 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/210,532, dated Oct. 7, 2013, 18 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/247,205, dated Oct. 7, 2013, 19 pages. |
| Final Office Action for U.S. Appl. No. 11/461,037, dated Oct. 24, 2013, 24 pages. |
| Chi-Hung Chi et al. , Context Query in Information Retrieval, dated 2002, Proceedings of the 14th IEEE International Conference on Tools with Artificial Intelligence (ICTAI'02) 6 pages (http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=1180793). |
| U.S. Office Action, U.S. Appl. No. 12/059,583, dated Sep. 10, 2012, 41 pages. |
| U.S. Notice of Allowance, U.S. Appl. No. 12/240,590, dated Oct. 1, 2012, 19 pages. |
| U.S. Notice of Allowance, U.S. Appl. No. 12/491,018, dated Oct. 11, 2012, 13 pages. |
| U.S. Office Action, U.S. Appl. No. 13/192,458, dated Oct. 11, 2012, 30 pages. |
| U.S. Office Action, U.S. Appl. No. 13/415,756, dated Oct. 26, 2012, 40 pages. |
| U.S. Office Action, U.S. Appl. No. 12/253,715, dated Nov. 14, 2012, 76 pages. |
| U.S. Office Action, U.S. Appl. No. 11/461,300, dated Nov. 28, 2012, 37 pages. |
| U.S. Notice of Allowance, U.S. Appl. No. 12/121,275, dated Nov. 28, 2012, 31 pages. |
| JP Office Action, JP Application No. 2008-180789, dated Sep. 25, 2012, 3 pages. |
| Tomohiro Nakai; Document Image Retrieval Based on Cross-Ration and Hashing IEICE Technical Report; The Institute of Electronics, Information and Communication Engineers; dated Mar. 11, 2005; vol. 104 No. 742; pp. 103-108. |
| U.S. Office Action, U.S. Appl. No. 13/415,228, dated Dec. 3, 2012, 38 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/933,078, dated Mar. 17, 2014, 9 pages. |
| Notice of Allowance for U.S. Appl. No. 13/273,186, dated Mar. 26, 2014, 9 pages. |
| Notice of Allowance for U.S. Appl. No. 11/461,037, dated Apr. 3, 2014, 10 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/060,200, dated Apr. 8, 2014, 65 pages. |
| Non-Final Office Action for U.S. Appl. No. 11/461,085, dated Apr. 9, 2014, 16 pages. |
| Final Office Action for U.S. Appl. No. 11/461,147, dated Apr. 24, 2014, 11 pages. |
| Notice of Allowance for U.S. Appl. No. 12/210,511, dated Apr. 30, 2014, 11 pages. |
| Final Office Action for U.S. Appl. No. 12/247,205, dated May 13, 2014, 17 pages. |
| Notice of Allowance for U.S. Appl. No. 12/210,540, dated May 22, 2014, 20 pages. |
| Final Office Action for U.S. Appl. No. 13/729,458, dated Jun. 2, 2014, 8 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/192,458, dated Jun. 5, 2014, 12 pages. |
| Final Office Action for U.S. Appl. No. 12/060,198, dated Jun. 5, 2014, 63 pages. |
| Josef Sivic, “Video Google: A Text Retrieval Approach to Object Matching in Videos,” IEEE, Proceedings of the Ninth IEEE International Conference on Computer Vision (ICCV 2003), 8 pages, vol. 2. |
| Japanese Office Action for JP Application No. 2013222652, dated May 20, 2014, 5 pages. |
| Japanese Office Action for JP Application No. 2013222655, dated May 20, 2014, 4 pages. |
| U.S. Office Action, U.S. Appl. No. 13/273,189, dated Nov. 28, 2012, 26 pages. |
| U.S. Office Action, U.S. Appl. No. 13/273,186, dated Dec. 17, 2012, 28 pages. |
| U.S. Office Action, U.S. Appl. No. 11/461,279, dated Dec. 19, 2012, 31 pages. |
| U.S. Notice of Allowability, U.S. Appl. No. 12/240,590, dated Dec. 20, 2012, 4 pages. |
| U.S. Office Action, U.S. Appl. No. 11/461,037, dated Jan. 7, 2013, 21 pages. |
| U.S. Appeal Decision, U.S. Appl. No. 11/461,085, dated Jan. 23, 2013, 8 pages. |
| U.S. Office Action, U.S. Appl. No. 12/340,124, dated Jan. 23, 2013, 23 pages. |
| U.S. Notice of Allowance, U.S. Appl. No. 13/415,756, dated Feb. 4, 2013, 7 pages. |
| U.S. Office Action, U.S. Appl. No. 12/060,206, dated Feb. 8, 2013, 16 pages. |
| Hirokazu Kate et al., A Registration Method for Augmented Reality based on Matching Templates Generated from Texture Image, Transaction for the Virtual Reality Society of Japan, The Virtual Reality Society of Japan, 2002, vol. 7, No. 2, pp. 119-128. |
| Japanese Office Action, JP2008-180790, dated May 22, 2012, 3 pages. |
| Japanese Office Action, JP2008-180791, dated May 22, 2012, 4 pages. |
| Japanese Office Action, JP2008-180792, dated May 22, 2012, 3 pages. |
| Japanese Office Action, JP2008-180793, dated May 29, 2012, 3 pages. |
| Japanese Office Action, JP2008-180794, dated May 22, 2012, 3 pages. |
| United States Final Office Action, U.S. Appl. No. 12/247,205, dated May 23, 2012, 50 pages. |
| United States Final Office Action, U.S. Appl. No. 12/210,532, dated Jun. 5, 2012, 48 pages. |
| United States Non-Final Office Action, U.S. Appl. No. 11/461,037, dated Jun. 13, 2012, 46 pages. |
| United States Final Office Action, U.S. Appl. No. 12/240,596, dated Jun. 14, 2012, 28 pages. |
| United States Non-Final Office Action, U.S. Appl. No. 12/340,124, dated Jun. 27, 2012, 31 pages. |
| United States Final Office Action, U.S. Appl. No. 12/210,519, dated Jun. 28, 2012, 33 pages. |
| United States Final Office Action, U.S. Appl. No. 12/491,018, dated Jun. 28, 2012, 64 pages. |
| United States Final Office Action, U.S. Appl. No. 11/461,300, dated Jul. 13, 2012, 33 pages. |
| United States Notice of Allowance, U.S. Appl. No. 11/461,294, dated Aug. 9, 2012, 33 pages. |
| United States Final Office Action, U.S. Appl. No. 11/461,279, dated Aug. 10, 2012, 50 pages. |
| United States Notice of Allowance, U.S. Appl. No. 11/461,286, dated Aug. 14, 2012, 42 pages. |
| Notice of Allowance for U.S. Appl. No. 13/729,458, dated Sep. 29, 2014, 8 pages. |
| Final Office Action for U.S. Appl. No. 13/933,078, dated Oct. 6, 2014, 14 pages. |
| Notice of Allowance for U.S. Appl. No. 12/060,200, dated Nov. 5, 2014, 8 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/789,669, dated Nov. 19, 2014, 13 pages. |
| Final Office Action for U.S. Appl. No. 13/330,492, dated Nov. 26, 2014, 18 pages. |
| Notice of Allowance for U.S. Appl. No. 12/340,124, dated Dec. 19, 2014, 12 pages. |
| Non-Final Office Action for U.S. Appl. No. 11/461,109 dated Jun. 26, 2014, 18 pages. |
| Notice of Allowance for U.S. Appl. No. 13/273,186 dated Jul. 10, 2014, 9 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/330,492 dated Jul. 17, 2014, 16 pages. |
| Final Office Action for U.S. Appl. No. 12/253,715, dated Jul. 25, 2014, 40 pages. |
| Final Office Action for U.S. Appl. No. 12/340,124, dated Aug. 21, 2014, 26 pages. |
| Final Office Action for U.S. Appl. No. 13/789,669 dated Aug. 29, 2014, 9 pages. |
| Non-Final Office Action for U.S. Appl. No. 11/461,164, dated Sep. 15, 2014, 18 pages. |
| Notice of Allowance for U.S. Appl. No. 11/461,085, dated Sep. 17, 2014, 5 pages. |
| Moghaddam et al., Visualization and User-Modeling for Browsing Personal Photo Libraries, Mitsubishi Electric Research Laboratories, dated Feb. 2004, 34 pages. |
| Japanese Application Office Action for JP Publication No. 2013-192033, dated Jun. 24, 2014, 7 pages. |
| Japanese Application Office Action for JP Publication No. 2013-222655, dated Aug. 26, 2014, 5 pages. |
| Jonathan Hull, Mixed Media Reality (MMR) A New Method of eP-Fusion, Ricoh Technical Report, Ricoh Company, Ltd., dated Dec. 1, 2007, No. 33, p. 119-125; online search dated Aug. 22, 2013 <URL: http://www.ricoh.com/ja/technology/techreport/33/pdf/A3314.pdf >. |
| Notice of Allowance for U.S. Appl. No. 12/247,205, dated Apr. 8, 2015, 15 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/330,492, dated Apr. 8, 2015, 19 pages. |
| Notice of Allowance for U.S. Appl. No. 12/719,437, dated Apr. 10, 2015, 16 pages. |
| Notice of Allowance for U.S. Appl. No. 13/933,078, dated May 16, 2015, 7 pages. |
| Non-Final Office Action for U.S. Appl. No. 11/461,109, dated Jun. 15, 2015, 18 pages. |
| Non-Final Office Action for U.S. Appl. No. 11/461,164, dated Jun. 30, 2015, 20 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/253,715, dated Jan. 7, 2015, 35 pages. |
| Final Office Action for U.S. Appl. No. 11/461,109, dated Jan. 15, 2015, 20 pages. |
| Notice of Allowance for U.S. Appl. No. 13/192,458, dated Jan. 28, 2015, 9 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/933,078, dated Feb. 26, 2015, 7 pages. |
| Final Office Action for U.S. Appl. No. 11/461,164, dated Mar. 12, 2015, 19 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/060,198, dated Mar. 13, 2015, 22 pages. |
| Notice of Allowance for U.S. Appl. No. 13/789,669, dated Mar. 16, 2015, 8 pages. |
| Non-Final Office Action for U.S. Appl. No. 11/461,147, dated Mar. 20, 2015, 11 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/059,583, dated Jul. 2, 2015, Jonathan J. Hull, 29 pages. |
| Non-Final Office Action for U.S. Appl. No. 12/060,206, dated Jul. 23, 2015, Berna Erol et al., 23 pages. |
| Non-Final Office Action for U.S. Appl. No. 14/604,619, dated Oct. 7, 2015, Moraleda et al., 9 pages. |
| Final Office Action for U.S. Appl. No. 13/330,492, dated Oct. 8, 2015, Graham et al., 20 pages. |
| Final Office Action for U.S. Appl. No. 12/060,198, dated Oct. 8, 2015, Erol et al., 32 pages. |
| Non-Final Office Action for U.S. Appl. No. 13/914,417, dated Oct. 14, 2015, Erol et al., 18 pages. |
| Final Office Action for U.S. Appl. No. 11/461,109, dated Nov. 10, 2015, Erol et al., 21 pages. |
| Final Office Action for U.S. Appl. No. 11/461,164, dated Nov. 27, 2015, Hull et al., 20 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20120257237 A1 | Oct 2012 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12253815 | Oct 2008 | US |
| Child | 13494008 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11461017 | Jul 2006 | US |
| Child | 12253815 | US | |
| Parent | 11461279 | Jul 2006 | US |
| Child | 11461017 | US | |
| Parent | 11461286 | Jul 2006 | US |
| Child | 11461279 | US | |
| Parent | 11461294 | Jul 2006 | US |
| Child | 11461286 | US | |
| Parent | 11461300 | Jul 2006 | US |
| Child | 11461294 | US | |
| Parent | 11461126 | Jul 2006 | US |
| Child | 11461300 | US | |
| Parent | 11461143 | Jul 2006 | US |
| Child | 11461126 | US | |
| Parent | 11461268 | Jul 2006 | US |
| Child | 11461143 | US | |
| Parent | 11461272 | Jul 2006 | US |
| Child | 11461268 | US | |
| Parent | 11461064 | Jul 2006 | US |
| Child | 11461272 | US | |
| Parent | 11461075 | Jul 2006 | US |
| Child | 11461064 | US | |
| Parent | 11461090 | Jul 2006 | US |
| Child | 11461075 | US | |
| Parent | 11461037 | Jul 2006 | US |
| Child | 11461090 | US | |
| Parent | 11461085 | Jul 2006 | US |
| Child | 11461037 | US | |
| Parent | 11461091 | Jul 2006 | US |
| Child | 11461085 | US | |
| Parent | 11461095 | Jul 2006 | US |
| Child | 11461091 | US | |
| Parent | 11466414 | Aug 2006 | US |
| Child | 11461095 | US | |
| Parent | 11461147 | Jul 2006 | US |
| Child | 11466414 | US | |
| Parent | 11461164 | Jul 2006 | US |
| Child | 11461147 | US | |
| Parent | 11461024 | Jul 2006 | US |
| Child | 11461164 | US | |
| Parent | 11461032 | Jul 2006 | US |
| Child | 11461024 | US | |
| Parent | 11461049 | Jul 2006 | US |
| Child | 11461032 | US | |
| Parent | 11461109 | Jul 2006 | US |
| Child | 11461049 | US | |
| Parent | 11827530 | Jul 2007 | US |
| Child | 11461109 | US | |
| Parent | 12060194 | Mar 2008 | US |
| Child | 11827530 | US | |
| Parent | 12059583 | Mar 2008 | US |
| Child | 12060194 | US | |
| Parent | 12060198 | Mar 2008 | US |
| Child | 12059583 | US | |
| Parent | 12060200 | Mar 2008 | US |
| Child | 12060198 | US | |
| Parent | 12060206 | Mar 2008 | US |
| Child | 12060200 | US | |
| Parent | 12121275 | May 2008 | US |
| Child | 12060206 | US | |
| Parent | 11776510 | Jul 2007 | US |
| Child | 12121275 | US | |
| Parent | 11776520 | Jul 2007 | US |
| Child | 11776510 | US | |
| Parent | 11776530 | Jul 2007 | US |
| Child | 11776520 | US | |
| Parent | 11777142 | Jul 2007 | US |
| Child | 11776530 | US | |
| Parent | 11624466 | Jan 2007 | US |
| Child | 11777142 | US | |
| Parent | 12210511 | Sep 2008 | US |
| Child | 11624466 | US | |
| Parent | 12210519 | Sep 2008 | US |
| Child | 12210511 | US | |
| Parent | 12210532 | Sep 2008 | US |
| Child | 12210519 | US | |
| Parent | 12210540 | Sep 2008 | US |
| Child | 12210532 | US |
