Information processing system, and method for controlling information processing system

Abstract

To make controllable linking of master information related to management of an article in a more suitable mode, in a situation where a transition of information on the article is made between a plurality of groups.SOLUTION: A transition tool 102 determines whether first master information for managing information on an article in a first group, and second master information related to management of information on a common article, are present in a second group. When determining that the second master information is present in the second group, the transition tool 102 changes the first master information to be linked to the information on the article to the second master information, and when determining that the second master information is not present in the second group, links the first master information to the second group. When linking the first master information to the second group, the transition tool 102 restricts newly linking the first master information to the information on the article.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present disclosure relates to an information processing system and a method for controlling the information processing system.

Background Art

[0002] In recent years, for the management of devices such as printers and multifunction peripherals, there are various services such as data backup services, consumable management / ordering services, print performance collection / reporting services, etc. In such services, devices of multiple customers are registered so that a service provider can manage these devices. Also, these services may be provided as a cloud service system. When providing services such as those exemplified above, a multi-region method may be applied in which servers are constructed in each of a plurality of countries or regions and these servers are operated in cooperation. Patent Document 1 discloses a technique that enables a user to continue using a device in an integrated group even when a plurality of groups are integrated in a situation where devices are managed in each of a plurality of groups, such as in the multi-region method. Also, when providing services such as those exemplified above, a method of managing by associating management information called master information with a device to be managed and consumables used in the device may be applied. Such a management method using master information may also be applied to a system to which the multi-region method is applied.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In a system to which a multi-region method is applied, in a situation where, due to the abolition of some regions or the like, information on articles such as products and consumables managed in those some regions is assumed to be transferred to other regions. When a management method using master information is applied to such a system, it may be necessary to review the linking of the master information when information on articles is transferred between regions.

[0005] In view of the above problems, an object of the present invention is to enable the linking of master information related to the management of an article to be controlled in a more suitable manner in a situation where information on the article is transferred between a plurality of groups.

Means for Solving the Problems

[0006] An information processing system according to the present invention is an information processing system that transfers information on an article managed as a distribution target in a first group to a second group different from the first group, and includes a first master information for managing information on the article in the first group, and a determination means for determining whether second master information related to the management of information on a common article exists in the second group. When the determination means determines that the second master information exists in the second group, a transfer means for changing the linking to the information on the article from the first master information to the second master information, and when the determination means determines that the second master information does not exist in the second group, a transfer means for linking the first master information to the second group, and a restriction means for restricting linking the first master information to information on a new article when the first master information is linked to the second group by the transfer means.

Effects of the Invention

[0007] According to the present invention, in a situation where information on an article is transferred between a plurality of groups, it is possible to control the linking of master information related to the management of the article in a more suitable manner.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Modes for Carrying Out the Invention

[0009] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the present specification and drawings, components having substantially the same functional configuration are denoted by the same reference numerals, and redundant description is omitted.

[0010] First, in order to make the technology according to the present disclosure easier to understand, an overview of the multi-region method and master information will be described. The multi-region method is a method of constructing multiple servers around the world and making them operate in cooperation. In an environment where the multi-region method is applied, various information regarding articles (for example, products, consumables, etc.) that are managed as distribution targets in each country or region, such as information on the devices of service users, is managed by a server group constructed in the relevant country or region. As a specific example, information regarding various articles associated with Japanese customers is managed by a server group constructed in Japan. Thus, the unit of the server group that manages data such as the information regarding the articles exemplified above is also referred to as a region. In addition, there is a method of associating and managing master information with articles to be distributed, such as devices distributed as products like image forming apparatuses, and consumables used in such devices. In the present disclosure, the master information corresponds to information for centrally managing articles such as devices and consumables applied to such devices (particularly, articles managed as distribution targets).

[0011] Examples of the master information include information regarding the model of the target article (for example, a device), the product name of the article, consumables used in articles (devices, etc.) distributed as products, and error codes. The model master corresponds to management information in which information regarding the model of a device (article) for which various models can be released, such as a printer or a multifunction device, is defined. For example, information such as whether the target device is a printer or a multifunction device, or whether it is a color device or a monochrome device can be defined in the model master. The product master corresponds to management information in which information for managing an article that can be distributed as a product, such as a printer or a multifunction device, is defined. Examples of information that can be defined in the product master include the product name and the release date to the market. The consumable master is information for managing consumables used in devices (articles) that are distributed as products such as printers and multifunction printers, etc., and is equivalent to management information in which information for managing the consumables is defined for articles that can be distributed individually from the device. As the consumable master, for example, information such as the name of the consumable, the type of the consumable (e.g., color in the case of toner), and which product the consumable is used for can be defined. The error code master is management information in which error information that may occur for each model is defined. Note that there are two types of master information: those that are globally and commonly managed, and those that are individually managed for each region. For example, information about models and error codes corresponds to information according to the characteristics of the target article (e.g., a device such as a multifunction printer) itself and can be uniquely defined globally. On the other hand, different situations can be assumed for products and consumables for each region. For example, even if it is the same device, the product name, etc. may be different depending on the specifications for each region. Factors that can lead to such a situation include, for example, the business policies of service-providing companies that oversee each region, and the trademark registration status in each country. As a specific example, it can be assumed that in one country, a device of the model "Model A" is sold under the product name "Printer A", and in another country, a device of the same model is sold under the product name "Printer Ax".

[0012] Master information may be effectively managed centrally in one place from the perspective of convenience even in a situation where a multi-region system is applied. By applying such a management method, for example, even when a region is added or separated, it is not necessary for the service operating in the new region to hold its own master information, and it becomes easy to always refer to the same master information.

