US8006176B2ExpiredUtilityPatentIndex 92
Methods and systems for imaging-device-based form field management
Est. expiryOct 8, 2024(expired)· nominal 20-yr term from priority
G03G 15/5087H04N 1/32561H04N 2201/0049H04N 1/00389H04N 2201/3278H04N 2201/0094H04N 1/00503G06K 15/00H04N 2201/0074H04N 1/00411H04N 2201/001G06K 15/005H04N 1/00384H04N 1/00464H04N 1/32117H04N 1/00973G06F 21/41H04N 1/00498G06F 21/84H04N 1/00244H04N 2201/3221G03G 15/502H04N 2201/0075H04N 1/00352H04N 2201/0039H04N 2201/3242G06F 40/174G03G 2215/00109H04N 1/00278H04N 2201/0013H04N 1/00204G03G 15/5091
92
PatentIndex Score
20
Cited by
748
References
12
Claims
Abstract
Aspects of the present invention relate to systems, methods and devices for modifying and managing form documents with an application that receives input from an imaging device user interface and from other sources. Some aspects relate to a input field definition file that is transmitted to the imaging device and which comprises display parameters and UI options for prompting a user for field input and as well as instructions for obtaining field data from other sources.
Claims
exact text as granted — not AI-modified1. A method for imaging device remote document modification, said method comprising:
sending remote form file menu data and imaging device (IDev) instructions from a remote computing device (RCD) to an IDev via an IDev device management application programming interface (API) residing on said IDev, wherein said remote file menu data and IDev instructions comprise display parameters for displaying said remote form file menu data on an IDev user interface (UI) display, wherein said IDev UI display is an integral part of said IDev;
receiving services from said device management API at said RCD, said services consisting of a device status message, a device configuration message comprising a list of installed options supported by said IDev, a web page setting function for retrieving and setting configurable values on web pages embedded on said IDev, a key operator program allowing said RCD to retrieve and set configurable values in hardware and software keys on said IDev, a job status function allowing said RCD to retrieve and reprioritize a current job queue, a click count function allowing said RCD to retrieve device counts and clicks for each function by account code and a data security setting function allowing said RCD to retrieve storage data information and initiate data clear functions;
receiving a form file request from said IDev device management API, wherein said form file request comprises user input received at said IDev UI in response to displaying said remote file menu data;
sending display content to said IDev device management API, said display content comprising a list of available forms;
receiving a form selection from said IDev device management API, wherein said form selection identifies a form and wherein said form selection is received in response to displaying said display content on said IDev UI display;
determining an input field definition file (IFDF) identified from said form selection, wherein said IFDF is a markup language file that comprises display parameters, field input menu content for obtaining user input for fields in said form and UI options for prompting a user for field input and wherein said IFDF also comprises instructions for obtaining field data from other sources;
sending field input menu data contained in said IFDF to said IDev device management API;
receiving a field data entry from said IDev device management API, wherein said field data entry comprises user input data received at said IDev UI in response to displaying said field input menu data from said IFDF;
appending said field data entry to a form file representing said form thereby creating a completed form; and
wherein said receiving, said sending, said determining and said appending are performed by an application residing on said IDev.
2. A method as described in claim 1 further comprising requesting file data from a remote resource where form files are stored.
3. A method as described in claim 1 wherein said display content is formatted in a markup language.
4. A method as described in claim 1 wherein said form field prompt is formatted in a markup language.
5. A method as described in claim 1 further comprising receiving a user identification and filtering said list of available forms based on said user identification.
6. A method as described in claim 1 wherein said form file is a printer-ready file and said field data entry is appended as a markup language tag.
7. A method for imaging device remote document modification, said method comprising:
sending remote form file menu data and imaging device (IDev) instructions to an IDev via an IDev device management application programming interface (API), wherein said remote form file menu data and IDev instructions comprise display parameters for displaying said remote form file menu data on an IDev user interface (UI) display, wherein said IDev UI display is an integral part of said IDev;
receiving services from said device management API at said RCD, said services consisting of a device status message, a device configuration message comprising a list of installed options supported by said IDev, a web page setting function for retrieving and setting configurable values on web pages embedded on said IDev, a key operator program allowing said RCD to retrieve and set configurable values in hardware and software keys on said IDev, a job status function allowing said RCD to retrieve and reprioritize a current job queue, a click count function allowing said RCD to retrieve device counts and clicks for each function by account code and a data security setting function allowing said RCD to retrieve storage data information and initiate data clear functions;
receiving a form request from said IDev device management API, wherein said form request comprises user input received at said IDev UI in response to displaying said remote file menu data;
requesting available form data from a remote resource;
receiving available form data from said remote resource;
formatting said available form data into a form selection prompt;
sending said form selection prompt to said IDev UI device management API;
receiving a form selection from said IDev device management API, wherein said form selection identifies a form;
requesting, from said remote resource, an input field definition file (IFDF) associated with said form designated in said form selection, wherein said IFDF is a markup language file that comprises display parameters, field input menu data for fields in said form and UI options for prompting a user for field input and wherein said IFDF also comprises instructions for obtaining field data from other sources;
receiving, from said remote resource, said IFDF associated with said form;
sending said IFDF to said IDev device management API;
receiving a field data entry in response to said IFDF from said IDev device management API, wherein said field data entry comprises user input data received at said IDev UI in response to displaying said field input menu data in said IFDF;
appending said field data entry to a form file representing said form thereby creating a completed form;
sending said completed form to a printing device; and
wherein said receiving, said requesting, said sending, said formatting and said appending are performed by an application residing on said IDev.
8. A method as described in claim 7 wherein said form selection prompt is formatted in a markup language.
9. A method as described in claim 7 wherein said data entry prompt is formatted in a markup language.
10. A method as described in claim 7 further comprising receiving a user identification and filtering said available form data based on said user identification.
11. A method as described in claim 7 wherein said form file is a printer-ready file and said field data entry is appended as a markup language tag.
12. A method as described in claim 7 wherein said sending said completed form to a printing device comprises sending said completed form to a direct print utility.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.