Patent Grant
10579741
The presently disclosed inventive concepts relate to machine translation, and more specifically to improving machine translation via adaptively and proactively replacing and/or supplementing inputs for machine translation platforms and solution.
A plethora of online tools exist to facilitate machine translation of textual information from one language to another. As mobile devices become an increasingly prevalent mechanism to access online tools, translation via mobile devices is a useful extension of pre-existing machine translation solutions.
In addition, as optical sensors embedded with mobile devices become more powerful, a wide variety of image-based technologies are migrating to mobile platforms. Accordingly, some translation tools for mobile applications include the ability to extract textual information from image data, so long as the textual information depicted in the image data is of sufficient quality to allow conventional extraction techniques, such as optical character recognition (OCR), to accurately recognize the characters of the text.
However, due to limitations inherent to the mobile device, and also the variability of conditions surrounding capturing an image using a mobile device, it is often difficult, or even impossible, to capture an image of sufficient quality to allow conventional extraction techniques to accurately recognize the characters of the text. As a result, existing machine translation tools are unable to provide an accurate result in many situations.
Accordingly, it would be beneficial to provide systems and techniques for providing accurate translation results of textual information represented in image data even when the image data are of insufficient quality to allow conventional extraction techniques to accurately recognize the characters of the text.
In one embodiment, a computer-implemented method for proactively improving machine translation in real time by processing a translation request includes: receiving the translation request from a mobile device; and either generating or retrieving translation information based on a result of either or both of: determining whether the translation request includes image data suitable for generating a machine translation; and determining whether the translation request includes metadata suitable for generating an estimated translation.
In another embodiment, a computer-implemented method for proactively improving machine translation in real time by generating and submitting a translation request includes: capturing image data; evaluating one or more conditions corresponding to the captured image data; generating metadata corresponding to the captured image data; and generating and submitting the translation request to a machine translation platform.
In still another embodiment, a computer program product for proactively improving machine translation in real time by processing a translation request includes a computer readable storage medium having stored thereon: first program instructions executable by a processor of a CIMTS server to cause the processor to generate or retrieve translation information based on a result of either or both of: determining whether a translation request received from a mobile device includes image data suitable for generating a machine translation; and determining whether the translation request includes metadata suitable for generating an estimated translation.
Other aspects and embodiments of the present invention will become apparent from the following detailed description, which, when taken in conjunction with the drawings, illustrate by way of example the principles of the invention.
The following description is made for the purpose of illustrating the general principles of the present invention and is not meant to limit the inventive concepts claimed herein. Further, particular features described herein can be used in combination with other described features in each of the various possible combinations and permutations.
Unless otherwise specifically defined herein, all terms are to be given their broadest possible interpretation including meanings implied from the specification as well as meanings understood by those skilled in the art and/or as defined in dictionaries, treatises, etc.
It must also be noted that, as used in the specification and the appended claims, the singular forms “a,” “an” and “the” include plural referents unless otherwise specified. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The following description discloses several preferred embodiments of systems, methods and computer program products for improving machine translation in real time, especially machine translation based on image inputs.
In one general embodiment, a computer-implemented method for proactively improving machine translation in real time by processing a translation request includes: receiving the translation request from a mobile device; and either generating or retrieving translation information based on a result of either or both of: determining whether the translation request includes image data suitable for generating a machine translation; and determining whether the translation request includes metadata suitable for generating an estimated translation.
In another general embodiment, a computer-implemented method for proactively improving machine translation in real time by generating and submitting a translation request includes: capturing image data; evaluating one or more conditions corresponding to the captured image data; generating metadata corresponding to the captured image data; and generating and submitting the translation request to a machine translation platform.
In still another general embodiment, a computer program product for proactively improving machine translation in real time by processing a translation request includes a computer readable storage medium having stored thereon: first program instructions executable by a processor of a CIMTS server to cause the processor to generate or retrieve translation information based on a result of either or both of: determining whether a translation request received from a mobile device includes image data suitable for generating a machine translation; and determining whether the translation request includes metadata suitable for generating an estimated translation.
In use, the gateway 101 serves as an entrance point from the remote networks 102 to the proximate network 108. As such, the gateway 101 may function as a router, which is capable of directing a given packet of data that arrives at the gateway 101, and a switch, which furnishes the actual path in and out of the gateway 101 for a given packet.
Further included is at least one data server 114 coupled to the proximate network 108, and which is accessible from the remote networks 102 via the gateway 101. It should be noted that the data server(s) 114 may include any type of computing device/groupware. Coupled to each data server 114 is a plurality of user devices 116. User devices 116 may also be connected directly through one of the networks 104, 106, 108. Such user devices 116 may include a desktop computer, lap-top computer, hand-held computer, printer or any other type of logic. It should be noted that a user device 111 may also be directly coupled to any of the networks, in one embodiment.
A peripheral 120 or series of peripherals 120, e.g., facsimile machines, printers, networked and/or local storage units or systems, etc., may be coupled to one or more of the networks 104, 106, 108. It should be noted that databases and/or additional components may be utilized with, or integrated into, any type of network element coupled to the networks 104, 106, 108. In the context of the present description, a network element may refer to any component of a network.
According to some approaches, methods and systems described herein may be implemented with and/or on virtual systems and/or systems which emulate one or more other systems, such as a UNIX system which emulates an IBM z/OS environment, a UNIX system which virtually hosts a MICROSOFT WINDOWS environment, a MICROSOFT WINDOWS system which emulates an IBM z/OS environment, etc. This virtualization and/or emulation may be enhanced through the use of VMWARE software, in some embodiments.
In more approaches, one or more networks 104, 106, 108, may represent a cluster of systems commonly referred to as a “cloud.” In cloud computing, shared resources, such as processing power, peripherals, software, data, servers, etc., are provided to any system in the cloud in an on-demand relationship, thereby allowing access and distribution of services across many computing systems. Cloud computing typically involves an Internet connection between the systems operating in the cloud, but other techniques of connecting the systems may also be used.
The workstation shown in
The workstation may have resident thereon an operating system such as the Microsoft Windows® Operating System (OS), a MAC OS, a UNIX OS, etc. It will be appreciated that a preferred embodiment may also be implemented on platforms and operating systems other than those mentioned. A preferred embodiment may be written using XML, C, and/or C++ language, or other programming languages, along with an object oriented programming methodology. Object oriented programming (OOP), which has become increasingly used to develop complex applications, may be used.
Now referring to
As will be further understood by persons having ordinary skill in the art, conventional machine translation solutions that rely on a similar client/server-based architecture require high speed and high bandwidth network connections to facilitate sufficient data transfer and feedback between each side of the architecture. Similarly, low latency in the network is key to providing practical machine translation services to users. Further still, security restrictions (e.g. concerning transfer of personal, confidential, or other secure information) represent significant limitations to providing machine translation services.
Moreover, the client/server architecture is common due to the high computational cost and storage requirements associated with performing machine translation and providing translation services to users, especially where the translation workflow accepts or utilizes image data as an input. Image processing (e.g. to normalize an image orientation, color characteristics, etc. as would be understood by skilled artisans in the field of image processing) is a particularly intensive aspect of such solutions, and requires processing power that may not be available on the client side, particularly where the client device is a mobile device. So too is extraction of text, e.g. via OCR, a computationally-intensive operation requiring significant processing power. Translation techniques such as natural language processing (NLP) analysis represent yet another computationally intensive task that may be employed in the translation process. In sum, machine translation techniques of the type described herein are characterized by significant computational costs that often precipitate a need to perform at least some operations of the translation workflow on or within a server environment.
Accordingly, and as will be appreciated further upon reviewing the additional descriptions below, the presently disclosed inventive machine translation techniques represent an improvement to machine translation systems and architectures. Implementing the architecture and techniques described herein enables accurate accomplishment of machine translation while significantly reducing the computational cost of performing such translation, particularly from image data inputs.
In brief, and again as described further below, determining whether image data are of sufficient quality to accurately recognize and extract data therefrom, and if not selecting substitute or alternate inputs to accomplish translation may avoid the need to attempt processing the low-quality image, recognizing text depicted therein, extracting text, and translating the extracted text when such operations are unlikely or incapable of producing an accurate result. Similarly, even if image data are of sufficient quality to be processed and text therein translated, if a same or similar image has been previously translated using the system, the presently disclosed inventive concepts enable provision of accurate translation results directly without engaging in the computationally-intensive process of processing the image, recognizing the content, extracting the text, and translating the extracted text.
The presently disclosed inventive concepts also represent an improvement to the field of machine translation by way of enabling the generation and/or retrieval of translation information under circumstances that would not allow accurate translation using conventional approaches and systems. For instance, when conditions surrounding the process of capturing an image (e.g. weather, illumination, distance, etc.) preclude the ability to capture an image of sufficient quality to enable machine translation, the presently disclosed inventive concepts may nonetheless provide an accurate translation result, e.g. based on analyzing metadata associated with the image and/or provided from the client side 302.
Such metadata may, for example, identify location information concerning the client at the time of the capture operation or at the time of submitting a translation request, such as mobile device GPS coordinates, mobile device position, azimuth, orientation of the capture device optical sensors, users' native or desired destination language (i.e. the language into which text should be translated), metrics describing the captured image (e.g. illumination, color depth, resolution, aspect ratio, contrast, orientation, etc.), and/or any other suitable metadata content as described herein and as would be understood by a person having ordinary skill in the art as suitable for use in performing machine translation according to the instant descriptions and upon reading the present disclosure.
In some approaches, providing accurate machine translation results may be accomplished using only metadata, in which case the presently disclosed inventive concepts further improve the function of machine translation systems by enabling accurate translation results without requiring the transfer of significant quantities of data (e.g. image data) between the client and server sides of the system. For instance, metadata regarding image quality and/or capture location (position, orientation, etc. as noted above) may be provided prior to transferring the image data from the client side 302 to the server side 304. By analyzing the metadata, the server side 304 may determine whether a previous translation corresponding to a same or very similar capture location has been accomplished, and if so provide the translation result to the client side 302 without requiring any image data transfer. Similarly if image data quality are insufficient, the server side 304 may request the user alter the image or capture another image for translation, thereby avoiding the need to transmit image data which are not suitable as input for machine translation over the network. This may reduce overall network traffic, as well as serve the user's advantage by reducing amount of data usage consumed to accomplish the translation task.
Returning now to
As will be described in further detail below, the client side 302 in preferred embodiments conveys a significant advantage and improvement to CIMTS platform 300 functionality by providing metadata descriptive of captured image data and/or conditions relating to capture of the image data. These data may, in some embodiments, be critical to determining appropriate substitute inputs and/or processing workflow operations to accomplish machine translation. Accordingly, in preferred approaches the metadata generated by the client side 302 facilitates substitution of inputs for translation as well as intelligent selection of inputs for improving the function of machine translation systems by reducing computational cost, network bandwidth and/or data usage.
With continuing reference to
For instance in one embodiment the user may interact with the CIMTS client GUI 306 (e.g. by invoking and app installed on the mobile device, via a call to the OS, launching a program on a workstation, etc.) and in the process of seeking a translation may invoke the capture device 308 of the client side 302 to capture image data depicting the textual information for which translation is sought.
The CIMTS client GUI 306 may also facilitate defining native languages, secondary languages, default locations, permissions to access location and/or personal information, permissions to enable or disable real-time translation input selection (including selecting between image data and metadata, selecting only metadata, and/or replacing or substituting captured image data with image data from a repository, etc. as described in further detail herein), sharing settings, etc. as may be useful to accomplish accurate, efficient machine translation using the CIMTS platform 300, in preferred approaches.
To facilitate translation in a manner appropriate for the individual engaging the CIMTS platform 300, e.g. to ensure translations are made to the correct destination language such as a user's native language or a language selected by the user, the CIMTS client GUI 306 is also communicatively coupled to the user module 318 according to preferred embodiments. The user module 318 may include a plurality of user profiles and/or settings 318a, 318b, 318c . . . 318n.
Each profile and/or group of settings 318a . . . 318n may include information regarding individual users such as native language, languages which the user may speak and/or read (whether native or non-native), degree of fluency in various respective languages, desired destination language for translations, language spoken in the user's place of current residence, etc. as would be understood by a person having ordinary skill in the art upon reading the present disclosures. Any one or more of the foregoing information types may be leveraged in any combination for translation without departing from the scope of the presently disclosed inventive concepts.
The user module 318 may also facilitate providing feedback regarding translation results, desired destination language, etc. to the client side 302 via the CIMTS feedback agent 322, and therefore may be communicatively coupled to the CIMTS feedback agent 322. Feedback and/or translation results may therefore optionally be stored in a corresponding user profile and/or group of settings 318a . . . 318n, in various embodiments. For instance, translation results received from the server side 304 via the network may be provided to the client side 302 via a CIMTS receiver module 320, which may communicate such results to the user module 318 for storage in the appropriate user profile and/or group of settings 318a . . . 318n, and optionally provided to the CIMTS feedback agent 322 for requesting user feedback and returning such feedback to the server side 304.
In another embodiment the CIMTS client GUI may instruct, e.g. in response to a user invoking the capture device 308, the CIMTS condition evaluator 312 to analyze and/or record conditions relevant to machine translation (e.g. time of day, weather, location information, network connectivity and/or speed etc.). Thus the CIMTS condition evaluator 312 may be in communication with other sensors, components, and/or software (e.g. weather applications, map applications, etc.) resident on the client side 302 or mobile device/workstation upon which client side 302 is embodied. These other sensors, components, and/or software are not depicted in
Preferably, the CIMTS condition evaluator 312 may provide an instruction to the image submitting module to enable input selection and/or replacement in response to detecting particular conditions associated with a request, such as a time of day being outside a predefined suitable capture time window (e.g. excluding hours where insufficient daylight or other ambient light is available to capture high quality images) or weather at time of capture indicating poor image quality (such as fog, rain, snow, smog or other conditions likely to negatively impact image quality).
Client side 302 may also include a metadata generator 310 in communication with the capture device 308 and/or image submitting module 314. The metadata generator 310 preferably generates metadata relevant to machine translation, particularly camera input machine translation. As such, metadata generator 310 may be configured to determine and/or receive, e.g. from the capture device 308, and/or other sensors, components and/or software of the mobile device such as an accelerometer, GPS receiver, gyroscope, barometer, compass, etc. (not shown in
Accordingly, exemplary metadata which may be generated by metadata generator 310 may encompass any single data point or combination of data descriptive of: capture device position (e.g. GPS coordinates from a GPS receiver); capture device orientation (e.g. facing direction as may be determined from the compass); capture azimuth (e.g. as may be determined using the compass and/or gyroscope); image resolution (e.g. as may be reported by the capture device); capture flash setting (e.g. as may be reported by the capture device); image illumination level (e.g. as may be reported by the capture device), or any other suitable type of metadata descriptive of image capture characteristic.
Upon receiving the image data, generated metadata, and/or condition data from the metadata generator 310 and/or CIMTS condition evaluator 312, the image submitting module 314 assembles appropriate information into a translation request, and submits the translation request to the server side 304 via the network. As will be understood more clearly upon reviewing the present disclosures in their entirety, the image submitting module 314 may submit such information in a single request, as multiple parts of a single request, or as multiple requests, e.g. by submitting metadata and/or condition data prior to transmitting image data in order to reduce network bandwidth consumption and data usage, as well as to reduce computational cost of accomplishing translations.
Now referring to
Each of the steps of the method 400 may be performed by any suitable component of the operating environment. For example, in various embodiments, the method 400 may be partially or entirely performed using a CIMTS platform 300, and particularly any one or more of the modules client side 302 of a CIMTS platform 300 such as depicted in
As shown in
Method 400 also includes operation 404, in which one or more conditions corresponding to captured image data are evaluated, e.g. via the CIMTS condition evaluator 312 as shown in
In operation 406 of method 400, metadata are generated, e.g. using a metadata generator 310 as shown in
With continuing reference to
Of course, the method 400 may include any number of additional and/or alternative operations, features, and characteristics as described herein, in various embodiments. In one approach, method 400 may include one or more operations following submission of the translation request, such as receiving a translation result from the machine translation platform.
The result may be returned simply for purposes of conveying the desired information to a user, but in more approaches returning results may be part of a user feedback process/mechanism to improve performance of the CIMTS platform 300. Accordingly, in more embodiments method 400 may include receiving user input comprising a confirmation, a negation, or a modification of the translation result; and submitting the user input to the machine translation platform. The user input are preferably utilized by the machine translation platform to adjust one or more parameters associated with processing future translation requests, for instance by modifying a translation result 366n stored in a translation repository 366, by modifying or influencing a ranking of one or more image data and/or metadata records 346n stored in image data and/or metadata repository 346, by modifying or defining one or more settings associated with CIMTS profiles 330, CIMTS rules 332, and/or user characteristic profiles 334, etc. as described herein and would be understood by a person having ordinary skill in the art upon reading the present disclosures.
The repositories 346 and/or 366 may be established at the time of initialization to provide a robust CIMTS platform 300 without requiring substantial user input. Additionally and/or alternatively, repositories may be periodically and/or iteratively updated to ensure the available replacement inputs and associated translation information are accurate and comprehensive.
The image data and/or metadata repository 346 preferably comprises image data received from users of the CIMTS platform in the course of requesting translations, and optionally further includes image data gathered by the CIMTS platform from other sources, such as social media, geolocation services (e.g. map databases, services, etc.), and/or other known sources of image data.
More preferably, the image data and/or metadata repository 346 includes metadata descriptive of the image data and stored in association with the image data in the image data and/or metadata repository 346. The metadata may include any suitable descriptive information regarding the image, and preferably include information descriptive of the subject of the image, image quality, image capture characteristics and or conditions (such as GPS location, camera position, azimuth, orientation, capture time, ambient lighting and/or environmental factors including weather, pollution, etc.), and equivalents of any of the foregoing descriptors as would be understood by a person having ordinary skill in the art upon reviewing the instant disclosures. In some approaches, image data received or collected from sources outside the CIMTS platform may be received and/or collected in connection with any suitable metadata descriptive of the image data.
In more approaches, and as will be discussed further below regarding the translation repository 366, the image data and/or associated metadata are preferably associated with a unique image identifier for each image stored in the image data and/or metadata repository 346. The image identifier may facilitate facile and rapid retrieval of prior translation results and/or identifying suitable images to use as a substitute input for translation requests submitted with inferior or inadequate image data, or to reduce computational cost of returning a translation result to the requester.
The translation repository 366 preferably includes one or more translation results 366n corresponding to textual information depicted in and/or extracted from image data stored in the image data and/or metadata repository 346 and/or received in connection with a translation request. Preferably, the translation information derived from a particular image is stored in the translation repository 366 in association with a translation identifier, which more preferably is associated with a corresponding image identifier mapping the translation result in the translation repository to the image in the image data and/or metadata repository from which the translation information was derived.
In particularly advantageous embodiments, the translation repository 366 includes a plurality of translation results 366n for each image to which the translation results correspond. Each translation result associated with the particular image may represent a translation of the textual information in the particular image to a different destination language. In this manner, translation information in many different languages may be provided based on a single submission of an image with a translation request, thereby avoiding the need to receive and/or store multiple images of the same subject and/or textual information in the CIMTS platform 300.
Preferably, each translation result 366n is stored in the translation repository 366 in association with a unique translation identifier. The translation identifier may preferably uniquely identify the source language (i.e. language in which the text was extracted from the image), the destination language (i.e. language into which the extracted text was translated), and/or the translation model used to perform the translation. Optionally, the translation identifier may additionally and/or alternatively identify or correspond to an extracted text identifier associated with text extracted from the image, and/or an image identifier associated with the image from which the text were extracted.
In this manner, each identifier may be utilized to map the image, extracted text, and translation result to one another, which advantageously allows facile and efficient identification of the image and associated text/translation subsequently. As described further elsewhere herein, such techniques improve the computational efficiency and reduce the network usage/bandwidth required to accomplish accurate machine translation using a CIMTS platform 300.
In more embodiments, and in order to facilitate improved computational efficiency and/or network/data usage for purposes of achieving machine translation, generating and submitting the translation request may be performed as a multi-stage process. For example, metadata may be submitted and analyzed prior to image data in order to determine whether a less computationally expensive process may be utilized to accomplish accurate translation results. In such cases, method 400 may include submitting the metadata corresponding to the captured image data to the machine translation platform; receiving an indication from the machine translation platform that machine translation may not be accomplished using the submitted metadata; and submitting the image data to the machine translation platform in response to receiving the indication that the metadata are not suitable for generating an appropriate translation result or estimating a translation result.
Returning to
CIMTS platform 300 server side 304 includes a CIMTS daemon 324 configured to handle CIMTS inputs, e.g. received from the image submitter module 314 of client side 302 via the network, as well as output APIs for accomplishing translation of the CIMTS inputs. The CIMTS daemon 324 is preferably further configured to manage image replacement for translations in real-time. As such, CIMTS daemon 324 is preferably coupled to at least the network facilitating data transfer between the client side 302 and the server side 304.
As shown in the embodiment of
The CIMTS manager module 326 and CIMTS daemon 324 may optionally be configured to exchange communications with one another in a two-way path. For instance, the CIMTS daemon 324 may output APIs to the CIMTS manager module 326 and/or manage real time image replacement operations via communications sent to the CIMTS manager module 326, in various embodiments. Conversely, the CIMTS manager module 326 may configure APIs received from the CIMTS daemon 324.
Generally speaking, the CIMTS manager module 326 is preferably configured to manage the CIMTS services provided by the CIMTS platform 300, and particularly by server side 304 to the end user via the network and client side 302. This management includes tasks such as configuring APIs (as noted above), configuring user profiles, configuring CIMTS rules, and/or configuring CIMTS profiles, in various embodiments. As such, the CIMTS manager module 326 is optionally but preferably communicatively coupled to a CIMTS configuration module 328 which, in turn, is communicatively coupled to and configured to define, set, update, adjust, and modify CIMTS profiles 330, CIMTS rules 332, and/or user characteristic profiles 334 stored within the CIMTS platform 300. For instance, the CIMTS configuration module 328 may perform any one or more of the foregoing management operations in response to receiving instructions to define or change settings that impact the function of the CIMTS platform 300, and particularly machine translation tasks performed thereby.
The CIMTS configuration module 328 may also be communicatively coupled to the CIMTS manager module 326 to facilitate two-way information exchange. For instance the CIMTS configuration module 328 may report current settings regarding CIMTS profiles 330, CIMTS rules 332, and/or user characteristic profiles 334 to the CIMTS manager module 326 to facilitate comparison of translation results with CIMTS settings, determining whether and if so how to modify various settings, etc. as would be understood by a person having ordinary skill in the art upon reading the present disclosures.
As described herein, CIMTS profiles 330 may be understood as including one or more profile entries, optionally arranged in sets, which facilitate configuration and control of the CIMTS platform 300. For instance, CIMTS settings reflected in the CIMTS profiles 330 may control the destination language to which text represented in a source language is translated, may define priority or assign weights to different measures in determining which input(s) to use for machine translation of textual information captured by the user of the device hosing the clients side 302 etc. as would be understood by a skilled artisan upon reading the instant descriptions. As such, CIMTS profiles 330, in various embodiments may include any combination, permutation, etc. of characteristics, settings, information, etc. such as location information, location profiles (e.g. information describing landmarks, places of business, etc. nearby, such as useful for providing contextual information as described herein), image processing settings to utilize in connection with image inputs corresponding to particular locations, whether substitute inputs are enabled, etc.
CIMTS rules 332, in preferred approaches may be understood as including one or more parameters, algorithms, or other controlling function for enabling input replacement and/or configuring suitable input replacement (e.g. defining type(s) of input replacement which are permissible such as substituting image data for metadata, metadata for image data, metadata for metadata, image data for image data, whether any particular type of data is permissible for substitution purposes, etc.).
In further embodiments CIMTS rules 332 may additionally and/or alternatively include rules that dictate one or more criteria by which image and/or metadata similarity is evaluated and corresponding image data and/or metadata are identified for purposes of substitution in the CIMTS platform workflow. For instance, one or more thresholds defining requisite degree of similarity of image data and substitute image data, or metadata and substitute metadata, may be defined via the CIMTS rules 332.
Further still, CIMTS rules 332 may include guidelines for determining how particular translations (e.g. previously performed translations) correspond to particular image data, metadata (particularly location data, position data regarding the capture device 308, etc. as described herein and would be appreciated by a skilled artisan upon reading the instant disclosures), or combinations there, in various embodiments.
User characteristic profiles 334 generally include personal information specific to different users and which facilitate or define the manner in which machine translation is accomplished by the CIMTS platform 300. For instance, in different approaches user characteristic profiles 334 may include personal information such as native language, current place of domicile, languages spoken by the user, languages read by the user, level of fluency in one or more languages, a default or user-defined destination language to which source language text should be translated, capture device characteristics (such as native resolution, default color depth, gamma, etc.), network connection type (e.g. as may be indicative of network connection speed,), data usage preferences and/or limits, user preferences regarding enabling or disabling any features described herein (such as intelligent input selection and/or input replacement), etc. as would be understood by a person having ordinary skill in the art upon reading the instant disclosures.
Any one or combination of the CIMTS profiles 330, CIMTS rules 332, and CIMTS characteristic profiles 334 may optionally be communicatively coupled to an image classifier module 340 which will be described in further detail below. In preferred embodiments, at least the CIMTS rules 332 are communicatively coupled to the image classifier module 340, e.g. in order to define or modify rules that dictate criteria by which image similarity is evaluated and corresponding image data are identified for purposes of substitution in the CIMTS platform workflow. For instance, CIMTS rules 332 may define criteria for the image classifier module 340 to utilize in determining which class an image belongs to, whether images belong to the same class or depict an object (e.g. a building, sign, street, etc.) of the same classification, etc. as would be understood by a person having ordinary skill in the art upon reading the present descriptions. The image classifier module 340 will be described in further detail below regarding updating and/or building the image data and/or metadata repository 346.
Returning now to the processing of inputs received from the client side 302 via the network, and in particular inputs including image data, input receiver module 336 is, according to preferred embodiments, configured to respond to translation requests received from the client side 302 and receive camera input image data as well as any related metadata that may have been submitted with the request. For instance, and as suggested above the input receiver module 336 may receive CIMTS inputs via the CIMTS daemon 324, in one embodiment. In various approaches and as described further herein, in order to facilitate improvements to the function of the CIMTS platform 300, the input received by the camera input receiver may include metadata alone, image data alone, image data in association with metadata, or any suitable combination of input data as described herein and would be appreciated by a person having ordinary skill in the art upon reading the present disclosures.
The input receiver module 336, in various embodiments, is configured to receive input of any suitable type for purposes of performing machine translation using the CIMTS platform 300. In particular, the input receiver module 336 is preferably configured to receive input comprising metadata, image data, image data and metadata (optionally in association with one another), or any combination of suitable types of input as described herein. In particularly preferred approaches the input receiver module 336 may be configured to receive metadata descriptive of capture conditions, such as metadata generated by the metadata generator 310 and/or CIMTS condition evaluator 312 of client side 302.
Input receiver module 336 as shown in the embodiment of
The determination of whether image data are sufficient for machine translation may be performed subsequent to, or in tandem with, another determination as to whether any metadata received at the input receiver module 336 are sufficient to generate an estimated translation of textual information that may be represented in the image data transmitted and/or captured by the user of the device hosting the client side 302. If image data are insufficient for machine translation, but metadata are sufficient to estimate a translation (e.g. based on metadata sufficient to identify a similar image and/or translation result by location, orientation, position, etc.) then substitute inputs may be utilized for translation. Similarly, if metadata sufficient to accurately estimate a translation are present then it may be advantageous to utilize substitute inputs where inputs of a higher quality are available to the CIMTS platform 300, or even to forego image processing to extract text from the image data submitted to the CIMTS daemon 324 and/or input receiver module 336 such as where a previous translation of the same textual information is already available to the CIMTS platform 300 without processing the image.
Accordingly, image quality control module 338 preferably includes, or is coupled to logic 348 for determining whether image data are insufficient for machine translation and/or metadata are sufficient to estimate a translation, and based on a result of either or both of these determinations, determine how to proceed with machine translation. For example in one embodiment based on image quality and/or type of metadata received at the input receiver module 336, the logic 348 is preferably configured to determine whether or not to proceed with translation via extracting textual information from the image data (e.g. via OCR, intelligent character recognition (ICR), or other equivalent extraction technique).
If translation is to proceed by extracting textual information from the image data (e.g. in response to determining image data are of superior or sufficient quality for extraction, metadata are insufficient to estimate a translation), the logic 348 may direct the translation process to proceed via operation 350 which includes extraction and subsequent translation of extracted text using any number of translation models, e.g. translation models 356n of translation module 356. For the purposes of operation 350 alone, any suitable technique as would be known in the art for extracting textual information and translating such textual information may be employed without departing from the scope of the present disclosures.
In some embodiments, and according to operation 358 upon translating the extracted textual information to one or more destination languages using the translation models 356n the translation result may be stored in translation repository 366, and/or the image data, associated metadata, etc. used to generate the translation result may optionally be stored in image data and/or metadata repository 346 for subsequent utilization, e.g. as substitute inputs for a subsequent translation request.
Subsequent lookup may improve computational efficiency of the machine translation service, as well as to enable translation based on metadata, e.g. when the image quality is insufficient to support text extraction and translation using more conventional approaches. To facilitate such advantages, the translations may be each stored in association with a unique translation identifier which may identifier parameters of the translation process (e.g. source, destination language, translation model, etc.) and/or be utilized to map the translation result to the extracted text upon which the translation was produced and/or the image from which the text were extracted.
In various embodiments, source and destination languages of the translation models may respectively be selected based on user-defined preferences (e.g. native language), location data corresponding to the mobile device or the location where the image was captured, etc.
If translation is to proceed by techniques other than extracting textual information from the image data (e.g. in response to determining image data are of insufficient or inferior quality to accurately extract text therefrom, or metadata are sufficient to estimate a translation), the logic 348 may direct the translation process to proceed via operation 352 which includes attempting to directly locate a previously translated message corresponding to the message for which translation is presently sought.
For example, in various embodiments a previously translated message may be identified based on similar metadata as submitted with the translation request, particularly location, orientation, and perspective metadata. In such situations, operation 352 may leverage other modules described herein (and which may or may not be shown in
If operation 352 does not yield a corresponding and appropriate previously translated result, then the non-extraction based translation process may proceed via operation 354, in which the server side 304 attempts to locate image data similar to the input image data and/or metadata, such image data being optionally and preferably stored in an image and metadata repository 346 comprising a plurality of records 346n each comprising image data and/or associated metadata. Accordingly, operation 354 may involve performing one or more analyses to determine image and/or metadata similarity based on known image analysis techniques (such as may be employed by image classifier module 340 in some embodiments). Such analysis is preferably performed using normalized image data and/or metadata from the repository 346, such normalization being accomplished using image data normalizing module 344.
In various illustrative embodiments, server side 304 may therefore further include the image classifier module 340 mentioned above, which may be communicatively coupled to an image identifier managing module 342 and which is in turn communicatively coupled to an image data normalizing module 344. The image data normalizing module is communicatively coupled to the image data and/or metadata repository 346 to form a pathway from image classifier module 340 to image data and/or metadata repository 346.
In operation, and according to one embodiment image data and/or input metadata may be received at the image classifier module 340 from the input receiving module 336 either in the course of performing a translation request or in the course of building or updating the image data and/or metadata repository 346. The image data may be classified using said image classifier module 340 and based on analyzing the image data and/or metadata. Based on the result of the classification and/or the metadata (whether or not such metadata were leveraged in determining the image classification), the image data may be associated with a unique image identifier by image identifier managing module 342. The unique identifier facilitates subsequent use of the image data as a substitute input for subsequent translation requests, for ranking purposes, etc. as will be appreciated by skilled artisans upon reading the present disclosures. Image data (and optionally associated metadata) may then be normalized according to image data normalizing module 344.
Normalizing image data and/or metadata to be included in the repository conveys the advantage of enabling the best image(s) and descriptive information concerning a particular subject, location, etc. to be used in translation. This further improves the function of the CIMTS system by ensuring that a high-quality input may be utilized for translation, e.g. a daytime photo may be used for translation in response to a user submitting a translation request (including an image, likely of poor quality) at a time of day when ambient lighting is insufficient to produce an image of sufficient quality for translation.
Similarly in preferred approaches normalizing allows embodiments where a clear image may always be used despite a user submitting a translation request including an image taken during inclement weather, which renders the image of insufficient quality for translation.
Further still, and especially when considering images captured using a camera such as typically embodied in a mobile device, images taken under ideal ambient conditions may nonetheless include distortions, and/or may not capture all content desired/necessary for translation.
For instance, and as is known in the art, perspective distortions are particularly challenging in the context of recognizing, extracting, and manipulating textual information represented in image data. Indeed, this is one reason that automated techniques for distinguishing human from machine actors (e.g. CAPTCHA®) utilize distorted images as the test prompt.
Image normalization may address the challenges associated with distortions and/or incomplete representations of text in image data submitted to the CIMTS solution. For instance, where textual information is cut-off, or sufficiently distorted that machine translation is not achievable, an image taken from a different angle so as to reduce/remove the distortive effects, and/or include missing text, may be substituted and thus the translation may be achieved without requiring the user to capture and submit a second image, As such, normalization represents a further improvement to the CIMTS system, especially in circumstances where recapture/resubmission may not be possible.
In some approaches, normalization may include generating a composite image from multiple images included in the repository.
In other approaches, normalization may include determining from among a plurality of images corresponding to a same location, subject, set or subset textual information, etc., which of the plurality of images are most suitable for machine translation, and ensuring those most suitable images are utilized for subsequent translation requests. For instance a ranking may be applied to various images in the repository, and substituting images from the repository for camera input provided by the user with the translation request may be performed according to the ranking, e.g. selecting the top ranked image, or from among the top ten ranked images, etc. as would be understood by a person having ordinary skill in the art upon reading the present disclosures.
The ranking may be determined automatically by the CIMTS platform 300, e.g. based on analyzing the image and/or metadata associated with the image, according to one implementation. Accordingly, metadata may preferably include one or more indicia of image quality and/or capture parameters relevant to translation, such as image capture time, location, position, orientation, azimuth, environmental conditions such as weather, lighting, etc. associated with image capture, translation results achieved using particular images, and other parameters or indicia as would be appreciated by a skilled artisan reviewing these disclosures.
In more approaches, independent of the automated ranking or in addition to automated ranking techniques, user input or feedback regarding particular images and/or translation results achieved using particular images may be utilized to rank images in the CIMTS repository.
User feedback or input, for example, may include a simple confirmation, modification, or negation of a translation result provided to the user in response to the user submitting a translation request to the CIMTS platform. Images may then be ranked, or ranking thereof influenced, based on accumulating user input/feedback over time in order to further improve the performance of the CIMTS platform. Modifications, in various approaches, may include user-provided translation suggestions, a user's selection from among a plurality of possible translations, etc.
Additionally and/or alternatively, in response to a translation attempt failing, and/or in response to user feedback indicating negation or modification of a translation result produced by the CIMTS platform, one or more candidate images from the image data and/or metadata repository may be presented to the user and the user may be instructed to select a substitute image from among the candidate images for purposes of performing machine translation. Based on the user's selection, and optionally further based on results and/or feedback regarding results of attempting translation with the substitute image, ranking of the selected substitute image may be determined and/or modified over time.
Of course, in more embodiments normalization may include both generating composite images, as well as determining suitability of images for machine translations and selectively substituting repository images for user-provided input, without departing from the scope of the presently disclosed inventive concepts.
Accordingly, and returning to operation 354, the non-extraction based translation process preferably identifies a similar image and/or metadata, and based on such similar image and/or metadata identifies a corresponding translated message 366n in translation repository 366. In order to identify the corresponding translated message 366n from among the plurality of translated messages, the image identifier of the image determined in operation 354 to be similar to the input image data and/or metadata may be mapped in operation 362 to a corresponding translated message identifier associated with the translated message 366n.
Based on the mapping, and according to one embodiment in operation 364 the corresponding translated message 366n may be located within the translation repository. Translation information may be returned to the client side 302 via the network using return translated message module 360, according to one embodiment. The returned translation information may include translated message 366n, and/or may be an estimated translation, in some approaches, while the translation information may comprise contextual information, in other approaches. For instance, where no similar image could be located in operation 354 the translation information provided to the client side 302 may include default contextual information about the location where the input image data were captured, in various embodiments.
Context is preferably determined based on predefined rules, e.g. report information relating to the location where the client device was present when the communication was sent, or where the image was taken (this location may be less precise than the position, azimuth, and orientation metadata utilized to identify similar images, but sufficiently precise to identify, e.g. the street name or city in which the device is located/image was captured). As such, default and/or contextual information may include or be determined based at least in part on: default transliteration rules which identify a transliterated street name, building name, city name, etc.; default location rules which provide translated high level info such as city history, neighborhood info, list of nearby restaurants, retail stores, landmarks, tourist attractions, etc. based on location; and/or default advertising rules which facilitate presenting promotional offers (optionally based further on default location and/or default transliteration rules) in response to the translation request.
Of course, the above modules, operations, and/or logic may be implemented as a method on any device and/or system or as a computer program product, according to various embodiments.
Now referring to
Each of the steps of the method 500 may be performed by any suitable component of the operating environment. For example, in various embodiments, the method 500 may be partially or entirely performed using a CIMTS platform 300, and particularly a server side 304 of a CIMTS platform 300 such as depicted in
As shown in the embodiment depicted in
Method 500 further includes generating or retrieving translation information based on a result of a first determination, a second determination, or both in operation 504. The first determination includes determining whether the translation request includes image data suitable for generating a machine translation; and the second determination includes determining whether the translation request includes metadata suitable for generating an estimated translation. The determinations may be performed in any order, and any combination or permutation, without departing from the scope of the presently disclosed inventive concepts as embodied in method 500 of
Of course, method 500 may include any suitable combination or permutation of additional or alternative operations, features, conditions, etc. as described herein without departing from the scope of the present disclosure. In various embodiments, method 500 may be characterized by including or featuring one or more of the following characteristics.
In one embodiment, the translation information generated or retrieved in operation 504 includes information selected from a machine translation, an estimated translation, and contextual information. The machine translation may be understood to include a translation result generated based on the captured image data, and optionally metadata/condition data associated with the captured image data, while estimated translations may be understood to include translation results retrieved based on similarity of the captured image data to previously captured image data (optionally stored in image data and/or metadata repository 346 and similarity of which may optionally be determined based on comparing image data, metadata, or both). Contextual information may include any suitable type of default or contextual information as described herein and equivalents thereof that would be appreciated by a person having ordinary skill in the art upon reading the instant disclosures.
Accordingly, retrieving contextual information may be performed in one embodiment in response to determining both: the translation request does not include image data suitable for generating a machine translation; and the translation request does not include image metadata suitable for generating an estimated translation.
In more embodiments, method 500 may optionally include, in response to determining the translation request includes image data suitable for machine translation, generating the translation information. Generating the translation information involves extracting textual information from the image data; translating some or all of the extracted textual information using at least one of a plurality of translation models; and for each of the plurality of translation models used to translate the extracted textual information, storing a corresponding translated message in a translation repository.
In some approaches, image data may be sufficient to perform machine translation, but nonetheless it may be advantageous to accomplish machine translation without processing the image data, e.g. where similar image data have previously been processed and accurate translation results generated thereby. In such embodiments, computational efficiency of translation may be improved by locating the previously generated translation result instead of repeating image processing. Accordingly, method 500 may include, in response to determining the translation request includes image data suitable for machine translation, generating the translation information. Generating the translation information in such embodiments includes: determining whether an image corresponding to the image data included in the translation request exists in an image data and/or metadata repository; in response to determining the image corresponding to the image data included in the translation request exists in the image data and/or metadata repository, determining a corresponding image identifier; identifying a previously translated message based on the corresponding image identifier; and retrieving the translation information from the previously translated message.
In further embodiments, method 500 may include generating the estimated translation without performing machine translation based on captured image data. For instance, such an approach may be advantageous in response to determining both: the translation request does not include image data suitable for machine translation; and the translation request does include image metadata suitable for generating the estimated translation. Thus, in this embodiment metadata (which may optionally include condition data generated by CIMTS condition evaluator 312 and/or metadata generator 310) may serve as a replacement input for machine translation purposes.
Optionally, generating the estimated translation may include: determining whether an image corresponding to the image data included in the translation request exists in an image data and/or metadata repository based at least in part on the image metadata; in response to determining the corresponding image exists in the image data and/or metadata repository, determining a corresponding image identifier; identifying a previously translated message associated with the corresponding image based on the corresponding image identifier; and generating the estimated translation information based on the previously translated message.
Generating the estimated translation information based on the previously translated message, in various embodiments, may include parsing some of the previous translation, converting the previous translation to a different destination language, etc. Generating estimated translations may alternatively include simply retrieving the previous translation as a whole and reporting back to the client.
Determining whether images correspond as suggested herein may be based on image classification indicating the corresponding image data in the repository depicts part or all of the same or substantially the same scene, e.g. building, street sign, place of business, public transportation station, etc. as the captured image. Alternatively, determining correspondence between images may be based on matching metadata and/or condition data associated with capture, preferably position/orientation/azimuth information.
In still more embodiments, e.g. where captured image data are of insufficient quality for machine translation, alternative input image data may be identified and processed. Accordingly, method 500 may optionally include, in response to determining the translation request does not include image data suitable for machine translation: determining whether an image corresponding to the image data included in the translation request exists in an image data and/or metadata repository; in response to determining the corresponding image exists in the image data and/or metadata repository, extracting textual information from the corresponding image; translating some or all of the extracted textual information using at least one of a plurality of translation models; and for each of the plurality of translation models used to translate some or all of the extracted textual information, storing a corresponding translated message in a translation repository.
The method 500 may also or alternatively include establishing and/or updating an image data and/or metadata repository; an extracted text repository; a translation repository; or any combination thereof. As noted above establishing the repositories facilitates providing intelligent input selection and/or input replacement and improves the function of machine translation systems in accordance with the present inventive concepts.
In one approach, establishing and/or updating the image data and/or metadata repository may be based at least in part on identifying superior or substitute image data inputs, and may include: receiving one or more images; receiving and/or generating metadata descriptive of each of the one or more of images (e.g. using or based on analyses performed using the image quality control module 338 and/or image classifier module 340), and associating the received and/or generated metadata with the image of which the metadata are descriptive.
The image data and/or metadata repository 346 establishment/update process may further include classifying at least some of the images, where the classifying is optionally based at least in part on the metadata associated with the respective image. In one approach, classifying may be based on metadata associated with the received image, e.g. metadata descriptive of image characteristics such as resolution, color depth, illumination, aspect ratio, etc. This classification may be further influenced based on settings defined in the CIMTS profiles 330, CIMTS rules 332, and/or user characteristic profiles 334, in several embodiments.
Further still, embodiments of establishing and/or updating the image data and/or metadata repository 346 may include associating a different image identifier with each classified image; and storing each classified image and the associated image identifier in the image data and/or metadata repository 346. Optionally, and preferably prior to storing the image data, associated metadata and/or unique image identifier in the image data and/or metadata repository 346, method 500 in one embodiment includes normalizing at least some of the classified images. Normalization conveys advantages explained in greater detail elsewhere herein, according to various embodiments.
Turning now to the translation repository 366, in various embodiments establishing and/or updating the translation repository may include: receiving one or more images; extracting textual information depicted in each of the one or more images; translating the textual information extracted from each respective one of the one or more images according to one or more of a plurality of translation models (e.g. translation models 356n as shown in
Establishing and/or updating the translation repository 366 may additionally and/or alternatively include: associating a different message identifier with the textual information extracted from each respective one of the one or more images; and storing the textual information extracted from each respective one of the one or more images in association with the respective different message identifier in an extracted text repository. Establishing an extracted text repository in this manner may facilitate mapping images and/or translation results to each other, as well as performing additional translations of extracted text without needing to repeat the extraction process, in various embodiments.
In one particularly preferred embodiment, method 500 may proceed according to the following series of operations. In a first operation, input(s) received from the client side (e.g. client side 302) are evaluated to determine whether the input(s) include image data suitable for generating a machine translation, e.g. image data that have sufficient resolution, clarity, illumination characteristics, etc. for extracting textual information therefrom.
If the result of the first operation is a determination that image data suitable for machine translation are included in the input(s), then the method 500 may proceed via conventional CIMTS-based machine translation, including extracting textual information from image data and translating extracted textual information using any suitable known technique(s) that would be appreciated by a person having ordinary skill in the art upon reading the present disclosures. Such conventional techniques may include character recognition such as OCR and/or ICR, NLP, machine translation, etc. and may be performed in any suitable manner such as described above with regard to
With continuing reference to the particularly preferred embodiment of method 500, if the first operation results in a determination that the input(s) do not include image data suitable for machine translation, then a second operation is performed, and includes determining whether the input(s) include metadata suitable for generating an estimated translation, e.g. by identifying substitute input image data, corresponding previously performed translations, etc. as described herein and would be understood by a skilled artisan upon reading the instant descriptions.
Such metadata are ideally descriptive of the position or location where the input(s) were obtained (e.g. GPS coordinates where image data were captured); the orientation of the capture device when inputs were obtained (e.g. vertical, horizontal, and/or rotational angle between the capture device and the subject of the image data at time of capture, direction faced/viewed by capture device during capture; and/or the azimuth of the image data and/or subject thereof with respect to the capture device at time of capture.
According to such preferred embodiments, generating the estimated translation includes identifying and returning previous translation results corresponding to a similar location, orientation, and/or azimuth. For example, based on the metadata descriptive of the input(s), similar images in an image data and/or metadata repository 346 may be identified, and corresponding translations of textual extraction depicted therein identified by mapping image identifier(s) to translated message identifier(s), e.g. as described above regarding
With still further reference to the particularly preferred embodiment of method 500, if the first operation and second operation each result in determining that the input(s) do not include image data or metadata suitable for machine translation, then default or contextual information may be provided to the client side 302. Default or contextual information may take any form as described herein, and generally includes information selected based on context of the original translation request and/or associated input(s), such as user preferences, location information, orientation information, etc.
Meanwhile, and still according to the particularly preferred embodiment of method 500, the CIMTS platform 300 is configured to build and iteratively update repositories including but not limited to an image data and/or metadata repository 346 and a translation repository 366. Building the repositories is performed at initialization of the CIMTS platform, while iterative updates may be performed according to needs of the platform, user-defined settings, or other suitable criteria.
Essentially, building and updating the repositories include collecting image data and associated metadata from various sources such as online repositories and data received from clients of the CIMTS platform 300; examining collected and received image data and associated metadata; classifying qualified images based on the image data and/or related metadata and saving classified images to the image data and/or metadata repository 346; indexing each classified image; extracting textual information from the classified, indexed images; indexing each set of extracted textual information and storing indexed textual information to an extracted text repository; translating each set of extracted textual information; indexing each translation result achieved based on each respective set of extracted textual information; and saving each indexed translation result in a translation repository 366.
The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
Moreover, a system according to various embodiments may include a processor and logic integrated with and/or executable by the processor, the logic being configured to perform one or more of the process steps recited herein. By integrated with, what is meant is that the processor has logic embedded therewith as hardware logic, such as an application specific integrated circuit (ASIC), a FPGA, etc. By executable by the processor, what is meant is that the logic is hardware logic; software logic such as firmware, part of an operating system, part of an application program; etc., or some combination of hardware and software logic that is accessible by the processor and configured to cause the processor to perform some functionality upon execution by the processor. Software logic may be stored on local and/or remote memory of any memory type, as known in the art. Any processor known in the art may be used, such as a software processor module and/or a hardware processor such as an ASIC, a FPGA, a central processing unit (CPU), an integrated circuit (IC), a graphics processing unit (GPU), etc.
It will be clear that the various features of the foregoing systems and/or methodologies may be combined in any way, creating a plurality of combinations from the descriptions presented above.
It will be further appreciated that embodiments of the present invention may be provided in the form of a service deployed on behalf of a customer to offer service on demand.
While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
| Number | Name | Date | Kind |
|---|---|---|---|
| 6047251 | Pon et al. | Apr 2000 | A |
| 6584221 | Moghaddam et al. | Jun 2003 | B1 |
| 6763148 | Sternberg et al. | Jul 2004 | B1 |
| 6834274 | Tafoya | Dec 2004 | B2 |
| 7359562 | Raskar et al. | Apr 2008 | B2 |
| 7474759 | Sternberg et al. | Jan 2009 | B2 |
| 7499588 | Jacobs et al. | Mar 2009 | B2 |
| 7590310 | Retterath et al. | Sep 2009 | B2 |
| 7751805 | Neven et al. | Jul 2010 | B2 |
| 7756291 | Lennington et al. | Jul 2010 | B2 |
| 7912289 | Kansal et al. | Mar 2011 | B2 |
| 7933454 | Bressan et al. | Apr 2011 | B2 |
| 8009921 | Csurka | Aug 2011 | B2 |
| 8019118 | Sternberg et al. | Sep 2011 | B2 |
| 8150910 | Tatsubori | Apr 2012 | B2 |
| 8300764 | Yamaguchi | Oct 2012 | B2 |
| 8520099 | Hayashi | Aug 2013 | B2 |
| 8601147 | Craft et al. | Dec 2013 | B2 |
| 8725490 | Athsani et al. | May 2014 | B2 |
| 8761513 | Rogowski | Jun 2014 | B1 |
| 8942437 | Schneider et al. | Jan 2015 | B2 |
| 8949170 | Ladeh | Feb 2015 | B2 |
| 9082035 | Hwang et al. | Jul 2015 | B2 |
| 9141184 | Uchikoshi et al. | Sep 2015 | B2 |
| 9171261 | Ladeh | Oct 2015 | B1 |
| 9177225 | Cordova-Diba et al. | Nov 2015 | B1 |
| 9342533 | Copsey | May 2016 | B2 |
| 9563690 | Copsey | Feb 2017 | B2 |
| 9639921 | Cho et al. | May 2017 | B2 |
| 9697348 | Maresh et al. | Jul 2017 | B1 |
| 9773197 | Englund | Sep 2017 | B2 |
| 10311330 | Anglin et al. | Jun 2019 | B2 |
| 20010032070 | Teicher | Oct 2001 | A1 |
| 20020156832 | Duri et al. | Oct 2002 | A1 |
| 20030093412 | Urkumyan | May 2003 | A1 |
| 20030123737 | Mojsilovic et al. | Jul 2003 | A1 |
| 20030130974 | Tafoya | Jul 2003 | A1 |
| 20030164819 | Waibel | Sep 2003 | A1 |
| 20040133927 | Sternberg et al. | Jul 2004 | A1 |
| 20040150726 | Gallagher | Aug 2004 | A1 |
| 20060041590 | King | Feb 2006 | A1 |
| 20070098288 | Raskar et al. | May 2007 | A1 |
| 20080199060 | Boyden et al. | Aug 2008 | A1 |
| 20080221862 | Guo et al. | Sep 2008 | A1 |
| 20080233980 | Englund | Sep 2008 | A1 |
| 20090048820 | Buccella | Feb 2009 | A1 |
| 20090106016 | Athsani | Apr 2009 | A1 |
| 20090164213 | Lennington et al. | Jun 2009 | A1 |
| 20090196510 | Gokturk et al. | Aug 2009 | A1 |
| 20100008582 | Kim et al. | Jan 2010 | A1 |
| 20100011105 | Tatsubori | Jan 2010 | A1 |
| 20100067773 | Yamaguchi | Mar 2010 | A1 |
| 20100077003 | Kondo et al. | Mar 2010 | A1 |
| 20100228751 | Oh et al. | Sep 2010 | A1 |
| 20100278439 | Lennington et al. | Nov 2010 | A1 |
| 20110279664 | Schneider et al. | Nov 2011 | A1 |
| 20110279712 | Hayashi | Nov 2011 | A1 |
| 20120095982 | Lennington et al. | Apr 2012 | A1 |
| 20120130704 | Lee et al. | May 2012 | A1 |
| 20120163668 | Englund et al. | Jun 2012 | A1 |
| 20120268621 | Kanma et al. | Oct 2012 | A1 |
| 20130108115 | Hwang et al. | May 2013 | A1 |
| 20130110565 | Means, Jr. | May 2013 | A1 |
| 20130113943 | Wormald | May 2013 | A1 |
| 20130114849 | Pengelly et al. | May 2013 | A1 |
| 20130230214 | Arth et al. | Sep 2013 | A1 |
| 20140067679 | O'Reilly et al. | Mar 2014 | A1 |
| 20140081619 | Solntseva | Mar 2014 | A1 |
| 20140160250 | Pomerantz et al. | Jun 2014 | A1 |
| 20140280091 | Nasarov | Sep 2014 | A1 |
| 20140297256 | Rogowski | Oct 2014 | A1 |
| 20140344948 | Hayato et al. | Nov 2014 | A1 |
| 20150049948 | Bala | Feb 2015 | A1 |
| 20150093033 | Kwon et al. | Apr 2015 | A1 |
| 20150134318 | Cuthbert | May 2015 | A1 |
| 20150268913 | Adachi et al. | Sep 2015 | A1 |
| 20150286888 | Maison | Oct 2015 | A1 |
| 20150310291 | Cuthbert | Oct 2015 | A1 |
| 20150370785 | Mauser et al. | Dec 2015 | A1 |
| 20160004692 | Rogowski | Jan 2016 | A1 |
| 20160165193 | Rasheed et al. | Jun 2016 | A1 |
| 20160189000 | Dube et al. | Jun 2016 | A1 |
| 20160292887 | Cho et al. | Oct 2016 | A1 |
| 20160350286 | Murthy | Dec 2016 | A1 |
| 20160357732 | Hsu | Dec 2016 | A1 |
| 20160371256 | Mauser et al. | Dec 2016 | A1 |
| 20170046427 | Tang et al. | Feb 2017 | A1 |
| 20180053068 | Anglin et al. | Feb 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 105389375 | Mar 2016 | CN |
| 2144189 | Jan 2010 | EP |
| 2410465 | Jan 2012 | EP |
| 5267451 | Aug 2013 | JP |
| 2009115855 | Sep 2009 | WO |
| 2011080946 | Jul 2011 | WO |
| Entry |
|---|
| Chang et al., “Enhancing Image-Based Arabic Document Translation Using a Noisy Channel Correction Model,” Proceedings of MT Summit XI, 2007, pp. 1-7. |
| Anglin et al., U.S. Appl. No. 15/239,716, filed Aug. 17, 2016. |
| Non-Final Office Action from U.S. Appl. No. 15/239,716, dated Nov. 6, 2017. |
| International Search Report and Written Opinion from PCT Application No. PCT/IB2017/053734, dated Sep. 27, 2017. |
| Non-Final Office Action from U.S. Appl. No. 15/239,716, dated May 9, 2018. |
| Final Office Action from U.S. Appl. No. 15/239,716, dated Oct. 22, 2018. |
| Notice of Allowance from U.S. Appl. No. 15/239,716, dated Jan. 22, 2019. |
| Number | Date | Country | |
|---|---|---|---|
| 20180052832 A1 | Feb 2018 | US |