[0013] On the other hand, in a system to which the multi-region method is applied, a situation may be assumed in which, along with the abolition of some regions, information on articles managed in those regions is transferred to other regions. When a management method using master information is applied to such a system, it may be necessary to review the linking of master information when information on articles is transferred between regions. As a specific example, when information is transferred from a source region (e.g., a region to be abolished) to a destination region (e.g., a region for integration), there may be a case where there is no master information regarding the management of articles similar to the articles to be transferred in the destination region. Also, even if the articles themselves are the same, a situation where the product names and the like differ depending on the tailoring for each region can be assumed. When reports such as aggregation information for each model and consumable remaining quantity data reports are provided to customers in the management service, if the product name of the device suddenly changes, it will cause confusion. Therefore, a case can be assumed where it is desired to provide reports to customers with the same product name as before. In such a use case, for example, when the same product does not exist in the destination region, it may be desirable to continue using the master information used in the source region for the management of the articles to be transferred (e.g., devices such as multifunction printers). On the other hand, the master information used in the source region is not used for management other than the articles to be transferred in the destination region, and becomes unnecessary master information for customers who have been under management in the destination region before the transfer. In addition, due to issues such as commercial law registration, a situation where information such as the product name registered in the master information used in the source region is referred to by existing customers in the destination region may not be desirable. In view of such a situation, in this embodiment, an example of a mechanism will be described that enables the linking of master information related to the management of an article to be controlled in a more suitable manner in a situation where information on the article is transferred between a plurality of groups.

[0014] Referring to FIG. 1, an example of the system configuration of the device management service according to an embodiment of the present disclosure will be described. The device management service 101 according to this embodiment is realized as a network service such as a so-called cloud service, and integrally provides various services related to device management. The device management service 101 is realized, for example, by servers provided in a plurality of regions operating in cooperation with each other. In the example shown in FIG. 1, a situation is shown where there are a region R1 that manages master information, and regions R2 and R3 that manage customer information and device registration information.

[0015] Region R1 plays a role of centrally managing master information. The migration tool 102 is a tool that operates on the server in region R1. In this embodiment, an example of the case where the migration tool 102 operates on the server in region R1 will be described, but the migration tool 102 may operate anywhere as long as it can communicate with the servers in each region. The information processing terminal 103 plays a role as a user interface for a user to give various instructions to the device management service 101. The information processing terminal 103 is equipped with, for example, a web browser, presents the WebUI provided by the device management service 101 to the user, and receives instructions from the user via the WebUI. Devices 104-1, 104-2, 104-3, and 104-4 (hereinafter also collectively referred to as device 104) indicate the devices to be managed by the device management service 101. Devices 104-1 and 104-2 indicate the devices owned by customer C1. Also, device 104-3 indicates the device owned by customer C2. Also, device 104-4 indicates the device owned by customer C3. Data related to customers C1 and C2 is managed in region R2. Also, data related to customer C3 is managed in region R3. The device 104 is connected to the device management service 101, and transmits the setting information and operation information of the device 104 to the device management service 101.

[0016] The network 105 is realized by a network that connects various network services and various devices, such as the Internet. The device management service 101 is published on a network such as the Internet and is communicably connected to the information processing terminal 103 and the device 104 via the network 105.

[0017] Referring to FIG. 2, an example of the hardware configuration of the information processing device in each region where the device management service 101 operates will be described. In the present embodiment, it is assumed that a plurality of information processing devices physically arranged in a region (for example, a country, etc.) corresponding to each region are used to construct and provide the device management service 101. Further, it is also possible to realize data management by one or more regions by one or more information processing devices arranged in one region.

[0018] The information processing device includes a CPU 201 that executes software stored in a hard disk drive (HDD) 210, which is a storage device. The CPU 201 comprehensively controls each hardware connected to the system bus 204. The memory 202 is a storage area that functions as the main memory and work area of the CPU 201. The network interface card (NIC) 203 exchanges data bidirectionally with other nodes via the network 105. The keyboard controller 205 controls the instruction input from the keyboard 206 provided in the information processing device. Note that, depending on the role of the information processing device, a configuration that does not include the keyboard controller 205 and the keyboard 206 may be applied. The display controller 207 performs control related to the display of information on a display module 208 configured by, for example, a liquid crystal display. Note that, depending on the role of the information processing device, a configuration that does not include the display controller 207 and the display module 208 may be applied. The disk controller 209 controls the operation of the HDD 210, which is a storage device.

[0019] Referring to FIG. 3, an example of the functional configuration of each region of the device management service 101 will be described. Each of the regions R1 to R3 has a control unit 301, a data storage unit 302, a communication unit 303, and a display unit 304. Each unit of each of the regions R1 to R3 is realized by the CPU 201 reading a program stored in the HDD 210 of the information processing device of each region where the device management service 101 operates into the memory 202 and executing it. The control unit 301 is a software module that receives instructions related to the execution of various processes and executes the processes according to the instructions. The data storage unit 302 schematically shows the functions related to the storage of various data, and can be realized, for example, as a database configured in the HDD 210. The communication unit 303 is a software module for communicating with an external system via the network 105. The display unit 304 is a software module that provides a UI (for example, a WebUI) for operating the device management service 101 in response to requests from the information processing terminal 103 or the like.

[0020] Table A shown below shows an example of a product master management table related to the management of product master information, and is stored, for example, in the data storage unit 302 of region R1. As product master information, for example, a product primary ID to which a value is assigned for each product specification, a region, a product name, a product code for uniquely identifying the product itself, and a release date are managed. Also, in this embodiment, the product master information may include information indicated as "restrictions". Details of this "restriction" will be described separately later. The product primary ID is uniquely assigned by the device management service 101 at the time of master registration. The method of master registration will be described separately later.

