Systems, servers, server programs, electronic devices and device programs

Abstract

To provide a system capable of reducing a workload of associating a tenant in a multi-tenant type cloud service with an electronic device using the tenant, a server, a program for the server, an electronic device, and a program for the device.SOLUTION: A cloud server assigns a customer site 22 as a tenant with an organization number of the customer site 22 (S107-S108) and notifies a customer administrator of that effect. An MFP causes the organization number input by the customer administrator to be notified of and makes an inquiry to the cloud server about a subdirectory name of the customer site 22. The cloud server notifies the MFP of the subdirectory name associated with the notified organization number. The MFP notifies the customer site 22 accessed using the notified subdirectory name, of a serial number of the MFP. The customer site 22 manages the notified serial number.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present invention relates to a system, a server, a server program, an electronic device, and a device program in a multi-tenant cloud service. [Background technology]

[0002] BACKGROUND ART Conventionally, a distributed pull-print image forming system that does not require a server has been known (see, for example, Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-181573 Summary of the Invention [Problem to be solved by the invention]

[0004] However, conventional technologies cannot be applied to cloud-based pull printing, in which a computer such as a PC (Personal Computer) stores print job data (hereinafter referred to as "print job data") in a tenant in a multi-tenant cloud service, and then an image forming device associated with the tenant performs printing based on the print job data.

[0005] Not only in cloud-based pull printing, but also in multi-tenant cloud services, there are cases where it is necessary to associate a tenant with an electronic device that uses this tenant.

[0006] Therefore, the present invention aims to provide a system, a server, a server program, an electronic device, and a device program that can reduce the workload of associating tenants in a multi-tenant cloud service with electronic devices that use those tenants. [Means for solving the problem]

[0007] The system of the present invention includes a multi-tenant cloud server and electronic devices that use tenants of the cloud server, wherein the cloud server assigns tenant identification information to the tenant as identification information for the tenant and notifies the user of the assigned tenant identification information, the electronic device queries the cloud server for access information for accessing the tenant by notifying the cloud server of the tenant identification information entered by the user, the cloud server notifies the electronic device of the access information associated with the tenant identification information notified by the electronic device, the electronic device accesses the tenant using the access information notified by the cloud server and notifies the tenant that has accessed the tenant of device identification information as identification information for the electronic device, and the tenant manages the device identification information notified by the electronic device.

[0008] The server of the present invention is a multi-tenant server that assigns tenant identification information to a tenant as identification information for the tenant of the server, notifies a user of the assigned tenant identification information, notifies the electronic device of access information for accessing the tenant that is associated with the tenant identification information notified from an electronic device using the tenant, and the tenant manages the device identification information notified from the electronic device.

[0009] The server program of the present invention is a server program executed by a multi-tenant cloud server, which causes the cloud server to assign tenant identification information as identification information for the tenant of the cloud server to the tenant, causes the cloud server to notify the user of the tenant identification information assigned by the cloud server, causes the electronic device to notify the cloud server of access information for accessing the tenant that is associated with the tenant identification information notified to the cloud server from an electronic device using the tenant, and causes the tenant to manage the device identification information notified to the tenant from the electronic device.

[0010] The electronic device of the present invention is an electronic device that uses a tenant of a multi-tenant cloud server, and is characterized in that it queries the cloud server for access information for accessing the tenant by notifying the cloud server of tenant identification information input by a user as identification information for the tenant, accesses the tenant using the access information notified by the cloud server, and notifies the accessed tenant of device identification information as identification information for the electronic device.

[0011] The device program of the present invention is a device program executed by an electronic device that uses a tenant of a multi-tenant cloud server, and is characterized in that it causes the electronic device to notify the cloud server of tenant identification information as identification information of the tenant input into the electronic device by a user, thereby causing the electronic device to query the cloud server for access information for accessing the tenant, allows the tenant to access the electronic device using the access information notified to the electronic device from the cloud server, and notifies the electronic device of device identification information as identification information of the electronic device to the tenant that has accessed the electronic device. [Effects of the Invention]

[0012] The system, server, server program, electronic device, and device program of the present invention can reduce the workload of associating tenants in a multi-tenant cloud service with electronic devices that use these tenants. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a block diagram of a system according to a first embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating an example of a device management database illustrated in FIG. [Figure 3] FIG. 2 is a diagram showing an example of an organization management database shown in FIG. [Figure 4] FIG. 2 is a block diagram of the MFP shown in FIG. [Figure 5] FIG. 2 is a sequence diagram of the operation of the system shown in FIG. 1 when registering a customer. [Figure 6] FIG. 4 is a diagram showing an example of the organization management database shown in FIG. 3 immediately after a customer is registered. [Figure 7] 10 is a sequence diagram of the operation of the system shown in FIG. 1 when an administrator PIN is registered in the organization management database. [Figure 8] 1 when a customer administrator refers to an organization number. FIG. [Figure 9] 1 when the MFP itself checks the customer site where the MFP is registered. [Figure 10] 10 is a sequence diagram of an example of the operation of the system shown in FIG. 1 when an MFP is registered at a customer site. [Figure 11] FIG. 11 is a sequence diagram of an example of the operation of the system when registering an MFP at a customer site, which is different from the example shown in FIG. 10. [Figure 12] 12 is a diagram showing an example of a portion of a device management permission request email sent in the operation shown in FIG. 11. FIG. [Figure 13]FIG. 12 is a sequence diagram of an example of the operation of the system when registering an MFP at a customer site, which is different from the examples shown in FIGS. 10 and 11. [Figure 14] FIG. 10 is a block diagram of a system according to a second embodiment of the present invention. [Figure 15] FIG. 15 is a diagram showing an example of an organization management database shown in FIG. 14. [Figure 16] FIG. 15 is a sequence diagram of the operation of the system shown in FIG. 14 when registering a customer. [Figure 17] FIG. 15 is a sequence diagram of an example of the operation of the system shown in FIG. 14 when an MFP is registered at a customer site. [Figure 18] 15 is a flowchart of the operation of the cloud server shown in FIG. 14 when deleting a reservation number whose expiration date has passed. DETAILED DESCRIPTION OF THE INVENTION

[0014] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0015] (First embodiment) First, the configuration of a system according to a first embodiment of the present invention will be described.

