JP4881915B2 - Printing system, print management server, control method therefor, and program - Google Patents

Printing system, print management server, control method therefor, and program Download PDF

Info

Publication number
JP4881915B2
JP4881915B2 JP2008152926A JP2008152926A JP4881915B2 JP 4881915 B2 JP4881915 B2 JP 4881915B2 JP 2008152926 A JP2008152926 A JP 2008152926A JP 2008152926 A JP2008152926 A JP 2008152926A JP 4881915 B2 JP4881915 B2 JP 4881915B2
Authority
JP
Japan
Prior art keywords
identification information
user identification
print
print data
printer
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
JP2008152926A
Other languages
Japanese (ja)
Other versions
JP2009301185A (en
JP2009301185A5 (en
Inventor
敏幸 上原
拓矢 宮里
Original Assignee
キヤノンソフトウェア株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by キヤノンソフトウェア株式会社 filed Critical キヤノンソフトウェア株式会社
Priority to JP2008152926A priority Critical patent/JP4881915B2/en
Publication of JP2009301185A publication Critical patent/JP2009301185A/en
Publication of JP2009301185A5 publication Critical patent/JP2009301185A5/ja
Application granted granted Critical
Publication of JP4881915B2 publication Critical patent/JP4881915B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Description

The present invention includes a printer including a reading unit reading a storage medium, a printing system print management server for managing correspondence print data and user identification information are connected via a network to a print server and its control method and program .

  Conventionally, a so-called “pull print (accumulated printing) that enables only an authenticated user to output print data from the printing apparatus by making a print request to the print data temporarily accumulated on the server from the printing apparatus. "Is proposed. Thus, print data corresponding to the authenticated user can be output from a desired printing apparatus.

For example, in Patent Document 1, an IC card authentication process is performed by a multifunction peripheral, a list of print data of authenticated users is displayed on a display unit of a printing apparatus, and print data selected on the display is displayed on a print management server. A print system is disclosed in which print data specified by a user authenticated by sending a print command to a print server storing the specified print data can be printed by a desired printing apparatus.
JP 2006-99714 A

  However, if the printer does not have a display unit (even if there is a display unit, the performance of the display unit is poor and the list cannot be displayed and cannot be selected), the user cannot select and print the data he wants to print. There was a problem that no print data was printed. Further, in Patent Document 1, when print data is selected and a print request is made, it is output regardless of whether or not the user is near the printer, and it is difficult to perform high-security printing.

Accordingly, an object of the present invention is to provide a mechanism capable of performing secure printing by receiving user identification information from a printer again and outputting it to print data instructed to be output from a portable terminal .

In order to achieve the above object, a first invention is a printing system in which a printer including a reading unit that reads a storage medium and a print management server that manages print data in association with user identification information are connected via a network. The printer includes user identification information transmitting means for transmitting, to the print management server, user identification information for identifying a user obtained by reading a predetermined area of a storage medium. Management means for managing user identification information and information for specifying a portable terminal associated with the user identification information, user identification information receiving means for receiving the user identification information from the printer, and user identification information receiving means List information including print data identification information of print data associated with the user identification information received in In accordance with the user identification information received by the user identification information receiving means and the user identification information managed by the management means, a list information transmission means for transmitting to the portable terminal corresponding to the information for identifying the portable terminal, and the print data identification information A print request receiving unit that receives print data identification information instructed to be printed from the portable terminal that has transmitted the list information, and after receiving the print data identification information instructed to print by the print request receiving unit, Waiting means for waiting to receive user identification information from the printer again, and the print request received by the print request receiving means when the waiting means waits and the user identification information is received again by the user identification information receiving means. Print data output command means for issuing an output command to print the print data corresponding to the data identification information with the printer; Characterized in that it obtain.

In addition, the management unit manages the user identification information, the portable terminal, and the printer that has received the user identification information in association with each other, and the print data output command unit waits at the standby unit The user identification information receiving unit receives the user identification information again from the printer managed by the management unit, thereby issuing an output command of print data corresponding to the print data identification information.

The storage medium is provided in a portable terminal, and the user identification information transmitting means transmits user identification information obtained by holding the portable terminal over the reading unit to the print management server, and outputs the print data. The command means receives user identification information obtained by holding the portable terminal over the reading unit by the user identification information receiving means from the printer, and prints the print data corresponding to the print data identification information. An output command is given.

The standby unit prepares printing of print data corresponding to the print data identification information instructed to be printed, and the print data output command unit issues an output command of the print data prepared for printing. To do.

The preparation for printing is to generate print data to be transmitted to the printer, and the print management server indicates that the generation of print data to be output by the print data output instruction means has been completed. Printing preparation notifying means for notifying at least one of the printer and the portable terminal.

The print management server includes first determination means for determining whether or not the printer has a display unit, and the list information transmission unit includes the display unit in the printer by the first determination unit. If it is determined that the list information including the print data identification information of the print data is transmitted to the printer, and if it is determined that there is no display unit, the list information including the print data identification information of the print data is It transmits to a portable terminal, It is characterized by the above-mentioned.

The management unit manages portable terminal identification information of a portable terminal corresponding to user identification information, and the print management server sends print data of the print data to the portable terminal according to the portable terminal identification information of the portable terminal. A second determination unit configured to determine whether to transmit list information including identification information; and when the list information transmission unit determines that the second determination unit transmits to the portable terminal, List information including print data identification information of print data is transmitted to the portable terminal of the portable terminal identification information.

When the first determination unit determines that the printer does not have a display unit and the second determination unit determines not to transmit to the portable terminal, the list information is output. An output command for print data associated with the user identification information is issued without transmitting the list information by the transmission means.

Further, the print management server includes an unprinted print data number notifying unit for notifying at least one of the printer and the portable terminal of the number of unprinted print data.

Further, the print management server receives the user identification information by the user identification information receiving means each time the print data output command means reads a predetermined area of the storage medium by the printer, and displays the user identification information. Each time the data is received, a print data output command corresponding to the print data identification information instructed to be printed is issued.

In addition, when the print management server receives the user identification information again by the user identification information reception unit while waiting by the standby unit, the print management server identifies the received printer and the user identification by the user identification information reception unit first. A printer determination unit that determines whether or not the printer that received the information matches, and the print data output command unit determines that the printer determination unit does not match the user identification information reception unit In this case, a print data output command corresponding to the print data identification information instructed to be printed is issued using the printer that has received the user identification information again as an output destination.

In order to achieve the above object, a second invention includes a printer and a network that include a reading unit that reads a storage medium, and transmits user identification information for specifying a user obtained by reading a predetermined area of the storage medium. A print management server for managing print data in association with user identification information, connected via the management means for managing user identification information and information for identifying a mobile terminal associated with the user identification information; List information including print data identification information of print data associated with user identification information received by the user identification information receiving means and user identification information receiving means for receiving the user identification information from the printer, According to the user identification information received by the user identification information receiving means and the user identification information managed by the management means, List information transmitting means for transmitting to the portable terminal corresponding to the information for specifying the end, and print request receiving means for receiving the print data identification information instructed for printing from the portable terminal that transmitted the list information including the print data identification information And after receiving the print data identification information instructed to be printed by the print request receiving means, the standby means for waiting again to receive the user identification information from the printer; A print data output command means for instructing to output print data corresponding to the print data identification information received by the print request receiving means by the printer when the user identification information is received again by the user identification information receiving means; It is characterized by providing.

In order to achieve the above object, a third invention is a printing system in which a printer including a reading unit that reads a storage medium and a print management server that manages print data in association with user identification information are connected via a network. A control method, wherein the printer executes user identification information transmission step of transmitting user identification information for identifying a user obtained by reading a predetermined area of a storage medium to the print management server, and A management step in which the print management server manages user identification information and information for specifying a portable terminal associated with the user identification information; a user identification information receiving step for receiving the user identification information from the printer; and the user Print data of the print data associated with the user identification information received in the identification information receiving step List information transmission including list information including other information according to the user identification information received in the user identification information reception step and the user identification information managed in the management step to the portable terminal corresponding to the information identifying the portable terminal A print request receiving step for receiving print data identification information instructed to print from a portable terminal that has transmitted the list information including the print data identification information, and the print data instructed for printing by the print request receiving step. After receiving the identification information, when waiting for receiving the user identification information again from the printer, and waiting in the standby step, and receiving the user identification information again by the user identification information receiving step, Print data corresponding to the print data identification information received in the print request receiving step; In order to print with serial printer, and executes the print data output command step of outputting instruction.
In order to achieve the above-described object, a fourth invention includes a reading unit that reads a storage medium, and transmits a user identification information for specifying a user obtained by reading a predetermined area of the storage medium. And a print management server control method for managing print data in association with user identification information, wherein the print management server connects the user identification information and a portable terminal associated with the user identification information. Management step for managing information to be specified, user identification information receiving step for receiving the user identification information from the printer, and printing of print data associated with the user identification information received in the user identification information receiving step The list information including the data identification information, the user identification information received in the user identification information receiving step and the In accordance with the user identification information managed in the management step, a list information transmission step for transmitting to the portable terminal corresponding to the information for identifying the portable terminal, and a printing instruction from the portable terminal that transmitted the list information including the print data identification information The print request receiving step for receiving the print data identification information and the print request receiving step for receiving the print data identification information instructed for printing, and then waiting to receive the user identification information from the printer again. When waiting in the waiting step and the waiting step, and receiving the user identification information again in the user identification information receiving step, print data corresponding to the print data identification information received in the print request receiving step is printed by the printer To execute a print data output instruction step for instructing output To.

In order to achieve the above-mentioned object, a fifth invention is a printing system in which a printer including a reading unit that reads a storage medium and a print management server that manages print data in association with user identification information are connected via a network. A program that causes the printer to function as user identification information transmitting means for transmitting user identification information for identifying a user obtained by reading a predetermined area of a storage medium to the print management server, A management server for managing user identification information and information for identifying a mobile terminal associated with the user identification information; user identification information receiving means for receiving the user identification information from the printer; and the user identification Print data identification information of print data associated with the user identification information received by the information receiving means List information transmitting means for transmitting the list information to the portable terminal corresponding to the information identifying the portable terminal according to the user identification information received by the user identification information receiving means and the user identification information managed by the management means; Print request receiving means for receiving print data identification information instructed to print from the portable terminal that has transmitted the list information including the print data identification information, and the print data identification information instructed for printing by the print request receiving means. After the reception, when the user identification information is received again by the user identification information receiving unit, the print request is received when waiting for receiving the user identification information from the printer again. The print data corresponding to the print data identification information received by the receiving means is printed out to be printed by the printer. Characterized in that function as data output instruction means.
In order to achieve the above-described object, a sixth invention includes a reading unit that reads a storage medium, and transmits a user identification information for specifying a user obtained by reading a predetermined area of the storage medium. And a print management server program for managing print data in association with user identification information, wherein the print management server is connected to the user identification information and a mobile terminal associated with the user identification information. Management means for managing information to be identified, user identification information receiving means for receiving the user identification information from the printer, and printing of print data associated with the user identification information received by the user identification information receiving means List information including data identification information is received by the user identification information received by the user identification information receiving means and the management means. Print data instructed to be printed from the list information transmitting means for transmitting to the portable terminal corresponding to the information specifying the portable terminal according to the user identification information to be managed, and the portable terminal that has transmitted the list information including the print data identification information Print request receiving means for receiving identification information; and standby means for waiting again to receive user identification information from the printer after receiving the print data identification information instructed to be printed by the print request receiving means. In order to print on the printer the print data corresponding to the print data identification information received by the print request receiving means when waiting in the waiting means and receiving the user identification information again by the user identification information receiving means, It functions as print data output command means for commanding output.

According to the present invention, it is possible to perform secure printing by receiving user identification information from the printer again and outputting it to the print data instructed to be output from the portable terminal .

[First Embodiment]
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a system configuration diagram illustrating an example of a configuration of a printing system to which a print management server and a printer of the present invention can be applied.
As shown in FIG. 1, the printing system of this embodiment includes one or a plurality of client terminals 400 (for example, for each user), a plurality of printers 300 (a printer 300a, a printer 300b,...), A print management server 100, and an authentication server. 200 is connected via a local area network (LAN) 600, and the print management server 100 is configured to communicate with the mobile terminal 500.

  The client terminal 400 is installed with form software that obtains a form and text data necessary for form generation from a server (not shown) and overlays to generate a form. The form software transmits the generated form to the print management server together with a form print execution command and user identification information using communication such as SOAP. In this embodiment, a form is considered as print data, and the following explanation will be given. However, the print data may be data that can be normally printed by a printer, and can be a general document created by word processing software or image editing. This includes images created with software.

  The print management server 100 is installed with a printer driver, accumulates the received forms (print data) in a form management database (FIG. 5 described later), and sends the print data to the printer 300 via the printer driver based on the output instruction. Send.

  The authentication server 200 stores an authentication table (FIG. 8 to be described later), and in response to an authentication request made by holding the portable terminal 500 over a card reader (319 in FIG. 3 to be described later) of the printer 300. Authentication processing is performed using.

  Hereinafter, a hardware configuration of an information processing apparatus applicable to the client terminal 400, the print management server 100, and the authentication server 200 illustrated in FIG. 1 will be described with reference to FIG.

  FIG. 2 is a block diagram illustrating a hardware configuration of an information processing apparatus applicable to the client terminal 400, the print management server 100, and the authentication server 200 illustrated in FIG.

  In FIG. 2, reference numeral 201 denotes a CPU, which loads various programs and the like necessary for execution of processing from the ROM 202 or the external memory 211 to the RAM 203 and executes the loaded programs to realize various operations and is connected to the system bus 204. Centrally control each device and controller.

  Further, the ROM 202 or the external memory 211 is necessary to realize a BIOS (Basic Input / Output System) or an operating system program (hereinafter referred to as an OS) that is a control program of the CPU 201 and a function executed by each server or each PC. Various programs to be described later are stored. A RAM 203 functions as a main memory, work area, and the like for the CPU 201.

  An input controller 205 controls input from a keyboard (KB) 209 or a pointing device such as a mouse (not shown). A video controller 206 controls display on a display device such as a CRT display (CRT) 210. In FIG. 2, although described as CRT 210, the display device is not limited to the CRT, but may be another display device such as a liquid crystal display. These are used by the administrator as needed.

  Note that the CPU 201 enables display on the CRT 210 by executing outline font rasterization processing on a display information area in the RAM 203, for example. In addition, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the CRT 210.

  A memory controller 207 is connected via an adapter to a hard disk (HD), flexible disk (FD), or PCMCIA card slot for storing a boot program, various applications, font data, user files, editing files, various data, and the like. The access to the external memory 211 such as a compact flash (registered trademark) memory is controlled.

  A communication I / F controller 208 is connected to and communicates with an external device via a network (for example, the LAN 600 shown in FIG. 1), and executes communication control processing on the network. For example, communication using TCP / IP is possible.

  Various programs to be described later for realizing the present invention are recorded in the external memory 211 and executed by the CPU 201 by being loaded into the RAM 203 as necessary. Furthermore, definition files and various information tables used when executing the program are also stored in the external memory 211, and a detailed description thereof will be described later.

  Next, the hardware configuration of the controller unit 316 that controls the printer 300 shown in FIG. 1 will be described with reference to FIG.

  FIG. 3 is a block diagram illustrating an example of a hardware configuration of the controller unit 316 of the printer 300 illustrated in FIG.

  In FIG. 3, reference numeral 316 denotes a controller unit which is connected to a scanner unit 314 functioning as an image input device and a printer unit 312 functioning as an image output device, while being connected to a LAN (for example, the LAN 600 shown in FIG. 1) or a public line network. By connecting to (WAN) (for example, PSTN or ISDN), input / output of image data and device information is performed.

  In the controller unit 316, reference numeral 301 denotes a CPU, which is a processor that controls the entire system. A RAM 302 is a system work memory for the CPU 301 to operate, and is also a program memory for recording a program and an image memory for temporarily recording image data.

  A ROM 303 stores a system boot program and various control programs. A hard disk drive (HDD) 304 stores various programs for controlling the system, image data, and the like.

  An operation unit interface (operation unit I / F) 307 is an interface unit with the operation unit 308. Further, the operation unit I / F 307 serves to transmit the key information (for example, pressing of the start button) input from the operation unit 308 to the CPU 301.

305 is a network interface (Network
I / F) connects to a network (LAN) and inputs / outputs data. A modem (MODEM) 306 is connected to the public line network and inputs / outputs data such as FAX transmission / reception.

  Reference numeral 318 denotes an external interface (external I / F), which is an I / F unit that accepts external inputs such as USB, IEEE 1394, printer port, and RS-232C. In this embodiment, a card reader 319 for reading an IC card (storage medium, 419 in FIG. 4 described later) of the portable terminal 500 required for authentication is connected to the external I / F unit 318. The CPU 301 can control reading of information from the IC card by the card reader 319 (reading unit) via the external I / F 318, and can acquire information read from the IC card. The above devices are arranged on the system bus 309. Note that not only the card reader but also a fingerprint reader (not shown) may be provided. In this case, a value is calculated from the fingerprint read by the fingerprint reader and used as the calculated value and identification information.

320 is an image bus interface (IMAGE).
BUS I / F), which is a bus bridge that connects a system bus 309 and an image bus 315 that transfers image data at high speed and converts a data structure.

  The image bus 315 is configured by a PCI bus or IEEE1394. On the image bus 315, in addition to the image bus interface 320, a raster image processor (RIP) 310, a printer interface (printer I / F) 311, a scanner interface (scanner I / F) 313, an image processing unit 317, Is placed.

  A raster image processor (RIP) 310 develops vector data such as a PDL code into a bitmap image. A printer interface (printer I / F) 311 connects the printer unit 312 and the controller unit 316 and performs synchronous / asynchronous conversion of image data. A scanner interface (scanner I / F) 313 connects the scanner unit 314 and the controller unit 316 and performs synchronous / asynchronous conversion of image data.

  An image processing unit 317 corrects, processes, and edits input image data, and performs printer correction, resolution conversion, and the like on print output image data. In addition, the image data is rotated, and compression / decompression processing such as JPEG for multi-valued image data and JBIG, MMR, MH, etc. is performed for binary image data.

  The scanner unit 314 illuminates an image on paper as a document and scans it with a CCD line sensor, thereby converting it into an electrical signal as raster image data. The original paper is set on the tray of the original feeder, and when the apparatus user gives a reading start instruction from the operation unit 308, the CPU 301 gives an instruction to the scanner unit 314, and the original feeder feeds the original paper one by one to copy the original image. Perform a read operation.

  The printer unit 312 is a part that converts raster image data into an image on paper. The method includes an electrophotographic method using a photosensitive drum or a photosensitive belt, an ink jet method in which ink is ejected from a micro nozzle array and an image is directly printed on a sheet, and any method may be used. The activation of the printing operation is started by an instruction from the CPU 301. The printer unit 312 has a plurality of paper feed stages so that different paper sizes or different paper orientations can be selected, and has a paper cassette corresponding thereto.

  The operation unit 308 has an LCD display unit, and a touch panel sheet is pasted on the LCD display unit. The LCD display unit displays the operation screen of the system, and when the displayed key is pressed, the position information is transmitted to the CPU 301 via the operation unit I / F 307. The operation unit 308 includes, for example, a start key, a stop key, a reset key, and the like as various operation keys.

  The display unit has different display performance depending on the printer, a printer that can be operated via a touch panel, a printer that simply has a liquid crystal screen and displays a character string (displaying the print status and the name of the document being printed), or a display There are printers or the like that do not have a section and have only operation keys, but any method may be used.

  Here, the start key of the operation unit 308 is used when starting a document image reading operation. Further, the stop key of the operation unit 308 functions to stop the operation in operation. The reset key is used when initializing settings from the operation unit.

  The card reader 319 reads information stored in the IC card under the control of the CPU 301 and notifies the CPU 301 of the read information via the external I / F 318. The reading method may be a non-contact type or a contact type. In this embodiment, a configuration in which a card reader is externally attached as a reading unit will be described. However, a configuration in which a reading unit is provided in the printer main body may be used.

  With the above configuration, the printer 300 transmits information read from the IC card via the card reader 319 and image data read from the scanner unit 314 via the LAN, and print data received via the LAN. It can be printed out by the printer unit 312.

  Further, the image data read from the scanner unit 314 can be fax-transmitted via the public line network by the modem 306, and the image data received via the public line network can be output by the printer unit 312.

  Hereinafter, the hardware configuration of the mobile terminal 500 shown in FIG. 1 will be described with reference to FIG. The portable terminal only needs to have a transmission / reception unit that transmits and receives data, a display unit that displays various types of information, and an input unit that can be selected based on the display information. For example, a mobile phone or a PDA (Personal Digital Assistant). In this embodiment, a case where a mobile phone is used as a mobile terminal will be described.

  FIG. 4 is a block diagram illustrating a hardware configuration of the mobile terminal 500 of the present embodiment illustrated in FIG.

  As shown in FIG. 4, the mobile terminal 500 includes a control unit 411, a reception unit 412, a transmission unit 413, a transmission / reception unit 414, a display unit 415, an input unit 416, a ROM 417, a RAM 418, and an IC. Card 419.

  The control unit 411 operates according to a program stored in the ROM 417, and controls the operation of the entire mobile terminal.

  The reception unit 412 includes a speaker and the like, converts a digital audio signal supplied from the control unit 411 into an analog audio signal, and emits sound from the speaker. The transmitter 413 includes a microphone and the like, captures voice data to be transmitted, converts it into a digital signal, and supplies the digital signal to the controller 411.

  The transmission / reception unit 414 performs wireless communication with the print management server 100 via an antenna. The display unit 415 displays various information.

  The wireless communication between the portable terminal 500 and the print management server 100 is configured to be performed via a base station (not shown).

  The input unit 416 includes dial buttons and inputs various instructions. The ROM 417 stores the operation program of the control unit 411 and fixed data.

  The RAM 418 is backed up by a battery, functions as a work area for the control unit 411, and temporarily stores information acquired from the outside.

  The IC card 419 is a storage medium constituted by an IC chip, and predetermined identification information is written therein. The predetermined identification information is information such as a production number or an individual. In addition, communication is performed with a card reader 319 provided in the printer 300. In this embodiment, the IC card 419 is built in the portable terminal 500.

  The data stored in the external memory 211 of the print management server 100 shown in FIG. 1 will be described below with reference to FIGS.

  FIG. 5 is a schematic diagram showing an example of a form management database stored in the external memory 211 of the print management server 100 shown in FIG.

  As shown in FIG. 5, the form management database includes a time stamp 501, a user name 502, a document name 503, a print state 504, and form data 505 associated with each other.

  The time stamp 501 indicates the date and time when the print management server 100 received the form data 505. A user name 502 and a document name 503 correspond to the user name (user identification information) and document name received together with the form data 505 from the client terminal 400. A print state 504 indicates a print state of the form data 505. For example, it has not been output or has been output. The form data 505 is form data created at the client terminal 400 and transmitted to the print management server 100.

  Note that this form management database is registered in the print management server 100 from the client terminal 400 as described above.

  FIG. 6 is a schematic diagram illustrating an example of a printer driver related table stored in the external memory 211 of the print management server 100 illustrated in FIG.

  As shown in FIG. 6, the printer driver related table includes a printer name 601, a printer IP address 602, and a printer driver name 603.

  A printer name 601 and a printer driver name 603 are provided for each printer and printer driver. The printer IP address is an IP address assigned to each printer.

  It is assumed that this printer driver related table is registered in advance in the external memory 211 of the print management server 100.

  FIG. 7 is a schematic diagram illustrating an example of a printer display unit presence / absence table stored in the external memory 211 of the print management server 100 illustrated in FIG. 1.

  The printer display portion presence / absence table is composed of a printer name, a printer IP address, and display portion presence / absence information. The printer name and printer IP address are provided for each printer. The display unit presence / absence information indicates whether or not each printer has a display unit (which can display a form data list).

  Note that this printer display unit presence / absence table is registered in the external memory 211 of the print management server 100 in advance.

  Hereinafter, the authentication table stored in the external memory 211 of the authentication server 200 shown in FIG. 1 will be described with reference to FIG.

  FIG. 8 is a schematic diagram showing an example of an authentication table stored in the external memory 211 of the authentication server 200 shown in FIG.

  As shown in FIG. 8, the authentication table is composed of a manufacturing number 801, a user name 802, a mail address 803, a department ID 804, a department password 805, administrator authority 806, portable terminal identification information 807, and the like.

The production number 801 is the production number of the IC card 419 built in the portable terminal 500, and is information for identifying the IC card (storage medium). A user name 802 and a mail address 803 are a user name and a mail address set by the user. A department ID 804 and a department password 805 are an ID and a password provided for each department to which the user belongs. The administrator authority 806 is information on the administrator authority that the user has. The mobile terminal identification information 807 is information for identifying individual mobile terminals, and is, for example, a telephone number or an IP address.
The mobile terminal 500 is configured so that an IC card for specifying a user (user) who owns the mobile terminal 500 can be inserted. The IC card can be simply replaced with another mobile terminal. This is to allow other mobile terminals to be used in the same way as their mobile terminals. That is, it is also possible to use the identification number of the IC card for specifying this user as portable terminal identification information.

  Hereinafter, with reference to the flowchart of FIG. 9, the registration process of the manufacturing number 801 and the mobile terminal identification information 807 in the authentication table shown in FIG. 8 will be described. In the present embodiment, the authentication server 200 is connected to the card reader for reading the IC card 419 built in the portable terminal 500 (similar to the card reader 319 in FIG. 3) via an external interface (for example, USB) (not shown). Function) is connected. Then, the CPU 201 of the authentication server 200 can control the information reading of the IC card 419 by the card reader, and can acquire the information read from the IC card 419.

  FIG. 9 is a flowchart showing an example of a first control processing procedure in the present invention, and corresponds to the authentication table registration processing in the present invention.

  In the figure, S1 corresponds to the step of the mobile terminal 500, and is realized by the control unit 411 of the mobile terminal 500 executing a program stored in the ROM 417.

  S2 to S3 correspond to the steps of the authentication server 200, and are realized by the CPU 201 of the authentication server 200 executing a program stored in the external memory 211 on the RAM 203.

  First, in step S <b> 1, the control unit 411 of the mobile terminal 500 transmits mobile terminal identification information (for example, a telephone number or an IP address) stored in the ROM 417 or the like of the mobile terminal 500 to the authentication server 200.

  In step S <b> 2, the CPU 201 of the authentication server 200 receives mobile terminal identification information transmitted from the mobile terminal 500.

  During a predetermined period after reception of the mobile terminal identification information, the CPU 201 of the authentication server 200 reads the IC card 419 built in the mobile terminal 500 by a card reader.

  When portable terminal 500 is held over a card reader, CPU 201 of authentication server 200 detects this and reads the manufacturing number of IC card 419 (S3).

  Next, in step S4, the CPU 201 of the authentication server 200 associates the mobile terminal identification information received in step S2 with the manufacturing number read in step S3, and manufactures the authentication table shown in FIG. 6 using the manufacturing number as a key. Registered in the number 801, portable terminal identification information 807.

  Even if the administrator does not execute the processing shown in FIG. 9, the method of registering the manufacturing number 801 and the mobile terminal identification information 807 in the authentication table by manual operation or the like can be used. Is feasible.

  Hereinafter, the printing process according to the present invention will be described with reference to the flowcharts of FIGS. 10A, 10B, and 10C.

  FIG. 10A, FIG. 10B, and FIG. 10C are flowcharts showing an example of the second control processing procedure in the present invention, and correspond to processing related to printing based on the print instruction in the present invention.

  In FIG. 10A, S101 to S103 correspond to the steps of the authentication server 200, and are realized by the CPU 201 of the authentication server 200 executing a program stored in the external memory 211 on the RAM 203.

  10B, S201 to S217 and S501 to S508 in FIG. 10C correspond to the steps of the print management server 100, and the CPU 201 of the print management server 100 executes the program stored in the external memory 211 on the RAM 203. It is realized by doing.

  In FIG. 10C, S501 to S508 indicate steps of the main thread program that is always executed by the CPU 201 of the print management server 100. In FIG. 10B, S201 to S217 are the CPU 201 of the print management server 100. When actually controlling printing, each step of a sub-thread program that can be executed in parallel for each series of print processing processes is shown.

  In FIG. 10B, S301 to S314 correspond to the steps of the mobile terminal 500, and are realized by the control unit 411 of the mobile terminal 500 executing a program stored in the ROM 417.

  In FIG. 10A, S401 to S419 correspond to the steps of the printer 300 (here, any printer may be described as the printer 300a), and the CPU 301 of the printer 300a executes a program stored in the ROM 303. Is realized.

  In FIGS. 10A, 10B, and 10C, I601 to I609 and I701 to I703 are symbols for association to indicate the connection of data passing between the steps in FIGS. 10A, 10B, and 10C. .

  10A, 10B, and 10C, the solid line that connects the steps indicates the order of the processing flow, and the broken line indicates the flow of data exchange between the programs.

  First, when the user instructs the mobile terminal 500 to start an application (a connection application for connecting to the print management server 100), in step S301, the control unit 411 of the mobile terminal 500 starts the application, and step S302. Then, a connection request including the mobile terminal identification information of the mobile terminal 500 as connection information is transmitted to the print management server 100.

  In step S501, the print management server 100 receives the connection request (I609). In step S502, based on the connection request from the connection application of the portable terminal 500 (including portable terminal identification information as connection information), the portable terminal 500 Search for existence of sub-thread corresponding to. The search for sub-threads is performed on the thread management table shown in FIG. In the first search, since there is no sub thread, the search result has no target sub thread.

  Next, in step S503, if the CPU 201 of the print management server 100 determines that the sub-thread search result indicates that there is no target sub-thread, the process proceeds to step S504, where a new sub-thread is generated, as shown in FIG. A new sub thread information record is added (written) to the indicated thread management table.

  FIG. 11 is a diagram illustrating an example of a thread management table stored in the RAM 203 of the print management server 100.

  As shown in FIG. 11, in the thread management table, a thread ID 1101 for identifying a sub thread, a user name 1102, a portable terminal identification information 1103, a printer IP address (printer identification information) 1104, and a thread pointer 1105 are associated (associated). ing.

  The thread ID 1101 is assigned a unique value when a sub thread is generated. The mobile terminal identification information 1103 records a value acquired from the connection information of the mobile terminal 500. The thread pointer 1105 records information indicating the address information of the execution program in the RAM 203 of the generated sub thread. The user name 1102 and the printer IP address 1104 have no data at this point.

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

  Next, in step S505, if the CPU 201 of the print management server 100 determines that the content received in step S501 is a connection request including connection information from the portable terminal 500, the process proceeds to step S506.

  Next, in step S506, the CPU 201 of the print management server 100 delivers a connection request including connection information to the sub-thread generated in step S504 (I701), and then enters the reception waiting state in step S501 again. .

  In step S506, the sub-thread that has received the connection request is transferred in step S201 (I701). Thereby, the connection between the print management server 100 and the portable terminal 500 is established. That is, it is possible to receive a list of form data from the print management server, display the list of form data on the display unit of the portable terminal 500, and issue a print instruction. Note that authentication is performed by holding an IC card in S401 to S403, which will be described later, and when the list of form data is transmitted to the portable terminal (list information transmission) in S206, the connection between the print management server 100 and the portable terminal 500 is established. If not, a list of form data may be displayed using an e-mail according to a second embodiment described later.

  In step S202, if the CPU 201 of the print management server 100 determines that the received information is a connection request from the portable terminal 500, the process proceeds to step S203, establishes a session with the portable terminal, and then repeats step S201. Waiting to receive.

