System, and method therefor

Abstract

To provide a system with improved user usability.SOLUTION: The system has: means for, when a client apparatus 104 is installed in a nation 106 and a nation indicated by destination information held by the client apparatus 104 is a nation 107, transferring registration information of the client apparatus 104 in a cloud service developed in the nation 107 to a cloud service developed in the nation 106; and means for carrying out connection destination instruction to the client apparatus 104 for changing the connection destination from a cloud management server 101 installed in the nation 107 to a cloud management server 102 installed in the nation 106.SELECTED DRAWING: Figure 1

Description

[Technical field]

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

[0002] As Internet usage has become commonplace around the world, Internet connections are now made in a wide variety of network environments, depending on a combination of factors such as national and regional infrastructure and residential environments.

[0003] On the other hand, from the viewpoint of protecting personal information, there is an accelerating movement to prevent information from being sent outside the country more than necessary. Under such circumstances, in order to use services comfortably on client devices, it is important to maintain the user experience by completing the registration process without complicated operations when connecting from a registered server to a server in another region.

[0004] Patent Document 1 discloses an example in which authorization servers are installed in multiple countries, and when a client receives an authorization token from the authorization server, the client determines the destination country based on that information and establishes a connection. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] JP 2019-139520 A Summary of the Invention [Problem to be solved by the invention]

[0006] However, in the past, when the server on which the user's device was registered was different from the server to which the user was trying to connect, there was a problem that registration could not be completed due to inconsistency in the registration information, and the registration status could not be transferred. For this reason, there was room for improvement in the usability of the previous system.

[0007] The present invention has been made in consideration of the above problems, and has an object to provide a system with improved usability for users. [Means for solving the problem]

[0008] A system according to an embodiment of the present invention includes a first client device installed in a first country and having destination information for a second country, a second client device installed in the first country, a first cloud management server installed in the second country, a second cloud management server installed in the first country, a first cloud service deployed in the first country, a second cloud service deployed in the second country, a third cloud service deployed in the first country and providing the same service as the second cloud service, means for instructing the second cloud service from the second cloud management server to transfer registration information of the first client device to the third cloud service, and a cloud management server for managing a cloud service on which the third cloud service is deployed. the first cloud service provided by the second cloud management server in the first country; a means for transferring registration information of the first client device in the second cloud service to the third cloud service in accordance with a result of the check; a means for sending a registration success notification from the second cloud management server to the first cloud management server in accordance with completion of the transfer; a means for deleting the registration information of the first client device in the second cloud service in accordance with completion of the transfer; and a means for issuing a connection destination instruction to the first client device to change its connection destination from the first cloud management server to the second cloud management server in accordance with receiving the registration success notification. Equipped with. Effect of the Invention

[0009] According to the present invention, it is possible to provide a system with improved usability for users. [Brief description of the drawings]

[0010] [Figure 1] 1 is a schematic diagram illustrating a configuration of an information processing system according to a first embodiment of the present invention. [Diagram 2] FIG. 2 is a block diagram showing a schematic configuration of a client device 104. [Diagram 3] FIG. 2 is a block diagram showing a schematic configuration of a client device 105. [Figure 4] FIG. 2 is a block diagram showing a schematic configuration of a cloud management server. [Diagram 5] 13 is a diagram showing a conventional registration sequence when the country in the destination information of the client device 104 does not match the country in which the client device 105 is installed. [Figure 6] FIG. 4 is a diagram showing a registration sequence according to the first embodiment. [Figure 7] 13 is an example of a database for acquiring a client device identification ID. [Figure 8] 1 is an example of a database for acquiring a service to be registered. [Figure 9] FIG. 11 is a diagram showing a sequence according to the second embodiment of the present invention. [Figure 10] FIG. 11 is a diagram illustrating a configuration after data transfer and notification are completed in the second embodiment of the present invention. [Figure 11] FIG. 11 is a diagram showing a sequence according to the third embodiment of the present invention. [Figure 12] FIG. 11 is a diagram illustrating a configuration after data transfer and notification of a cloud service are completed in the third embodiment of the present invention. [Figure 13] FIG. 11 is a diagram showing a sequence according to the fourth embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0011] Hereinafter, the embodiments of the present invention will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the present invention, and not all of the combinations of features described in the embodiments are necessarily essential to the solution of the present invention.