[0016] FIG. 1 is a block diagram of a system 10 according to the present embodiment.

[0017] As shown in Fig. 1, a system 10 that realizes a multi-tenant cloud service includes a multi-tenant cloud server 20 and an MFP (Multifunction Peripheral) 30 as an electronic device managed by the cloud server 20. The system 10 may include one or more MFPs with a configuration similar to that of the MFP 30 in addition to the MFP 30. The system 10 is located in, for example, Japan. Note that systems with a configuration similar to that of the system 10 may also be located in specific regions, such as the United States and Europe.

[0018] The cloud server 20 may be configured by one computer or by multiple computers.

[0019] The tenants of cloud server 20 include provider site 21, which is a tenant for the provider that provides the MFP, and customer site 22, which is a tenant for the customer that provides the MFP. Cloud server 20 can have one or more provider sites other than provider site 21 that have a similar configuration to provider site 21. A provider site in cloud server 20 exists for each provider. Cloud server 20 can have one or more customer sites other than customer site 22 that have a similar configuration to customer site 22. A customer site in cloud server 20 exists for each customer.

[0020] A provider can manage multiple customers. A provider site manages the customer sites of the customers managed by the provider that corresponds to it. An administrator belongs to a provider. Hereinafter, an administrator who belongs to a provider will be referred to as a "provider administrator."

[0021] Each customer in system 10 is managed by only one provider. A customer can manage multiple MFPs. A customer site manages the MFPs managed by its corresponding customer. MFP users belong to a customer. An administrator belongs to a customer. Hereinafter, an administrator belonging to a customer will be referred to as a "customer administrator."

[0022] Each MFP in system 10 is managed by only one customer.

[0023] The customer site 22 has a device management database 22 a that indicates the MFPs that the customer site 22 manages.

[0024] FIG. 2 is a diagram showing an example of the device management database 22a.

[0025] As shown in FIG. 2, the device management database 22a indicates, for each MFP managed by the customer site 22, for example, the serial number, IP (Internet Protocol) address, host name, and the like.

[0026] The serial number is, for example, a 10-digit alphanumeric code. The serial number of an MFP is unique and differs for each MFP. The serial number is identification information for the MFP and constitutes device identification information.

[0027] The cloud server 20 shown in FIG. 1 can provide cloud-based pull printing (hereinafter referred to as "cloud printing") and cloud-based scanning functions (hereinafter referred to as "cloud scanning"). Cloud printing is a function that allows an MFP user to save print job data from a computer such as a PC (not shown) to the customer site of the customer to which the user belongs, and then execute printing based on the print job data using an MFP associated with the customer site. Cloud scanning is a function that allows an MFP user to upload documents scanned by the MFP to the customer site associated with the MFP. Documents uploaded to the customer site by cloud scanning can be downloaded by a computer such as a PC (not shown).

[0028] The cloud server 20 includes a main control unit 23 that executes control such as searching for customer sites where MFPs are registered.

[0029] The cloud server 20 stores an organization management database 24 that manages customers.

[0030] FIG. 3 is a diagram showing an example of the organization management database 24. As shown in FIG.

[0031] As shown in Figure 3, the organization management database 24 manages, for each customer, an organization name indicating the customer's name, a subdirectory name as access information for accessing the customer site, an organization number indicating the customer's identification number, an administrator email address indicating the email address of the customer administrator, and an administrator PIN indicating the customer administrator's PIN (Personal Identification Number).

[0032] The organization name and subdirectory name each consist of a string of characters, for example, from 1 to 64 characters. The types of characters that can be included in the organization name and subdirectory name include, for example, alphanumeric characters and specific symbols. All organization names registered in the organization management database 24 are unique and different from one another. All organization names registered in the organization management database 24 are unique and different from one another.

[0033] The organization number is, for example, a six-digit number. All organization numbers registered in the organization management database 24 are unique and different from one another. The organization number is identification information for a customer site that is a tenant, and constitutes tenant identification information.

[0034] The administrator PIN is, for example, a four-digit number and is used to enter administrator mode on the MFP's device app (described later).

[0035] 1, cloud server 20 stores server program 25. Cloud server 20 executes server program 25 to realize the operations described below.

[0036] FIG. 4 is a block diagram of the MFP 30.

[0037] As shown in FIG. 4, the MFP 30 includes an operation unit 31, which is an operation device such as a button or an IC (Integrated Circuit) card reader through which various operations are input; a display unit 32, which is a display device such as an LCD (Liquid Crystal Display) that displays various information; a printer 33, which is a printing device that prints images on a recording medium such as paper; a scanner 34, which is a reading device that reads images from a document; a communication unit 35, which is a communication device that communicates with an external device via a network such as a LAN (Local Area Network) or the Internet, or directly via a wired or wireless connection without using a network; a fax communication unit 36, which is a fax device that communicates by fax with an external facsimile machine (not shown) via a communication line such as a public telephone line; a memory unit 37, which is a non-volatile memory device such as a semiconductor memory or an HDD (Hard Disk Drive) that stores various information; and a control unit 38 that controls the entire MFP 30.

[0038] The storage unit 37 stores a device application program 37a, which is an application program for implementing cloud printing and cloud scanning, as a device program. The device application program 37a may be installed on the MFP 30 during the manufacturing stage of the MFP 30, or may be additionally installed on the MFP 30 from an external storage medium such as a CD (Compact Disk), a DVD (Digital Versatile Disk), or a USB (Universal Serial Bus) memory, or may be additionally installed on the MFP 30 from a network.