This session is managed in the target sub thread until it is released. Note that the session may be released when communication with the portable terminal 500 is not performed for a certain period of time.

  When the application of the portable terminal 500 is activated by a command from the print management server 100, the connection request in S301, S302, S201, and S202 is assumed on the assumption that the print management server 100 actively generates a sub thread. The present embodiment can be realized without executing the processing.

  After the session (connection) between the portable terminal 500 and the print management server 100 is established, the CPU 301 of the printer 300a detects that the portable terminal 500 is held over the card reader 319 in step S401. 500 reads the serial number of the IC card 419 built-in. Next, in step S402, the manufacturing number is transmitted as authentication information to the authentication server 200 (authentication information transmission).

  In step S101, the authentication server 200 receives the manufacturing number transmitted from the printer 300a. Next, in step S102, the CPU 201 of the authentication server 200 refers to the received manufacturing number and the authentication table (stored in the external memory 211 of the authentication server 200) shown in FIG. Authenticate.

  Next, in step S103, the CPU 201 of the authentication server 200 transmits the authentication result of S102 to the printer (printer 300a) that requested the authentication. Specifically, if the received manufacturing number is registered in the authentication table, it is determined that the authentication is successful (normal authentication), and the user name 802 of the authentication table acquired using the manufacturing number as a key, the mobile terminal identification An authentication result including information 807 is transmitted to the printer 300a. If the received manufacturing number is not registered in the authentication table, it is determined as an authentication error, and an authentication result including information indicating the authentication error is transmitted to the printer 300a.

  The printer 300a receives the authentication result transmitted from the authentication server 200 in step S403. Next, in step S404, the CPU 301 of the printer 300a determines whether normal authentication has been performed based on the received authentication result, and determines that normal authentication has not been performed (the user name is not included in the authentication result). In such a case, the process returns to step S401 and waits for the portable terminal to be held again.

  On the other hand, if it is determined in step S404 that normal authentication has been performed (the user name and portable terminal identification information are included in the authentication result), the CPU 301 of the printer 300a advances the process to step S405.

  Next, in step S405, the CPU 301 of the printer 300a transmits the print information set request of the authenticated user shown in FIG. 18 to the print management server 100 based on the user name and portable terminal identification information included in the received authentication result. (User identification information transmission). (I601)

  A print information set is a group of information transmitted and received between the printer and the print management server. As shown in FIGS. 19 to 23, this information group includes an information type representing the type of information group, a thread ID generated in S504 and managed in FIG. 11, and information necessary for each information type. .

  The thread ID is identification information for specifying whether there is a process of the portable terminal held over the portable terminal. By having this thread ID, for example, when a specific portable terminal 500 is held over for the first time, a thread ID is generated and a list of form data is sent to the portable terminal 500, so the same portable terminal 500 is held over (second time) ) Can be specified that the list of form data has already been sent, and when it is held over for the second time, the operation can be shifted to an operation for printing the form data instructed to be output. (You can see what process to perform when you hold your mouse over the first time and when you hold it over the second time.)

  FIG. 18 is a diagram illustrating an example of a print information set request transmitted from the printer 300 a to the print management server 100.

  As shown in FIG. 18, in the print information set request, the user name included in the received authentication result is recorded in 1801, the portable terminal identification information is recorded in 1802, and the IP address of the printer 300a is recorded in 1803 and transmitted.

  In the present embodiment, the printer 300a acquires the user name (user identification information) and the portable terminal identification information from the authentication server 200 using the manufacturing number of the IC card 419 as a key, and transmits it to the print management server 100. However, the print management server 100 may be configured to store and manage the user name, the portable terminal identification information, and the IC card manufacturing number in advance. In this case, the printer 300a transmits the manufacturing number of the IC card 419 to the print management server 100, and the print management server acquires the user name and the portable terminal identification information using the manufacturing number of the IC card 419 as a key.

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