[0021]

Table 1

[0022] In the example shown in Table A, products with the same product code of 001 are defined as the same product name "Printer P1" in regions R2 and R3 respectively. On the other hand, for products with the same product code of 002, although the products themselves are the same, they are defined as the product name "Printer P2" in region R2 and "Printer 002" in region R3.

[0023] Table B shown below shows an example of a consumable master management table related to the management of consumable master information, and is stored, for example, in the data storage unit 302 of region R1. As the information of the consumable master, for example, a consumable primary ID to which a value is assigned for each specification of the consumable, a region, a consumable name, a consumable code that uniquely identifies the consumable itself, the primary ID of the product for which the consumable is used, and color information, etc. are managed. Also, in the present embodiment, the information of the consumable master may include information indicated as "restriction". Details of this "restriction" will be described separately later. The consumable primary ID is uniquely assigned by the device management service 101 at the time of corresponding master registration. The method of master registration will be described separately later.

[0024]

Table 2

[0025] In the example shown in Table B, consumables CS0011, CS0012, and CS0013 are registered as consumables for product MA001. Also, consumable CS0021 is registered as a consumable for product MA002, and consumables CS0031 and CS0032 are registered as consumables for product MA003. For consumables with the same consumable code of 0012, although the consumables themselves are the same, they are defined as the consumable name "C0012 Black" in region R2 and "0012 Black" in region R3.

[0026] The product master and the consumable master shall be configured to be addable upon an instruction from the information processing terminal 103. Regarding the addition of the master, for example, the display unit 304 of the server in region R1 displays a WebUI for master addition upon an instruction from the information processing terminal 103, and the addition of the master information is implemented by individually inputting or importing the master information via the WebUI.

[0027] Table C shown below shows an example of the device management table, and in the data storage unit 302 of each region, the device information to be managed by the region is stored. As the device information, for example, a device ID that uniquely identifies the device, a customer ID that uniquely identifies the customer to which the device belongs, a device name, an IP address, etc. are managed. Also, as the device information, a product primary ID indicating which product the device is, and a consumable primary ID indicating the consumables used by the device are associated and managed. The device ID is uniquely assigned by the device management service 101 at the time of device registration. The method of device registration will be described separately later.

[0028]

Table 3

[0029] Table C shows an example of the device information stored in the data storage unit 302 of region R2. In the example shown in Table C, only one consumable is associated with the device, but in the case of a color machine, a plurality of consumables for each color are associated and stored in the consumable primary ID column. In addition to the examples shown above, information referred to when providing the service of the device management service may also be stored together. As a specific example, when a consumable ordering service is used, information such as the delivery destination may also be stored together. In the example shown in Table C, device 104-1 is owned by customer C1, the product is MA001, and CS0011 is used as a consumable. Also, device 104-2 is owned by customer C1, the product is MA001, and CS0012 is used as a consumable. Further, device 104-3 is owned by customer C2, the product is MA002, and CS0021 is used as a consumable. Device registration is executed according to an instruction from the information processing terminal 103. Regarding device registration, for example, the display unit 304 of the server in each region displays a WebUI for device registration according to an instruction from the information processing terminal 103, and device information is input via the WebUI to implement it.

[0030] Here, with reference to FIGS. 4 and 5, an example of the processing of the device management service according to the present embodiment will be described by focusing on the processing when region R2 is abolished and integrated into region R3. In the examples shown in FIGS. 4 and 5, the abolished region R2 corresponds to the source region of the information on the article to be transferred, and the integrated region R2 corresponds to the destination region of the information on the article. Also, in this case, the source region, region R2, corresponds to an example of the first group, and the destination region, region R3, corresponds to an example of the second group.

[0031] First, with reference to FIG. 4, an example of the processing when transferring the information on the articles managed by the master information of the abolished region to the master information of the integration destination region will be described. The series of processes shown in FIG. 4 corresponds to the transfer process of the information on the articles managed by the master of the abolished region. For example, the transfer tool 102 starts upon receiving an instruction from the information processing terminal 103 by a user corresponding to the administrator of the information transfer between regions.

[0032] In S401, the transfer tool 102 acquires the product master information with the region being R2 from the product master management table (Table A). In S402, the migration tool 102 matches one product primary ID among the product master information obtained in S401 with the product primary ID associated with the device stored in the device management table (Table C) of region R2. Thereby, the migration tool 102 determines whether the corresponding product master information is being used. If in S402 the migration tool 102 determines that the corresponding product master information is not being used, that is, if it determines that there is no device (article distributed as a product) associated with the corresponding product master information, the process proceeds to S403. On the other hand, if in S402 the migration tool 102 determines that the corresponding product master information is being used, that is, if it determines that there is a device (article distributed as a product) associated with the corresponding product master information, the process proceeds to S404.

[0033] In S403, the migration tool 102 deletes the corresponding product master information. Also, if there is consumable master information associated with the corresponding product master information, the migration tool 102 also deletes the consumable master information. In the examples shown in Table A and Table C, the product master information with the product primary ID of MA999 has no associated device, so it will be deleted without migration. Also, among the consumable master information stored in the consumable master management table (Table B), the consumable CS9999 associated with the product primary ID of MA999 will also be deleted without migration.

[0034] In S404, the migration tool 102 searches the product master management table (Table A) and matches the corresponding product master information with the product master information of region R3. Thereby, the migration tool 102 determines whether the same product master information (in other words, the product master information used for managing information regarding a product that is the same article as the source of migration) exists in the destination region R3. For the determination of whether they are the same or not, in this embodiment, it is made based on whether the product name and product code are the same. If the migration tool 102 determines in S404 that the same product master information exists in the destination region R3, the process proceeds to S405. On the other hand, if the migration tool 102 determines in S404 that the same product master information does not exist in the destination region R3, the process proceeds to S407. In this case, the product master information associated with the source region R2 corresponds to an example of the first master information, and the product master information identical to the first master information associated with the destination region R3 corresponds to an example of the second master information.