[0039] The control unit 38 includes, for example, a CPU (Central Processing Unit), a ROM (Read Only Memory) that stores programs and various data, and a RAM (Random Access Memory) that serves as a working area for the CPU. The CPU executes programs stored in the storage unit 37 or the ROM.

[0040] The control unit 38 realizes a device application 38a by executing a device application program 37a stored in the storage unit 37. That is, the MFP 30 can use the customer site 22 of the cloud server 20 through cloud print and cloud scan.

[0041] The customer administrator can enter administrator mode on the device app 38a by entering an administrator PIN on the device app 38a. In administrator mode on the device app 38a, various network settings can be performed, such as proxy server settings, cloud server 20 domain settings, and customer site 22 subdirectory settings.

[0042] The operation of the system 10 will now be described.

[0043] First, the operation of the system 10 when registering a customer will be described.

[0044] FIG. 5 is a sequence diagram of the operation of the system 10 when registering a customer.

[0045] In the following description of the operation shown in FIG. 5, provider site 21 is shown as an example of the provider site of the provider to which the provider administrator belongs, and customer site 22 is shown as an example of the customer site of the customer registered by this provider administrator.

[0046] As shown in FIG. 5, the provider administrator can use a computer (hereinafter referred to as the "provider administrator computer") 40 to access the website of the provider site 21 and send a customer registration instruction (hereinafter referred to as the "customer registration instruction") to the provider site 21 from this website (S101). The provider administrator computer 40 may be, for example, a PC or a mobile device such as a smartphone. The provider administrator includes in the customer registration instruction the name of the organization of the customer who wishes to register and the administrator email address of the customer administrator of this customer.

[0047] When the provider site 21 is notified of the customer registration instruction in S101, it checks whether the organization name included in the customer registration instruction notified in S101 is registered as an organization name or subdirectory name in the organization management database 24 (S102).

[0048] When the provider site 21 confirms in S102 that the organization name included in the customer registration instruction notified in S101 is registered as an organization name or subdirectory name in the organization management database 24, it notifies the provider administrator computer 40 via the provider site 21 website that the customer registration failed due to an unavailable organization name (S103).

[0049] Upon receiving the notification in S103, the provider administrator computer 40 notifies the customer that the customer registration has failed due to the unavailable organization name, for example, by displaying a message on a display unit (not shown) (S104). Thus, the provider administrator can recognize that the customer registration has failed due to the unavailable organization name.

[0050] When the provider site 21 confirms in S102 that the organization name included in the customer registration instruction notified in S101 is not registered as either an organization name or a subdirectory name in the organization management database 24, it creates a customer site 22 on the cloud server 20 identified by a subdirectory name that is the same string as the organization name included in the customer registration instruction notified in S101 (S105).

[0051] Next, the provider site 21 requests the main control unit 23 to register in the organization management database 24 a combination of the organization name included in the customer registration instruction notified in S101, a subdirectory name that is the same string as the organization name, and the administrator email address included in the customer registration instruction notified in S101 (S106).

[0052] Upon receiving the request in S106, the main control unit 23 generates a unique organization number that is not registered in the organization management database 24 (S107).

[0053] Next, the main control unit 23 registers in the organization management database 24 a combination of the organization name, subdirectory name, and administrator email address requested to be registered in S106 and the organization number generated in S107 (S108). That is, the main control unit 23 assigns the organization number to the customer site 22.

[0054] FIG. 6 is a diagram showing an example of the organization management database 24 immediately after a customer is registered.

[0055] The organization management database 24 shown in Figure 6 shows an example of a state immediately after a customer whose organization name is "Organization D" has been registered. In Figure 6, for the customer whose organization name is "Organization D," the organization name, subdirectory name, organization number, and administrator email address have been registered, but the administrator PIN has not yet been registered.

[0056] As shown in FIG. 5, after processing S108, the main control unit 23 notifies the provider site 21 that the organization name, subdirectory name, organization number, and administrator email address of the customer site 22 have been registered in the organization management database 24 (S109).

[0057] Upon receiving the notification in S109, the provider site 21 sends an email notifying the completion of the customer's registration (hereinafter referred to as the "customer registration completion email") to the administrator email address included in the customer registration instruction notified in S101 (S110). The provider site 21 includes a URL (Uniform Resource Locator) for accessing the customer site 22 in the customer registration completion email. Here, the URL for accessing the customer site 22 is composed of the domain of the cloud server 20 and the subdirectory name registered in S108. For example, if the domain of the cloud server 20 is "abcserver.biz" and the subdirectory name registered in S108 is "OrganizationD", the URL for accessing the customer site 22 is "https: / / abcserver.biz / OrganizationD".

[0058] After the process of S110, the provider site 21 notifies the provider administrator computer 40 of the success of the customer registration via the website of the provider site 21 (S111).

[0059] Upon receiving the notification in S111, the provider administrator computer 40 notifies the customer of the success of the registration, for example, by displaying a message on a display unit (not shown) (S112). Thus, the provider administrator can recognize the success of the customer's registration.

[0060] The provider administrator can change the organization name or administrator email address registered in the organization management database 24 via the website of the provider site 21 using the provider administrator computer 40. However, the subdirectory name and organization number registered in the organization management database 24 are fixed information that cannot be changed.

[0061] Next, the operation of the system 10 when registering the administrator PIN in the organization management database 24 will be described.

[0062] FIG. 7 is a sequence diagram of the operation of the system 10 when registering the administrator PIN in the organization management database 24.

[0063] In the following description of the operation shown in FIG. 7, customer site 22 is shown as an example of the customer site of the customer to which the customer administrator belongs.

[0064] As shown in FIG. 7, the customer administrator can use a computer (hereinafter referred to as the "customer administrator computer") 50 to access the website of the customer site 22 and send an instruction to register the customer administrator's administrator PIN (hereinafter referred to as the "PIN registration instruction") to the customer site 22 from this website (S121). The customer administrator computer 50 may be, for example, a PC or a mobile device such as a smartphone. The customer administrator includes the administrator PIN they wish to register in the customer registration instruction. The customer administrator uses the URL contained in the email sent to the administrator email address in S110 as the URL for accessing the website of the customer site 22.

