Apparatus, cloud printing server system, cloud printing system and control method thereof

Abstract

The invention provides a device, a cloud printing server system, a cloud printing system and a control method thereof. A cloud printing apparatus is connected to a cloud print server system, the cloud printing apparatus including: a transmission unit configured to transmit a registration request including an apparatus type indicating at least one of a cloud print function and a cloud scan function to the cloud print server system; a receiving unit configured to receive, from the cloud print server system, a service identifier for acquiring an access token corresponding to a device type included in the registration request and endpoint information indicating an endpoint; an acquisition unit configured to transmit the service identifier to the cloud print server system, and acquire an access token used in a service corresponding to the device type from the cloud print server system; and a communication unit configured to communicate with the endpoint by using the access token when the service is executed.

Description

Technical Field

[0001] The present invention relates to a device for cloud printing, a control method for the device for cloud printing, a cloud printing server system, a control method for the cloud printing server, a cloud printing system, a control method for the cloud printing system, a storage medium, and a computer program product. Background Art

[0002] Known printing services have enabled a user to directly send a print job from a client terminal such as a PC to a multifunction peripheral device for printing. Japanese Patent Application Laid-Open No. 2023-71252 proposes a cloud printing service using a cloud service processed on the Internet.

[0003] As described in Japanese Patent Application Laid-Open No. 2022-136867, a multifunction peripheral device compatible with a local scanning function is known from the "Mopria Alliance Technical Working Group eSCL Technical Specification" version 2.9 of March 22, 2021 (URL = https: / / mopria.org / mopria-escl-specification) approved by the Mopria Commission.

[0004] When registering a device in a cloud device registration service in known cloud printing, it is impossible to determine whether the registered device is a device compatible with cloud scanning having a cloud scanning function. Therefore, the device registered in the cloud device registration service cannot be used as a cloud scanning device. Summary of the Invention

[0005] The present invention can implement a technique of using a device registered in a cloud device registration service as a cloud scanning device.

[0006] One aspect of the present invention provides a device for cloud printing, which is connected to a cloud printing server system via a network. The cloud printing server system processes a cloud printing service and a cloud scanning service. The device for cloud printing includes: a sending unit configured to send a registration request to the cloud printing server system, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; a receiving unit configured to receive, from the cloud printing server system, a service identifier and endpoint information indicating an endpoint, the service identifier being used to obtain an access token corresponding to the device type included in the registration request; an obtaining unit configured to send the service identifier to the cloud printing server system and obtain, from the cloud printing server system, an access token used in a service corresponding to the device type; and a communication unit configured to communicate with the endpoint by using the access token when executing the service.

[0007] Another aspect of the present invention provides a control method for a cloud printing device, the cloud printing device being connected to a cloud printing server system via a network, the cloud printing server system processing cloud printing services and cloud scanning services, the control method comprising the steps of: sending a registration request to the cloud printing server system that processes cloud printing services and cloud scanning services, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; receiving, from the cloud printing server system, a service identifier and endpoint information indicating an endpoint, the service identifier being used to obtain an access token corresponding to the device type included in the registration request; sending the service identifier to the cloud printing server system and obtaining, from the cloud printing server system, an access token used in a service corresponding to the device type; and communicating with the endpoint by using the access token when executing the service.

[0008] Still another aspect of the present invention provides a non-transitory computer-readable storage medium storing a program for causing a computer to execute the respective steps of the control method for a cloud printing device, the cloud printing device being connected to a cloud printing server system via a network, the cloud printing server system processing cloud printing services and cloud scanning services, the control method comprising the steps of: sending a registration request to the cloud printing server system that processes cloud printing services and cloud scanning services, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; receiving, from the cloud printing server system, a service identifier and endpoint information indicating an endpoint, the service identifier being used to obtain an access token corresponding to the device type included in the registration request; sending the service identifier to the cloud printing server system and obtaining, from the cloud printing server system, an access token used in a service corresponding to the device type; and communicating with the endpoint by using the access token when executing the service.

[0009] Another aspect of the present invention provides a computer program product, which includes a program for causing a computer to execute the respective steps of a control method for a cloud printing device. The cloud printing device is connected to a cloud printing server system via a network. The cloud printing server system processes cloud printing services and cloud scanning services. The control method includes the following steps: sending a registration request to the cloud printing server system that processes cloud printing services and cloud scanning services, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; receiving, from the cloud printing server system, a service identifier and endpoint information indicating an endpoint, the service identifier being used to obtain an access token corresponding to the device type included in the registration request; sending the service identifier to the cloud printing server system and obtaining, from the cloud printing server system, an access token used in a service corresponding to the device type; and communicating with the endpoint by using the access token when executing the service.

[0010] Another aspect of the present invention provides a cloud printing server system that processes cloud printing services and cloud scanning services for a device. The cloud printing server system includes: a receiving unit configured to receive a registration request from the device, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; a sending unit configured to send a service identifier and endpoint information indicating an endpoint to the device, the service identifier being used to obtain an access token corresponding to the device type; and an access token generation unit configured to, when receiving a request from the device for obtaining an access token including the service identifier, generate an access token corresponding to the service identifier and send the access token corresponding to the service identifier to the device.

[0011] Another aspect of the present invention provides a control method for a cloud printing server system that processes cloud printing services and cloud scanning services for a device. The control method includes: receiving a registration request from the device, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; sending a service identifier and endpoint information indicating an endpoint to the device, the service identifier being used to obtain an access token corresponding to the device type; and when receiving a request from the device for obtaining an access token including the service identifier, generating an access token corresponding to the service identifier and sending the access token corresponding to the service identifier to the device.

[0012] Another aspect of the present invention provides a non - transitory computer - readable storage medium storing a program for causing a computer to execute each step of a control method of a cloud printing server system that processes cloud printing services and cloud scanning services. The control method includes the following steps: receiving, from the device, a registration request for at least one of the cloud printing service and the cloud scanning service, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; sending, to the device, a service identifier and endpoint information indicating an endpoint, the service identifier being used to obtain an access token corresponding to the device type; and when receiving, from the device, a request for obtaining an access token including the service identifier, generating an access token corresponding to the service identifier and sending the access token corresponding to the service identifier to the device.

[0013] Another aspect of the present invention provides a computer program product including a program for causing a computer to execute each step of a control method of a cloud printing server system that processes cloud printing services and cloud scanning services. The control method includes the following steps: receiving, from the device, a registration request for at least one of the cloud printing service and the cloud scanning service, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; sending, to the device, a service identifier and endpoint information indicating an endpoint, the service identifier being used to obtain an access token corresponding to the device type; and when receiving, from the device, a request for obtaining an access token including the service identifier, generating an access token corresponding to the service identifier and sending the access token corresponding to the service identifier to the device.

[0014] Another aspect of the present invention provides a cloud printing system, which includes a device; and a cloud printing server system. The cloud printing server system processes cloud printing services and cloud scanning services for the device. The device includes: a first sending unit configured to send a registration request to the cloud printing server system, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; a first receiving unit configured to receive a service identifier and endpoint information indicating an endpoint from the cloud printing server system, the service identifier being used to obtain an access token corresponding to the device type included in the registration request; an obtaining unit configured to send the service identifier to the cloud printing server system and obtain an access token corresponding to the device type from the cloud printing server system; and a communication unit configured to communicate with the endpoint by using the access token when performing a cloud printing service or a cloud scanning service. The cloud printing server system includes: a second receiving unit configured to receive a registration request from the device; a second sending unit configured to send a service identifier and endpoint information indicating an endpoint to the device, the service identifier being used to obtain an access token corresponding to the device type; and an access token generating unit configured to generate an access token corresponding to the service identifier and send the access token corresponding to the service identifier to the device when receiving a request for obtaining an access token from the device.