[0035] In S405, the migration tool 102 creates a mapping between the product primary ID of the corresponding product master information in the region to be abolished and the product primary ID of the product master information at the integration destination. In the examples shown in Table A and Table C, the product master with the product primary ID of MA001 corresponds to the product master information to be integrated. That is, in the product master information with the product primary ID of MA001, there are associated devices 104-1 and 104-2, and MA003 of the same product master information exists in region R3. Table D shown below is an example of a product mapping table and is stored in the data storage unit 302 of region R1. The migration tool 102 stores the mapping created in S405 in the product mapping table.

[0036]

Table 4

[0037] In S406, the migration tool 102 deletes the corresponding product master information in the region where the mapping was created.

[0038] In S407, the migration tool 102 changes the region of the corresponding product master information and saves it as restricted master information. Specifically, the migration tool 102 rewrites the region of the corresponding product master information in the product master management table (Table A) to the integration destination region and changes the value of the "Restriction" item to 1. The "Restriction" item corresponds to a flag indicating whether the corresponding master is a restricted master. In the case of restricted master information, the value 1 is set, and in the case of other master information, the value 0 is set. In the examples shown in Table A and Table C, the product master information with the product primary ID of MA002 corresponds to an example of restricted master information. That is, as exemplified by the product master information with the product primary ID of MA002, when there is an associated device 104-3 and the same product master information does not exist in region R3, it corresponds to restricted master information. The migration tool 102 changes the region of MA002 to R3 and changes the value of "Restriction" to 1. As a result, the region to which the product master information of MA002 is associated (in other words, the region in which the product master is managed) is changed from the region R2 to be abolished to the integration destination region R3.

[0039] In S408, the migration tool 102 acquires the consumable master information associated with the corresponding product master information being processed from the consumable master management table (Table B). In S409, the migration tool 102 matches one consumable primary ID among the consumable master information acquired in S408 with the consumable primary ID associated with the device stored in the device management table (Table C). Thereby, the migration tool 102 determines whether the corresponding consumable master information is being used. If the migration tool 102 determines in S409 that the corresponding consumable master information is not being used, that is, if it determines that there is no article (consumable) associated with the corresponding consumable master information, the process proceeds to S410. On the other hand, if the migration tool 102 determines in S409 that the corresponding consumable master information is being used, that is, if it determines that there is an article (consumable) associated with the corresponding consumable master information, the process proceeds to S411.

[0040] In S410, the migration tool 102 deletes the corresponding consumable master. In the examples shown in Table B and Table C, since there is no associated item (consumable) for the consumable master information with the consumable primary ID of CS0013, it is deleted without migration.

[0041] In S411, the migration tool 102 searches the consumable management table (Table B) and matches the corresponding consumable master information with the consumable master information with the region being R3. Thereby, the migration tool 102 determines whether the same consumable master information (in other words, the consumable master information used for managing information regarding consumables that are the same items as the source) exists in the destination region R3. For the determination of whether they are the same, in this embodiment, it shall be made based on whether the consumable name and the consumable name code are the same. If the migration tool 102 determines in S411 that the same consumable master information exists in the destination region R3, the process proceeds to S412. On the other hand, if the migration tool 102 determines in S411 that the same consumable master information does not exist in the destination region R3, the process proceeds to S414. Note that in this case, the consumable master information associated with the source region R2 corresponds to an example of the first master information, and the consumable master information that is the same as the first master information associated with the destination region R3 corresponds to an example of the second master information.

[0042] In S412, the migration tool 102 creates a mapping between the consumable primary ID of the corresponding consumable master information in the abolished region and the consumable primary ID of the consumable master information in the destination. In the example shown in Table B, the consumable master information with the consumable primary ID of CS0011 corresponds to the consumable master information to be integrated. That is, in the consumable master information with the consumable primary ID of CS0011, CS0031 of the same consumable master information exists in region R3. Table E shown below is an example of a consumable mapping table and is stored, for example, in the data storage unit 302 of region R1. The migration tool 102 stores the mapping created in S412 in the consumable mapping table.

[0043]

Table 5

[0044] In S413, the migration tool 102 deletes the corresponding consumable master information of the decommissioned region for which the mapping was created.

[0045] In S414, the migration tool 102 changes the region of the corresponding consumable master information and stores it as restricted master information. As a result, the region to which the corresponding consumable master information is linked (in other words, the region in which the corresponding consumable master information is managed) is changed from the decommissioned region to the integration destination region, and it is managed as restricted master information in the integration destination region. Specifically, the migration tool 102 rewrites the region of the corresponding consumable master in the consumable master management table (Table B) to the integration destination region and changes the value of the "restriction" item to 1. The "restriction" item corresponds to a flag indicating whether the corresponding master information is restricted master information. In the case of restricted master information, the value is set to 1, and in the case of other master information, the value is set to 0. In the example shown in Table B, the consumable master with the consumable primary ID of CS0012 corresponds to an example of restricted master information. That is, as exemplified by the consumable master information with the consumable primary ID of CS0012, when the same consumable master information does not exist in region R3, it corresponds to restricted master information. The migration tool 102 changes the region of CS0012 to R3 and changes the value of "restriction" to 1.

[0046] In S415, the migration tool 102 determines whether the product master information associated with the corresponding consumable master information being processed exists in the product mapping table (Table D). When the migration tool 102 determines that the product master information associated with the corresponding consumable master information being processed exists in the product mapping table, the process proceeds to S416. On the other hand, when the migration tool 102 determines that the product master information associated with the corresponding consumable master information being processed does not exist in the product mapping table, the process proceeds to S417.