[0012] <Example 1> First, a first embodiment of the present invention will be described. FIG. 1 is a schematic diagram showing a configuration of a system according to the first embodiment of the present invention. The system according to the first embodiment includes a cloud management server 101, a cloud management server 102, a client device 104, and a client device 105. The cloud management server 101 is an example of a first cloud management server. The cloud management server 102 is an example of a second cloud management server. The client device 104 is an example of a first client device. The client device 105 is an example of a second client device. The cloud management server 101, the cloud management server 102, the client device 104, and the client device 105 are connected via the Internet 103.

[0013] Cloud management server 101 and cloud management server 102 hold information on client devices 104 and manage registration information for various cloud services. Client device 104 is a terminal used by a user. Client device 104 is, for example, a peripheral device. Client device 104 is, for example, an inkjet type printing device having a printing function and a scanning function. Client device 105 is capable of connecting to the Internet. Client device 105 is, for example, an information processing device such as a personal computer or a smartphone. Client device 105 is a device on which a web browser and applications are installed.

[0014] Country 106 and country 107 indicate national territories. Country 106 is a different country from country 107. Country 106 is an example of a first country. Country 107 is an example of a second country. In this embodiment, destination information, which is country information of the destination written inside client device 104, is country information about country 107. Therefore, in normal operations, client device 104 is connected to cloud management server 101 installed in country 107 based on the destination information.

[0015] Normally, it is desirable for the client device 104 to be managed by the cloud management server 101 installed in the country 107 indicated in the destination information. However, as shown in FIG. 1, when the client device 105 transitions to a registration page of the country 106, the registration-related process is sent to the cloud management server 102 installed in the country 106.

[0016] 2 is a block diagram showing a schematic configuration of the client device 104. In this embodiment, an example will be described in which the client device 104 is an image processing device. The client device 104 is, for example, a device equipped with a copier, printer, facsimile, scanner, or the like, capable of scanning paper media and digitizing them. The client device 104 is not limited to these, and any type of device may be used as long as it is configured to communicate over a network.

[0017] In the client device 104 , the print function is realized by a printer unit 201 , the scanner function is realized by a scanner unit 202 , and the storage function is realized by a memory card mounting unit 203 and a memory card 204 .

[0018] The printer unit 201 prints image data received from outside or image data stored in a memory card 204 on printing paper by a recording method such as an inkjet method or an electrophotographic method. The printer unit 201 also manages ink information including the remaining amount of ink and paper information including the number of loaded sheets of paper.

[0019] The scanner unit 202 optically reads an original placed on a platen and converts it into electronic data. Furthermore, the scanner unit 202 converts the electronic data generated by reading the original into a specified file format, and transmits it to an external device via a network or stores it in a storage area such as a HDD.

[0020] The client device 104 also executes a copy service. The copy service is realized by reading an original placed on a platen with a scanner unit 202, generating image data, transferring the generated image data to a printer unit 201, and the printer unit 201 printing the image data on printing paper.

[0021] Various file data are stored in the memory card 204 inserted in the memory card insertion unit 203. The client device 104 can read and edit the file data from an external device via a network. The client device 104 can also store file data from an external device in the memory card 204.

[0022] Furthermore, the client device 104 includes a CPU 205, a program memory 206, a work memory 207, a display unit 208, an operation unit 209, a network communication unit 210, a network connection unit 211, and a flash memory 212. CPU is an abbreviation for Central Processing Unit.

[0023] The CPU 205 is a central processing unit for controlling each unit in the client device 104. The program memory 206 is composed of a ROM or the like, and stores various program codes and an application 215 for communicating with a server device or the like. ROM is an abbreviation for Read Only Memory. The application 215 also accesses the printer unit 201 to obtain information on consumables such as ink and paper. The work memory 207 is composed of a RAM or the like, and temporarily stores and buffers image data when each service is executed. RAM is an abbreviation for Random Access Memory.

[0024] The display unit 208 is, for example, an LCD, and displays various information. The operation unit 209 is made up of switches and the like that allow the user to perform various input operations. LCD is an abbreviation for Liquid Crystal Display.