[0015] Another aspect of the present invention provides a control method for a cloud printing system, the cloud printing system including a device; and a cloud printing server system. The cloud printing server system processes cloud printing services and cloud scanning services for the device. Wherein, the device sends a registration request to the cloud printing server system, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function. The cloud printing server system receives the registration request from the device and sends a service identifier and endpoint information indicating an endpoint to the device, the service identifier being used to obtain an access token corresponding to the device type. The device receives the service identifier and the endpoint information from the cloud printing server system. The device sends the service identifier to the cloud printing server system. The cloud printing server system generates an access token corresponding to the service identifier and sends the access token corresponding to the service identifier to the device when receiving the service identifier from the device. The device obtains the access token from the cloud printing server system, and the device communicates with the endpoint by using the access token when performing a cloud printing service or a cloud scanning service. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 is a cloud printing registration sequence diagram of a multi-functional peripheral device.

[0017] Figure 2 It is a sequence diagram for the cloud printing startup of a multifunctional peripheral device.

[0018] Figure 3 It is a sequence diagram for cloud printing - style printing of a multifunctional peripheral device.

[0019] Figure 4 It is a sequence diagram for the startup and printing of the local scanning function of a multifunctional peripheral device.

[0020] Figure 5 It is a hardware configuration diagram of a multifunctional peripheral device in an example.

[0021] Figure 6 It is a software configuration diagram of a multifunctional peripheral device in an example.

[0022] Figure 7 It is an operation panel description diagram of a multifunctional peripheral device in an example.

[0023] Figure 8 It is a hardware configuration diagram of a cloud printing server in an example.

[0024] Figure 9 It is a software configuration diagram of a cloud printing server in an example.

[0025] Figure 10 It is a cloud device registration sequence diagram of a multifunctional peripheral device in an example.

[0026] Figure 11 It is a startup sequence diagram of a multifunctional peripheral device in an example.

[0027] Figure 12 It is a cloud printing - style printing sequence diagram of a multifunctional peripheral device in an example.

[0028] Figure 13 It is a cloud scanning sequence diagram of a multifunctional peripheral device in an example.

[0029] Figure 14 It is a diagram showing the device type sent by a multifunctional peripheral device during cloud device registration in an example.

[0030] Figure 15 It is a flowchart showing the cloud device registration process of a multifunctional peripheral device in an example.

[0031] Figure 16 It is a flowchart showing the processing when a cloud device registration service receives a registration request in an example. Detailed implementation manners

[0032] In the following, embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments are not intended to limit the scope of the present invention. In the embodiments, multiple features are described, but the invention is not limited to inventions that require all of these features, and these features can be appropriately combined. In addition, in the drawings, the same or similar configurations are given the same reference numerals, and redundant descriptions thereof will be omitted.

[0033] Reference will be made to Figures 1 to 3 describe the operation sequence of cloud printing.

[0034] Figure 1 is a sequence diagram for cloud printing registration of a multifunction peripheral device.

[0035] It is assumed that the multifunction peripheral device 101 supports the cloud printing function and the WebUI function for operating the multifunction peripheral device 101. It is assumed that the client terminal 100 supports the cloud printing client function and the WebUI client for operating the WebUI. It is assumed that the cloud device registration service 102 is a service on the Internet processed by the cloud printing server.

[0036] The user first uses the WebUI client of the client terminal 100 to send a request 110 for cloud device registration to the multifunction peripheral device 101 via the WebUI. When the multifunction peripheral device 101 receives the request 110, it sends a device code generation request 111 to the cloud device registration service 102. When the cloud device registration service 102 receives the request 111, it sends a device code generation response 112 to the multifunction peripheral device 101. The device code generation response 112 includes a device code 130, a user code 131, and a verification URL 132 generated by the cloud device registration service 102. When the multifunction peripheral device 101 receives the device code generation response 112, it sends a cloud device registration response 113 to the client terminal 100. The cloud device registration response 113 includes the user code 131 and the verification URL 132 generated by the cloud device registration service 102.

[0037] When the client terminal 100 receives the cloud device registration response 113, it displays the user code 131 and the verification URL 132 on the WebUI client. The user operates the WebUI client to access the displayed verification URL 132. Then, by inputting the cloud account 133 and the user code 131, a cloud device registration approval request 114 is sent to the cloud device registration service 102. When the cloud device registration service 102 receives the cloud device registration approval request 114, it associates the cloud device registration approval request 114 with the administrator of the multifunction peripheral device 101 registered as the cloud account 133, and manages the multifunction peripheral device 101 as having been approved for registration. Then, the cloud device registration service 102 sends a cloud device registration approval response 115 to the client terminal 100.

[0038] The multifunctional peripheral device 101 sends an access token request 116 to the cloud device registration service 102. The access token request 116 includes a device code 130 generated by the cloud device registration service 102. When receiving the access token request 116, the cloud device registration service 102 generates an access token 134. The access token 134 is used for subsequent registration processes and proves the authorization of the registration process. The cloud device registration service 102 sends an access token response 117 to the multifunctional peripheral device 101. The access token response 117 includes the access token 134 generated by the cloud device registration service 102.

[0039] The multifunctional peripheral device 101 sends a registration request 118 to the cloud device registration service 102. The registration request 118 includes a device name 135 and a device type 136. The access token 134 is added to the HTTP header of the registration request 118. The device name 135 is the device name set in the multifunctional peripheral device 101. The device type 136 indicates the device type of the multifunctional peripheral device 101, and "printer" is set in the cloud printing service 200. Assume that the cloud printing service 200 is a service on the Internet processed by a cloud printing server. When receiving the registration request 118, the cloud device registration service 102 determines whether the access token 134 is a token to which the cloud device registration server 102 itself has responded with an access token response 117. This confirms whether the sent registration request 118 is an authorized registration request. When the cloud device registration service 102 determines that the registration request 118 is an authorized registration request as a result of the confirmation, it sends a registration response 119 to the multifunctional peripheral device 101 and starts the registration process of the multifunctional peripheral device 101.

[0040] The multifunctional peripheral device 101 sends a registration status request 120 to the cloud device registration service 102. Similarly, in the registration status request 120, the access token 134 is added to the HTTP header. When receiving the registration status request 120, the cloud device registration service 102 confirms the access token 134 in the same way as when receiving the registration request 118. When it is determined that the registration request is an authorized registration request, the registration status request 120 continues the following process. When the registration is completed, the cloud device registration service 102 sends a registration status response 121 to the multifunctional peripheral device 101. The access token response 117 includes a print service URL 137, a notification service URL 138, and a print service resource ID 139. The print service URL 137 is endpoint information indicating the endpoint of the cloud printing service 200. The notification service URL 138 is endpoint information indicating the endpoint of the cloud printing event notification service 201. The print service resource ID 139 is unique information generated by the cloud device registration service to obtain an access token for using the print service. Assume that the cloud printing event notification service 201 is a service on the Internet processed by a cloud printing server.

[0041] Next, the multifunctional peripheral device 101 obtains an access token for using the cloud printing service 200. The multifunctional peripheral device 101 sends a Nonce request 122 to the cloud device registration service 102. A Nonce is random data that is only valid for use once in authentication. When the cloud device registration service 102 receives the Nonce request 122, it generates a Nonce 140 and sends a Nonce response 123 to the multifunctional peripheral device 101. The Nonce response 123 includes the Nonce 140.

[0042] When the multifunctional peripheral device 101 obtains the Nonce 140 in the Nonce response 123, it generates a JSON Web Token (JWT) 141. A JWT is authentication information represented in JSON format, encoded with Base64 and added with a signature. Then, the multifunctional peripheral device 101 sends an access token request 124 to the cloud device registration service 102. The access token request 124 includes the print service resource ID 139 received from the cloud device registration service 102 and the JWT 141 generated by the multifunctional peripheral device 101.