[0065] When the customer site 22 receives the PIN registration instruction in S121, the customer site 22 registers the administrator PIN included in the PIN registration instruction received in S121 as the administrator PIN of the customer site 22 in the organization management database 24 (S122).

[0066] Next, the operation of the system 10 when the customer administrator refers to the organization number will be described.

[0067] FIG. 8 is a sequence diagram of the operation of the system 10 when the customer administrator refers to the organization number.

[0068] In the following description of the operation shown in FIG. 8, customer site 22 is shown as an example of the customer site of the customer to which the customer administrator belongs.

[0069] 8, the customer administrator can use customer administrator computer 50 to access the website of customer site 22 and, from this website, send an instruction to customer site 22 to reference the organization number of the customer to which the customer administrator belongs (hereinafter referred to as the "organization number reference instruction") (S141). Note that the customer administrator uses the URL included in the email sent to the administrator's email address in S110 as the URL for accessing the website of customer site 22.

[0070] When the customer site 22 receives the organization number reference instruction in S141, it references the organization number of the customer corresponding to the customer site 22 in the organization management database 24 (S142).

[0071] Next, the customer site 22 notifies the customer administrator computer 50 of the organization number referenced in S142 via the website of the customer site 22 (S143). That is, the customer site 22 notifies the customer administrator of the organization number.

[0072] When the customer administrator computer 50 is notified of the organization number in S143, it notifies the customer administrator of the organization number notified in S143, for example, by displaying the organization number on a display unit (not shown) (S144). Therefore, the customer administrator can recognize the organization number of the customer corresponding to the customer site 22.

[0073] Next, the operation of the system 10 when the MFP itself checks the customer site where the MFP is registered will be described.

[0074] FIG. 9 is a sequence diagram of the operation of the system 10 when the MFP itself checks the customer site where the MFP is registered.

[0075] In the following description of the operation shown in FIG. 9, customer site 22 is shown as an example of the customer site of the customer to which the customer administrator belongs, and MFP 30 is shown as an example of the MFP operated by the customer administrator.

[0076] The customer administrator can install the device application program 37a on the MFP 30 and start the device application program 37a installed on the MFP 30, for example, via the operation unit 31 of the MFP 30.

[0077] When the device application program 37a is installed on the MFP 30 or when the device application program 37a installed on the MFP 30 is started, the device application 38a of the MFP 30 notifies the main control unit 23 of the cloud server 20 of an inquiry about the customer site where the MFP 30 is registered (hereinafter referred to as the "customer site inquiry") (S161), as shown in FIG. 9. The device application 38a includes the serial number of the MFP 30 in the customer site inquiry. The device application 38a can access the main control unit 23 by accessing the domain of the cloud server 20 that is set in the device application program 37a.

[0078] When the main control unit 23 of the cloud server 20 is notified of the customer site inquiry in S161, the main control unit 23 searches for a customer site whose device management database has registered the serial number included in the customer site inquiry notified in S161 (S162).

[0079] If the main control unit 23 detects in S162 a customer site whose serial number included in the customer site inquiry notified in S161 is registered in the device management database, the main control unit 23 notifies the device application 38a of the MFP 30 of the subdirectory name of the customer site detected in S162 (S163). Therefore, until the device application 38a finishes executing, the device application 38a can access the customer site 22 identified by the URL composed of the domain of the cloud server 20 and the subdirectory name notified in S163. Therefore, the device application 38a can access the customer site 22 when, for example, performing cloud print or cloud scan.

[0080] If a customer site where the serial number included in the customer site inquiry notified in S161 is registered in the equipment management database is not detected in S162, the main control unit 23 notifies the equipment application 38a of the MFP 30 that there is no customer site where the MFP 30 is registered (S164).

[0081] When the device application 38a receives the notification in S164, it displays a screen (hereinafter referred to as the "input screen") on the display unit 32 instructing the customer administrator to enter the organization number of the customer site where the customer administrator wishes to register the MFP 30 and the customer administrator PIN (S165).

[0082] Next, the operation of the system 10 when registering an MFP at a customer site will be described.

[0083] FIG. 10 is a sequence diagram of an example of the operation of the system 10 when an MFP is registered at a customer site.

[0084] In the following description of the operation shown in FIG. 10, customer site 22 is shown as an example of the customer site of the customer to which the customer administrator belongs, and MFP 30 is shown as an example of the MFP operated by the customer administrator.

[0085] In S165, the customer administrator can input the organization number of the customer site 22 to which the customer administrator wishes to register the MFP 30 and the customer administrator's administrator PIN via the operation unit 31 of the MFP 30 into the input screen displayed on the display unit 32 of the MFP 30. Here, the customer administrator can use the organization number notified in S144 as the organization number of the customer site 22.

[0086] 10, when the organization number and administrator PIN are entered on the input screen, the device application 38a of the MFP 30 sends a subdirectory name query (hereinafter referred to as the "subdirectory name query") to the main control unit 23 of the cloud server 20 (S181). The device application 38a includes the organization number entered on the input screen in the subdirectory name query. That is, the MFP 30 sends a query to the cloud server 20 about the subdirectory name for the customer site 22 by notifying the cloud server 20 of the organization number entered by the customer administrator. Note that the device application 38a can access the main control unit 23 by accessing the domain of the cloud server 20 set in the device application program 37a in S181.

[0087] When the main control unit 23 of the cloud server 20 is notified of the subdirectory name query in S181, it searches for the subdirectory name associated in the organization management database 24 with the organization number included in the subdirectory name query notified in S181 (S182).

[0088] If the main control unit 23 does not detect in S182 a subdirectory name associated in the organization management database 24 with the organization number included in the subdirectory name inquiry notified in S181, the main control unit 23 notifies the device application 38a of the MFP 30 that the registration of the MFP 30 at the customer site has failed (S183). Therefore, the device application 38a can notify the failure of the registration of the MFP 30 at the customer site by, for example, displaying a message on the display unit 32.