[0025] The network communication unit 210 connects the client device 104 to a network to perform various communications. The client device 104 can be connected to a network such as the Internet via the network connection unit 211. The network communication unit 210 supports wired LAN and wireless LAN. When the network communication unit 210 supports wired LAN, the network connection unit 211 is a connector for connecting a cable of the wired LAN. When the network communication unit 210 is compatible with wireless LAN, the network connection unit 211 is an antenna.

[0026] The flash memory 212 is a non-volatile memory for storing image data and the like received by the network communication unit 210. The above-mentioned units are connected to each other via a bus 213.

[0027] Next, Fig. 3 will be described. Fig. 3 is a block diagram showing a schematic configuration of the client device 105. The client device 105 is made up of a ROM 302, a RAM 303, a CPU 304, and a storage device 307. A control program 308 that controls the entire client device 105 is stored in the storage device 307.

[0028] The client device 105 also has a display unit 305 and an input unit 306. All of the above-mentioned units are connected by an electrical wiring bus 301. Furthermore, a browser 310 is installed in the client device 105 as a means of communication for the user. The browser 310 is just an example, and a native application or the like may be used as long as it is useful as a means of communication for the user.

[0029] Next, Fig. 4 will be described. Fig. 4 is a block diagram showing a schematic configuration of cloud management servers 101 and 102. Each of cloud management servers 101 and 102 is composed of a communication module 407, ROM 402, RAM 403, CPU 404, and storage device 405. A control program 406 that controls the entire cloud management servers 101 and 102 is stored in the storage device 405.

[0030] Furthermore, each of the cloud management servers 101, 102 has a database 410. This database 410 stores user information and information required to provide services that are read and written by each of the cloud management servers 101, 102. Furthermore, all of the above-mentioned components are connected by an electrical wiring bus 401.

[0031] Next, a specific sequence will be described with reference to Fig. 5 and Fig. 6. Fig. 5 is a diagram showing a conventional registration sequence when the country in the destination information of the client device 104 does not match the country in which the client device 105 is installed. The client device 104 connects to the cloud management server 101 in the same country 107 based on the destination information that the client device 104 possesses being country 107.

[0032] When a user registers for a new cloud service, the user operates client device 104 to issue a registration ID from cloud management server 101. In step S501, client device 104 receives a user operation and requests cloud management server 101 to issue a registration ID.

[0033] In step S502, cloud management server 101 issues a registration ID and stores the issued registration ID in its own database. In step S503, cloud management server 101 transmits the issued registration ID to client device 104. Also in step S503, client device 104 displays the registration ID received from cloud management server 101 on its own screen display device (for example, display unit 208).

[0034] The user checks the registration ID displayed on the screen display device of client device 104, and operates client device 105 to access a website for cloud service registration and enters the registration ID. Here, client device 105 is installed in country 106. Therefore, in step S504, client device 105 receives the user's operation and inputs the registration ID to cloud management server 102. Therefore, the registration ID input by the user to client device 105 is referenced by cloud management server 102 installed in country 106, which is the same country as the country in which client device 105 is installed.

[0035] In response to the registration ID input from client device 105, cloud management server 102 returns an error in step S505 because cloud management server 102 does not have registration information for client device 104.

[0036] 6 is a diagram showing a registration sequence according to the first embodiment. Based on the fact that the destination information held by the client device 104 is country 107, the client device 104 connects to the cloud management server 101 located in the same country 107. When registering for a new cloud service, the user operates the client device 104 to issue a registration ID from the cloud management server 101. In step S601, the client device 104 receives a user operation and requests the cloud management server 101 to issue a registration ID.

[0037] In this embodiment, the process of step S606 is executed instead of the process of step S502 in Fig. 5. In step S606, cloud management server 101 executes a process of issuing a registration ID. Here, cloud management server 101 issues an encrypted registration ID that includes information about the country in which cloud management server 101 is installed. In step S606, cloud management server 101 stores the issued registration ID in its own database. In step S603, cloud management server 101 transmits the issued registration ID to client device 104. Also in step S603, client device 104 displays the registration ID received from cloud management server 101 on its own screen display device (for example, display unit 208).

[0038] The user checks the registration ID displayed on the screen display device of client device 104, operates client device 105 to access a website for cloud service registration, and enters the registration ID. Here, client device 105 is installed in country 106. Therefore, in step S604, client device 105 receives the user's operation and inputs the registration ID to cloud management server 102.