[0043] When the cloud device registration service 102 receives the access token request 124, it verifies the generated Nonce 140 and the JWT 141 received from the multifunctional peripheral device 101 to authenticate the multifunctional peripheral device 101. The cloud device registration service 102 generates an access token 142 based on the print service resource ID 139 included in the access token request 124 and sends an access token response 125 to the multifunctional peripheral device 101. The access token response 125 includes the access token 142.

[0044] So far, the cloud device registration process of the multifunctional peripheral device 101 is completed.

[0045] Next, the Figure 2 . Figure 2 is the cloud printing start sequence diagram of the multifunctional peripheral device. The description is given based on the following assumptions: The communication of this sequence uses the Internet Printing Protocol (IPP), which is a printing protocol using HTTP.

[0046] The multifunctional peripheral device 101 sends a printer information sending request 210 to the cloud printing service 200. The IPP operation is Update-Output-Device-Attributes. The printer information sending request 210 includes printer information 220. The printer information 220 is information represented by printer-description, which is an attribute group of IPP.

[0047] The multifunctional peripheral device 101 sends a job information sending request 211 to the cloud printing service 200. The IPP operation is Update-Active-Job. The job information sending request 211 includes job information 221. The job information 221 includes a job-id (job ID) and an output-device-job-state as IPP attributes. The job ID indicates the ID of the job, and the output device job state indicates the state of the job.

[0048] The multifunctional peripheral device 101 sends an event notification registration request 212 to the cloud printing event notification service 201. The IPP operation is Create-Printer-Subscription. The event notification registration request 212 includes a job reception event 222 indicating the type of event to be notified. The job reception event 222 includes a job-fetchable as an IPP attribute. The job-fetchable is an event type indicating that there is a job receivable in the cloud printing service.

[0049] The multifunctional peripheral device 101 sends an event acquisition request 213 to the cloud printing event notification service 201. The IPP operation is Get-Notifications. The event acquisition request 213 includes the job reception event 222 as the type of event to be acquired. The job reception event 222 includes a job-fetchable as an IPP attribute.

[0050] Next, the Figure 3 . Figure 3 is a sequence diagram of cloud printing type printing of the multifunctional peripheral device. The description is given based on the following assumption: The communication of the multifunctional peripheral device 101 in this sequence uses IPP, and IPP is a printing protocol using HTTP.

[0051] The client terminal 100 sends a cloud printer information request 300 to the cloud printing service 200. The cloud printer information request 300 includes a cloud account 133. When the cloud printing service 200 receives the cloud printer information request 300, it sends a cloud printer information response 301 to the client terminal 100. The cloud printer information response 301 includes a cloud printer ID 320 allowed to be used by the cloud account 133 and printer attributes 321 indicating the capabilities of the printer.

[0052] In response to a user's printing operation, the client terminal 100 sends a print request 302 to the cloud printing service 200. The print request 302 includes a cloud printer ID 320 for specifying the printer, print data 322, and a cloud account 133 for specifying the user.

[0053] When the Cloud Print Event Notification Service 201 detects that a print job addressed to the multifunction peripheral device 101 has been generated in the Cloud Print Service 200, it sends an event response 303 to the multifunction peripheral device 101. The event response 303 includes a job reception event 323 as the event type. The IPP operation is Get-NotificationsResponse. The job reception event 323 includes that the job is retrievable as an IPP attribute.

[0054] When the multifunction peripheral device 101 receives the event response 303, it sends a print job request 304 to the Cloud Print Service 200. The IPP operation is Get-Jobs.

[0055] When the Cloud Print Service 200 receives the print job request 304, it sends a print job response 305 to the multifunction peripheral device 101. The IPP operation is Get-Job Response. The print job response 305 includes a job ID 324 indicating the downloadable job.

[0056] When the multifunction peripheral device 101 receives the print job response 305, it sends a print job attribute request 306 to the Cloud Print Service 200. The IPP operation is Fetch Job. The print job attribute request 306 includes the job ID 324 specifying the target job.

[0057] When receiving the print job attribute request 306, the Cloud Print Service 200 sends a print job attribute response 307 to the multifunction peripheral device 101. The IPP operation is Fetch-Job Response. The print job attribute response 307 includes job attributes 325 of the job ID 324. The job attributes 325 are information represented by Job-Template-attributes as an IPP attribute group.

[0058] When the multifunction peripheral device 101 receives the print job attribute response 307, it sends a print job data request 308 to the Cloud Print Service 200. The IPP operation is Fetch-Document. The print job data request 308 includes the job ID 324 specifying the target job.

[0059] When the Cloud Print Service 200 receives the print job data request 308, it sends a print job data response 309 to the multifunction peripheral device 101. The IPP operation is Fetch-Document Response. The print job data response 309 includes job data 326 of the job ID 324.

[0060] So far, the operation sequence of cloud printing has been described. In the following, the local scanning function of the multifunctional peripheral device will be described.

[0061] Figure 4 It is a scan sequence diagram of the local scanning function of the multifunctional peripheral device. The description is given based on the following assumptions: The communication of the multifunctional peripheral device 101 in this sequence uses eSCL, and eSCL is a scanning protocol using HTTP.

[0062] The client terminal 100 sends a scanner capabilities request 410 to the multifunctional peripheral device 101. The eSCL operation is ScannerCapabilities (scanner capabilities). When the multifunctional peripheral device 101 receives the capabilities request 410, it sends a scanner capabilities response 411 to the client terminal 100. The eSCL operation is ScannerCapabilities Response (scanner capabilities response). The scanner capabilities response 411 includes scanner attributes 430. The scanner attributes 430 are information indicating the capabilities of the scanner represented in XML.

[0063] The client terminal 100 sends a scanner status request 412 to the multifunctional peripheral device 101. The eSCL operation is ScannerStatus (scanner status). When the multifunctional peripheral device 101 receives the scanner status request 412, it sends a scanner status response 413 to the client terminal 100. The eSCL operation is ScannerStatus Response (scanner status response). The scanner status response 413 includes scanner status 431. The scanner status 431 is information about the scanner status represented in XML.

[0064] The client terminal 100 sends a scan job generation request 414 to the multifunctional peripheral device 101. The eSCL operation is ScanJobs (scan job). The scan job generation request 414 includes scan job attributes 432. The scan job attributes 432 are information indicating the scan job attributes represented in XML. The information indicating the scan job attributes also includes the destination information of the job scanned by the multifunctional peripheral device 101. When the multifunctional peripheral device 101 receives the scan job generation request 414, it sends a scan job generation response 415 to the client terminal 100. The eSCL operation is ScanJobs Response (scan job response).

[0065] When the multifunctional peripheral device 101 receives a scan job generation request 414, it starts the scan process. The multifunctional peripheral device 101 sends a scan job transmission request 416 to the scan data transmission destination 400. The scan job transmission request 416 includes scan data 433 scanned by the multifunctional peripheral device 101. The scan data transmission destination 400 is specified from the client terminal 100 in the form included in the scan job attributes 432. Note that the protocol determined between the scan job transmission request 416 and the scan data transmission destination 400 is used for the scan job transmission requirement 416. eSCL is not necessarily used.

[0066] The client terminal 100 sends a scan job status request 417 to the multifunctional peripheral device 101. The eSCL operation is the scanner status. When the multifunctional peripheral device 101 receives the scan job status request 417, it sends a scan job status response 418 to the client terminal 100. The eSCL operation is the ScannerStatus Response. The scan job status response 418 includes information indicating the status of the scan job in a format represented by XML.

[0067] When the scan data transmission destination 400 receives the scan data 433 through the scan job transmission request 416, it sends a scan job transmission response 419 to the multifunctional peripheral device 101.