[0047] In S416, the migration tool 102 changes the association of the product master information of the corresponding consumable master to the product master information of the integration destination region. In the examples shown in Table B and Table D, for example, product MA001 associated with a consumable with a consumable primary ID of CS0012 exists in the product mapping table. In this case, the product primary ID associated with the consumable of CS0012 is changed to MA003 in the product master information of the integration destination region.

[0048] In S417, the migration tool 102 determines whether all the processing of the series of consumable master information acquired in S408 has been completed, that is, whether there is any consumable master information for which the processing has not been executed among the series of consumable master information acquired in S408. When the migration tool 102 determines in S417 that there is consumable master information for which the processing has not been executed, the process proceeds to S409. In this case, the processing from S409 onwards is executed again for the consumable master information for which the processing has not been executed. On the other hand, when the migration tool 102 determines in S417 that there is no consumable master information for which the processing has not been executed, that is, when it determines that all the processing of the series of consumable master information acquired in S408 has been completed, the process proceeds to S418.

[0049] In S418, the migration tool 102 determines whether all the processing of the series of product master information acquired in S401 has been completed, that is, whether there is any product master information for which the processing has not been executed among the series of product master information acquired in S401. If the migration tool 102 determines in S418 that there is product master information for which the processing has not been executed, the process proceeds to S402. In this case, the processing after S402 is executed again for the product master information for which the processing has not been executed. On the other hand, if the migration tool 102 determines in S418 that there is no product master information for which the processing has not been executed, that is, if it determines that the processing of the series of product master information acquired in S401 has all been completed, the process proceeds to S419. In S419, after the migration tool 102 returns information indicating that the migration process has been completed to the information processing terminal 103, the series of processes shown in FIG. 4 is terminated.

[0050] Next, with reference to FIG. 5, an example of the processing when migrating customers and devices in the abolition region to the integration destination region will be described. It is assumed that the master migration process described with reference to FIG. 4 has been completed before the migration of customers and devices by the series of processes shown in FIG. 5. The series of processes shown in FIG. 5 corresponds to the migration process of customers and devices in the abolition region. For example, the migration tool 102 starts upon receiving an instruction from the information processing terminal 103 by a user corresponding to the administrator of the migration of customers and devices.

[0051] Table F shown below is an example of a customer management table, and customer information to be managed by the region is stored in the data storage unit 302 of each region. As customer information, for example, a customer ID that uniquely identifies a customer and a customer name are managed.

[0052]

Table 6

[0053] Table F shows an example of customer information stored in the data storage unit 302 of region R2. In the example shown in Table F, it is shown that customers with customer IDs C1 and C2 are managed in region R2.

[0054] In S501, the migration tool 102 obtains customer information managed in region R2 from the customer management table (Table F) stored in the data storage unit 302 of region R2, which is the region to be abolished. In S502, the migration tool 102 registers the customer information obtained in S501 in the customer management table stored in the data storage unit 302 of region R3, which is the integration destination region. In S503, the migration tool 102 deletes the customer information migrated to the integration destination region from the customer management table of region R2. In S504, the migration tool 102 obtains device information managed in region R2 from the device management table (Table C) stored in the data storage unit 302 of region R2.

[0055] In S505, for one device among the device information obtained in S504, the migration tool 102 determines whether the product primary ID of the associated product master information exists in the abolished region product primary ID of the product mapping table (Table D). If the migration tool 102 determines in S505 that the product primary ID of the target product master information exists in the abolished region product primary ID of the product mapping table, the process proceeds to S506. In S506, the migration tool 102 changes the product master information associated with the corresponding device to the integration destination region product primary ID corresponding to the corresponding abolished region product primary ID. On the other hand, if the migration tool 102 determines in S505 that the product primary ID of the target product master information does not exist in the abolished region product primary ID of the product mapping table, the process proceeds to S507. In this case, the association of the product master information will not be changed. In the examples shown in Table C and Table D, the product primary ID associated with the device with device ID 104-1 is MA001, and the MA001 is associated with MA003 in the integration destination region. Therefore, the device with device ID 104-1 has its association newly changed to MA003.

[0056] In S507, the migration tool 102 determines whether the consumable primary ID of the consumable master information associated with the device being processed exists in the obsolete region consumable primary ID of the consumable mapping table (Table E). If the migration tool 102 determines in S507 that the consumable primary ID of the consumable master information targeted exists in the obsolete region consumable primary ID of the consumable mapping table, the process proceeds to S508. In S508, the migration tool 102 changes the consumable master information associated with the corresponding device to the integration destination region consumable primary ID corresponding to the corresponding obsolete region consumable primary ID. On the other hand, if the migration tool 102 determines in S507 that the consumable primary ID of the consumable master information targeted does not exist in the obsolete region consumable primary ID of the consumable mapping table, the process proceeds to S509. In this case, the association of the consumable master information is not changed.

[0057] In S509, the migration tool 102 registers one device for which the confirmation of the master information to be associated has been completed in the device management table stored in the data storage unit 302 of region R3, which is the integration destination region. In S510, the migration tool 102 deletes the device information migrated to the integration destination region from the device management table in region R2.

[0058] In S511, the migration tool 102 determines whether all the processes for the series of device information acquired in S504 have been completed, that is, whether there is a device for which the process has not been executed. If the migration tool 102 determines in S511 that there is a device for which processing has not been executed, the process proceeds to S505. In this case, the processing from S505 onwards is executed again for the device for which processing has not been executed. On the other hand, if the migration tool 102 determines in S511 that there is no device for which processing has not been executed, the process proceeds to S512.

