JP2008287724A - Pay service system and method for document processing - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a pay service system and method for document processing, capable of performing accurate tracking of expenses associated with a service or the like. <P>SOLUTION: A document processing device receives a document processing request and calculates costs associated with the performance thereof. Transaction identification data are then received and compared to common identifier data. When the transaction identification data match the common identifier data, the device prompts the user to pay at a counter at the service provider location and then performs the requested operation. The details of the transaction are then communicated to the server. <P>COPYRIGHT: (C)2009,JPO&INPIT

Description

  The present invention relates to a paid service system and method for document processing.

  Stand-alone document processing devices, document processing service stores and other document processing service providers are typically constrained in the manner in which payments for services can be collected. Usually, the payment method is limited to charging to a credit card, prepaid card or user account. While these payment methods are acceptable to some users, other users need to be able to pay other methods for payment, such as cash, to the service provider. Inconsistent with such cash payment demands, document processing service providers need to be able to accurately track and correct expenses and revenues. Therefore, there is no means to accurately track the type of transaction related to the transaction, the resources used, the devices used, etc. that are required when a user makes a cash payment, so document processing services • Providers typically do not provide cash payment services to the sales floor. In other words, records corresponding to the key components of the document processing service transaction are not easily and automatically maintained.

  Accordingly, there is a need for a document processing pay service system and method that enables accurate tracking of costs associated with the service.

  The present invention has been made in view of the above-described conventional problems, and an object thereof is to provide a fee-based service system and method for document processing that enables accurate tracking of a service-related cost or the like.

  A document processing fee service system according to the present invention comprises a document processing station for processing documents and a payment station associated with each of the document processing stations and including means for receiving billing data from each of the document processing stations. Prepare. The document processing station includes: means for accessing the common identifier data; means for receiving the transaction identifier data from the portable data storage means; means for comparing the transaction identification data with the common identifier data; the transaction identifier data is the common identifier data; Means for outputting billing data when matched, and means for communicating debit data associated with the portable data storage means when the transaction identifier data does not match the common identifier data.

  In one embodiment of the present invention, the system further comprises means for generating an error signal when the transaction identifier data is unknown data.

  In another embodiment of the invention, the system further comprises means for outputting billing data to a payment station.

  In yet another embodiment of the invention, the portable data storage means is a debit card.

  In a further embodiment of the invention, the billing data includes data corresponding to completed document processing operations.

  In one embodiment of the invention, the payment station includes means for receiving a payment corresponding to the received billing data.

  The document processing chargeable service method according to the present invention also includes a step of receiving a document processing request for an electronic document at a document processing station, a step of generating billing data related to the document processing request, and accessing common identifier data. Charging the associated payment station when the transaction identifier data matches the common identifier data, receiving the transaction identification data from the portable data storage device, comparing the transaction identification data with the common identifier data, and Outputting billing data and communicating debit data associated with the portable data storage device when the transaction identifier data does not match the common identifier data.

  In accordance with the present invention, a document processing pay service system and method is provided that enables accurate tracking of costs associated with the service.

  Hereinafter, embodiments of the present invention will be described as appropriate with reference to the drawings. FIG. 1 shows an example of the configuration of the entire fee-based service system for document processing according to an embodiment of the present invention. The illustrated system 100 utilizes a distributed computing environment represented as a computer network 102. The computer network 102 is any distributed communication system known in the art that enables the exchange of data between multiple electronic devices. Computer network 102 is known in the art including, for example, a virtual local area network, a wide area network, a personal area network, a local area network, the Internet, an intranet, or any combination thereof. Any computer network. In one embodiment according to the present invention, the computer network 102 can be configured with a number of existing, such as token ring, IEEE 802.11 (x), Ethernet, or other wireless or wire-based data communication mechanisms. It consists of a physical layer and a transport layer as exemplified by the data transfer mechanism. Although computer network 102 is shown in FIG. 1, the present invention can be similarly implemented in a stand-alone system known in the art.

  The system 100 further includes a first document processing device, represented in the figure as a Multi-Function Peripheral (hereinafter also referred to as MFP), suitable for performing various document processing. 104 and a second document processing device 120. However, the MFP is a form of the document processing apparatus, and the document processing apparatus in the present invention is not limited to the MFP. Processing operations in the document processing apparatus include, for example, facsimile communication, image scanning, copying, printing, e-mail, document management or document storage. In one form according to the present invention, document processing devices 104 and 120 provide remote document processing services to external devices or network devices. Document processing devices 104 and 120 include hardware, software, and any suitable combination thereof configured to interact with a user, a device connected to a network, or the like. Functions and the like of the document processing apparatuses 104 and 120 will be described later with reference to FIGS.

  In one embodiment according to the present invention, the document processing devices 104 and 120 include an interface for receiving a plurality of portable storage media such as various drives having various IEEE 1394 or USB interfaces and various IC memory cards. . In an embodiment of the present invention, each of the document processing devices 104 and 120 further comprises a user interface 106 and 122, such as a touch screen, LCD, touch panel or alphanumeric keypad, so that the user can Can interact directly with the corresponding document processing device 104 or 120 via a simple user interface. In one embodiment according to the present invention, user interfaces 106 and 122 are used to communicate information to the user and receive selections from the user. User interfaces 106 and 122 include a variety of components suitable for presenting data to a user, as is known in the art. According to one embodiment of the present invention, user interfaces 106 and 122 each display one or more graphic elements, text data, images, etc. to the user, as described in more detail below, from the user. It includes a display that is suitably adapted to receive input and communicate received user input to back-end components such as controllers 108 and 124. Document processing devices 104 and 120 are communicatively connected to computer network 102 via appropriate communication links 112 and 128, respectively. Suitable communication links include, for example, WiMax (Worldwide Interoperability for Microwave Access), IEEE802.11a, IEEE802.11b, IEEE802.11g, IEEE802.11 (x), Bluetooth (registered trademark), public switched telephone network, dedicated communication Network, infrared connections, optical connections, or other suitable wired or wireless data communication channels known in the art are included.

  In embodiments in accordance with the present invention, document processing devices 104 and 120 further incorporate appropriate controllers 108 and 124, respectively, that facilitate processing operations by the corresponding document processing devices 104 and 120, respectively. Controllers 108 and 124 facilitate processing such as controlling operations of corresponding document processing devices 104 and 120, displaying images via user interfaces 106 and 122, or instructing operation of electronic image data. It is implemented by hardware, software, or an appropriate combination thereof. In the following description, the terms controllers 108 and 124 include hardware, software, or a combination thereof that functions to perform, cause, or control, or otherwise direct the operations described below. In the sense of any number of components associated with the corresponding document processing devices 104 and 120. In the figure and the above description, the controllers 108 and 124 are incorporated in the corresponding document processing devices 104 and 120. However, the controllers 108 and 124 can communicate with the corresponding document processing devices 104 and 120, respectively. It may be in the form of a connected external device. The operations described in connection with controllers 108 and 124 may be performed by any general purpose computing system known in the art. Thus, the controllers 108 and 124 represent such general purpose computing devices and are intended to be so when used in the following description. Furthermore, although the following description uses controllers 108 and 124, this is merely an example embodiment, and other embodiments utilize the document processing fee-based service system and method of the present invention. be able to. The configuration of the controllers 108 and 124 will be described later with reference to FIGS. 4 and 5.

  Data storage devices 110 and 126 are communicably connected to the document processing devices 104 and 120, respectively. Data storage devices 110 and 126 are mass storage devices known in the art including, for example, hard disk drives, other magnetic storage devices, optical storage devices, flash memory, or any combination thereof. . In one embodiment, the data storage devices 110 and 126 are suitably adapted to store document data, image data, electronic database data, or the like. Data storage devices 110 and 126 are illustrated as independent components of system 100 in the figure, but may be internal storage devices of corresponding document processing devices 104 and 120, such as, for example, internal hard disk drives, or the like. It can be implemented as a component of the controllers 108 and 124. In accordance with one embodiment of the present invention, data storage devices 110 and 126 can store common identifier data and configuration data associated with document processing devices 104 and 120. Configuration data includes, for example, account information, service provider information and available document processing capabilities.

  A first payment station-based kiosk 114 and a second payment station-based kiosk 130 are communicatively connected to the document processing devices 104 and 120, respectively. First and second kiosks 114 and 130 can communicate with computer network 102 via document processing devices 104 and 120, respectively. The kiosks 114 and 130 can be implemented as components independent of the corresponding document processing devices 104 and 120, respectively, or as components built into the corresponding document processing devices. Here, the use of kiosks 114 and 130 is for illustrative purposes only, and the present invention can be embodied without the use of kiosks. According to one embodiment of the present invention, kiosks 114 and 130 include displays 116 and 132 and user input devices 118 and 134, respectively. The kiosks 114 and 130 may implement a device that combines a user input device and a display, such as a touch screen interface. According to one embodiment of the present invention, kiosks 114 and 130 perform prompting to the user, receiving instructions from the user, receiving payment data, and the like. For example, kiosks 114 and 130 are adapted to receive a portable storage medium such as a magnetic card having transaction identification data recorded thereon. In such embodiments, kiosks 114 and 130 include magnetic card readers that receive and read data from portable storage media. Also, kiosks 114 and 130 can communicate with back-end components such as server 136 via computer network 102 using connections via associated document processing devices 104 and 120, respectively.

  System 100 further includes a back-end server 136 capable of data communication with computer network 102 via communication link 140. The back-end server 136 further includes a data storage device 138 connected thereto. In accordance with one embodiment of the present invention, the data storage device 138 can store a plurality of databases corresponding to document processing service providers, document processing services, document processing devices, users, payment information, and the like. The communication link 140 is, for example, Bluetooth (registered trademark), WiMax, IEEE802.11a, IEEE802.11b, IEEE802.11g, IEEE802.11 (x), dedicated communication network, infrared connection, optical connection, public switched telephone network, or Other suitable wired or wireless data communication channels known in the art. The configuration of the back-end server 136 will be described later with reference to FIG.

  The system 100 also includes a user device 142 that is in data communication with the computer network 102 via the communication link 144. Although the user device 142 is shown as a notebook personal computer in the figure, this is merely an example. The user device 142 includes, for example, a computer workstation, desktop personal computer, personal digital assistant (PDA), web-compatible mobile phone, smartphone, device for a dedicated communication network, or other web-compatible electronic device. It represents any personal computing device known in the art. The communication link 144 is, for example, Bluetooth (registered trademark), WiMax, IEEE802.11a, IEEE802.11b, IEEE802.11g, IEEE802.11 (x), dedicated communication network, infrared connection, optical connection, public switched telephone network, or Other suitable wired or wireless data communication channels known in the art. The user device 142 generates, for example, an electronic document, a document processing instruction, a user interface modification, upgrade, update, or personalized data, and the generated data is stored in the document processing device 104, the document processing device 120, and the server 136. Or to any other similar device connected to the computer network 102. According to one embodiment of the present invention, the user device 142 includes a suitable web browser application to securely interact with the document processing device 104, document processing device 120, server 136, etc. in a secure manner. The user device 142 can also be implemented as a management device, in which case the user associated with the device 142 can access, delete, view, or make other changes to data stored in the backend server 136. It can be performed.

  Next, the hardware and functional configuration of the document processing apparatus in which the operation of the system according to the embodiment of the present invention is executed will be described with reference to FIGS. FIG. 2 shows the hardware of a document processing device 200 (represented as the first document processing device 104 and the second document processing device 120 in FIG. 1) on which the operation of the system 100 is executed in the embodiment according to the present invention. A configuration example of the hardware architecture is shown. The document processing apparatus 200 includes a processor 202 composed of at least one CPU. The processor 202 may be composed of a plurality of CPUs that operate in cooperation with each other. The document processing apparatus 200 is effective for static or fixed data such as BIOS function, system function, system configuration data, and other routines or data used for the operation of the document processing apparatus 200, or for instructions. A non-volatile or read-only memory (ROM) 204 that is used is included.

  The document processing device 200 also includes a RAM 206 comprised of dynamic random access memory, static random access memory, or any other suitable addressable and writable memory system. ing. RAM 206 provides storage for data instructions related to applications and data processing processed by processor 202.

  Storage interface 208 provides a mechanism for non-volatile storage, mass storage, or long-term storage of data associated with document processing device 200. The storage interface 208 may be a disk drive illustrated as 216, or any suitable addressable such as an optical drive, tape drive, etc., or a mass storage device such as a serial storage device, as well as those skilled in the art. Any suitable storage medium known in the art is used.

  The network interface subsystem 210 allows the document processing device 200 to communicate with other devices by appropriately routing inputs and outputs to and from the network. The network interface subsystem 210 establishes one or more connections with external devices of the document processing device 200. In the figure, as an example, at least one network interface card 214 for data communication with a fixed or wired network such as Ethernet (registered trademark) and token ring, and WiFi (Wireless Fidelity), WiMax, wireless modem A suitable wireless interface 218 for wireless communication via means such as a cellular network or any suitable wireless communication system is shown. The network interface subsystem 210 suitably utilizes a data transfer layer or protocol layer that is not any physical data transfer layer or physical data transfer layer. In the figure, the network interface card 214 is used to exchange data over a physical network 220 suitably configured from, for example, a local area network, a wide area network, or a combination thereof. It is connected.

  Data communication between the processor 202, read only memory (ROM) 204, RAM 206, storage interface 208, and network interface subsystem 210 occurs via a bus data transfer mechanism illustrated by bus 212.

  Executable instructions in the document processing apparatus 200 smoothly execute communication with a plurality of external devices such as a workstation, another document processing apparatus, or a server. In operation, typical devices operate autonomously, but often direct control by a local user may be desirable. Direct control by the local user may be performed via an optional input / output (I / O) interface 222 to a user input / output (I / O) panel 224.

  An interface to one or more document processing engines also performs data communication via bus 212. In the illustrated embodiment, print interface 226, copy interface 228, image scan interface 230, and facsimile interface 232 are print engine 234, copy engine 236, image scan engine (scanner) 238, and facsimile, respectively. -Facilitates communication with the engine 240. The document processing apparatus 200 appropriately executes one or more document processing functions. A system that executes a plurality of document processing operations is generally called a multi-function peripheral device (MFP) or multi-function device as described above.

  Next, functional blocks of the document processing apparatus in which the system operation is executed will be described with reference to FIG. FIG. 3 shows a functional block configuration example of the document processing apparatus 300 in which the operation of the system 100 according to the embodiment of the present invention is executed. FIG. 3 illustrates the functionality of the hardware shown in FIG. 2 in connection with software and operating system functions.

  The document processing apparatus 300 includes a document processing engine 302 that smoothly performs one or more document processing operations. The document processing engine 302 includes a print engine 304, a facsimile engine 306, an image scanning engine (scanner) 308, and a console panel 310. The print engine 304 can output a physical document, that is, a hard copy, of the electronic document transmitted to the document processing apparatus 300. The facsimile engine 306 performs facsimile communication with an external facsimile apparatus via an apparatus such as a facsimile modem.

  An image scanning engine (scanner) 308 functions to receive a hardcopy document and convert it to image data corresponding to the hardcopy document. A user interface, such as console panel 310, allows input of instructions from the user and display of information to the user. The image scanning engine 308 converts visible tangible document input into an electronic form in bitmap format, vector format, or page description language (PDL) format, and for optical character recognition. It is configured. Moreover, the actual image scanning of a tangible document functions effectively even in a facsimile operation.

  The document processing engine 302 shown in the figure also includes an interface 316 with a network via a driver 326, and is composed of, for example, a network interface card. The network provides sufficient interaction with any suitable physical and non-physical layer such as wired, wireless or optical data communication.

  Document processing engine 302 communicates appropriately with one or more device drivers 314. Device driver 314 enables data exchange between document processing engine 302 and one or more physical devices to perform actual document processing operations. Such document processing operations include one or more of printing by driver 318, facsimile communication by driver 320, image scanning by driver 322, and user interface functions by driver 324. These various devices are coupled to one or more corresponding engines associated with the document processing engine 302. In the present invention, any set or subset of document processing operations is envisioned. A document processing apparatus that includes a plurality of available document processing options is called an MFP.

  Next, with reference to FIG. 4 and FIG. 5, the hardware and functional configuration of the controller in which the system operation in the embodiment according to the present invention is executed will be described. FIG. 4 illustrates an example hardware architecture configuration of a back-end component on which the operation of the system 100 is performed in the embodiment according to the present invention, that is, the controller 400 shown as the controllers 108 and 124 in FIG. The figure is shown. In the figure, in order to clarify the significance of the constituent elements of the controller, a part of the constituent elements of the document processing apparatus other than the controller, which is represented by reference numeral 432, is also shown. Controller 400 represents any general-purpose computing device known in the art that has the ability to smoothly perform the operations described herein. The controller 400 includes a processor 402 including at least one CPU. The processor 402 may be composed of a plurality of CPUs that operate in cooperation with each other. Further, the controller 400 is effectively used for static or fixed data such as BIOS function, system function, system configuration data, and other routines or data used for the operation of the controller 400, or for instructions. Non-volatile or read-only memory (ROM) 404 is included.

  Controller 400 also includes a RAM 406 comprised of dynamic random access memory, static random access memory, or any other suitable addressable and writable memory system. . RAM 406 provides a storage area for data instructions related to applications and data processing processed by processor 402.

  Storage interface 408 provides a mechanism for non-volatile storage, mass storage or long-term storage of data associated with controller 400. The storage interface 408 is known to those skilled in the art in addition to a disk drive illustrated as 416 or any suitable addressable such as an optical drive, tape drive, or mass storage device such as a serial storage device. Use any suitable storage medium.

  The network interface subsystem 410 allows the controller 400 to communicate with other devices by appropriately routing inputs and outputs to and from the network. The network interface subsystem 410 suitably interfaces one or more connections with external devices to the device 400. In the figure, for example, at least one network interface card 414 for data communication with a fixed or wired network, such as Ethernet and Token Ring, etc., and WiFi, WiMax, wireless modem, cellular network or A suitable wireless interface 418 for wireless communication via means such as any suitable wireless communication system is shown. The network interface subsystem 410 suitably utilizes a data transfer layer or protocol layer that is not any physical data transfer layer or physical data transfer layer. In the figure, the network interface card 414 is used to exchange data over a physical network 420 suitably configured from, for example, a local area network, a wide area network, or a combination thereof. It is connected.

  Data communication between the processor 402, read only memory (ROM) 404, RAM 406, storage interface 408, and network interface subsystem 410 is through a bus data transfer mechanism illustrated by bus 412.

  The document processor interface 422 also performs data communication via the bus 412. Document processor interface 422 provides a connection with document processing hardware 432 to perform various document processing operations. Such document processing operations include copying performed by the copy hardware 424, image scanning performed by the image scanning hardware 426, printing performed by the printing hardware 428, and performed by the facsimile hardware 430. There is facsimile communication done. The controller 400 properly operates any or all of these document processing operations. A system capable of executing a plurality of document processing operations is called an MFP or a multi-function device as described above. The functions of system 100 include document processing devices 104 and 120, etc., including controller 400 (shown as controllers 108 and 124 in FIG. 1) as an intelligent subsystem associated with the document processing device. In any suitable document processing apparatus.

  Next, referring to FIG. 5, a functional block of the controller that executes the system operation and an outline of the operation will be described. FIG. 5 is a diagram for explaining a configuration example of functional blocks of a controller that executes the operation of the system 100 according to the embodiment of the present invention. Also in FIG. 5, in order to clarify the significance of the functional elements of the controller, some of the functional elements of the document processing apparatus other than the controller are also shown. FIG. 5 illustrates the functionality of the hardware shown in FIG. 4 in connection with software and operating system functions.

  Controller functionality includes a document processing engine 502. In one embodiment, document processing engine 502 enables printing operations, copying operations, facsimile communication operations, and image scanning operations. An apparatus capable of executing these functions by one apparatus is an MFP which is a document processing peripheral apparatus generally preferred in the industry. However, it is not necessary for the controller to allow all of the document processing operations described above. The controller is also effectively used in a dedicated document processing apparatus that executes a part of the document processing operation described above or a document processing apparatus for a more limited purpose.

  Document processing engine 502 is appropriately interfaced with user interface panel 510. A user or administrator can access functions controlled by the document processing engine 502 via the user interface panel 510. Access can be through an interface located locally on the controller, or remotely by a remote thin client or thick client.

  The document processing engine 502 performs data communication with the print function unit 504, the facsimile communication function unit 506, and the image scanning function unit 508. These functional units facilitate the actual processing operations of document image scanning to print, send and receive faxes, and obtain document images for copying, or generate electronic versions of document images.

  A job queue 512 performs data communication with the print function unit 504, the facsimile communication function unit 506, and the image scanning function unit 508. Various image formats, such as bitmap format, page description language (PDL) format, or vector format, are relayed from image scanning function 508 via job queue 512 for subsequent processing.

  The job queue 512 also performs data communication with the network service function unit 514. In one embodiment, job control, status data, or electronic document data is exchanged between job queue 512 and network service function 514. Thus, a suitable interface is provided for network-based access to the controller function via the client-side network service function 520, which can be any suitable thin or thick client. In one embodiment, web service access is performed by hypertext transfer protocol (HTTP), file transfer protocol (FTP), uniform data diagram protocol, or any other suitable exchange mechanism. The network service function unit 514 also effectively provides data exchange with the client-side network service function 520 for communication by FTP, electronic mail, TELNET, or the like. Thus, the controller function facilitates the output or reception of electronic documents and user information through various network access mechanisms.

  The job queue 512 also performs data communication with the image processor 516. The image processor 516 is connected to an apparatus function unit such as a print function unit 504, a facsimile communication function unit 506, or an image scanning function unit 508, raster image processing (RIP) for converting an electronic document into a format suitable for exchanging, and page description. A language interpreter or any suitable image processing mechanism.

  Finally, the job queue 512 performs data communication with a job analysis unit (job parser) 518, and the job analysis unit 518 receives a print job language (PJL) file from an external device such as the client device service unit 522. do. The client device service unit 522 includes electronic document printing, facsimile communication, or other suitable electronic document input that is valid for processing by the controller function. The job analysis unit 518 functions to analyze the received electronic document file and relay the analyzed electronic document file information to the job queue 512 for processing related to the functions and components described above.

  Next, with reference to FIG. 6, the operation of the system in the embodiment according to the present invention is executed, and the hardware configuration of the server shown as the back-end server 136 in FIG. 1 will be described. FIG. 6 shows a configuration example of the hardware architecture of the server 600 on which the operation of the system 100 is executed in the embodiment according to the present invention. The server 600 includes a processor 602 that includes at least one CPU. The processor 602 may be composed of a plurality of CPUs that operate in cooperation with each other. Further, the server 600 includes a nonvolatile function that is effectively used for static or fixed data such as a BIOS function, a system function, a system configuration, or other routines or data used for the operation of the server 600, or an instruction. Or read only memory (ROM) 604 is included.

  Server 600 also includes a RAM 606 comprised of dynamic random access memory, static random access memory, or any other suitable addressable and writable memory system. . The RAM 606 provides a storage area for data and instructions related to applications processed by the processor 602 and data processing.

  Storage interface 608 provides a mechanism for non-volatile storage, mass storage, or long-term storage of data associated with server 600. The storage interface 608 is known to those skilled in the art in addition to a disk drive illustrated as 616 or any suitable addressable such as an optical drive, tape drive, or a mass storage device such as a serial storage device. Use any suitable storage medium that is.

  The network interface subsystem 610 allows the server 600 to communicate with other devices by appropriately routing input and output to and from the network. The network interface subsystem 610 appropriately interfaces one or more connections with external devices to the server 600. In the figure, for example, at least one network interface card 614 for data communication with a fixed or wired network such as Ethernet and Token Ring, and WiFi, WiMax, wireless modem, cellular network or A suitable wireless interface 618 is shown for wireless communication via means such as any suitable wireless communication system. The network interface subsystem 610 suitably utilizes a data transfer layer or protocol layer that is not any physical data transfer layer or physical data transfer layer. In the figure, the network interface card 614 is used to exchange data over a physical network 620, suitably configured from, for example, a local area network, a wide area network, or a combination thereof. It is connected.

  Data communication between the processor 602, read only memory (ROM) 604, RAM 606, storage interface 608, and network interface subsystem 610 is via a bus data transfer mechanism illustrated by bus 612.

  Proper executable instructions at server 600 facilitate communication with a plurality of external devices such as workstations, document processing devices or other servers. In operation, a typical server operates autonomously, but direct control by the user may be desirable, and such direct control is performed via an optional input / output interface 622.

  The outline of the operation in the present invention will be described below. First, at least one of a plurality of document processing stations controlled in common receives a request to execute a document processing operation on an electronic document. Next, transaction identification data is received from the associated portable data storage device by the document processing station that received the document processing request. The station then generates billing data corresponding to each requested document processing operation. Next, the received transaction identification data is compared with common identification data. If the received transaction data matches the common identifier data, billing data is output to the associated payment station. If the received transaction data does not match the common identifier data, debit data associated with the portable data storage device is output.

  According to an exemplary embodiment of the present invention, a document processing request is received by the document processing device 104 or 120 via the associated kiosk 114, 130, user interface 106, 122, user device 142, or the like. Transaction identification data is then received from the portable storage medium. In one embodiment according to the present invention, the transaction identification data is in an account number or alphanumeric character string received from a portable storage medium such as a magnetic storage device, for example, a credit card, debit card or smart card. Correspond. The document processing device 104 or 122 that receives the document processing request then calculates the costs associated with performing the requested document processing operation by the corresponding controller 108 or 124. Based on the calculation result, billing data corresponding to the cost of executing the document processing request is generated.

  Next, the controller 108 or 124 corresponding to each of the document processing devices 104 or 120 that received the document processing request determines whether or not the received transaction identification data is unknown data. . That is, a determination is made whether the data received from the portable data storage device is incomprehensible, has been altered, cannot be read, represents an unrecognizable account number, or the like. If the received transaction identification data is unknown, an error signal is generated by the document processing device 104 or 120 that has received the document processing request, and the generated error signal is, for example, visually on the user interfaces 106, 122. Communicated to the user associated with the document processing request via any suitable means known in the art including indicators, displays 116, 132, email messaging, text messaging or audible alerts, etc. The

  If it is determined that the transaction identification data is not of an unknown type or format, the transaction identification data is compared with the common identifier data. According to one embodiment of the present invention, the common identifier data corresponds to a local account that indicates a counter-payment type transaction in which a user pays for a document processing service at a payment station. In one embodiment of the present invention, the common identifier data is received from the back-end server 136 and the physical location of the document processing device 104 or 120 that received the document processing request, the document processing device that received the document processing request. Corresponding to the service provider or the like associated with 104 or 120.

  When the common identifier data and the transaction identification data match, billing data is output to the payment station, prompting the user to pay for the costs associated with performing the requested document processing operation. Payment stations include, for example, automated payment stations, assisted payment stations, cashiers, and the like. If the transaction identification data and the common identifier data do not match, debit data associated with the portable data storage device is output. That is, a credit card account, personal account, or prepaid account, such as a prepaid account, represented by the transaction identification data is debited according to the costs associated with performing the requested document processing operation. As used herein, the term “withdrawal” includes, for example, charging a credit-based account, subtracting from a prepaid account, charging a business account, or charging a personal account.

  In an exemplary embodiment according to the present invention, the backend server 136 receives common identifier data corresponding to account data representing an account associated with a service provider. Service providers provide facilities and services for fee-based document creation, management, storage, communication, equipment, and the like. According to one embodiment of the present invention, the service provider includes kiosks 114 and 130 connected to document processing devices 104 and 120, respectively, via which a user can request to perform document processing operations. . For example, a kiosk, document processing device is located in a facility operated by a service provider, including a plurality of such kiosks, document processing devices, thereby providing document processing services to multiple users. The common identifier data includes data representing the 16-digit account number corresponding to the prepaid account in this exemplary embodiment. Next, the server 136 receives service provider location identification data representing the service provider location and the document processing device 104.

  The received account data is then stored by the server 136 in association with the service provider identification data in the associated database. Server 136 then communicates the relevant data to document processing devices 104 and 120 and selectively modifies the configuration data associated with those document processing devices with the communicated data. The configuration data includes, for example, common identifier data, account data corresponding to the service provider, location data, and other document processing device configuration data.

  In another embodiment according to the present invention, the first document processing device 104 receives configuration update data from the server 136 via the computer network 102. Next, the controller 108 associated with the document processing device 104 updates the configuration data according to the configuration data received from the server 136. According to one embodiment of the present invention, the configuration data received from the server 136 includes common identifier data. In a further embodiment according to the present invention, the configuration data also includes an account number associated with the service provider location where the document processing device 104 is located. In another embodiment, the account number corresponds to an account that can be used at multiple locations of the service provider.

  When a user logs into document processing device 104 or 120 via user interface 106 or 122, kiosk 114 or 130, user device 142, or the like, the user is prompted to select a desired document processing operation. Examples of the document processing operation include an e-mail transmission operation, a copy operation, an operation for saving after image scanning, an operation for transmitting an e-mail after image scanning, a facsimile communication operation, a printing operation, and the like. Next, based on the request for the document processing operation selected by the user, controller 108 or 124, kiosk 114 or 130, or other suitable device calculates a fee associated with performing the requested document operation. This cost is then displayed to the user via user interface 106 or 122, display 116 or 132, user device 142, or the like. A user can remotely request a document processing operation at the user device 142 via a secure web portal, thus requesting the document processing operation and accepting a fee at the user device 142 Is possible.

  Transaction identification data is then received from the user in the form of a credit card, a username and password combination, or a prepaid card. The user may enter, for example, an account number associated with the service being charged for, a credit card number, or an account number associated with a prepaid account. Such data entry may be performed by a card reader (not shown) associated with the document processing device 104, 120, kiosk 114, 130, etc. or, for example, user device 142, user Manual input can be through an appropriate keyboard, such as the interfaces 106, 122 or user input devices 118, 134. For received transaction identification data, determine whether the data is unknown, for example, whether the data has been tampered with, cannot be understood, cannot be recognized, or the like Is done first. If the received transaction identification data is unknown data, the document processing device 104 or 120 that receives the document processing request generates an error signal indicating an error to the user by using an appropriate component thereof.

  If the transaction identification data is not unknown data, the controller 108, 124, kiosk 114, 130, or other appropriate component associated with the document processing device 104 or 120 that received the document processing request is received from the user. It is determined whether the identified transaction identification data corresponds to a prepaid account, a credit card account, or a user account such as a business account or personal account. If the transaction identification data corresponds to a credit card or user account, a fee is presented to the user for approval. When a fee approval is received, the document processing device 104 performs the requested action and charges the corresponding account. In one embodiment in accordance with the present invention, the billing for the account communicates to the server 136 transaction details associated with the performed document processing operation for storage in a database stored in the data storage device 138. Including that.

  If it is determined that the transaction identification data corresponds to a prepaid account, the controller 108, 124, kiosk 114, 130 or other appropriate component associated with the document processing device 104 or 120 that received the document processing request is The configuration file is searched for common identifier data corresponding to the account number associated with the location of the service provider where the document processing device 104 or 120 is received. That is, the configuration file includes an account number, such as a 16-digit account number, which is within the service provider's location for document processing operations requested by the user associated with the received payment data. The document processing device 104 or 120 that received the document processing request indicates that the user is to pay the fee at the sales office, for example, the cashier. In other embodiments of the present invention, the configuration file indicates prepaid cards that are acceptable at multiple service provider locations, as opposed to the previous example associated with only a single service provider. A second account number can be included.

  If the transaction identification data received from the user matches the account information stored in the configuration file, the user interface 106 or 122, the display 116 or 132, or the user device 142 may operate as a “counter payment” operation. A prompt indicating that the user must pay a fee associated with processing by the document processing device 104 or 120 that received the document processing request at the service counter location within the service provider location. Display to the user. The requested document processing operation is then performed by the document processing device 104 or 120 that received the document processing request, and transaction details, such as the type of operation, resources used, costs, etc., for storage in the database. Is transmitted to the server 136.

  If the received payment data and the account data in the configuration file do not match, transaction identification data is communicated to server 136 via computer network 102. The server 136 can search the data storage device 138 for data representing the account balance and user information corresponding to the received transaction identification data. The document processing device 104 then receives the balance remaining in the prepaid account from the server 136 via the controller 108 or kiosk 114 and displays it to the user via the user interface 106 or display 116 or the like. If the user approves the billing fee, the document processing operation is performed by the document processing device 104 that has received the document processing request, and the account withdrawal is communicated to the server 136 for storage in the database 138.

  A better understanding of the operation of the system 100 and related components described with reference to FIGS. 1-6 is provided by the following description with reference to FIGS. 7-9. FIG. 7 is a flowchart showing an example of the basic operation of the charged service system for document processing in the embodiment according to the present invention. First, in S702, the commonly controlled document processing station shown in FIG. 1 as the document processing devices 104 and 120 receives a request to execute a document processing operation on the electronic document. For the sake of simplicity and specific description, the following description with reference to FIG. 7 will refer to the case where the first document processing device 104 and the first kiosk 114 are selected. Here, even when other document processing apparatuses and kiosks are selected, the operation shown in FIG. 7 is the same.

  Next, in S704, transaction identification data is received by the document processing device 104 from the associated portable data storage device. A user can provide transaction identification data using a portable data storage device in the form of a magnetic card or IC card that is read by a card reader associated with kiosk 114 or document processing device 104 or the like. In such an embodiment, transaction identification data is communicated from the card reader to the document processing device 104 for subsequent processing. In S706, a device, component associated with the controller 108, kiosk 114 or other document processing device 104 generates billing data corresponding to the requested document processing operation.

  The received transaction identification data is then compared to the common identifier data at S708. Preferably, the common identifier data is stored in association with the document processing device 104, eg, in the data storage device 110. In one embodiment according to the present invention, the common identifier data corresponds to account information. In S710, it is determined whether the transaction identification data matches the common identifier data. If it is determined in S710 that the transaction identification data does not match the common identifier data, the process proceeds to S712 and the debit data associated with the portable data storage device is output. For example, when the portable data storage device is a credit card or a prepaid card, the account associated with the card is charged or deducted with the charge generated in S706. If it is determined in S710 that the transaction identification data matches the common identifier data, the billing data calculated in S706 is output to the associated payment station (S714).

  Referring now to FIG. 8, the operation of the document processing pay service system from the server perspective will be described in an exemplary embodiment according to the present invention. FIG. 8 is a flowchart showing an operation example from the viewpoint of a server of a charged service system for document processing in an exemplary embodiment of the present invention. First, at S802, a document processing request is received by the document processing device 104 or 120 via the associated kiosk 114, 130, user interface 106, 122, user device 142, or the like. For the sake of brevity and concreteness, in the following description with reference to FIG. 8, the first document processing device 104 and its associated components, such as the kiosk 114, user interface 106, controller 108 and Reference is made to the data storage device 110 and the like.

  The document processing device 104 then receives transaction identification data from the portable data storage device at S804. According to an embodiment of the present invention, the transaction identification data includes an account number or an alphanumeric character string. In such an embodiment of the present invention, the portable data storage device includes a magnetic card or IC card, such as a credit card, debit card or smart card, for example. In step S806, the document processing device 104 then generates billing data by calculating the costs associated with performing the requested document processing operation via the controller 108 or kiosk 114.

  In step S808, the controller 108 determines whether the received transaction identification data is unknown data. Alternatively, a determination is made as to whether the received transaction identification data has been altered, cannot be read, cannot be understood, represents an unrecognizable account number, or the like. . If it is determined in S808 that the transaction identification data is unknown, the process proceeds to S810, and the document processing apparatus 104 generates an error signal. According to one embodiment of the present invention, the generated error signal may be in the art including, for example, a visual display on the user interface 106, a display 116, email messaging, text messaging or audible alerts, etc. It is communicated to the user associated with the document processing request via any suitable means known.

  If it is determined in S808 that the transaction identification data is not unknown, the process proceeds to S812, and the received transaction identification data is compared with the common identifier data. According to one embodiment of the invention, the common identifier data corresponds to a local account indicating a counter-payment type transaction, ie a type in which a user provides payment for document processing services at a payment station. If it is determined in S814 that the common identifier data and the received transaction identification data do not match, the process proceeds to S816 and the debit data is output in connection with the portable data storage device. In accordance with one embodiment of the present invention, the credit card account, personal account, or prepaid account represented by the transaction identification data is deducted according to the costs associated with performing the requested document processing operation. If it is determined in S814 that the common identifier data matches the received transaction identification data, the process proceeds to S818, and billing data is output to the payment station. The user is then prompted to provide a payment corresponding to the costs associated with performing the requested document processing operation. The payment station can include, for example, an automated payment station, an assisted payment station, or a cashier.

  Next, referring to FIG. 9, in the exemplary embodiment according to the present invention, the operation from the viewpoint of the document processing apparatus of the document processing pay service system will be described. FIG. 9 is a flowchart showing an operation example from the viewpoint of the document processing apparatus of the paid service system for document processing in the exemplary embodiment according to the present invention. For the sake of brevity and specific description, the following description with reference to FIG. 9 describes the case where it is executed by the second document processing device 120. First, in step S <b> 902, the controller 124 receives user login data via the user interface 122 or the kiosk 130 via the input device 134. According to one particular embodiment of the present invention, the login data corresponds to one or both of a username and password, and the user's information from the local storage, such as the back-end server 136 or data storage device 126. Used to retrieve data. When using a prepaid account, some form of login data is required, such as passing the card of a prepaid account through a card reader. Note that it is not always necessary to first request the user to log in to the document processing apparatus 120. In this case, step S902 is skipped.

  In step S904, the document processing apparatus 120 receives a document processing request corresponding to a user-desired document processing operation. The controller 124, kiosk 130, or other suitable component associated with the document processing device 120 then calculates a fee associated with performing the requested document processing operation at S906. Fees associated with performing a requested document processing operation include, for example, document size, operation type, amount of toner or ink used, resource usage, storage usage, file size, and communication distance Based on etc. The calculated document processing fee is then displayed to the user via the user interface 122 or display 132 for approval.

  Next, in S908, transaction identification data corresponding to the selected payment data is received from the user. In accordance with one embodiment of the present invention, the appropriate transaction identification data is, for example, prepaid account data, credit card data, billing associated with a user, business or department, etc., as is known in the art. Contains possible account data, or other data. Next, in S910, it is determined whether the received transaction data is unknown data. If the data is unknown, the process proceeds to S912 and an error signal is generated and transmitted to the user. If the received transaction data is not unknown, the process proceeds to S914 and whether the received transaction identification data corresponds to a prepaid account, i.e., the account (credit card account or other billable) where the service is charged. It is determined whether or not it corresponds to an account recognized by the controller 124 or the kiosk 130 or the like.

  If it is determined in S914 that the received transaction identification data does not correspond to a prepaid account, the process proceeds to S916, where it is determined whether the user has approved a fee associated with performing the requested document processing operation. Done. If the fee is not approved, the process ends. When the fee is approved, the document processing apparatus 120 executes the requested service in S918. Thereafter, the controller 124, kiosk 130, or other suitable component associated with the document processing device 120 may be charged to a credit card account, addition to a bill corresponding to a user, business or department account, etc., at S920. After transferring the received payment data to the back-end server 136, the process ends.

  Returning to S914, the kiosk 130 or the controller 124 determines that the transaction identification data received from the user corresponds to a 16-digit account number that can be recognized as a prepaid account number and not a credit card number. The process proceeds to S922, and the common identifier data is searched. The transaction identification data is then compared with the common identifier data at S924, and a determination is made at S926 as to whether the transaction identification data and the common identifier data match. That is, it is determined whether or not the 16-digit account number represented by the transaction identification data corresponds to the 16-digit account number represented by the common identifier data. When the transaction identification data matches the common identifier data, the process proceeds to S928, and the user is prompted to pay for the service at the sales floor when the service requested by the user is completed via the user interface 122 or the display 132 or the like. In step S930, the document processing apparatus 120 executes the requested operation. Detailed data relating to the transaction, i.e., cost, resource, device identification information, date and time, service provider identification information, etc. are collected, and in S932 the collected transaction data is stored in a database associated with the data storage device 138. To the server 136 via the computer network 102. Data corresponding to the transaction immediately after completion is stored in association with the service provider identification data so that subsequent transactions can be settled, eg, per provider base.

  Returning to S926, if it is determined that the common identifier data and the transaction identification data do not match, in S934, the controller 124 or kiosk 130 or the like transmits the received transaction identification data to the server 136. In accordance with one embodiment of the present invention, server 136 receives transaction identification data, accesses a database stored in data storage device 138, and accounts information corresponding to the transaction identification data received from document processing device 120. Search for. The account information corresponding to the transaction identification data includes, for example, an account balance corresponding to the amount remaining in the account. In step S936, the account balance is transmitted to the document processing apparatus 120. Thereafter, in S938, the account balance is displayed to the user via the user interface 122 or display 132, indicating the amount remaining on the prepaid card.

  Next, in S940, a determination is made as to whether the fee calculated in S906 has been approved by the user for execution of the requested document processing operation. In other words, it is determined whether the user has agreed that the amount calculated for the execution of the document processing operation will be deducted from the account specified by the prepaid card. If the fee is not approved by the user, the process ends. According to one embodiment of the present invention, controller 124 or kiosk 130 or the like determines whether the amount remaining on the prepaid card is sufficient to cover the fee for the requested operation. When the prepaid card level is insufficient, the user is prompted to cancel the action or select a new payment method. If the fee is approved by the user in S940, the process proceeds to S930, and the document processing apparatus 120 executes the requested document processing operation. Then, detailed data about the transaction, i.e., cost, resource, device identification information, date and time, service provider identification information, etc. are collected, and the collected transaction data is stored in a database associated with the data storage device 138 in S932. To be transmitted to the server 136 via the computer network 102. As previously mentioned, the data corresponding to the transaction is stored in association with the service provider identification data so that subsequent transaction settlements, for example, on a provider basis, document processing device basis, location basis, etc. It becomes possible.

  The present invention may be in the form of code intermediate source and object code, such as source code, object code, partially compiled form, or any other form suitable for use in embodiments of the present invention. Including other computer programs. A computer program can be a stand-alone application, a software component, a script, or a plug-in to another application. The computer program for carrying out the present invention transmits a computer program such as a storage medium such as ROM and RAM, an optical recording medium such as a CD-ROM, and a magnetic recording medium such as a floppy (registered trademark) disk. Can be embodied on a carrier that is any entity or device capable of transmitting or can be transmitted by any carrier such as an electrical or optical signal transmitted by electrical or optical cable, or by radio or other means it can. The computer program can also be downloaded from the server via the Internet. The function of the computer program can also be incorporated in an integrated circuit. Any and all embodiments that contain code that causes a computer or processor to substantially execute the described principles of the invention are within the scope of the invention.

  The foregoing description of the preferred embodiment of the present invention has been presented for purposes of illustration and description. The description is not exhaustive and is not intended to limit the invention to the form disclosed. Obvious modifications or variations are possible in light of the above disclosure. For example, the systems and methods described in the description of embodiments according to the present invention are applicable to a number of different fields using remote transaction monitoring, including, for example, communication, general purpose computing or data processing, etc. The present invention is not limited to application to document processing. The embodiments best illustrate the principles of the invention and its practical applications, so that those skilled in the art can use the invention in various modifications in various embodiments suitable for the particular intended use. Was selected and explained. It will be apparent that all such modifications and variations can be made by those skilled in the art within the principles and scope of the invention as set forth in the appended claims. Within the scope of the invention as defined.