[0068] The client terminal 100 periodically sends a scan job status request 420 to the multifunctional peripheral device 101. The eSCL operation is ScannerStatus. When the multifunctional peripheral device 101 receives the scan job status request 420, it sends a scan job status response 421 to the client terminal 100. Here, when the scan job transmission response 419 is received from the scan data transmission destination 400 and the transmission of the scan data is normally completed, the scan job status response 421 includes information indicating completion in a format represented by XML as the status of the scan job. Note that the protocol determined between the scan job transmission response 419 and the scan data transmission destination 400 is used for the scan job transmission response 419. eSCL is not necessarily used.

[0069] Next, with reference to Figure 5 The hardware configuration of the multifunctional peripheral device 101 according to the present invention will be described. The multifunctional peripheral device 101 includes a control unit 501, a printer 507, a scanner 509, and an operation panel 511. The control unit 501 includes a CPU 502, a RAM 503, a ROM 504, an HDD 514, a printer I / F 506, a scanner I / F 508, an operation panel I / F 510, and a network I / F 512. The blocks in the control unit 501 are connected by a system bus 505.

[0070] The control unit 501 including the CPU 502 controls the entire operation of the multifunctional peripheral device 101. The CPU 502 reads the control program stored in the ROM 504 into the RAM 503 and performs various types of control such as communication control. The RAM 503 serves as a temporary storage area such as the main memory and the work area for the CPU 502. The HDD 514 stores data, various programs, or various information tables.

[0071] The printer I / F 506 serves as an interface for outputting an image signal to the printer 507 (printer engine). The scanner I / F 508 serves as an interface for inputting the read image signal from the scanner 509 (scanner engine). The CPU 502 processes the image signal input from the scanner I / F 508 and outputs the processed image signal as a recording image signal to the printer I / F 506.

[0072] The operation panel I / F 510 connects the operation panel 511 and the control unit 501. The operation panel 511 includes a keyboard and a liquid crystal display unit having a touch panel function.

[0073] The network I / F 512 sends information to external terminals such as the client terminal 100 and the cloud printing service 200, or receives various types of information from external devices.

[0074] Will refer to Figure 6 The software configuration of the multifunctional peripheral device 101 will be described. It is achieved by the CPU 502 of the multifunctional peripheral device 101 reading the control program stored in the ROM 504 into the RAM 503 and executing these control programs. ​ Each functional unit shown. The software of the multifunctional peripheral device 101 includes an operation control unit 600, a cloud device registration control unit 601, a cloud printing type printing control unit 602, a cloud printing job information management unit 603, a cloud printing event control unit 604, a cloud printing device information management unit 605, a storage unit 606, an image processing unit 607, a printing processing unit 608, a scanning processing unit 609, a cloud scanning control unit 610, a cloud scanning job information management unit 611, a cloud scanning device information management unit 612, and a WebUI control unit 613.

[0075] The operation control unit 600 controls the operation panel 511. An operation menu is displayed on the operation panel 511 to wait for an instruction input from the user, the content of the received instruction is notified to another functional unit, and the instruction result is displayed on the operation panel 511.

[0076] The cloud device registration control unit 601 controls the process of registering the multifunctional peripheral device 101 into the cloud device registration service 102 in response to a request 110 for cloud device registration received from the client terminal 100.

[0077] The WebUI control unit 613 controls the display and input of Web content for receiving operations of the multifunction peripheral device 101 via the Web. As an example, in this example, the multifunction peripheral device 101 receives a request 110 for cloud device registration via the network.

[0078] The cloud printing type print control unit 602 transfers the job data 326 received from the cloud printing service 200 to the image processing unit 607 together with the print instruction according to the job attribute 325.

[0079] The image processing unit 607 performs a process of rendering a print job into image data for printing.

[0080] The print processing unit 608 performs a process of printing the image data rendered by the image processing unit 607.

[0081] The cloud printing job information management unit 603 manages the job information of the multifunction peripheral device 101 and notifies it to the cloud printing service 200.

[0082] The cloud printing event control unit 604 controls the event notification process between the multifunction peripheral device 101 and the cloud printing event notification service 201.

[0083] The cloud printing device information management unit 605 manages the printing device information of the multifunction peripheral device 101 and notifies it to the cloud printing service 200.

[0084] The scanning processing unit 609 controls the following process: scanning the original document set in the scanner of the multifunction peripheral device 101 and acquiring the original document as data.

[0085] The cloud scanning control unit 610 controls the process of performing scanning according to an instruction from the client terminal 100 and sending the generated data to the cloud scanning service 1100. The cloud scanning control unit 610 transfers the job data 326 received from the cloud scanning service 1100 to the image processing unit 607 together with the print instruction according to the job attribute 325.

[0086] The cloud scanning job information management unit 611 manages the cloud job information in the multifunction peripheral device 101 and the cloud scanning service 1100 and notifies the job information in response to a query from the client terminal 100.

[0087] The cloud scanning device information management unit 612 manages the scanning device information of the multifunction peripheral device 101 and notifies the scanning device information to the client terminal 100 and the cloud scanning service 1100.

[0088] The storage unit 606 stores specified data into the HDD 505 or the RAM 503 according to an instruction from another functional unit. The storage unit 606 reads the data stored in the RAM 503, the ROM 504, and the HDD 505. Examples of data managed by the storage unit 606 include print job data and scan job data.

[0089] will be referred to ​ The operation panel 511 of the multifunction peripheral 101 will be described. The operation panel 511 includes a display panel 705, arrow keys 706, an OK key 707, a numeric keypad 708, a monochrome button 709, a color button 710, a stop button 711, a menu button 712, and a status confirmation / cancel button 713. The display panel 705 is a display panel using an LCD or the like. The display panel 705 displays a copy button 701, a fax button 702, and a scan button 703.

[0090] The copy button 701 is a button operated when copying using the multifunction peripheral 101, and a copy operation screen is displayed on the display panel 705 by operating the copy button 701. The fax button 702 is a button operated when faxing using the multifunction peripheral 101, and a fax operation screen is displayed on the display panel 705 by operating the fax button 702. The scan button 703 is a button operated when scanning using the multifunction peripheral 101, and a scan operation screen is displayed on the display panel 705 by operating the scan button 703. The display panel 705 also displays a dialog box for exchanging with the user. In addition, in this example, a user login screen and a print job list display screen are displayed.

[0091] The numeric keypad 708 is used to input numbers and the like. The OK key 707 is used when determining the display content of the display panel 705. The arrow keys 706 are used when selecting a menu or the like displayed on the display panel 705. The monochrome button 709 and the color button 710 are used when performing monochrome copying and color copying, respectively. The stop button 711 is used when the process is stopped. The menu button 712 is used when displaying a menu screen for setting the multifunction peripheral 101. The status confirmation / cancel button 713 is used when confirming the status of the multifunction peripheral 101 (such as a list of print jobs received by the multifunction peripheral 101).

[0092] will be referred to ​Describe the hardware configuration of the cloud printing server according to the present invention. The cloud printing server is a server that processes cloud device registration service 102, cloud printing service 200, cloud scanning service 1100, and cloud printing event notification service 201. The cloud printing server includes a control unit 801, and the control unit 801 includes a CPU 802, a RAM 803, a ROM 804, an HDD 805, a system bus 806, and a network I / F 810. Modules in the control unit 801 are connected through the system bus 806.

[0093] The control unit 801 including the CPU 802 controls the operations of the entire services processed by the cloud printing server. The CPU 802 performs various types of controls such as communication control by reading control programs stored in the ROM 804 into the RAM 803 and executing these control programs. The RAM 803 serves as a temporary storage area such as a main memory and a work area for the CPU 802. The HDD 805 stores data, various programs, or various information tables. The network I / F 810 sends information to external terminals such as client terminals 100 and multifunctional peripherals 101, or receives various types of information from external devices.