[0059] In S512, the migration tool 102 deletes the product mapping table (Table D) and the consumables mapping table (Table E) that are no longer needed. In S513, the migration tool 102 returns information indicating that the migration process has been completed to the information processing terminal 103, and then ends the series of processes shown in FIG.

[0060] In this embodiment, an example has been described in which a user who is an administrator of the region abolition process instructs the processes shown in Figures 4 and 5, causing the migration tool 102 to execute each process. However, the above is merely an example and does not necessarily limit the configuration and processes of the device management service according to this embodiment. As a specific example, a configuration may be applied in which the user specifies the abolition region and the integration destination region, causing the migration tool 102 to execute the processes shown in Figures 4 and 5 in a straight line.

[0061] Referring to FIG. 6, an example of a WebUI for registering a device to be managed with respect to the device management service 101 according to this embodiment will be described. When registering a device as a management target in region R3, a user who is an administrator of device registration makes a display request for the WebUI for device registration to the server in region R3 from the information processing terminal 103. In response to a request from the user via the information processing terminal 103, the display unit 304 of the server provides the WebUI for device registration to the user via the information processing terminal 103. When the display unit 304 detects that the registration button 606 has been pressed with information related to device registration entered in each input area of the WebUI, the display unit 304 transfers the information related to the device registration to the control unit 301 and instructs the control unit 301 to execute device registration. The control unit 301 stores the device information received from the display unit 304 in a device management table (Table C).

[0062] In the example shown in FIG. 6, input areas for receiving input of device information are provided corresponding to items of customer name, device name, IP address, product name, and consumable name respectively. Regarding the customer name, a list of a series of customer names stored in a customer management table (Table F) is displayed by a pull-down list 601. By selecting any one of the series of customer name candidates presented via the pull-down list 601, the selected customer name candidate is set as the registration target. Note that a customer ID corresponding to the selected customer name candidate is registered in the device management table (Table C). For the device name, any character string entered in the text box 602 is applied. The IP address is an address referred to when the device communicates with the device management service 101, and the address entered in the text box 603 is applied.

[0063] For product names and consumable names, input may be accepted via a text box, or a series of candidates registered in the master may be presented by a pull-down list, and a target candidate may be selected from among the series of candidates. In the example shown in FIG. 6, an example of the case where a product name or a consumable name is specified by a pull-down list is shown. For the product name, among the product master information registered in the product master management table (Table A), a list of product names registered in the product master information of region R3, which is the region for device registration, is displayed as candidate selection targets by the pull-down list 604. At this time, for the product names in the restricted product master information, they are excluded from the display targets by the pull-down list. By applying such control, it is possible to prevent a situation where the product master information of the abolished region is erroneously linked to a newly registered device. By selecting any one of the series of product name candidates presented via the pull-down list 604, the selected product name candidate is set as the registration target. In the device management table (Table C), the product primary ID corresponding to the selected product name is registered. For the consumable name, among the consumable master information registered in the consumable master management table (Table B), a list of consumable names in the consumable master information associated with the product selected in the pull-down list 604 is displayed as candidate selection targets by the pull-down list 605. At this time, for the consumable names in the restricted consumable master, they are excluded from the display targets by the pull-down list. By applying such control, it is possible to prevent a situation where the consumable master information of the abolished region is erroneously linked to a newly registered device. By selecting any one of the series of consumable name candidates presented via the pull-down list 605, the selected consumable name candidate is set as the registration target. In the device management table (Table C), the consumable primary ID corresponding to the selected consumable name is registered.

[0064] When registering a new device, as described above, the display of restricted master information in the pull-down lists for products and consumables was restricted. On the other hand, it is conceivable that the device management service 101 provides a WebUI for changing the registered device information. This is because, for example, a situation where only the IP address is changed among the information of the registered device can be assumed. In such a situation, it may be desirable to maintain the already associated restricted master information. Therefore, when restricted master information is already associated, only the corresponding restricted master may be displayed in the pull-down list, or it may be additionally displayed together with unrestricted master information. Also, the display of restricted master information not associated with the corresponding device should be restricted. By applying such control, it becomes possible to use the restricted master information already associated with the article information as it is. Also, for example, it becomes possible to handle the change of association in a situation where the consumables in the abolished region are used up and then changed to the consumables in the integration destination region. Also, in this case, while allowing the change of association to the unrestricted master information which is the consumables in the integration destination region, it is also possible to prevent the occurrence of a situation where other restricted master information is accidentally associated.

[0065] Next, with reference to FIGS. 7 and 8, an example of the processing of the device management service according to the present embodiment will be described, particularly focusing on the processing of deleting the master information of the abolished region that is no longer used. The master information of the abolished region in the present embodiment is not newly associated with the device in the integration destination region. Also, when there are no devices migrated from the abolished region or consumables used in the device, the master information becomes unnecessary. In such a situation, the data of the master information becomes unnecessary data in the system and may also be a factor that compresses the storage area. Therefore, it is desirable to delete it when it becomes unnecessary.

[0066] First, with reference to FIG. 7, an example of a process for changing the association of consumable master information will be described. When all the consumables in the abolished region that have been delivered to the customer have been used up, it is conceivable that consumables in the integration destination region will be delivered next. In such a case, it is desirable that the consumables associated with the device be changed to the consumables in the integration destination region. When changing the consumables associated with a device managed in region R3, the user who is the administrator of the consumable change makes a display request for the WebUI for device information change from the information processing terminal 103 to the server in region R3. In response to a request from the user via the information processing terminal 103, the display unit 304 of the server provides the user with the WebUI for device information change via the information processing terminal 103. The WebUI for device information change is a screen for receiving selection of a device for which information is to be changed and instructions regarding change of the information of the device. As a specific example, the WebUI for device information change displays a list of device information stored in the device management table (Table C) and accepts selection of a device included in the list. Then, the WebUI displays the information stored in the device management table for the device selected from the list and accepts instructions regarding change of the information. Note that the method of selecting consumables is assumed to be the same as that of the WebUI for device registration (FIG. 6).