[0039] In step S607, cloud management server 102 decrypts the entered registration ID and verifies the country that issued the registration ID (verifies the region). Cloud management server 102 recognizes from the country information included in the entered registration ID that this registration ID was issued by cloud management server 101 in country 107. In step S608, cloud management server 102 queries cloud management server 101 that issued the entered registration ID about the registration information.

[0040] In step S609, cloud management server 101 references the database to confirm that the queried registration ID has already been registered, and transmits information to that effect to cloud management server 102. Cloud management server 102 receives the information to the effect that the registration has already been performed from cloud management server 101.

[0041] In step S610, in response to receiving information from cloud management server 101 indicating that registration has been completed, cloud management server 101 transmits information to client device 105 indicating that registration has been completed.

[0042] In this way, according to this embodiment, the registration ID includes information about the country in which the cloud management server that issued the registration ID is installed. Therefore, even if the country indicated by the destination information held by the client device 104 is different from the country in which the client device 105 is installed, the information can be correctly referenced, improving usability for the user.

[0043] <Example 2> Next, a second embodiment of the present invention will be described. In the first embodiment, a method was described in which the country information included in the encrypted state in the registration ID is decrypted, and the registration information is queried from the cloud management server 101 that exists in the registered country. In this embodiment, the registration information is transferred from the cloud management server 101 to the cloud management server 102, and all subsequent communications are processed within a system that exists in the country 106.

[0044] First, the registration information of the database will be described with reference to Fig. 7 and Fig. 8. Fig. 7 shows an example of a database for acquiring a client device identification ID. A database 700 has records each consisting of a primary key 701 and a client device identification ID 702.

[0045] The primary key 701 is information that can identify a client device, such as a device serial number, a MAC address, or a registration ID. The client device identification ID 702 is an ID that can identify the client device within the system. According to the database 700, if the value of the primary key 701 is known, the client device identification ID 702 can be obtained.

[0046] 8 shows an example of a database for acquiring a service to be registered. A database 800 has records each consisting of a primary key 801, a serial number 802, a client device identification ID 803, and a service name 804.

[0047] Primary key 801 is a combination of a registration ID and a client device identification ID. According to database 800, if the value of primary key 801, the registration ID, and the client device identification ID are known, information on the client device that issued the registration ID can be obtained. The information on the client device that issued the registration ID includes the values ​​of serial number 802, client device identification ID 803, and service name 804.

[0048] The record formats shown in FIG. 7 and FIG. 8 are merely examples, and there are no limitations on the values ​​used as primary keys or on the combinations of data held by client devices.

[0049] The process flow of the second embodiment will be described with reference to Fig. 9. Fig. 9 is a diagram showing a sequence according to the second embodiment of the present invention. In Fig. 9, the processes from step S901 to step S907 are the same as the processes from step S601 to step S608 in Fig. 6, and therefore the description thereof will be omitted.

[0050] In step S909, cloud management server 101 references the database to confirm that the queried registration ID has already been registered, and transmits the registration information together with information indicating that the ID has already been registered to cloud management server 102. This registration information is information stored in the database of cloud management server 101. Cloud management server 102 receives the registration information together with information indicating that the ID has already been registered from cloud management server 101.

[0051] In step S910, cloud management server 102 stores the registration information received from cloud management server 101 in its own database. In step S911, cloud management server 102 recognizes which server it should have been connected to based on communication from cloud management server 101, and notifies cloud management server 101 of the completion of registration. In step S913, in response to receiving the registration completion notification, cloud management server 101 notifies client device 104 of the connection destination, indicating that the connection destination is cloud management server 102. In step S914, once cloud management server 101 has completed notifying client device 104 of the connection destination, it deletes the registration information for identifying client device 104 that is stored in its own database.

[0052] In step S912, in response to the completion of the registration completion notification to cloud management server 101, cloud management server 102 returns a registration completion response to client device 105. Upon receiving this response, client device 105 displays a registration completion screen on a web page and notifies the user that the registration process has been successfully completed.

[0053] 10 is a diagram showing the configuration after the transfer and notification of registration information is completed in Example 2. According to the series of processes described above, it becomes possible to transfer registration information from cloud management server 101 to cloud management server 102 and complete all communications of client device 104 within the system in country 106.