[0089] If the main control unit 23 detects in S182 a subdirectory name associated in the organization management database 24 with the organization number included in the subdirectory name inquiry notified in S181, the main control unit 23 notifies the device application 38a of the MFP 30 of the subdirectory name detected in S182 (S184).

[0090] Upon receiving the notification in S184, the device application 38a notifies the customer site 22 identified by the URL composed of the domain of the cloud server 20 and the subdirectory name notified in S184 of an instruction to register the MFP 30 (hereinafter referred to as the "device registration instruction") (S185). The device application 38a includes the serial number of the MFP 30 and the administrator PIN entered on the input screen in the device registration instruction. In other words, the MFP 30 accesses the customer site 22 using the subdirectory name notified by the cloud server 20, and notifies the accessed customer site 22 of the serial number of the MFP 30.

[0091] When the customer site 22 is notified of the device registration instruction in S185, it performs authentication based on the administrator PIN included in the device registration instruction notified in S185 (S186). Here, the customer site 22 determines that the authentication has been successful if the administrator PIN included in the device registration instruction notified in S185 matches the administrator PIN associated with the customer site 22 in the organization management database 24. On the other hand, the customer site 22 determines that the authentication has failed if the administrator PIN included in the device registration instruction notified in S185 does not match the administrator PIN associated with the customer site 22 in the organization management database 24.

[0092] If the authentication executed in S186 fails, the customer site 22 notifies the device application 38a of the MFP 30 of the failure to register the MFP 30 at the customer site (S187). Therefore, the device application 38a can notify the failure to register the MFP 30 at the customer site by, for example, displaying on the display unit 32.

[0093] If the authentication executed in S186 is successful, the customer site 22 registers information about the MFP 30, including the serial number included in the device registration instruction notified in S185, in the device management database 22a (S188). That is, by the customer site 22 managing the serial number notified from the MFP 30, the customer site 22 in the multi-tenant cloud service and the MFP 30 that uses this customer site 22 are associated with each other.

[0094] Next, the customer site 22 sends a notification of the completion of the registration of the MFP 30 at the customer site 22 via email to the administrator email address associated with the customer site 22 in the organization management database 24 (S189).

[0095] Next, the customer site 22 notifies the device app 38a of the MFP 30 that the MFP 30 has been successfully registered at the customer site 22 (S190). Therefore, the device app 38a can notify the customer site 22 of the success of the registration of the MFP 30, for example, by displaying a message on the display unit 32. Upon receiving the notification in S190, the device app 38a can access the customer site 22 identified by the URL composed of the domain of the cloud server 20 and the subdirectory name notified in S184 until execution of the device app 38a is completed. Therefore, the device app 38a can access the customer site 22 when, for example, performing cloud print or cloud scan.

[0096] As described above, system 10 associates a customer site in a multi-tenant cloud service with an MFP that uses the customer site by having the customer administrator input the customer organization number corresponding to the customer site, rather than the subdirectory name for accessing the customer site, into the MFP (S181 to S188). Here, the subdirectory name for accessing the customer site is the organization name of the customer corresponding to the customer site, which is input by the provider administrator when registering the customer (S101 to S108). The customer organization name is information that can be freely determined by each provider administrator and is likely to be a complex and long character string. In other words, the subdirectory name for accessing the customer site is likely to be a complex and long character string. On the other hand, the customer organization number is identification information assigned to the customer site by cloud server 20 (S107 to S108) and is likely to be a shorter and simpler character string than the subdirectory name for accessing the customer site. System 10 associates a customer site in a multi-tenant cloud service with an MFP that uses this customer site by having a customer administrator input an organization number, which is a short and simple string of characters, into the MFP, thereby reducing the workload of associating a customer site in a multi-tenant cloud service with an MFP that uses this customer site.

[0097] If the administrator PIN entered into the MFP matches the administrator PIN associated with the customer site, i.e., if authentication of the customer administrator based on the administrator PIN entered into the MFP is successful, the system 10 allows the customer site to manage the serial number notified from the MFP (S188). Therefore, the system 10 can reduce the possibility that the customer site will incorrectly manage the serial number of the MFP.

[0098] In this embodiment, system 10 authenticates a user based on the administrator PIN entered into the MFP as authentication of the user based on the information entered into the MFP. However, authentication of the user based on the information entered into the MFP may be authentication based on information other than the administrator PIN. For example, authentication of the user based on the information entered into the MFP may be authentication based on the ID and password entered into the MFP, or authentication based on IC card information entered into the MFP by an IC card.

[0099] When the serial number is notified from the MFP to the customer site, the system 10 may request permission from the user to manage the MFP's serial number, instead of authenticating the user based on information entered into the MFP. That is, the system 10 may execute the operation shown in FIG. 11 instead of the operation shown in FIG. 10.

[0100] FIG. 11 is a sequence diagram of an example, different from the example shown in FIG. 10, of the operation of the system 10 when registering an MFP at a customer site.

[0101] In the following description of the operation shown in FIG. 11, customer site 22 is shown as an example of the customer site of the customer to which the customer administrator belongs, and MFP 30 is shown as an example of the MFP operated by the customer administrator.

[0102] When the system 10 performs the operation shown in Fig. 11, the organization management database 24 does not need to manage the administrator PIN. Therefore, when the system 10 performs the operation shown in Fig. 11, it does not perform the operation shown in Fig. 7. Furthermore, when the system 10 performs the operation shown in Fig. 11, the input screen that the device application 38a displays on the display unit 32 in S165 prompts the customer administrator to input the organization number of the customer site where the customer administrator wishes to register the MFP 30, but does not prompt the customer administrator to input the administrator PIN.

[0103] As shown in FIG. 11, the system 10 executes the processes of S201 to S204 which are similar to the processes of S181 to S184.