[0094] Note that the cloud device registration service 102, the cloud printing service 200, the cloud scanning service 1100, and the cloud printing event notification service 201 can be services implemented by different servers. One service can be implemented by multiple servers. The cloud printing server can be one or more cloud printing servers, and when the cloud printing server is referred to as a server system, the cloud printing server refers to a device that includes one or more cloud printing servers and processes each service.

[0095] Will refer to ​ Describe the software configuration of the cloud printing server according to the present invention. The cloud device registration service 102, the cloud printing service 200, the cloud scanning service 1100, and the cloud printing event notification service 201 of the present invention are implemented through the software of the cloud printing server.

[0096] The software of the cloud printing server includes a cloud device registration control unit 901, a cloud printing style printing control unit 902, a cloud printing event control unit 903, a cloud printing job information management unit 904, a cloud printing device information management unit 905, a storage unit 906, a WebUI control unit 907, a cloud scanning control unit 908, a cloud scanning job information management unit 909, and a cloud scanning device information management unit 910. Each of the function units shown is implemented by reading control programs stored in the ROM 804 into the RAM 803 through the CPU 802 of the cloud printing server and executing these control programs. ​ The various function units shown.

[0097] The cloud printing server is connected to the multi-functional peripheral device 101 via a network to form a cloud printing system.

[0098] The cloud device registration control unit 901 controls the process of registering the multi-functional peripheral device 101 into the cloud device registration service 102.

[0099] The cloud printing type print control unit 902 controls the process of receiving a print request 302 from the client terminal 100 and sending the print data 322 included in the print request 302 to the multi-functional peripheral device 101.

[0100] In response to the event notification registration request 212 and the event acquisition request 213 from the multi-functional peripheral device 101, the cloud printing event control unit 903 controls the process of sending an event response 303 in response to the presence or absence of an event.

[0101] The cloud printing job information management unit 904 manages the information and status of print jobs.

[0102] The cloud printing device information management unit 905 manages the multiple multi-functional peripheral devices 101 registered in the cloud device registration service 102. Specifically, it stores and manages the print capability information of the multi-functional peripheral device corresponding to each multi-functional peripheral device 101 and the information of the print queue where the print job is spooled.

[0103] The storage unit 906 stores the specified data into the HDD 805 or the RAM 803 according to an instruction from another functional unit. The storage unit 906 reads the data stored in the RAM 803, the ROM 804, and the HDD 805. Examples of the data managed by the storage unit 906 include the print data 322, the event information, and the capability information of the registered multi-functional peripheral device 101.

[0104] The cloud scanning control unit 908 controls the process of receiving a scanning job sent from the multi-functional peripheral device 101 and sending the scanning job to the scanning data sending destination 400.

[0105] The cloud scanning job information management unit 909 manages the information and status of scanning jobs.

[0106] The cloud scanning device information management unit 910 manages the multiple multi-functional peripheral devices 101 registered in the cloud device registration service 102. Specifically, it stores and manages the scanning capability information of the multi-functional peripheral device corresponding to each multi-functional peripheral device 101.

[0107] Will refer to ​ Describe the cloud device registration sequence of the multi-functional peripheral device in this example.

[0108] The first half of the sequence before the multifunctional peripheral device 101 of this sequence receives the access token response 117 is exactly the same as the cloud printing registration sequence diagram of the multifunctional peripheral device described in ​ . Therefore, the description until the access token response 117 will be omitted here, and the description will start from the part where the registration request 118 is sent from the multifunctional peripheral device 101.

[0109] The multifunctional peripheral device 101 sends a registration request 118 to the cloud device registration service 102. The registration request 118 includes a device name 135 and a device type 136. The access token 134 is added to the HTTP header of the registration request 118. The device name 135 is the device name set in the multifunctional peripheral device 101. The device type 136 indicates the device type of the multifunctional peripheral device 101. As ​ shown, the value of the device type determined by whether the device is a printer, scanner, or multifunctional peripheral device is set. In this example, since the device is a multifunctional peripheral device, "printer, scanner" is set. This will be described later ​ .

[0110] When the cloud device registration service 102 receives the registration request 118, it determines whether the access token 134 is the token that the cloud device registration server 102 itself has already responded to with the access token response 117. This confirms whether the sent registration request is an authorized registration request. When the cloud device registration service 102 determines that the registration request 118 is an authorized registration request as the confirmation result, it sends a registration response 119 to the multifunctional peripheral device 101 and starts the registration process for this multifunctional peripheral device.

[0111] The multifunctional peripheral device 101 sends a registration status request 120 to the cloud device registration service 102. Similarly, in the registration status request 120, the access token 134 is added to the HTTP header.

[0112] When the cloud device registration service 102 receives the registration status request 120, it confirms the access token 134 in the same manner as when it receives the registration request 118. And when the cloud device registration service determines that the registration status request 120 is an authorized registration status request, it continues the following processing. When the registration is completed, the cloud device registration service 102 sends a registration status response 1010 to the multifunctional peripheral device 101. The registration status response 1010 includes a print service URL 1030, a scan service URL 1031, a notification service URL 1032, a print service resource ID 1033, and a scan service resource ID 1034. The print service URL 1030 is information indicating the endpoint of the cloud printing service. The scan service URL 1031 is information indicating the endpoint of the cloud scanning service 1100. The notification service URL 1032 is information indicating the endpoint of the cloud print event notification service. The print service resource ID 1033 is unique information generated by the cloud device registration service for obtaining an access token for using the print service. The scan service resource ID 1034 is unique information generated by the cloud device registration service for obtaining an access token for using the scan service. The print service resource ID 1033 and the scan service resource ID 1034 are examples of service identifiers for obtaining access tokens in the present invention.

[0113] Next, the multifunctional peripheral device 101 obtains an access token for using the cloud printing service 200.

[0114] The multifunctional peripheral device 101 sends a Nonce request 1011 to the cloud device registration service 102. When the cloud device registration service 102 receives the Nonce request 1011, it generates a Nonce 1035 and sends a Nonce response 1012 to the multifunctional peripheral device 101. The Nonce response 1012 includes the Nonce 1035.

[0115] When the multifunctional peripheral device 101 obtains the Nonce 1035 through the Nonce response 1012, it generates a JWT 1037. Then, the multifunctional peripheral device 101 sends an access token request 1013 to the cloud device registration service 102. The access token request 1013 includes the print service resource ID 1033 received from the cloud device registration service 102 and the JWT 1037 generated by the multifunctional peripheral device 101.

[0116] When the cloud printing server receives the access token request 1013, it verifies the generated Nonce 1035 and the JWT 1037 received from the multifunctional peripheral device 101 to authenticate the multifunctional peripheral device 101. The cloud device registration service 102 generates an access token 1038 based on the print service resource ID 1033 included in the access token request 1013 and sends an access token response 1014 to the multifunctional peripheral device 101. The access token response 1014 includes the access token 1038.

[0117] When the multifunctional peripheral device 101 communicates with the cloud printing service 200, the access token 1038 obtained here is used.

[0118] Next, the multifunctional peripheral device 101 obtains an access token for the cloud scanning service 1100.

[0119] The multifunctional peripheral device 101 sends a Nonce request 1015 to the cloud device registration service 102. When the cloud device registration service 102 receives the Nonce request 1015, it generates a Nonce 1039 and sends a Nonce response 1016 to the multifunctional peripheral device 101. The Nonce response 1016 includes the Nonce 1039.

[0120] When the multifunctional peripheral device 101 obtains the Nonce 1039 through the Nonce response 1016, it generates a JWT 1041. Then, the multifunctional peripheral device 101 sends an access token request 1017 to the cloud device registration service 102. The access token request 1017 includes the scan service resource ID 1034 received from the cloud device registration service 102 and the JWT 1041 generated by the multifunctional peripheral device 101.