It is an example of a structure of the whole pay service system of document processing according to embodiment by this invention. It is a hardware structural example of the document processing apparatus with which the operation | movement of the system of embodiment by this invention is performed. It is a structural example of the functional block of the document processing apparatus with which operation | movement of the system of embodiment by this invention is performed. It is a figure for demonstrating the structural example of the hardware of the controller with which the operation | movement of the system of embodiment by this invention is performed. It is a figure for demonstrating the structural example of the functional block of the controller with which the operation | movement of the system of embodiment by this invention is performed. It is a hardware structural example of the server with which the operation | movement of the system of embodiment by this invention is performed. 5 is a flowchart showing a basic operation example of a document processing pay service system in the embodiment according to the present invention. 6 is a flowchart showing an operation example from the viewpoint of a server of a fee-based service system for document processing in an embodiment according to the present invention. 6 is a flowchart showing an operation example from the viewpoint of a document processing apparatus of a fee-based service system for document processing in an embodiment according to the present invention.

Explanation of symbols

100 System 102 Computer Network, Distributed Communication System 104, 120 Document Processing Device, MFP
106, 122 User interface 108, 124 Controller 110, 126, 138 Data storage 112, 128, 140, 144 Communication link 114, 130 Kiosk 116, 132 Display 118, 134 User input device 136 Back-end server, server 142 User Device 200, 300 Document processing device 202, 402, 602 Processor 204, 404, 604 Read-only memory, ROM
206, 406, 606 RAM
208, 408, 608 Storage interface 210, 410, 610 Network interface subsystem 212, 412, 612 Bus 214, 316, 414, 614 Network interface card 216, 416, 616 Disk drive 218, 418, 618 Wireless interface 220, 420, 620 Physical network 222, 622 Optional input / output interface 224 User input / output panel 226 Print interface 228 Copy interface 230 Image scanning interface 232 Facsimile interface 234, 304 Print engine 236 Copy engine 238, 308 Image scanning engine 240, 306 Facsimile engine 31 0 console panel 314 device driver 318, 320, 322, 324, 326 driver 400 controller 422 document processor interface 424 copy hardware 426 image scanning hardware 428 printing hardware 430 facsimile hardware 432 document processing hardware 502, 302 Document processing engine 504 Print function unit 506 Facsimile communication function unit 508 Image scanning function unit 510 User interface panel 512 Job queue 514 Network service function unit 516 Image processor 518 Job analysis unit 520 Client side network service function 522 Client device service unit 600 server