[0054] The protocol used for communication can be HTTP, MQTT, XMPP, etc., and there are no restrictions on the combination. HTTP is an abbreviation for Hypertext Transfer Protocol. MQTT is an abbreviation for Message Queuing Telemetry Transport. XMPP is an abbreviation for Extensible Messaging and Presence Protocol.

[0055] <Example 3> Next, a third embodiment of the present invention will be described. In the second embodiment, the cloud management server 101 receives an inquiry about registration information from the cloud management server 102, and transfers only the information of the client device 104 registered in the cloud management server 101. In the third embodiment, a case where there is registration information of the cloud service 110 to be migrated will be described with reference to FIG. 11. FIG. 11 is a diagram showing a sequence according to the third embodiment. The cloud service 109 is an example of a first cloud service. The cloud service 110 is an example of a second cloud service. The cloud service 111 is an example of a third cloud service. The cloud service 110 and the cloud service 111 are deployed in different countries, but are the same service. The cloud service 109 is a service deployed in the country 106. The cloud service 110 is a service deployed in the country 107. The cloud service 111 is a service deployed in the country 106.

[0056] The processes from step S1101 to step S1103 are the same as the processes from step S601 to step S603 in the first embodiment of Fig. 6. In step S1104, the client device 105 inputs a registration ID to the cloud service 109 in response to a user operation.

[0057] In step S1105, cloud service 109 inputs a registration ID to cloud management server 102. In step S1106, cloud management server 102 decrypts the input registration ID and verifies the country that issued the registration ID (verifies the region). From the country information included in the input registration ID, cloud management server 102 recognizes that this registration ID was issued by cloud management server 101 in country 107. In step S1107, cloud management server 102 queries cloud management server 101 that issued the input registration ID for registration information.

[0058] In step S1108, cloud management server 101 references the database to confirm that the queried registration ID has already been registered, and transmits information to that effect to cloud management server 102. Cloud management server 102 receives the information to the effect that the registration has already been performed from cloud management server 101.

[0059] In step S1109, the cloud management server 102 returns information indicating success to the cloud service 109. In step S1110, the cloud service 109 returns information indicating success to the client device 105.

[0060] In step S1111, cloud management server 102 transmits a request to cloud management server 101 to transfer the registration information. In step S1112, if there is a registered service, cloud management server 101 returns information indicating success to cloud management server 102. Furthermore, cloud management server 101 performs a process to transfer the registration information of the services registered in cloud management server 101. That is, in step S1113, cloud management server 101 instructs cloud service 110 to transfer the registration information. This transfer instruction is an instruction to transfer the registration information of client device 104 to cloud service 111. The process of step S1113 is an example of a means for the second cloud management server to instruct the second cloud service to transfer the registration information of the first client device to the third cloud service.

[0061] In step S1114, the cloud service 110 checks the target country in the transfer instruction of the registration information. The process of step S1114 is an example of a means for checking the deployment status of the service provided by the cloud service 110 in the country 106 in which the cloud service 111 is deployed. In step S1115, the cloud service 110 transfers the registration information to the cloud service 111 that exists in the country in which the cloud management server 102 is installed. At that time, if it is determined based on the check result of step S1114 that a child service linked to the cloud service 110 is a non-target country in the country in which the cloud service 111 is deployed, the registration information is transferred with the linkage of the child service released. The process of step S1115 is an example of a means for transferring the registration information of the client device 104 in the cloud service 110 to the cloud service 111 based on the check result of step S1114.

[0062] In step S1116, the cloud service 111 registers the registration information in the database. In step S1117, the cloud service 111 returns a success response to the cloud service 110.

[0063] In step S1118, the cloud service 110 deletes the registration information to prevent unnecessary data from remaining and to prevent personal information from being leaked due to an unexpected incident. The process of step S1118 is an example of a means for deleting the registration information of the client device 104 in the cloud service 110 in response to the completion of the migration.

[0064] After that, in step S1119, cloud service 111 notifies cloud management server 102 of migration completion. In step S1120, cloud management server 102 notifies cloud management server 101 of registration success. The process of step S1120 is an example of a means for cloud management server 102 to notify cloud management server 101 of registration success in response to completion of migration.