[0067] In S701, when the display unit 304 receives an instruction to change the consumables used in the device, it notifies the control unit 301 of the corresponding device ID and the consumable primary ID of the changed consumables. The control unit 301 acquires the consumable primary ID associated with the corresponding device ID from the device management table (Table C). In S702, the control unit 301 acquires the consumable master information of the corresponding consumable primary ID from the consumable master management table (Table B) in region R1 via the communication unit 303.

[0068] In S703, the control unit 301 determines whether the consumable master information acquired in S702 is restricted master information. When the control unit 301 determines in S703 that the corresponding consumable master information is not restricted master information, the process proceeds to S706. In this case, in S706, the control unit 301 changes the consumable associated with the corresponding device to the changed consumable, and ends the series of processes shown in FIG. 7. On the other hand, when the control unit 301 determines in S703 that the corresponding consumable master information is restricted master information, the process proceeds to S704.

[0069] In S704, the control unit 301 searches for the consumable primary ID associated with the device stored in the device management table (Table C), and determines whether there is any other device associated with the corresponding consumable master information. When the control unit 301 determines in S704 that there is no other device associated with the corresponding consumable master information, the process proceeds to S705. In this case, it is possible to determine that the corresponding consumable has become unused. Therefore, in S705, the control unit 301 deletes the pre-change restricted consumable master information from the consumable master management table (Table B) in region R1 via the communication unit 303. On the other hand, when the control unit 301 determines in S704 that there is another device associated with the corresponding consumable master information, the process proceeds to S706. In this case, it is possible to determine that the corresponding consumable is still in use. Therefore, the process of S705 is skipped, and the pre-change restricted consumable master information is not deleted. Then, in S706, the control unit 301 changes the consumable associated with the corresponding device to the changed consumable, and ends the series of processes shown in FIG. 7.

[0070] Note that in this embodiment, an example has been described in which when the consumable to be used is changed to the consumable in the integration destination region, the association of the consumable is manually changed in the operation on the WebUI. However, the association of the consumable may be automatically changed in conjunction with the inventory management. Specifically, assuming that when the inventory of consumables in the decommissioned region during use reaches 0, the consumables in the integration destination region are switched, the consumables to be used next are set in advance and stored in the device management table (Table C). Furthermore, when the device management service 101 detects that the inventory of the corresponding consumables in the decommissioned region has actually reached 0, it may automatically change the association of the consumables of the device, and trigger a series of processes shown in FIG. 7 based on this change.

[0071] Referring to FIG. 8, an example of the process of deleting a device from the device management service 101 will be described. When a device is removed from the customer site or the like, it is desirable to delete the data of the corresponding device managed by the device management service 101. When deleting a device managed in region R3, the user who is the administrator of device deletion makes a display request for the WebUI for device deletion to the server in region R3 from the information processing terminal 103. In response to a request from the user via the information processing terminal 103, the display unit 304 of the server provides the user with the WebUI for device deletion via the information processing terminal 103. The WebUI for device deletion is, for example, a screen that displays a list of device information stored in the device management table (Table C) and accepts the designation of a device to be deleted from the list.

[0072] In S801, when the display unit 304 receives a device deletion instruction, it notifies the control unit 301 of the device ID of the deletion target. The control unit 301 acquires the product primary ID associated with the corresponding device ID from the device management table (Table C). In S802, the control unit 301 acquires the product master information of the corresponding product primary ID from the product master management table (Table A) in region R1 via the communication unit 303.

[0073] In S803, the control unit 301 determines whether the product master information acquired in S802 is restricted master information. If the control unit 301 determines in S803 that the corresponding product master information is not restricted master information, the process proceeds to S806. In this case, in S806, the control unit 301 deletes the corresponding device from the device management table (Table C) and ends the series of processes shown in FIG. 8. On the other hand, if the control unit 301 determines in S803 that the corresponding product master information is restricted master information, the process proceeds to S804.

[0074] In S804, the control unit 301 searches for the product primary ID associated with the device stored in the device management table (Table C) and determines whether the corresponding product master information is associated with a device other than the device to be deleted. If the control unit 301 determines in S804 that the corresponding product master information is associated with a device other than the device to be deleted, the process proceeds to S806. In this case, in S806, the control unit 301 deletes the corresponding device from the device management table (Table C) and ends the series of processes shown in FIG. 8. On the other hand, if the control unit 301 determines in S804 that the corresponding product master information is not associated with a device other than the device to be deleted, the process proceeds to S805. In this case, since the restricted master information will not be newly associated with a device, it can be determined that the master information is unnecessary. Therefore, in S805, the control unit 301 deletes the corresponding product master information from the product master management table (Table A) in region R1 via the communication unit 303. Also, the control unit 301 deletes the consumable master information associated with the corresponding product master information from the consumable master management table (Table B). Then, in S806, the control unit 301 deletes the corresponding device from the device management table (Table C) and ends the series of processes shown in FIG. 8.

[0075] In the present embodiment, an example of the case where the master is managed in units of regions assuming countries or regions has been described. However, the unit for managing the master is not limited to the unit of region. As a specific example, when different masters are used for each service provider company, the master may be managed with the service provider company as the unit of group.