Next, in step S501, when the print management server 100 receives the print information set request of the authenticated user transmitted from the printer 300a in step S405 (receives user identification information), the process proceeds to step S502, and the print management server 100 includes the print information set request. The presence of a sub thread corresponding to the mobile terminal identification information is searched, and then the process proceeds to step S503. The sub-thread search is performed on the thread management table shown in FIG. 11 using the mobile terminal identification information as a key. In this embodiment, since the session has already been established, the target subthread is always searched. The user name 1102 and printer IP address 1104 in the thread management table are in a state without data, but the user name 1801 and printer IP address 1803 in the print information set request are recorded here. In step S503, since the sub-thread search result is determined to be present, the process proceeds to step S505.
The printer IP address to be recorded (stored) is configured to be included in the print information set request, but is acquired from a protocol (for example, TCP / IP communication) between the printer 300a and the print management server 1000. You may comprise.

  Next, in step S505, if the CPU 201 of the print management server 100 determines that the content received in step S501 is a print information set request from the printer 300a, the process proceeds to step S507.

  Next, in step S507, the CPU 201 of the print management server 100 delivers the print information set request to the target subthread (I702), and then enters the reception waiting state in step S501 again.

  In step S507, the sub thread that has received the print information set request is passed in step S201. (I702)

  Next, in step S202, the CPU 201 of the print management server 100 determines that the received information is not a connection request from the portable terminal 500 (a print information set request), and proceeds to step S204.

  In step S204, the CPU 201 of the print management server 100 determines whether the printer 300a has a display unit that can display a form data list based on the printer display unit presence / absence table shown in FIG.

  In step S204, if the CPU 201 of the print management server 100 determines that there is a display unit capable of displaying the form data list on the printer 300a, the process proceeds to step S205. If it is determined that there is no display unit, the process proceeds to step S206. To proceed.

  If it is determined that the printer 300a has a display unit that can display a list of form data, the process proceeds to step S205.

  In step S205, the CPU 201 of the print management server 100 refers to the form management database shown in FIG. More specifically, the form data corresponding to the user name 1801 included in the received print information set request of the authenticated user is retrieved from the form data in which the print status 504 in FIG. 5 is not output (unprinted). Generate a list of data. A list of the generated form data is acquired and transmitted to the printer (in this case, the printer 300a) corresponding to the printer IP address 1803 (I602) (list information transmission). The format at this time is the format of the print information set (form list) shown in FIG.

  FIG. 19 is a diagram illustrating an example of a format of a print information set (form list) when a form data list is transmitted from the print management server 100 to the printer 300a.

  As shown in FIG. 19, for transmission of the form data list, a symbol indicating that the information content is the form data list is recorded in the information type 1901, and the ID of the thread that returned this information is recorded in the thread ID 1902. . The number of form data to be transmitted is recorded in the form number 1903, and the form data information is recorded by the number recorded in the form number 1903. The form data information includes a time stamp 1904, a user name 1905, and a document name 1906.

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

  In step S406, the printer 300a receives the print information set of the form data list transmitted from the print management server 100 (I602). Then, in step S407, it is determined that the received content is a form data list according to the content of the information type 1901, and the process proceeds to step S408. In step S408, the CPU 301 of the printer 300a displays the received form data list on the display unit of the operation unit 308, proceeds to step S409, and waits until the next event occurs.

  FIG. 13 is a schematic diagram illustrating an example of a form data list displayed on the display unit of the printer 300a in the present invention.

  In FIG. 13, reference numeral 1301 denotes a form data selection area. The user touches and selects form data to be printed from the form data selection area 1301 (a plurality of form data can be selected).

  Reference numeral 1302 denotes a print button. By touching this button, the print management server 100 can be requested to print the form data selected in the form data selection area 1301. That is, in step S409, when form data is selected in the form data selection area 1301, and the print button 1302 is touched, the process proceeds to step S410. If it is determined in step S410 that a user selection event has occurred (the print button 1302 has been pressed), the process proceeds to step S411.

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

  On the other hand, the print management server 100 proceeds to step S206 after performing the process of step S205. In the present embodiment, when the printer has a display unit capable of displaying a list of form data, the form data list can be displayed on both the printer and the portable terminal. Therefore, after the process of step S205, the process proceeds to step S206. Configured to proceed. However, it may be configured not to process step S206. In step S204, if the CPU 201 of the print management server 100 determines that there is no display unit capable of displaying the form data list on the printer 300a, the process proceeds to step S206 without performing step S205. Note that when step S205 is performed (when there is a display unit), the printer 300a has proceeded to step S408 (waiting until a ready status is transmitted in step S208 and received in step S409). If step S205 is not performed (when there is no display unit), the printer 300a waits for a reply of information from the print management server 100 in step S406 (steps S307 and S207, through step S208). The preparation completion status is transmitted and waits until it is received in step S409).

  In step S206, the CPU 201 of the print management server 100 refers to the form management database shown in FIG. 5 and corresponds to (matches) the unoutput form corresponding to the user name 1801 included in the received print information set request of the authenticated user. A list of data (print data identification information) is acquired and transmitted to the portable terminal 500 via a session associated with the portable terminal identification information 1802 (list information transmission). The format at this time is the format of the print information set (form list) shown in FIG. When step S205 is performed, it is not necessary to acquire the form data list again, and the same data as that transmitted to the printer 300a in step S205 may be transmitted.

  Next, in step S303, the control unit 411 of the mobile terminal 500 receives the print information set of the form data list transmitted from the print management server 100, and displays the form data list on the display unit 415 in step S304. . Thereafter, the process proceeds to step S305 and waits until the next event occurs.

  FIG. 12 is a schematic diagram showing an example of the form data list displayed on the display unit 415 of the portable terminal 500 in the present invention.

  In FIG. 12, reference numeral 1201 denotes a form data selection area, and the user selects (checks) form data to be printed from the form data selection area 1201 (a plurality of form data can be selected).

  Reference numeral 1202 denotes a transmission button. By selecting and instructing this button, a list of form data selected in the form data selection area 1201 is transmitted to the print management server 100.

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

  In step S305, when the form data to be printed is selected (checked) in the form data selection area 1201 and the send button 1202 is selected, the process proceeds to step S306, where it is determined that a user selection event has occurred, and the process proceeds to step S307. move on.

  In step S307, the control unit 411 of the mobile terminal 500 transmits a list of form data to be printed selected in the form data selection area 1201 to the print management server 100 via the above-described session. Thereafter, the process proceeds to step S305 and waits until the next event occurs.

  The data format at this time may be the format of the print information set (form list) shown in FIG. 19 which is the same as when the form data list is received, but this time, only the form data to be printed is returned. It is different from the time of receipt. More specifically, a time stamp for identifying at least form data is transmitted.

  On the other hand, in the case of a printer having a display unit capable of displaying a form data list, the following operation can also be performed on the display unit of the operation unit 308 of the printer 300a.

  In step S409, when form data is selected in the form data selection area 1301 and the print button 1302 is touched, the process proceeds to step S410, where it is determined that a user selection event has occurred, and the process proceeds to step S411.

  In step S411, the CPU 301 of the printer 300a transmits a list of form data to be printed selected in the form data selection area 1301 to the print management server 100 (I603). Thereafter, the process proceeds to step S409 and waits until the next event occurs.

  The data format at this time may be the format of the print information set (form list) shown in FIG. 19 which is the same as when the form data list is received, but this time, only the form data to be printed is returned. It is different from the time of receipt. More specifically, a time stamp for identifying at least form data is transmitted.

  In step S411, when the CPU 301 of the printer 300a transmits a print information set of the form data list to be printed, the CPU 201 of the print management server 100 receives this in step S501. (I603)

  When the print management server 100 receives the print information set of the form data list to be printed by the authenticated user, the print management server 100 searches for the existence of a sub thread corresponding to the user based on the thread ID 1902 in the print information set. The sub thread search is performed on the thread management table shown in FIG. 11 using the thread ID 1902 as a key. Since the mobile terminal has already established a session, the target subthread is always searched.

  Next, in step S505, the CPU 201 of the print management server 100 determines that the content received in step S501 is a print information set from the printer, and proceeds to step S508.

  Next, in step S508, the CPU 201 of the print management server 100 delivers the print information set of the form data list to be printed selected by the user to the target sub thread (I703), and then again in step S501. Waiting for reception.

  In step S508, the sub thread that has received the print information set of the form data list to be printed selected by the user is transferred in step S207. (I703)

  In step S207, the CPU 201 of the print management server 100 receives either the print information set of the form data list to be printed selected by the user transmitted in step S307 of the portable terminal 500 or step S411 of the printer 300a. (Reception of print request) and one or more print target form data included in the print information set of the print target form data list are acquired.

  The CPU 201 of the print management server 100 records the acquired one or more print target form data in a print management table generated for each sub thread shown in FIG.

  FIG. 14 is a schematic diagram showing an example of a print management table stored in the RAM 203 of the print management server 100 shown in FIG.

  As shown in FIG. 14, the print management table includes a user name 1401, a printer name 1402, an IP address 1403, and a time stamp 1404 (a selected number exists) of a printing target form selected by the user.

  Next, an example of a procedure for generating a print management table in step S207 of FIG. 10B will be described with reference to FIG.

  In step S <b> 2401, the CPU 201 of the print management server 100 reserves a memory area for holding the print management table in the RAM 203. At this time, only a memory area for recording the user name 1401, the printer name 1402, and the IP address 1403 corresponding to the header of the table may be secured, and the area of the time stamp 1404 may be sequentially added later. Based on the information on the number of forms 1903 in the print information set of the form data list, a method may be adopted in which the memory area of the entire print management table is secured from the beginning.

  In step S2402, the CPU 201 of the print management server 100 acquires the user name 1102 and the printer IP address 1104 from the thread management table using the thread ID of the sub thread executing this process as a key, and the user name 1401. , Recorded in the IP address 1403. Also, using the printer IP address 1104 as a key, the printer name 601 is acquired from the printer driver related table of FIG. 6 and recorded in the printer name 1402.

  Next, in step S2403, the CPU 201 of the print management server 100 sequentially acquires time stamps 1904 from the print information set of the form data list to be printed. First, the time stamp 1904 at the head of the table is acquired.

  Next, in step S2404, the CPU 201 of the print management server 100 confirms whether or not the time stamp 1904 has been acquired. If it is determined that the time stamp 1904 has been acquired, the CPU 201 adds the time stamp 1904 to the time stamp 1404 in step S2405.

  Thereafter, the CPU 201 of the print management server 100 repeatedly executes steps S2403 to S2405 to add a time stamp up to the last record of the print information set of the form data list to be printed. After the processing up to the last record is completed, it is determined in step S2404 that the time stamp 1904 could not be acquired, and the processing ends.

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

  Next, in step S208, the CPU 201 of the print management server 100, when the recording in the print management table is completed, displays a status code for indicating that the preparation for printing is completed in the print information set (status shown in FIG. 20). Code) format to both the printer 300a and the portable terminal 500. In the present embodiment, it is configured to determine that the preparation for printing is completed at the stage when recording in the print management table is completed. However, the present invention is not limited to this, and the description language of the printer to which the form data is output is not limited to this. It is also possible to make the preparation for printing complete when it is converted to (page description language) and ready for transmission.

  FIG. 20 is a diagram illustrating an example of a format of a print information set (status code) when a status code is transmitted from the print management server 100 to the mobile terminal 500 and the printer 300a.

  As shown in FIG. 20, in transmitting the status code, a symbol indicating that the content of the information is a status code is recorded in the information type 2001, and the ID of the thread that transmitted this information is recorded in the thread ID 2002. In the status code 2003, a status code to be transmitted is recorded. This time, a status code indicating completion of printing preparation is recorded.

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

  In step S305, when the portable terminal 500 receives from the print management server 100 the status code of print preparation completion in the format of the print information set (status code) shown in FIG. 20, the process proceeds to step S306, where the print preparation is completed. It is determined that a status reception event has occurred, and the process proceeds to step S308.

  Note that if the print management server 100 has received the print target form data list transmitted in step S307 by the portable terminal 500 in step S207, the portable terminal 500 executes the processes in steps S306 to S307 once. Will be. On the other hand, if the print management server 100 has received the form data list to be printed that the printer 300a has transmitted in step S411 in step S207, the portable terminal 500 does not execute the processes in steps S306 to S307. . However, in either case, the processing (steps S306 to S308) after receiving the print preparation completion status code in the portable terminal 500 is the same.

  Next, in step S308, a message notifying that preparation for printing has been completed is displayed on the display unit 415 of the portable terminal 500.

  FIG. 15A is a schematic diagram illustrating an example of a message notifying completion of printing displayed on the display unit 415 of the mobile terminal 500 illustrated in FIG. Although it is assumed that the screen is closed when the OK button is pressed, the screen may be automatically changed by the occurrence of an event without pressing the OK button.

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

  If the printer 300a does not have a display unit that can display a list, the CPU 301 of the printer 300a stands by in step S406. However, in step S208, the print management server 100 prints the print information set (status code) shown in FIG. When the status code indicating completion of print preparation is transmitted in the format (I602), the process proceeds to step S407. Further, it is determined that the information type 2001 is a status code notifying completion of printing preparation, and the process proceeds to step S412. If the printer 300a has a display unit capable of displaying a small message, preparation for printing is completed. Display a message to let you know

  For example, in the case where the printer 300a has a display unit that can display a small message of about one line of text, “Insaturation” is displayed on the display unit.

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

  On the other hand, if the printer 300a has a display unit that can display a list, in step S409, the printer 300a receives a print preparation completion message from the print management server 100 in the form of a print information set (status code) shown in FIG. When the status code is received, the process proceeds to step S410, where it is determined that a status reception event indicating completion of print preparation has occurred, and the process proceeds to step S412.

  If the print management server 100 has received the form data list transmitted by the printer 300a in step S411 in step S207, the processing in steps S410 to S411 is executed once in the printer 300a. . On the other hand, if the print management server 100 has received the form data list transmitted by the portable terminal 500 in step S307 in step S207, the printer 300a does not execute the processing in steps S410 to S411. However, in either case, the processing after receiving the print preparation completion status code in the printer 300a (steps S410 to S412) is the same.

  Next, in step S412, a message notifying that the preparation for printing has been completed is displayed on the display unit of the printer 300a.

  For example, a message such as “Ready for printing” may be displayed in the lower end area of the display unit of the printer 300a shown in FIG.

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

  Next, the printer 300a returns to step S401 and waits for the portable terminal 500 to be held over the card reader 319. In step S209, the print management server 100 also waits for a print information set request from the printer 300a.

  The reason for waiting without executing printing is that when the preparation for printing is started and printing is started, the printed matter is output even if the user leaves the vicinity of the printer 300a. This is to avoid being missed. In order to start printing, the user needs to hold the portable terminal 500 over the card reader 319 of the printer 300a again to read the IC card 419.

  That is, when the portable terminal 500 is held over for the first time, the form data list is displayed on the display unit 415 of the portable terminal 500, and when the portable terminal 500 is held over for the second time, the form data displayed when the portable terminal 500 is held over the first time. A form that is instructed to be output in the list is output from the printer 300a. If there are a plurality of forms designated in the form data list, the designated forms are output from the printer 300a when the portable terminal 500 is held over the second time (from the third time). (Hold the portable terminal 500 as many times as the number of form data instructed to be output from the form data list).

  Accordingly, even if the user gives an output instruction from the form data list displayed on the display unit 415 of the portable terminal 500 at a location away from the printer 300a, the portable terminal 500 must be held over the printer 300a again. High printing can be performed. Further, since it is necessary to hold the portable terminal 500 as many times as the number of forms (print data) instructed to be output (every time the instructed form is issued), the user must be present (in front of the printer 300a) when outputting. In addition, it is possible to perform printing with higher security.

  In step S401, when the CPU 301 of the printer 300a detects that the portable terminal 500 is held over the card reader 319, the CPU 301 reads the serial number of the IC card 419 built in the portable terminal 500. Using this as authentication information, after passing through the authentication in steps S402 to S404 of the printer 300a and in steps S101 to S103 of the authentication server 200, the CPU 301 of the printer 300a proceeds to step S405 when it is determined as normal authentication in step S404. In step S405, a print information set request is transmitted to the print management server 100 in the format shown in FIG. 18 (I601), and the process proceeds to step S406.

  When the CPU 301 of the printer 300a transmits a print information set request in step S405, the CPU 201 of the print management server 100 receives this in step S501.

  When the print management server 100 receives the print information set request of the authenticated user transmitted from the printer 300a in step S501, the print management server 100 prints the target sub thread via steps S502 to S503, S505, and S507. After the information set request is transferred (I702), the process again enters the reception waiting state in step S501. In addition, although I702 is comprised so that a process may transfer to step S201 and step S209, if an IC card is passed once, the process will transfer to step S208. That is, after the IC card is held up once and the IC card is held up after the preparation for printing (second time), the process proceeds to step S209 after step S507.

  In step S507, the sub thread that has received the print information set request is delivered in step S209. (I702)

  Next, when the CPU 201 of the print management server 100 receives the print information set request in step S209, the process proceeds to step S210, and a print start command is transmitted to the printer 300a in the format of the print information set (print start command) shown in FIG. To do. (I602)

  FIG. 21 is a diagram illustrating an example of a format of a print information set (print start command) when a print start command is transmitted from the print management server 100 to the printer 300a.

  As shown in FIG. 21, when transmitting a print start command, a symbol indicating that the information content is a print start command is recorded in the information type 2101, and the ID of the thread that transmitted this information is recorded in the thread ID 2102. . In the time stamp 2103 and the user name 2104, the time stamp 1404 and user name 1401 of one form data to be printed are extracted from the print management table and recorded.

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

  In step S406, the printer 300a receives the print start command transmitted from the print management server 100 in the form of a print information set (print start command) (I602). Next, in step S407, it is determined that the received content is a print start command according to the content of the information type 2101, and the process proceeds to step S413. In step S413, the CPU 301 of the printer 300a transmits a status code indicating that printing can be performed in the same print information set (status code) format as that in FIG. 20 (I605). At this time, a status code indicating that printing is possible is recorded in the status code 2003. Also, the print start command is held in the RAM 302 as it is.

  When the CPU 301 of the printer 300a transmits a status code indicating that printing is possible in step S413, the CPU 201 of the print management server 100 receives this in step S501. (I605)

  In step S501, when the print management server 100 receives the status code (FIG. 20) indicating that printing is possible and transmitted from the printer 300a, the print management server 100 passes the steps S502 to S503, S505, and S508 to the target sub thread. On the other hand, after passing the status code indicating that printing is possible (I703), the process again enters the reception waiting state in step S501.

