Information processing system and control method thereof

Abstract

To provide an information processing system and a method for controlling the information processing system that reduce a burden on a user applied in input of authentication information in preliminary operations for printing image data submitted to a message application service in a printer.SOLUTION: An information processing system has: first authentication means that receives first authentication information input by a user and executes authentication based on the first authentication information; registration means that registers an image processing apparatus based on the authentication; second transmission means that transmits second authentication information to the image processing apparatus based on the registration of the image processing apparatus performed by the registration means; and second authentication means that executes authentication for executing installation of a predetermined application in a second information processing apparatus based on the second authentication information.SELECTED DRAWING: Figure 13

Description

[Technical field]

[0001] The present invention relates to an information processing system and a control method thereof. [Background technology]

[0002] Patent Document 1 describes that in a message application service (chat service), a cooperative application (Bot application) is executed to transmit image data posted by a user to a printer, and the printer prints the image data. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2018-128843 A Summary of the Invention [Problem to be solved by the invention]

[0004] As described in Patent Document 1, in order for a user to send image data posted to a message application service to a printer, a linked application needs to be installed in a message application server that provides the message application service, and the printer needs to be registered in a tenant server that manages information on the message application service and cloud storage service.

[0005] For example, the following processes are required in the conventional sequences of FIG. 9 (sequence for registering a printer in a tenant server) and FIG. 10 (sequence for installing a cooperative application in a message application server).

[0006] For example, when performing authentication (S810) to register a printer on a tenant server, the user needs to input authentication information (S808). Also, when performing authentication (S910) to install a cooperative application on a message application server (S913), the user needs to input the same authentication information (S906) as the authentication information input in S808. In other words, the user needs to input the same authentication information twice to perform the process of registering a printer on a tenant server and the process of installing a cooperative application on a message application server, which is cumbersome.

[0007] The present invention has been made in consideration of the above-mentioned problems, and aims to reduce the burden on users of entering authentication information as a preliminary step in printing image data posted in a message application service on a printer. [Means for solving the problem]

[0008] An image processing device, a first information processing device, From the terminal device A second information processing device that transmits and receives messages, the second information processing device being configured to transmit the message to the image processing device registered in the first information processing device by executing a predetermined application. Received from the terminal device An information processing system including the second information processing device that transmits print data based on a message, The first information processing device, In the terminal device The first authentication information entered by the user From the terminal device a first receiving means for receiving; The first receiving means receives 1. a first authentication means for performing authentication based on authentication information; The authentication by the first authentication means is performed in order to transmit the print data based on the message to the image processing device. and a registration request received from the image processing device. A registration means for registering the image processing device based on the a second transmission means for transmitting second authentication information to the image processing device based on the registration means having registered the image processing device, The image processing device includes: a second receiving means for receiving the second authentication information from the first information processing device; The second authentication information is generated based on the second receiving means receiving the second authentication information. and a request to install the predetermined application. of The second information processing device and a third transmitting means for transmitting, The second information processing device is transmitting the second authentication information received from the image processing device to the first information processing device; The first information processing device further comprises: The second authentication information From the second information processing device a third receiving means for receiving; a second authentication means for performing authentication for installing the predetermined application in the second information processing device based on the second authentication information received by the third receiving means; and If the installation of the predetermined application is permitted as a result of the authentication by the second authentication means, the predetermined application is installed in the second information processing device based on the installation request. An information processing system comprising: Effect of the Invention

