Patent Grant
8156424
Embodiments of the present invention comprise methods and systems for imaging device dynamic document creation and organization.
Imaging devices such as printers, copiers, scanners and fax machines can have a wide array of functions and capabilities to fit specific uses or combinations of uses. Imaging devices often take the form of a multi-function peripheral device (MFP) that combines the functions of two or more of the traditionally separated imaging devices. An MFP may combine any number of imaging devices, but typically comprises the functions of a printer, scanner, copier and fax machine.
Some imaging devices may comprise computing resources for data storage and processing such as processors, hard disk drives, memory and other devices. As imaging devices add more features and functions, they become more costly and complex.
More complex imaging devices and MFPs may comprise network connectivity to provide communication with other computing devices, such as personal computers, other imaging devices, network servers and other apparatus. This connectivity allows the imaging device to utilize off-board resources that are available on a connected network.
Imaging devices typically have a user input panel with an array of buttons, knobs and other user input devices. Some devices also have a display panel, which can be for display only or can be a touch panel display that enables user input directly on the display.
Devices with touch panel displays or displays with buttons arranged in cooperation with the display can display menu data that may be selected by user input. This menu data is typically driven by an on-board server module within the imaging device.
Embodiments of the present invention comprise systems and methods for creating, organizing and editing dynamic documents through the use of an imaging device user interface.
Embodiments of the present invention comprise systems, methods and devices for interacting with a remote computing device from an imaging device. These embodiments comprise remote computing devices configured to communicate with imaging devices, imaging devices configured to communicate with remote computing devices and systems comprising various combinations of remote computing devices in communication with imaging devices.
The foregoing and other objectives, features, and advantages of the invention will be more readily understood upon consideration of the following detailed description of the invention taken in conjunction with the accompanying drawings.
Embodiments of the present invention will be best understood by reference to the drawings, wherein like parts are designated by like numerals throughout. The figures listed above are expressly incorporated as part of this detailed description.
It will be readily understood that the components of the present invention, as generally described and illustrated in the figures herein, could be arranged and designed in a wide variety of different configurations. Thus, the following more detailed description of the embodiments of the methods and systems of the present invention is not intended to limit the scope of the invention but it is merely representative of the presently preferred embodiments of the invention.
Elements of embodiments of the present invention may be embodied in hardware, firmware and/or software. While exemplary embodiments revealed herein may only describe one of these forms, it is to be understood that one skilled in the art would be able to effectuate these elements in any of these forms while resting within the scope of the present invention.
Embodiments of the present invention comprise interfaces and architecture that integrate imaging devices with remote computing device applications and environments to provide solutions that may not be possible solely with an imaging device alone. Some embodiments comprise an infrastructure and set of interfaces that allow applications on a network to programmatically control imaging device functions and interact with a user through an imaging device input panel. Software functions that are not practical within the imaging device can be performed on the server but are accessible from the imaging device.
For the purposes of this specification and claims, an imaging device (IDev) may be described as a device that performs an imaging function. Imaging functions comprise scanning, printing, copying, image transmission (sending and receiving), image conversion and other functions. Exemplary imaging devices comprise printers, copiers, facsimile machines, scanners, computing devices that transmit, convert or process images and other devices. An IDev may also perform multiple imaging functions. For example, and not by way of limitation, a multi-function peripheral device (MFP), which typically has the capability to perform a plurality of functions comprising a printer, scanner, copier and/or a facsimile machine or image transmitter/receiver, is a type of imaging device. Other MFP imaging devices may comprise other combinations of functions and still qualify as an IDev.
For the purposes of this specification and claims, a remote computing device (RCD) is a device capable of processing data and communicating with other devices through a communications link. An RCD is a remote device because it requires a communications link, such as a network connection, a telephone line, a serial cable or some other wired or wireless link to communicate with other devices such as an imaging device. Some exemplary RCDs are network servers, networked computers and other processing and storage devices that have communications links.
Some embodiments of the present invention may be described with reference to
These embodiments further comprise a remote computing device (RCD) 6 that is linked to the imaging device 4 via a communications link 10, such as a network connection. This network connection may be a typical wired connection or a wireless link.
Embodiments of the present invention may provide menu data from the RCD 6 to the imaging device UI panel 2 or remote panel 8 via the network connection 10. Once this menu data is fed to the imaging device 4, an UI panel 2, 8 on the imaging device 4 may be used to interact with applications that run on the remote computing device 6. User input received from UI panels 2, 8 may be returned directly to the remote computing device 6.
A Web Service is a software application identified by a Uniform Resource Identifier (URI), whose interfaces and binding are capable of being defined, described and discovered by Extensible Markup Language (XML) artifacts and supports direct interactions with other software applications using XML based messages via Internet-based protocols.
An application on the remote computing device 6 may use one or more Web Services to control various features in the imaging device 4, such as enabling, disabling or setting device values or controlling device functions.
Embodiments of the present invention allow network applications running on remote computing devices to interact with the user of the imaging device through the imaging device I/O panel. These embodiments allow imaging device user interface (UI) control (i.e., touch panel, button/display) by applications. Some embodiments may also integrate custom display screens or menus with the native imaging device UI. Embodiments may hand off control of imaging device functions between standard operation modes performed on the imaging device in response to user input to an imaging device UI and open systems modes that utilize network resources, such as applications on RCDs, through user input at the imaging device UI.
Embodiments of the present invention comprise network-based applications that have full control over the imaging device UI to display text and graphics in any format. In these embodiments, the application can programmatically display buttons, textboxes, graphics, etc. in any layout desired.
In some embodiments, the UI layout is easy to program using a standard language, such as a markup language. These languages comprise Hypertext Markup Language (HTML), Extensible Markup Language (XML), Wireless Markup Language (WML), Extensible Hypertext Markup Language (XHTML) and other languages.
In some embodiments of the present invention a remote computing device application or server application is able to request a keyboard UI to be displayed on the imaging device display 13, 8. In some embodiments, this functionality is available on the imaging device and does not need to be recreated by remote computing device applications. In some embodiments, the remote computing device may define the keyboard prompt and default values. These embodiments may comprise a remote computing device that is able to rename imaging device UI buttons, such as the OK and Cancel buttons as well as define additional buttons.
In some embodiments, menu templates may be served to the imaging device UI by the imaging device itself 4 or from a remote computing device 6.
External Authorization Application
Some embodiments of the present invention may comprise a remote computing device application that is registered as the External Authorization server. The External Authorization application may control access to the imaging device and may have top-level control of the UI. UI control may be given to this application in the same manner that control is given to an internal auditor.
In these embodiments, when an imaging device system boots, it checks to see if an External Authorization application is registered. If so, the imaging device is placed in disabled mode and the application is contacted to take control of the UI. If the External Authorization server is not available, an error message may be displayed and the device may remain disabled. The imaging device may periodically try to contact the External Authorization server until it is available. Table 1 below describes what entity has control of the UI, in an exemplary embodiment, when the device is in a disabled state.
Remote Computing Device Applications
In embodiments of the present invention, access to the custom UI panels of imaging devices may vary from application to application. Some solutions, such as Document Management integration, may wish to leverage the native Image Send screens, but display some custom UI's to gather additional information about a scan job. Other solutions, like custom printing applications, may be accessed from a separate mode than the native functions.
In order to accommodate the diversified needs of these solutions applications, embodiments may support multiple integration points for UI control. These integration points are based on a user action (“trigger”) for which applications may register. In some embodiments, applications may be registered with target devices so that the device knows that when “trigger A” occurs on the front panel to contact “remote computing device B” for instructions. In exemplary embodiments, applications may be integrated with an imaging device at any of several “trigger” points.
Remote computing devices may be registered to a specific function and contacted when that function's hardware key is pressed (e.g. Image Send) on the imaging device UI. Any UI information provided by the remote computing device may be displayed instead of the standard function screens native to the imaging device. This trigger may be used for applications that wish to replace the existing functions with completely custom UI's, such as an alternative scan solution or a specialized display, such as a “Section 508” compatible screen or other specialized-need interface that may have large buttons or other accommodations.
In some embodiments, each function on the imaging device may have a menu on the touch screen that remote computing devices, such as servers, can register. This enables solutions applications to provide custom content and still use some of the standard functionality provided by the imaging device. When a button assigned to a custom application is selected, a menu will be displayed with the solutions registered to that function. Users may select the desired solution and the remote computing device will be contacted for instructions.
In some embodiments, a stand-alone RCD mode that provides remote computing device application access can be accessed from the job queue portion of the UI that is displayed on every screen. This trigger point may be used for applications that do not fit within one of the standard device functions, such as custom printing solutions on an imaging device. When the RCD menu is selected, a menu will be displayed with the solutions applications registered to the generic RCD mode. Users will select the desired solution and the remote computing device will be contacted for instructions.
Hardware Key Interaction
In some embodiments of the present invention, when an imaging device is enabled, additional hardware keys may be used to manage the device. Hardware key assignments for an exemplary embodiment are shown in table 2.
In some embodiments, in addition to the * key for logout, a timeout period may be implemented. Some embodiments also comprise an auto clear setting that can be configured for a given period of time, such as 10 to 240 seconds (or disabled). In these embodiments, when there is no activity for the time configured in auto clear, the device may automatically return to disabled mode and attempt to contact a remote computing device to retake control of the UI.
Error & Jam Notifications
Depending on a particular solution, a remote computing device application may have full or only partial control of the imaging device UI and a particular imaging job. In some embodiments, partial control may include cases where a remote computing device is monitoring clicks, but native modes are responsible for the UI interaction and controlling the job. Partial control may also include cases where the remote computing device application is integrated with a native mode (UI trigger=function custom menu). In these embodiments, the imaging device may handle all error and jam notifications with only a notification sent to the relevant remote computing device application.
For some embodiments, in cases where the remote computing device application has full control over the UI and the job, error and jam notifications may be handled differently depending on the type of error. For recoverable errors, a notification may be sent to the remote computing device application and the application may be responsible for displaying messages and resolving the error. For non-recoverable errors, the imaging device and RCD mode may interact to gracefully handle the error condition (e.g. provide user with instructions for clearing jam).
Control Handoffs
In some embodiments, at different points throughout an imaging job, several applications may need control over an imaging device including, but not limited to, an External Authorization application, a standard RCD application, an imaging device native mode and other applications. The following section describes, for an exemplary embodiment, the various steps in an exemplary job, the entities that may have control during each step, and what type of control may be allowed.
Step 1: User provides credentials to access the device at the device UI. This step may be controlled by a remote computing device, such as an External Authorization application or by Internal Accounting (native mode) in the imaging device itself. At the end of this step, the device is enabled. The External Authorization application may also specify default parameters or disable specific job parameters (e.g. default file format is PDF, but user may change; color mode is set to B/W and user may not change).
Step 2: User sets parameters for the job using one of the native imaging device modes or a standard RCD application. At the end of this step the user makes an input to initiate the job. When the input is made, an optional notification may be sent to the standard RCD application, which can then change job parameters if desired. An e-mail application is one example of an application that may request notification when the user input is made. A user may use native Image Send screens or other input to select scan options and choose e-mail recipients. A user may then select a custom application button and choose the scan-to-e-mail option from the menu. The e-mail application may then display custom screens for the user to set permissions for the file. Once a user places the original document(s) on the scanner and initiates the process, the e-mail application may capture the destination parameters set by the user and change the target destination to the e-mail application FTP server. The e-mail application may then receive the file, apply the appropriate permissions, and send to the e-mail recipients selected by the user. A remote computing device application may also want to retake control of the UI at this point, if, as in some embodiments, the application generates thumbnails of the scanned images and displays them to the user for verification.
Step 3: Once the job is initiated, the imaging device is responsible for scanning or RIPing the job and spooling it to the HDD. If the imaging device is configured to authorize jobs with an external authorization application, it may send a click report to the application and wait for instructions. The external authorization application may enable the job for sending/printing, cancel the job, or change job parameters (and then enable). As an example, a rules-based printing application may wish to change job parameters after it receives a click report. Some rules-based printing applications support rules-based printing and scanning that can limit what each user is allowed to do based on the time of day, the destination, or many other parameters. For example, only users in the marketing group may be able to scan high-quality color images. If a user from another group selects color and 600 dpi, a rules-based application may change the parameters to color and 200 dpi. At the end of this step the job should either be authorized or canceled.
Step 4: In some embodiments, this may be an optional step, where the standard RCD application in step 2 may have specified the destination as a HDD for temporary storage. This step may also be used, in some embodiments, by a Java application running on the imaging device. For example, a government office may have a custom encryption application running on the device that takes the scanned document, encrypts it, and then requests the imaging device to send it to the target destination selected by the user in step 2. In some embodiments, it may be beneficial to send a notification to the external authorization application after this step—because the imaging device does not know how long the file will be on the HDD or what the application is going to do with it—and after the send/print step.
Step 5: In the final step, the file is actually output. In typical embodiments, the file is either sent over the network or printed locally. At the end of this step, a notification that the job was successfully completed should be sent to the external authorization application and optionally, to the standard RCD application.
Device Control and Management API's
The API's may be used to allow a remote computing device application to control access to an imaging device for vend applications and to manage the device from a remote location.
Device Control and Vend API
In some embodiments of the present invention, a Device Control and Vend API allows applications to enable and disable access to the device and track click counts. The Device Control and Vend API may provide an RCD with the following controls:
Enable/disable device of function—this may allow an RCD to enable or disable access to the device as a whole or by function to enforce individual user privileges. In some exemplary embodiments, the functions listed in Table 3 may be selectively enabled or disabled by an application.
Report clicks used—at the end of a successful job, the clicks used may be reported back to an RCD including:
Debit mode—in these embodiments, when an application enables the device it may specify if the current job requires authorization. If so, the job will be spooled to memory and click information (e.g., as defined in Table 4) will be sent to an RCD. An RCD will then notify the device if the job should be deleted or output/sent. At this point, the application also has the option of changing job parameters. If the application does not require authorization, the job will continue as normal and a click report will be sent at the end of the job.
Print job accounting—in these embodiments, an RCD may wish to monitor print jobs along with walk-up functions. For print job accounting, an IDev may monitor all incoming print jobs and send accounting data in the PJL header to an RCD for verification before printing the job. The RCD will evaluate the accounting data (or lack thereof) and inform the IDev to continue with or cancel the job.
Report on unidentified jobs—in these embodiments, an RCD may also wish to monitor print jobs that it cannot associate to a specific user, such as device reports and incoming fax jobs. The RCD can register to receive click counts for all unidentified jobs, so that it may bill them to a general account.
Device Management API
In some embodiments of the present invention, a Device Management API allows a network application to remotely setup and manage the imaging device. In exemplary embodiments, the Device Management API may provide an RCD with the following controls:
The above groupings are provided only as an exemplary embodiment detailing which settings should be included. In some embodiments, actual API's should be grouped by functional areas since there may be overlap between Key Operator settings and web page settings.
Internal Accounting API
In some embodiments, an Internal Accounting API may allow a remote computing device application to configure internal accounting and report click counts. In some exemplary embodiments an Internal Accounting API may include:
Some embodiments of the present invention may comprise a Font and Form Management API, which allows an RCD application to remotely download and manage fonts and forms in mass-storage. In some exemplary embodiments, a Font and Form Management API may provide a remote computing device with the following controls:
In some embodiments of the present invention, a Firmware Management API may allow a remote computing device or network application to remotely download and manage the imaging device firmware. In some exemplary embodiments, a Firmware Management API may provide a remote computing device (e.g., a server) with the following controls:
In some embodiments of the present invention, device function API's allow a remote computing device application to use existing imaging device functionality to provide new custom solutions.
Image Send API
In some embodiments, an Image Send API may provide the remote computing device application with the following controls:
In some embodiments, a remote computing device can change the default values on the imaging device or the values for the current job. For the current job, the remote computing device may also specify if scan parameters may be modified by the user or not. If one remote computing device application (e.g. Access Control) specifies that a parameter cannot be changed and then a second application (e.g. Document Management) tries to set the parameter, a notification may be sent to the second application and the setting will not be changed.
Print API
In some embodiments, print jobs may be submitted by remote computing device applications using standard printing channels. In some exemplary embodiments, a Print API may provide a remote computing device with the following additional control:
In some embodiments of the present invention, a Copy API may provide a remote computing device with the following exemplary controls:
In some embodiments, a remote computing device can change the default values on the imaging device or the values for the current job. For the current job, the remote computing device may also specify if copy parameters may be modified by the user or not.
Document Filing API
In some embodiments of the present invention, a Document Filing API may provide a remote computing device with the following exemplary controls:
Allowing external applications to control an imaging device opens up the imaging device to new security vulnerabilities. In embodiments of the present invention that provide some security measures, the following exemplary items are security concerns that may be addressed by the remote computing device interface.
Access to remote computing device interfaces may be limited to valid applications. Embodiments provide extensive access and control of the imaging device, which poses a significant security risk. The interface of these embodiments may be protected from access by attackers, while maintaining ease of setup and use for valid solutions.
Confidential data (user credentials and job data) may be protected during network transfer. User credentials and job data may be secured during network transfer to ensure that it cannot be stolen, an intruder cannot monitor device activity, and a man-in-the-middle attack cannot change messages. Imaging devices may support Secure Sockets Layer (SSL) and other connections to ensure data is safe while being communicated between the imaging device and remote computing device applications.
Administrators may have the ability to lock-down imaging device access. For users with strict security policies, administrators may have the ability to disable access by remote computing devices or limit access to specific applications. Administrators may have an option to register the limited applications that they wish to access the imaging device interfaces.
Remote computing device applications may ensure the imaging device is not being “spoofed.” The remote computing device may be able to authenticate an imaging device that it is contract with it to ensure an intruder cannot imitate the imaging device to collect network configuration and password information, monitor file/folder structures of a document management system, or spoof security settings and DSK status of the imaging device.
A remote computing device may ensure that the server is not being “spoofed.” The imaging device must be able to authenticate all remote computing devices that it is in contact with to ensure that an intruder is not spoofing the remote computing device's IP address. By pretending to be the remote computing device, an intruder could steal user credentials, redirect scanned documents, change device settings or firmware, or bring down the access control system (either to provide access to unauthorized users or initiate a denial of service attack for valid users).
Access control/vend applications may not be compromised when a remote computing device is unavailable. When the remote computing device is unavailable, it may not be acceptable to provide open access to the device. If the remote computing device is unavailable at startup or becomes unavailable at anytime (e.g. someone disconnects network cable), the imaging device may immediately be disabled and an error message displayed.
An administrator may be able to adjust a security level based on company and application requirements. Security requirements can have a large impact on the time it takes to develop a remote computing device application and the resources required to implement the solution. Users using some embodiments may range from a small business with one imaging device, no IT staff, and a simple scan or print application to a large government office using access control and audit trails to track all device activity. The security measures used to protect imaging device interfaces may be adjustable by the administrator to match the target environment.
The imaging device and remote computing device applications may be able to hand-off user credentials. Users may be prompted to login at multiple points throughout a job. For example, an access control application or accounting application may control total device access, the imaging device may have user authentication enabled for Image Send, and a document management application may require user login before showing a folder list. In many environments, all of these applications will use a common user database. In some embodiments, it is, therefore, desirable for the applications to pass user credentials to each other, so that each one does not have to repeat the authentication process.
Some embodiments of the present invention may be described with reference to
Imaging device 30 will typically be capable of performing one or more imaging functions including, but not limited to, scanning, printing, copying, facsimile transmission (sending and receiving) and others.
These embodiments further comprise a communications link 38, which may be a wired connection (as shown in
The operation of some imaging device embodiments may be explained with reference to
Imaging devices of these embodiments are further configured to accept input from a user in response to a display of remote menu data and communicate 44 that user input to a remote computing device. In some embodiments, this user input data will be processed by a remote computing device. This may comprise running an application on the remote computing device. This processing may also comprise accessing and communicating data that is stored on the remote computing device.
The imaging devices of these embodiments are further configured to receive 46 data resulting from processing the user input data. This may comprise data generated by an application running on the remote computing device in response to the user input. The imaging device may also receive data that was stored on a remote computing device, such as a file server, in response to processing the user input.
Once the imaging device 30 has received 46 the processed data, the imaging device 30 may perform 48 a native function in response to the data or using the data. For example, and not be way of limitation, the imaging device 30 may print a document that was stored on the remote computing device and modified on the remote computing device according to the user input. As another non-limiting example, the imaging device 30 may active or enable functions (i.e., scanning, copying, printing, fax transmission) on the imaging device in response to the receipt 46 of processed data.
Some, more specific, imaging device embodiments may be explained with reference to
Once the menu data is received 50, it may be displayed 52 on the imaging device user interface display 36. As in previously described embodiments, the menu data is typically intended to prompt user input on imaging device user interface 32. Display 52 of the remotely-stored menu data may be accomplished with a browser application that is native to the imaging device 30.
In these embodiments, the imaging device 30 is further configured to route 54 user input received though its user interface 32 to a remote computing device. The remote computing device that receives the user input may then run an application or otherwise process the user input and return the results of the processing the imaging device 30. Accordingly, the imaging device 30 is further configured to receive 58 processed data from a remote computing device. In some embodiments, the imaging device 30 may perform one or more functions in response to the receipt 58 of processed data.
Some embodiments of the present invention may be explained with reference to
Embodiments of RCD 60 may be further described with reference to
In some embodiments, described with reference to
An RCD 60, of some embodiments, will be further configured to receive 84 user input obtained through the user interface 32 of an imaging device 30 and transferred to the RCD 60 over communications links 38 & 64. Once this input data is received at an RCD 60, the input data may be processed 86. This processing 86 may comprise conversion of the data to a new format, execution of commands contained within the data or some other process. Once the input data has been processed 86, the processed output may be sent 88 back to the imaging device 30 where the processed output may be used in an imaging device process or function.
In some embodiments, as described with reference to
Some embodiments of the present invention may be described with reference to
In these embodiments, menu data is stored on RCD 60 and sent 110 to at least one of the imaging devices 30a-30d where the menu data is displayed on a user interface. Any of Imaging devices 30a-30d that receive the menu data are configured to accept 112 and transmit 114 user input to an RCD 60. Once the user input data is received at the RCD, the data may be processed 116 as discussed in previously described embodiments. The result of processing 116 may then be sent 118 back to any combination of the imaging devices 30a-30d.
In these embodiments, a single RCD 60 may be used to provide processing power, resources and functionality to a plurality of imaging devices 30a-30d without reproducing these resources in each imaging device. In some embodiments, data generated by input on one imaging device 30a may be directed to another imaging device 30d for processed data output or final processing.
Dynamic Document Creation Embodiments
Some embodiments of the present invention may comprise an imaging device (IDev) with internal processing capabilities. Other embodiments may comprise an imaging device (IDev) in communication with one or more remote computing devices (RCDs) on which processing may be performed.
Some embodiments of the present invention may be described with reference to
In an exemplary embodiment of a dynamic document creation and editing application, a user, through the use of an imaging device (IDev) user interface (UI), may select a document format, such as a business letter, invoice, vacation request or some other document format. A document format may comprise one or more parameters for defining a page size, page orientation, single-sided, double-sided, margins, headers, footers, columns, text boxes, graphics boxes and other formatting options. In some embodiments, a document format may comprise a predefined template.
A user, through the IDev UI, may also define a dynamic field structure for a dynamic document. A dynamic field structure may comprise one or more data fields for text, numerical data, graphics, images or other field types.
A dynamic field structure may also comprise field display characteristics. Field display characteristics may comprise a field size, field shape, field color, field background color field shading, font size, field rotation, field orientation and other characteristics that affect the way field content is displayed on a display screen or output to media. In an exemplary embodiment comprising a company advertisement flyer, dynamic field display characteristics may comprise a text color, background color, text font size, text orientation and other characteristics.
A dynamic field structure may also comprise a field relationship. A filed relationship may comprise a relationship between field content and the content of another field or a relationship between field content and other data. A field relationship may comprise a geographical relationship, a mathematical relationship, a logical relationship, such as with Boolean logic, or another relationship. In an exemplary embodiment comprising a purchase order form, a field relationship may comprise a mathematical relationship for a total amount field that is a summation of the column above that field.
In addition to a document format and a dynamic field structure, a dynamic document may comprise static content. A user may specify static content, such as text, graphics, images, or other content that remain in a static state on the document. In an exemplary embodiment comprising a company letter, static content may comprise a company logo and/or text denoting the company name. This static content will remain constant when other field content may vary, such as an addressee field or a signature block field.
Some embodiments of the present invention may be described with reference to
A user may also define dynamic field structures for a document. These dynamic field structures may comprise one or more fields that may be populated with many types of information that may be linked or related to the field with a field relationship, such as a link to a remote site or a mathematical relationship to another field. A field structure typically comprises field types, field display characteristics and field relationships. In the exemplary business letter embodiment 130A shown in
In addition to a document format and a document field structure, a user may also designate document static content. This static content may include graphics, such as a company logo 131A or images and text such as a company letterhead 141A or 132A. Static content may also include column headings 148A, numbers and other data that is intended to be communicated by each instance of the document.
Once these three document elements have been defined, they may be compiled into a dynamic document that may automatically populate its fields when it is selected and generated by a user at an imaging device. In some embodiments, the fields may be linked or related to user data once the user is identified through a login process or another identification process.
In another exemplary embodiment 140A, illustrated in
In some embodiments of the present invention, as illustrated in
A user may also define 143 a dynamic field structure. This dynamic field structure may comprise one or more fields that may be populated with data. Fields may be populated with user input at the IDev UI 124. Fields may also be populated by automated processes that access information stored on the IDev, an RCD or some other resource in communication with the IDev. Some fields may be populated at the time of dynamic document creation. Fields may also be populated when a document is generated for output, such as for printing or transmission to a recipient. Fields may comprise many types of information. Some types comprise text, numerical data, graphics, images and other types.
A user may also designate 144 document static content. This static content may comprise text, graphics, images, symbols, numbers and other data that is intended to be communicated by each instance of the document. Document static content does not change with any document variable. Once these elements are defined, a combination of the document format, dynamic field structure and static content may be formed into a dynamic document. The application that combines these elements into a dynamic document may reside on the IDev or may reside on a remote computing device (RCD). The dynamic document may then be saved 147 at any location accessible to the IDev.
Further embodiments of the present invention may be described with reference to
In some embodiments of the present invention, the RCD may then send 156 a dynamic field structure menu to the IDev. This dynamic field structure menu may be formatted as a hypertext language document, such as an XML document. The IDev may then display 157 the dynamic field structure menu. This menu may be displayed through a web browser as described above in the document format menu. In response to this menu display, a user may input a selection through the IDev UI. The IDev may receive 158 this selection and then send 159 the dynamic field structure menu selection to the RCD.
In some embodiments, the RCD may respond to the receipt of the dynamic field structure menu selection data by sending 160 a static content menu to the IDev. The IDev may then display 161 the static content menu in a manner similar to that described for other embodiments. When a user responds, the IDev may accept 162 a user selection of the static content menu and send 163 the static content menu selection to the RCD.
The RCD may then compile 164 the document format, the dynamic field structure and the static content into a dynamic document. The dynamic document may then be saved 165 at the IDev, the RDC or some other location.
Some embodiments of the present invention comprise associating dynamic document editor application options with user specific data. In these embodiments, a user is identified through the IDev. Data linked to the user may then be accessed by the IDev or a device in communication with the IDev. This user-specific data may be linked or otherwise related to the document field structure. A document field may relate user-specific data that is stored on a resource accessible to the IDev or RCD. In some embodiments, a user's personal information may be related to fields in a dynamic document. A user's name, address, social security number, bank account data and/or other information may be related to dynamic document fields so that these fields are automatically populated with personal data when a user selects a defined dynamic document. Security measures may be implemented when a user logs onto the application.
Some embodiments, illustrated in
Some embodiments of the present invention may further comprise sending 176 a dynamic field structure menu, which may comprise user specific data, to the IDev from an RCD. The IDev may then display 177 the dynamic field structure menu and accept 178 a user selection of the menu. The IDev may then send 179 the dynamic field structure menu selection to the RCD.
Some embodiments of the present invention may further comprise sending 180 a static content menu, which may comprise user specific data, to the IDev from an RCD. The IDev may then display 181 the static content menu and accept 182 a user selection of the menu. The IDev may then send 183 the static content menu selection to the RCD. The RCD may then compile 184 a dynamic document comprising data from the document format menu selection, the field structure menu selection and the static content menu selection. The dynamic document may then be saved 185 at the RDC, the IDev or some other location.
Further embodiments of the present invention may be described with reference to
Further embodiments of the present invention, as illustrated in
The IDev may then receive 206 a dynamic field structure menu from the RCD and may then display 207 the dynamic field structure menu. The IDev may then accept 208 a user selection in response to the dynamic field structure menu and send 209 the user selection to the RCD. The IDev may then receive 210 a static content menu from the RCD and may then display 211 the static content menu. The IDev may then accept 212 a user selection in response to the static content menu and send 213 the user selection to the RCD.
Further embodiments of the present invention may be described with reference to
The IDev may then receive 227 a dynamic field structure menu from the RCD. This menu may also comprise user specific data correlated to the identified user. The IDev may then display 228 the dynamic field structure menu. The IDev may then accept 229 a user selection in response to the dynamic field structure menu and send 230 the user selection to the RCD. The IDev may then receive 231 a static content menu from the RCD. Again, this menu may comprise user-specific data correlated to the identified user. The IDev may then display 232 the static content menu. The IDev may then accept 233 a user selection in response to the static content menu and send 234 the user selection to the RCD. The dynamic document editor application may then take this selection data transmitted from the IDev and compile a dynamic document.
Further embodiments of the present invention may be described with reference to
Further embodiments of the present invention may be described with reference to
The terms and expressions which have been employed in the forgoing specification are used therein as terms of description and not of limitation, and there is no intention in the use of such terms and expressions of excluding equivalence of the features shown and described or portions thereof, it being recognized that the scope of the invention is defined and limited only by the claims which follow.
This application is a continuation-in-part of U.S. patent application Ser. No. 10/962,248, entitled “Methods and Systems for Imaging Device Remote Application Interaction,” filed on Oct. 8, 2004; this application is also a continuation-in-part of U.S. patent application Ser. No. 10/961,793, entitled “Methods and Systems for Imaging Device Remote Form Management,” filed on Oct. 8, 2004; this application is also a continuation-in-part of U.S. patent application Ser. No. 10/961,911, entitled “Methods and Systems for Imaging Device Remote Location Functions,” filed on Oct. 8, 2004; this application is also a continuation-in-part of U.S. patent application Ser. No. 10/961,594, entitled “Methods and Systems for Imaging Device Remote document Management,” filed on Oct. 8, 2004; and this application is also a continuation-in-part of U.S. patent application Ser. No. 10/962,103, entitled “Methods and Systems for Imaging Device Document Translation,” filed on Oct. 8, 2004; this application also claims the benefit of U.S. Provisional Patent Application No. 60/704,066, entitled “Methods and Systems for Imaging Device Applications,” filed Jul. 28, 2005.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5085587 | DesForges et al. | Feb 1992 | A |
| 5228100 | Takeda et al. | Jul 1993 | A |
| 5323393 | Barrett et al. | Jun 1994 | A |
| 5365494 | Lynch | Nov 1994 | A |
| 5410646 | Tondevoid et al. | Apr 1995 | A |
| 5504589 | Montague et al. | Apr 1996 | A |
| 5513112 | Herring et al. | Apr 1996 | A |
| 5542031 | Douglass et al. | Jul 1996 | A |
| 5586260 | Hu | Dec 1996 | A |
| 5659845 | Krist et al. | Aug 1997 | A |
| 5671412 | Christiano | Sep 1997 | A |
| 5699493 | Davidson et al. | Dec 1997 | A |
| 5699494 | Colbert et al. | Dec 1997 | A |
| 5717439 | Levine et al. | Feb 1998 | A |
| 5726883 | Levine et al. | Mar 1998 | A |
| 5727082 | Sugishima | Mar 1998 | A |
| 5727135 | Webb et al. | Mar 1998 | A |
| 5745883 | Krist et al. | Apr 1998 | A |
| 5760775 | Sklut et al. | Jun 1998 | A |
| 5774678 | Motoyama | Jun 1998 | A |
| 5791790 | Bender et al. | Aug 1998 | A |
| 5796934 | Bhanot et al. | Aug 1998 | A |
| 5799206 | Kitagawa et al. | Aug 1998 | A |
| 5799289 | Fukushima et al. | Aug 1998 | A |
| 5812818 | Adler et al. | Sep 1998 | A |
| 5832264 | Hart et al. | Nov 1998 | A |
| 5848231 | Teitelbaum et al. | Dec 1998 | A |
| 5877776 | Beaman et al. | Mar 1999 | A |
| 5944824 | He | Aug 1999 | A |
| 5956487 | Venkatraman et al. | Sep 1999 | A |
| 5956698 | Lacheze et al. | Sep 1999 | A |
| 5968127 | Kawabe et al. | Oct 1999 | A |
| 5993088 | Nogay et al. | Nov 1999 | A |
| 5995553 | Crandall et al. | Nov 1999 | A |
| 5999708 | Kajita | Dec 1999 | A |
| 6042384 | Loiacono | Mar 2000 | A |
| 6044382 | Martino | Mar 2000 | A |
| 6069706 | Kajita | May 2000 | A |
| 6075860 | Ketcham | Jun 2000 | A |
| 6115132 | Nakatsuma et al. | Sep 2000 | A |
| 6118546 | Sanchez et al. | Sep 2000 | A |
| 6128731 | Zarrin et al. | Oct 2000 | A |
| 6141662 | Jeyachandran | Oct 2000 | A |
| 6148346 | Hanson | Nov 2000 | A |
| 6161139 | Win et al. | Dec 2000 | A |
| 6178308 | Bobrow et al. | Jan 2001 | B1 |
| 6199080 | Nielsen | Mar 2001 | B1 |
| 6213652 | Suzuki et al. | Apr 2001 | B1 |
| 6216113 | Aikens et al. | Apr 2001 | B1 |
| 6233409 | Haines et al. | May 2001 | B1 |
| 6240456 | Teng et al. | May 2001 | B1 |
| 6246487 | Kobayashi et al. | Jun 2001 | B1 |
| 6292267 | Mori et al. | Sep 2001 | B1 |
| 6301016 | Matsueda et al. | Oct 2001 | B1 |
| 6307640 | Motegi | Oct 2001 | B1 |
| 6311040 | Kucinski et al. | Oct 2001 | B1 |
| 6353878 | Dunham | Mar 2002 | B1 |
| 6369905 | Mitsuhashi et al. | Apr 2002 | B1 |
| 6407820 | Hansen et al. | Jun 2002 | B1 |
| 6426798 | Yeung | Jul 2002 | B1 |
| 6433883 | Kajita | Aug 2002 | B1 |
| 6438589 | Iwata | Aug 2002 | B1 |
| 6462756 | Hansen et al. | Oct 2002 | B1 |
| 6476926 | Yano et al. | Nov 2002 | B1 |
| 6490601 | Markus et al. | Dec 2002 | B1 |
| 6509974 | Hansen | Jan 2003 | B1 |
| 6510466 | Cox et al. | Jan 2003 | B1 |
| 6516157 | Maruta et al. | Feb 2003 | B1 |
| 6526258 | Bejar et al. | Feb 2003 | B2 |
| 6567179 | Sato et al. | May 2003 | B1 |
| 6590589 | Sluiman et al. | Jul 2003 | B1 |
| 6590673 | Kadowaki | Jul 2003 | B2 |
| 6592275 | Aihara et al. | Jul 2003 | B1 |
| 6597469 | Kuroyanagi | Jul 2003 | B1 |
| 6604157 | Brusky et al. | Aug 2003 | B1 |
| 6621422 | Rubenstein | Sep 2003 | B2 |
| 6636929 | Frantz et al. | Oct 2003 | B1 |
| 6643650 | Slaughter et al. | Nov 2003 | B1 |
| 6652169 | Parry | Nov 2003 | B2 |
| 6685637 | Rom | Feb 2004 | B1 |
| 6707466 | Van Sickle et al. | Mar 2004 | B1 |
| 6721286 | Williams et al. | Apr 2004 | B1 |
| 6735773 | Trinh et al. | May 2004 | B1 |
| 6749434 | Stuppy | Jun 2004 | B2 |
| 6772945 | Mahoney et al. | Aug 2004 | B2 |
| 6775729 | Matsuo et al. | Aug 2004 | B1 |
| 6823225 | Sass | Nov 2004 | B1 |
| 6826727 | Mohr et al. | Nov 2004 | B1 |
| 6836623 | Imai | Dec 2004 | B2 |
| 6836845 | Lennie et al. | Dec 2004 | B1 |
| 6850252 | Hoffberg | Feb 2005 | B1 |
| 6854839 | Collier et al. | Feb 2005 | B2 |
| 6862110 | Harrington | Mar 2005 | B2 |
| 6862583 | Mazzagatte et al. | Mar 2005 | B1 |
| 6873429 | Matsuura | Mar 2005 | B2 |
| 6874010 | Sargent | Mar 2005 | B1 |
| 6904412 | Broadbent et al. | Jun 2005 | B1 |
| 6915525 | Ozawa | Jul 2005 | B2 |
| 6934706 | Mancuso et al. | Aug 2005 | B1 |
| 6934740 | Lawande et al. | Aug 2005 | B1 |
| 6940532 | Fukui et al. | Sep 2005 | B1 |
| 6948175 | Fong et al. | Sep 2005 | B1 |
| 6951303 | Peterson et al. | Oct 2005 | B2 |
| 6975820 | Wong | Dec 2005 | B2 |
| 6999987 | Billingsley et al. | Feb 2006 | B1 |
| 7003723 | Kremer et al. | Feb 2006 | B1 |
| 7007026 | Wilkinson et al. | Feb 2006 | B2 |
| 7012706 | Hansen | Mar 2006 | B1 |
| 7013289 | Horn et al. | Mar 2006 | B2 |
| 7019753 | Rappaport et al. | Mar 2006 | B2 |
| 7034958 | Hara | Apr 2006 | B1 |
| 7072057 | Hansen | Jul 2006 | B1 |
| 7079143 | Gilbert | Jul 2006 | B2 |
| 7095513 | Stringham | Aug 2006 | B2 |
| 7107615 | Cossel et al. | Sep 2006 | B2 |
| 7124097 | Claremont et al. | Oct 2006 | B2 |
| 7126717 | Jeyachandran et al. | Oct 2006 | B2 |
| 7127700 | Large | Oct 2006 | B2 |
| 7136909 | Balasuriya | Nov 2006 | B2 |
| 7136941 | Nguyen et al. | Nov 2006 | B2 |
| 7143364 | Tam | Nov 2006 | B1 |
| 7145673 | Lin | Dec 2006 | B1 |
| 7145686 | Simpson et al. | Dec 2006 | B2 |
| 7149697 | Zerza et al. | Dec 2006 | B2 |
| 7149964 | Cottrille et al. | Dec 2006 | B1 |
| 7162103 | Meunier et al. | Jan 2007 | B2 |
| 7170618 | Fujitani et al. | Jan 2007 | B2 |
| 7174056 | Silverbrook et al. | Feb 2007 | B2 |
| 7177814 | Gong et al. | Feb 2007 | B2 |
| 7181017 | Nagel et al. | Feb 2007 | B1 |
| 7181442 | Yeh et al. | Feb 2007 | B2 |
| 7185078 | Pleyer et al. | Feb 2007 | B2 |
| 7188125 | Karr | Mar 2007 | B1 |
| 7188181 | Squier et al. | Mar 2007 | B1 |
| 7191391 | Takashima | Mar 2007 | B2 |
| 7197615 | Arakawa et al. | Mar 2007 | B2 |
| 7203699 | Bellamy | Apr 2007 | B2 |
| 7212301 | Treibach-Heck et al. | May 2007 | B2 |
| 7216347 | Harrison et al. | May 2007 | B1 |
| 7233929 | Lingle et al. | Jun 2007 | B1 |
| 7239409 | Parry | Jul 2007 | B2 |
| 7249100 | Murto et al. | Jul 2007 | B2 |
| RE39808 | Motegi | Sep 2007 | E |
| 7268896 | Bellagamba et al. | Sep 2007 | B2 |
| 7272269 | Tojo et al. | Sep 2007 | B2 |
| 7275044 | Chauvin et al. | Sep 2007 | B2 |
| 7284061 | Matsubayashi et al. | Oct 2007 | B2 |
| 7284199 | Parasnis et al. | Oct 2007 | B2 |
| 7293034 | Paya et al. | Nov 2007 | B2 |
| 7296221 | Treibach-Heck et al. | Nov 2007 | B1 |
| 7301658 | Henry | Nov 2007 | B2 |
| 7305616 | Nelson et al. | Dec 2007 | B1 |
| 7321440 | Kimura | Jan 2008 | B2 |
| 7325196 | Covington et al. | Jan 2008 | B1 |
| 7327478 | Matsuda | Feb 2008 | B2 |
| 7328245 | Hull et al. | Feb 2008 | B1 |
| 7343551 | Bourdev | Mar 2008 | B1 |
| 7349949 | Connor et al. | Mar 2008 | B1 |
| 7363586 | Briggs et al. | Apr 2008 | B1 |
| 7404204 | Davenport et al. | Jul 2008 | B2 |
| 7406660 | Sikchi et al. | Jul 2008 | B1 |
| 7441188 | Russell et al. | Oct 2008 | B1 |
| 7444519 | Laferriere et al. | Oct 2008 | B2 |
| 7451117 | Cozianu et al. | Nov 2008 | B2 |
| 7451392 | Chalecki et al. | Nov 2008 | B1 |
| 7454623 | Hardt | Nov 2008 | B2 |
| 7467211 | Herman et al. | Dec 2008 | B1 |
| 7468805 | Lo et al. | Dec 2008 | B2 |
| 7496837 | Larcheveque et al. | Feb 2009 | B1 |
| 7500178 | O'Donnell | Mar 2009 | B1 |
| 7508535 | Hart et al. | Mar 2009 | B2 |
| 7509649 | Shenfield | Mar 2009 | B2 |
| 7523401 | Aldridge | Apr 2009 | B1 |
| 7545528 | Takabayashi et al. | Jun 2009 | B2 |
| 7548334 | Lo et al. | Jun 2009 | B2 |
| 7552265 | Newman et al. | Jun 2009 | B2 |
| 7565554 | Joosten et al. | Jul 2009 | B2 |
| 7567360 | Takahashi et al. | Jul 2009 | B2 |
| 7573593 | Hart et al. | Aug 2009 | B2 |
| 7657557 | Super | Feb 2010 | B2 |
| 7729363 | Shenfield et al. | Jun 2010 | B2 |
| 7904600 | Madril et al. | Mar 2011 | B2 |
| 8060556 | Krane et al. | Nov 2011 | B2 |
| 20010021945 | Matsuura | Sep 2001 | A1 |
| 20010027527 | Khidekel et al. | Oct 2001 | A1 |
| 20010028808 | Nomura et al. | Oct 2001 | A1 |
| 20010038462 | Teeuwen et al. | Nov 2001 | A1 |
| 20010039614 | Hellberg et al. | Nov 2001 | A1 |
| 20010044787 | Shwartz et al. | Nov 2001 | A1 |
| 20020016921 | Olsen et al. | Feb 2002 | A1 |
| 20020029256 | Zintel et al. | Mar 2002 | A1 |
| 20020032745 | Honda | Mar 2002 | A1 |
| 20020049786 | Bibliowicz et al. | Apr 2002 | A1 |
| 20020052916 | Kloba et al. | May 2002 | A1 |
| 20020055984 | Chang et al. | May 2002 | A1 |
| 20020059265 | Valorose, III | May 2002 | A1 |
| 20020073148 | Haines et al. | Jun 2002 | A1 |
| 20020080381 | Haines | Jun 2002 | A1 |
| 20020089691 | Fertlitsch et al. | Jul 2002 | A1 |
| 20020093676 | Parry | Jul 2002 | A1 |
| 20020098027 | Koike et al. | Jul 2002 | A1 |
| 20020099796 | Chou | Jul 2002 | A1 |
| 20020103827 | Sesek | Aug 2002 | A1 |
| 20020105664 | Inoue et al. | Aug 2002 | A1 |
| 20020107939 | Ford et al. | Aug 2002 | A1 |
| 20020109718 | Mansour et al. | Aug 2002 | A1 |
| 20020112037 | Koss | Aug 2002 | A1 |
| 20020120792 | Blair | Aug 2002 | A1 |
| 20020138279 | Al-Kazily et al. | Sep 2002 | A1 |
| 20020138476 | Suwa et al. | Sep 2002 | A1 |
| 20020138666 | Fujisawa | Sep 2002 | A1 |
| 20020145627 | Whitmarsh et al. | Oct 2002 | A1 |
| 20020147858 | Motoyama et al. | Oct 2002 | A1 |
| 20020152183 | Soares et al. | Oct 2002 | A1 |
| 20020152235 | Motoyama et al. | Oct 2002 | A1 |
| 20020152302 | Motoyama et al. | Oct 2002 | A1 |
| 20020156795 | Edwards et al. | Oct 2002 | A1 |
| 20020156846 | Rawat et al. | Oct 2002 | A1 |
| 20020171857 | Hisatomi et al. | Nov 2002 | A1 |
| 20020194180 | Alsop et al. | Dec 2002 | A1 |
| 20020194350 | Lu et al. | Dec 2002 | A1 |
| 20030002074 | Miyano | Jan 2003 | A1 |
| 20030007170 | Kajita et al. | Jan 2003 | A1 |
| 20030011633 | Conley et al. | Jan 2003 | A1 |
| 20030011640 | Green et al. | Jan 2003 | A1 |
| 20030014515 | Motoyama et al. | Jan 2003 | A1 |
| 20030014529 | Simpson et al. | Jan 2003 | A1 |
| 20030033369 | Bernhard | Feb 2003 | A1 |
| 20030035133 | Berkema et al. | Feb 2003 | A1 |
| 20030038965 | Simpson et al. | Feb 2003 | A1 |
| 20030043205 | Hill | Mar 2003 | A1 |
| 20030043396 | Klosterman et al. | Mar 2003 | A1 |
| 20030043405 | Hill | Mar 2003 | A1 |
| 20030048470 | Garcia | Mar 2003 | A1 |
| 20030048473 | Rosen | Mar 2003 | A1 |
| 20030049037 | Sadowara et al. | Mar 2003 | A1 |
| 20030053123 | Wu et al. | Mar 2003 | A1 |
| 20030063313 | Ito | Apr 2003 | A1 |
| 20030065766 | Parry | Apr 2003 | A1 |
| 20030065791 | Garg et al. | Apr 2003 | A1 |
| 20030074267 | Acharya et al. | Apr 2003 | A1 |
| 20030074312 | White | Apr 2003 | A1 |
| 20030081240 | Soto et al. | May 2003 | A1 |
| 20030084114 | Simpson et al. | May 2003 | A1 |
| 20030084302 | de Jong et al. | May 2003 | A1 |
| 20030088642 | Price et al. | May 2003 | A1 |
| 20030123112 | Kajita et al. | Jul 2003 | A1 |
| 20030131110 | Chang et al. | Jul 2003 | A1 |
| 20030142351 | Sakura | Jul 2003 | A1 |
| 20030164987 | Enomoto et al. | Sep 2003 | A1 |
| 20030167336 | Iwamoto et al. | Sep 2003 | A1 |
| 20030174356 | Cherry et al. | Sep 2003 | A1 |
| 20030182632 | Murdock et al. | Sep 2003 | A1 |
| 20030184552 | Chadha | Oct 2003 | A1 |
| 20030184590 | Will | Oct 2003 | A1 |
| 20030184782 | Perkins et al. | Oct 2003 | A1 |
| 20030187922 | Ohara | Oct 2003 | A1 |
| 20030188193 | Venkataramappa | Oct 2003 | A1 |
| 20030197883 | Lay et al. | Oct 2003 | A1 |
| 20030225796 | Matsubara | Dec 2003 | A1 |
| 20030225829 | Pena et al. | Dec 2003 | A1 |
| 20030225894 | Ito | Dec 2003 | A1 |
| 20030231196 | Keohane et al. | Dec 2003 | A1 |
| 20030233437 | Kitada et al. | Dec 2003 | A1 |
| 20040003341 | alSafadi et al. | Jan 2004 | A1 |
| 20040008363 | Suzuki et al. | Jan 2004 | A1 |
| 20040012628 | Kropf et al. | Jan 2004 | A1 |
| 20040012644 | Allen et al. | Jan 2004 | A1 |
| 20040019705 | Ogura | Jan 2004 | A1 |
| 20040030693 | Toda | Feb 2004 | A1 |
| 20040034786 | Okamoto et al. | Feb 2004 | A1 |
| 20040034807 | Rostowfske | Feb 2004 | A1 |
| 20040039990 | Bakar et al. | Feb 2004 | A1 |
| 20040044779 | Lambert | Mar 2004 | A1 |
| 20040054573 | Shah et al. | Mar 2004 | A1 |
| 20040061729 | Green | Apr 2004 | A1 |
| 20040064759 | McGuire et al. | Apr 2004 | A1 |
| 20040068693 | Rawat et al. | Apr 2004 | A1 |
| 20040070606 | Yang et al. | Apr 2004 | A1 |
| 20040080511 | Gilbert | Apr 2004 | A1 |
| 20040080771 | Mihira et al. | Apr 2004 | A1 |
| 20040080778 | Ito et al. | Apr 2004 | A1 |
| 20040093515 | Reeves, Jr. | May 2004 | A1 |
| 20040098165 | Butikofer | May 2004 | A1 |
| 20040098316 | Philippe et al. | May 2004 | A1 |
| 20040098595 | Apperle et al. | May 2004 | A1 |
| 20040105104 | Ishikawa et al. | Jun 2004 | A1 |
| 20040105122 | Schaeffer | Jun 2004 | A1 |
| 20040109028 | Stern et al. | Jun 2004 | A1 |
| 20040111670 | Sasakuma et al. | Jun 2004 | A1 |
| 20040113941 | Sliwa et al. | Jun 2004 | A1 |
| 20040117358 | von Kaenel et al. | Jun 2004 | A1 |
| 20040117784 | Endoh | Jun 2004 | A1 |
| 20040125403 | Furst et al. | Jul 2004 | A1 |
| 20040128349 | Maruyama | Jul 2004 | A1 |
| 20040130744 | Wu et al. | Jul 2004 | A1 |
| 20040130749 | Aoki | Jul 2004 | A1 |
| 20040133525 | Singh et al. | Jul 2004 | A1 |
| 20040150663 | Kim | Aug 2004 | A1 |
| 20040158471 | Davis et al. | Aug 2004 | A1 |
| 20040161257 | Ishihara | Aug 2004 | A1 |
| 20040162076 | Chowdry et al. | Aug 2004 | A1 |
| 20040165209 | Aoki et al. | Aug 2004 | A1 |
| 20040169881 | Sato | Sep 2004 | A1 |
| 20040179229 | Laughlin | Sep 2004 | A1 |
| 20040181747 | Hull et al. | Sep 2004 | A1 |
| 20040187018 | Owen et al. | Sep 2004 | A1 |
| 20040190057 | Takahashi et al. | Sep 2004 | A1 |
| 20040193678 | Trufinescu et al. | Sep 2004 | A1 |
| 20040199538 | Matsuda et al. | Oct 2004 | A1 |
| 20040203358 | Anderson | Oct 2004 | A1 |
| 20040205118 | Yu | Oct 2004 | A1 |
| 20040205533 | Lopata et al. | Oct 2004 | A1 |
| 20040205620 | Nishikiori et al. | Oct 2004 | A1 |
| 20040212823 | Chavers et al. | Oct 2004 | A1 |
| 20040215671 | Hyakutake et al. | Oct 2004 | A1 |
| 20040221231 | Madril et al. | Nov 2004 | A1 |
| 20040223778 | Zwiefelhofer | Nov 2004 | A1 |
| 20040226993 | Fulcher et al. | Nov 2004 | A1 |
| 20040227968 | Nakamura et al. | Nov 2004 | A1 |
| 20040230500 | Imago | Nov 2004 | A1 |
| 20040236862 | Ito | Nov 2004 | A1 |
| 20040254955 | Reese et al. | Dec 2004 | A1 |
| 20040255263 | Ando | Dec 2004 | A1 |
| 20040261010 | Matsuishi | Dec 2004 | A1 |
| 20040268229 | Paoli et al. | Dec 2004 | A1 |
| 20040268306 | Cheng et al. | Dec 2004 | A1 |
| 20050005094 | Jamieson et al. | Jan 2005 | A1 |
| 20050015472 | Catania et al. | Jan 2005 | A1 |
| 20050015585 | Kurose | Jan 2005 | A1 |
| 20050026593 | Anderson et al. | Feb 2005 | A1 |
| 20050028086 | Itavaara et al. | Feb 2005 | A1 |
| 20050044248 | Mihira et al. | Feb 2005 | A1 |
| 20050055475 | MacKay et al. | Mar 2005 | A1 |
| 20050057560 | Bibr et al. | Mar 2005 | A1 |
| 20050060046 | Ito et al. | Mar 2005 | A1 |
| 20050060564 | Murakami et al. | Mar 2005 | A1 |
| 20050063010 | Giannetti | Mar 2005 | A1 |
| 20050068581 | Hull et al. | Mar 2005 | A1 |
| 20050071507 | Ferlitsch | Mar 2005 | A1 |
| 20050071746 | Hart et al. | Mar 2005 | A1 |
| 20050080649 | Alvarez et al. | Apr 2005 | A1 |
| 20050091087 | Smith et al. | Apr 2005 | A1 |
| 20050091490 | Ogura | Apr 2005 | A1 |
| 20050097458 | Wilson | May 2005 | A1 |
| 20050108353 | Yamamoto | May 2005 | A1 |
| 20050114267 | Miwa et al. | May 2005 | A1 |
| 20050114658 | Dye et al. | May 2005 | A1 |
| 20050114766 | Yamamoto | May 2005 | A1 |
| 20050119955 | Dang et al. | Jun 2005 | A1 |
| 20050129423 | Lester et al. | Jun 2005 | A1 |
| 20050149576 | Marmaros et al. | Jul 2005 | A1 |
| 20050152334 | Okamoto et al. | Jul 2005 | A1 |
| 20050185217 | Nishizawa et al. | Aug 2005 | A1 |
| 20050195221 | Berger et al. | Sep 2005 | A1 |
| 20050210399 | Filner et al. | Sep 2005 | A1 |
| 20050223413 | Duggan et al. | Oct 2005 | A1 |
| 20050231747 | Bledsoe et al. | Oct 2005 | A1 |
| 20050231755 | Araumi et al. | Oct 2005 | A1 |
| 20050246428 | Araumi | Nov 2005 | A1 |
| 20050257134 | Goodman et al. | Nov 2005 | A1 |
| 20050257148 | Goodman et al. | Nov 2005 | A1 |
| 20050265744 | Uruta | Dec 2005 | A1 |
| 20060007480 | Yokokura | Jan 2006 | A1 |
| 20060010180 | Kawamura et al. | Jan 2006 | A1 |
| 20060015734 | Atobe | Jan 2006 | A1 |
| 20060028397 | O'Rourke | Feb 2006 | A1 |
| 20060031411 | Gimson et al. | Feb 2006 | A1 |
| 20060038004 | Rielly et al. | Feb 2006 | A1 |
| 20060041443 | Horvath | Feb 2006 | A1 |
| 20060045386 | Fukuoka et al. | Mar 2006 | A1 |
| 20060056873 | Kimura | Mar 2006 | A1 |
| 20060059434 | Boss et al. | Mar 2006 | A1 |
| 20060064647 | Tapuska et al. | Mar 2006 | A1 |
| 20060077423 | Mathieson et al. | Apr 2006 | A1 |
| 20060077432 | Lovat et al. | Apr 2006 | A1 |
| 20060077439 | Yamamura et al. | Apr 2006 | A1 |
| 20060077444 | Lum et al. | Apr 2006 | A1 |
| 20060085835 | Istvan et al. | Apr 2006 | A1 |
| 20060112123 | Clark et al. | May 2006 | A1 |
| 20060154227 | Rossi et al. | Jul 2006 | A1 |
| 20060162076 | Bartlett et al. | Jul 2006 | A1 |
| 20060198653 | Plewnia et al. | Sep 2006 | A1 |
| 20060221941 | Kishinsky et al. | Oct 2006 | A1 |
| 20060224405 | White et al. | Oct 2006 | A1 |
| 20060235742 | Castellanos et al. | Oct 2006 | A1 |
| 20060279475 | Lum et al. | Dec 2006 | A1 |
| 20070022180 | Cocotis et al. | Jan 2007 | A1 |
| 20070041035 | Sembower et al. | Feb 2007 | A1 |
| 20070094103 | Hyakutake et al. | Apr 2007 | A1 |
| 20070173266 | Barnes, Jr. | Jul 2007 | A1 |
| 20070174894 | Matsunaga | Jul 2007 | A1 |
| 20070186150 | Rao et al. | Aug 2007 | A1 |
| 20070291293 | Bellagamba et al. | Dec 2007 | A1 |
| 20080072162 | Dauerer et al. | Mar 2008 | A1 |
| Number | Date | Country |
|---|---|---|
| 09160441 | Dec 1995 | JP |
| 09293036 | Nov 1997 | JP |
| 09330190 | Dec 1997 | JP |
| 10013695 | Jan 1998 | JP |
| 10154190 | Jun 1998 | JP |
| 10240490 | Sep 1998 | JP |
| 10269184 | Oct 1998 | JP |
| 2000112691 | Apr 2000 | JP |
| 2000174949 | Jun 2000 | JP |
| 2000207108 | Jul 2000 | JP |
| 2002259071 | Feb 2001 | JP |
| 2001268296 | Sep 2001 | JP |
| 200284383 | Mar 2002 | JP |
| 2002140195 | May 2002 | JP |
| 2002171380 | Jun 2002 | JP |
| 2002175195 | Jun 2002 | JP |
| 2002221877 | Aug 2002 | JP |
| 2002236830 | Aug 2002 | JP |
| 2002298049 | Oct 2002 | JP |
| 2002312148 | Oct 2002 | JP |
| 2002324049 | Nov 2002 | JP |
| 2002351644 | Dec 2002 | JP |
| 2003022258 | Jan 2003 | JP |
| 2003157155 | May 2003 | JP |
| 2003178023 | Jun 2003 | JP |
| 2003196554 | Jul 2003 | JP |
| 2003198792 | Jul 2003 | JP |
| 2003208484 | Jul 2003 | JP |
| 2003209644 | Jul 2003 | JP |
| 2003216368 | Jul 2003 | JP |
| 2003216395 | Jul 2003 | JP |
| 2003223299 | Aug 2003 | JP |
| 2003281227 | Oct 2003 | JP |
| 2003288179 | Oct 2003 | JP |
| 2003308195 | Oct 2003 | JP |
| 200430448 | Jan 2004 | JP |
| 2004074530 | Mar 2004 | JP |
| 2004088561 | Mar 2004 | JP |
| 2004094313 | Mar 2004 | JP |
| 2004128561 | Apr 2004 | JP |
| 2004118549 | May 2004 | JP |
| 2004164157 | Jun 2004 | JP |
| 2004185396 | Jul 2004 | JP |
| 2004213356 | Jul 2004 | JP |
| 2004215309 | Jul 2004 | JP |
| 2004222247 | Aug 2004 | JP |
| 2004228686 | Aug 2004 | JP |
| 2004228687 | Aug 2004 | JP |
| 2004246771 | Sep 2004 | JP |
| 2004310516 | Nov 2004 | JP |
| 2004276271 | Dec 2004 | JP |
| 2004358800 | Dec 2004 | JP |
| 2005014591 | Jan 2005 | JP |
| 2005059496 | Mar 2005 | JP |
| 2005070979 | Mar 2005 | JP |
| 2005078278 | Mar 2005 | JP |
| 2005084891 | Mar 2005 | JP |
| 2005115543 | Apr 2005 | JP |
| 2005004243 | Jun 2005 | JP |
| 2005209059 | Aug 2005 | JP |
| 2005219440 | Aug 2005 | JP |
| 2005235034 | Sep 2005 | JP |
| 2005269250 | Sep 2005 | JP |
| 2006053905 | Feb 2006 | JP |
| 2006140898 | Jun 2006 | JP |
| WO0118754 | Mar 2001 | WO |
| WO0133381 | May 2001 | WO |
| WO0198864 | Dec 2001 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20060103588 A1 | May 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60704066 | Jul 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 10962248 | Oct 2004 | US |
| Child | 11232827 | US | |
| Parent | 10961793 | Oct 2004 | US |
| Child | 10962248 | US | |
| Parent | 10961911 | Oct 2004 | US |
| Child | 10961793 | US | |
| Parent | 10961594 | Oct 2004 | US |
| Child | 10961911 | US | |
| Parent | 10962103 | Oct 2004 | US |
| Child | 10961594 | US |