The sub thread that has received the status code indicating that printing is possible in step S508 is delivered in step S211. (I703)
Note that I703 is configured so that the process proceeds to step S207 and step S211, but since the process has already shifted to the process of step S210, the print information set (step S210 (print start command transmission)) generated after the process is performed. It is assumed that the print information set having a status code indicating that printing is possible is transferred to step S211 and received in step S211.

  Next, in step S211, when the CPU 201 of the print management server 100 receives a status code indicating that printing is possible, the process proceeds to step S212, where the form data of the print target form is acquired (print data acquisition) (that is, in the print management table). Based on the time stamp 1404, it is obtained from the form management database), and print processing of the obtained form data is executed for the printer (printer 300a) having the IP address indicated by the IP address 1403 of the print management table (I606). The printing process is to issue an output command (print data output command) for printing by the printer 300a, or to output (send) the print data to the printer 300a.

  At this time, based on the IP address 1403, a printer driver related table (FIG. 6) is searched to select a printer driver, and print data of form data is output (transmitted) to the printer 300a through the selected printer driver. . In addition, this printing process may be LPR printing or a printing process using a standard TCP / IP port supported by Windows (registered trademark).

  Next, when the printer 300a receives the print data of the form data output from the print management server 100 via the printer driver (I606), in step S414, the CPU 301 of the printer 300a converts the print data of the form data to the received print data. Perform print output based on In addition, a process of taking out a time stamp or a user ID from a print header or the like and checking whether or not printing can be performed by collating it with the contents of a held print start command may be added.

  Next, when the print output based on the print data of the form data is completed, in step S415, the CPU 301 of the printer 300a transmits a print completion notification to the print management server 100 in the format of the print information set (completion notification) in FIG. . (I607)

  FIG. 22 is a diagram illustrating an example of a format of a print information set (completion notification) when a print completion notification is transmitted from the printer 300a to the print management server 100.

  As shown in FIG. 22, for transmission of the print completion notification, a symbol indicating that the content of the information is a print completion notification is recorded in the information type 2201, and is stored in the thread ID 2202, the time stamp 2203, and the user name 2204. The thread ID 2102, the time stamp 2103, and the user name 2104 of the print start command that has been printed are copied. The time stamp 2203 and the user name 2204 may be acquired from within print data (for example, a header).

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

  In step S415, when the CPU 301 of the printer 300a transmits the print information set of the print completion notification, the CPU 201 of the print management server 100 receives this in step S501. (I607)

  In step S501, when the print management server 100 receives the print information set of the authentication user's print completion notification transmitted from the printer 300a, the print management server 100 passes the steps S502 to S503, S505, and S508 to the target sub thread. On the other hand, after delivering the print information set of the print completion notification (I703), the process again enters the reception waiting state in step S501.

  In step S508, the sub thread that has received the print information set of the print completion notification is transferred in step S213. (I703)

  Next, when receiving the print information set of the print completion notification (S213), the print management server 100 deletes the record including the time stamp 1404 corresponding to the received time stamp 2203 from the print management table, and the process proceeds to step S214. Proceed.

  In step S214, the CPU 201 of the print management server 100 counts the remaining number in the print management table, and uses the result as the remaining number in the form of a print information set (remaining number) shown in FIG. Transmit to both terminals 500.

  FIG. 23 is a diagram illustrating an example of a format of a print information set (remaining number) when the print management server 100 transmits the remaining number of print forms (notifies the number of unprinted print data).

  As shown in FIG. 23, in transmitting the number of remaining cases, a symbol indicating that the content of the information is the number of remaining cases is recorded in the information type 2301, and the ID of the thread that transmitted this information is recorded in the thread ID 2302. Record the number of unoutput forms from the remaining number in the print management table in the remaining number 2303 and send it (notification of number of unprinted print data).

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

  In step S215, the CPU 201 of the print management server 100 determines whether or not printing of all the selected forms has been completed (there is no time stamp 1404 in the print management table), and printing has not been completed (print management). If it is determined that there is still a time stamp 1404 in the table, the process returns to step S209.

  On the other hand, if it is determined in step S215 that all the selected forms have been printed (the print management table has no time stamp 1404), the process proceeds to step S216.

  On the other hand, when the printer 300a receives the print information set of the remaining number transmitted from step S214 of the print management server 100 in step S416 (I608), if the remaining number 2303 is 1 or more in step S417, it is not output. It is determined that the form remains, and the process proceeds to step S418. If the printer 300a has a display unit capable of displaying the remaining number, the remaining number is displayed. In step S417, if the remaining number 2303 is 0, it is determined that there is no unoutput form, and the process advances to step S419. If the printer 300a has a display unit capable of displaying a message, printing is completed. Display a message to let you know.

  For example, as a message informing the number of remaining cases, “X printed documents still remain” may be displayed in the lower end area of the display unit of the printer 300a shown in FIG. Further, as a message notifying the completion of printing, it may be possible to display “printing of all documents completed” in the lower end area of the display unit of the printer 300a shown in FIG.

  When the printer 300a has a display unit capable of displaying a small message of about one line of text, the message indicating the number of remaining cases is “Insatsu Kori X Ken” displayed on the display unit. Conceivable. Further, as a message notifying the completion of printing, it is conceivable to display “Senken insole” on the display unit.

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

  Thereafter, the printer 300a returns to step S401 and is in a standby state until the portable terminal 500 is held over the card reader 319 again. Printing is repeated in the flow, and when printing of all the forms is completed, the process proceeds to S419.

  On the other hand, in the portable terminal 500, when the print information set of the remaining number transmitted from step S214 of the print management server 100 is received in step S309, if the remaining number 2303 is 1 or more in step S310, an unoutput form Is determined to remain, the process proceeds to step S311 to display the number of remaining cases. In step S310, if the number of remaining cases is 0, it is determined that there is no unoutput form, and the process proceeds to step S312 to display a message notifying that printing has been completed.

  FIG. 15B is a schematic diagram illustrating an example of a message informing the number of remaining cases displayed on the display unit 415 of the mobile terminal 500 illustrated in FIG. 4, and FIG. 15C illustrates the mobile phone illustrated in FIG. 4. FIG. 10 is a schematic diagram illustrating an example of a message notifying completion of printing displayed on the display unit 415 of the terminal 500. Although it is assumed that the screen is closed when the OK button is pressed, the screen may be automatically changed by the occurrence of an event without pressing the OK button.

  Hereinafter, the description returns to the flowcharts of FIGS. 10A, 10B, and 10C.

  When all printing is completed, in step S313, the control unit 411 of the portable terminal 500 transmits a session disconnection request to the print management server 100, and the CPU 201 of the print management server 100 performs session release processing in step S216. And the session stops.

  Next, in step S314, the control unit 411 of the mobile terminal 500 ends the application.

  Finally, in step S217, the CPU 201 of the print management server 100 releases the print management table from the memory, deletes its own thread ID record from the thread management table, and terminates the thread.

  If the mobile terminal 500 is not held over the printer 300a for a certain period of time and communication is not performed between the printer 300a and the print management server 100, the CPU 201 of the print management server 100 does not proceed. However, the record of its own thread ID may be automatically deleted from the thread management table, and the thread may be terminated. In this case, even when printing cannot be performed due to the circumstances of the user, information related to user printing can be automatically deleted on the print management server 100 side.

  Note that if the session is not held in S203, the processing in S216 and S313 is not performed.