[0121] When the cloud printing server receives the access token request 1017, it verifies the generated Nonce 1039 and the JWT 1041 received from the multifunctional peripheral device 101 to authenticate the multifunctional peripheral device 101. The cloud device registration service 102 generates an access token 1042 based on the scan service resource ID 1034 included in the access token request 1039 and sends an access token response 1018 to the multifunctional peripheral device 101. The access token response 1018 includes the access token 1042.

[0122] The access token 1042 obtained here is used when the multifunctional peripheral device 101 communicates with the cloud scanning service 1100.

[0123] Note that this example is described based on the following assumption: The cloud printing service 200 and the cloud scanning service 1100 use different access tokens from each other. Therefore, the Nonce request and the access token request are made twice. An embodiment in which the same access token is used in the cloud printing service 200 and the cloud scanning service 1100 can be adopted. In this case, the Nonce request and the access token request are made only once.

[0124] The startup sequence of the multifunction peripheral device in this example will be described with reference to ​ Describe the startup sequence of the multifunction peripheral device in this example.

[0125] The description will be given based on the following assumption: In this sequence, the multifunction peripheral device 101 communicates with the cloud printing service 200 and the cloud printing event notification service 201 using IPP, which is a printing protocol using HTTP. In the HTTP communication via IPP, the multifunction peripheral device 101 sets the access token 1038 for the printing service in the HTTP header. Therefore, the cloud printing service 200 and the cloud printing event notification service 201 authorize the request.

[0126] The description will be given based on the following assumption: The communication between the multifunction peripheral device 101 and the cloud scanning service 1100 uses eSCL, which is a scanning protocol using HTTP. In the HTTP communication via eSCL, the multifunction peripheral device 101 sets the access token 1042 for the scanning service in the HTTP header. Therefore, the cloud scanning service 1100 authorizes the request.

[0127] The multifunction peripheral device 101 sends a printer information sending request 1100 to the cloud printing service 200. The IPP operation is Update-Output-Device-Attributes (update output device attributes). The printer information sending request 1110 includes the printer information 220. The printer information 1110 is information represented by printer-description, which is an attribute group of IPP.

[0128] The multifunction peripheral device 101 sends a job information sending request 1101 to the cloud printing service 200. The IPP operation is Update-Active-Jobs (update active jobs). The job information sending request 1101 includes the job information 1111. The job information 1111 includes the job-id (job ID) and output-device-job-states (output device job state) as IPP attributes. The job ID indicates the ID of the job, and the output device job state indicates the state of the job.

[0129] The multifunctional peripheral device 101 sends an event notification registration request 1102 to the cloud printing event notification service 201. The IPP operation is Create-Printer-Subscription. The event notification registration request 1102 includes a job reception event 1112 indicating the type of event to be notified. The job reception event 1112 includes that the job is available as an IPP attribute. The job being available is an event type indicating that there is a job that can be received in the cloud printing service 200.

[0130] The multifunctional peripheral device 101 sends a scanner capabilities transmission 1104 to the cloud scanning service 1100. The eSCL operation is ScannerCapabilities. The scanner capabilities transmission 1104 includes scanner attributes 1113. The scanner attributes 1113 are information representing the capabilities of the scanner in XML.

[0131] The multifunctional peripheral device 101 sends a scanner status transmission 1105 to the cloud scanning service 1100. The eSCL operation is ScannerStatus. The scanner status transmission 1105 includes scanner status 1114. The scanner status 1114 is information representing the status of the scanner in XML.

[0132] ​ is the cloud printing-style printing sequence diagram of the multifunctional peripheral device in this example. The cloud printing-style printing sequence is exactly the same as that of ​ Therefore, the description will be omitted here. Note that in this sequence, it is assumed that the multifunctional peripheral device 101 communicates with the cloud printing service 200 and the cloud printing event notification service 201 using IPP, and IPP is a printing protocol using HTTP. In the HTTP communication through IPP, the multifunctional peripheral device 101 sets an access token 1038 for the printing service in the HTTP header. Therefore, the cloud printing service 200 and the cloud printing event notification service 201 authorize the request.

[0133] Refer to ​ to describe the scanning sequence of cloud scanning of the multifunctional peripheral device in this example. The description will be given based on the following assumption: In this sequence, the communication between the multifunctional peripheral device 101 and the cloud scanning service 1100 uses eSCL, and eSCL is a scanning protocol using HTTP. In the HTTP communication through eSCL, the multifunctional peripheral device 101 sets an access token 1042 for the scanning service in the HTTP header. Therefore, the cloud scanning service 1100 authorizes the request.

[0134] The first half of the sequence before the multifunctional peripheral device 101 of this sequence sends a scan job generation response 415 is the same as that of ​The scanning sequence diagram of the local scanning function of the multifunctional peripheral device described in [reference] is exactly the same. Therefore, the description until the generation of the scan job response 415 will be omitted here, and the description will start from the part where the scan job generation request 1310 is sent from the multifunctional peripheral device 101.

[0135] The multifunctional peripheral device 101 sends a scan job generation request 1310 to the cloud scanning service 1100. The eSCL operation is ScanJobs (scan job). The scan job generation request 1310 may include scan job attributes 432 sent from the client terminal 100.

[0136] When the cloud scanning service 1100 receives the scan job generation request 1310, it generates a scan job and sends a scan job generation response 1311 to the multifunctional peripheral device 101. The eSCL operation is ScanJobs Response (scan job response). The scan job generation response 1311 includes a scan job ID 433.

[0137] The multifunctional peripheral device 101 sends a scan job send request 1312 to the cloud scanning service 1100. The eSCL operation is ScanJobs (scan job). The scan job send request 1312 includes scan data 434.

[0138] When the cloud scanning service 1100 receives the scan job send request 1312, it saves the scan data in the storage area and sends a scan job send response 1313 to the multifunctional peripheral device 101. The eSCL operation is ScanJobsResponse (scan job response).

[0139] The cloud scanning service 1100 sends a scan job send 1314 to the scan data destination 400. The scan job send 1314 includes scan data 434. Note that the protocol determined between the scan job send 1314 and the scan data destination 400 is used for the scan job send 1312. eSCL is not necessarily used.

[0140] When the scan data destination 400 receives the scan job send 1314, it sends a scan job send response 1317 to the cloud scanning service 1100. Note that the protocol determined between the scan job send response 1317 and the scan data destination 400 is used for the scan job send response 1317. eSCL is not necessarily used.

[0141] The multifunctional peripheral device 101 sends a scan job status request 1315 to the cloud scanning service 1100 to confirm the status of the scan job. The eSCL operation is ScannerStatus (scanner status).

[0142] When the cloud scanning service 1100 receives the scan job status request 1315, it sends a scan job status response 1316 to the multifunctional peripheral device 101. The eSCL operation is ScannerStatus Response.

[0143] Repeat the scan job status response 1316 until the scan job transitions to a final state.

[0144] The client terminal 100 sends a scan job status request 417 to the multifunctional peripheral device 101 to confirm the status of the scan job. The eSCL operation is ScannerStatus.

[0145] When the multifunctional peripheral device 101 receives the scan job status request 417, it sends a scan job status response 418 to the client terminal 100. The eSCL operation is ScannerStatus Response.

[0146] Repeat the scan job status response 418 until the scan job transitions to a final state.

[0147] Refer to ​ , which will describe the device type sent by the multifunctional peripheral device in this example during cloud device registration. The device type described here is the device type set for the registration request 118 in the cloud device registration sequence diagram described in ​

[0148] Examples of the device type 1411 include printers, scanners, and multifunctional peripheral devices. The multifunctional peripheral device 101 selects the device type according to the service to be registered in the cloud device registration service.