[0104] Next, the device application 38a executes the process of S205, which is the same as the process of S185, except that the device application 38a includes the serial number of the MFP 30 in the device registration instruction, but does not include the administrator PIN in the device registration instruction.

[0105] When the customer site 22 is notified of the device registration instruction in S205, it sends an email (hereinafter referred to as the "device management permission request email") to the customer administrator requesting permission to manage the serial number of the MFP 30 to the administrator email address associated in the organization management database 24 with the customer corresponding to the customer site 22 (S206).

[0106] FIG. 12 is a diagram showing an example of a portion of the device management permission request email.

[0107] 12, the device management permission request email includes text 61 indicating the serial number of the MFP 30, a reject button 62 for rejecting the customer site 22 from managing the serial number of the MFP 30, and an accept button 63 for permitting the customer site 22 to manage the serial number of the MFP 30. When the reject button 62 is pressed, the computer opening the device management permission request email notifies the customer site 22 of the rejection of management of the serial number of the MFP 30. When the accept button 63 is pressed, the computer opening the device management permission request email notifies the customer site 22 of the permission to manage the serial number of the MFP 30.

[0108] As shown in FIG. 11, after the process of S206, when the customer site 22 is notified that management of the serial number of the MFP 30 has been rejected, the customer site 22 executes the process of S207, which is the same as the process of S187.

[0109] After the process of S206, when the customer site 22 is notified that management of the serial number of the MFP 30 is permitted, the customer site 22 executes the processes of S208 to S210, which are similar to the processes of S188 to S190.

[0110] 11, the customer site manages the serial number notified from the MFP when the customer administrator has permitted management of the MFP serial number (S208). Therefore, when system 10 performs the operation shown in FIG. 11, it is possible to reduce the possibility that the customer site will incorrectly manage the MFP serial number.

[0111] 11, customer site 22 uses email to request permission to manage the serial number of MFP 30 from the customer administrator. However, customer site 22 may request permission to manage the serial number of MFP 30 from the customer administrator by a method other than email. For example, if a dedicated application is installed on customer administrator computer 50, customer site 22 may request permission to manage the serial number of MFP 30 from the customer administrator by using a notification function in this application.

[0112] When the serial number is notified from the MFP to the customer site, system 10 may allow the customer site to manage the serial number notified from the MFP without authenticating the user based on information entered into the MFP or requesting permission from the customer site to manage the MFP's serial number. In other words, system 10 may perform the operation shown in Fig. 13 instead of the operations shown in Figs. 10 and 11.

[0113] FIG. 13 is a sequence diagram of an example of the operation of system 10 when registering an MFP at a customer site, which is different from the examples shown in FIGS.

[0114] In the following description of the operation shown in FIG. 13, customer site 22 is shown as an example of the customer site of the customer to which the customer administrator belongs, and MFP 30 is shown as an example of the MFP operated by the customer administrator.

[0115] When the system 10 performs the operation shown in Fig. 13, the organization management database 24 does not need to manage the administrator PIN. Therefore, when the system 10 performs the operation shown in Fig. 13, it does not perform the operation shown in Fig. 7. Furthermore, when the system 10 performs the operation shown in Fig. 13, the input screen that the device application 38a displays on the display unit 32 in S165 prompts the customer administrator to input the organization number of the customer site where the customer administrator wishes to register the MFP 30, but does not prompt the customer administrator to input the administrator PIN.

[0116] As shown in FIG. 13, the system 10 executes the processes of S221 to S224 which are similar to the processes of S181 to S184.

[0117] Next, the device application 38a executes the process of S225, which is the same as the process of S185, except that the device application 38a includes the serial number of the MFP 30 in the device registration instruction, but does not include the administrator PIN in the device registration instruction.

[0118] When the customer site 22 receives the device registration instruction in S225, it executes the processes of S226 to S228, which are the same as the processes of S188 to S190.

[0119] In this embodiment, the system 10 includes a cloud server 20. However, instead of the cloud server 20, a server that is not a cloud server but has the same functions as the cloud server 20 may be included.

[0120] (Second embodiment) First, the configuration of a system according to the second embodiment of the present invention will be described.

[0121] FIG. 14 is a block diagram of a system 310 according to this embodiment.

[0122] Of the components of the system 310 shown in FIG. 14, the same components as those of the system 10 (see FIG. 1) are denoted by the same reference numerals as those of the system 10, and detailed description thereof will be omitted.

[0123] The configuration of the system 310 is similar to that of the system 10, except that a multi-tenant cloud server 320 is provided instead of the cloud server 20 (see FIG. 1).

[0124] The configuration of cloud server 320 is similar to that of cloud server 20, except that it includes a main control unit 323 that performs control such as searching for customer sites where MFPs are registered, an organization management database 324 that manages customers, and a server program 325, instead of main control unit 23 (see Figure 1), organization management database 24 (see Figure 1), and server program 25 (see Figure 1).

[0125] The cloud server 320 executes a server program 325 to realize the operations described below.

[0126] FIG. 15 is a diagram showing an example of the organization management database 324. As shown in FIG.

[0127] 15, the organization management database 324 includes a table 324a that indicates, for each customer, the organization name, subdirectory name, administrator email address, and administrator PIN. The organization management database 324 also includes a reservation number table 324b that indicates, for each customer, the reservation number required to register an MFP at the customer site, the organization name, and the expiration date of the reservation number.

[0128] The reservation number is, for example, a five-digit number. All reservation numbers registered in the organization management database 324 are unique and different from one another. The reservation number is identification information for a customer site that is a tenant, and constitutes tenant identification information.

[0129] The operation of the system 310 will now be described.

[0130] The operation of system 310 is similar to that of system 10, except as described below.

[0131] First, the operation of the system 310 when registering a customer will be described.

[0132] FIG. 16 is a sequence diagram of the operation of the system 310 when registering a customer.

[0133] In the following description of the operation shown in FIG. 16, provider site 21 is shown as an example of the provider site of the provider to which the provider administrator belongs, and customer site 22 is shown as an example of the customer site of the customer registered by this provider administrator.