[Second Embodiment]
In the first embodiment, the configuration in which a session is established between the print management server 100 and the mobile terminal 500 to perform communication has been described. However, communication between the print management server 100 and the mobile terminal 500 can be performed using e-mail and Web. You may comprise so that it may be performed by. In this case, there is no need to maintain a session between the print management server 100 and the mobile terminal 500, and the mobile terminal 500 may not have a dedicated application for connecting to the print management server 100. The portable terminal 500 can cope with only a general electronic mail transmission / reception function and a web browser.

  In this case, the e-mail address of the portable terminal 500 is stored in the e-mail address 803 of the authentication table shown in FIG. 8, and after authentication in S102 of FIG. 10A, in S103, along with the user name 802 and the like, The CPU 201 transmits the request to the printer 300a that requested the authentication.

  Hereinafter, with reference to FIG. 26, the processing of the sub thread of the print management server 100 and the processing of the mobile terminal 500 of the present embodiment will be described.

  FIG. 26 is a flowchart illustrating an example of a third control processing procedure according to the present invention, which replaces the processing of the sub-thread of the print management server 100 and the mobile terminal 500 of FIG. 10B in the first embodiment of the present invention. .

  In the figure, S28201 to S28212 correspond to the steps of the print management server 100, and are realized by the CPU 201 of the print management server 100 executing the program stored in the external memory 211 on the RAM 203.

  Similarly, in the figure, S28101 to S28106 correspond to each step of the mobile terminal 500, and are realized by the control unit 411 of the mobile terminal 500 executing a program stored in the ROM 417 on the RAM 418.

  In the figure, I602 to I703 are symbols for associating the sub thread of the print management server 100 with the main thread of the print management server 100 or the printer 300 in FIG. 10C or 10A.

  In step S2821, the CPU 201 of the print management server 100 receives the print information set request from the printer 300a sent via the main thread. (I702)

  The format of the print information set request in the second embodiment is shown in FIG. Unlike the first embodiment, the print information set request includes the mail address 2902 of the mobile terminal 500 instead of the mobile terminal identification information 1802.

  FIG. 28 shows a thread management table in the second embodiment. Instead of the mobile terminal identification information 1103, the mail address 3003 of the mobile terminal is recorded in the thread management table.

  The next steps S28202 and S28203 have the same processing contents as steps S204 and S205 in FIG. 10B.

  Next, in step S28204, the CPU 201 of the print management server 100 acquires a list of non-output form data as in step S206 of FIG. 10B, but does not make this a print information set, but describes it in an HTML file. And stored in the external memory 211. This HTML file has a format that can be displayed by a Web browser of the portable terminal 500 to be described later.

  Next, in step S28205, the CPU 201 of the print management server 100 transmits an e-mail in which URL information indicating the location of the HTML file exists as link information to the e-mail address indicated by the e-mail address 3003 by the SMTP protocol. .

  Since the mail address is that of the portable terminal 500, the portable terminal 500 receives an e-mail in step S28101.

  Next, in step S28102, when the user of the mobile terminal 500 opens the received e-mail and selects the displayed link information, the web browser is activated, and the connection request to the link destination URL is printed as an HTTP request. It transmits to the management server 100.

  Next, in step S28206, the CPU 201 of the print management server 100 receives an HTTP request from the portable terminal 500, and in step S28207, in accordance with the specified URL, an HTML file is sent to the portable terminal 500 as an HTTP response. Send.

  Next, in step S28103, the portable terminal 500 displays the HTML file received by the HTTP response as a home page on the Web browser. The display contents at this time are the same as the display of the form data list by the dedicated application in FIG.

  In step S28104, when the user of the portable terminal 500 operates the home page to select a form to be printed using the button 1201 and presses the send button 1202, a list of the selected form data is printed as an HTTP request. It is transmitted to the management server 100.

  The next step S28208 performs the same operation as step S207 in FIG. 10B, but the list of form data from the printer 300a received through I703 is the same print information set as in the first embodiment, whereas the portable terminal 500 The difference is that the reception from is in the form of an HTTP request.

  In the next step S28209, the same operation as in step S208 in FIG. 10B is performed to notify the completion of the print preparation (print preparation notification), but the status code of the print preparation completion transmitted to the printer 300a through I602 or I604 is the first. The print information set is the same as that in the embodiment, but the transmission to the mobile terminal 500 is in the HTTP response format. However, if an HTTP request from the mobile terminal 500 is not received in step S28208, transmission to the mobile terminal 500 is not performed.

  The next step S28210 is a series of processes in which printing is actually performed by the printer 300a, but is omitted because it is the same operation as steps S209 to S215 in FIG. 10B. However, the number of remaining cases in step S214 is transmitted only to the printer 300, and is not transmitted to the portable terminal 500.

  In step S2821, the CPU 201 of the print management server 100 transmits an e-mail notifying that printing has been completed to the e-mail address indicated by the e-mail address 3003.

  Since the mail address is that of portable terminal 500, portable terminal 500 receives the electronic mail in step S28106. The contents of the e-mail are the same as those shown in FIG.

  Finally, in step S28212, the CPU 201 of the print management server 100 ends this thread and ends the operation.