[0149] In the case of registering as a printer with cloud printing function, set "printer" as the value of the device type. In the case of registering as a scanner with cloud scanning function, set "scanner" as the value of the device type. In the case of registering as a multifunctional peripheral device with both cloud printing function and cloud scanning function, set "printer, scanner" as the value of the device type.

[0150] In the case of a multifunctional peripheral device, the value of the device type can be set to "MFP". In this case, assuming there is a cloud printing service 200 and a cloud scanning service 1100, the cloud device registration service 102 controls the registered device.

[0151] Refer to ​Describe the process of cloud device registration processing for the multifunctional peripheral device in this example. For example, the following processing is implemented by the CPU 502 of the multifunctional peripheral device 101 reading the program stored in the ROM 504 into the RAM 503 and executing the program. In the following, the step numbers of the respective processes included in the flowchart are represented by numbers starting with "S". This also applies to subsequent flowcharts.

[0152] Receive from the client terminal 100 by the multifunctional peripheral device 101 ​ The request 110 for cloud device registration described in and start this flowchart.

[0153] In S1500, the cloud device registration control unit 601 of the multifunctional peripheral device 101 acquires the device code. This is a process implemented by ​ the device code generation request 111 and the device code generation response 112.

[0154] In S1501, the cloud device registration control unit 601 of the multifunctional peripheral device 101 acquires the access token for registration. This is a process implemented by ​ the access token request 116 and the access token response 117.

[0155] In S1502, the cloud device registration control unit 601 of the multifunctional peripheral device 101 determines the type of the device. If the device type is a printer, the process proceeds to S1503, sets "printer" as the device type, and the process proceeds to S1506. If the device type is a scanner, the process proceeds to S1504, sets "scanner" as the device type, and the process proceeds to S1506. If the device type is a multifunctional peripheral device, the process proceeds to S1505, sets "printer, scanner" as the device type, and the process proceeds to S1506.

[0156] In S1506, the cloud device registration control unit 601 of the multifunctional peripheral device 101 performs the cloud device registration process. This is a process implemented by ​ the registration request 118, the registration response 119, the registration status request 120, and the registration status response 1010. The information sent in the registration request 118 also includes the device type generated in S1503, S1504, or S1505.

[0157] When the cloud device registration process of S1506 is completed, the cloud device registration control unit 601 of the multifunction peripheral device 101 proceeds to S1507 and performs the access token acquisition process. First, in S1507, the type of the device is determined. If the type of the device is a printer, the process proceeds to S1508 to acquire an access token for the printing service. If the type of the device is a scanner, the process proceeds to S1509 to acquire an access token for the scanning service.

[0158] If the type of the device is a multifunction peripheral device, the process proceeds to S1510, and first an access token for the printing service is acquired, and the process proceeds to S1511. In S1511, an access token for the scanning service is acquired.

[0159] When the cloud device registration control unit of the multifunction peripheral device 101 acquires an access token in S1508 to S1511, the process proceeds to S1512. In S1512, the cloud device registration control unit 601 of the multifunction peripheral device 101 saves the acquired access token to the storage unit 606.

[0160] Reference will be made to ​ Describe the processing flow when the cloud device registration service 102 of the cloud printing server in this example receives a registration request. For example, the following processing is implemented by the CPU 802 of the cloud printing server reading the program stored in the ROM 804 into the RAM 803 and executing the program.

[0161] When the cloud device registration service 102 receives the registration request 118 described with reference to ​ from the multifunction peripheral device 101, this flowchart starts.

[0162] In S1600, the cloud device registration control unit 901 of the cloud device registration service 102 analyzes the message of the registration request 118, and sends a registration response 119 indicating the receipt of the registration, and the process proceeds to S1601.

[0163] In S1601, the cloud device registration control unit 901 of the cloud device registration service 102 reads the device type included in the message of the registration request 118, and the process proceeds to S1602.

[0164] In S1602, the cloud device registration control unit 901 of the cloud device registration service 102 determines the value set for the device type read in S1601.

[0165] If the value of the device type indicates a printer in S1602, the process proceeds to S1603. In S1603, the cloud printing device information management department 905 of the cloud device registration service 102 adds the device that has sent the registration request as a device that can be used in the cloud printing service 200, and the process proceeds to S1604.

[0166] In S1604, the cloud printing event control department 903 of the cloud device registration service 102 adds the device that has sent the registration request as a device for event notification in the cloud printing event notification service 201, and the process proceeds to S1605.

[0167] In S1605, the cloud printing event control department 903 of the cloud device registration service 102 generates a print service resource ID 1033, and the process proceeds to S1613.

[0168] If the value of the device type indicates a scanner in S1602, the process proceeds to S1606. In S1606, the cloud printing device information management department 905 of the cloud device registration service 102 adds the device that has sent the registration request as a device that can be used in the cloud scanning service 1100, and the process proceeds to S1607.

[0169] In S1607, the cloud printing event control department 903 of the cloud device registration service 102 generates a scanning service resource ID 1034, and the process proceeds to S1613.

[0170] If the value of the device type indicates a multifunction peripheral in S1602, the process proceeds to S1608. In S1608, the cloud printing device information management department 905 of the cloud device registration service 102 adds the device that has sent the registration request as a device that can be used in the cloud printing service 200, and the process proceeds to S1609.

[0171] In S1609, the cloud printing event control department 903 of the cloud device registration service 102 adds the device that has sent the registration request as a device for event notification in the cloud printing event notification service 201, and the process proceeds to S1610.

[0172] In S1610, the cloud printing event control department 903 of the cloud device registration service 102 generates a print service resource ID 1033, and the process proceeds to S1611.

[0173] In S1611, the cloud printing device information management department 905 of the cloud device registration service 102 adds the device that has sent the registration request as a device that can be used in the cloud scanning service 1100, and the process proceeds to S1612.

[0174] In S1612, the cloud printing event control unit 903 of the cloud device registration service 102 generates a scan service resource ID 1034, and the process proceeds to S1613.

[0175] In S1613, the cloud device registration control unit 901 of the cloud device registration service 102 receives a registration status request 120 from the multifunction peripheral 101, and the process proceeds to S1614.

[0176] In S1614, the cloud device registration control unit 901 of the cloud device registration service 102 sends a registration status response 1010 to the multifunction peripheral 101. The following data is set in the registration status response 1010 according to the device type.

[0177] If the device type is a printer, a print service URL 1030, a notification service URL 1032, and a print service resource ID 1033 are set.

[0178] If the device type is a scanner, a scan service URL 1031 and a scan service resource ID 1034 are set.

[0179] When the device type is a multifunction peripheral, a print service URL 1030, a scan service URL 1031, a notification service URL 1032, a print service resource ID 1033, and a scan service resource ID 1034 are set.

[0180] Other embodiments

[0181] Embodiments of the present invention can also be implemented by a computer of a system or device that reads and executes computer-executable instructions (e.g., one or more programs) recorded on a storage medium (which may also be more fully referred to as a "non-transitory computer-readable storage medium") to perform one or more functions of the above-described embodiments, and / or includes one or more circuits (e.g., an application-specific integrated circuit (ASIC)) for performing one or more functions of the above-described embodiments. Moreover, embodiments of the present invention can be implemented by a method in which the computer of the system or device, for example, reads and executes the computer-executable instructions from the storage medium to perform one or more functions of the above-described embodiments, and / or controls the one or more circuits to perform one or more functions of the above-described embodiments. The computer may include one or more processors (e.g., a central processing unit (CPU), a microprocessing unit (MPU)), and may include a network of separate computers or separate processors to read and execute the computer-executable instructions. The computer-executable instructions may be provided to the computer, for example, from a network or the storage medium. The storage medium may include, for example, a hard disk, a random access memory (RAM), a read-only memory (ROM), the memory of a distributed computing system, an optical disc (such as a compact disc (CD), a digital versatile disc (DVD), or a Blu-ray disc (BD) TM ), a flash device, and a memory card, among others.