Claims (12)

A document processing station for processing documents;
A payment station associated with each of the document processing stations and including means for receiving billing data from each of the document processing stations;
The document processing station is
Means for receiving a document processing request for an electronic document;
Means for generating the billing data associated with the document processing request;
Means for accessing the common identifier data;
Means for receiving transaction identifier data from the portable data storage means;
Means for comparing the transaction identification data with the common identifier data;
Means for outputting the billing data when the transaction identifier data is consistent with the common identifier data;
A document processing chargeable service system comprising: means for communicating debit data associated with the portable data storage means when the transaction identifier data does not match the common identifier data.   2. The document processing pay service system according to claim 1, further comprising means for generating an error signal when the transaction identifier data is unknown data.   2. The fee processing service system for document processing according to claim 1, further comprising means for outputting the billing data to the payment station.   2. The document processing chargeable service system according to claim 1, wherein the portable data storage means is a debit card.   2. The document processing pay service system according to claim 1, wherein the billing data includes data corresponding to a completed document processing operation.   2. The document processing pay service system according to claim 1, wherein the payment station includes means for receiving a payment corresponding to the received billing data. Receiving a document processing request for an electronic document at a document processing station;
Generating billing data associated with the document processing request;
Accessing the common identifier data;
Receiving transaction identification data from a portable data storage device;
Comparing the transaction identification data with the common identifier data;
Outputting the billing data to an associated payment station when the transaction identifier data matches the common identifier data;
Paying for debit data associated with the portable data storage device when the transaction identifier data does not match the common identifier data.   8. The paid service method for document processing according to claim 7, further comprising a step of generating an error signal when the transaction identifier data is unknown data.   8. The fee processing method for document processing according to claim 7, further comprising the step of outputting the billing data to the payment station.   8. The document processing pay service method according to claim 7, wherein the portable data storage device is a debit card.   8. The document processing chargeable service method according to claim 7, wherein the billing data includes data corresponding to a completed document processing operation.   8. The document processing pay service method according to claim 7, wherein the payment station includes means for receiving payment corresponding to the received billing data.

Images