[0134] As shown in FIG. 16, the system 310 executes the processes of S401 to S406 which are similar to the processes of S101 to S106.

[0135] Upon receiving the request in S406, the main control unit 323 generates a unique reservation number that is not registered in the organization management database 324 and an expiration date for this reservation number (S407). For example, the main control unit 323 may generate an expiration date that is a certain time after the current date and time, such as 24 hours after the current date and time.

[0136] After the processing of S407, the main control unit 323 registers in the organization management database 324 a combination of the organization name, subdirectory name, and administrator email address requested to be registered in S406, and the reservation number and expiration date generated in S407 (S408). That is, the main control unit 323 assigns the reservation number to the customer site 22.

[0137] After the process of S408, the system 310 executes the processes of S409 to S412, which are similar to the processes of S109 to S112.

[0138] Next, the operation of the system 310 when the customer administrator refers to the reservation number will be described.

[0139] The operation of system 310 when the customer administrator refers to the reservation number is the same as the operation of system 10 when the customer administrator refers to the organization number, except for the difference between the reservation number and the organization number.

[0140] Next, the operation of system 310 when the MFP itself checks the customer site where the MFP is registered will be described.

[0141] The operation of system 310 when the MFP itself checks the customer site where the MFP is registered is the same as the operation of system 10 when the MFP itself checks the customer site where the MFP is registered, except for the difference between the reservation number and the organization number.

[0142] Next, the operation of system 310 when registering an MFP at a customer site will be described.

[0143] FIG. 17 is a sequence diagram of an example of the operation of system 310 when registering an MFP at a customer site.

[0144] In the following description of the operation shown in FIG. 17, customer site 22 is shown as an example of the customer site of the customer to which the customer administrator belongs, and MFP 30 is shown as an example of the MFP operated by the customer administrator.

[0145] The customer administrator can input the reservation number of the customer site 22 where the customer administrator wishes to register the MFP 30 and the customer administrator's administrator PIN via the operation unit 31 of the MFP 30 into the input screen displayed on the display unit 32 of the MFP 30 during the operation of the system 310 when the MFP itself checks the customer site where the MFP is registered. Here, the customer administrator can use the reservation number notified during the operation of the system 310 when the customer administrator refers to the reservation number as the reservation number of the customer site 22.

[0146] 17, when a reservation number and administrator PIN are entered on the input screen, the device application 38a of the MFP 30 sends a subdirectory name query to the main control unit 323 of the cloud server 320 (S481). The device application 38a includes the reservation number entered on the input screen in the subdirectory name query. That is, the MFP 30 queries the cloud server 320 about the subdirectory name for the customer site 22 by notifying the cloud server 320 of the reservation number entered by the customer administrator. Note that the device application 38a can access the main control unit 323 by accessing the domain of the cloud server 320 set in the device application program 37a in S481.

[0147] When the main control unit 323 of the cloud server 320 is notified of the subdirectory name query in S481, it searches for the subdirectory name associated in the organization management database 324 with the reservation number included in the subdirectory name query notified in S481 (S482).

[0148] If the main control unit 323 does not detect in S482 a subdirectory name associated in the organization management database 324 with the reservation number included in the subdirectory name inquiry notified in S481, the main control unit 323 notifies the device application 38a of the MFP 30 that registration of the MFP 30 at the customer site has failed (S483). Therefore, the device application 38a can notify the failure of registration of the MFP 30 at the customer site by, for example, displaying a message on the display unit 32.

[0149] If the main control unit 323 detects in S482 a subdirectory name associated in the organization management database 324 with the reservation number included in the subdirectory name inquiry notified in S481, it determines whether the expiration date associated in the organization management database 324 with the reservation number included in the subdirectory name inquiry notified in S481 has passed (S484).

[0150] If the main control unit 323 determines in S484 that the expiration date associated in the organization management database 324 with the reservation number included in the subdirectory name inquiry notified in S481 has passed, the main control unit 323 notifies the device application 38a of the MFP 30 that registration of the MFP 30 at the customer site has failed (S485). Therefore, the device application 38a can notify the failure of registration of the MFP 30 at the customer site by, for example, displaying a message on the display unit 32.

[0151] If the main control unit 323 determines in S484 that the expiration date associated in the organization management database 324 with the reservation number included in the subdirectory name inquiry notified in S481 has not passed, it notifies the device application 38a of the MFP 30 of the subdirectory name detected in S482 (S486).

[0152] After the process of S486, the system 310 executes the processes of S487 to S492 which are similar to the processes of S185 to S190.

[0153] Next, the operation of cloud server 320 when deleting a reservation number whose expiration date has passed will be described.

[0154] FIG. 18 is a flowchart showing the operation of cloud server 320 when deleting a reservation number whose expiration date has passed.

[0155] The main control unit 323 of the cloud server 320 executes the operation shown in FIG. 18 at a specific timing, for example, at regular intervals.

[0156] As shown in FIG. 18, the main control unit 323 determines whether or not there is a reservation number in the reservation number table 324b whose associated expiration date has passed (S501).

[0157] When the main control unit 323 determines in S501 that there is a reservation number in the reservation number table 324b whose associated expiration date has passed, it deletes all records containing the associated reservation number in the reservation number table 324b whose associated expiration date has passed from the reservation number table 324b (S502).

[0158] When the main control unit 323 determines in S501 that there is no expired reservation number associated with it in the reservation number table 324b, or when it finishes the processing of S502, it ends the operation shown in FIG.

