Self-adding smartcard reader system
AssigneeXerox Corporation
InventorsJoseph H. Lang, Christopher L. Stone
Life of this patent
Estimating the term…
Abstract
A downloaded app controls a device to recognize whether a connected card reader is an unsupported card reader or whether an unsupported card is supplied to the connected card reader. The app automatically generates support for the unsupported card reader or unsupported card by reading the identifying information from the unsupported card reader or unsupported card, modifying an existing driver support file by adding the identifying information to the existing driver support file to create a modified driver support file, and testing the unsupported card reader or unsupported card using the modified driver support file. If the tests are successful, the app then supplies the modified driver support file to other devices separate from the printer.
Claims17
A device comprising:
- a processor;
- functional components operatively connected to the processor;
- a user interface operatively connected to the processor;
- a connected card reader operatively connected to the processor;
- and
- a computer storage device operatively connected to the processor,
- wherein the processor is configured to recognize whether the connected card reader is an unsupported card reader or whether an unsupported card is supplied to the connected card reader,
- wherein the processor is configured to automatically modify driver support files in the computer storage device to communicate with the unsupported card reader or the unsupported card by:
- reading identifying information from the unsupported card reader or the unsupported card;
- modifying an existing driver support file by adding the identifying information to the existing driver support file to create a modified driver support file;
- testing the unsupported card reader or the unsupported card using the modified driver support file by:
- storing a backup of the existing driver support file before creating the modified driver support file;
- deactivating the backup of the existing driver support file and activating the modified driver support file;
- facilitating a series of communication and operation tests on the unsupported card reader or the unsupported card using the modified driver support file;
- deactivating the modified driver support file and reactivating the backup of the existing driver support file based on tests being unsuccessful;
- and
- keeping the backup of the existing driver support file deactivated based on the testing being successful;
- and
- supplying the modified driver support file to other devices separate from the device based on the testing being successful.
A system comprising:
- a printer having a connected card reader, wherein the printer comprises a computer storage device;
- a computer server in communication with the printer through a computerized network;
- and
- a computer application (app) maintained by the computer server,
- wherein the computer server is configured to provide the app to the printer,
- wherein the app is configured to control the printer to recognize whether the connected card reader is an unsupported card reader or whether an unsupported card is supplied to the connected card reader,
- wherein the app is configured to automatically control the printer to modify driver support files in the computer storage device to communicate with the unsupported card reader or the unsupported card by:
- reading identifying information from the unsupported card reader or the unsupported card;
- modifying an existing driver support file by adding the identifying information to the existing driver support file to create a modified driver support file;
- testing the unsupported card reader or the unsupported card using the modified driver support file by:
- storing a backup of the existing driver support file before creating the modified driver support file;
- deactivating the backup of the existing driver support file and activating the modified driver support file;
- facilitating a series of communication and operation tests on the unsupported card reader or the unsupported card using the modified driver support file;
- deactivating the modified driver support file and reactivating the backup of the existing driver support file based on tests being unsuccessful;
- and
- keeping the backup of the existing driver support file deactivated based on the testing being successful;
- and
- supplying the modified driver support file to other devices separate from the printer based on the testing being successful.
A method comprising:
- providing an app from a computer server to a device, wherein the device comprises a computer storage device;
- controlling the device, by the app, to detect an unsupported card reader or detect an unsupported card supplied to a connected card reader of the device;
- and
- automatically generating support for the unsupported card reader or the unsupported card by the app by:
- reading identifying information from the unsupported card reader or the unsupported card;
- modifying an existing driver support file in the computer storage device by adding the identifying information to the existing driver support file to create a modified driver support file;
- testing the unsupported card reader or the unsupported card using the modified driver support file by:
- storing a backup of the existing driver support file before creating the modified driver support file;
- deactivating the backup of the existing driver support file and activating the modified driver support file;
- facilitating a series of communication and operation tests on the unsupported card reader or the unsupported card using the modified driver support file;
- deactivating the modified driver support file and reactivating the backup of the existing driver support file based on tests being unsuccessful;
- and
- keeping the backup of the existing driver support file deactivated based on the testing being successful;
- and
- supplying the modified driver support file to other devices separate from the device based on the testing being successful.
Dependencies are inferred from the claim text.