[0009] This reduces the burden on the user of inputting authentication information as a preliminary step for printing image data posted in a message application service on a printer. [Brief description of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing an example of a system configuration of the present invention. [Diagram 2] A diagram showing an example of the hardware configuration of an MFP10 [Diagram 3] FIG. 2 shows an example of a hardware configuration of a user terminal 20. [Figure 4] FIG. 2 is a diagram showing an example of a hardware configuration of a message application server 30. [Diagram 5] FIG. 1 shows an example of a hardware configuration of a tenant server 40. [Figure 6] FIG. 2 is a diagram showing an example of a hardware configuration of an application data server 50. [Figure 7]FIG. 6 is a diagram showing an example of tenant information 601 stored in the tenant server 40. [Figure 8] FIG. 7 shows an example of a message screen 701 of the message application 306. [Figure 9] FIG. 6 is a diagram showing an example of a sequence for registering printer information 606 of the MFP 10 in tenant information 601. [Figure 10] FIG. 13 is a diagram showing an example of a sequence for installing a cooperative application 506 in a message application server 30. [Figure 11] FIG. 10 shows an example of a tenant registration initial screen 1010 displayed on the operation panel 201 of the user terminal 20. [Figure 12] FIG. 11 shows an example of a tenant information authentication screen 1110 displayed on the operation panel 201 of the user terminal 20. [Figure 13] FIG. 13 shows an example of a sequence of a process for registering printer information 606 of the MFP 10 in the tenant information 601 and a process for installing a cooperative application 506 in the message application server 30. [Figure 14] FIG. 13 shows an example of a tenant registration initial screen 1310, 1320 displayed on the operation panel 201 of the user terminal 20. [Figure 15] FIG. 13 is a diagram showing an example of a table showing the correspondence between user information, printer information, and access tokens used in the tenant server 40. [Figure 16] FIG. 13 is a diagram showing an example of a cooperative application operation sequence using the message application server 30 in which the cooperative application 506 is installed. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the configurations shown in the following embodiments are merely examples, and the present invention is not limited to the configurations shown in the drawings.

[0012] 1 is a diagram showing an example of a system configuration of the present invention. The information processing system for providing a message application service, which is a chat service, includes MFPs (Multi Function Peripherals) 10 and 11, which are image processing devices, and user terminals 20 to 22, which are information processing devices. It also includes a message application server 30, a tenant server 40, and an application data server 50.

[0013] MFPs 10 and 11 are image forming devices having a function of printing an image notified by a message application server 30, or a function of notifying a scanned image to the message application server 30. In the figure, an example is given in which two MFPs, indicated as MFPs 10 and 11, are connected, but the number of connections is arbitrary. MFPs 10 and 11 have the same configuration, and hereafter, only MFP 10 will be described.

[0014] The user terminals 20 to 22 are information processing devices such as smartphones, tablet terminals, and personal computers used by users of the message application service. In the figure, three terminals shown as the user terminals 20 to 22 are connected as an example, but the number of connections is arbitrary. A user operates any of the user terminals 20 to 22 to access the message application server 30 on the cloud 60, exchange messages with other users, and execute applications installed in the message application server 30. The user terminals 20 to 22 and the message application server 30 are connected to a wired or wireless communication network, and are capable of transmitting and receiving data between them. In this embodiment, a public line on the Internet is assumed as an example of a communication network, but a dedicated line may also be used. The user terminals 20 to 22 can have the same configuration, and the user terminal 20 will be described below.

[0015] The message application server 30 is a cloud server arranged on the cloud 60, and is a server for providing services using a message application 306. The message application server 30 executes general processing related to message exchange, such as transmission and reception processing of messages and the like for the user terminals 20 to 22, and display of a display screen for message transmission and reception. The message application server 30 can process the exchange of messages and the like between two members, or form a group of three or more members and process the exchange of messages and the like within the group.

[0016] The tenant server 40 is a cloud server arranged on the cloud 60, and is a server that stores and provides information on each tenant. Details of the tenant information stored in the tenant server 40 will be described in the section explaining FIG. 7. Here, a tenant is information indicating an organization, and is information to which account information of multiple users and information on a group in which multiple users participate are linked.

[0017] The application data server 50 is a cloud server located on the cloud 60, and holds data of an integrated application 506 that can be installed in the message application 306. Note that, although the application data is held in the application data server 50 in this embodiment, the data of the integrated application 506 may be downloaded from a network outside the cloud.

[0018] 2 is a diagram showing an example of the hardware configuration of MFP 10. MFP 10 includes a CPU 111, a ROM 112, a RAM 113, a storage 114, an operation unit I / F 115, an operation unit 116, a reading unit I / F 117, a reading unit 118, a printing unit I / F 119, and a printing unit 120. MFP 10 also includes a wireless communication unit I / F 121, a wireless communication unit 122, a communication unit I / F 123, and a communication unit 124.

[0019] The control unit 110 including the CPU 111 controls the operation of the entire MFP 10. The CPU 111 reads out a control program stored in the ROM 112 or the storage 114 to the RAM 113, and performs various controls such as reading control and printing control. The ROM 112 stores a control program executable by the CPU 111. The ROM 112 also stores a boot program, font data, and the like. The RAM 113 is a main memory, and is used as a work area, and a temporary storage area for developing various control programs stored in the ROM 112 and the storage 114. The storage 114 stores image data, print data, various programs, various addresses, and various setting information. In this embodiment, a flash memory is assumed as the storage 114, but an auxiliary storage device such as an SSD (Solid State Drive) or an HDD (Hard Disc Drive) may be used. An eMMC (embedded Multi Media Card) may also be used.

[0020] In the MFP10 of this embodiment, one CPU 111 executes each process shown in the flowcharts described later using one memory (RAM 113), but this is not limited to this. For example, each process shown in the flowcharts described later can be executed by using multiple CPUs, RAMs, ROMs, and storages in cooperation. Also, some of the processes can be executed using hardware circuits such as ASICs and FPGAs.

[0021] An operation unit I / F 115 connects an operation unit 116 including a display unit such as a touch panel and hard keys to the control unit 110. The operation unit 116 displays information to the user and detects inputs from the user.

[0022] The reading unit I / F 117 connects a reading unit 118, such as a scanner, to the control unit 110. The reading unit 118 reads an image of a document, and the CPU 111 converts the image into image data such as binary data. Image data generated based on the image read by the reading unit 118 is transmitted to an external device or printed on recording paper.

[0023] The printing unit I / F 119 connects the control unit 110 to a printing unit 120, such as a printer. The CPU 111 transfers image data (print data) stored in the RAM 113 to the printing unit 120 via the printing unit I / F 119. The printing unit 120 prints an image based on the transferred image data on recording paper fed from a paper feed cassette.

[0024] The wireless communication unit I / F 121 is an I / F for controlling the wireless communication unit 122, and connects the control unit 110 to an external wireless device via wireless communication. The user terminals 20 to 22 may be used as the external wireless device.

[0025] The communication unit I / F 123 connects the control unit 110 and the network 100. The communication unit I / F 123 allows the communication unit 124 to transmit image data and various information within the device to an external device on the network 100, and receives print data and information on the network 100 from an information processing device on the network 100. As a method of transmission and reception via the network 100, transmission and reception using electronic mail (E-mail) and file transmission using other protocols (for example, FTP, SMB, WEBDAV, etc.) can be performed. Furthermore, image data and various setting data can be transmitted and received over the network 100 by accessing from the user terminal 20 and the message application server 30 via HTTP communication.

[0026] 3 is a diagram showing an example of a hardware configuration of the user terminal 20. Note that the user terminal 20 in this embodiment is assumed to be a device such as a smartphone or a tablet PC, but may be any other device as long as it is an information processing device capable of wired or wireless communication.

[0027] The CPU 207 reads out a control program stored in the ROM 208 and executes various processes for controlling the operation of the user terminal 20. The ROM 208 stores the control program. The RAM 209 is used as a temporary storage area such as a main memory and a work area for the CPU 207. The HDD 210 stores various data such as photographs and electronic documents.

[0028] The operation panel 201 has a touch panel function capable of detecting a user's touch operation, and displays various screens provided by the OS and an e-mail sending application. The operation panel 201 is also used to check information stored in the message application server 30. The user can input a desired operation instruction to the user terminal 20 by inputting a touch operation to the operation panel 201. The user terminal 20 has hardware keys (not shown), and the user can input an operation instruction to the user terminal 20 by using the hardware keys.

[0029] The camera 204 captures an image in response to an image capture instruction from the user. The photograph captured by the camera 204 is stored in a predetermined area of ​​the HDD 210. It is also possible to obtain information from a QR code read by the camera 204 using a program capable of analyzing QR codes (registered trademark).

[0030] The user terminal 20 can exchange data with various peripheral devices via an NFC communication unit 205, a Bluetooth (registered trademark) communication unit 206, and a wireless LAN communication unit 211. The Bluetooth communication unit 206 of the user terminal 20 may be compatible with Bluetooth Low Energy.

[0031] FIG. 4 is a diagram showing an example of a hardware configuration of the message application server 30. The CPU 301 reads out a control program stored in the ROM 302 and a message application 306 stored in the HDD 305, and executes various processes for controlling the operation of the message application server 30. The ROM 302 stores the control program. The RAM 303 is used as a temporary storage area such as the main memory and work area of ​​the CPU 301. The HDD 305 stores various data such as messages, images, channel information, and applications. Data can be transmitted and received to and from various devices such as the user terminal 20 and the MFP 10 via the communication unit 304. The communication unit 304 may perform wired communication using Ethernet (registered trademark) or wireless communication such as Wi-Fi. The message application 306 is installed in the HDD 305 and runs on the CPU 301.

[0032] 5 is a diagram showing an example of the hardware configuration of the tenant server 40. The CPU 401 reads out a control program stored in the ROM 402 and executes various processes for controlling the tenant information 601. The stored tenant information 601 will be described later. The ROM 402 stores the control program. The RAM 403 is used as a temporary storage area such as the main memory and work area of ​​the CPU 401. The HDD 405 stores the tenant information 601 and the like. Data can be sent and received via the communication unit 404 to and from various models such as the message application server 30.

[0033] FIG. 6 is a diagram showing an example of a hardware configuration of the application data server 50. The CPU 501 reads out a control program stored in the ROM 502 and executes various processes for controlling the application data server 50. The ROM 502 stores the control program. The RAM 503 is used as a temporary storage area such as the main memory and work area of ​​the CPU 501. The HDD 505 stores linked application data A 506 to C 508 shown in 506 to 508. Data can be transmitted and received with each model such as the message application server 30 via the communication unit 504. The linked applications A 506 to C 508 are applications that operate in cooperation with the message application 306, are stored in the HDD 505, and are installed in the HDD 305 of the message application server 30 via the communication unit 504 in response to a command.

[0034] Fig. 7 is a diagram showing an example of tenant information 601 stored in the HDD 405 in the tenant server 40. The tenant information 601 has one or more groups, and in the example of Fig. 7, there are two groups 602 and 609. Depending on the configuration of the message application 306, one piece of tenant information may have only one piece of group information, in which case the tenant information 601 and the group information are equivalent.

[0035] Each group 602, 609 has information constituting the group, and taking group 602 as an example, it has user information 603, channel information 604, printer information 606, linked application information 607, and files 608. User information 603 indicates information such as the ID of each user belonging to the group.

[0036] The channel information 604 is information for grouping the user information 603, and holds a list 605 that collects the user information corresponding to each channel.

[0037] Printer information 606 indicates device information of the MFP 10. An application that uses group information 602 can refer to this information to send commands such as a print command to any MFP.

[0038] The cooperative application information 607 is information indicating the cooperative application 506 installed in the HDD 305 in which the message application 306 corresponding to the group 602 is installed.

[0039] File information 608 is information about a file held in group 602. For example, by transmitting this file information 608 to MFP 10, MFP 10 can print the file.

[0040] When a user list is referenced within the message application 306 corresponding to the tenant information 601, the message application 306 references group information 602 held in the HDD 405 of the tenant server 40 via the communication unit 304. Then, user information 603 is listed. The same applies to channel information 604, printer information 606, linked application information 607, and file information 608.

[0041] 8 is a diagram showing an example 701 of a message screen of the message application 306. This example screen shows a case where a user 603 accesses the message application 306 linked to a group 602.

[0042] A display area 702 shows user information 603 of a user who is logged in to the user terminal 20 and group information 602 to which the user belongs.

[0043] The display area 703 displays other user information 603 associated with the group information 602 and channel information 604 associated with the group information 602. The user can exchange messages with the selected person by selecting any person from the display area 703. If the user selects channel information 604 here, he or she can exchange messages with all members belonging to the channel.

[0044] A button 704 is a button for adding the cooperating application 506, and pressing this button installs the cooperating application 506 in the message application server 30. In this embodiment, the cooperating application 506 is configured to be installed, but other cooperating applications may be displayed in a list so that the user can select the cooperating application to be installed.

[0045] The person or channel with whom you are currently exchanging messages is displayed in display area 705. That is, the person selected in display area 703 is displayed in 705. In the case of FIG. 8, since channel 1 is selected, channel 1 is displayed in display area 705.

[0046] Messages 706 to 707 are a timeline of messages, displaying a history of messages exchanged. A message may be just text as shown in 706, or may include file 608 information as shown in 707.

[0047] The sequence diagram in Fig. 9 is a conventional method, and shows an example of a sequence for registering printer information 606 of the MFP 10 in the tenant information 601. This sequence is started by transitioning from the operation panel 201 on the user terminal 20 to a tenant registration initial screen 1010 shown in Fig. 11. The tenant registration screen shown in Fig. 11 and the tenant information authentication screen shown in Fig. 12 will also be described together with this sequence diagram.

[0048] FIG. 11 is a diagram showing an example of a tenant registration initial screen 1010 displayed on the operation panel 201 of the user terminal 20. As shown in FIG.

[0049] FIG. 12 is a diagram showing an example of a tenant information authentication screen 1110 displayed on the operation panel 201 of the user terminal 20. In S801, the CPU 207 of the user terminal 20 transmits a tenant information registration request to the MFP 10 when the user presses a tenant registration button 1011 displayed on a tenant registration initial screen 1010 in Fig. 11. Note that the tenant initial registration button in Fig. 11 is displayed based on screen data that the user terminal 20 receives from the MFP 10. The screen data is, for example, HTML data received from the WEB server of the MFP 10 by HTTP communication. Here, connection information (such as a URL) for accessing the tenant server to which the MFP 10 transmits the tenant information registration request is stored in advance in the storage 114 of the MFP 10.

[0050] In S802, the CPU 111 of the MFP 10 sends a device authentication request to the tenant server 40. At this time, as additional information, a client ID that indicates this request in subsequent inquiries and the scope of the requested authentication are notified. The processes permitted by the authentication requested in this sequence are three types: registering the information of the MFP 10 in the tenant server as printer information 606, changing the registered printer information, and performing image processing control using the registered printer information.

[0051] In S803, the CPU 401 of the tenant server 40 returns an authentication request response to the MFP 10. The information returned as the response information is a device code indicating subsequent authentication request information between the MFP 10 and the tenant server 40, a user code indicating authentication request information between the user terminal 20 and the tenant server 40, and a registration URI for signing in using the user code.

[0052] After S803, the MFP 10 continues to poll the tenant server 40 to inquire whether the device has been authenticated using the client ID and device code (S811). The tenant server 40 continues to return to the MFP 10 that the access token has not been issued until the device authentication is completed in S810 (S812). In parallel with this process, the processes from S804 onwards are performed.

[0053] In S804, the CPU 111 of the MFP 10 notifies the user terminal 20 of the user code and registration URI acquired in S803.

[0054] In S805, the CPU 207 of the user terminal 20 displays the user code and URI acquired in S804 on the operation panel 201. A tenant registration information display screen 1020 shown in Fig. 11 is an example of a screen displayed on the operation panel 201 in S805, and displays a registration URI 1021 and a registration code 1022 that is a user code.

[0055] Fig. 12 shows a tenant authentication screen displayed on the operation panel 201 of the user terminal 20. When a user accesses the registration URI displayed on the operation panel 201 in Fig. 11, a screen 1110 for inputting a user code is displayed. The user inputs a user code (registration code) in an input field 1111 and presses an OK button 1112 to request user authentication from the tenant server 40.

[0056] 9, S806 is a flow in which the user terminal 20 requests user authentication from the tenant server 40, and corresponds to the timing when the above-mentioned OK button 1112 is pressed. The user code entered in the input field 1111 is notified to the tenant server.

[0057] In S807, the tenant server 40 requests the user terminal 20 to obtain information for user authentication.

[0058] In S808, the user inputs authentication information (ID, password) corresponding to the tenant in which the user participates. A user authentication screen 1120 shown in Fig. 12 is a screen displayed on the operation panel 201 in S808, and the process transitions to S809 when the confirm button 1122 is pressed after the tenant authentication information is input in 1121. The tenant authentication information input here is authentication information for logging in to the tenant in which the user participates, and is authentication information set for each user.

[0059] In S809, the CPU 207 of the user terminal 20 transmits the authentication information to the tenant server 40.

[0060] In S810, the tenant server 40 performs authentication using the received authentication information. If it is determined that the user corresponding to the received authentication information has authentication authority to add device information, authentication of the device is permitted.

[0061] Fig. 15 is a diagram showing an example of a table showing the correspondence between user information, printer information, and access tokens used by the tenant server 40. Table 1401 is created in the device registration sequence S810, and is stored in the HDD 405 in the tenant server 40. As shown in Fig. 15, the user information and printer information of an authenticated user are linked and saved in table 1401, and a control access token 1402 is assigned to each combination of user information and printer information.

[0062] As described above, the device authentication confirmation flow S811 to S812 is repeated until S810 is performed. S813 is the same process as S811, and when device authentication S810 is completed, the response to device authentication confirmation S813 becomes information S814 indicating authentication completion.

[0063] In S814, if the device authentication process S810 is completed, the tenant server 40 returns a device authentication confirmation to the MFP 10. As a return value, an authentication access token related to the authenticated device is returned.

[0064] S815 is the same process as S817, and the CPU 111 of the MFP 10 polls the tenant server 40 for a registration request using an authentication access token until registration completion is obtained. If registration is not completed, Accepted is returned as shown in S816, and S815 is performed again. If registration is completed, the process proceeds to S818.

[0065] In S818, when the CPU 401 of the tenant server 40 completes the device registration, it returns OK to the MFP 10. At this time, it also notifies the MFP 10 of a unique ID distributed to the printer and a device token acquisition URI to be accessed for the subsequent control access token acquisition process.

[0066] In S819, the MFP 10 uses the device token URI acquired in S818 to request acquisition of the control access token 1402. At this time, the authentication access token is notified as authentication information.

[0067] In S820, the tenant server 40 returns the control access token 1402 to the MFP 10.

[0068] With the above configuration, it is possible to register the printer information 606 on the tenant server 40. Thereafter, it becomes possible for the MFP 10 to make a control request to the tenant server 40 by using the control access token 1402 notified in step S820.

[0069] Through the above operations, it is possible to register the MFP 10 in the tenant server 40. By registering the MFP 10 in the tenant server 40, it is possible to print image data posted in a message application on the MFP 10. A specific printing process will be described with reference to FIG.

[0070] The sequence diagram in Fig. 10 is a conventional method, and shows an example of a sequence for installing a cooperative application 506 in a message application server 30. Fig. 10 shows a sequence for installing the cooperative application 506 in a message application server 30 in which a message application 306 linked to an arbitrary group 602 is installed. By installing the cooperative application 506 in the message application server 30, the user becomes able to instruct the message application to send a print job to the MFP. Also, the message application server 30 becomes able to send a print job to the MFP. Specific processing will be described in Fig. 16.

[0071] This sequence is started when installation of any of the cooperative applications 506 is designated from the operation panel 201 of the user terminal 20.

[0072] In S901, the user terminal 20 checks with the application data server whether data of the cooperative application 506 to be installed in the message application 306 exists in the HDD 505 in the application data server 50. If the cooperative application 506 exists, in S902, the application data server 50 returns a unique application ID indicating the cooperative application 506 to the user terminal 20.

[0073] In S903, the CPU 207 of the user terminal 20 creates a URI for requesting authentication, using the application ID acquired in S902.

[0074] In S904, the CPU 207 of the user terminal 20 uses the URI created in S903 to request the tenant server 40 for authentication to install the coordinated application 506 in the message application server 30. At this time, the scope of the requested authentication is notified as additional information. The processes permitted by the requested authentication in this sequence are to install the coordinated application 506 in the message application server 30 and to change the settings of the coordinated application 506 in the message application server 306.

[0075] In S905, the CPU 401 of the tenant server 40 requests the user terminal 20 to obtain information for authentication.

[0076] In S906, the user inputs authentication information corresponding to the tenant in which the user will participate, and the operation panel 201 of the user terminal 20 accepts the input. The authentication information input here is the same as the authentication information input in S908 of FIG.

[0077] In S907 , the CPU 207 of the user terminal 20 transmits the input authentication information to the tenant server 40 .

[0078] In S908, the CPU 401 of the tenant server 40 performs user authentication using the authentication information received in S907. If it is determined by the authentication that the identified user information 603 has authentication authority for application installation, the CPU 401 of the tenant server 40 notifies the user terminal 20 of an access token for application installation authentication.

[0079] In S909, the CPU 207 of the user terminal 20 requests the message application server 30 to install the cooperative application 506. At this time, the application ID acquired in S902 and the access token acquired in S908 are sent as additional information.

[0080] In S910, the CPU 301 of the message application server 30 requests the tenant server 40 to confirm whether the installation has been authenticated. At this time, the CPU 301 transmits the received access token to the tenant server 40.

[0081] In S911, the tenant server 40 performs authentication using the access token, and if the authentication is successful, responds to the message application server 30 that the authentication is successful.

[0082] In S912, the CPU 301 of the message application server 30 requests the application data server 50 for data of the cooperative application 506. At this time, the CPU 301 transmits the received application ID to the application data server 50.

[0083] In S913, the application data server 50 transmits data of the cooperative application 506 corresponding to the received application ID to the message application server 30. Then, the CPU 301 of the message application server 30 installs the received cooperative application 506.

[0084] With the above configuration, the user can install the cooperative application 506 in the HDD 505 of the application data server 50 into the HDD 305 of the message application server 30 .

[0085] By the above process, a cooperative application 506 for enabling a print job to be sent on a message application can be installed in the message application server 30. Then, the user can send a print job to the MFP using the cooperative application 506 on the message application. Furthermore, by performing the process in Fig. 9, the MFP 10 is registered in the tenant server 40, and it becomes possible to specify the MFP 10 to which the print job is to be sent using the cooperative application 506.

[0086] In order for a user to instruct the message application to transmit a print job to the MFP 10, it is necessary to register the MFP 10 in the tenant server 40 and install a cooperative application 506 in the message application server 30.

[0087] In the conventional method of FIGS. 9 and 10, the user must input the same authentication information in both the process of installing the cooperative application 506 in the message application server 30 and the process of registering the MFP 10 in the tenant server 40, which is cumbersome.

[0088] Therefore, in this embodiment, an object is to reduce the user's effort in issuing an instruction on a message application to transmit a print job to the MFP 10. In order to solve the above problem, the following process is executed.

[0089] 13 is a diagram showing an example of a sequence of a process for registering the printer information 606 of the MFP 10 in the tenant information 601 and a process for installing the cooperative application 506 in the message application server 30. This sequence is started by transitioning from the operation panel 201 on the user terminal 20 to a tenant registration initial screen 1310 shown in FIG.

[0090] 14 is a diagram showing an example of tenant registration initial screens 1310, 1320 displayed on the operation panel 201 of the user terminal 20. When the tenant registration button 1311 on the tenant registration initial screen 1310 is pressed, the CPU 207 of the user terminal 20 requests the MFP 10 to register tenant information. When the tenant registration button 1311 is pressed after checking a check box 1312, the CPU 207 of the user terminal 20 simultaneously requests tenant registration and installation of the associated application 506. In S1201, the user presses the tenant registration button 1311 with the check box 1312 checked, and the operation panel 201 of the user terminal 20 accepts the pressing.

[0091] In S1202, the CPU 111 of the MFP 10 sends a device authentication request to the tenant server 40. At this time, as additional information, a client ID that indicates this request in a subsequent inquiry and the scope of the requested authentication are notified. The processes permitted by the authentication requested in this sequence include registering the information of the MFP 10 in the tenant server as printer information 606, changing the registered printer information, and controlling image processing using the registered printer information. Also included are installing the cooperative application 506 in the message application server 30 and changing the settings of the cooperative application 506 in the message application 306.

[0092] In S1203, the CPU 401 of the tenant server 40 returns an authentication request response to the MFP 10. The information returned as the response information is a device code indicating subsequent authentication request information between the MFP 10 and the tenant server 40, a user code indicating authentication request information between the user terminal 20 and the tenant server 40, and a registration URI for signing in using the user code.

[0093] After S1203, the CPU 111 of the MFP 10 continues to poll the tenant server 40 to inquire whether the device has been authenticated using the client ID and device code (S1211). The tenant server 40 continues to return to the MFP 10 that the access token has not been issued until the device authentication is completed in S1210 (S1212). In parallel with this process, the processes from S1204 onwards are performed.

[0094] In S1204, the CPU 111 of the MFP 10 notifies the user terminal 20 of the user code and registration URI acquired in S1203.

[0095] In S1205, the CPU 111 of the user terminal 20 displays the user code and URI acquired in S1204 on the operation panel 201. The tenant registration information display screen displayed by accessing the URI is the same as that shown in FIG. 12 described above, and therefore will not be described.

[0096] S1206 is a flow in which the CPU 207 of the user terminal 20 requests user authentication from the tenant server 40, and corresponds to the timing when the user inputs a user code (registration code) and presses the OK button 1112 in Fig. 12. With this flow, the user code is notified from the user terminal 20 to the tenant server 40.

[0097] In S1207, the CPU 401 of the tenant server 40 requests the user terminal 20 to acquire information for user authentication.

[0098] In S1208, the user inputs authentication information corresponding to the tenant in which the user participates. A user authentication screen 1120 shown in Fig. 12 is a screen displayed on the operation panel 201 in S1208, and when the user inputs authentication information in an input field 1121 and then presses an OK button 1122, the process transitions to S1209.

[0099] In S1209, the CPU 207 of the user terminal 20 transmits the input authentication information to the tenant server 40. Here, the CPU 207 transmits the authentication information as a response to the accessed URI. Since the URI and information on the MFP 10 are registered in association with each other in the tenant server 40, by receiving the authentication information as a response to the URI, it is possible to identify which MFP should be registered.

[0100] Note that the information on the MFP 10 corresponding to the URI here includes identification information for identifying the MFP 10. In addition, the information may include the IP address of the MFP 10, the name of the MFP 10, and the like.

[0101] In S1210, the CPU 401 of the tenant server 40 performs user authentication using the received authentication information. If it is determined that the user information 603 indicated by the authentication information has authentication authority to add device information, the CPU 401 of the tenant server 40 permits device authentication. In other words, the CPU 401 of the tenant server 40 determines whether or not to register the MFP 10 in the tenant server 40 based on the received authentication information.

[0102] As described above, the device authentication confirmation flow S1211 to S1212 is repeated until S1210 is performed. S1213 is the same process as S1211, and when the device authentication S1210 is completed, the process proceeds to S1214 for transmitting information indicating that the response to the device authentication confirmation S1213 is authentication completion.

[0103] In S1214, if the device authentication process S1210 is completed, the CPU 401 of the tenant server 40 returns information indicating device authentication confirmation to the MFP 10. Specifically, the CPU 401 returns an authentication access token related to the authenticated device as a return value.

[0104] S1215 and S1217 are equivalent processes, and the CPU 111 of the MFP 10 polls the tenant server 40 for a registration request using an authentication access token until a registration completion notice is obtained. If registration is not completed, Accepted is returned as shown in S1216, and S1215 is performed again. If registration is completed, the process proceeds to S1218.

[0105] In S1218, when the CPU 401 of the tenant server 40 completes the device registration, it returns OK to the MFP 10. At this time, it also notifies the MFP 10 of a unique ID that is distributed to the printer and a token acquisition URI for accessing for the subsequent control access token acquisition process.

[0106] In S1219, the CPU 111 of the MFP 10 uses the token acquisition URI acquired in S1218 to request acquisition of the control access token 1402. At this time, the authentication access token is transmitted to the tenant server 40 as authentication information.

[0107] In S1220, the tenant server 40 returns the control access token 1402 to the MFP 10.

[0108] In this embodiment, an example has been described in which an authentication access token is received in S1214 based on the registration of the MFP 10 in S1210, and a control access token is obtained using the authentication access token, but the present invention is not limited to this. For example, the CPU 401 of the tenant server 40 may transmit a control access token to the MFP 10 based on the registration of the MFP 10 in S1210. In this case, the CPU 111 of the MFP 10 transmits the received control access token and a request to install the linked application 506 to the message application server 30.

[0109] In S1221, based on receiving the control access token 1402, the CPU 111 of the MFP 10 requests the message application server 30 to install the coordinated application 506. As the attached information at this time, the control access token acquired in S1214 and an application ID that uniquely identifies the coordinated application 506 are transmitted. The application ID transmitted here is pre-stored in the storage 114 of the MFP 10. Therefore, in the conventional technology, the user had to search for the application ID of the coordinated application 506 and transmit the ID to the application data server 50, but this process can be omitted in this flow.

[0110] In S1222, the CPU 301 of the message application server 30 requests the tenant server 40 to confirm whether the installation has been authenticated by sending the control access token acquired in S1214. That is, the CPU 401 of the tenant server 40 performs authentication based on the control access token, and determines whether or not to permit installation of the linked application 506 in the message application server 30.

[0111] In S1223, the CPU 401 of the tenant server 40 responds to the message application server 30 that confirmation has been completed.

[0112] In S 1224 , the CPU 301 of the message application server 30 requests the application data server 50 to transmit data of the cooperative application 506 .

[0113] In S1225, the CPU 501 of the application data server 50 transmits data of the cooperative application 506 to the message application server 30. Then, the CPU 301 of the message application server 30 installs the received cooperative application 506.

[0114] With the above configuration, it is possible to install the cooperative application 506 in the message application server 30 and to input the authentication information required for registering the MFP 10 in the tenant server 40 by the user only once.

[0115] 16 is a diagram showing an example of a sequence illustrating an example of using a cooperative application 506 installed in the message application server 30. In this embodiment, the cooperative application 506 has a function of transmitting image data received from the user terminal 20 to the MFP 10 and requesting print control, and this function will be described.

[0116] Note that this sequence shows the operation when the cooperative application 506 is installed in the HDD 305 of the message application server 30 by implementing the sequences shown in Fig. 10 and Fig. 13. Here, the cooperative application 506 is executed by the message application server 30. Also, in the tenant server 40, the process of registering the MFP 10 in the tenant server 40 is executed as in the sequences in Fig. 9 and Fig. 13.

[0117] In the sequence of FIG. 16, all steps of the message application server 30 are processes executed when the cooperative application 506 is executed.

[0118] In S1501, the CPU 207 of the user terminal 20 requests the message application server 30 to send a list of printer information 606 linked to tenants in which the user of the user terminal 20 participates.

[0119] In S1502 , the CPU 301 of the message application server 30 requests the tenant server 40 to send a list of the printer information 606 linked to the tenant information 601 .

[0120] In S1503, the tenant server 40 requests the user terminal 20 to obtain information for user authentication.

[0121] In S1504, the user inputs authentication information corresponding to the tenant in which the user will participate. The authentication information input here is the same as the ID and password input in the input field 1121 in Fig. 12. In addition, the operation panel 201 of the user terminal 20 accepts the input of the authentication information by the user.

[0122] In S1505, the CPU 207 of the user terminal 20 transmits to the tenant server 40 the authentication information accepted in S1504.

[0123] In S1506, the CPU 401 of the tenant server 40 performs authentication using the received authentication information. If the authentication is successful, the CPU 401 of the tenant server 40 searches table 1401 for printers that can be used by the user information 603 corresponding to the authentication information. From the search results, usable printer information 606 and a control access token 1402 are listed and sent to the message application server 30. For example, when the tenant server 40 receives the authentication information of user 1, in the example of Fig. 15, "Printer 1" and "Printer 2" are sent as printer information, and "AAAA-BBBB-CCCC" and "DDDD-EEEE-FFFF" are sent as control access tokens.

[0124] In S1507, the CPU 301 of the message application server 30 transmits to the user terminal 20 the list (printer information and control access token) acquired in S1505.

[0125] In S1508, the CPU 207 of the user terminal 20 displays the received printer information on the operation panel 201 as available printers. The user selects an arbitrary printer from the displayed information. The user also designates the image data posted as a message to the message application server 30 as the image data to be printed. For example, in the example of FIG. 8, the message 707 to which the file is attached is designated, and thus "document.pdf" is designated as the image data to be printed. Note that a plurality of image data may be designated here. Here, the method of designating the image data is performed by the user sending a message such as "Please print document.pdf" to the message application server 30, and the message application server 30 interpreting the message. In other words, the message application server 30 can interpret the message received from the user and transmit image data (print data) to the MFP 10 based on the message.

[0126] Furthermore, the message application server 30 may interpret a received message and designate a printer based on the message.

[0127] In S1509, the CPU 207 of the user terminal 20 sends to the message application server 30 the access token 1402 for controlling the printer selected in S1508 and the image data to be printed.

[0128] In S1510, the CPU 301 of the message application server 30 sends the control access token 1402 received in S1509 to the tenant server 40.

[0129] In S1511, the CPU 401 of the tenant server 40 sends to the message application server 30 the printer information corresponding to the received control access token.

[0130] In S1512, the CPU 301 of the message application server 30 sends the image data and a print request to the MFP 10 corresponding to the printer information. Specifically, the CPU 301 of the message application server 30 identifies the MFP to which the image data is to be sent, based on the printer information received in S1511.

[0131] In S1513, the CPU 111 of the MFP 10 performs printing processing of the received image data. Note that print settings may also be received from the message application server 30 together with the image data. In this case, the print settings are those set by the user on the message application server 30 via the user terminal 20.

[0132] With the above configuration, the message application server 30 can transmit image data received from the user terminal 20 to the MFP 10 and request print control.

[0133] The configuration shown in this embodiment is merely an example, and the present invention is not limited to the illustrated configuration. For example, by storing the control access token shown in S1501 to S1507 in the message application server 30 or the user terminal 20, it is possible to omit the need to perform authentication every time.

[0134] In this embodiment, an example has been described in which authentication information is input at user terminal 20 as in S1208, but it may be possible to input the information at MFP 10. In that case, the registration button in S1201 is also pressed on operation unit 116 of MFP 10, and the display of the user code and URI in S1205 is also performed on operation unit 116. Input of the user code is also performed on operation unit 116.

[0135] When the authentication information is inputted at the user terminal 20, the authentication information is stored in the storage 114. Then, when the registration of the MFP 10 to the tenant server 40 is completed, the MFP 10 transmits an installation request for the coordinated application 506 and the stored authentication information to the message application server 30 without receiving a control access token. The message application server 30 transmits the received authentication information and a permission request to install the coordinated application 506 in the message application server 30 to the tenant server 40. The subsequent processing is similar to S1223 to S1235.

[0136] <Other embodiments> The present invention can be realized by supplying a program that realizes one or more functions of the above-mentioned embodiments to a system or device via a network or a storage medium. Then, one or more processors in the computer of the system or device can read and execute the program. It can also be realized by a circuit (e.g., ASIC) that realizes one or more functions. [Explanation of symbols]

[0137] 10 MFP 20 User terminal 30 Message Application Server 40 Tenant Server 50 Application Data Server

Claims

1. An information processing system including an image processing device, a first information processing device, and a second information processing device that transmits and receives messages from a terminal device, the second information processing device transmitting print data based on a message received from the terminal device to the image processing device registered in the first information processing device by executing a predetermined application, The first information processing device, a first receiving means for receiving, from the terminal device, first authentication information input by a user at the terminal device; a first authentication means for performing authentication based on the first authentication information received by the first receiving means; a registration unit that registers the image processing device based on the authentication by the first authentication unit and a registration request received from the image processing device in order to transmit the print data based on the message to the image processing device; a second transmission means for transmitting second authentication information to the image processing device based on the registration means having registered the image processing device, The image processing device includes: a second receiving means for receiving the second authentication information from the first information processing device; a third transmission means for transmitting the second authentication information and an installation request for the predetermined application to the second information processing device based on the second authentication information received by the second reception means, The second information processing device is transmitting the second authentication information received from the image processing device to the first information processing device; The first information processing device further includes: a third receiving means for receiving the second authentication information from the second information processing device; a second authentication means for performing authentication for installing the predetermined application in the second information processing device based on the second authentication information received by the third receiving means, An information processing system characterized in that, if installation of the specified application is permitted as a result of authentication by the second authentication means, the specified application is installed in the second information processing device based on the installation request.

2. the third transmission means transmits the second authentication information to the first information processing device; 2. The information processing system according to claim 1, wherein the third receiving means receives the second authentication information from the image processing device.

3. 3. The information processing system according to claim 1, wherein the first receiving means receives the first authentication information input by the user in a terminal device.

4. The information processing system according to any one of claims 1 to 3, characterized in that the second information processing device receives information about image processing devices registered in the first information processing device from the first information processing device, and transmits the print data to an image processing device selected by a user from among the image processing devices based on the information.

5. The first information processing device, 5. The information processing system according to claim 1, further comprising a decision means for deciding whether or not to permit installation of the specified application on the second information processing device based on authentication by the second authentication means.

6. The first information processing apparatus transmits predetermined information to the second information processing apparatus based on the decision by the decision means to permit installation of the predetermined application in the second information processing apparatus; 6. The information processing system according to claim 5, wherein the second information processing apparatus installs the predetermined application on the basis of receiving the predetermined information from the first information processing apparatus.

7. The information processing system according to any one of claims 1 to 6, characterized in that the third transmitting means transmits the second authentication information and identification information of the specified application to the second information processing device based on the second receiving means receiving the second authentication information.

8. 8. The information processing system according to claim 7, wherein the identification information of the predetermined application is stored in the image processing device.

9. The information processing system according to claim 7 or 8, characterized in that the second information processing device receives the specified application from an external device based on the identification information of the specified application received from the image processing device, and installs the specified application.

10. 10. The information processing system according to claim 1, wherein the second information processing apparatus interprets a received message and transmits the print data to the image processing apparatus based on the message.

Images