[0159] As described above, system 310 associates a customer site in a multi-tenant cloud service with an MFP that uses the customer site by having the customer administrator input into the MFP the customer reservation number corresponding to the customer site, rather than the subdirectory name for accessing the customer site (S481-S490). Here, the subdirectory name for accessing the customer site is the organization name of the customer corresponding to the customer site, which was input by the provider administrator when registering the customer (S401-S408). The customer organization name is information that can be freely determined by each provider administrator, and is likely to be a complex and long character string. In other words, the subdirectory name for accessing the customer site is likely to be a complex and long character string. On the other hand, the customer reservation number is identification information assigned to the customer site by cloud server 320 (S407-S408), and is likely to be a shorter and simpler character string than the subdirectory name for accessing the customer site. System 310 associates a customer site in a multi-tenant cloud service with an MFP that uses this customer site by having a customer administrator input a reservation number, which is a short and simple string of characters, into the MFP, thereby reducing the workload of associating a customer site in a multi-tenant cloud service with an MFP that uses this customer site.

[0160] In system 310, cloud server 320 assigns a reservation number that is valid only for a specific period to a customer site (S407-S408), thereby reducing the number of reservation numbers that exist validly at the same time. Therefore, system 310 is likely to be able to make the character string of the reservation number shorter and simpler than the organization number in the first embodiment, and as a result, the workload of associating a customer site in a multi-tenant cloud service with an MFP that uses this customer site can be reduced compared to the first embodiment.

[0161] In system 310, cloud server 320 assigns a reservation number that is valid only for a specific period to the customer site, and the customer site manages the serial number notified from the MFP only for the period that the reservation number is valid (S481 to S490). Therefore, system 310 can reduce the possibility that the customer site will incorrectly manage the MFP serial number.

[0162] If the administrator PIN entered into the MFP matches the administrator PIN associated with the customer site, i.e., if authentication of the customer administrator based on the administrator PIN entered into the MFP is successful, system 310 allows the customer site to manage the serial number notified from the MFP (S490). Therefore, system 310 can reduce the possibility that the customer site will incorrectly manage the MFP's serial number.

[0163] In this embodiment, system 310 authenticates a user based on the administrator PIN entered into the MFP as authentication of the user based on information entered into the MFP. However, authentication of the user based on information entered into the MFP may be authentication based on information other than the administrator PIN. For example, authentication of the user based on information entered into the MFP may be authentication based on the ID and password entered into the MFP, or authentication based on IC card information entered into the MFP by an IC card.

[0164] Similar to the first embodiment, when the serial number is notified to the customer site from the MFP, system 310 may request from the customer site permission to manage the MFP's serial number, instead of authenticating the user based on information entered into the MFP. When the serial number is notified to the customer site from the MFP and system 310 requests from the customer site permission to manage the MFP's serial number, it is possible to reduce the possibility that the customer site will erroneously manage the MFP's serial number.

[0165] As in the first embodiment, when the serial number is notified from the MFP to the customer site, system 310 may allow the customer site to manage the serial number notified from the MFP without performing either authentication of the user based on information entered into the MFP or a request from the customer site to the user for permission to manage the MFP's serial number.

[0166] In this embodiment, system 310 includes cloud server 320, but may include a server that is not a cloud server but has the same functions as cloud server 320 instead of cloud server 320.

[0167] In each of the above-described embodiments, the tenant identification information of the present invention is composed only of numbers. However, the tenant identification information of the present invention may include characters other than numbers, or may be composed only of characters other than numbers.

[0168] In the above-described embodiments, the access information of the present invention is a subdirectory name. However, the access information of the present invention may be information other than a subdirectory name. For example, the access information of the present invention may be a subdomain.

[0169] In each of the above-described embodiments, the electronic device of the present invention is an MFP. However, the electronic device of the present invention may be an image forming device other than an MFP, such as a dedicated printer, or may be an electronic device other than an image forming device, such as a PC. [Explanation of symbols]

[0170] 10 Systems 20 Cloud Servers 22 Customer Site (Tenant) 25 Server Programs 30 MFP (electronic equipment) 37a Equipment application programs (programs for equipment) 310 System 320 Cloud Server 325 Server Program

Claims

1. Multi-tenant cloud servers and an electronic device that uses a tenant of the cloud server; Equipped with the cloud server assigns tenant identification information as identification information of the tenant to the tenant and notifies the user of the assigned tenant identification information; the electronic device notifies the cloud server of the tenant identification information input by the user, thereby inquiring of access information for accessing the tenant from the cloud server; the cloud server notifies the electronic device of the access information associated with the tenant identification information notified from the electronic device; the electronic device accesses the tenant using the access information notified from the cloud server, and notifies the accessed tenant of device identification information as identification information of the electronic device; The system is characterized in that, when the device identification information is notified from the electronic device, the tenant requests permission from the user to manage the device identification information, and then, when permission to manage the device identification information is granted by the user, the tenant manages the device identification information notified from the electronic device.

2. The system according to claim 1 , wherein the cloud server assigns the tenant the tenant identification information that is valid for a specific period of time.

3. The system according to claim 1 or claim 2, characterized in that the tenant manages the device identification information notified from the electronic device when user authentication based on information input into the electronic device is successful.

4. A multi-tenant server, assigning tenant identification information as identification information of the tenant of the server to the tenant, notifying a user of the assigned tenant identification information, and notifying the electronic device of access information for accessing the tenant, the access information being associated with the tenant identification information notified from the electronic device using the tenant; The tenant is characterized in that, when device identification information is notified from the electronic device as identification information of the electronic device, the tenant requests permission from the user to manage the device identification information, and then, when management of the device identification information is permitted by the user, the tenant manages the device identification information notified from the electronic device.

5. A server program executed by a multi-tenant cloud server, comprising: assigning tenant identification information as identification information of the tenant of the cloud server to the tenant, notifying the cloud server of the tenant identification information assigned to the cloud server to a user; having the electronic device notify the cloud server of access information for accessing the tenant, the access information being associated with the tenant identification information notified to the cloud server from the electronic device using the tenant; when device identification information as identification information of the electronic device is notified to the tenant from the electronic device, a user is made to request permission for management of the device identification information from the tenant; A server program characterized by having a user request the tenant for permission to manage the device identification information, and then, if the user grants permission to manage the device identification information, having the tenant manage the device identification information notified to the tenant from the electronic device.

Images