The subject application is directed generally to authorization for operation of data devices using a cellular telephone. The application is particularly suited for user authentication and securing payment from operation of devices such as document processing devices. It will be appreciated that the subject cellular telephone-based system and method is readily usable with any device for vending of products or services, particularly those for which a fee is required.
Many devices such as computers, workstations, copiers, printers, facsimile machines, as well as many shared devices including vending or service machines, ATMs, and the like, require users to enter information in order to secure operation. Information, such as user ID and password, serves many different functions. It limits those who are able to use a device, provides a mechanism to track usage, and allows for assessment of fees associated with such use. Users much remember myriad login sequences, not only to use such devices, but also to gain access to databases such as web-based account access, online purchases, and the like. Still other sequences must be recalled to authenticate someone calling into a service that has access to confidential, personal, or financial information of a user.
The many instances where sequences, such as character strings, must be memorized are rendered even more burdensome by the varying requirements for items such as username and password, which are commonly used. Some sites require a minimum number of characters which vary according to a location. Sites also require unique identifiers for each user. Thus, it is difficult for a user to be able to consistently use the same information to gain access in many instances.
In accordance with one embodiment of the subject application, there is provided a system and method for mobile telephone-based user authentication. A plurality of data records are stored in a data storage, wherein each data record includes a cellular telephone number and payment data corresponding to a pre-set payment mechanism associated therewith. Login data, comprised of a telephone number of a cellular telephone associated with a user, is received from the user via a user interface associated with a document processing device. The presence of a data record in the data storage corresponding to received login data is determined, and operation of the document processing device is commenced upon a determination of the presence of a data record in the data storage. A data message is sent to the cellular telephone corresponding to the telephone number of the login data. Confirmation data is received from the cellular telephone responsive to the data message, and an operation on the document processing device is completed in accordance with received confirmation data.
Still other advantages, aspects, and features of the subject application will become readily apparent to those skilled in the art from the following description, wherein there is shown and described a preferred embodiment of the subject application, simply by way of illustration of one of the modes best suited to carry out the subject application. As it will be realized, the subject application is capable of other different embodiments, and its several details are capable of modifications in various obvious aspects, all without departing from the scope of the subject application. Accordingly, the drawings and descriptions will be regarded as illustrative in nature and not as restrictive.
The subject application is described with reference to certain figures, including:
The subject application is directed to a system and method for authorization of operation of data devices using a cellular telephone. In particular, the subject application is directed to a system and method for user authentication and securing payment for operation of devices such as document processing devices. It will become apparent to those skilled in the art that the system and method described herein are suitably adapted to a plurality of varying electronic fields employing user authentication including, for example and without limitation, communications, general computing, data processing, document processing, financial transactions, vending of products or services, and the like. The preferred embodiment, as depicted in
Referring now to
The system 100 also includes a document processing device 104, which is depicted in
According to one embodiment of the subject application, the document processing device 104 is suitably equipped to receive a plurality of portable storage media including, without limitation, Firewire drive, USB drive, SD, MMC, XD, Compact Flash, Memory Stick, and the like. In the preferred embodiment of the subject application, the document processing device 104 further includes an associated user interface 106, such as a touch-screen LCD display, touch-panel, alpha-numeric keypad, or the like, via which an associated user is able to interact directly with the document processing device 104. In accordance with the preferred embodiment of the subject application, the user interface 106 is advantageously used to communicate information to the associated user and to receive selections from the associated user. The skilled artisan will appreciate that the user interface 106 comprises various components suitably adapted to present data to the associated user, as are known in the art. In accordance with one embodiment of the subject application, the user interface 106 comprises a display suitably adapted to display one or more graphical elements, text data, images, or the like to an associated user, to receive input from the associated user, and to communicate the same to a backend component such as the controller 108, as explained in greater detail below. Preferably, the document processing device 104 is communicatively coupled to the computer network 102 via a communications link 112. As will be understood by those skilled in the art, suitable communications links include, for example and without limitation, WiMax, 802.11a, 802.11b, 802.11g, 802.11(x), Bluetooth, the public switched telephone network, a proprietary communications network, infrared, optical, or any other suitable wired or wireless data transmission communications known in the art. The functioning of the document processing device 104 will be better understood in conjunction with the block diagrams illustrated in
In accordance with one embodiment of the subject application, the document processing device 104 further incorporates a backend component, designated as the controller 108, suitably adapted to facilitate the operations of the document processing device 104, as will be understood by those skilled in the art. Preferably, the controller 108 is embodied as hardware, software, or any suitable combination thereof configured to control the operations of the associated document processing device 104, facilitate the display of images via the user interface 106, direct the manipulation of electronic image data, and the like. For purposes of explanation, the controller 108 is used to refer to any of the myriad components associated with the document processing device 104 including hardware, software, or combinations thereof functioning to perform, cause to be performed, control, or otherwise direct the methodologies described hereinafter. It will be understood by those skilled in the art that the methodologies described with respect to the controller 108 are capable of being performed by any general purpose computing system known in the art, and thus the controller 108 is representative of such general computing devices and is intended as such when used hereinafter. Furthermore, the use of the controller 108 hereinafter is for the example embodiment only, and other embodiments, which will be apparent to one skilled in the art, are capable of employing the system and method for mobile telephone-based user authentication. The functioning of the controller 108 will better be understood in conjunction with the block diagrams illustrated in
Communicatively coupled to the document processing device 104 is a data storage device 110. In accordance with the one embodiment of the subject application, the data storage device 110 is any mass storage device known in the art including, for example and without limitation, magnetic storage drives, a hard disk drive, optical storage devices, flash memory devices, or any suitable combination thereof. In the one embodiment, the data storage device 110 is suitably adapted to store data records, user information, cellular telephone data, pre-set payment data, document data, image data, electronic database data, or the like. It will be appreciated by those skilled in the art that, while illustrated in
Illustrated in
The system 100 of
The system 100 illustrated in
The system 100 illustrated in
Communicatively coupled to the server 126 is the data storage device 128. According to the foregoing example embodiment, the data storage device 128 is any mass storage device, or plurality of such devices, known in the art including, for example and without limitation, magnetic storage drives, a hard disk drive, optical storage devices, flash memory devices, or any suitable combination thereof. In such an embodiment, the data storage device 128 is suitably adapted to store software updates, secured electronic documents, text data, data strings, account information, policy information, and the like. It will be appreciated by those skilled in the art that, while illustrated in
Turning now to
Also included in the device 200 is random access memory 206 suitably formed of dynamic random access memory, static random access memory, or any other suitable addressable memory system. Random access memory 206 provides a storage area for data instructions associated with applications and data handling accomplished by the processor 202.
A storage interface 208 suitably provides a mechanism for volatile, bulk, or long-term storage of data associated with the device 200. The storage interface 208 suitably uses bulk storage, such as any suitable addressable or serial storage such as a disk, optical, tape drive and the like as shown as 216, as well as any suitable storage medium, as will be appreciated by one of ordinary skill in the art.
A network interface subsystem 210 suitably routes input and output from an associated network, allowing the device 200 to communicate to other devices. The network interface subsystem 210 suitably interfaces with one or more connections with external devices to the device 200. By way of example, illustrated is at least one network interface card 214 for data communication with fixed or wired networks, such as Ethernet, Token-Ring, and the like, and a wireless interface 218 suitably adapted for wireless communication via means such as WiFi, WiMax, wireless modem, cellular network, or any suitable wireless communication system. It is to be appreciated, however, that the network interface subsystem 210 suitably utilizes any physical or non-physical data transfer layer or protocol layer, as will be appreciated by one of ordinary skill in the art. In the illustration, the network interface card 214 is interconnected for data interchange via a physical network 220 suitably comprised of a local area network, wide area network, or a combination thereof.
Data communication between the processor 202, read only memory 204, random access memory 206, storage interface 208, and the network subsystem 210 is suitably accomplished via a bus data transfer mechanism, such as illustrated by the bus 212.
Suitable executable instructions on the device 200 facilitate communication with a plurality of external devices such as workstations, document processing devices, other servers, or the like. While, in operation, a typical device operates autonomously, it is to be appreciated that direct control by a local user is sometimes desirable and is suitably accomplished via an optional input/output interface 222 to a user input/output panel 224, as will be appreciated by one of ordinary skill in the art.
Also in data communication with the bus 212 are interfaces to one or more document processing engines. In the illustrated embodiment, printer interface 226, copier interface 228, scanner interface 230, and facsimile interface 232 facilitate communication with printer engine 234, copier engine 236, scanner engine 238, and facsimile engine 240, respectively. It is to be appreciated that the device 200 suitably accomplishes one or more document processing functions. Systems accomplishing more than one document processing operation are commonly referred to as multifunction peripherals or multifunction devices.
Turning now to
The document processing engine 302 suitably includes a print engine 304, facsimile engine 306, scanner engine 308, and console panel 310. The print engine 304 allows for output of physical documents representative of an electronic document communicated to the processing device 300. The facsimile engine 306 suitably communicates to or from external facsimile devices via a device such as a fax modem.
The scanner engine 308 suitably functions to receive hard copy documents and, in turn, image data corresponding thereto. A suitable user interface, such as the console panel 310, suitably allows for input of instructions and display of information to an associated user. It will be appreciated that the scanner engine 308 is suitably used in connection with input of tangible documents into electronic form in bitmapped, vector, or page description language format and is also suitably configured for optical character recognition. Tangible document scanning also suitably functions to facilitate facsimile output thereof.
In the illustration of
The document processing engine 302 is suitably in data communication with one or more device drivers 314, which device drivers 314 allow for data interchange from the document processing engine 302 to one or more physical devices to accomplish the actual document processing operations. Such document processing operations include one or more of printing via driver 318, facsimile communication via driver 320, scanning via driver 322, and user interface functions via driver 324. It will be appreciated that these various devices are integrated with one or more corresponding engines associated with the document processing engine 302. It is to be appreciated that any set or subset of document processing operations are contemplated herein. Document processors that include a plurality of available document processing options are referred to as multi-function peripherals.
Turning now to
Also included in the controller 400 is random access memory 406 suitably formed of dynamic random access memory, static random access memory, or any other suitable addressable and writable memory system. Random access memory 406 provides a storage area for data instructions associated with applications and data handling accomplished by processor 402.
A storage interface 408 suitably provides a mechanism for non-volatile, bulk, or long-term storage of data associated with the controller 400. The storage interface 408 suitably uses bulk storage, such as any suitable addressable or serial storage such as a disk, optical, tape drive, and the like as shown as 416, as well as any suitable storage medium, as will be appreciated by one of ordinary skill in the art.
A network interface subsystem 410 suitably routes input and output from an associated network, allowing the controller 400 to communicate to other devices. The network interface subsystem 410 suitably interfaces with one or more connections with external devices to the device 400. By way of example, illustrated is at least one network interface card 414 for data communication with fixed or wired networks, such as Ethernet, Token-Ring, and the like, and a wireless interface 418 suitably adapted for wireless communication via means such as WiFi, WiMax, wireless modem, cellular network, or any suitable wireless communication system. It is to be appreciated, however, that the network interface subsystem 410 suitably utilizes any physical or non-physical data transfer layer or protocol layer, as will be appreciated by one of ordinary skill in the art. In the illustration, the network interface card 414 is interconnected for data interchange via a physical network 420 suitably comprised of a local area network, wide area network, or a combination thereof.
Data communication between the processor 402, read only memory 404, random access memory 406, storage interface 408, and the network interface subsystem 410 is suitably accomplished via a bus data transfer mechanism, such as illustrated by bus 412.
Also in data communication with the bus 412 is a document processor interface 422. The document processor interface 422 suitably provides connection with hardware 432 to perform one or more document processing operations. Such operations include copying accomplished via copy hardware 424, scanning accomplished via scan hardware 426, printing accomplished via print hardware 428, and facsimile communication accomplished via facsimile hardware 430. It is to be appreciated that the controller 400 suitably operates any or all of the aforementioned document processing operations. Systems accomplishing more than one document processing operation are commonly referred to as multifunction peripherals or multifunction devices.
Functionality of the subject system 100 is accomplished on a suitable document processing device, such as the document processing device 104, which includes the controller 400 of
In the preferred embodiment, the engine 502 allows for printing operations, copy operations, facsimile operations, and scanning operations. This functionality is frequently associated with multi-function peripherals, which have become a document processing peripheral of choice in the industry. It will be appreciated, however, that the subject controller does not have to have all such capabilities. Controllers are also advantageously employed in dedicated or more limited-purpose document processing devices that perform one or more of the document processing operations listed above.
The engine 502 is suitably interfaced to a user interface panel 510, which panel 510 allows for a user or administrator to access functionality controlled by the engine 502. Access is suitably enabled via an interface local to the controller or remotely via a remote thin or thick client.
The engine 502 is in data communication with the print function 504, facsimile function 506, and scan function 508. These functions 504/506/508 facilitate the actual operation of printing, facsimile transmission and reception, and document scanning for use in securing document images for copying or generating electronic versions.
A job queue 512 is suitably in data communication with the print function 504, facsimile function 506, and scan function 508. It will be appreciated that various image forms such as bit map, page description language or vector format, and the like are suitably relayed from the scan function 308 for subsequent handling via the job queue 512.
The job queue 512 is also in data communication with network services 514. In a preferred embodiment, job control, status data, or electronic document data is exchanged between the job queue 512 and the network services 514. Thus, suitable interface is provided for network-based access to the controller function 500 via client side network services 520, which is any suitable thin or thick client. In the preferred embodiment, the web services access is suitably accomplished via a hypertext transfer protocol, file transfer protocol, uniform data diagram protocol, or any other suitable exchange mechanism. The network services 514 also advantageously supplies data interchange with client side services 520 for communication via FTP, electronic mail, TELNET, or the like. Thus, the controller function 500 facilitates output or receipt of electronic document and user information via various network access mechanisms.
The job queue 512 is also advantageously placed in data communication with an image processor 516. The image processor 516 is suitably a raster image process, page description language interpreter or any suitable mechanism for interchange of an electronic document to a format better suited for interchange with device functions such as print 504, facsimile 506, or scan 508.
Finally, the job queue 512 is in data communication with a parser 518, which parser 518 suitably functions to receive print job language files from an external device, such as client device services 522. The client device services 522 suitably include printing, facsimile transmission, or other suitable input of an electronic document for which handling by the controller function 500 is advantageous. The parser 518 functions to interpret a received electronic document file and relay it to the job queue 512 for handling in connection with the afore-described functionality and components.
Turning now to
Upon a determination by the comparator 610 that a data record 604 corresponding to the login data 608 is present in the data storage, a system start mechanism 612 is rendered operable by an output of the comparator 610. The system 600 further includes a data transmitter 614 that is operable for data message transmission to the cellular telephone 616 corresponding to the cellular telephone number of the login data 608. Confirmation data 618 is then received from the cellular telephone 616 in response to the data message from the data transmitter 614. The document processor 620 is then operable in accordance with the received confirmation data 618 so as to process the operations of the associated document processing device 104.
Referring now to
Operations of the document processing device 710 are then commenced upon a determination from the testing 708 that a data record 702 is present in the storage 704 that corresponds to the received login data 706. A data message 712 is then communicated to the cellular telephone 714 associated with the telephone number of the login data 706 and corresponding data record 702. Confirmation data 716 is then communicated by the cellular telephone 714 to the document processing device 710, which completes the document processing operation in accordance with the received confirmation data 716.
The skilled artisan will appreciate that the subject system 100 and components described above with respect to
At step 804, login data is received from an associated user via the user interface 106, the kiosk 114, or the like associated with the document processing device 104. According to one embodiment of the subject application, the login data includes a telephone number of a cellular telephone 122 associated with the user. The controller 108 or other suitable component associated with the document processing device 104, the kiosk 114, or the like then tests for the presence of a data record in the associated data storage 110 corresponding to the login data received from the user at step 806. It will be appreciated by those skilled in the art that such testing is capable of being undertaken by the server 126 with respect to the data storage device 128 in accordance with one embodiment of the subject application when such data records are stored via the computer network 102.
At step 808, operation of the associated document processing device 104 is commenced following a determination from the testing of the presence of a data record in the associated data storage device 110 corresponding to the received login data. A data message is then sent from the controller 108 or other suitable component associated with the document processing device 104 to the cellular telephone 122 corresponding to the telephone number of the login data at step 810. It will be appreciated by those skilled in the art that the communication from the document processing device 104 to the cellular telephone 122 is suitably accomplished via the computer network 102, via a telephone communication with the public switched telephone network, or the like. In accordance with one embodiment of the subject application, the message is an SMS text message, an electronic mail message, or other suitable message format, as will be known in the art.
The controller 108 or other suitable component associated with the document processing device 104 then receives confirmation data from the cellular telephone 122 at step 812 in response to the previously communicated message. The skilled artisan will appreciate that such confirmation includes, for example and without limitation, a reply from the cellular telephone 122 to the received message, a new message to a given telephone number associated with the document processing device 104, an electronic mail message communicated to the document processing device 104, or the like. At step 814, the document processing device 104 then completes the operation in accordance with the received confirmation data.
Referring now to
At step 906, the controller 108 or other suitable component associated with the document processing device 104 tests for the presence in the data storage 110 or 128 of a data record that contains the same cellular telephone number as that contained in the received login data. It will be appreciated by those skilled in the art that, when the data records are stored on the server 126, the controller 108 or other suitable component associated with the document processing device 104 communicates the received login data to the server 126 for testing thereon. At step 908, a determination is made as to whether a data record has been located in the data storage 110 or 128 containing the same cellular telephone number as that in the login data. In the event that no matching data record has been located, flow proceeds to step 910, whereupon an error is displayed to the user via the user interface 106 or the kiosk 114. A determination is then made at step 912 as to whether the user has provided new login data, e.g. a new cellular telephone number or the like. When no updated login data has been received, operations of the document processing device 104 are denied at step 926 and the flowchart 900 thereafter terminates.
Following a determination at step 908 that a matching data record has been detected, flow proceeds to step 914. At step 914, operation of the document processing device 104 is commenced. That is, the user is able to select a desired document processing operation for performance by the associated document processing device 104. Following such user selection, cost data is generated at step 916 by the controller 108 or other suitable component associated with the document processing device 104 corresponding to a charge associated with the selected document processing operation. A data message is then communicated to the cellular telephone number of the data record, including the generated cost data, at step 918. According to one embodiment of the subject application, the controller 108 or other suitable component associated with the document processing device 104 communicates a text message to the cellular telephone 122 that includes details of the selected document processing operation and the charges associated with the performance thereof.
Confirmation data is then received from the cellular telephone 122 at step 920 in response to the data message. That is, the controller 108 or other suitable component associated with the document processing device 104 receives a reply text message or the like from the cellular telephone 122, indicating a confirmation of the charges. At step 922, the controller 108 or other suitable component associated with the document processing device 104 verifies the authenticity of the received confirmation data via the telephone number or data content of the confirmation data. A determination is then made at step 924 as to whether the received confirmation data has been verified. When no verification has been determined, flow proceeds to step 926, whereupon the user is denied operations of the document processing device 104.
Upon a determination at step 924 that the authenticity of the confirmation data has been verified, flow proceeds to step 928. At step 928, the document processing device 104 completes the selected document processing operation in accordance with the confirmation data received from the cellular telephone 122. At step 930, the controller 108 or other suitable component associated with the document processing device 104, the server 126, or the like thereafter assesses the charge in accordance with the pre-set payment mechanism, e.g. charges the credit card, debit card, pre-paid account, or the like.
The foregoing description of a preferred embodiment of the subject application has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the subject application to the precise form disclosed. Obvious modifications or variations are possible in light of the above teachings. The embodiment was chosen and described to provide the best illustration of the principles of the subject application and its practical application to thereby enable one of ordinary skill in the art to use the subject application in various embodiments and with various modifications, as are suited to the particular use contemplated. All such modifications and variations are within the scope of the subject application as determined by the appended claims when interpreted in accordance with the breadth to which they are fairly, legally, and equitably entitled.