[Third Embodiment]
In the first and second embodiments, the process of executing printing by holding the mobile terminal 500 including the display unit 415 and incorporating the IC card 419 over the card reader 319 of the printer 300a has been described. In addition to this, the third embodiment enables printing to be executed even when an IC card that is not associated with a portable terminal (hereinafter referred to as “IC card (independent)”) is used. Thereby, for example, the user A who uses the portable terminal and the user B who uses the IC card (independent) can execute printing with the same printing system.

  When using an IC card (independent), when the IC card (independent) is held over the card reader 319 of the printer 300a, the manufacturing number of the IC card (independent) is transmitted from the printer 300a to the authentication server 200.

  The authentication server 200 authenticates whether the user is a legitimate user by referring to the transmitted manufacturing number and the authentication table in FIG. At the time of normal authentication, the user name and portable terminal identification information are transmitted to the printer 300a as an authentication result. At this time, information corresponding to the IC card (independent) to be used is added to the authentication table in advance by manual work or the like. At this time, the content of the mobile terminal identification information 807 is left blank. As a result, when the IC card (independent) is held over, the mobile terminal identification information of the authentication server 200 is blank, and therefore the authentication result including the blank mobile terminal identification information is transmitted to the printer 300a together with the user name 802.

  Upon receiving the authentication result (the portable terminal identification information is blank), the printer 300a records the user name 1801 and the printer IP address 1803 of the printer 300a when transmitting the print information set request of FIG. The portable terminal identification information 1802 is recorded with blanks transmitted. (I601)

  When the CPU 201 of the print management server 100 receives the print information set request in step S501 in FIG. 10C (I601), the process proceeds to step S502, and the target subthread is searched from the thread management table using the user name as a key (print data). And then proceeds to step S503. If it is determined in step S503 that the target sub thread does not exist, a sub thread is generated in step S504, and a thread ID that is identification information of the sub thread is added to the thread management table. If the target sub thread exists, the process proceeds to the target thread.

  In step S505, if the CPU 201 of the print management server 100 determines that the received content is a print information set request, the process advances to step S507, and the print information set request is transferred to the target subthread. (I702)

  Hereinafter, with reference to FIG. 16, the processing of the sub thread of the print management server 100 of the present embodiment will be described.

  FIG. 16 is a flowchart illustrating an example of a fourth control processing procedure according to the present invention, which replaces the sub-thread processing of the print management server 100 of FIG. 10B according to the first embodiment of the present invention.

  In the figure, S1601 to S1612 correspond to the steps of the print management server 100, and are realized by the CPU 201 of the print management server 100 executing the program stored in the external memory 211 on the RAM 203.

  In the figure, I602, I701, I702, and I703 are symbols for associating the sub thread of the print management server 100 with the main thread of the print management server 100 or the printer 300 in FIG. 10C or 10A.

  In FIG. 16, step S1601 is the same process as S201 of FIG. 10B. In step S1601, the sub thread of the print management server 100 waits for reception of the connection request (I701) from the portable terminal 500 or the print information set request (I702) from the printer 300a, and after receiving either of them, step S1602 Proceed to

  In step S1602, the CPU 201 of the print management server 100 receives information indicating whether the content received in step S1601 is a connection request (I701) from the portable terminal 500 or a print information set request (I702) from the printer 300a. If it is a connection request from the mobile terminal 500, the process proceeds to step S1603 to establish a session with the mobile terminal 500.

  On the other hand, if the CPU 201 of the print management server 100 determines in step S1602 that the content received in step S1601 is a print information set request (I702) from the printer 300a, the process advances to step S1604. When an IC card (independent) is used, a connection request from the portable terminal 500 cannot occur, so that the determination is always made to branch to step S1604.

  In step S1604, the CPU 201 of the print management server 100 determines whether or not there is a display unit that can display a list on the transmission source printer 300a of the print information set request of the authenticated user based on the printer display unit presence / absence table shown in FIG. Judgment.

  If the CPU 201 of the print management server 100 determines in step S1604 that the printer 300a has a display unit that can display a list of form data, the process advances to step S1605.

  Each step from step S1601 to step S1604 has the same contents as each step from step S201 to step S204 in FIG. 10B.

  In step S1605, the CPU 201 of the print management server 100 performs the same processing as in step S205 in FIG. 10B, transmits a list of unoutput form data to the printer 300a, and then proceeds to step S1607.

  On the other hand, in step S1604, if the CPU 201 of the print management server 100 determines that there is no display unit capable of displaying a list of form data on the printer 300a, the process proceeds to step S1606.

  In step S1606, the CPU 201 of the print management server 100 checks whether the content of the mobile terminal identification information 1802 of the print information set request of the authenticated user received in step S1601 is blank.

  If it is determined in step S1606 that the content of the mobile terminal identification information 1802 is not blank, it can be said that the mobile terminal 500 is held over the card reader 319 of the printer 300a, so the process proceeds to step S1608, and FIG. The same process as step S206 is performed to transmit a list of non-output form data to the portable terminal 500, and then the process proceeds to step S1610.

  On the other hand, if it is determined in step S1606 that the content of the mobile terminal identification information 1802 is blank, it is not the mobile terminal 500 but the IC card (independent) that is held over the card reader 319 of the printer 300a. Determination is made and the process proceeds to step S1609.

  On the other hand, in step S1607, the same determination as in step S1606 is performed. If it is determined that the content of the mobile terminal identification information 1802 is not blank, the process proceeds to step S1608, and a list of unoutput forms to the mobile terminal 500 is displayed. Although transmission is performed, when it is determined that the content of the mobile terminal identification information 1802 is blank, the process proceeds to step S1610.

  As a result, it is possible to determine whether the portable terminal 500 containing the IC card 419 is held over or the IC card (independent) is held over, so it is determined whether to display the form data list on the mobile phone. Therefore, even when there is a user who uses an IC card (independent) instead of the portable terminal 500, printing with high security can be performed.

  In step S1610, the CPU 201 of the print management server 100 waits for reception of the form data list selected for printing from the printer 300a or the portable terminal 500. This process is the same as step S207 in FIG. 10B.

  In step S1609, the CPU 201 of the print management server 100 acquires all unoutput form data corresponding to the user name included in the print information set request of the authenticated user received in step S1601 from the form management database, and this subthread Add to the print management table to be managed. This is because the printer 300a does not have a display unit and does not use a portable terminal, so there is no way to display a list of forms, and printing is executed by automatically setting all forms as print targets. .

  Next, an example of a procedure for generating a print management table in step S1609 in FIG. 16 will be described with reference to FIG.

  In step S <b> 2501, the CPU 201 of the print management server 100 reserves a memory area for holding the print management table in the RAM 203. At this time, only a memory area for recording the user name 1401, printer name 1402, and IP address 1403 corresponding to the header of the print management table may be secured, and a time stamp 1404 area may be sequentially added later. A method may be adopted in which the number of user names 502 that are targets of the management database is counted and the memory area of the entire print management table is secured from the beginning.

  Next, in step S2502, the CPU 201 of the print management server 100 acquires the user name 1102 and the printer IP address 1104 from the thread management table using the thread ID of the sub thread executing this processing as a key, and print management table. Are recorded in the user name 1401 and the IP address 1403 of the user. Also, using the printer IP address 1104 as a key, the printer name 601 is acquired from the printer driver related table of FIG. 6 and recorded in the printer name 1402.

  In step S2503, the CPU 201 of the print management server 100 acquires a user name 502 and a time stamp 501 sequentially from the form management database. First, a user name 502 and a time stamp 501 at the top of the database are acquired.

  In step S2504, the CPU 201 of the print management server 100 checks whether the user name 502 and the time stamp 501 have been acquired. If it is determined that the user name 502 and time stamp 501 have been acquired, the process advances to step S2505.

  In step S2505, the CPU 201 of the print management server 100 checks whether the acquired user name 502 is the same as the user name 1401 in the print management table. If it is determined that the user name 502 is the same, the process advances to step S2506. , The time stamp 501 is added to the time stamp 1404. If it is determined that they are not the same, the process returns to step S2503.

  Thereafter, the CPU 201 of the print management server 100 repeatedly executes steps S2503 to S2506 to perform processing up to the last record in the form management database. After the processing of the last record is completed, the time stamp 501 is set in step S2504. It is determined that acquisition has failed, and the process ends.

  Hereinafter, the description returns to the flowchart of FIG.

  When the process of step S1609 ends, the CPU 201 of the print management server 100 proceeds to step S1611. The reason for not going to step S1610 is that it is determined that all forms are to be printed, and therefore it is not necessary to receive a list of forms selected for printing from a printer or portable terminal.

  In the next step S1611, the same processing as the series of operations in steps S208 to S215 in FIG. 10B is executed. However, the difference is that what is held over the card reader 319 of the printer 300a may be not only a portable terminal with a built-in IC card but also an IC card (independent). Therefore, in step S208 and step S214 in FIG. 10B, transmission to the printer 300a is performed, but information is not transmitted to the portable terminal if an IC card (independent) is used. This is realized by not transmitting the information to the mobile terminal when the mobile terminal information 1103 in the record for the thread ID 1101 in the thread management table is blank.

  Finally, in step S1612, the CPU 201 of the print management server 100 ends this thread and ends the operation.

  Further, instead of the printer display unit presence / absence table, the configuration of the display unit may be determined on the printer side, and the request (command) to be transmitted to the print management server 100 may be changed in step S405.

  In this case, in step S1604, the presence or absence of the printer display unit is determined based on the received information.

[Fourth Embodiment]
In the first, second, and third embodiments, the configuration in which the IC card manufacturing number, the user name, and the mobile terminal identification information or the mail address are associated and recorded in the authentication table of the authentication server 200 has been described. However, the HD 211 of the print management server 100 may be configured to record the IC card manufacturing number, the user name, and the mobile terminal identification information or the mail address in association with each other.

  In this case, in step S103 of FIG. 10A, the CPU 201 of the authentication server 200 transmits the IC card manufacturing number to the printer 300a as an authentication result. In step S405, the printer 300a transmits the IC card manufacturing number to the print management server 100. Send to.

  Next, the CPU 201 of the print management server 100 acquires the user name and portable terminal identification information or mail address held in the HD 211 of the print management server 100 using the IC card manufacturing number transmitted from the printer 300a as a key. The subsequent processing is executed.

  Further, the IC card manufacturing number and the user name are linked and recorded in the authentication table of the authentication server 200, and the user name and the portable terminal identification information or the mail address are linked in the HD 211 of the print management server 100. You may comprise so that it may attach and record. In this case, in step S103 of FIG. 10A, the CPU 201 of the authentication server 200 transmits the user name as an authentication result to the printer 300a, and the printer 300a transmits the user name to the print management server 100 in step S405. Next, the CPU 201 of the print management server 100 acquires the mobile terminal identification information or the mail address held in the HD 211 of the print management server 100 using the user name transmitted from the printer 300a as a key, and executes the subsequent processing. To be configured.

  Furthermore, in the authentication table of the authentication server 200, the IC card manufacturing number and the portable terminal identification information or the mail address are recorded in association with each other, and the portable terminal identification information or the mail address is stored in the HD 211 of the print management server 100. And a user name may be associated and recorded. In this case, in step S103 in FIG. 10A, the CPU 201 of the authentication server 200 transmits the mobile terminal identification information or the mail address as the authentication result to the printer 300a. The printer 300a receives the mobile terminal identification information or the mail address in step S405. Transmit to the print management server 100. Next, the CPU 201 of the print management server 100 acquires the user name held in the HD 211 of the print management server 100 using the mobile terminal identification information or the mail address transmitted from the printer 300a as a key, and executes the subsequent processing. To be configured.