[0182] Embodiments of the present invention can also be implemented by the following method, that is, by providing software (including a computer program product of computer programs / instructions) that performs the functions of the above-described embodiments to a system or device through a network or various storage media, and the computer (central processing unit (CPU), microprocessing unit (MPU)) of the system or device reads and executes the computer program / instructions.

[0183] Although the present invention has been described with reference to exemplary embodiments, it should be understood that the present invention is not limited to the disclosed exemplary embodiments. The scope of the appended claims should be given the broadest interpretation so as to cover all such variations and equivalent structures and functions.

Claims

1. An apparatus for cloud printing, which is connected to a cloud printing server system via a network, the cloud printing server system processing cloud printing services and cloud scanning services, the apparatus for cloud printing comprising: a sending unit configured to send a registration request to the cloud printing server system, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; a receiving unit configured to receive from the cloud printing server system a service identifier and endpoint information indicating an endpoint, the service identifier being used to obtain an access token corresponding to the device type included in the registration request; an obtaining unit configured to send the service identifier to the cloud printing server system and obtain from the cloud printing server system an access token used in a service corresponding to the device type; and a communication unit configured to communicate with the endpoint by using the access token when executing the service.

2. The apparatus for cloud printing according to claim 1, wherein communication with the cloud printing server system is performed via the Internet Printing Protocol or eSCL.

3. The apparatus for cloud printing according to claim 1, wherein the access token corresponding to each of the cloud printing service and the cloud scanning service is generated.

4. The apparatus for cloud printing according to claim 1, wherein the device type includes a multifunction peripheral, and when the device type is a multifunction peripheral, the device type indicates that the apparatus for cloud printing includes a cloud printing function and a cloud scanning function.

5. A control method for an apparatus for cloud printing, the apparatus for cloud printing being connected to a cloud printing server system via a network, the cloud printing server system processing cloud printing services and cloud scanning services, the control method comprising the following steps: sending a registration request to the cloud printing server system that processes cloud printing services and cloud scanning services, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; receiving from the cloud printing server system a service identifier and endpoint information indicating an endpoint, the service identifier being used to obtain an access token corresponding to the device type included in the registration request; sending the service identifier to the cloud printing server system and obtaining from the cloud printing server system an access token used in a service corresponding to the device type; and communicating with the endpoint by using the access token when executing the service.

6. A non-transitory computer-readable storage medium storing a program for causing a computer to execute each step of the control method for an apparatus for cloud printing, the apparatus for cloud printing being connected to a cloud printing server system via a network, the cloud printing server system processing cloud printing services and cloud scanning services, the control method comprising the following steps: sending a registration request to the cloud printing server system that processes cloud printing services and cloud scanning services, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; Receiving a service identifier and endpoint information indicating an endpoint from the cloud printing server system, the service identifier being used to obtain an access token corresponding to the device type included in the registration request; Sending the service identifier to the cloud printing server system and obtaining an access token used in the service corresponding to the device type from the cloud printing server system; And Communicating with the endpoint by using the access token when executing the service.

7. A computer program product comprising a program for causing a computer to execute the respective steps of a control method for a cloud printing device, the cloud printing device being connected to a cloud printing server system via a network, the cloud printing server system processing cloud printing services and cloud scanning services, the control method comprising the following steps: Sending a registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function to the cloud printing server system that processes cloud printing services and cloud scanning services; Receiving a service identifier and endpoint information indicating an endpoint from the cloud printing server system, the service identifier being used to obtain an access token corresponding to the device type included in the registration request; Sending the service identifier to the cloud printing server system and obtaining an access token used in the service corresponding to the device type from the cloud printing server system; And Communicating with the endpoint by using the access token when executing the service.

8. A cloud printing server system that processes cloud printing services and cloud scanning services for a device, the cloud printing server system comprising: A receiving unit configured to receive a registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function from the device; A sending unit configured to send a service identifier and endpoint information indicating an endpoint to the device, the service identifier being used to obtain an access token corresponding to the device type; And An access token generation unit configured to generate an access token corresponding to the service identifier and send the access token corresponding to the service identifier to the device when receiving a request for obtaining an access token including the service identifier from the device.

9. A control method for a cloud printing server system that processes cloud printing services and cloud scanning services for a device, the control method comprising: Receiving a registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function from the device; Sending a service identifier and endpoint information indicating an endpoint to the device, the service identifier being used to obtain an access token corresponding to the device type; And Generating an access token corresponding to the service identifier and sending the access token corresponding to the service identifier to the device when receiving a request for obtaining an access token including the service identifier from the device.

10. A non - transitory computer - readable storage medium stores a program for causing a computer to execute each step of a control method of a cloud printing server system, where the cloud printing server system processes cloud printing services and cloud scanning services, and the control method includes the following steps: Receiving a registration request for at least one of the cloud printing service and the cloud scanning service from the device, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; Sending a service identifier and endpoint information indicating an endpoint to the device, where the service identifier is used to obtain an access token corresponding to the device type; And When receiving a request for obtaining an access token including the service identifier from the device, generating an access token corresponding to the service identifier and sending the access token corresponding to the service identifier to the device.

11. A computer program product includes a program for causing a computer to execute each step of a control method of a cloud printing server system, where the cloud printing server system processes cloud printing services and cloud scanning services, and the control method includes the following steps: Receiving a registration request for at least one of the cloud printing service and the cloud scanning service from the device, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; Sending a service identifier and endpoint information indicating an endpoint to the device, where the service identifier is used to obtain an access token corresponding to the device type; And When receiving a request for obtaining an access token including the service identifier from the device, generating an access token corresponding to the service identifier and sending the access token corresponding to the service identifier to the device.

12. A cloud printing system includes a device and a cloud printing server system. The cloud printing server system processes cloud printing services and cloud scanning services for the device. The device includes: A first sending unit configured to send a registration request to the cloud printing server system, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function; A first receiving unit configured to receive a service identifier and endpoint information indicating an endpoint from the cloud printing server system, where the service identifier is used to obtain an access token corresponding to the device type included in the registration request; An obtaining unit configured to send the service identifier to the cloud printing server system and obtain an access token corresponding to the device type from the cloud printing server system; And A communication unit configured to communicate with the endpoint by using the access token when performing a cloud printing service or a cloud scanning service. The cloud printing server system includes: A second receiving unit configured to receive a registration request from the device; A second sending unit configured to send a service identifier and endpoint information indicating an endpoint to the device, where the service identifier is used to obtain an access token corresponding to the device type; and An access token generation unit, configured to generate an access token corresponding to the service identifier and send the access token corresponding to the service identifier to the device when receiving a request for obtaining an access token from the device.

13. A control method of a cloud printing system, the cloud printing system including a device; and a cloud printing server system, the cloud printing server system processing cloud printing services and cloud scanning services for the device, wherein, the device sends a registration request to the cloud printing server system, the registration request including a device type indicating at least one of a cloud printing function and a cloud scanning function, the cloud printing server system receives the registration request from the device and sends a service identifier and endpoint information indicating an endpoint to the device, the service identifier being used to obtain an access token corresponding to the device type, the device receives the service identifier and the endpoint information from the cloud printing server system, the device sends the service identifier to the cloud printing server system, the cloud printing server system, when receiving the service identifier from the device, generates an access token corresponding to the service identifier and sends the access token corresponding to the service identifier to the device, the device obtains the access token from the cloud printing server system, and the device communicates with the endpoint by using the access token when performing a cloud printing service or a cloud scanning service.

Images