Source: https://patents.google.com/patent/JP4241577B2/en
Timestamp: 2019-12-09 08:41:49
Document Index: 251325600

Matched Legal Cases: ['art 31', 'art 33', 'art, 12', 'art, 13', 'art, 14', 'art, 15', 'art, 16', 'art, 17', 'art, 18', 'art, 20']

JP4241577B2 - Service registration system, server, terminal device and peripheral device - Google Patents
Service registration system, server, terminal device and peripheral device Download PDF
JP4241577B2
JP4241577B2 JP2004322948A JP2004322948A JP4241577B2 JP 4241577 B2 JP4241577 B2 JP 4241577B2 JP 2004322948 A JP2004322948 A JP 2004322948A JP 2004322948 A JP2004322948 A JP 2004322948A JP 4241577 B2 JP4241577 B2 JP 4241577B2
JP2004322948A
JP2006135699A (en
2004-11-05 Application filed by ブラザー工業株式会社 filed Critical ブラザー工業株式会社
2004-11-05 Priority to JP2004322948A priority Critical patent/JP4241577B2/en
2006-05-25 Publication of JP2006135699A publication Critical patent/JP2006135699A/en
2009-03-18 Publication of JP4241577B2 publication Critical patent/JP4241577B2/en
The present invention relates to a service registration system or the like for registering usage information related to a service for a peripheral device that can function using a service via a network.
In recent years, peripheral devices (for example, printer devices, scanner devices, facsimile devices, multi-function devices, etc.) whose functions can be expanded by communicating with a server that provides various services (for example, data processing) via a network And other devices having network functions have been proposed. Further, it has been proposed that operation information (for example, service menu, service parameters, etc.) necessary for using a service is downloaded from a server and used (for example, Patent Document 1).
JP-A-9-238215
However, the display panel of such a peripheral device is generally very poor as compared with a terminal device such as a personal computer. For example, a description of a service that has been newly provided can be given by using the peripheral device. There was a problem that this could not be done sufficiently for the elderly. In addition, the operation panel is generally very poor, and it has not been possible to request a complicated operation from the user when newly applying for a service to be used by a peripheral device.
Therefore, it is conceivable that only a registration application, which is an important process, can be performed using a terminal device with a more enhanced user interface. However, in many cases, it is necessary to register information such as identification information (for example, URL) of the server providing the service and attribute information (for example, user name and password) of the service in the peripheral device. The peripheral device cannot use the service provided by the server simply by making a registration application to the server using the existing terminal device.
The present invention has been made in view of such a problem, and when registering a service used by a peripheral device, a registration application can be made using a terminal device having a user interface more enhanced than the peripheral device, and the peripheral device An object of the present invention is to provide a service registration system or the like that enables a device to use a service provided by a server.
The service registration system according to claim 1, which has been made to solve the above problem, includes a server that provides a service via a network, and a peripheral device that can use the service by communicating with the server, A service registration system including a terminal device capable of communicating with a server and peripheral devices. When the terminal device receives registration request information, which is information related to registration for using the service, from the user of the terminal device, the terminal device transmits the registration request information to the server, and the server receives the registration request information from the terminal device. When received, the service use necessary information necessary for using the service is transmitted to the terminal device. When the terminal device receives the service use necessary information from the server, the terminal device transmits the service use necessary information to the peripheral device. When the peripheral device receives the service use necessary information from the terminal device, the terminal device stores the information and can use the service. It is characterized by becoming a state.
Note that “service” here is a general term for functions that can obtain a desired result through communication between a peripheral device and a server. For example, OCR, translation, calibration, voice conversion, data storage, etc. Can be mentioned. The “registration request information” is information such as service type, usage period, user name, password, and the like. The “service use necessary information” is, for example, information such as identification information of a server that provides a service (for example, the URL of the server), service attribute information (for example, a user name or password for using the service), and the like. .
According to such a service registration system, a user of a peripheral device that does not have a sufficient user interface uses a terminal device with a rich user interface for registration for using the service, which is generally complicated. Can be done. That is, it is possible to easily request registration using a terminal device having a richer user interface as compared to the peripheral device, and registration of service use necessary information to the peripheral device is performed through a series of operations. Therefore, it is possible to reduce the registration error of the user and the difficulty of operation at the time of registration.
By the way, as a specific configuration example, the server, the terminal device, and the peripheral device may be configured as described in claim 2. That is, when the server receives the registration request information from the terminal device via the server communication means that communicates with the peripheral device and the terminal device, the server communication means determines whether the registration request information is appropriate, communicates with peripheral devices through a service notification information transmission control means for transmitting the service required information necessary to the terminal device via the server communication means when using the service, the server communication means if appropriate And a service providing means for providing the service.
The terminal device includes registration information receiving means for receiving registration request information, which is information related to registration for using the service, from a user, terminal device communication means for communicating with the server and peripheral devices, and registration information receiving means. Registration request information transmission control means for transmitting the received registration request information to the server via the terminal device communication means, and when the service use necessary information is received from the server via the terminal device communication means, the peripheral device via the terminal device communication means Service usage required information transfer control means for transmitting service usage required information to the network.
In addition, the peripheral device uses the peripheral device communication means for communicating with the server and the terminal device, the storage means for storing the information, and the service use for the storage means upon receiving the service use necessary information from the terminal device via the peripheral device communication means. as with the service required information registration control means for storing the required information, and a service implementation unit to implement the service by communicating with the server via the terminal device communication unit based on the service usage required information storing means for storing Configure.
Thus, if a server, a terminal device, and a peripheral device are comprised, the effect mentioned above can be acquired.
By the way, when a user inputs registration request information to a terminal device, it is good to be able to input based on an input screen. Further, the screen configuration information that is the basis of the input screen may be stored in advance in the terminal device, and the input information may be configured by using the stored information. It should be stored on the side. That is, the server can further provide screen configuration information, which is configuration information of the input screen used when the registration information receiving unit of the terminal device receives registration request information from the user, to the terminal device via the server communication unit. The terminal device further includes a display unit for displaying an image, and when the registration information receiving unit receives the registration request information from the user, the terminal device further includes a display unit for displaying an image. An input screen configured based on the screen configuration information acquired from the server via the terminal device communication means may be displayed (Claim 3).
With this configuration, the user can input the registration request information according to the input screen displayed on the display means, so that the registration request information can be input more accurately and easily. Further, since the screen configuration information that is the basis of the input screen is stored on the server side, the input screen displayed on the terminal device is also corrected by the server administrator correcting the screen configuration information. . Therefore, the specification of the input screen can be centrally managed on the server side, and the input screen can be easily changed.
By the way, when there are a plurality of peripheral devices or when the peripheral devices are connected to a network to which many devices such as a LAN are connected, the service use necessary information transfer control means of the terminal device is sent from the server. It is necessary to specify a peripheral device that transmits the received service use necessary information.
Therefore, it is preferable to be as described in claim 4. In other words, the input screen displayed by the display means includes a part for inputting peripheral device specifying information, which is information for specifying the peripheral device, and the registration request information transmission control means uses the registration information as one of the registration request information. The peripheral device specifying information received by the receiving means is transmitted to the server. Then, the service use necessary information transmission control unit of the server transmits the peripheral device specifying information received from the terminal device together with the service use necessary information to the terminal device, and the service use necessary information transfer control unit of the terminal device has received from the server. and identifying the peripheral device for transmitting a service necessary information based on the peripheral device identifying information, the service usage required information may and transmits to the identified peripheral device.
If this is the case, the user can explicitly specify the peripheral device to be registered from now on, so incorrect information registered in the terminal device (for specifying the peripheral device) Information) is used, and it is possible to prevent the service use necessary information from being transmitted to the wrong peripheral device. Further, since information for specifying the peripheral device is transmitted to the server, the server can store the information and use the information when providing the service.
Further, as another method for specifying the peripheral device to which the service use necessary information transfer control means of the terminal device transmits the service use necessary information, it may be as described in claim 5. In other words, the input screen displayed by the display means has a part for inputting peripheral device specifying information, which is information for specifying the peripheral device, and the terminal device can further store the peripheral device specifying information. When the registration request information is transmitted to the server, the registration request information transmission control unit stores the peripheral device identification information received by the registration reception unit in the peripheral device identification information storage unit. The service use necessary information transfer control means, when receiving the service use necessary information from the server, transmits the service use necessary information based on the peripheral device specifying information stored in the peripheral device specifying information storage means. The service use necessary information may be transmitted to the specified peripheral device.
Even in this case, since the user can explicitly specify the peripheral device to be registered from now, incorrect information registered in the terminal device (for specifying the peripheral device) Information) is used, and the possibility that service use necessary information is transmitted to the wrong peripheral device can be reduced.
By the way, on the above-described input screen, the user may directly input information for specifying the peripheral device (for example, input an IP address assigned to the peripheral device). If this is the case, the user needs to know the information completely in advance, which may be a factor that hinders smooth input. Therefore, it is convenient for the user if the user can input information on the input screen without knowing information for specifying the peripheral device in advance. Therefore, the terminal device further includes search means for searching for a peripheral device with which the terminal device communication means can communicate according to a predetermined condition, and the display means displays information related to the peripheral device searched by the search means on one of the input screens. It is good to display as a part (Claim 6).
If this is the case, the user can select and input the intended peripheral device from the information displayed on the input screen even if he / she vaguely remembers information for specifying the peripheral device. , It is possible to reduce the burden of user input.
In addition, the service transfer control means may be configured to send the service use necessary information to the peripheral device as it is without any inquiry to the user when the service use necessary information is received from the server. After inquiring about the presence / absence, the service use necessary information may be transmitted to the peripheral device. In other words, the terminal apparatus further comprises a transfer command receiving unit configured to receive a transfer instruction from the user of the terminal, the service requires data transfer control means receives a service usage required information from the server, the service information necessary A confirmation screen for confirmation may be configured and displayed on the display unit, and only when the transfer command receiving unit receives the transfer command from the user , the service use necessary information may be transmitted to the peripheral device ( Claim 7).
If this is the case, it is possible to prevent information required for use of the service that is not intended by the user from being transmitted to the peripheral device and stored, and to increase the certainty of use registration for the service itself. Can do. It is also possible to dispel the anxiety of the user , for example, “Is the correct service use necessary information transmitted to the peripheral device?”.
The transmission of the service use necessary information performed by the service use necessary information transfer control means may be as follows. First, as a premise, the screen configuration information storage unit of the server further stores the screen configuration information of the confirmation screen in the HTML format, and the service use necessary information transmission control unit of the server includes the screen configuration of the confirmation screen together with the service use necessary information. Information is also sent. Then, the service use necessary information transfer control means of the terminal device forms a confirmation screen based on the screen configuration information transmitted from the server, and transmits the service use necessary information to the peripheral device by the POST method in the HTML request. 8).
If this is the case, the user can instruct the transmission of the service use necessary information to the peripheral device by pressing a button displayed on the page constituted by HTML. That is, the service use necessary information can be easily transmitted without inputting the service use necessary information or selecting the service use necessary information.
By the way, a server as described in claim 9, that is, a server communication unit that communicates with a peripheral device and a terminal device, and a registration request that is information related to registration for using a service from the terminal device via the server communication unit. A service that, upon receiving information, determines whether or not the registration request information is appropriate, and transmits service use necessary information necessary for using the service to the terminal device via the server communication means when it is appropriate Even a server including use necessary information transmission control means and service providing means for providing a service by communicating with a peripheral device via server communication means constitutes a part of the service registration system described above. The above-described effects can be derived by combining with a predetermined terminal device or peripheral device.
A terminal device as claimed in claim 10, that is, a registration information receiving means for receiving registration request information, which is information relating to registration for using a service, from a user, and a terminal device for communicating with a server and peripheral devices A communication means, registration request information transmission control means for transmitting registration request information received by the registration information receiving means to the server via the terminal device communication means, and service use necessary information received from the server via the terminal device communication means. Even a terminal device provided with service use necessary information transfer control means for transmitting service use necessary information to a peripheral device via a terminal device communication means can constitute a part of the service registration system described above, and The above-described effects can be derived by combining with other servers and peripheral devices.
Further, it is necessary to use a service from the terminal device via the peripheral device as described in claim 11, that is, the peripheral device communication means for communicating with the server and the terminal device, the storage means for storing information, and the peripheral device communication means. Service use necessary information registration control means for storing service use necessary information in the storage means when receiving the information, and service by communicating with the server via the terminal device communication means based on the service use necessary information stored in the storage means. Even a peripheral device provided with a service realization means that realizes part of the service registration system described above can be combined with a predetermined server or terminal device to achieve the effects described above.
Hereinafter, for an embodiment to which the present invention is applied, [Description of overall configuration], [Service information registration mechanism], [Service provision mechanism], [Effect], [Modification], [Correspondence with the present invention] [Relationship].
[Description of overall configuration]
As shown in FIG. 1, a service providing system to which a service is provided via a network to which the present invention is applied includes a multifunction machine 10, a directory server 20, a function server 30, a PC 60, and the like. In this embodiment, it is connected via a wide area network 1 such as the Internet so that data communication is possible. Specifically, the multifunction machine 10, the directory server 20, the function server 30, and the PC 60 are connected to the network 1 via routers (R: known broadband routers) 2 to 4, respectively.
The multifunction machine 10 includes a control unit 11, an operation unit 12, a reading unit 13, a recording unit 14, a communication unit 15, a storage unit 16, a sound input unit 17, a sound output unit 18, and the like.
Among these, the control unit 11 includes a CPU, a ROM, a RAM, and the like, and this CPU performs overall control of the entire multifunction machine 10 according to a program stored in the ROM.
2, the operation unit 12 includes a copy key 41, a scanner key 42, a FAX key 43, a service key 44, a setting key 45, up / down / left / right direction keys 46 to 49, an OK key 50, and a cancel key 51. , A display 52 and the like as a user interface.
Returning to FIG. 1, the reading unit 13 is an input device for realizing a function as a scanner. The reading unit 13 reads an image recorded (for example, printed) on a sheet-like recording medium such as paper and reads the image. Generate image data to represent.
The recording unit 14 is an output device for realizing a function as a printer, and prints an image represented by image data on a sheet-like recording medium such as paper.
In addition, the communication unit 15 connects the MFP 10 to the network 1 and performs processing for transmitting and receiving data via the network 1.
The storage unit 16 includes a nonvolatile storage medium such as a hard disk (not shown), and can store input / output data and the like.
The sound input unit 17 inputs sound from a microphone provided in a handset (receiver) (not shown) provided in the multifunction machine 10 and generates sound data (PCM data) representing the sound.
The sound output unit 18 outputs the sound represented by the sound data (PCM data) from a speaker provided in a handset (not shown) or a speaker (not shown) provided in the main body of the multifunction machine 10.
The directory server 20 includes a control unit 21, a communication unit 22, and a storage unit 23.
Among these, the control unit 21 includes a CPU, a ROM, a RAM, and the like, and this CPU performs overall control of the entire directory server 20 in accordance with a program stored in the ROM.
The communication unit 22 connects the directory server 20 to the network 1 and performs processing for transmitting and receiving data via the network 1.
The storage unit 23 includes a hard disk (not shown), and stores data in the hard disk. The storage unit 23 is provided with a service definition information storage unit 24 for storing service definition information 25 described later. The service definition information 25 is data described in XML (eXtensible Markup Language), and is provided by the function server 30 by displaying a service selection screen (to be described later) according to the description (see FIG. 10A). A list of possible services (type of each service and request destination address (URL) can be provided. The definition of each tag in the service definition information 25 is shown in FIG.
The function server 30 includes a control unit 31, a communication unit 32, a storage unit 33, and the like.
Among these, the control part 31 is provided with CPU, ROM, RAM, etc., and this CPU performs overall control of the function server 30 according to the program memorize | stored in ROM. The control unit 31 has a sufficiently high-performance configuration as compared with the control unit 11 of the multifunction machine 10, and can perform processing that is difficult to execute by the control unit 11 of the multifunction machine 10.
The communication unit 32 connects the function server 30 to the network 1 and performs processing for transmitting and receiving data via the network 1.
And the memory | storage part 33 is provided with the hard disk which is not shown in figure, and memorize | stores data in this hard disk. The storage unit 33 includes a service I / F information storage unit 34 for storing service I / F information 36, which will be described later, and a service software 37 for storing processing for providing different services. And a soft storage unit 35. The service I / F information 36 is data described in XML, and a parameter input screen (to be described later) is displayed on the multi-function device 10 according to the description (see FIG. 16). An interface for setting information for requesting provision of service (detailed contents of service, etc.) is realized.
The definition of each tag in the service I / F information 36 is shown in FIG.
The PC 60 includes a control unit 61, an operation unit 62, a display unit 63, a storage unit 64, a communication unit 65, and the like.
Among these, the control unit 61 includes a CPU, a ROM, a RAM, and the like, and the CPU controls the entire PC 60 according to a program stored in the ROM.
The operation unit 62 includes a known keyboard and mouse.
The display unit 63 includes a known CRT, liquid crystal display, or the like.
The storage unit 64 includes a non-volatile storage medium such as a hard disk (not shown), and can store input / output data and the like.
The communication unit 65 connects the PC 60 to the network 1 and performs processing for transmitting and receiving data via the network 1.
[Service information registration mechanism]
In the service providing system, pre-use processing necessary for the MFP 10 to use the service provided by the function server 30 will be described. The pre-use process is a process in which information such as a user is registered in the function server 30 and service information necessary for using the service is stored in the multifunction machine 10.
(1) Overview First, an overview of this process will be described with reference to FIG.
The user operates the operation unit 62 of the PC 60 to request a page for user registration from the function server 30 (S151). This is performed by starting a well-known browser in the PC 60 and inputting the URL of the function server 30 in the address input field of the browser or selecting the URL from the bookmark.
Subsequently, a user registration page (HTML1 to be described later) is returned from the function server 30 (S152). The PC 60 that has received the user registration page displays the registration page on the display unit 63 and prompts the user to input necessary items (type of service for which usage registration is performed, user ID, password, etc.).
When the user finishes inputting necessary items and presses a transmission button (submit button), the input information is transmitted to the function server 30 (S153), and user registration is performed in the function server 30. This user registration means storing the user as a user who can use the service.
When user registration is performed in the function server 30, a page (HTML2 described later) including service information necessary for using the service is sent to the PC 60 (S154). The PC 60 that has received the page including the service information displays the page on the display unit 63, prompts the user to confirm the registered content, and prompts the user to press the transmission button (submit button).
When the user presses the transmission button (submit button), service information is transmitted to the multifunction device 10 (S155), and the multifunction device 10 that has received the service information stores the service information in the storage unit 16.
Through the flow as described above, a user is registered in the function server 30 and service information necessary for using the service is stored in the multifunction machine 10.
Next, an outline of processing when the MFP 10 actually uses the translation copy service based on the service information will be described. The translation copy service is a service in which a translated document is output from the multifunction device 10 when the multifunction device 10 reads the document to be translated.
In the multifunction device 10, when the user selects the translation copy service, the user ID in the service information is transmitted to the server providing the service (here, the function server 30) (S161).
The function server 30 that has received the user ID determines whether or not the user ID is an ID that can use the service. If the user ID is a user ID that can use the service, the function server 30 sends a scan request to the MFP 10. Send (S162).
Upon receiving the scan request, the MFP 10 prompts the user to scan the document, and transmits scan data obtained as a result of scanning the document to the function server 30 (S163).
The function server 30 that has received the scan data extracts the character information from the scan data, translates it, and transmits the translation result as print data to the MFP 10 together with the print request (S165, S166).
Upon receiving the print request and the print data, the multifunction machine 10 performs printing based on the print data and outputs a translation result.
The function server 30 finally transmits a termination request to the multifunction device 10 (S167), and the multifunction device 10 that has received the termination request terminates the program executing the translation copy service.
This is the end of the description of the processing overview. Next, each process executed by the PC 60, the function server 30, and the multifunction machine 10 will be described.
(2) Processing by PC 60 First, browser processing executed by the control unit 61 of the PC 60 will be described with reference to FIG. The browser process is started when a user operates the operation unit 62 to input an activation instruction.
When the browser process is activated, first, a URL is received (S351). The URL received in this step may be received by being directly input to the address field by the user, or may be received by the user selecting the URL from the bookmark. .
Subsequently, it is determined whether or not an input has been made to a form (for example, FIG. 34A) by operating the operation unit 62 (S355). When the user inputs the form (S355: YES), the input content is reflected on the form (S357), and the state shifts to a state of accepting the input from the user (S353). If any input is received from the user in S353, the process proceeds to S355.
On the other hand, if it is determined in S355 that the form has not been input by the user (S355: NO), it is determined whether or not the URL has been input by operating the operation unit 62 by the user (S355: NO). S359). As described above, the input of the URL includes both the case where the URL is directly input to the address field and the case where the URL is selected from the bookmark. If the URL is input (S359: YES), the content is requested to the input URL destination (S367). The request for content is made by an HTTP request based on HTTP 1.1 (hereinafter simply referred to as “HTTP request”).
If it is determined in S359 that no URL has been input (S359: NO), it is determined whether the user has selected a link (S361). If it is determined that the user has selected the link (S361: YES), the content is requested by the HTTP request to the URL pointed to by the selected link (S367).
On the other hand, if it is determined in S361 that the user has not selected a link (S361: NO), it is determined whether or not the submit button has been pressed by the user (S363). If it is determined that the submit button has been pressed by the user (S363: YES), the content input in the form is transmitted to the URL destination defined in the form by an HTTP request to request the content (S369).
On the other hand, if it is determined in S363 that the user has not pressed the submit button (S363: YES), it is determined whether or not the user has pressed the end button (S365). If it is determined that the user has pressed the end button (S365: YES), the browser process is terminated.
On the other hand, if it is determined in S365 that the user has not pressed the end button (S365: NO), an error is notified by displaying a message indicating an error on the display unit 63 (S381), and The process proceeds to S353.
By the way, after requesting the content in S367 and S369, the content is received by the HTTP response (HTTP response based on HTTP1.1) transmitted from the requested server (here, the function server 30) (S371). Then, it is determined whether or not the received content is a JAVA applet ("JAVA" is a registered trademark) (S373). If the received content is a JAVA applet (S373: YES), the JAVA applet is executed (S379), and the process proceeds to S353 described above.
On the other hand, if the received content is not a JAVA applet (S373: NO), the received content (HTML) is displayed on the display unit 63 (S375), and the process proceeds to S353 described above.
The above is the description of each processing step of the browser process. Since this browser process is a general-purpose process, the process transition in the case of the present invention will be described in particular. First, when the browser process is activated, “http://adgi.com/registpage.html” indicating the html for the user registration process of the function server 30 is input (S351), and the HTML file is requested (S351). S359: YES, S367).
Subsequently, when the HTML file designated by the URL is received (S371), a display screen is configured based on the received HTML file, and the configured screen is displayed on the display unit 63 (S373: NO, S375).
The HTML file received at this time is HTML1 shown in FIG. As shown in FIG. 31, the <form> tag is used, and the address of the MFP 10 to be registered, the service type, the user name (user ID), and the password can be input or specified. The description that composes the screen is made. Further, “POST” is designated as the method of the <form> tag, and “http://adgi.com/regist.cgi” is designated as the request URL. When the submit button is pressed, the name of the MFP 10 to be registered is ip_address, the service type is service_type, the user name (user ID) is user_name, and the password is register_password. Is transmitted to the function server 30 so that it can be referred to.
A specific display screen displayed by HTML1 is shown in FIG. As shown in FIG. 34 (a), the display screen 750 includes an address input field 751 of a device (device from which service information is to be registered), a service type selection field 752, and a user name (user ID). Input field 753, password input field 754, cancel button 755, and submit button 756.
Returning to FIG. 27, when the user makes an input in each entry field of the form, the input is reflected on the screen (S353, S355: YES, S357). When the submit button 756 is pressed, the input contents of the form are transmitted to the above “http://adgi.com/regist.cgi” (function server 30), and the content (HTML file) is requested (S369).
When the content (HTML file) is transmitted from the function server 30, and the HTML file is received by the PC 60, a screen is constructed based on the received HTML file and displayed on the display unit 63 (S371, S373: NO, S375).
The HTML transmitted from the function server 30 is HTML2 shown in FIG. As shown in FIG. 32, the address of the device (multifunction device 10), the name of the service, and the user name input on the previous screen are displayed. Also, <form> tag is used, and service information ("userID" = "Richard", "imfcsessionControlRequestUrl" = "http://adgi.com/sessionControl.cgi", "imfcDisplayNameForBookMark" = "Regist") is hidden information is described.
A specific display screen is shown in FIG. As shown in FIG. 34B, the display screen 760 displays a message for inquiring whether or not to register service information in the device (multifunction device 10), the device address, the service name, the user name, and the registration button 761. It consists of. This registration button 761 is a so-called submit button.
Returning to FIG. 27, when the registration button 761 is pressed, it is determined that the submit button has been pressed by the user (S363: YES), and the service information is transmitted to the multifunction machine 10 (S369).
As a result, the service information is registered on the multifunction device 10 side, and the content (HTML file) of the registration result is returned from the multifunction device 10 (S371), and the screen is configured based on the HTML file and displayed on the display unit 63. (S375).
The HTML file returned from the multifunction machine 10 is HTML3 shown in FIG. As shown in FIG. 33, HTML3 is described to display a message indicating that registration is complete. A specific display screen by the HTML 13 is shown in FIG. As shown in FIG. 34 (c), the display screen 770 is composed of a message signifying completion of registration.
(3) Processing by Function Server 30 Next, Web response processing and user registration processing executed by the control unit 31 of the function server 30 will be described.
(3-1) Web Response Processing First, web response processing will be described with reference to FIG. This Web response process is a process that starts executing as soon as the function server 30 is powered on.
When the Web response process is started, it is first determined whether or not there is an HTTP request from another external device (S451). If there is an HTTP request from another external device (S451: YES), it is determined whether or not the method of the HTTP request is POST (S453). If the method of the HTTP request is POST (S453: YES), it is further determined whether or not the request URL of the HTTP request points to the CGI program for service registration (S461). That is, it is determined whether or not the request URL of the HTTP request is “http://adgi.com/regist.cgi”. If the request URL indicates a CGI program for service registration (S461: YES), a user registration process described later is executed (S463), and when the process ends, the process returns to S451 described above.
On the other hand, in S461, when the request URL of the HTTP request does not indicate a CGI program for service registration (S461: NO), other processing such as executing another CGI program specified in the request URL is performed. Execute (S465). Then, the HTML generated by other processing is transmitted as an HTTP response to the device that has made the HTTP request (S467), and the processing returns to S451 described above.
On the other hand, if the HTTP request method is not POST in S453 described above (S453: NO), it is determined whether or not the HTTP request method is GET (S455). If the method of the HTTP request is not GET (S455: NO), each process according to the type of the method is executed (S455), and an HTTP request is sent with HTML corresponding to the process result as an HTTP response. The data is transmitted to the apparatus (S467), and the process returns to S451 described above.
If the HTTP request method is GET in S455 (S455: YES), whether the request URL of the HTTP request is a page for service registration (http://adgi.com/registpagepage.html) or not. Is determined (S457). If the request URL is a page for service registration (S457: YES), HTML1 shown in FIG. 31 is transmitted to the apparatus that sent the HTTP request (S459), and the process returns to S451 described above.
On the other hand, if the request URL is not a page for service registration (S457: NO), the file corresponding to the request URL is searched from the storage unit 33 (S465), and the file is sent to the device that sent the HTTP request. Transmit (S467). Then, the process returns to S451 described above.
(3-2) User Registration Process Next, a detailed processing procedure of the user registration process corresponding to S463 in FIG. 28 will be described with reference to FIG.
In this user registration process, first, it is determined whether or not the combination of the user ID (user_name) and password (register_password) sent together with the HTTP request exists in the list stored in the storage unit 33 in advance. (S551). This determination is made in consideration of the type of service (service_type) sent together with the HTTP request. When the combination of the user ID (user_name) and password (register_password) sent together with the HTTP request exists in the list (S551: YE)
S) Since the user ID has the right to use the service, the information is stored in the storage unit 33 (S555). Then, HTML2 (see FIG. 32) is transmitted to the apparatus that sent the HTTP request (S557), the user registration process is terminated, and the process returns to the step following S463 in FIG.
On the other hand, if the combination of the user ID (user_name) and password (register_password) sent together with the HTTP request does not exist in the list (S551: NO), HTML1 (FIG. 31) is sent to the device that sent the HTTP request. (See FIG. 28), the user registration process is terminated, and the process returns to the step following S463 in FIG.
(4) Processing by MFP 10 Next, service information storage processing executed by the control unit 11 of the MFP will be described with reference to FIG. This service information storage process is a process that starts executing as soon as the multifunction device 10 is turned on.
When this service information storage process is activated, it is first determined whether or not there is an HTTP request from another device (S651). If there is no HTTP request from another device (S651: NO), the determination in S651 is continued until there is an HTTP request from another device.
On the other hand, if the HTTP request is from another device (S651: YES), it is determined whether the method of the HTTP request is POST (S653). If the method of the HTTP request is not POST (S653: NO), processing according to the method is performed (S655), and an HTTP response is returned to the request source (S657). Then, the process returns to S651 described above.
On the other hand, if the HTTP request method is POST in S653 (S653: YES), the CGI for user registration is indicated in the form information (service information) sent along with the HTTP request. It is determined whether there is a URL (S659). That is, it is determined whether or not the data of the property NAME = “imfcsessionControlRequestUrl” of the information sent together with the HTTP request is “http://adgi.com/sessionControl.cgi”. When there is a URL indicating the CGI for user registration in the form information sent together with the HTTP request, the form information (service information) sent together with the HTTP request is stored in the storage unit 16. Store (S661), and send HTML3 shown in FIG. 33 to the apparatus (that is, PC 60) that has sent the HTTP request (S663). As shown in FIG. 33, the HTML 3 displays a message indicating that registration of service information has been completed. A specific display screen is shown in FIG. As shown in FIG. 34C, the display screen 770 is configured by a message in which the address of the apparatus (that is, the multifunction machine 10) and the type of service are described. The service information stored in the storage unit 16 is used in session processing (see FIG. 12) described later.
When the transmission of HTML3 is completed, the process returns to S651 described above. The description of the service information registration mechanism is completed. Next, the actual service provision mechanism will be described.
[Service provision mechanism]
First, an example of communication performed between the MFP 10 and the function server 30 when a service is provided will be described with reference to a ladder chart of FIG.
The multifunction machine 10 and the function server 30 perform a series of communication processes (sessions) from service activation to service termination. In this session, first, the multifunction machine 10 requests the function server 30 to start a service. Then, the function server 30 transmits a session ID to the multifunction machine 10. Here, the session ID is an identifier for specifying a session in the function server 30. In the subsequent communication, the multifunction machine 10 transmits a session ID in response to the request, and the function server 30 performs a session based on the session ID. Is identified. Thereby, the function server 30 can process a plurality of sessions simultaneously.
Upon receiving the session ID, the multi-function device 10 periodically makes a multi-function device command inquiry, which is a command inquiry to the multi-function device 10, and receives a command in the form of a response from the function server 30. If there is no command to be transmitted in response to the multifunction device command inquiry, the function server 30 transmits that there is no command (no multifunction device command).
In this example, the function server 30 first transmits a UI (user interface) job activation command to the multifunction machine 10. Here, the UI job activation command notifies the start of use of a UI device (operation panel 12) provided in the multifunction machine 10. As a result, UI job communication processing is started between the MFP 10 and the function server 30. This UI job communication process is performed in parallel with the session. Further, in response to the UI job start command, the function server 30 transmits a job ID (identifier unique to the session) for specifying a job in the function server 30. In the UI job communication process, the multifunction machine 10 transmits a session ID and a job ID according to the request, and the function server 30 identifies the job based on the session ID and the job ID. Thereby, the function server 30 can process a plurality of jobs simultaneously. The contents of the UI job communication process will be described later.
Subsequently, the function server 30 transmits an input job activation command to the multifunction machine 10 at a predetermined timing. Here, the input job activation command is a notification of the start of use of an input device (reading unit 13 or sound input unit 17) provided in the multifunction machine 10. As a result, communication processing of the input job is started between the multifunction machine 10 and the function server 30. Then, the communication process of this input job is also performed in parallel with the session, like the UI job. In addition, a job ID is transmitted from the function server 30 to the multi-function device 10 in response to an input job activation command. Then, in the input job communication process, the multifunction device 10 transmits a session ID and a job ID in response to the request, and the function server 30 identifies a job based on the session ID and the job ID. The contents of the input job communication process will be described later.
Subsequently, the function server 30 transmits an output job start command to the multifunction device 10 at a predetermined timing. Here, the output job activation command is a notification of the start of use of an output device (recording unit 14 or sound output unit 18) provided in the multifunction machine 10. As a result, output job communication processing is started between the MFP 10 and the function server 30. The communication process of the output job is also performed in parallel with the session, like the UI job and the input job. In addition, a job ID is transmitted from the function server 30 to the multi-function device 10 in accordance with an output job start command. Then, in the output job communication process, the multifunction device 10 transmits a session ID and a job ID in response to the request, and the function server 30 identifies the job based on the session ID and the job ID. The contents of the output job communication process will be described later.
Subsequently, the function server 30 transmits an output job end instruction, which is a notification of the end of the output job, to the multi-function device 10 at a predetermined timing.
Subsequently, the function server 30 transmits an input job end command, which is a notification to end the input job, to the multi-function device 10 at a predetermined timing.
Subsequently, the function server 30 transmits a UI job end command, which is a notification to end the UI job, to the multi-function device 10 at a predetermined timing.
Subsequently, the function server 30 transmits a service end instruction, which is a notification of the end of the service, to the multi-function device 10 at a predetermined timing.
The above is the content of the session.
Next, UI job communication processing will be described.
In the UI job communication process, first, the multi-function device 10 makes a multi-function device job command inquiry to the function server 30 as a command inquiry to the multi-function device 10. Then, the function server 30 transmits a parameter request to the multifunction device 10. Here, the parameter request is for causing the user of the multifunction device 10 to set parameters necessary for executing the service, and service I / F information is sent from the function server 30 to the multifunction device 10 in accordance with the parameter request. 36 is transmitted.
When receiving the parameter request from the function server 30, the multifunction machine 10 displays a parameter input screen based on the service I / F information 36 on the display 52 of the operation panel 12 (for example, FIG. 16). Then, the parameters set by the user are transmitted to the function server 30.
When the function server 30 receives the parameter from the multifunction device 10, the function server 30 transmits a server reception status that is a notification indicating whether the function server 30 has successfully received the information from the multifunction device 10.
Then, when the multifunction device 10 confirms that the function server 30 has received the parameters normally based on the server reception status received from the function server 30, the service state information that is a request for information regarding the service state is sent to the function server 30. Make a request.
When the function server 30 receives the service status information request from the multifunction device 10, the function server 30 transmits service status information, which is a notification of the status of the function server 30 and the service, to the multifunction device 10.
Thereafter, the service status information request and the transmission of the service status information corresponding thereto are repeated.
Next, input job communication processing will be described.
In the input job communication process, first, the multifunction machine 10 transmits to the function server 30 multifunction machine state information that is information relating to the state of the multifunction machine 10. Then, the function server 30 transmits the multifunction machine parameter to the multifunction machine 10. Here, the MFP parameter is an input device parameter set by the user of the MFP 10 in the UI job communication process.
When the multifunction device 10 receives the multifunction device parameters from the function server 30, the multifunction device 10 transmits a multifunction device reception status that is a notification indicating whether the multifunction device 10 has successfully received the information from the function server 30.
When the function server 30 confirms that the multifunction device 10 has received the information normally based on the reception status of the multifunction device from the multifunction device 10, the function server 30 requests the multifunction device 10 to input data corresponding to the job. Send a request. Here, if the input data corresponding to the job is a scan job (a job executed by a service relating to the image data generated by the reading unit 13), the image data generated by the reading unit 13, a voice input job (sound) PCM data is a job executed by a service relating to sound data representing sound output from the input unit 17.
Upon receiving the input data request from the function server 30, the multifunction device 10 performs a display for prompting the user to perform an input operation (image reading operation or voice input operation), and transmits the input data generated as a result to the function server 30. To do.
When the function server 30 receives the input data from the multi-function device 10, the function server 30 transmits service status information that is a notification of the status of the function server 30 and the service to the multi-function device 10.
Next, output job communication processing will be described.
In the output job communication process, first, the multifunction machine 10 transmits, to the function server 30, multifunction machine status information that is information relating to the state of the multifunction machine 10. Then, the function server 30 transmits the multifunction machine parameter to the multifunction machine 10. Here, the MFP parameter is an output device parameter set by the user of the MFP 10 in the UI job communication process.
When the function server 30 confirms that the multifunction device 10 has received information normally based on the reception status of the multifunction device from the multifunction device 10, the function server 30 transmits output data to the multifunction device 10. Here, if the output data is a print job (a job executed by a service relating to image data representing an image to be printed by the recording unit 14), it represents image data, an audio output job (sound output by the sound output unit 18) PCM data is a job executed by a service related to PCM data.
When the multifunction device 10 receives the output data from the function server 30, the multifunction device 10 performs an output process (printing an image or outputting sound) based on the output data. Then, the multifunction device 10 transmits multifunction device state information, which is information related to the state of the multifunction device 10, to the function server 30.
When the function server 30 receives the MFP status information from the MFP 10, the function server 30 transmits service status information, which is a notification of the status of the function server 30 and the service, to the MFP 10.
Next, processing performed by the control units 11, 21, 31 of the multifunction machine 10, the directory server 20, and the function server 30 will be described.
(1) Processing by Directory Server 20 First, the directory server processing executed by the control unit 21 of the directory server 20 will be described with reference to FIG.
The directory server process is started when an HTTP request is received from the multifunction machine 10. First, an HTTP request is received (S71). It is checked whether or not the content of the HTTP request is for inquiring a list of services (S72). If the content of the HTTP request refers to a list of services (S72: YES), the top service definition information 25 is read from the service definition information storage unit 24 (S73), and the process proceeds to S77.
On the other hand, if the content of the HTTP request does not refer to the service list in S72 (S72: NO), it is checked whether or not the content of the HTTP request is a service inquiry (S74). If the content of the HTTP request refers to a service (S74: YES), the designated service definition information 25 is read from the service definition information storage unit 24 (S75), and the process proceeds to S77.
On the other hand, if the content of the HTTP request does not refer to the service in S74 (S74: NO), error information is set (S76), and the process proceeds to S77.
In S77, the service definition information 25 or the error information is transmitted as an HTTP response to the requesting multifunction machine 10 and the directory server process is terminated.
(2) Processing by MFP 10 Next, various processes executed by the control unit 11 of the MFP 10 will be described.
(2-1) Multifunction Device Processing First, multifunction device processing that is repeatedly executed after the multifunction device 10 is activated will be described with reference to FIG.
When the MFP process is started, first, an initialization process is performed (S102).
After completion of this initialization process, when an external command, for example, an input operation to the operation unit 12 or an input of a command signal via the network 1 occurs (S104), this input changes the operation mode to the service mode. It is checked whether or not the content is to be transferred (S106). Here, if the input in S104 is an operation of pressing the service key 44 of the operation unit 12, it is determined that the content is for shifting to the service mode. The “service mode” is an operation mode for executing a process for requesting the function server 30 to provide a service, as shown in the following process.
If it is determined in S106 that the content is not for shifting to the service mode (S106: NO), processing for other operation modes (processing in other modes) is performed according to the input content (S108), and then S104. Return to.
On the other hand, if it is determined in S106 that the content is for shifting to the service mode (S106: YES), the user is allowed to specify a method for specifying the service to be requested to the function server 30 (S110). Here, the method selection screen shown in FIG. 8 is displayed on the display 52, whether the service is specified from the list (“Select from list” in FIG. 8) or the request destination address is specified by direct input (“ Prompt to select "Direct input"). After this selection screen is displayed, the user can use the operation unit 12 to select which one to specify.
If it is selected in this S110 that designation is made from the list (S110: YES), the directory server 20 is requested to obtain an inquiry of the top service list (S112). Here, as an address for requesting the directory server 20 to transmit the service definition information 25, an HTTP request is transmitted to an address stored in the storage unit 16 in advance, thereby requesting a service list inquiry. The directory server 20 that has been accessed based on this address returns the top service definition information 25 as an HTTP response as described above.
Thus, after requesting the top service list inquiry, when the service definition information 25 returned from the directory server 20 is received (S114), a service selection screen is displayed on the display 52 based on the service definition information 25. After (S116), the process proceeds to the next process (S120). When the process of S116 is performed after receiving the top service definition information 25, as shown in FIG. 10A, according to the top service definition information 25 (XML description) as shown in FIG. The characters “directory service” are arranged at the top of the display area of the display 52 as a display title (Title), and items (Link_Title) representing selectable categories are “data storage service”, “print service”, and “copy application”. The service category selection screen in which the characters “service” are arranged at the bottom of the display area is displayed. In the service category selection screen in this case, the ID of another service definition information 25 corresponding to the category is assigned as a link destination (see “Link_Location” in FIG. 9), and any item is selected. At this time, the service definition information 25 having the ID corresponding to the item is requested from the directory server 20.
In addition, when the process of S116 is performed after receiving the service definition information 25 other than the top, as a specific example, when the service definition information 25 related to the “copy application service” is received, as shown in FIG. In accordance with the service definition information 25 (XML description), as shown in FIGS. 10B and 10C, the characters “Copy Application Service” are arranged at the top of the display area as a title for display (Title) and are selected. Display of the service selection screen in which characters “Linked Title”, “Translation Copy”, “Read Text” and “Speech Text Conversion” which are items (Link_Title) representing possible services are arranged at the bottom of the display area Do. In this embodiment, due to display area restrictions, when all items cannot be displayed at once, the arrangement of each item is configured to move up and down by scrolling the screen. FIG. 10B and FIG. 10C show such a state before and after scrolling. In this case, on the service selection screen, an ID of another service definition information 25 corresponding to the service is assigned as a link destination (see “Link_Location” in FIG. 11), and when any item is selected. In addition, the function server 30 is requested to provide a service having an ID corresponding to the item.
If it is selected in S110 described above that the request destination address is designated by direct input (S110: NO), an address input screen (not shown) for inputting the request destination address is displayed on the display 52. Later (S118), the process proceeds to the next process (S120).
After the service selection screen or the address input screen is displayed in this way, the user selects an item (operation for inputting an address) or ends the service mode (stop operation) using the operation unit 12. )It can be performed.
Next, an input operation to the operation unit 12 by the user is accepted (S120), and it is checked whether or not the input operation thus performed is an operation for selecting a link (S122). Here, a link is selected when an operation for selecting an item on the service selection screen displayed in S116 or an operation for inputting an address on the address input screen displayed in S118 is performed as an input operation. It is determined that the operation.
If it is determined in S122 that the operation is not an operation for selecting a link (S122: NO), if the input operation is a stop operation (S124: YES), the process as the service mode is ended by returning to S104. On the other hand, if the input operation is not a stop operation (S124: NO), a rejection sound (such as a buzzer sound) is sounded (S126), and the process returns to S120.
If it is determined in S122 that the input operation is an operation for selecting a link (S122: YES), the selected link is a link to a service, that is, for requesting the function server 30 to provide a service. It is checked whether or not it is an ID (S128).
If it is determined in S128 that the link is not a link to a service, that is, if it is an ID of another service definition information 25 (S128: NO), a request for a service list is requested to the directory server 20, and the corresponding After the service definition information 25 to be received is received (S130), the process returns to S116 to display a service selection screen on the display 52.
If it is determined in S128 that the link is to the service (S128: YES), the session process (FIG. 12) described later is performed (S132), and then the process returns to S104 as the service mode. Exit.
(2-2) Session Processing Next, a detailed processing procedure of the session processing which is S132 in FIG. 7 will be described with reference to FIGS.
In this session process, first, a service to be used is selected, and a service activation command is activated together with a user ID based on Link_Location (address if the address is directly input) of the service definition information 25 (S202). That is, by transmitting a service activation command to the service address using an HTTP request, the service selected by the user is activated on the function server 30 side. The function server 30 that has received this service activation command returns a session ID as an HTTP response. The user ID referred to here is the user ID stored in the storage unit 16 in the above-described service information storage process (see FIG. 30), and is the user ID corresponding to the service to be started.
Next, the session ID returned from the function server 30 in response to the service activation command in S204 is received (S204). Unless otherwise specified, the HTTP request and the HTTP response transmitted in the subsequent processing are all transmitted in a state in which the session ID is included, and the function server 30 that has received this HTTP request receives this session. Based on the ID, the communication device is managed (known session management).
Next, a “multifunction machine command inquiry” for inquiring whether there is a command to the multifunction machine 10 is transmitted to the function server 30 by an HTTP request (S206). The function server 30 that has received this “multifunction device command inquiry” indicates the content of a command for the multifunction device 10 (a command indicating “no command” if no command is generated). Is returned as an HTTP response.
Next, when a command (multifunction device command) returned by the inquiry in S206 is received (S208), it is determined whether or not the command is a job start command (S210). As will be described later, the “job start command” is a command generated on the function server 30 side after the service start command is transmitted in S202, and the “UI job”, It is a content that instructs activation of either “input job (scan job or voice job)” or “output job (print job or speaker job)”. The job activation command includes the job ID of the job to be activated, the job type (UI job, input job (scan job or voice job), output job (print job or speaker job)), and job communication address. Is added.
If it is determined in S210 that the command is a job activation command (S210: YES), after securing resources necessary for job activation (S212), the job commanded by the job activation command in S252 to S266 described below Start up.
Hereinafter, S252 to S266 will be described with reference to FIG.
Here, first, it is checked whether or not the job commanded by the job start command is a UI job (S252). If it is determined that the job is a UI job (S252: YES), it is added to the job start command. After starting the UI job based on the job ID and the communication destination address (S254), the process proceeds to the next process (S214 in FIG. 12). This UI job is executed in parallel with other processes after being activated in the process of S254, and will be described in detail in a “UI job” (FIG. 14) described later.
If it is determined that the job commanded by the job start command is not a UI job (S252: NO), the commanded job is a type of input job, a scan job (S256: YES) or a voice job (S256: If NO, S262: YES), after starting the input job based on the job ID and the communication destination address added to the job start command (S260), the process proceeds to the next process (S214 in FIG. 12). This input job is executed in parallel with other processes after being activated in the process of S260, and will be described in detail in an “input job” (FIG. 17) described later.
If it is determined that the job commanded by the job start command is not one of the jobs described above (S258: NO), the commanded job is a print job (S262: YES) or speaker job that is a kind of output job. If (S262: NO, S264: YES), after starting the output job based on the job ID and the communication destination address added to the job start command (S266), the process proceeds to the next process (S214 in FIG. 12). To do. This output job is executed in parallel with other processes after being activated in the process of S266. This will be described in detail in an “output job” (FIG. 18) described later.
If it is determined that the job instructed by the job activation command is not any of the above-described jobs (S264: NO), the process proceeds to the next process (S214 in FIG. 12) without starting the job.
Thus, after starting the job, the process returns to FIG. 12, waits for a predetermined interval (S214), and returns to S206.
If it is determined in S210 described above that the command is not a job start command (S210: NO), it is checked whether the command received in S208 is a job end command (S216). As will be described later, the “job end command” is a command issued on the function server 30 side when this job is ended after the job is started in each process in FIG. In addition, the job ID of the completed job is added to this job end command.
If it is determined in S216 that the command is a job end command (S216: YES), the job with the job ID added to the job end command is stopped (end command is passed to the corresponding job), and After releasing the resources secured in S212 before starting the job (S218), the process proceeds to S214.
If it is determined in S216 that the command is not a job end command (S216: NO), it is checked whether or not it indicates “no command” (S220), and “no command” is indicated. (S220: YES), the process proceeds to S214. On the other hand, if it does not indicate “no command” (S220: NO), it is determined whether it is a session end command (S222). This “session end command” is a process that is generated on the function server 30 side when service provision to the multifunction device 10 is ended.
If it is determined in S222 that the command is a session end command (S222: YES), this session processing is ended. On the other hand, if the command received in S208 is not any of the commands described above, the process for notifying an error (command error processing) is performed (S224), and then the session process is terminated. In S224, the error is notified by causing the display 52 to display a message indicating an error.
(2-3) UI Job Next, the UI job processing procedure started in S254 in FIG. 13 will be described with reference to FIG.
When this UI job is started, first, a “service I / F information transmission request” which is a request for the function server 30 to transmit the service I / F information 36 and a URL for specifying the request target are transmitted. Write to a predetermined area as trust data. This transmission data is information used in the processing of S321 described later, and the information written as this data is transmitted to the function server 30 together with the session ID and job ID. The transmission data storage area is provided in a predetermined area of a RAM (not shown) provided in the control unit 11 of the multifunction machine 10 (S301).
Subsequently, it is determined whether or not there is an end instruction (instruction output in S218 of FIG. 12) from the session processing described above (S303).
If it is determined in S303 that there has been an end instruction from the session process (S303: YES), the end of the UI job is notified to the session process (S305), and then the UI job is ended. This session end command is received during the process in S218 of the session process of FIG. In S218, it is determined that the job has been completely stopped by receiving this command, and the subsequent procedure is executed.
On the other hand, if it is determined that there is no termination instruction from the session processing (S303: NO), it is determined whether or not the operation unit 12 is busy (S309). Here, based on the busy flag Fu set so that it stands while each job is activated (“1” is set), if the busy flag Fu is set, it is determined that the busy state is set, and the busy flag Fu is lowered ( If “0” is set, it is determined that the device is not busy.
If it is determined in S309 that it is in a busy state (S309: YES), the operation unit 12 waits until the busy state is canceled, that is, until the busy flag Fu is lowered (S307), and then returns to S309. On the other hand, if it is determined that the state is not busy (S309: NO), the busy flag Fu is set (S311), and it is assumed that the operation unit 12 is busy by this UI job.
Next, the information written in the storage area as transmission data is transmitted to the function server 30 with the session ID and job ID by an HTTP request (S321). Upon receiving this HTTP request, the function server 30 replies with a HTTP response indicating an MFP command indicating the content of the UI job if there is a command. If there is no command for this UI job, a multi-function device command indicating “no command” is returned as an HTTP response.
Next, when a multifunction device command returned by an HTTP response is received (S323), it is determined whether or not the command is a parameter request (S325). This “parameter request” is a request transmitted in the process of S904 in the UI job process (FIG. 23) described later executed by the function server 30, and the service I / F information 36 added to the parameter request Based on this, the user is requested to specify parameters necessary for using the service.
If it is determined in S325 that the request is a parameter (S325: YES), a parameter input screen is displayed on the display 52 of the operation unit 12 based on the service I / F information 36, and an input operation for setting a parameter is performed. To the user (S327).
Here, how the parameter input screen is displayed will be described by exemplifying the service I / F information 36 corresponding to the translation copy service in the service I / F information 36. The translation copy service is based on the image data read by the reading unit 13 in the multifunction machine 10 and the function server 30 converts the text represented by the image data by OCR (Optical Character Recognition) processing. It is a service that prints this image on the recording unit 14 in the multi-function peripheral 10 by generating and providing image data representing an image of content whose text has been translated into a predetermined language.
First, in accordance with the description contents of XML as shown in FIG. 15, as shown in FIG. 16A, the characters “translation copy” are arranged at the upper part of the display area as the title for display (Title), and the input items below that are displayed. (Disp_Name) is arranged with the characters “language selection”, and further below that, items (Disp_Select) representing parameters that can be selected for the input item “language selection” are “English → Japanese” and “Japanese → English”. Display the parameter input screen with the characters. Here, input items (Disp_Name) related to “translation copy” include “scanner setting”, “print setting”, and “comment” in addition to the “language selection” displayed above. Only the input items for "Language selection" are displayed. This is simply due to the limitation of the size of the display 52, and the operation unit 12 is operated from this state (left and right direction keys 48 and 49), as shown in FIGS. 16 (b) to 16 (e). As described above, the input items displayed in the lower part of the display area can be switched among four types including “scanner setting”, “print setting”, and “comment”.
The parameters that can be selected for these input items will be described. As items (Disp_Select) representing the parameters that can be selected for “scanner settings”, “normal characters” and “fine characters” are displayed. (See FIG. 16B). Here, “ordinary characters” means that the resolution (reading resolution) that is a parameter of the reading unit 13 is set to 300 × 300 dpi, and “fine characters” sets the resolution to 600 × 600 dpi. Means that.
In addition, as items (Disp_Select) representing parameters that can be selected for “print setting”, characters of “print speed priority”, “normal”, and “high definition” are displayed. Note that due to the size limitation of the display 52, “high definition” is not initially displayed (see FIG. 16C), but is displayed by scrolling the screen (see FIG. 16D). ). “Print speed priority” here means that the resolution (print resolution) that is a parameter of the recording unit 14 is set to 200 × 200 dpi, and “normal” means that the resolution is set to 300 × 300 dpi. “High definition” means that the resolution is set to 600 × 600 dpi.
For “comment”, a comment input field is displayed below the character “comment”, and a set character string (Default_String) is input (see FIG. 16E). In this way, the character string input in the input field as a comment is used in the form of being described in the header or footer of the print image, for example.
After the parameter input screen is displayed in this way, when the user specifies parameters for each input item, inputs a character string in the input field, and confirms the specified content, these The input information (parameter) is written in the storage area as transmission data (S329). Then, the busy flag Fu is lowered (S319), and the process returns to S303.
Next, if it is determined that the MFP command received in S323 is not a parameter request (S325: NO), whether the MFP command received in S323 is a service status information display command or not. Is determined (S331). The “service status information display command” referred to here is a command transmitted on the function server 30 side (command transmitted in S926 in FIG. 23), and processing related to the service is executed without any problem in the function server 30. Or a command for notifying that there is a problem and the service is stopped.
If it is determined in S331 that the command is a service status information display command (S331: YES), the display based on the service status information is displayed on the display 52 (S333), and the service running on the function server 30 is activated. A “service status information request” requesting new information on the status is written in the storage area as transmission data (S335). Then, the busy flag Fu is lowered (S319), and the process returns to S303.
If it is determined in S331 that the command is not a service status information display command (S331: NO), it is checked whether the MFP command received in S323 is a status information request (S337). This “status information request” is a command for requesting information transmission regarding the status of the multifunction machine 10.
If it is determined in S337 that the request is a status information request (S337: YES), the storage area is written using information related to the status of the multifunction machine 10 (for example, information indicating no paper, cover open, etc.) as transmission data (S339). ). Then, the busy flag Fu is lowered (S319), and the process returns to S303.
If it is determined in S337 that the request is not a status information request (S337: NO), it is checked whether or not the MFP command received in S323 is a command indicating the server reception status (S341). The “server reception status” is a command transmitted to notify whether or not the function server 30 has successfully received information from the multifunction machine 10.
If it is determined in S341 that the server reception status is present (S341: YES), if the content of the server reception status indicates abnormal reception (NG) (S343: YES), the server reception status is transmitted. The triggered information is written in the storage area as transmission data (S346). Then, the busy flag Fu is lowered (S319), and the process returns to S303. On the other hand, if it does not indicate an abnormal receipt (NG) (S343: NO), the above-mentioned “service status information request” is written in the storage area as transmission data (S345), the busy flag Fu is lowered (S319), and the process proceeds to S303. Return processing.
On the other hand, if it is determined in S341 that the MFP command received in S323 is not “server receipt status” (S341: NO), it is checked whether or not the MFP command received in S323 indicates “no command”. If it indicates “no command” (S338: YES), “command for multi-function device job command”, which is a command inquiry to the multi-function device 10, is written in the storage area as transmission data (S349). ), The busy flag Fu is lowered (S319), and the process returns to S303. On the other hand, if “no command” is not indicated (S338: NO), error processing is performed (S347), the busy flag Fu is lowered (S319), and the process returns to S303. The specific contents of the error processing are writing information indicating that an error has occurred in the storage area as transmission data, displaying the error occurrence on the display 52, and the like.
(2-4) Input Job Next, the processing procedure of the input job activated in S260 in FIG. 13 will be described based on FIG. This input job is a process that operates in parallel with the above-described session process and UI job.
When this input job is started, it is first determined whether or not the input device is busy (S402). Here, based on the busy flag Fi set to stand when the input device is busy ("1" is set), if the busy flag Fi is set, it is determined to be busy, and the busy flag Fi is set. If it is down (“0” is set), it is determined that it is not busy. Here, the “input device” is the reading unit 13 when receiving a service related to the image data generated by the reading unit 13, and sound data representing sound output from the sound input unit 17. It is the sound input unit 17 if the service is received.
If it is determined in S402 that the input device is busy (S402: YES), the process waits until the input device is released from the busy state (S404), and then returns to the process of S402. Is determined not to be busy (S402: NO), the busy flag Fi is set (S406).
Next, the MFP status information, which is information related to the status of the MFP 10, is transmitted to the function server 30 by the HTTP request together with the job ID passed in S260 in the session process (S408). The function server 30 that has received this multifunction device status information returns a multifunction device parameter, which is information based on the parameter transmitted to the function server 30 in S321 in FIG. 14, as an HTTP response, as will be described later. .
Next, when a multifunction machine parameter is returned in response to the multifunction machine status information transmitted in S408 (S410), it is determined whether or not an end instruction is passed from the session process (whether there is an end instruction from the session). (S412). This end instruction is an instruction passed from the session process to the input job when the job to be ended in S218 in FIG. 12 is an input job.
If it is determined in S412 that an end instruction has not been passed from the session process (S412: NO), the MFP parameters returned in S410 cannot be normally received (S414: NO). The MFP reception status for notifying that the information from the function server 30 cannot be received normally (abnormal reception (NG)), together with the job ID passed in S260 in the session processing, is displayed in HTTP. The request is transmitted to the function server 30 (S416). As will be described later, the function server 30 that has received the MFP reception status returns the MFP parameter as an HTTP response again, and returns to S410 after S416.
On the other hand, if the MFP parameters can be normally received in S410 (S414: YES), the fact that the information from the function server 30 has been normally received (notice that it is normal reception (OK)) is notified. The MFP reception status is transmitted to the function server 30 by the HTTP request together with the job ID passed in S260 in the session processing (S418). The function server 30 that has received the reception status of the multifunction peripheral returns an input data request for requesting transmission of data to be processed on the function server 30 side, as will be described later.
Next, when an input data request is returned from the function server 30 that has received the MFP reception status (S420), it is determined whether or not an end instruction has been passed from the session process (S422), as in S412.
If it is determined in S422 that an end instruction has not been passed from the session process (S422: NO), the input data request returned in S420 cannot be normally received (S424: NO). In the same manner as in S416, the MFP receiving status for notifying that it is abnormal receiving (NG) is transmitted to the function server 30 (S426). As will be described later, the function server 30 that has received this multifunction device receipt status returns an input data request again, and returns to S420 after S426.
On the other hand, if the input data request returned in S420 can be normally received (S424: YES), the input data to be processed on the function server 30 side is combined with the job ID passed in S260 in the session processing. Then, the HTTP request is transmitted to the function server 30 (S428). Here, first, after changing the setting value of the input device to the parameter indicated by the MFP parameter received in S410, a data input screen for prompting input of data to be processed on the function server 30 side is displayed on the display 52. The display prompts the user to perform an operation for inputting data to the multifunction machine 10. Thereafter, the data (input data) acquired by the user performing an operation for inputting data is transmitted to the function server 30 by the HTTP request together with the job ID passed in S260 in the session processing. As a specific example, for example, a message such as “Please set the manuscript and press the OK key”, “Please pick up the handset and input the voice” is displayed on the display 52, and then the reading unit 13 Alternatively, data acquired by the sound input unit 17 is sequentially transmitted to the function server 30. It can be considered that the function server 30 that has received the input data returns service status information for notifying whether or not the data processing based on the input data has been normally completed.
The data acquisition method in this process may be a method of reading from a memory card set in a memory card slot (not shown) or reading from a specific storage area in the storage unit 16, in which case A message for designating a storage area from which data is acquired may be displayed on the display 52.
Thus, after the input data is transmitted to the function server 30, the setting value of the input device changed in the process of S428 is restored (S430), and then the service status information returned from the function server 30 is received (S432). ).
Then, after receiving the service information in S432, or when it is determined in S412 and S422 that an end instruction has been passed from the session process (S412: YES, S422: YES), the service information is set in S406. After the busy flag Fi is lowered (S434), the end of the input job is notified to the session processing together with the job ID passed in S260 in the session processing (S436), and this input job is ended. This notification of the end of the input job is received during the process in S218 of the session process of FIG. In S218, it is determined that the job has been completely stopped by receiving this command, and the subsequent processing procedure is executed.
(2-5) Output Job Next, the processing procedure of the output job activated in S266 in FIG. 13 will be described with reference to FIG. This input job is a process that operates in parallel with the above-described session process and UI job.
When this output job is started, it is first determined whether or not the output device is busy (S502). Here, based on the busy flag Fo set to stand when the output device is busy ("1" is set), it is determined that the busy flag Fo is set when the busy flag Fo is set. If it is down (“0” is set), it is determined that it is not busy. Note that the “output device” here is the recording unit 14 in the case of receiving a service related to image data to be printed by the recording unit 14, and relates to sound data representing sound output by the sound output unit 18. If the service is provided, the sound output unit 18 is used.
If it is determined in S502 that the output device is busy (S502: YES), after waiting for the output device to be released (S504), the process returns to S502, while the output device Is determined not to be busy (S502: NO), the busy flag Fo is set (S506).
Next, the MFP status information, which is information related to the status of the MFP 10, is transmitted to the function server 30 by the HTTP request together with the job ID passed in S266 in the session processing (S508). The function server 30 that has received this multifunction device status information returns a multifunction device parameter, which is information based on the parameter transmitted to the function server 30 in S321 in FIG. 14, as an HTTP response, as will be described later. .
Next, when the MFP parameter is returned to the MFP state information transmitted in S508 (S510), it is determined whether or not an end instruction is passed from the session processing (whether there is an end instruction from the session). (S512). This end instruction is an instruction that is passed from the session process to this output job when the job to be ended in S218 in FIG. 12 is an output job.
If it is determined in S512 that an end instruction has not been passed from the session process (S512: NO), the MFP parameters returned in S510 cannot be normally received (S514: NO). The MFP reception status for notifying that information from the function server 30 cannot be received normally (abnormal reception (NG)) is displayed together with the job ID passed in S266 in the session processing. The request is transmitted to the function server 30 (S516). The function server 30 that has received this multi-function peripheral reception status returns the multi-function peripheral parameters again as will be described later, and returns to S510 after S516.
On the other hand, if the MFP parameters can be normally received in S510 (S514: YES), the fact that the information from the function server 30 has been normally received (notice that it is normal reception (OK)) is notified. The MFP reception status is transmitted to the function server 30 by the HTTP request together with the job ID passed in S266 in the session processing (S518). The function server 30 that has received the reception status of the multi-function device returns data (output data) processed based on the input data transmitted in S428 in FIG. 17, as will be described later.
Next, when output data is returned from the function server 30 that has received the MFP reception status (S520), it is determined whether or not an end instruction has been passed from the session processing (S522), as in S512.
If it is determined in S522 that an end instruction has not been passed from the session process (S522: NO), if the output data returned in S520 has not been received normally (S524: NO), Similar to S516, the MFP reception status for notifying that it is abnormal reception (NG) is transmitted to the function server 30 (S526). The function server 30 that has received the reception status of the multi-function peripheral returns the output data again as will be described later, and returns to S520 after S526.
On the other hand, if the output data returned in S520 can be normally received (S524: YES), this output data is output by the output device (S528). Here, first, after changing the setting value of the output device to the parameter indicated by the MFP parameter received in S510, output data is output by this output device (for example, printing of an image represented by the image data, sound data) The voice represented by
In this way, after the output of the output data by the output device is finished, the setting value of the output device changed in S528 is restored (S530), and the MFP status information, which is information related to the status of the MFP 10, is obtained in the session process. Along with the job ID passed in S266, the HTTP request is transmitted to the function server 30 (S532). The function server 30 that has received the MFP status information returns service status information as will be described later.
Then, after receiving the service status information returned from the function server 30 (S534), or when it is determined in S512 and S522 that an end instruction has been passed from the session processing (S512: YES, S522: (YES) After the busy flag Fo set in S406 is lowered (S536), the end of the input job is notified to the session processing together with the job ID passed in S266 in the session processing (S538), and this input job is completed. To do. This notification of the end of the input job is received during the process in S218 of the session process of FIG. In S218, it is determined that the job has been completely stopped by receiving this command, and the subsequent procedure is executed.
(3) Processing by Function Server 30 Next, various processes executed by the control unit 31 of the function server 30 will be described.
(3-1) Function Server Process Next, a function server process performed every time an HTTP request is received will be described with reference to FIGS. 19 and 20.
When this function server process is activated, it is first checked whether or not the received HTTP request is a service activation instruction (S702). This “service activation instruction” is transmitted by the multifunction machine 10 in S202 of FIG.
If it is determined in S702 that it is a service activation command (S702: YES), it is checked whether or not the user ID sent from the multi-function device 10 is a user ID that can use the service (S702). S704). When it is not a user ID that can use the service (S704: NO), after generating information for error notification (error notification information) (S706), the process proceeds to the next process (S734). On the other hand, if the user ID is a user ID that can use the service (S704: YES), a session ID is generated, transmission data indicating the session ID is generated, and resources for executing the service are secured. After starting the process to be performed (S708), the process proceeds to the next process (S734). The process activated here is session processing (FIG. 21) described later.
If it is determined in S702 that the command is not a service activation command (S702: NO), it is checked whether the HTTP request is a service termination command (S710).
If it is determined in S710 that it is a service end command (S710: YES), the session ID and the resources secured in S708 are released, and transmission data indicating service end is created (S712). The process proceeds to the next process (S734 in FIG. 20). On the other hand, if it is determined that it is not a service end command (S710: NO), whether or not information on the service (session or job) is included, specifically, the MFP 10 performs session processing or job (UI). It is checked whether the request is an HTTP request transmitted in (job, input job, output job) (S714).
If it is determined in S714 that information about the service is included (S714: YES), the process (session process, UI job, input job, or output job) that has transmitted the HTTP request is selected. Specify (S716).
If the process cannot be specified in S716 (S718: YES), information (error notification information) for notifying an error is generated (S720), and the process proceeds to the next process (S734).
On the other hand, if the process can be specified in S716 (S718: NO), the information transmitted by the HTTP request is passed to the specified process (S722).
Thus, after S722 is completed or when it is determined in S714 that information related to the service is not included (S714: NO), the storage area of the information corresponding to the session ID or job ID is specified (S724). .
If the storage area cannot be specified in S724 (S726: YES), the process proceeds to S720, error notification information is generated, and the process proceeds to the next process (S734). On the other hand, if the storage area can be specified (S726: NO), it is checked whether or not there is information to be returned to the multifunction machine 10 in this storage area (S728).
If it is determined in S728 that there is no information to be returned (S728: NO), “no command” information is generated (S730), and the process proceeds to the next process (S734). On the other hand, if it is determined that there is information to be transmitted (S728: YES), the MFP control command is generated based on the return information (S732), and the process proceeds to the next process (S734).
Thus, S706, S708, S712, S720. The information generated in S730 and S732 is returned to the multi-function device 10 as an HTTP response (S734). Of the HTTP response returned here, the transmission data generated in S708 is received by the multi-function device 10 in S204 in FIG. Further, the transmission data representing the end of service generated in S712 is received by the multi-function device 10 in S208 in FIG. 12, and determined as YES in S222. The error notification information generated in S720 is received by the multi-function device 10 in S208 in FIG. 12, is determined NO in S222, and the process of S224 is performed. Further, the “no command” information generated in S730 is received by the multi-function device 10 in S208 in FIG. 12, and YES is determined in S220. The MFP control command generated in S732 has a different content for each job to be described later, and is received in the corresponding job on the MFP 10 side.
If the service control information processing (S714 to S732) has been performed (S736: YES), after setting “transmitted” to the memory address corresponding to the session ID or job ID (S738), this function server The process ends. On the other hand, if the service control information processing is not performed (S736: NO), the function server process is terminated without setting the memory address.
(3-2) Session Process Next, a session process procedure executed in parallel with the function server process will be described with reference to FIGS. In the present embodiment, session processing for a translation copy service will be described as an example.
When this session processing is started, first, initialization processing is performed (S802).
Next, a service-side UI job is activated (S804). This UI job is a process executed in parallel with the session process, and a detailed processing procedure will be described later.
Next, a UI job start command is output as a multifunction device command (S806). Here, a process of writing a UI job start command together with a job ID and a communication destination address in a storage area for storing reply information is performed. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as an activation command to the multifunction device 10 side in S734 in FIG. This activation command is received on the multifunction device 10 side in S208 in FIG. 12, and based on this, a UI job is activated on the multifunction device 10 side (S254 in FIG. 13).
Next, it is checked whether or not the input of parameters from the multifunction device 10 side has been completed (S808). As described later, the UI job activated in S804 described above is configured to acquire a parameter from the multi-function peripheral 10 and notify the session processing to that effect. For this reason, in S808, when a parameter acquisition notification is made from this UI job, it is determined that the input of parameters from the MFP 10 side is completed.
If it is determined in S808 that the parameter input has not been completed (S808: NO), it is checked whether the UI job has been stopped (S810). In the UI job activated in S804 described above, if the parameter acquisition from the MFP 10 side is not performed normally, as described later, the UI job itself is stopped (terminated) and a message to that effect is displayed. It is configured to notify the session processing. For this reason, in S810, it is determined that the UI job has been stopped when the stop notification is made from this UI job.
If it is determined in S810 that the UI job is not stopped (S810: NO), the process returns to S808. On the other hand, if it is determined that the UI job is stopped (S810: YES), the process proceeds to S848 described later. To do.
If it is determined in S808 that parameter input has been completed (S808: YES), a scan job, which is a type of service-side input job, is activated (S812). This scan job is a process executed in parallel with the session process, and a detailed processing procedure will be described later.
Next, a scan (input) job start command is output as a multifunction device command (S814). Here, a process of writing a scan job start command together with a job ID and a communication destination address in a storage area for storing reply information is performed. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as an activation command to the multifunction device 10 side in S734 in FIG. The activation command is received by the multifunction device 10 in S208 in FIG. 12, and based on this, the input job is activated on the multifunction device 10 side.
Next, it is checked whether preparation of the scanner (reading unit 13) is completed on the multifunction machine 10 side (S816). As described later, the scan job activated in S812 described above is configured to receive notification that the preparation of the scanner has been completed on the multifunction device 10 side, and notify this session processing to that effect. Yes. For this reason, in S816, when the notification that the scanner preparation is completed from this scan job is made, it is determined that the scanner preparation is completed on the multifunction peripheral 10 side.
If it is determined in S816 that the scanner has not been prepared on the multifunction device 10 side (S816: NO), it is checked whether the scan job is stopped (S818). In the scan job activated in S812 described above, the scan job itself is stopped (terminated) when the notification that the preparation of the scanner has been completed is not normally received from the multifunction peripheral 10, as will be described later. At the same time, it is configured to notify the session processing to that effect. Therefore, in S818, it is determined that the scan job has been stopped when a stop notification is made from this scan job.
If it is determined in S818 that the scan job is not stopped (S818: NO), the process returns to S816, while if it is determined that the scan job is stopped (S818: YES), the process proceeds to S844 described later. To do.
If it is determined in S816 that the scanner is ready (S816: YES), a print job, which is a type of service-side output job, is activated (S820). This print job is a process executed in parallel with the session process, and a detailed processing procedure will be described later.
Next, a print (output) job start command is output as a multi-function device command (S822). Here, a process of writing a print job start command together with a job ID and a communication destination address in a storage area for storing reply information is performed. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as an activation command to the multifunction device 10 side in S734 in FIG. This activation command is received on the multifunction device 10 side in S208 in FIG. 12, and based on this, an output job is activated on the multifunction device 10 side (S266 in FIG. 13).
Next, it is checked whether preparation for printing (recording unit 14) is completed on the multifunction peripheral 10 side (S824). As described later, the print job activated in S820 described above is configured to receive notification that the preparation for printing has been completed on the multifunction device 10 side, and notify the session processing to that effect. . Therefore, in S824, when notification that the print preparation from the print job is completed is made, it is determined that the print preparation is completed on the multifunction peripheral 10 side.
If it is determined in S824 that the preparation for printing has not been completed on the MFP 10 side (S824: NO), it is checked whether the print job has been stopped (S826). In the print job activated in S820 described above, the print job itself is stopped (terminated) when the notification that the preparation for printing has been completed is not normally received from the multifunction peripheral 10, as will be described later. This is configured to notify the session processing to that effect. For this reason, in S826, it is determined that the print job has been stopped when a stop notification is made from this print job.
If it is determined in S826 that the print job is not stopped (S826: NO), the process returns to S824, whereas if it is determined that the print job is stopped (S826: YES), the process proceeds to S840 described later. To do.
If it is determined in S824 that the print preparation is completed (S824: YES), the input data acquired from the multifunction machine 10 side is read (S828). Since the scan job activated in S812 described above is configured to acquire image data read by the reading unit 13 of the multi-function device 10 from the multi-function device 10 as will be described later, this S828. Then, a data area corresponding to one page is read out from the data (input data) acquired in this way and stored in a predetermined storage area.
Next, image data is generated by performing processing such as OCR, translation, and print layout on the input data read in S828 (S830). Here, first, an OCR process is performed on the input data read in S828 to recognize a text portion included in the image represented by the input data. Next, a translation process is performed on the text part to convert the text part into text expressed in a predetermined language. Note that the translation processing here is performed based on the parameter acquired in the UI job activated in S804 described above, and conversion into the language indicated by this parameter is performed. Then, for the text portion recognized in this way, image data for printing in which a predetermined print layout is set is generated.
Next, the image data generated in S830 is output (S832). Here, a process of writing the image data generated in S830 together with the job ID and the communication destination address to the storage area for storing the return information is performed. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as output data to the multifunction device 10 side in S734 in FIG. The output data is received by the multi-function device 10 in S520 in FIG. 18, and based on this, the image recording unit 14 records the image indicated by the output data.
Next, in S828, it is checked whether or not reading of all input data (data area for all pages) is completed (S834). If not completed (S834: NO), the process returns to S828, If completed (S834: YES), it is checked whether or not output of output data (writing to the storage area) in S832 has been completed (S836).
If the output of the output data is not completed in S836 (S836: NO), the process returns to S828. On the other hand, if the output of the output data is completed (S836: YES), a print (output) job end command is issued. It is output as a multifunction machine command (S838). Here, a process of writing a print job end instruction together with the job ID in a storage area for storing reply information is performed. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as an end command to the multifunction device 10 side in S734 in FIG. This termination command is received by the multifunction device 10 in S208 in FIG. 12, and based on this, the output job is stopped (terminated) on the multifunction device 10 side (S218 in FIG. 12).
Thus, after outputting the print job end command or when it is determined that the print job is stopped in S826 described above (S826: YES), the service-side print job started in S820 is ended (S840).
Next, a scan (input) job end command is output as a multifunction device command (S842). Here, a process of writing a scan job end instruction together with the job ID in a storage area for storing return information is performed. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as an end command to the multifunction device 10 side in S734 in FIG. This termination command is received by the multifunction device 10 in S208 in FIG. 12, and based on this, the input job is stopped (terminated) on the multifunction device 10 side (S218 in FIG. 12).
In this way, after outputting the scan job end command or when it is determined that the scan job is stopped in S818 described above (S818: YES), the service side scan job started in S812 is ended (S844).
Next, a UI job end command is output as a multifunction device command (S846). Here, a process of writing a scan job end instruction together with the job ID in a storage area for storing return information is performed. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as an end command to the multifunction device 10 side in S734 in FIG. This termination command is received by the multifunction device 10 in S208 in FIG. 12, and based on this, the UI job is stopped (terminated) on the multifunction device 10 side (S218 in FIG. 12).
Then, after performing a termination process such as releasing resources reserved in each job (S850), the session process is terminated. In S852, a process of writing a service end instruction in a storage area for storing reply information is performed. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as an end command to the multifunction device 10 side in S734 in FIG. This termination command is received on the multifunction device 10 side in S208 in FIG. 12, and based on this, the session processing is terminated on the multifunction device 10 side (S222 in FIG. 12).
(3-3) UI Job Next, a UI job processing procedure started in step S804 in FIG. 21 will be described with reference to FIG.
When this UI job is started, first, it waits until a multifunction device job command inquiry is received from the multifunction device 10 by an HTTP request. When this multifunction device job command inquiry is received (S902), it is necessary to execute the service. A parameter request command for requesting the setting of various parameters is returned to the multifunction device 10 as a multifunction device command (S904). The MFP command transmitted in S904 is an HTTP response received by the MFP 10 in S323 in FIG. 14, and the service I / F information 36 (for example, corresponding to the translation copy service) is stored. It is added. The multi-function device 10 that has received this multi-function device command sends an HTTP request with parameters in S321 of FIG.
Next, the error count is initialized (S906). Here, as will be described later, a counter for counting the number of times that the parameter itself has not been received normally has occurred is reset ("0" is set).
Next, it waits until a parameter is transmitted from the multifunction device 10 that has received the multifunction device command transmitted in S904. When the parameter is received (S908), it is checked whether or not this parameter has been received normally. (S910).
If it is determined in S910 that the parameters cannot be received normally (S910: NO), such a situation that the parameters cannot be received normally occurs continuously a predetermined number of times (twice in the present embodiment). Is checked based on the count value of the error count (S912), and if it does not occur continuously for a predetermined number of times (S912: NO), the fact that the parameter could not be received normally (server received NG) ; Server reception status for notifying abnormal reception) is output (S914), the error count is counted up (S916), and the process returns to S908. In S914, processing for writing the server reception status in a storage area for storing reply information is performed. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as a server reception status to the multifunction device 10 side in S734 in FIG. The server reception status is received by the multi-function device 10 in S323 in FIG. 14, and based on this, parameters are retransmitted on the multi-function device 10 side (S341, S343, etc. in FIG. 14).
In S912, if a situation where normal reception is not possible occurs continuously for a predetermined number of times (S912: YES), the UI job is stopped (terminated) is notified to the session processing (S918), and then this UI job Exit. The notification in S918 is received by the session process in S810 in FIG.
If it is determined in S910 that the parameter has been received normally (S910: YES), the server for notifying that the parameter has been received normally (server receipt OK; normal receipt) The reception status is output (S920). Here, a process of writing the server reception status in a storage area for storing reply information is performed. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as a server reception status to the multifunction device 10 side in S734 in FIG. This server reception status is received by the multi-function device 10 in S323 in FIG. 14, and based on this, it is confirmed that there is no need to retransmit parameters on the multi-function device 10 side (S341, S343 in FIG. 14). .
Next, it notifies the session processing that parameter input is complete (parameter acquisition) (S922). This notification is received by the session processing in S808 in FIG.
Then, after the completion of S922, the process waits until a service status information request is received from the multifunction machine 10, and when this service status information request is received (S924), the service status information is output (S926). This process is repeated until the UI job is stopped (terminated) by another process (for example, S844 in FIG. 22). In S926, a process for writing the service status information in a storage area for storing reply information is performed. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as service status information to the multifunction device 10 side in S734 in FIG.
(3-4) Scan Job Next, the processing procedure of the scan job activated in S812 in FIG. 21 will be described with reference to FIG.
When this scan job is started, first, it waits until it receives MFP status information from the MFP 10, and when this MFP status information is received (S1002), it initializes an error count in the same manner as S906 in FIG. After that, the MFP parameters are output (S1006). The MFP status information received in S1002 is an HTTP request transmitted from the MFP 10 in S408 in FIG. 17, and in response to this, MFP parameters are returned as an HTTP response in S1006. . The MFP parameter is a parameter corresponding to the MFP 10 that is received in S908 in FIG. 23 and that is the transmission source of the MFP status information received in S1002.
The multi-function peripheral 10 receiving the multi-function peripheral parameters transmits a multi-function peripheral reception status indicating whether or not the multi-function peripheral parameters have been normally received. In step S1008, it is checked whether the message can be normally received. Specifically, if the content of the MFP reception indicates that it is abnormal reception (NG), it is determined that it has not been received normally, and if the content indicates normal reception (OK), it is normal. It is determined that it can be received.
If it is determined in S1008 that the MFP 10 has not received the MFP parameters normally (S1008: NO), such a situation where the MFP 10 cannot receive normally is determined a predetermined number of times (in the present embodiment). (2 times) Check whether or not it has occurred continuously based on the count value by error count (S1010), and if it has not occurred continuously for a predetermined number of times (S1010: NO), count up the error count After (S1012), the process returns to S1006.
In S1010, if a situation in which reception cannot be performed normally has occurred continuously for a predetermined number of times (S1010: YES), the stop (end) of the scan job is notified to the session processing (S1014), and then abnormal termination is performed. A notification command for notification is output as service status information (S1016). This notification in S1014 is received by the session process in S818 in FIG. In S1016, a notification command is written in a storage area for storing reply information. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as a notification command to the multifunction device 10 side in S734 in FIG. This notification command is received on the multifunction device 10 side in S432 in FIG.
If it is determined in S1008 that the multifunction device parameter can be normally received on the multifunction device 10 side (S1008: YES), the multifunction device 10 receives the scanner (reading unit) upon reception of the multifunction device parameter. It is assumed that the preparation of 13) has been completed, and the scanner preparation is notified to the session processing (S1018). This notification is received by the session processing in S816 in FIG.
Next, an input data request for requesting transmission of data to be processed on the function server 30 side is output. Here, a process of writing the input data request in the storage area for storing the return information is performed (S1020). Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as an input data request to the multifunction device 10 side in S734 in FIG. This input data request is received on the multi-function peripheral 10 side in S420 in FIG. 17, whereby input data is transmitted in response to a user operation.
In this way, when input data is received from the MFP 10 that has received the input data request (S1022), if reception of this input data has been completed normally (S1024: YES), a notification command for notifying normal termination is issued. After output as service status information (S1026), the scan job is terminated. In S1026, a process for writing a notification command in a storage area for storing reply information is performed. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as a notification command to the multifunction device 10 side in S734 in FIG. This notification command is received on the multifunction device 10 side in S432 in FIG.
On the other hand, if reception of input data does not end normally (S1024: NO), the process proceeds to S1016, and a notification command for notifying abnormal end is output as service state information, and then this scan job is ended. This notification command is received on the multifunction device 10 side in S432 in FIG.
(3-5) Print Job Next, the processing procedure of the print job activated in S820 in FIG. 21 will be described with reference to FIG.
When this print job is started, first, it waits until it receives multifunction device status information from the multifunction device 10, and when this multifunction device status information is received (S1102), it initializes an error count in the same manner as S906 in FIG. After that, the MFP parameters are output (S1106). The MFP status information received in S1102 is an HTTP request transmitted from the MFP 10 in S508 in FIG. 18. In response to this, the MFP parameters are returned as an HTTP response in S1106. . The MFP parameter is a parameter corresponding to the MFP 10 that is received in S908 in FIG. 23 and that is the transmission source of the MFP status information received in S1102.
Since the multifunction device 10 that has received the multifunction device parameter transmits a multifunction device reception status indicating whether or not the multifunction device parameter has been normally received, this multifunction device reception status is similar to S1008 in FIG. Based on the above, it is checked whether or not the MFP 10 has received the message normally (S1108).
If it is determined in S1108 that the MFP 10 cannot normally receive the MFP parameters (S1108: NO), such a situation in which the MFP 10 cannot be normally received is determined a predetermined number of times (in the present embodiment). (2 times) It is checked whether or not it is continuously generated based on the count value by the error count (S1110), and if it does not occur continuously for a predetermined number of times (S1110: NO), the error count is counted up. After (S1112), the process returns to S1106.
In S1110, if a situation in which reception cannot be performed normally has occurred continuously for a predetermined number of times (S1110: YES), the stop (end) of the print job is notified to the session processing (S1114), and then abnormal termination is performed. A notification command for notification is output as service status information (S1116). The notification in S1114 is received by the session process in S826 in FIG. In S1116, a notification command is written in a storage area for storing reply information. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as a notification command to the multifunction device 10 side in S734 in FIG. This notification command is received on the multifunction machine 10 side in S510 in FIG.
If it is determined in S1108 that the MFP 10 has successfully received the MFP parameters (S1108: YES), printing (recording unit) is performed on the MFP 10 upon receipt of the MFP parameters. It is assumed that the preparation of 14) has been completed, and the print processing completion is notified to the session process. This notification is received by the session processing in S824 in FIG. In session processing, in response to this notification, S828 to S836 in FIG. 22 are performed, and print data is transmitted.
Next, a process of converting the print data generated in the session process (S832 in FIG. 22) into print data that can be processed by the multi-function peripheral 10 and writing it in a storage area for storing transmission information is performed (S1120). Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as a notification command to the multifunction device 10 side in S734 in FIG. This notification command is received on the multi-function peripheral 10 side in S520 in FIG.
In this way, the MFP 10 that has received the print data to be transmitted transmits the MFP status information as an HTTP request in S532 in FIG.
In this way, when the MFP status information is received from the MFP 10 that has received the print data (S1122), if the reception of the MFP status information has ended normally (S1124: YES), a notification of normal end is sent. After the notification command is output as service status information (S1126), the print job is terminated. In S1126, a process for writing a notification command in a storage area for storing reply information is performed. Based on this, a multifunction device control command is generated in S732 in FIG. 19, and is transmitted as a notification command to the multifunction device 10 side in S734 in FIG. This notification command is received on the multi-function peripheral 10 side in S534 in FIG.
On the other hand, if the reception of the MFP status information does not end normally (S1124: NO), the process proceeds to S1116, and a notification command for notifying abnormal end is output as service status information, and then this print job is ended. . This notification command is received on the multi-function peripheral 10 side in S534 in FIG.
In the service providing system of the embodiment configured as described above, the multifunction device 10 realizes the function by receiving the service provided by the function server 30. Prior to this, the multifunction device 10 provides the service. Pre-use processing necessary for receiving is performed. At this time, the user can perform user registration using the PC 60 having a user interface superior to that of the multifunction machine 10 (S153 in FIG. 26). Registration of service information in the multifunction machine 10 is also performed by a series of operations (S155 in FIG. 26). Therefore, according to the service providing system, it is possible to reduce the registration error of the user and the difficulty of operation at the time of registration.
Further, when registering service information in the multifunction device 10, an HTML file (HTML2) including the service information as a hidden item of the <form> tag is sent from the function server 30 to the PC 60 (S154 in FIG. 26). When the submit button is pressed by the user, the service information is transferred to the multifunction machine 10 (S155 in FIG. 26). This eliminates the need for the user to re-enter the service information and transmit it to the multifunction device 10, and allows the user to register the service information in the multifunction device 10 without trouble.
For example, in the above-described embodiment, the configuration applied to the multifunction device 10 is exemplified as the peripheral device in the present invention. However, if the peripheral device can receive a service provided by the function server 30 and can realize the function, the multifunction device For example, the present invention can be applied to a printer device, a scanner device, a facsimile device, and the like.
In addition, although the configuration in which the PC 60 is applied is illustrated as the terminal device in the present invention, any device may be used as long as the device has a richer user interface than the peripheral device. For example, a mobile phone or a PDA may be used.
Further, in the service providing system of the above embodiment, the configuration including one each of the multifunction machine 10, the directory server 20, the function server 30, and the PC 60 is illustrated. However, such a configuration only facilitates the description. However, the service providing system can take various configurations other than this. For example, in the service providing system to which the present invention is applied, a plurality of multifunction peripherals 10 may be provided. Specifically, a plurality of MFPs 10 can receive service definition information 25 from a common directory server 20 and request a service from the common function server 30.
Further, the directory server 20 or a part of the directory server 20 and the part of the function server 30 or the function server 30 may be configured as a single device.
Further, the directory server 20 (or a part of the directory server 20) and the function server 30 (or a part of the function server 30) may be provided in the multi-function device 10 constituting the service providing system. Good.
In the service providing system of the above embodiment, the user inputs the address of the multifunction device 10 at the time of user registration in pre-use processing necessary for the multifunction device 10 to receive the service. This address is transmitted to the function server 30. However, if the function server 30 does not need the address information of the multifunction device 10, it may be stored in the multifunction device 10 without sending the address information to the function server 30. When an HTML file including service information is sent from the function server 30, the destination of the service definition information is corrected by modifying the HTML file using, for example, a JAVA script or JAVA applet sent together. An address corresponding to HTML2 (see FIG. 32) in which the address is set may be automatically generated. Further, the address of the MFP 10 may be automatically input on the screen by a JAVA script (see the text box 781 in FIG. 35).
In the service providing system example of the above embodiment, the user directly inputs the address of the device (multifunction device 10) when performing user registration in pre-use processing necessary for the multifunction device 10 to receive the service. However, the address of the MFP 10 on the network 1 may be automatically acquired and used (corresponding to the function of the search means in the present invention). At that time, if there are a plurality of candidates, the candidates may be displayed and selected.
[Correspondence with the present invention]
In the embodiment described above, the multifunction machine 10 is a peripheral device in the present invention, the function server 30 is a server in the present invention, and the PC 60 is a terminal device in the present invention.
The communication unit 32 is a server communication unit in the present invention, the control unit 31 is a service providing unit and a service use necessary information transmission control unit in the present invention, and the storage unit 33 is a screen configuration information storage unit in the present invention. is there.
Further, the control unit 61 is the registration request information transmission control unit and the service use necessary information transfer control unit in the present invention, the communication unit 65 is the terminal device communication unit in the present invention, and the display unit 63 is in the present invention. It is a display means, the operation unit 62 is a registration information receiving unit and a transfer command receiving unit in the present invention, and the storage unit 64 is a peripheral device specifying information storing unit in the present invention.
The control unit 11 is a service realization unit and a service use necessary information registration control unit in the present invention, the communication unit 15 is a peripheral device communication unit in the present invention, and the storage unit 16 is a storage unit in the present invention.
Block diagram showing the configuration of the service provision system Diagram showing the configuration of the operation unit Diagram showing the definition of each tag in service definition information The figure which shows the definition of each tag in service I / F information Ladder chart showing an example of communication between the MFP and the function server Directory server processing by directory server Multi-function machine processing by multi-function machine Figure showing the selection method selection screen Figure showing data example of service definition information (1) Service selection screen Figure 2 shows an example of service definition information data Session processing by MFP (1/2) Session processing by multifunction devices (2/2) UI job by MFP The figure which shows the example of data of service I / F information Diagram showing parameter input screen Input job by MFP Output job by MFP Function server processing by function server (1/2) Function server processing by function server (2/2) Session processing by function server (1/2) Session processing by function server (2/2) UI job by function server Scan jobs by function server Print jobs by function server Ladder chart to explain the service information registration mechanism Browser processing by PC Web response processing by function server User registration process by the server yesterday Service information storage processing by MFP An example of HTML1 used when registering service information An example of HTML2 used when registering service information An example of HTML3 used when registering service information Example of screen displayed on PC (1) Example of screen displayed on PC (2)
DESCRIPTION OF SYMBOLS 10 ... MFP, 11 ... Control part, 12 ... Operation part, 13 ... Reading part, 14 ... Recording part, 15 ... Communication part, 16 ... Memory | storage part, 17 ... Sound input part, 18 ... Sound output part, 20 ... Directory Server, 21 ... Control unit, 22 ... Communication unit, 23 ... Storage unit, 24 ... Service definition information storage unit, 25 ... Service definition information, 30 ... Function server, 31 ... Control unit, 32 ... Communication unit, 33 ... Storage unit 34 ... Service I / F information storage unit, 35 ... Service software storage unit, 36 ... Service I / F information, 37 ... Service software, 41 ... Copy key, 42 ... Scanner key, 43 ... FAX key, 44 ... Service key 45 ... Setting key, 46 ... Direction key, 48 ... Direction key, 49 ... Right key, 50 ... OK key, 51 ... Cancel key, 52 ... Display, 60 ... PC, 61 ... Control unit, 62 ... Operation unit, 63 Display unit, 64 ... storage unit, 65 ... communication unit.
A service comprising a server that provides a service via a network, a peripheral device that can use the service by communicating with the server, and a terminal device that can communicate with the server and the peripheral device In the registration system,
When the terminal device receives registration request information that is information related to registration for using the service from a user of the terminal device, the terminal device transmits the registration request information to the server,
When the server receives the registration request information from the terminal device, the server transmits service use necessary information necessary for using the service to the terminal device,
When the terminal device receives the service use necessary information from the server, the terminal device transmits the service use necessary information to the peripheral device,
When the peripheral device receives the service use necessary information from the terminal device, the peripheral device stores the information, and the service becomes available.
Service registration system characterized by
The service registration system according to claim 1,
Server communication means for communicating with the peripheral device and the terminal device;
When the registration request information is received from the terminal device via the server communication means, it is determined whether or not the registration request information is appropriate, and if necessary, use of the service is necessary when using the service. and service needs information transmission control means for transmitting the required information to the terminal device via the server communication means,
Service providing means for providing a service by communicating with the peripheral device via the server communication means;
And the registration information accepting means for accepting the registration request information, which is information about the registration of the order to use the service from the user,
Terminal device communication means for communicating with the server and the peripheral device;
Registration request information transmission control means for transmitting the registration request information received by the registration information receiving means to the server via the terminal device communication means;
And service utilization necessary information transfer control means for transmitting said service use information necessary to the peripheral device via the terminal device communication unit to receive the service required information from the server via the terminal device communication unit,
Peripheral device communication means for communicating with the server and the terminal device;
Storage means for storing the service use necessary information;
Service use necessary information registration control means for storing the service use necessary information in the storage means upon receiving the service use necessary information from the terminal device via the peripheral device communication means;
Service realization means for realizing a service by communicating with the server via the terminal device communication means based on the service use necessary information stored in the storage means;
In the service registration system according to claim 2,
The server further said the registration information receiving unit which is configuration information of an input screen used when accepts the registration request information from said user screen configuration information of the terminal device, said via said server communication means Screen configuration information storage means for storing in a state that can be provided to the terminal device;
The terminal device further includes display means for displaying an image,
The display means, when the registration information receiving unit receives the registration request information from the user, an input screen which is constructed in accordance with the screen configuration information acquired from the server via the terminal device communication unit Displaying,
In the service registration system according to claim 3,
In the input screen displayed by the display means, there is a place for inputting peripheral device specifying information which is information for specifying the peripheral device,
The registration request information transmission control unit transmits the peripheral device specifying information received by the registration information receiving unit as one of the registration request information to the server,
The service use necessary information transmission control means of the server transmits the peripheral device specifying information received from the terminal device together with the service use necessary information to the terminal device,
The service use necessary information transfer control means of the terminal device specifies the peripheral device that transmits the service use necessary information based on the peripheral device specifying information received from the server, and for the specified peripheral device Transmitting the service use necessary information
The terminal device further includes a peripheral device specifying information storage unit capable of storing the peripheral device specifying information,
The registration request information transmission control means stores the peripheral device specifying information received by the registration receiving means in the peripheral device specifying information storage means when transmitting the registration request information to the server,
When the service use necessary information transfer control unit receives the service use necessary information from the server, the service use necessary information transfer control unit transmits the service use necessary information based on the peripheral device specifying information stored in the peripheral device specifying information storage unit. Identifying the peripheral device to be transmitted and transmitting the service use necessary information to the identified peripheral device;
In the service registration system according to claim 4 or 5,
The terminal device further includes search means for searching for the peripheral device with which the terminal device communication means can communicate according to a predetermined condition,
The display means displays information on the peripheral device searched by the search means as a part of the input screen;
In the service registration system according to any one of claims 3 to 6,
The terminal device further includes a transfer command receiving means for receiving a transfer command from a user of the terminal device ,
When the service use necessary information transfer control unit receives the service use necessary information from the server, the service use necessary information transfer control unit configures a confirmation screen for confirming the service use necessary information and displays the confirmation screen on the display unit. only when receiving a transfer instruction from the user, transmitting the service required information to the peripheral device,
The service registration system according to claim 7,
The screen configuration information storage means of the server further stores the screen configuration information of the confirmation screen in an HTML format,
The service usage required information transmission control means of the server also transmits the screen configuration information of the confirmation screen together with the service usage required information,
The service use necessary information transfer control unit of the terminal device configures the confirmation screen based on the screen configuration information transmitted from the server, and transmits the service use necessary information to the peripheral device by a POST method in an HTML request. To send,
A peripheral device capable of using a service via a network, a service registration for enabling the peripheral device to use the service, and communication with a terminal device capable of communicating with the peripheral device; and A server that provides the service to the peripheral device via a network;
When registration request information, which is information related to registration for using the service, is received from the terminal device via the server communication means, it is determined whether or not the registration request information is appropriate. and service needs information transmission control means for transmitting to the terminal device a service required information through the server communication means necessary for using the service,
Service registration for enabling communication with a server that provides a service via a network and a peripheral device that can use the service by communicating with the server, and for allowing the peripheral device to use the service A terminal device for performing
Registration information receiving means for receiving registration request information, which is information related to registration for using the service, from a user of the terminal device ;
Service use for transmitting the service use necessity information to the peripheral device via the terminal device communication means when receiving the service use necessary information necessary for using the service from the server via the terminal device communication means Necessary information transfer control means,
A peripheral device capable of communicating with a server that provides a service via a network and a terminal device that performs service registration for using the service to the server, and that can use the service,
Storage means for storing service use necessary information necessary for using the service ;
JP2004322948A 2004-11-05 2004-11-05 Service registration system, server, terminal device and peripheral device Active JP4241577B2 (en)
JP2004322948A JP4241577B2 (en) 2004-11-05 2004-11-05 Service registration system, server, terminal device and peripheral device
US11/266,585 US8645522B2 (en) 2004-11-05 2005-11-04 Service registering system
EP05256872A EP1655944A1 (en) 2004-11-05 2005-11-07 Service registering system
CNB2005101176327A CN100424682C (en) 2004-11-05 2005-11-07 Service registering system
US14/146,184 US9609029B2 (en) 2004-11-05 2014-01-02 System, terminal device, computer readable medium and method
JP2006135699A JP2006135699A (en) 2006-05-25
JP4241577B2 true JP4241577B2 (en) 2009-03-18
ID=35774127
JP2004322948A Active JP4241577B2 (en) 2004-11-05 2004-11-05 Service registration system, server, terminal device and peripheral device
US (2) US8645522B2 (en)
EP (1) EP1655944A1 (en)
JP (1) JP4241577B2 (en)
CN (1) CN100424682C (en)
JP4572943B2 (en) 2008-03-26 2010-11-04 ブラザー工業株式会社 Data utilization apparatus and data utilization system
JP6375834B2 (en) * 2014-09-30 2018-08-22 ブラザー工業株式会社 Control server and computer program
JP6421643B2 (en) 2015-02-27 2018-11-14 ブラザー工業株式会社 Image forming apparatus, server apparatus, and communication system
JP6460932B2 (en) * 2015-07-01 2019-01-30 キヤノン株式会社 Image processing apparatus, system, image processing apparatus control method, system control method, and program
JP2000242597A (en) * 1999-02-18 2000-09-08 Canon Inc Processor and method for information processing for setting output to devices and storage medium stored with program
JP3977059B2 (en) * 2000-12-22 2007-09-19 キヤノン株式会社 Information processing apparatus, method, and control program
2004-11-05 JP JP2004322948A patent/JP4241577B2/en active Active
2005-11-04 US US11/266,585 patent/US8645522B2/en active Active
2005-11-07 EP EP05256872A patent/EP1655944A1/en active Pending
2005-11-07 CN CNB2005101176327A patent/CN100424682C/en active IP Right Grant
2014-01-02 US US14/146,184 patent/US9609029B2/en active Active
US20060136566A1 (en) 2006-06-22
US8645522B2 (en) 2014-02-04
EP1655944A1 (en) 2006-05-10
CN1770142A (en) 2006-05-10
US9609029B2 (en) 2017-03-28
CN100424682C (en) 2008-10-08
US20140115133A1 (en) 2014-04-24
JP2006135699A (en) 2006-05-25
JP4821892B2 (en) 2011-11-24 Image processing system, server apparatus, image forming apparatus, and computer program
CN100384202C (en) 2008-04-23 Image processing system, image processing device and server