[Fifth Embodiment]
In the first, second, third, and fourth embodiments, the print management server 100 is provided with form data, and the print data of the form data is output from the print management server 100 to the authenticated printer 300a. In the embodiment, one or a plurality of print servers are provided, print data (PDL format) is held in the print server, and print data management information held in the print server is managed by the print management server 100. To do.

  The print management server 100 may be configured to receive a print request from the printer 300a and to instruct the print server to output print data corresponding to the print request to the printer 300a.

  In this configuration, form data is generated in the client terminal 400, and the form data is transmitted as print data to the above-described print server through the printer driver. The print server holds print data transmitted from the client terminal 400.

  The print management server 100 also holds bibliographic information (user name, print data storage server IP address, print data storage path, document name, timestamp, etc.) stored in the print server. . By having this bibliographic information, the print management server 100 can recognize in which print server the print data designated by the printer 300a exists, and the print instruction for the designated print data is sent to the designated print data. This can be done on the print server that holds the data.

  In the first to fifth embodiments, the number of form data to be printed may be changed every time the portable terminal (or IC card (independent)) is held over. In the first to fifth embodiments, each time the portable terminal (or IC card (independent)) is held over the card reader 319, one of the selected forms (one job) is printed. After the portable terminal (or IC card (independent)) is held over, all selected forms may be printed at once. In order to switch between the two configurations, whether to print each job (one job print mode) or all forms at once (all job print mode) in the external memory 211 of the print management server 100 If flag information for identifying the image is stored in advance by a method such as manual, the flag information is read after the sub-thread activation of the print management server 100, and the flag information is specified to be printed for each job. After printing preparation is completed, the mobile terminal (or IC card (independent)) is held over the card reader 319 for each job and printing is performed. If it is specified to print all forms at once, printing preparation is completed. Thereafter, when the portable terminal (or IC card (independent)) is held over the card reader 319 only once, the operation of printing all the forms is performed. When printing all forms at once, the printing process in step S212 in the print management server 100 in FIG. 10B is a process for sequentially printing all forms. Information for identifying the number of form data to be printed each time the portable terminal (or IC card (independent)) is held up may be stored in advance in the external memory 211 of the print management server 100 by a manual method or the like. In the same procedure, the desired number of form data can be printed each time the portable terminal (or IC card (independent)) is held over.

  In the first to fifth embodiments, the description has been made on the assumption that the same portable terminal (or IC card (single)) is always held over the card reader 319. However, in FIG. 10A, the printer 300a is waiting in step S401. Then, even if you hold another mobile terminal (or IC card (single)) with an interrupt, you can identify the handheld mobile terminal (or IC card (single)). )) Can be printed and a list of forms can be displayed. That is, even if a plurality of users hold their own portable terminal (or IC card (single)) and hold the same printer 300a over the card reader 319 in any order, the portable terminal ( Alternatively, processing (form list display or printing) according to an IC card (single) can be performed. For example, when user A is printing up to 3 of 10 forms, and user B holds his / her mobile terminal over card reader 319 of printer 300a, printer 300a responds to user B. Process (print form data or list display). Next, when the user A holds his portable terminal over the card reader 319 of the printer 300a, the printer 300a prints the fourth form of the user A.

In the first to fifth embodiments, the description has been made on the assumption that the portable terminal (or IC card (single)) is always held over the card reader of the same printer. However, after the print preparation is completed, the portable terminal ( Or even if you hold the IC card (single), you can specify the printer IP address of the printer that holds the mobile terminal (or IC card (single)), so you can print from a printer other than the printer it can. For example, in a configuration in which the printer 300a and the printer 300b exist, the user A holds up the portable terminal sequentially to the card reader 319 of the printer 300a and performs printing of three of ten forms with the printer 300a. Then, when the user A holds the portable terminal over the card reader 319 of the printer 300b, the fourth form is printed from the printer 300b.
More specifically, it is determined (printer determination) whether the printer IP address in FIG. 11 (the IP address of the printer 300a) matches the IP address of the printer over which the portable terminal is currently held. If the form data is instructed to be output to 300a and they do not match (that is, the printer over which the portable terminal is currently held is the printer 300b), the form data is instructed to output to the printer 300b.

  Moreover, in the said 1st-5th embodiment, when using the portable terminal, it demonstrated on the assumption that the IC card was built in the portable terminal, but even if the IC card and the portable terminal are separated separately, By associating the portable terminal, printing can be performed in the same procedure. In this case, in FIG. 9, the IC card and the portable terminal 500 can be associated by holding the IC card to be associated with the portable terminal 500 over the card reader of the authentication server 200. When printing is performed, when the IC card is held over the card reader 319 of the printer 300a, the form data list is transmitted to the associated portable terminal 500. After selecting a form on the portable terminal 500, when the IC card associated with the card reader 319 of the printer 300a is held over, printing is executed for each job, and the remaining number is notified to the portable terminal 500.

  Further, the configuration and contents of the various data described above are not limited to this, and it goes without saying that the various data and configurations are configured according to the application and purpose.

  Although one embodiment has been described above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or recording medium, and specifically includes a plurality of devices. The present invention may be applied to a system including a single device.

  The configuration of the data processing program that can be read by the server device according to the present invention will be described below with reference to the memory map shown in FIG.

  FIG. 17 is a diagram for explaining a memory map of a recording medium (storage medium) for storing various data processing programs readable by the server according to the present invention.

  Although not particularly illustrated, information for managing a program group stored in the recording medium, for example, version information, creator, etc. is also stored, and information depending on the OS on the program reading side, for example, a program is identified and displayed. Icons may also be stored.

  Further, data depending on various programs is also managed in the directory. In addition, when a program or data to be installed is compressed, a program to be decompressed may be stored.

  A program for causing a computer to execute the functions shown in FIGS. 9, 10A, 10B, 10C, 16, 24, 25, and 26 in this embodiment is installed from the outside, and these functions are installed in the program. It may be performed by a host computer. In such a case, the present invention can be applied even when an information group including a program is supplied to an output device from a recording medium such as a CD-ROM, a flash memory, or an FD or from an external recording medium via a network. It is.

  As described above, a recording medium in which a program code of software for realizing the functions of the above-described embodiments is recorded is supplied to the system or apparatus, and the computer (or CPU or MPU) of the system or apparatus is stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by reading and executing the program code.

  In this case, the program code itself read from the recording medium realizes the new function of the present invention.

  As a recording medium for supplying the program code, for example, a flexible disk, a hard disk, an optical disk, a magneto-optical disk, a CD-ROM, a CD-R, a DVD-ROM, a magnetic tape, a nonvolatile memory card, a ROM, an EEPROM, A silicon disk or the like can be used.

  Further, by executing the program code read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) or the like running on the computer based on the instruction of the program code. It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the actual processing and the processing is included.

  Furthermore, after the program code read from the recording medium is written in a memory provided in a function expansion board inserted in the computer or a function expansion unit connected to the computer, the function expansion is performed based on the instruction of the program code. It goes without saying that the case where the CPU or the like provided in the board or the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  Further, the present invention may be applied to a system composed of a plurality of devices or an apparatus composed of a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program represented by software for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  Furthermore, by downloading and reading out a program represented by software for achieving the present invention from a server, database, etc. on a network using a communication program, the system or apparatus can enjoy the effects of the present invention. It becomes.

  In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

1 is a system configuration diagram illustrating an example of a configuration of a printing system to which a print management server and a printer of the present invention can be applied. FIG. 2 is a block diagram illustrating a hardware configuration of an information processing apparatus applicable to the client terminal 400, the print management server 100, and the authentication server 200 illustrated in FIG. FIG. 2 is a block diagram illustrating an example of a hardware configuration of a controller unit 316 of the printer 300 illustrated in FIG. 1. It is a block diagram explaining an example of the hardware constitutions of the portable terminal 500 shown in FIG. FIG. 2 is a schematic diagram illustrating an example of a form management database stored in an external memory 211 of the print management server 100 illustrated in FIG. 1. FIG. 2 is a schematic diagram illustrating an example of a printer driver related table stored in an external memory 211 of the print management server 100 illustrated in FIG. 1. FIG. 2 is a schematic diagram illustrating an example of a printer display unit presence / absence table stored in an external memory 211 of the print management server 100 illustrated in FIG. 1. It is a schematic diagram which shows an example of the table for authentication memorize | stored in the external memory 211 of the authentication server 200 shown in FIG. It is a flowchart which shows an example of the 1st control processing procedure in this invention. It is a part of flowchart which shows an example of the 2nd control processing procedure in this invention. It is a part of flowchart which shows an example of the 2nd control processing procedure in this invention. It is a part of flowchart which shows an example of the 2nd control processing procedure in this invention. FIG. 2 is a diagram illustrating an example of a thread management table stored in a RAM 203 of the print management server 100 illustrated in FIG. 1. It is a schematic diagram which shows an example of the form data list displayed on the display part 415 of the portable terminal 500 in this invention. 4 is a schematic diagram illustrating an example of a form data list displayed on the printer 300 in the present invention. FIG. FIG. 2 is a schematic diagram illustrating an example of a print management table stored in a RAM 203 of the print management server 100 illustrated in FIG. 1. FIG. 5 is a schematic diagram illustrating an example of each message displayed on a display unit 415 of the mobile terminal 500 illustrated in FIG. 4. It is a flowchart which shows an example of the 4th control processing procedure in this invention. It is a figure explaining the memory map of the recording medium (storage medium) which stores the various data processing program which can be read (read) by the server apparatus based on this invention. 3 is a diagram illustrating an example of a print information set request transmitted from the printer 300 illustrated in FIG. 1 to the print management server 100. FIG. FIG. 2 is a diagram illustrating an example of a print information set of a form data list transmitted and received between the print management server 100 and the printer 300 or the portable terminal 500 illustrated in FIG. 1. FIG. 3 is a diagram illustrating an example of a print information set of status codes transmitted and received between the print management server 100 and the printer 300 or the portable terminal 500 illustrated in FIG. 1. 3 is a diagram illustrating an example of a print information set of a print start command transmitted from the print management server 100 illustrated in FIG. 1 to the printer 300. FIG. FIG. 2 is a diagram illustrating an example of a print information set of a print completion notification transmitted from the printer 300 illustrated in FIG. 1 to the print management server 100. FIG. 3 is a diagram illustrating an example of a print information set of the number of remaining cases transmitted from the print management server 100 illustrated in FIG. 1 to the printer 300 or the mobile terminal 500. 6 is a flowchart showing an example of a procedure for generating a print management table executed by a CPU 201 of the print management server 100 shown in FIG. 1 in a second control processing procedure according to the present invention. 10 is a flowchart illustrating an example of a print management table generation procedure executed by the CPU 201 of the print management server 100 illustrated in FIG. 1 in the fourth control processing procedure according to the present invention. It is a flowchart which shows an example of the 3rd control processing procedure in this invention. FIG. 10 is a diagram illustrating an example of a print information set request in a third control processing procedure transmitted from the printer 300 illustrated in FIG. 1 to the print management server 100. FIG. 10 is a diagram illustrating an example of a thread management table in a third control processing procedure stored in a RAM 203 of the print management server 100 illustrated in FIG. 1.

Explanation of symbols

100: Print management server 200: Authentication server 201, 301: CPU
202, 303, 417 ... ROM
203, 302, 418 ......... RAM
205 ......... Input controller 206 ......... Video controller 207 ......... Memory controller 208 ......... Communication I / F controller 209 ......... Keyboard (KB)
210 ……… CRT display (CRT)
211 ......... External memory 300a, 300b ......... Printer 304 ......... Hard disk drive (HDD)
305 ... Network interface (Network I / F)
306 ... Modem (MODEM)
307 ......... Operation unit interface (operation unit I / F)
308 ......... Operation unit 309 ......... System bus 310 ......... Raster image processor (RIP)
311: Printer interface (printer I / F)
312 ... Printer unit 313 ... Scanner interface (scanner I / F)
314 ......... Scanner unit 315 ......... Image bus 316 ......... Controller unit 317 ......... Image processing unit 318 ......... External interface (external I / F)
319 ... Card reader 320 ... Image bus interface (IMAGE BUS I / F)
400 ......... Client terminal 411 ......... Control unit 412 ......... Receiving unit 413 ......... Sending unit 414 ......... Transmission / reception unit 415 ......... Display unit 416 ......... Input unit 419 ......... IC card 500 ......... Mobile terminals 501, 1404, 1904, 2103, 2203 ......... Time stamps 502, 802, 1102, 1401, 1801, 1905, 2104, 2204, 2901, 3002 ......... User names 503, 1906 ......... Documents Name 504 ... Print status 505 ... Form data 600 ... LAN
601, 1402 ...... Printer name 602, 1104, 1803, 2903, 3004 ...... Printer IP address 603 ...... Printer driver name 801 ...... Manufacturing number 803, 2902, 3003 ...... Email address 804 ...... Department ID
805... Department password 806... Administrator authority 807, 1103, 1802... Mobile terminal identification information 1101, 1902, 2002, 2102, 2202, 2302, 3001 ...... Thread ID
1105, 3005... Thread pointer 1201, 1301 ... Form data selection area 1202 ... Send button 1302 ... Print button 1403 ... IP address 1901, 2001, 2101, 2201, 2301 ... Information type 1903 ... ... Number of forms 2003 ... ... Status code 2303 ... ... Number of remaining cases

Claims (16)

  1. A printer including a reading unit reading a storage medium, the print management server for managing in association with the print data and the user identification information is a printing system connected via a network,
    The printer is
    User identification information transmitting means for transmitting user identification information for specifying a user obtained by reading a predetermined area of a storage medium to the print management server;
    The print management server
    Management means for managing user identification information and information for identifying a mobile terminal associated with the user identification information;
    User identification information receiving means for receiving the user identification information from the printer ;
    List information including the print data identification information of the print data associated with the user identification information received by the user identification information reception unit, managed by the user identification information and the management unit received by the user identification information reception unit List information transmitting means for transmitting to the mobile terminal corresponding to the information specifying the mobile terminal according to the user identification information ;
    A print request receiving means for receiving print data identification information instructed to be printed from a portable terminal that has transmitted the list information including the print data identification information;
    Waiting means for waiting again to receive user identification information from the printer after receiving the print data identification information instructed to be printed by the print request receiving means;
    The waiting in the waiting means, when receiving the re-user identification information by the user identification information reception unit, so as to print the print data corresponding to print data identification information received by the print request receiving means by the printer, the output A printing system comprising: print data output command means for commanding.
  2. The management means manages the user identification information, the portable terminal, and the printer that has received the user identification information in association with each other,
    The print data output command means receives the user identification information again from the printer managed by the management means by the user identification information receiving means while waiting in the standby means, thereby printing corresponding to the print data identification information. The printing system according to claim 1, wherein a data output command is issued.
  3. The storage medium is provided in a mobile terminal,
    The user identification information transmission means transmits user identification information obtained by holding the portable terminal over the reading unit to the print management server,
    The print data output command means responds to the print data identification information by receiving from the printer user identification information obtained by the user identification information receiving means being held over the reading unit again by the user identification information receiving means. The printing system according to claim 1, wherein an output command for print data to be printed is issued.
  4. The waiting unit prepares printing of print data corresponding to the print data identification information instructed to print;
    4. The printing system according to claim 1, wherein the print data output command means issues an output command of the print data prepared for printing.
  5. The print preparation is generating print data to be sent to the printer;
    The print management server
    According to claim 4, further comprising a print ready notifying means for notifying a state in which generation is complete the print data output instruction by the print data output command means to at least one of the printer and the mobile terminal Printing system.
  6. The print management server
    First determination means for determining whether or not the printer has a display unit;
    The list information transmission unit transmits list information including print data identification information of the print data to the printer when the first determination unit determines that the printer has a display unit, and the display unit when it is determined that no printing system according to any one of claims 1 to 5, characterized in that to transmit the list information including the print data identification information of the print data to the mobile terminal.
  7. The management means manages portable terminal identification information of a portable terminal corresponding to user identification information,
    The print management server
    Accordance portable terminal identification information before Symbol mobile terminal, comprising a second determining means for determining whether to transmit the list information including the print data identification information of the print data to the mobile terminal,
    The list information transmission unit transmits the list information including the print data identification information of the print data to the portable terminal of the portable terminal identification information when the second determination unit determines to transmit to the portable terminal. The printing system according to claim 6 .
  8. When the first determination unit determines that the printer does not have a display unit and the second determination unit determines not to transmit to the portable terminal, the list information transmission unit The printing system according to claim 7 , wherein an output command for print data associated with the user identification information is issued without transmitting the list information.
  9. The print management server
    Printing system according to any one of claims 1 to 8, characterized in that it comprises a non-output print data number notifying means for notifying the number of print data that has not been output to at least one of the printer and the portable terminal.
  10. The print management server
    The print data output command means is instructed to print whenever the user identification information receiving means receives user identification information each time the printer reads a predetermined area of the storage medium, and each time the user identification information is received. the system according to any one of claims 1 to 9, characterized in that the output command of the print data corresponding to print data identification information.
  11. The print management server
    While waiting in the waiting means, when receiving the re-user identification information by the user identification information reception unit, and a printer that the received, and a printer that has received the user identification information in the user identification information reception unit previously Printer determination means for determining whether or not they match,
    The print data output instruction means, when the printer determination means determines that they do not match, the print data identification information instructed to be printed with the printer that has received the user identification information again by the user identification information receiving means as the output destination printing system according to any one of claims 1 to 10 and outputs commands for the print data corresponding to.
  12. Provided with a reading unit that reads the storage medium, connected via a network to a printer that transmits user identification information for identifying a user obtained by reading a predetermined area of the storage medium, and corresponding print data to the user identification information A print management server for managing
    Management means for managing user identification information and information for identifying a mobile terminal associated with the user identification information;
    User identification information receiving means for receiving the user identification information from the printer;
    List information including print data identification information of print data associated with the user identification information received by the user identification information receiving means is managed by the user identification information received by the user identification information receiving means and the management means. List information transmitting means for transmitting to the mobile terminal corresponding to the information specifying the mobile terminal according to the user identification information;
    A print request receiving means for receiving print data identification information instructed to be printed from a portable terminal that has transmitted the list information including the print data identification information;
    Waiting means for waiting again to receive user identification information from the printer after receiving the print data identification information instructed to be printed by the print request receiving means;
    When the user identification information is received by the user identification information receiving unit again after waiting in the standby unit, the print data corresponding to the print data identification information received by the print request receiving unit is output to be printed by the printer. Print data output command means to command and
    A print management server comprising:
  13. A printing system control method in which a printer including a reading unit that reads a storage medium and a print management server that manages print data in association with user identification information are connected via a network.
    The printer is
    A user identification information transmission step of transmitting user identification information for identifying a user obtained by reading a predetermined area of the storage medium to the print management server;
    The print management server is
    A management step for managing user identification information and information identifying a mobile terminal associated with the user identification information;
    A user identification information receiving step for receiving the user identification information from the printer;
    List information including print data identification information of print data associated with the user identification information received in the user identification information receiving step is managed in the user identification information received in the user identification information receiving step and the management step. According to user identification information, a list information transmission step for transmitting to a mobile terminal corresponding to information for identifying the mobile terminal;
    A print request receiving step of receiving print data identification information instructed to be printed from a portable terminal that has transmitted the list information including the print data identification information;
    A standby step of waiting to receive user identification information from the printer again after receiving the print data identification information instructed for printing by the print request receiving step;
    When waiting in the waiting step and receiving the user identification information again in the user identification information receiving step, the print data corresponding to the print data identification information received in the print request receiving step is output to be printed by the printer. Print data output command step to order and
    The control method characterized by performing.
  14. Provided with a reading unit that reads the storage medium, connected via a network to a printer that transmits user identification information for identifying a user obtained by reading a predetermined area of the storage medium, and corresponding print data to the user identification information A print management server control method for managing
    The print management server
    A management step for managing user identification information and information identifying a mobile terminal associated with the user identification information;
    A user identification information receiving step for receiving the user identification information from the printer;
    List information including print data identification information of print data associated with the user identification information received in the user identification information receiving step is managed in the user identification information received in the user identification information receiving step and the management step. According to user identification information, a list information transmission step for transmitting to a mobile terminal corresponding to information for identifying the mobile terminal;
    A print request receiving step of receiving print data identification information instructed to be printed from a portable terminal that has transmitted the list information including the print data identification information;
    A standby step of waiting to receive user identification information from the printer again after receiving the print data identification information instructed for printing by the print request receiving step;
    When waiting in the waiting step and receiving the user identification information again in the user identification information receiving step, the print data corresponding to the print data identification information received in the print request receiving step is output to be printed by the printer. Print data output command step to order and
    The control method characterized by performing.
  15. A printing system program in which a printer including a reading unit that reads a storage medium and a print management server that manages print data in association with user identification information are connected via a network.
    The printer
    Functioning as user identification information transmitting means for transmitting user identification information for identifying a user obtained by reading a predetermined area of a storage medium to the print management server,
    The print management server;
    Management means for managing user identification information and information for identifying a mobile terminal associated with the user identification information;
    User identification information receiving means for receiving the user identification information from the printer;
    List information including print data identification information of print data associated with the user identification information received by the user identification information receiving means is managed by the user identification information received by the user identification information receiving means and the management means. List information transmitting means for transmitting to the mobile terminal corresponding to the information specifying the mobile terminal according to the user identification information;
    A print request receiving means for receiving print data identification information instructed to be printed from a portable terminal that has transmitted the list information including the print data identification information;
    Waiting means for waiting again to receive user identification information from the printer after receiving the print data identification information instructed to be printed by the print request receiving means;
    When the user identification information is received by the user identification information receiving unit again after waiting in the standby unit, the print data corresponding to the print data identification information received by the print request receiving unit is output to be printed by the printer. Print data output command means to command and
    A program characterized by making it function.
  16. Provided with a reading unit that reads the storage medium, connected via a network to a printer that transmits user identification information for identifying a user obtained by reading a predetermined area of the storage medium, and corresponding print data to the user identification information A print management server program for managing
    The print management server;
    Management means for managing user identification information and information for identifying a mobile terminal associated with the user identification information;
    User identification information receiving means for receiving the user identification information from the printer;
    List information including print data identification information of print data associated with the user identification information received by the user identification information receiving means is managed by the user identification information received by the user identification information receiving means and the management means. List information transmitting means for transmitting to the mobile terminal corresponding to the information specifying the mobile terminal according to the user identification information;
    A print request receiving means for receiving print data identification information instructed to be printed from a portable terminal that has transmitted the list information including the print data identification information;
    Waiting means for waiting again to receive user identification information from the printer after receiving the print data identification information instructed to be printed by the print request receiving means;
    When the user identification information is received by the user identification information receiving unit again after waiting in the standby unit, the print data corresponding to the print data identification information received by the print request receiving unit is output to be printed by the printer. Print data output command means to command and
    A program characterized by making it function.
JP2008152926A 2008-06-11 2008-06-11 Printing system, print management server, control method therefor, and program Active JP4881915B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2008152926A JP4881915B2 (en) 2008-06-11 2008-06-11 Printing system, print management server, control method therefor, and program

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
JP2008152926A JP4881915B2 (en) 2008-06-11 2008-06-11 Printing system, print management server, control method therefor, and program

Publications (3)

Publication Number Publication Date
JP2009301185A JP2009301185A (en) 2009-12-24
JP2009301185A5 JP2009301185A5 (en) 2011-09-08
JP4881915B2 true JP4881915B2 (en) 2012-02-22

Family

ID=41548032

Family Applications (1)

Application Number Title Priority Date Filing Date
JP2008152926A Active JP4881915B2 (en) 2008-06-11 2008-06-11 Printing system, print management server, control method therefor, and program

Country Status (1)

Country Link
JP (1) JP4881915B2 (en)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5540644B2 (en) * 2009-10-09 2014-07-02 株式会社リコー Printing system and printing method
JP5523422B2 (en) * 2010-12-08 2014-06-18 京セラドキュメントソリューションズ株式会社 Mobile printing system and server device
JP5523423B2 (en) * 2010-12-08 2014-06-18 京セラドキュメントソリューションズ株式会社 Mobile printing system and server device
JP5523424B2 (en) * 2010-12-08 2014-06-18 京セラドキュメントソリューションズ株式会社 Mobile printing system
JP5453370B2 (en) * 2010-12-08 2014-03-26 京セラドキュメントソリューションズ株式会社 Mobile printing system, print control apparatus, and image forming apparatus
JP5453371B2 (en) * 2010-12-08 2014-03-26 京セラドキュメントソリューションズ株式会社 Mobile printing system and portable terminal device program
JP5602058B2 (en) * 2011-02-28 2014-10-08 京セラドキュメントソリューションズ株式会社 Mobile printing system
JP5241874B2 (en) * 2011-03-25 2013-07-17 中国電力株式会社 Multi-hop communication method and communication apparatus
JP5780099B2 (en) * 2011-09-30 2015-09-16 ブラザー工業株式会社 Image recording apparatus, image recording system, and program
JP5550750B2 (en) * 2013-01-23 2014-07-16 京セラドキュメントソリューションズ株式会社 Image forming system and server device
JP5550749B2 (en) * 2013-01-23 2014-07-16 京セラドキュメントソリューションズ株式会社 Image forming system and server device
JP5825336B2 (en) * 2013-06-27 2015-12-02 キヤノンマーケティングジャパン株式会社 Information processing system, image forming apparatus, processing method thereof, and program
CN104615388B (en) 2013-11-01 2017-12-22 精工爱普生株式会社 Print control system
IN2014DE02931A (en) 2013-11-01 2015-06-26 Seiko Epson Corp
JP6281248B2 (en) * 2013-11-07 2018-02-21 セイコーエプソン株式会社 Printing apparatus, printing apparatus control method, and printing control system
JP6421643B2 (en) * 2015-02-27 2018-11-14 ブラザー工業株式会社 Image forming apparatus, server apparatus, and communication system
JP6421644B2 (en) * 2015-02-27 2018-11-14 ブラザー工業株式会社 Image forming apparatus, server apparatus, and communication system

Also Published As

Publication number Publication date
JP2009301185A (en) 2009-12-24

Similar Documents

Publication Publication Date Title
US8964206B2 (en) Printing device, management device and management method
KR101458664B1 (en) Printing system, printing method, print server, control method, and storage medium
EP2409483B1 (en) Image forming apparatus and information processing system
CN101573685B (en) Printing management server, printing management method and program, and recording medium
US7327478B2 (en) Image processing device, information processing method and computer-readable storage medium storing a control program for performing an operation based on whether a function is being set or requested to be set
US8437024B2 (en) Print controlling system having usage restrictions for print data stored in a print managing server, print controlling method, and program
JP4324098B2 (en) Image processing apparatus, image processing method, and computer program
JP4518287B2 (en) Information processing system, information processing apparatus, first authentication server, control method, program, information processing method, information processing program
US8547574B2 (en) Information processing apparatus and method for wireless communication with other information processing apparatuses
JP5328389B2 (en) Image forming apparatus, image forming system, and image forming method
JP5677047B2 (en) Printing system, information processing apparatus, printing method, and program
EP1742165B1 (en) Data processing system, data processing apparatus, and data processing program product suited for transmitting and receiving data among a plurality of image processing apparatuses
US8131798B2 (en) Image processing system, information processing apparatus, control methods thereof, and program
US20080168542A1 (en) Control terminal, image processing apparatus, control system, control program and control method
US7609417B2 (en) Data processing apparatus, image processing apparatus, information notifying method therefor, and program for implementing the method
JP5301627B2 (en) Print control system, print control server, image forming apparatus, processing method thereof, and program
JP4033857B2 (en) Print system, print management server, print method, print management method, and program
JP5081021B2 (en) Information processing system, information processing device, terminal device, and computer program
US8040547B2 (en) Image forming apparatus, printing system, printing method and program
US8576429B2 (en) Image forming system, information processing apparatus, document processing method and printer driver for viewing in an image forming apparatus
US8576415B2 (en) Image processing system, image processing apparatus, and method of controlling image processing apparatus
JP4623469B2 (en) Print server, print system, print method, program, and recording medium
JP4683885B2 (en) File management apparatus and method, image output apparatus, and computer program
JP3998012B2 (en) Image output apparatus, control method therefor, and computer program
JP5219418B2 (en) File transmission apparatus, method, and program

Legal Events

Date Code Title Description
A621 Written request for application examination

Free format text: JAPANESE INTERMEDIATE CODE: A621

Effective date: 20091209

A711 Notification of change in applicant

Free format text: JAPANESE INTERMEDIATE CODE: A712

Effective date: 20110401

RD02 Notification of acceptance of power of attorney

Free format text: JAPANESE INTERMEDIATE CODE: A7422

Effective date: 20110425

A521 Written amendment

Free format text: JAPANESE INTERMEDIATE CODE: A523

Effective date: 20110725

A977 Report on retrieval

Free format text: JAPANESE INTERMEDIATE CODE: A971007

Effective date: 20111028

TRDD Decision of grant or rejection written
A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

Effective date: 20111108

A01 Written decision to grant a patent or to grant a registration (utility model)

Free format text: JAPANESE INTERMEDIATE CODE: A01

A61 First payment of annual fees (during grant procedure)

Free format text: JAPANESE INTERMEDIATE CODE: A61

Effective date: 20111205

R150 Certificate of patent or registration of utility model

Free format text: JAPANESE INTERMEDIATE CODE: R150

FPAY Renewal fee payment (event date is renewal date of database)

Free format text: PAYMENT UNTIL: 20141209

Year of fee payment: 3

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

S111 Request for change of ownership or part of ownership

Free format text: JAPANESE INTERMEDIATE CODE: R313111

R360 Written notification for declining of transfer of rights

Free format text: JAPANESE INTERMEDIATE CODE: R360

R370 Written measure of declining of transfer procedure

Free format text: JAPANESE INTERMEDIATE CODE: R370

S111 Request for change of ownership or part of ownership

Free format text: JAPANESE INTERMEDIATE CODE: R313111

R360 Written notification for declining of transfer of rights

Free format text: JAPANESE INTERMEDIATE CODE: R360

R370 Written measure of declining of transfer procedure

Free format text: JAPANESE INTERMEDIATE CODE: R370

S111 Request for change of ownership or part of ownership

Free format text: JAPANESE INTERMEDIATE CODE: R313111

R350 Written notification of registration of transfer

Free format text: JAPANESE INTERMEDIATE CODE: R350

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250

R250 Receipt of annual fees

Free format text: JAPANESE INTERMEDIATE CODE: R250