[0065] Next, in step S1121, cloud management server 101 issues a connection destination instruction to client device 104. The process in step S1121 is an example of a means for issuing a connection destination instruction to client device 104 to change the connection destination from cloud management server 101 to cloud management server 102 in response to receiving a registration success notification. Thereafter, client device 104 communicates with cloud management server 102, cloud service 109, and cloud service 111.

[0066] 12 is a diagram showing the configuration after the transfer and notification of the registration information is completed in the embodiment 3. According to the series of processes described above, the registration information is transferred from the cloud management server 101 to the cloud management server 102, and the client device 104 can use the cloud services 109 and 111.

[0067] <Example 4> Next, a fourth embodiment of the present invention will be described. In the second embodiment, cloud management server 102 makes a registration information inquiry to cloud management server 101. When cloud management server 102 receives a "registered" response from cloud management server 101, cloud management server 102 immediately registers the registration information. Here, a method of dealing with a case where registration of the registration information is not immediately performed or fails due to some factor will be described as the fourth embodiment with reference to FIG. 13.

[0068] Step S1301 in Fig. 13 is the same process as S909 in Fig. 9. In step S1302, cloud management server 102 attempts to register registration information, but it is assumed here that the registration fails. In step S1303, cloud management server 102 returns a registration completion to client device 105 even if registration fails.

[0069] In step S1304, client device 104 transmits data to cloud management server 101 through normal use. In step S1305, cloud management server 101 updates the registration information in the database based on the received data. In step S1306, cloud management server 101 returns a success response to client device 104.

[0070] In step S1307, cloud management server 101, which holds country information for cloud management server 102 in its database, sends the updated registration information to cloud management server 102 for synchronization. In step S1308, cloud management server 102 performs synchronization processing upon receiving the registration information so that there is no difference with the state held by cloud management server 101. The registration information can be synchronized each time, after a certain number of updates have accumulated, or at predetermined time intervals, and there is no restriction on the operation. In step S1309, if cloud management server 102 has successfully received the registration information, it returns a success response to cloud management server 101.

[0071] Even after the above-mentioned processing is executed, cloud management server 102 executes registration processing of the registration information in step S1310. When the registration processing is completed in step S1311, cloud management server 102 transmits a registration completion notification to cloud management server 101.

[0072] Cloud management server 102 may execute the registration information registration process of step S1310 each time synchronization data is received in step S1307. Cloud management server 102 may execute the registration information registration process of step S1310 periodically, like polling processing, after receiving "registered" in step S1301. Cloud management server 102 may execute the registration information registration process at any time, and there are no limitations on the method.

[0073] In step S1312, in response to receiving the registration completion notification from cloud management server 102, cloud management server 101 sends a connection destination notification to client device 104 indicating that the connection destination is cloud management server 102.

[0074] In step S1313, when the cloud management server 101 has completed the notification to the client device 104, it deletes the registration information for identifying the client device 104 that it owns. This prevents unnecessary data from remaining and prevents personal information from being leaked due to unforeseen circumstances.

[0075] (Other embodiments) The present invention can also be realized by a process in which a program for implementing one or more of the functions of the above-described embodiments is supplied to a system or device via a network or a storage medium, and one or more processors in a computer of the system or device read and execute the program. The present invention can also be realized by a circuit (e.g., ASIC) that implements one or more of the functions.

[0076] Although the preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and various modifications and changes are possible within the scope of the gist of the present invention.

