Source: https://patents.justia.com/patent/10146803
Timestamp: 2019-08-24 08:47:10
Document Index: 786449599

Matched Legal Cases: ['Application No. 61', 'Application No. 14788928', 'Application No. 14847922', 'Application No. 2015', 'Application No. 2016', 'Application No. 15764687', 'Application No. 14775259', 'Application No. 201480014229', 'Application No. 13738301', 'Application No. 2016', 'Application No. 2016', 'Application No. 2016', 'Application No. 2016', 'Application No. 201580014141', 'Application No. 14773721', 'Application No. 103114611']

US Patent for Smart mobile application development platform Patent (Patent # 10,146,803 issued December 4, 2018) - Justia Patents Search
Justia Patents Data Structure TypesUS Patent for Smart mobile application development platform Patent (Patent # 10,146,803)
Aug 18, 2015 - KOFAX, INC
A method includes receiving user input defining a workflow comprising one or more activities and one or more rules; receiving user input defining a user interface (UI) configured to facilitate a user performing the workflow at least in part using a processor of a mobile device; and generating a mobile software application based on the workflow and the UI. In another embodiment, a method includes: instantiating a mobile application on a mobile device; launching a workflow within the mobile application, the workflow comprising one or more activities and one or more rules; rendering one or more user interfaces based at least in part on the workflow; displaying at least one of the user interfaces on a display of the mobile device; receiving user input via at least one of the user interfaces; and modifying the workflow based at least partially on user input. Systems and computer program products are also disclosed.
Latest KOFAX, INC Patents:
This application is a continuation of U.S. patent application Ser. No. 14/259,866, filed Apr. 23, 2014, which claims priority to Provisional U.S. Provisional Patent Application No. 61/815,210, filed Apr. 23, 2013 to each of which priority is claimed and each of which is herein incorporated by reference.
This application is related to U.S. Pat. No. 6,370,277, granted Apr. 9, 2002 (U.S. patent application Ser. No. 09/206,753, filed Dec. 7, 1998) as well as copending U.S. patent application Ser. No. 13/740,123, filed Jan. 11, 2013; Ser. No. 13/802,226, filed Mar. 13, 2013; Ser. No. 14/209,825, filed Mar. 13, 2014; Ser. No. 14/177,136, filed Feb. 10, 2014; Ser. No. 14/175,999, filed Feb. 7, 2014; Ser. No. 14/220,016, filed Mar. 19, 2014; Ser. No. 14/220,023, filed Mar. 19, 2014 and Ser. No. 14/220,029, filed Mar. 19, 2014; and Provisional U.S. Patent Application Nos. 61/819,463 filed May 3, 2013; 61/883,865, filed Sep. 27, 2013, and 61/905,063, filed Nov. 15, 2013, each of which are herein incorporated by reference.
The present invention relates to software development, and more particularly to software development platforms for generating and/or modifying applications for use on a mobile device.
Mobile technology is rapidly developing, fueling even more rapid development of software capable of exploiting the new and expanded functionality offered by mobile devices. As a result, entire new development communities have arisen to contribute to the expanding pool of software tools available to mobile device users. Large producers of mobile hardware and software have even released software development platforms to the general public and/or provided access to application distribution services to select developers, e.g. via a registration process. To users' great benefit, a wide array of mobile applications designed to perform myriad activities using mobile devices are now readily available for quick download, installation and implementation via mobile communication networks.
The currently available mobile software applications and development platforms provide diverse and powerful functionality to both end-users and developers capable of leveraging the various capabilities of existing mobile devices. However, there is currently no tool available for dynamically developing and employing smart mobile applications capable of adapting to user behavior and/or requirements. For example, current mobile development platforms and/or mobile applications are incapable of transparently determining an appropriate format for processing and outputting data such that the processed data may be seamlessly passed to and/or processed by a subsequent application or algorithm based on prior user activity; such as a user formatting the output and passing the output to the subsequent application or processing algorithm.
Since users cannot dynamically develop and/or process data using currently-available mobile software tools, in order to implement a new or modified process or application, new development effort is required. At best, either new functionality must be encoded into an existing application, or entire new applications must be developed to provide the desired capabilities. At worst, the desired “new” functionality cannot be implemented due to compatibility issues, process limitations, etc. The ultimate result is that end users must wait for development and deployment of the new or modified process(es) or application(s), which is undesirable and even may be unacceptable in some situations.
Moreover, while some users may be capable of developing and/or modifying existing software to perform desired functions, the majority of users do not possess the time or technical expertise to customize software products in this manner. Therefore, valuable input from non-developer users cannot be incorporated into current mobile applications and/or software development platforms without communication between the user(s) and developers, which is inconvenient in some situations and impossible in others. Ultimately, these constraints exclude many individuals from the development community, frustrating or precluding communication between the development community and end users, as well as unnecessarily restricting the available development resources to individuals having significant technical expertise and/or development experience.
Therefore, it would be beneficial to provide systems, methods, and computer program products encompassing a platform for development and use of smart mobile software applications to enable real-time data processing and dynamic application development. It would be a further benefit to enable developers and non-developer users alike to transparently create and/or adapt mobile applications that process data and/or facilitate subsequent processing of the data according to learned criteria such as user behavior and/or requirements. The application is also beneficially capable of dynamically adapting workflow processes in response to various stimuli, enabling a user-oriented experience that provides user-specific benefits tailored to the user's desired activities.
In one approach, a computer implemented method includes: receiving user input defining a workflow comprising one or more activities and one or more rules; receiving user input defining a user interface (UI) configured to facilitate a user performing the workflow at least in part using a processor of a mobile device; and generating a mobile software application based on the workflow and the UI. The workflow is configured to process digital image data based at least in part on the activities and the rules.
In another embodiment, a computer implemented method includes: instantiating a mobile application on a mobile device; launching a workflow within the mobile application, the workflow comprising one or more activities and one or more rules; rendering one or more user interfaces based at least in part on the workflow; displaying at least one of the user interfaces on a display of the mobile device; receiving user input via at least one of the user interfaces; and modifying the workflow based at least in part on the user input. In addition, the workflow is configured to process digital image data.
In yet another embodiment, a computer program product includes a computer-readable medium having stored thereon computer readable program code. The computer readable program code is executable by a processor to cause the processor to: receive user input defining a workflow comprising one or more activities and one or more rules; receive user input defining a user interface (UI) configured to facilitate a user performing the workflow at least in part using a processor of mobile device; and generate a mobile software application based on the workflow and the UI. The workflow is also configured to process digital image data based at least in part on the activities and the rules.
Other aspects and features of the presently disclosed inventive concepts will become apparent from the following detailed descriptions, which should be understood to be illustrative in nature and not limiting on the instant disclosure.
The present application refers to image processing. In one high-level implementation, the present disclosures extend mobile capture capabilities to mobile devices via a native mobile application. The mobile user takes a photo of a document using a capture application, which may or may not be part of a larger mobile application, either of which may be built and/or modified at least in part on a mobile capture software development kit (SDK). The capture application exposes an image capture interface which enables the taking of a photograph of an object, preferably under user control, which is then processed with image perfection technology, such as disclosed in related U.S. patent application Ser. No. 13/740,123. The capture application then optionally allows a transfer of the image off device, preferably again under user control. The capture application user experience is embedded in the mobile capture application.
A new paradigm extends processing to mobile devices and simultaneously exposes native mobile operating system services as well as other device native services. A mobile development platform, according to one embodiment, allows the user to define the mobile user experience including the user interface (UI), the sequence of screens presented, how users interact with those screens, and the orchestration of both native device services and server services. The created user experience can be selectively applied to any known device.
In one general embodiment, a method includes receiving user input defining a workflow comprising one or more activities and one or more rules; receiving user input defining a user interface (UI) configured to facilitate a user performing the workflow at least in part using a processor of a mobile device; and generating a mobile software application based on the workflow and the UI, wherein the workflow is configured to process digital image data based at least in part on the activities and the rules.
In another general embodiment, a method includes instantiating a mobile application on a mobile device; launching a workflow within the mobile application, the workflow comprising one or more activities and one or more rules; rendering one or more user interfaces based at least in part on the workflow; displaying at least one of the user interfaces on a display of the mobile device; receiving user input via at least one of the user interfaces; and modifying the workflow based at least in part on the user input, wherein the workflow is configured to process digital image data.
In yet another general embodiment, a system includes a processor; and logic in and/or executable by the processor to cause the processor to: receive user input defining a workflow comprising one or more activities and one or more rules; receive user input defining a user interface (UI) configured to facilitate a user performing the workflow at least in part using a processor of mobile device; and generate a mobile software application based on the workflow and the UI, wherein the workflow is configured to process digital image data based at least in part on the activities and the rules.
In still yet another general embodiment, a computer program product includes a computer-readable medium having stored thereon computer readable program code executable by a processor to cause the processor to: receive user input defining a workflow comprising one or more activities and one or more rules; receive user input defining a user interface (UI) configured to facilitate a user performing the workflow at least in part using a processor of mobile device; and generate a mobile software application based on the workflow and the UI, wherein the workflow is configured to process digital image data based at least in part on the activities and the rules.
A user experience for mobile smart application development, in one approach, may be loosely based on the following scenario:
A user defines a process as a set of activities and rules. The process executes by moving from one activity to another in a fixed order or a by a dynamic order as determined by stimuli. Rules are applied at fixed points within the sequence or in response to stimuli. The user also designs UIs independently, with assistance from the development platform, or UIs are rendered automatically by development platform tools to associate with activities that require human interaction.
The process, rules and UI definitions define a mobile user experience by providing both the mobile UI the user sees and interacts with and also the application behavior. The process definition can describe the application behavior because the mobile development platform exposes a federated view of native mobile services and server services. The process executes and transparently orchestrates the execution of native code directly on the device and remote code that resides on a server.
In one embodiment, a user launches a mobile application. The application initiates the process, takes the first activity and renders the defined UI. The user interacts with the UI and completes the activity or provides stimuli, such as “clicking” a UI button. At this point a rule may be executed or the next activity may be taken/performed. In either case local native services may be accessed, such as the device location being retrieved from the OS or a server service, such as a database lookup, may be used. This provision of native and/or remote services is transparent to the user.
This capability would allow the user to create a dynamic, adaptive mobile user experience that leverages both the local device capabilities and remote server services.
The application may be installed on the mobile device, e.g., stored in a nonvolatile memory of the device. In one approach, the application includes instructions to perform processing of an image on the mobile device. In another approach, the application includes instructions to send the image to a remote server such as a network server. In yet another approach, the application may include instructions to decide whether to perform some or all processing on the mobile device and/or send the image to the remote site to perform some or all of the processing operations.
In other approaches, the application may be downloaded in whole or in part and/or run in real-time on the mobile device. For example, the application may be maintained in an online repository. An instance of the mobile application may be transferred to the mobile device automatically, in response to a user request, in response to a new release of the mobile application becoming available in the online repository, etc. In a preferred embodiment, transferring new instances of the mobile application to mobile devices and instantiating those new instances is a process that occurs transparently to the user and without requiring any interaction or instruction from end-users operating the mobile application on mobile devices.
In still more approaches, the presently disclosed systems, methods and/or computer program products may be advantageously applied to one or more of the use methodologies and/or scenarios disclosed in the aforementioned related Patent Applications, among others that would be appreciated by one having ordinary skill in the art upon reading these descriptions.
The presently disclosed inventive concepts may be embodied as systems, methods, and computer program products for developing and/or using mobile applications, e.g. via a mobile application development platform as discussed below with reference to FIG. 3.
In one particular embodiment, such a method 300 is shown in FIG. 3. The method 300 may be performed in any environment, including those depicted in FIGS. 1-2, among others. Moreover, method 300 may include any alternative permutation and/or additional combination of features and/or operations as discussed herein, in various approaches.
In operation 302, user input defining a workflow is received. Preferably, the workflow comprises one or more activities and one or more rules.
In operation 304, user input defining a user interface (UI) configured to facilitate a user performing the workflow at least in part using a processor of mobile device is received.
As understood herein, the user input received in each of operations 302 and/or 304 (as well as any other user input, feedback, data, etc. “received” according to the present descriptions) may be received from any suitable source, location, etc. and in any suitable manner. For example, user input may be received via a hardware component of a mobile device, such as a display configured to receive and/or process tactile feedback. User input may additionally and/or alternatively be tactile feedback in the form of detecting a user interacting with one or more buttons, switches, toggles, etc. of the mobile device or another device in communication with the mobile device. User input may be received via a remote device in communication with the mobile device, such as another mobile device, a workstation, a server, a network component, etc.
In operation 306, a mobile software application is generated based on the workflow and the UI. Notably, the workflow may be configured to process digital image data based at least in part on the activities and the rules.
In some approaches, the activities may include one or more of interactive activities, which may include any activity that requires, receives, or depends upon input from a user, such as displaying data for user review and/or response, requesting data from a user (such as a file name, metadata, processing parameters, etc.), designating process inputs and/or outputs, capturing an image or video, etc. as would be understood by one having ordinary skill in the art upon reading the present descriptions. and non-interactive activities, which include any activity that does not require user input, such as a pre-set image processing analysis pipeline, file format conversion, automated dataset validation, etc. as would be understood by one having ordinary skill in the art upon reading the present descriptions.
In more approaches, the one or more rules facilitate performing one or more of the activities according to a processing scheme. In general, rules dictate the flow of the process from one activity to another in response to stimuli.
The flow of the processing scheme may be static in some embodiments, i.e. a predefined set of operations performed in a predefined order according to a predefined set of criteria and/or parameters.
In additional embodiments, the flow of the processing scheme may be dynamic, i.e. defined, configured, adjusted and/or performed in real-time or near-real time by a user based at least in part on input received from the user. The processing scheme may be dynamically built using activities and/or rules in any desirable manner. For example, activities and/or rules of a dynamic processing scheme may be defined by the user, selected by the user from a predefined set of activities and/or rules, automatically generated based in whole or in part on user responses to one or more inquiries regarding the digital image data and/or processing thereof, automatically generated based on a result of performing a prior activity and/or rule, automatically generated based on previously received user responses to inquiries regarding the present digital image data and/or other digital image data, etc. as would be understood by one having ordinary skill in the art upon reading the present descriptions.
In an illustrative implementation of a dynamic process flow, a user captures a digital image of a document using a camera of a mobile device and instantiates a mobile application development platform (MADP). The user provides input to the MADP via a graphical user interface (GUI) and/or a command line interface (CLI). Users may interact with a GUI in one embodiment by dragging-and-dropping controls onto a form, into a graphically-represented workflow, etc. Users may additionally and/or alternatively design one or more GUIs as part of developing the custom mobile application. Further still, the mobile application development platform may enable users to efficiently integrate custom scripts or code snippets into mobile applications. Users may employ any suitable scripting language without departing from the scope of the present disclosures. In some embodiments the mobile development application includes support for Visual Basic and JavaScript, and HTML5.
In other embodiments, the mobile application development platform may be configured to interface with external development environments) and/or platform(s) to facilitate developing mobile applications utilizing functionality of both the presently disclosed platforms and the external development environments) and/or platform(s).
The user input defines workflow(s) and/or user interface(s) to facilitate processing the captured digital image of the document and/or similar documents. Based on the user input, the MADP generates a mobile application including a graphical user interface configured to facilitate similar processing of other digital images of documents.
For example, a user wishes to develop a mobile application for processing digital images of driver licenses. The user instantiates the MADP, and defines a workflow comprising activities and rules for driver license image processing according to a static process scheme.
A first rule directs the mobile application to invoke a native image capture functionality of the mobile device upon a user instantiating the mobile application. The native image capture functionality presents a capture interface and prepares integrated mobile device hardware such as the flash bulb and camera lens for performing a capture activity.
A second rule directs the mobile application to invoke an image quality assurance activity that checks for suitable capture conditions, including detecting ambient light levels using a mobile camera, detecting camera stability using native mobile device hardware such as an integrated gyroscope and/or accelerometer, etc.
A third rule directs the mobile application to invoke the capture activity upon determining that suitable capture conditions exist.
A fourth rule directs the mobile application to invoke an image quality control activity that analyzes the captured image using the mobile device processor and software installed on the mobile device to determine whether the captured image is of sufficient quality (e.g. sufficiently illuminated, focused, etc.) for subsequent processing.
A fifth rule directs the mobile application to invoke a preprocessing activity upon determining the captured image is of sufficient quality for processing, and upon determining the captured image is of insufficient quality for processing, to display an error message and repeat the image quality assurance, image capture, and image quality control activities according to the corresponding rules described above.
The preprocessing activity utilizes software installed on the mobile device to prompt a user for processing parameters, and define a processing profile based on the processing parameters. The preprocessing activity displays the captured image and prompts the user to designate the state that issued the driver license depicted in the captured image, as well as characteristics of driver licenses issued by that state.
For example, the user may designate Maryland as the state, and define the location and characteristics of various features on Maryland driver licenses, such as the location of the driver license number and birth date, and the characteristic that both the birth date and the license number are red text appearing on a substantially white background. The user may also designate the location of the licensee's photograph depicted on Maryland driver licenses. The user may designate the location of the state name, and the characteristic that the state name appears in white font on a substantially blue background.
Based on these characteristics, the user may define custom processing parameters for the locations corresponding to the license number and birth date, and define other custom processing parameters for the locations corresponding to the licensee photograph. The custom processing parameters may improve processing results, for example by under-emphasizing red hues when binarizing the license number and birthdate, under-emphasizing blue hues when binarizing the location depicting the state name, and excluding locations depicting the licensee photograph from binarization. Upon receiving the user input defining characteristics of Maryland driver licenses and the corresponding processing parameters, the preprocessing activity synthesizes this information into a processing profile for Maryland driver licenses which may be subsequently utilized to efficiently process other Maryland driver licenses using image processing software services installed on the mobile device (or other mobile devices capable of performing the same image processing software services).
A sixth rule directs the mobile application to invoke an image processing activity, pass the synthesized processing profile to the image processing activity, and to process the digital image according to the processing profile defined via the preprocessing activity.
A seventh rule directs the mobile application to transmit the processed image and associated metadata to a remote server for further processing using services and/or resources in communication with the server. In the driver license scenario, the user may define the seventh rule to transmit the processed image and associated metadata to a credit agency for performing credit check services using the processed image and/or associated metadata. In another use-case scenario, a designer wants to design a mobile app that allows employees of the organization to submit receipts for expenses. To do so, the designer defines a workflow including four steps: (1) capture at least one image of one or more receipts; (2) extract line items from the receipt image(s); (3) validate extracted data; and (4) transmit image(s) and extracted data to an expense reporting system.
In one approach, the designer creates mobile forms for steps 1 and 4 of the workflow. The designer can associate an image enhancement profile with the capture form to be used in step 1. This profile contains various image processing instructions that may be utilized in step 1, such as deskew, despeckle, auto-crop, binarize, etc. as would be understood by the skilled artisan upon reading these descriptions as being advantageous for various receipt submission applications. The form is partially generated by the platform and the designer preferably only needs to add/remove controls and/or associate actions with the desired control(s). The designer may, for example, place two buttons at the bottom of the form labeled “Re-take’ and “Use”. The designer associates a “mobile capture” action with the “Re-take” button and a “complete activity/take next’ action with the “Use” button. Designing a corresponding form for step 3 may be similarly accomplished.
A user installs the organization's “business app” on a mobile device. The “business app” is part of the mobile development platform and includes the native device services that are used by the designer. The user launches the app and engages an authentication interface. Upon authentication, a first screen is displayed, and includes a menu of options such as “Submit receipt.” The list of menu items may include any options the user is authorized to use. User authorization may be configured and/or managed using the organization's server(s). The user selects “Submit receipt,” which initiates the expense process created by the designer.
The next screen displayed to the user is the form created by the designer that uses the services on the device to operate the device camera, show the viewfinder and the buttons added by the designer. By interacting with this screen, the user takes a picture of the receipt and selects the ‘Use’ button. The action configured by the designer is triggered, and uses the services on the device to process (e.g. deskew, despeckle, crop, binarize, etc.) the image and upload it to the server. The process activity is completed and the app attempts to take the next process activity.
According to one approach, the server next executes the extract line items activity using the uploaded image. Line items may be extracted in any suitable manner, and in some embodiments may utilize mobile classification and/or mobile extraction functionalities such as discussed in the related patent documentation referenced above.
The app takes the next activity and displays the data validation screen to the user. The user makes any required corrections and selects the “Done” button. In response to detecting this user selection, the activity is completed (e.g. on the mobile device) and, on the server, the “send image and data to expense reporting system” activity is executed.
The foregoing illustrative examples are provided to demonstrate some of the many ways in which a user may define and/or use a mobile application within the scope of the present disclosures, and are not to be considered limiting on the present claims.
Those having ordinary skill in the art will appreciate that the mobile application development platform enables a user to define activities and rules in any desirable manner to generate a desired workflow. The activities and rules may utilize any functionality native to the mobile device, whether conferred via the operating system, optionally installed software, or integrated hardware components. The activities and rules may also utilize any functionality not native to the mobile device, but to which the mobile device has access, e.g. via communicating with a server, network, cellular data service, etc. as would be understood by one having ordinary skill in the art upon reading the present descriptions.
Of course, in various approaches a processing scheme may include some combination of dynamic and/or static processing sub-schemes arranged in a static or dynamic order. For example, several dynamic and/or processing sub-schemes may be arranged to define an overall processing scheme that proceeds from sub-scheme to sub-scheme according to a static flow, but one or more of the sub-schemes may proceed according to a dynamic flow. In other approaches, a plurality of dynamic and/or static sub-schemes may be performed in a dynamic manner according to as would be understood by a skilled artisan upon reading the present descriptions.
In various approaches, stimuli may take any form of feedback or information comprehensible by the mobile device. For example, stimuli may include user input such as tactile input (e.g. a user tapping on the screen, gesturing, interacting with a physical button or switch, etc.), audio input (e.g. a tone, a spoken command or data string, etc.), visual input (e.g. a photograph, video, etc.), etc. as would be understood by one having ordinary skill in the art upon reading the present descriptions.
In another embodiment, the processing scheme is static, e.g., a user defines a set of activities to be performed in a specified order, according to a specified set of instructions, using predefined parameters, etc. Subsequent execution of the processing scheme by another user merely performs the defined activities according to the specified order, instructions, parameters, etc. In this manner, users may quickly and conveniently develop new mobile application(s) to perform various data processing operations using any functionality accessible to the mobile device.
In various approaches, mobile applications within the scope of the present disclosure may perform or utilize functionalities native to the mobile device, such as any functionality native to the mobile device operating system, any functionality imparted by one or more hardware components of the mobile device, etc. as would be understood by one having ordinary skill in the art upon reading the present descriptions. Moreover, mobile applications within the scope of the present disclosure may perform or utilize any function the mobile device is configured to perform or utilize. For example, the presently disclosed embodiments may be configured to interface with any hardware and/or software function installed on the mobile device, such as an image processing application or service, data management application or service.
Those having ordinary skill in the art will appreciate that any function, operation, process, etc. recited herein may be performed using any suitable resource(s), such a mobile device, a remote server, a cloud computing environment, etc. with the preference that the resource performing the activity, operation, process, etc. has access to any hardware component(s) necessary to perform the function, operation, etc. More preferably, the hardware component(s) are integrated into the mobile device. Of course, any suitable approach to obtaining information utilized in performing activities, operations and/or processes that would be understood by one having ordinary skill in the art reading these descriptions may be employed without departing from the scope of the present disclosure.
For example, if a process relies on location information (such as may be obtained using data from a GPS satellite, wireless network connectivity information, etc.), then the resource assigned to perform the activity, operation, function, etc. relying on such location information (e.g. GPS satellite data, WiFi Network name, access point location, etc.) preferably is capable of obtaining the corresponding data. Thus if a process relies on GPS location information, the resource preferably has access to a GPS receiver. Similarly, a mobile device performing an activity, operation, process, etc. relying on stability information preferably has access to an accelerometer and a gyroscope. More preferably, the GPS receiver, accelerometer, gyroscope, etc. is/are integrated into the mobile device.
In a preferred embodiment, applications may be developed, modified, and/or adjusted and distributed in near-real time across a mobile communication network without needing to deploy new instance(s) of the mobile application.
In more embodiments, the processing scheme is dynamic, e.g. the user dynamically defines and/or modifies rules and/or activities in real-time or near real-time while processing an image or other data. In some embodiments, the mobile development platform may receive feedback from a user relating to developing a mobile application, workflow, etc. For example, the mobile development platform may request a user define or select an activity, rule, etc. from a predefined set. The request may be made in response to a user defining a rule, activity, workflow, etc. that has been previously associated with one or more of the activities, rules, etc. in the predefined set.
Similarly, members of the predefined set of rules, activities, etc. may be determined based on prior user interaction with and/or feedback provided to the mobile development platform. Those having ordinary skill in the art reading the present descriptions will appreciate that the mobile application development platform is capable of “learning” user preferences, tendencies, etc. and providing interactive feedback to assist users in developing custom mobile applications suitable to their needs.
In still more embodiments, one or more rules facilitate performing one or more of the activities based on one or more stimuli.
For instance, in one embodiment, rules dictate the sequence of activities performed in an overall workflow, and the workflow may proceed from one activity to another in response to receiving a stimulus and responding to the stimulus according to behavior defined in the rule.
In more embodiments, rules may direct a mobile application to invoke an image capture activity and capture digital image data using a mobile device camera in response to receiving environmental stimuli, e.g. via integrated hardware components such as an accelerometer and a gyroscope. More particularly, the rule may direct the mobile application to capture the digital image data only upon receiving stimuli satisfying specific criteria, e.g. the mobile device being oriented substantially parallel to the ground, the mobile device being stably oriented at a particular angle for a particular duration (e.g. 1-2 seconds) without any significant deviation (e.g. greater than 5 degrees), the mobile device being confined to a particular physical location for a particular duration (i.e. the mobile device being still for a sufficient time to minimize blur), etc. as would be understood by one having ordinary skill in the art upon reading the present descriptions.
Of course, stimuli may take other forms, such as external stimuli, which include user input via an input/output interface (keyboard displayed on the mobile device), a user interacting with a button or switch of the mobile device, interacting with the display of the mobile device, shaking the mobile device, etc. as would be understood by one having ordinary skill in the art upon reading the present descriptions.
As will be appreciated by those having ordinary skill in the art upon reading these descriptions, stimuli within the scope of these disclosures may include one or more of external stimuli and environmental stimuli.
In additional and/or alternative embodiments, method 300 may include any number of optional operations and/or features in any suitable combination as would be comprehended by a skilled artisan reading these descriptions. For example, in one embodiment method 300 may further include: querying one or more hardware components of the mobile device for metadata relating to the digital image data; and receiving the metadata from one or more of the hardware components.
Metadata may be any data relating to the digital image data and capable of being received from a hardware component of the mobile device. For example, metadata may include location information as described above. In one embodiment, the mobile application may, in the course of processing image data such as an image of a driver license or insurance claim, query the mobile device operating system to determine the geographical location of the mobile device.
For example, in one illustrative embodiment the user may utilize the mobile application development platform to generate and/or modify a mobile application to associate a captured image of a driver license or insurance claim with geographical location gathered by the mobile device at the time the image was captured or otherwise associated with the image.
In further embodiments, the user may utilize the mobile application development platform to generate and/or modify a mobile application to include image processing functionality capable of processing images of driver licenses, insurance claims, etc. using custom parameters based at least in part on geographical location. For example, the mobile device may have access to a knowledge base comprising template driver licenses, insurance claims, etc. organized according to geographical location and having associated therewith custom image processing parameters. A user may generate and/or modify a mobile application to retrieve the custom image processing parameters from the database, selecting a template and/or parameters based at least in part on geographical location information associated with the image to be processed.
In another illustrative embodiment, a user may utilize the mobile application development platform to generate and/or modify a mobile application to include document classification functionality capable of classifying documents depicted in digital images based at least in part on geographical location information associated with the image.
Moreover, metadata may be one or more of a mobile device geographical location, a date, a time, a mobile device orientation, mobile device acceleration vector, an audio recording, a video recording, a digital image, one or more alphanumeric characters, and user input i.e. tactile feedback provided via a display, switch, button, etc. of the mobile device.
In an exemplary embodiment, the workflow utilizes one or more of native mobile device services and server services. As understood herein, any operation may be considered a native mobile device service or a server service, interchangeably, with the primary difference being the identity and location of the resource(s) utilized to perform the operation. A native mobile device service is performed using one or more hardware and/or software components of a mobile device, while a server service is performed using one or more resources in communication with a server or network environment remote from the mobile device but with which the mobile device is capable of communicating. Of course, in various embodiments the presently disclosed mobile application development platform is capable of integrating native mobile device services and/or server services in any combination and/or permutation.
Moreover, in some approaches one or more operations may be performed using a combination of native mobile device services and server services. For example, a user initiates an operation utilizing native mobile device services. However, due to high computational cost (or other factors as would be appreciated by one having ordinary skill in the art upon reading the present descriptions), performing the operation utilizing only native mobile device services would be undesirably inefficient or take an undesirable amount of processing resources or time.
Thus, after a certain threshold of processing resources are consumed by the native mobile device services, or after a threshold duration of processing time has elapsed, the workflow may shift the operation and instead utilize server services, which generally will have greater available processing power than native mobile device services. In this manner, an operation may be performed utilizing the most efficient resources available, whether at the direction of the user or in a process that is transparent to the user.
While the presently disclosed systems, methods, and computer program products are suitable for use in a wide variety of applications and/or implementations, one particularly advantageous implementation of these concepts is in the field of digital image processing, and more particularly as relating to the processing of digital documents and/or images depicting documents.
As such, in some approaches the digital image data represents a document, and methods, systems and computer program products disclosed herein may further involve capturing the digital image data. Accordingly, in one particularly preferred approach, the user input defining the workflow relates to the document, the user input defining the user interface relates to the document, and the workflow is configured to process the digital image of the document utilizing one or more of native mobile device services and server services.
Moreover, the digital image data may represent a document having one or more unique characteristics, and the workflow may thus be advantageously configured to classify the document according to at least one of the unique characteristics.
Utilizing/Modifying a Mobile Application Developed Via the Mobile Application Development Platform
The presently disclosed inventive concepts may be embodied as systems, methods, and computer program products for using mobile applications, e.g. via a mobile application development platform as discussed below with reference to FIG. 4.
In one particular embodiment, such a method 400 is shown in FIG. 4. The method 400 may be performed in any environment, including those depicted in FIGS. 1-2, among others. Moreover, method 400 may include any alternative permutation and/or additional combination of features and/or operations as discussed herein, in various approaches.
In operation 402, a mobile application is instantiated on a mobile device. The mobile application may be instantiated in any suitable manner, such as in response to user input, in response to a call or request from another application and/or process being performed by the mobile device and/or another device in communication with the mobile device. Equivalent ways of instantiating mobile applications on mobile devices, such as would be understood by those having ordinary skill in the art upon reading the present descriptions are also within the scope of this disclosure.
In operation 404, a workflow is launched within the mobile application, the workflow comprising one or more activities and one or more rules.
In operation 406, one or more user interfaces are rendered, the rendering being based at least in part on the workflow. Rendering the defined user interface, in various embodiments, may be based on instructions from the user that defined the process, based on an auto-rendering capability, etc. For example, a user may define the user interface explicitly or allow the development platform to generate the UI automatically. In either case, what gets created is a package of HTML and JavaScript instructions that the device can interpret to create a user interface and including buttons and images and backgrounds, etc.
When utilizing auto-render capabilities, the application may utilize an algorithm that looks at what information is the activity is the information trying to collect. So we tend to call those fields. In one example, the user enters five pieces of data or reviews five pieces of data. The algorithm may create a form that has five fields with five labels and in the case of the review, text may be placed into each of those five fields and/or presented to the user, for instance with a button that allows the user to accept, reject, modify or negate the text.
In operation 408, at least one of the user interfaces is displayed via a display of the mobile device.
In operation 410, user input is received via at least one of the user interfaces.
In operation 412, the workflow is modified based at least in part on the user input.
In some approaches, modifying the workflow includes interfacing the mobile application with a mobile application development platform. In other approaches, the workflow additionally and/or alternatively utilizes one or more of native mobile device services and server services.
In any given approach, the workflow may be configured to process digital image data. The digital image data may be or include a digital representation of a document. As such, method 400 may include, in some embodiments, capturing the digital image data.
Where digital image data corresponds to a digital representation of a document, the user input defining the workflow and/or the user input defining the user interface may each be related to the document, singly or in unison. Moreover, the workflow may be configured to process the digital image of the document utilizing one or more of native mobile device services and server services.
The digital image data optionally represents a document having one or more unique characteristics. In these circumstances, the workflow may preferably be configured to classify the document according to at least one of the unique characteristics.
Preferably, the workflow is configured to process digital image data based at least in part on the activities and the rules. Further, the activities may include one or more of interactive activities and non-interactive activities; while the one or more rules facilitate performing one or more of the activities according to a processing scheme. In some approaches, the processing scheme is either static or dynamic, while in other approaches the processing scheme may be partially static and partially dynamic.
In some approaches, one or more of the rules facilitate performing one or more of the activities based on one or more stimuli, such as external stimuli and environmental stimuli.
Moreover, method 400 may include querying one or more hardware components of the mobile device for metadata relating to the digital image data, in one embodiment. The metadata may be received from one or more of the hardware components. The metadata may include mobile device geographical location information, date and/or time information, mobile device orientation information, mobile device acceleration vector information, an audio recording, a video recording, a digital image, one or more alphanumeric characters, and user input, in various approaches.
In one particularly preferred variety of embodiments, the presently disclosed inventive concepts may be implemented to define one or more dynamic workflow(s), e.g. as a mobile application. The dynamic workflow(s) are preferably configured to facilitate user interaction with a third-party service, e.g. a financial service. The third-party service may include a plurality of constituent services also facilitated via the specifically-configured mobile application, as described in further detail below.
The dynamic workflows may be defined using one or more interfaces provided via the smart development platform. Preferably, the development platform facilitates design and implementation of a plurality of forms to define the dynamic workflow and any associated rules, activities, etc. The user may leverage the development platform to design a series of interactive forms leveraging the activities, rules, etc. of the dynamic workflow to provide a functional application useful to an end user.
For example, in one approach the smart development platform may be utilized to develop a mobile application configured to facilitate financial activities. The user interacts with the interfaces provided via the smart development platform to design a series of forms including an authentication/authorization form or interface, one or more data entry and/or data capture form(s) or interface(s), one or more data review form(s) or interface(s), and one or more prompts, etc. as would be understood by one having ordinary skill in the art upon reading the present descriptions.
The exemplary approach set forth above may be embodied, for example, in a user-developed dynamic workflow that utilizes an authentication form, a capture form, a review form, and a submission/confirmation prompt.
The authentication form, in one approach, may be a “title” screen or a first interface displayed to a user after launching, switching focus to, or otherwise invoking the mobile application. The authentication form may be configured to include one or more buttons, fields, switches, etc.
The buttons may include, for example, a “login” button with which a user may interact to provide authentication information associated with an existing account or account(s), a “new” or “apply” button configured to facilitate the user engaging in a new account application or account opening process, one or more information buttons (e.g. “contact us,” “locations,” “about,” etc.) configured to facilitate displaying information to the user such as a list of physical locations where the service provider may be located, contact information for the service provider, version, compatibility, or other technical information for the mobile application, etc. as would be understood by one having ordinary skill in the art upon reading the present descriptions.
The user may in one approach interact with the login button and provide corresponding account information, e.g. a username and password, account number, security image, signature, or any other form of authenticating information, as would be appreciated by skilled artisans reading the instant descriptions. Upon providing the appropriate account information, the user is directed to an interface where the account(s) under the user's control may be managed or otherwise interacted with via the mobile application.
In more approaches, the user may instead (or in addition) seek a new service or account by interacting with the “new” or “apply” button as described above. The user is then directed to a capture interface that enables the user to capture information requisite to the application process. The requisite information may be manually input by the user, e.g. via a physical or virtual keyboard on the mobile device, and/or input via image data depicting some or all of the requisite information. Accordingly, the capture interface may take any suitable form in the particular context advantageous to the dynamic workflow in connection with which the mobile application is to be utilized.
For example, in preferred approaches the Capture Interface may substantially represent a viewfinder of a digital camera (e.g. on a mobile phone). The capture interface may even more preferably leverage an existing image capture interface native to the mobile device upon which the mobile application is implemented. Even more preferably, the capture interface includes one or more additional functions not native to the mobile device, such as one or more prompts providing relevant feedback to a user about the suitability of environmental conditions (e.g. lighting, focus, device orientation, field-of-view, etc.) to a requested data capture operation. The capture interface may also include additional functions such as an automatic or “continuous” capture capability that automatically acquires image data via the mobile device image sensor(s) upon detecting the existence of one or more optimal data capture conditions. Of course, the capture interface includes a function enabling a user to manually capture data according to the user's preference and using the mobile device components (e.g. a camera button in the case of manually capturing image data).
Sensors as described herein in various embodiments should be understood as potentially including any combination of image sensor(s) described herein and/or as would be understood by a skilled artisan as conventionally included in a mobile device. Exemplary sensors include audio sensors such as a microphone, motion sensor(s) such as an accelerometer and/or gyroscope, etc. as would be understood by a skilled artisan reading the present descriptions.
In some approaches, the capture form or interface may preferably include customizable features and corresponding controls for the user, e.g. allowing a user to modify a size or location of the capture “window” defined by viewfinder “corners”, modify the value or acceptable range of values for conditions sensed during a “continuous” capture operation (e.g. acceptable device orientation, angle, stability duration, etc.).
Regardless of whether data are captured via one or more sensors of the mobile device, manually input by the user, obtained via a lookup operation using external data sources, or any other data capture technique, the mobile application preferably provides an indication to the user upon capturing the data, and provides the user with the ability to review accept, modify and/or reject the captured data via a Review Form or Interface. In some approaches, this interface may be referred to as a “preview” interface, especially when the interface is invoked prior to submitting data for final review, approval, processing, etc. via the appropriate workflow(s).
Preferably, the review form or interface includes at least a preview of the captured data (e.g. a preview of an imaged document or typed word(s)) and a plurality of buttons or actions. For example, in a minimalist approach the review interface may include a “recapture” “reject” or “discard” button configured to reject previously captured/input data and repeat the capture process; and a “save,” “use” or “accept” button configured to designate the captured data for subsequent use in a dynamic workflow or smart mobile application.
The “save” button may be further configured, in preferred but optional approaches, to assist a user in improving the quality of the captured data for subsequent use in the context of the associated workflow. For example, assistance and/or quality improvement may include formatting the captured data in a manner specifically tailored to enable or assist subsequent processing or use thereof, (pre)processing data according to one or more procedures designed to improve or enhance desired data among the entirety of the captured data, such as specifically enhancing the appearance of black text characters on a document having a white background, and which was imaged on a wooden surface with a dark, glossy finish. In this example, the enhancement may include suppressing color data and enhancing the binary (black/white) distinctions between the text and the document background.
Of course, in other implementations, other enhancements may be advantageous or desirable. Continuing with the exemplary case of imaging documents, other useful enhancements may include functions such as modifying a page orientation, detecting uneven illumination, balancing uneven illumination, modifying document dimensions (i.e. edge positions, lengths) to adjust for perspective skew or “fishbowl” effects, modifying parameters associated with detecting page edges, optimal capture conditions (e.g. maximum device orientation angle, minimum stability duration, etc.). Any of these advantageous enhancements may be manually invoked via the review interface, and/or designated for automatic performance in response to capturing appropriate data.
In addition to the review interface described above in association with captured data, exemplary workflows developed using a dynamic smart mobile platform as described herein may optionally include an additional data input and/or verification interface. The additional data input and/or verification interface preferably represents a web page or form, and includes fields displaying captured information and fields enabling/facilitating the user confirming, negating, and/or modifying the captured information in the captured information fields. For example, in one approach the additional data input/verification interface includes a list of fields, each identified by a “type” label (e.g. “First” “Last” “MI” “Date of Birth” “Address” etc.) and accompanied by an indicator such as a check box and/or a manual text entry field. The user may then review each item of captured information, verify the accuracy thereof (both with respect to the “type” identified and with respect to the accurate representation of the specific value in the field) and either accept the captured information as “accurate,” reject the captured information outright, or input modified information accordingly.
Finally, in a preferred approach the mobile application developed using the presently described smart platform includes a legal interface, which essentially enables display of any pertinent legal information and/or to receive any required authorization from the user of the mobile application. The legal interface is preferably embodied as a form comprising text of the pertinent legal issues (e.g. terms and conditions of a license) and two buttons with which a user may interact—an accept/agree button and a decline/disagree button. The user may only complete the processing performed via the mobile application upon accepting the terms of the legal agreement(s) displayed via the legal interface, in some approaches.
In general, and as described above, a user interacting with the presently disclosed mobile application may be enabled to remotely conduct any number of activities that would be possible if the user were present at a physical location where the financial service provider conducts business.
Continuing with the exemplary scenario where a user wishes to engage one or more financial services, a user interacting with a mobile application as described herein may remotely perform any action and/or engage the service provider in any manner, context, or capacity that typically requires the user's physical presence at a service location.
For example, in some approaches the user may engage the financial mobile application to obtain and/or perform banking services such as depositing, withdrawing and/or transferring funds to and/or from one or more accounts owned or controlled by the user, making payments from an account under the user's control, link one or more user-controlled accounts to one or more external services, transactions, etc. (e.g. liking a bank account to an electronic payment service such as an electronic utility bill payment service, consumer payment service like PayPal, etc. as would be understood by one having ordinary skill in the art upon reading the present descriptions.
In more approaches, the user may also interact with the mobile application to facilitate opening, closing and/or modifying accounts under the user's authority to control. In some instances, the financial institution providing the financial services may implement security procedures that limit the capabilities offered with respect to a particular type of user, account, etc.
For example, in one embodiment a mobile application enabling a user to apply for a new account and/or an associated service may be deemed a “limited user” and accordingly prohibited or given only restricted access to sensitive actions, functions, etc. Illustrative scenarios where a “limited user” or analogous restriction may be utilized include a user attempting to withdraw funds from a loan for which the user has applied (but not yet been approved); a user attempting to withdraw funds from an account having a pending balance that has not yet cleared; a user attempting to administer an account for which a user is authorized to make deposits/withdrawals but for which the user is not authorized to view or modify account holder information, etc. as would be understood by one having ordinary skill in the art upon reading the present descriptions.
Further still, in some approaches the user may utilize the mobile application to apply for various types of services provided by the financial institution, such as applying for a loan or line of credit (or extension of existing loan or line of credit), applying for a new account (and/or changing an account status or type from one category to another, e.g. business to personal, checking to savings, etc.) requesting a credit report, etc. as would be understood by one having ordinary skill in the art upon reading the present descriptions.
As noted above, the presently disclosed inventive concepts may be implemented as a system. In one embodiment, such an exemplary system includes a processor; and logic in and/or executable by the processor. Specifically, the logic causes the processor to: receive user input defining a workflow comprising one or more activities and one or more rules; receive user input defining a user interface (UI) configured to facilitate a user performing the workflow at least in part using a processor of mobile device; and generate a mobile software application based on the workflow and the UI, where the workflow is configured to process digital image data based at least in part on the activities and the rules.
As similarly noted above, the presently disclosed inventive concepts may be implemented as a computer program product. In one embodiment, such an exemplary computer program product includes a computer-readable medium having stored thereon computer readable program code executable by a processor to cause the processor to: receive user input defining a workflow comprising one or more activities and one or more rules; receive user input defining a user interface (UI) configured to facilitate a user performing the workflow at least in part using a processor of mobile device; and generate a mobile software application based on the workflow and the UI, where the workflow is configured to process digital image data based at least in part on the activities and the rules.
In some approaches, the presently described systems, methods, and computer program products may utilize and/or be deployed in whole or in part as part of a VPN platform or a work platform to use as a tool to build mobile applications screens that display information similar to what users might see, and to define and/or determine (previously or in real-time) the subsequent information and/or screens a user may next be presented based on user interaction with the previous screen and the rules that were orchestrated with the business flow that was created.
The present descriptions provide guidance to creating new, intuitive tools for users to build mobile business apps based on specific associated processes, a dynamic mobile smart application. In some embodiments, the application is not static, so a user/developer can orchestrate the associated process through, for example, a mobile device. The user can go back in and change the associated process, and instantiations of that process and/or application would inherit those changes almost immediately, preferably deploying another instance of that application.
An additional feature is allowing that application that was built and orchestrated to actually interact with the hardware on the device and our mobile technology on the device to process information, e.g. to physically capture the document or classify an extraction information utilize other available information such as GPS information. In various embodiments, the application is not just a static workflow, it is a mutable workflow that can evoke and exploit any available mobile capture, mobile classification and/or mobile extraction functionality such as discussed in the related patent documentation referenced above. These embodiments thus enable a class of mobile applications that are not only dynamic, but applications can easily create new workflows and/or applications to acquire and/or understand information in real time.
instantiating a mobile application on a mobile device;
launching a workflow within the mobile application, the workflow comprising: one or more interactive activities; one or more non-interactive activities; and one or more rules that facilitate performing the one or more interactive activities and the one or more non-interactive activities according to a processing scheme, wherein the processing scheme comprises a first portion characterized by a static processing and a second portion characterized by dynamic processing;
rendering one or more user interfaces based at least in part on the workflow;
displaying at least one of the user interfaces on a display of the mobile device;
receiving user input via at least one of the user interfaces; and
modifying the workflow based at least in part on the user input,
wherein the workflow is configured to process digital image data based at least in part on the one or more activities and the one or more rules.
2. The computer implemented method as recited in claim 1, the one or more activities comprising:
capturing or receiving the digital image data via the mobile device; and
classifying an object represented in the digital image data.
3. The computer implemented method as recited in claim 1, wherein the user input comprises one or more of a confirmation, a negation, and a modification of at least one of:
one or more of the activities; and
one or more of the rules.
4. A computer program product comprising a non-transitory computer-readable medium having stored thereon computer readable program code executable by a processor to cause the processor to:
instantiate a mobile application on a mobile device;
launch a workflow within the mobile application, the workflow comprising: one or more interactive activities; one or more non-interactive activities; and one or more rules that facilitate performing the one or more interactive activities and the one or more non-interactive activities according to a processing scheme, wherein the processing scheme comprises a first portion characterized by a static processing and a second portion characterized by dynamic processing;
render one or more user interfaces based at least in part on the workflow;
display at least one of the user interfaces on a display of the mobile device;
receive user input via at least one of the user interfaces; and
modify the workflow based at least in part on the user input; and
5. The computer program product as recited in claim 4, wherein the one or more activities comprise:
6. The computer program product as recited in claim 4, wherein the user input comprises one or more of a confirmation, a negation, and a modification of at least one of:
7. A system, comprising a processor and logic integrated with, executable by, or integrated with and executable by the processor to cause the processor to:
modify the workflow based at least in part on the user input,
8. The system as recited in claim 7, wherein the one or more activities comprise:
9. The system as recited in claim 7, wherein the user input comprises one or more of a confirmation, a negation, and a modification of at least one of:
5899978 May 4, 1999 Irwin
6571008 May 27, 2003 Bandyopadhyay et al.
8059888 November 15, 2011 Chen et al.
8126924 February 28, 2012 Herin
8184156 May 22, 2012 Mina et al.
8261231 September 4, 2012 Hirsch et al.
8532374 September 10, 2013 Chen et al.
8553984 October 8, 2013 Slotine et al.
8620078 December 31, 2013 Chapleau et al.
8681150 March 25, 2014 Kim et al.
8811751 August 19, 2014 Ma et al.
8918357 December 23, 2014 Minocha
9020432 April 28, 2015 Matsushita et al.
9135277 September 15, 2015 Petrou
9183224 November 10, 2015 Petrou et al.
9239713 January 19, 2016 Lakshman
9251614 February 2, 2016 Tian
9277022 March 1, 2016 Lee
9292815 March 22, 2016 Vibhor
9298979 March 29, 2016 Nepomniachtchi et al.
9367899 June 14, 2016 Fang
9373057 June 21, 2016 Erhan et al.
9405772 August 2, 2016 Petrou et al.
9436921 September 6, 2016 Whitmore
9648297 May 9, 2017 Ettinger et al.
9747504 August 29, 2017 Ma et al.
9754164 September 5, 2017 Macciola et al.
9760788 September 12, 2017 Shustorovich et al.
9767354 September 19, 2017 Thompson et al.
9767379 September 19, 2017 Macciola et al.
9769354 September 19, 2017 Thrasher et al.
9779296 October 3, 2017 Ma et al.
9819825 November 14, 2017 Amtrup et al.
9934433 April 3, 2018 Thompson et al.
9946954 April 17, 2018 Macciola et al.
9978024 May 22, 2018 Ryan
9996741 June 12, 2018 Amtrup et al.
20030046445 March 6, 2003 Wilt et al.
20040022439 February 5, 2004 Beardsley
20040143547 July 22, 2004 Mersky
20040252190 December 16, 2004 Antonis
20050163343 July 28, 2005 Kakinami et al.
20050216564 September 29, 2005 Myers et al.
20050226505 October 13, 2005 Wilson
20060082595 April 20, 2006 Liu et al.
20060095830 May 4, 2006 Krishna et al.
20060239539 October 26, 2006 Kochi et al.
20060265640 November 23, 2006 Albomoz et al.
20070031028 February 8, 2007 Vetter et al.
20070036432 February 15, 2007 Xu et al.
20080177612 July 24, 2008 Starink
20080211809 September 4, 2008 Kim et al.
20090110267 April 30, 2009 Zakhor et al.
20090164889 June 25, 2009 Piersol et al.
20090254487 October 8, 2009 Dhar
20100049035 February 25, 2010 Hu et al.
20100142820 June 10, 2010 Malik et al.
20100174974 July 8, 2010 Brisebois
20100214291 August 26, 2010 Muller et al.
20110004547 January 6, 2011 Giordano
20110025825 February 3, 2011 McNamer et al.
20110313966 December 22, 2011 Schmidt
20120008856 January 12, 2012 Hewes et al.
20120008858 January 12, 2012 Sedky et al.
20120195466 August 2, 2012 Teng et al.
20120269398 October 25, 2012 Fan et al.
20120284185 November 8, 2012 Mettler et al.
20120301024 November 29, 2012 Yuan et al.
20130066798 March 14, 2013 Morin
20130078983 March 28, 2013 Doshi
20130080347 March 28, 2013 Paul et al.
20130085935 April 4, 2013 Nepomniachtchi et al.
20130185618 July 18, 2013 Macciola
20130290036 October 31, 2013 Strange
20140032406 January 30, 2014 Roach
20140047367 February 13, 2014 Nielsen
20140055812 February 27, 2014 DeRoller
20140149308 May 29, 2014 Ming
20140211991 July 31, 2014 Stoppa et al.
20150093033 April 2, 2015 Kwon et al.
20150248391 September 3, 2015 Watanabe
20150317529 November 5, 2015 Zhou et al.
20160320466 November 3, 2016 Berker et al.
20170147572 May 25, 2017 Kilby et al.
20170286764 October 5, 2017 Ma et al.
20170351915 December 7, 2017 Thompson et al.
20170357869 December 14, 2017 Shustorovich et al.
101339566 January 2009 CN
101673402 March 2010 CN
101894262 November 2010 CN
1229485 August 2002 EP
104034671 February 1992 JP
H05060616 March 1993 JP
H09091341 April 1997 JP
2000298702 October 2000 JP
2001297303 October 2001 JP
2002109242 April 2002 JP
2004005624 January 2004 JP
2004523022 July 2004 JP
2004363786 December 2004 JP
2005071262 March 2005 JP
2005208861 August 2005 JP
2006054519 February 2006 JP
2006126941 May 2006 JP
2006185367 July 2006 JP
2007251518 September 2007 JP
2009015396 January 2009 JP
2009211431 September 2009 JP
2009541896 November 2009 JP
2010062722 March 2010 JP
2011118513 June 2011 JP
2011118600 June 2011 JP
2012008791 January 2012 JP
2012058904 March 2012 JP
2012156644 August 2012 JP
2012194736 October 2012 JP
2012217159 November 2012 JP
97006522 February 1997 WO
2013059599 April 2013 WO
Kofax Inc., Module 2 Kofax Capture Overview, Jun. 2011, 22 pages.
Kofax Inc., Kofax Capture 10.0 Developer's Guide, Aug. 2011, 138 pages.
Abiteboul et al., Collaborative data-driven workflows: think global, act local, 12 pages (Year: 2013).
Chen et al., A model driven visualization platform for workflow, 6 pages (Year: 2010).
Notice of Allowance from U.S. Appl. No 14/491,901, dated Aug. 4, 2015.
Notice of Allowance from U.S. Appl. No 14/220,023, dated Jan. 30, 2015.
Notice of Allowance from U.S. Appl. No. 13/740,145, dated May 26, 2015.
Non-Final Office Action from U.S. Appl. No. 15/424,756, dated Jun. 27, 2017.
Corrected Notice of Allowance from U.S. Appl. No. 15/191,442, dated Jun. 29, 2017.
Notice of Allowance from U.S. Appl. No. 14/818,196, dated Jul. 3, 2017.
Extended European Search Report from European Application No. 14788928.1, dated Oct. 17, 2016.
Hottrix, “How to make an app in 60 seconds with App.Cat app creator for iPhone, Android, Mac, and Windows,” Youtube, Apr. 11, 2011, p. 1, retrieved from https://www.youtube.com/watch?v=0GhK8s5VYH4.
Extended European Search Report from European Application No. 14847922.3 dated Jun. 22, 2017.
Tsoi et al., “Geometric and Shading Correction for Images of Printed Materials a Unified Approach Using Boundary,” Proceedings of the 2004 IEEE Computer Society Conference on Computer Vision and Pattern Recognition (CVPR'04), 2004, pp. 1-7.
Tian et al., “Rectification and 3D Reconstruction of Curved Document Images,” 2011 IEEE Conference on Computer Vision and Pattern Recognition, Jun. 2011, pp. 377-384.
Notice of Allowance from U.S. Appl. No. 14/927,359, dated Jul. 20, 2017.
Clemons, J. et al., “MEVBench: A Mobile Computer Vision Benchmarking Suite,” IEEE, 2011, pp. 91-102.
Non-Final Office Action from U.S. Appl. No. 15/234,993, dated Dec. 14, 2017.
Corrected Notice of Allowance from U.S. Appl. No. 14/927,359, dated Aug. 2, 2017.
Corrected Notice of Allowance from U.S. Appl. No. 14/927,359, dated Aug. 9, 2017.
Corrected Notice of Allowance from U.S. Appl. No. 15/191,442, dated Aug. 2, 2017.
Notice of Allowance from U.S. Appl. No. 15/146,848, dated Aug. 4, 2017.
Notice of Allowance from U.S. Appl. No. 15/389,342, dated Aug. 14, 2017.
Notice of Grounds of Rejection from Japanese Application No. 2015-229466, dated Jul. 18, 2017, with English Translation.
Office Action from Japanese Patent Application No. 2016-512078, dated Aug. 8, 2017.
Thompson et al., U.S. Appl. No. 15/686,017, filed Aug. 24, 2017.
Corrected Notice of Allowance from U.S. Appl. No. 15/389,342, dated Aug. 30, 2017.
Non-Final Office Action from U.S. Appl. No. 15/214,351, dated Sep. 5, 2017.
Shustorovich et al., U.S. Appl. No. 15/672,200, filed Aug. 8, 2017.
Notice of Allowance from U.S. Appl. No. 15/390,321, dated Oct. 4, 2017.
Final Office Action from U.S. Appl. No. 14/932,902, dated Oct. 20, 2017.
Non-Final Office Action from U.S. Appl. No. 15/686,017, dated Oct. 18, 2017.
Corrected Notice of Allowance from U.S. Appl. No. 15/390,321, dated Oct. 20, 2017.
Supplementary European Search Report from European Application No. 15764687.8, dated Oct. 17, 2017.
Examination Report from European Application No. 14775259.6, dated Oct. 25, 2017.
Office Action from Chinese Patent Application No. 201480014229.9, dated Oct. 10, 2017.
Examination Report from European Application No. 13738301.4, dated Oct. 26, 2017.
Office Action from Japanese Patent Application No. 2016-502178, dated Apr. 10, 2018.
Office Action from Japanese Patent Application No. 2016-568791, dated Mar. 28, 2018.
Kawakatsu et al., “Development and Evaluation of Task Driven Device Orchestration System for User Work Support,” Forum on Information Technology 10th Conference Proceedings, Institute of Electronics, Information and Communication Engineers (IEICE), Aug. 22, 2011, pp. 309-310.
Statement of Relevance of Non-Translated Foreign Document NPL: Kawakatsu et al., “Development and Evaluation of Task Driven Device Orcestration System for User Work Support,” Forum on Information Technology 10th Conference Proceedings, Institute of Electronics, Information and Communication Engineers (IEICE), Aug. 22, 2011, pp. 309-310.
Non-Final Office Action from U.S. Appl. No. 15/214,351, dated May 22, 2018.
Final Office Action from U.S. Appl. No. 15/424,756, dated Dec. 22, 2017.
Non-Final Office Action from U.S. Appl. No. 15/157,325, dated Jan. 8, 2018.
Advisory Action from U.S. Appl. No. 14/932,902, dated Jan. 23, 2018.
Non-Final Office Action from U.S. Appl. No. 15/390,321, dated Jan. 23, 2018.
Final Office Action from U.S. Appl. No. 15/214,351, dated Jan. 25, 2018.
Notice of Allowance from U.S. Appl. No. 15/686,017, dated Feb. 14, 2018.
Office Action from Japanese Patent Application No. 2016-512078, dated Feb. 13, 2018.
Notice of Allowance from U.S. Appl. No. 14/932,902, dated Feb. 16, 2018.
Corrected Notice of Allowance from U.S. Appl. No. 14/932,902, dated Mar. 2, 2018.
Office Action from Japanese Patent Application No. 2016-502192, dated Feb. 13, 2018.
Hirose et al., “Media Conversion for Document Images Based on Layout Analysis and Character Recognition,” IEICE Technical Report, The Institute of Electronics, Information and Communication Engineers, vol. 99, No. 648, Feb. 21, 2000, pp. 39-46.
Oe et al., “Segmentation Method of Texture Image Using Two-Dimensional AR Model and Pyramid Linking,” The Transactions of the Institute of Electronics, Information and Communication Engineers, vol. J75-D-II, No. 7, Jul. 25, 1992, pp. 1132-1142.
Non-Final Office Action from U.S. Appl. No. 14/804,281, dated Mar. 16, 2018.
Office Action from Chinese Patent Application No. 201580014141.1, dated Feb. 6, 2018.
Notice of Allowance from U.S. Appl. No. 15/157,325, dated Mar. 26, 2018.
Corrected Notice of Allowance from U.S. Appl. No. 15/157,325, dated Apr. 5, 2018.
Non-Final Office Action from U.S. Appl. No. 15/385,707, dated Apr. 4, 2018.
Final Office Action from U.S. Appl. No. 15/234,993, dated Apr. 9, 2018.
Wang et al., “Object Recognition Using Multi-View Imaging,” ICSP2008 Proceedings, IEEE, 2008, pp. 810-813.
Examination Report from European Application No. 14773721.7, dated Mar. 27, 2018.
Office Action from Taiwanese Application No. 103114611, dated Feb. 8, 2018.
Notice of Allowance from U.S. Appl. No. 15/390,321, dated Aug. 6, 2018.
Corrected Notice of Allowance from U.S. Appl. No. 15/396,322, dated Aug. 8, 2018.
Corrected Notice of Allowance from U.S. Appl. No. 15/234,993, dated Aug. 1, 2018.
Notice of Allowance from U.S. Appl. No. 15/385,707, dated Aug. 15, 2018.
Corrected Notice of Allowance from U.S. Appl. No. 15/390,321, dated Sep. 19, 2018.
Patent number: 10146803
Patent Publication Number: 20150355889
Assignee: KOFAX, INC (Irvine, CA)
Inventors: Steven Kilby (Rancho Santa Margarita, CA), Anthony Macciola (Irvine, CA), Jan W. Amtrup (Silver Spring, MD), Bruce Orcutt (Newport Beach, CA)
Application Number: 14/829,474
Current U.S. Class: Data Structure Types (707/791)
International Classification: G06Q 10/00 (20120101); G06F 17/30 (20060101); G06F 9/44 (20180101); G06Q 10/06 (20120101); H04W 4/02 (20180101); G06F 8/38 (20180101); G06Q 40/02 (20120101); G06Q 20/10 (20120101); G06Q 40/08 (20120101); G06Q 10/08 (20120101); G06F 8/70 (20180101); G06F 3/0484 (20130101); G06K 9/00 (20060101); G06F 8/20 (20180101); G06K 9/62 (20060101); G06Q 50/20 (20120101);