[0076] Also, in the present embodiment, an example of the case where the master information of the abolished region is processed as restricted master information has been described. However, the conditions for treating it as restricted master information are not limited. For example, even when the product name of a device that has already been sold is changed, it is possible to apply the mechanism of restricted master information. As a specific example, according to the policy of the service provider company, a case where the brand name of the device is renewed can be considered. In such a situation, even if the content is the same product, the name may be changed. For example, a situation can be assumed where a device that has been sold under the product name "Printer A" is sold under the product name "MULTI Device A". In such a situation, for new customers, it is sold under the latter name, but for customers who already use the corresponding device, it may be desirable to use the existing name when handling the corresponding device in order to prevent confusion. In such a case, it is advisable to register the master after the name change separately and change the existing master to a restricted master. By applying such control, it becomes possible to provide reports and the like to existing customers who already use the corresponding device based on the information of the restricted master. Also, in this case, since the restricted master is restricted so that it is not linked to a new device, the old name is not referred to when managing the devices of new customers. Also, the above control is not limited to the case of products, and can be similarly applied to the case where the name of consumables is changed. Note that, similar to the case of region abolition, when it is determined that the restricted master is no longer used, the corresponding restricted master information will be deleted.

[0077] <Other Embodiments> The present invention can also be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or apparatus via a network or a storage medium, and causing one or more processors in a computer of the system or apparatus to read and execute the program. It can also be realized by a circuit (for example, ASIC) that realizes one or more functions.

[0078] The disclosure of this embodiment also includes the following systems and methods. (System 1) An information processing system for transferring information regarding an article managed as a distribution target in a first group to a second group different from the first group, the system including: first master information for managing information regarding the article in the first group; determination means for determining whether second master information related to management of information regarding a common article exists in the second group; transfer means for changing the association to the information regarding the article from the first master information to the second master information when it is determined by the determination means that the second master information exists in the second group, and for associating the first master information with the second group when it is determined that the second master information does not exist in the second group; and restriction means for restricting, when the first master information is associated with the second group by the transfer means, newly associating the first master information with information regarding the article. (System 2) The information processing system according to System 1, further including first deletion means for deleting the first master information when the first master information is not associated with the information regarding the article. (System 3) The first master information is master information for managing information regarding an article that is distributed as a product or information regarding a consumable used for another article that is distributed as a product, as information regarding the article. When all information regarding the article associated with the first master information linked to the second group by the transfer means is deleted from the system, the information processing system according to System 1 or 2, characterized by having second deletion means for deleting the first master information. (System 4) The first master information is master information for managing information regarding a consumable used for another article that is distributed as a product. The second deletion means deletes the first master information when all information regarding the consumable associated with the first master information linked to the second group by the transfer means is deleted from the system, or when all information regarding the other article for which the consumable is used is deleted from the system. The information processing system according to System 3. (System 5) When a selection of master information to be newly associated with information regarding an article is received, the restriction means controls so that the candidate for the master information does not include the first master information linked to the second group. The information processing system according to any one of Systems 1 to 4. (Method 1) A control method for an information processing system that transfers information about an article to be managed in a first group to a second group different from the first group, the method including: a determination step of determining whether second master information related to management of information about a common article exists in the second group, in addition to first master information for managing information about the article in the first group; a transfer step of changing the association to the information about the article from the first master information to the second master information when it is determined in the determination step that the second master information exists in the second group, and associating the first master information with the second group when it is determined that the second master information does not exist in the second group; and a restriction step of restricting newly associating the first master information with information about an article when the first master information is associated with the second group in the transfer step. A control method for an information processing system, characterized by including the above steps.

Explanation of Signs

[0079] 101 Device Management Service 102 Migration Tool

Claims

1. An information processing system that transfers information about an item managed as a distribution target in a first group to a second group different from the first group, a determination means for determining whether or not first master information for managing information about the items in the first group and second master information for managing information about a common item exist in the second group; a transition means for changing the link to information relating to the item from the first master information to the second master information when the determination means determines that the second master information exists in the second group, and for linking the first master information to the second group when the determination means determines that the second master information does not exist in the second group; and a restriction unit that restricts new association of the first master information with information relating to an item when the first master information is associated with the second group by the transfer unit; An information processing system comprising:

2. 2. The information processing system according to claim 1, further comprising a first deletion means for deleting the first master information when the first master information is not linked to information relating to the product.

3. the first master information is master information for managing, as the information about the item, information about an item distributed as a commodity or information about a consumable item used in another item distributed as a commodity, a second deletion means for deleting the first master information when all information relating to the item linked to the first master information linked to the second group is deleted from the system by the migration means; 2. The information processing system according to claim 1, wherein:

4. the first master information is master information for managing information about consumables used in other goods distributed as merchandise, The second deletion means deletes the first master information when all information about the consumable linked to the first master information linked to the second group is deleted from the system by the migration means, or when all information about the other goods in which the consumable is used is deleted from the system.

4. The information processing system according to claim 3, wherein:

5. 2. The information processing system according to claim 1, wherein the restriction means controls the selection of master information to be linked to new information relating to an item so that the first master information linked to the second group is not included in the candidates for the master information when the selection of master information to be linked to new information relating to an item is accepted.

6. A control method for an information processing system that transfers information about an item managed as a distribution target in a first group to a second group different from the first group, comprising: a determination step of determining whether or not first master information for managing information about the items in the first group and second master information for managing information about a common item exist in the second group; a transition step of changing the link to information related to the item from the first master information to the second master information when it is determined in the determination step that the second master information exists in the second group, and linking the first master information to the second group when it is determined that the second master information does not exist in the second group; a restriction step of restricting new association of the first master information with information relating to an item when the first master information is associated with the second group in the transfer step; 10. A method for controlling an information processing system, comprising:

Images