[0077] The disclosure of this embodiment includes the following configurations and methods. (Configuration 1) a first client device located in a first country and having destination information for a second country; a second client device located in the first country; a first cloud management server installed in the second country; a second cloud management server installed in the first country; a first cloud service deployed in the first country; a second cloud service deployed in the second country; and a third cloud service that is deployed in the first country and provides the same service as the second cloud service; a means for instructing the second cloud service from the second cloud management server to transfer registration information of the first client device to the third cloud service; A means for checking the deployment status of the services provided by the second cloud service in the first country where the third cloud service is deployed; a means for transferring registration information of the first client device in the second cloud service to the third cloud service according to a result of the check; a means for notifying the first cloud management server of a successful registration from the second cloud management server in response to completion of the migration; a means for deleting registration information of the first client device in the second cloud service in response to completion of the migration; a means for instructing the first client device to change a connection destination from the first cloud management server to the second cloud management server in response to receiving the registration success notification; A system comprising: (Configuration 2) The transfer means transfers the registration information of the first client device in a state where the association of the child service with the second cloud service is released when the child service is not available in a country where the third cloud service is deployed. 2. The system according to configuration 1, (Configuration 3) means for acquiring a registration ID of the first client device from the first cloud management server installed in the second country, which is a country indicated by destination information held by the first client device; means for registering the first client device with the first cloud service using the registration ID; 3. The system according to claim 1 or 2, comprising: (Configuration 4) The registration ID includes information about the country in which the first cloud management server is installed. 4. The system according to configuration 3. (Configuration 5) The first client device is an image processing device, and the second client device is an information processing device. 5. The system of any one of configurations 1 to 4. (Method 1) a first client device located in a first country and having destination information for a second country; a second client device located in the first country; a first cloud management server installed in the second country; a second cloud management server installed in the first country; a first cloud service deployed in the first country; a second cloud service deployed in the second country; and a third cloud service deployed in the first country and providing the same service as the second cloud service, sending an instruction from the second cloud management server to the second cloud service to transfer registration information of the first client device to the third cloud service; checking the deployment status of the services provided by the second cloud service in the first country in which the third cloud service is deployed; migrating registration information of the first client device in the second cloud service to the third cloud service according to a result of the check; sending a registration success notification from the second cloud management server to the first cloud management server in response to completion of the migration; deleting registration information of the first client device in the second cloud service in response to completion of the migration; in response to receiving the registration success notification, issuing a connection destination instruction to the first client device to change a connection destination from the first cloud management server to the second cloud management server; The method according to claim 1, further comprising: [Explanation of symbols]

[0078] 101 Cloud Management Server 102 Cloud Management Server 104 Client device 105 Client device

Claims

1. a first client device located in a first country and having destination information for a second country; a second client device located in the first country; a first cloud management server installed in the second country; a second cloud management server installed in the first country; A first cloud service deployed in the first country; a second cloud service deployed in the second country; A third cloud service that is deployed in the first country and provides the same service as the second cloud service; a means for instructing the second cloud service from the second cloud management server to transfer registration information of the first client device to the third cloud service; A means for checking the deployment status of the services provided by the second cloud service in the first country where the third cloud service is deployed; a means for transferring registration information of the first client device in the second cloud service to the third cloud service according to a result of the check; a means for notifying the first cloud management server of a successful registration from the second cloud management server in response to completion of the migration; a means for deleting registration information of the first client device in the second cloud service in response to completion of the migration; a means for instructing the first client device to change a connection destination from the first cloud management server to the second cloud management server in response to receiving the registration success notification; A system comprising:

2. The transfer means transfers the registration information of the first client device in a state where the association of the child service with the second cloud service is released when the child service is in a non-target country among countries in which the third cloud service is deployed.

2. The system of claim 1 .

3. means for acquiring a registration ID of the first client device from the first cloud management server installed in the second country, which is a country indicated by destination information held by the first client device; means for registering the first client device with the first cloud service using the registration ID; 2. The system of claim 1, further comprising:

4. The registration ID includes information about the country in which the first cloud management server is installed.

4. The system of claim 3.

5. The first client device is an image processing device, and the second client device is an information processing device.

2. The system of claim 1 .

6. a first client device located in a first country and having destination information for a second country; a second client device located in the first country; a first cloud management server installed in the second country; a second cloud management server installed in the first country; A first cloud service deployed in the first country; a second cloud service deployed in the second country; a third cloud service deployed in the first country and providing the same service as the second cloud service, sending an instruction from the second cloud management server to the second cloud service to transfer registration information of the first client device to the third cloud service; checking the deployment status of the services provided by the second cloud service in the first country in which the third cloud service is deployed; migrating registration information of the first client device in the second cloud service to the third cloud service according to a result of the check; sending a registration success notification from the second cloud management server to the first cloud management server in response to completion of the migration; deleting registration information of the first client device in the second cloud service in response to completion of the migration; in response to receiving the registration success notification, issuing a connection destination instruction to the first client device to change a connection destination from the first cloud management server to the second cloud management server; The method according to claim 1, further comprising:

Images