JP2023092055A - Electronic equipment, information processing device, information processing system, management method and program - Google Patents

Abstract

To lighten the load of work to register electronic equipment on an information processing device.SOLUTION: The present invention relates to electronic equipment capable of communicating with a first information processing device and a second information processing device, and the electronic equipment comprises: an instruction reception unit which receives a registration instruction including a registration number that the first information processing device issues from the second information processing device; and a registration request unit which sends a registration request including the registration number to the first information processing device in response to the registration instruction.SELECTED DRAWING: Figure 4

Description

The present invention relates to an electronic device, an information processing device, an information processing system, a management method and a program.

There is an information processing system in which an information processing device manages electronic devices via a communication network. In such an information processing system, one electronic device may be registered with and managed by a plurality of information processing apparatuses.

For example, in Patent Document 1, by registering a printing device registered with a first cloud print service with a second cloud print service, print data uploaded to the second cloud print service is transferred to the first cloud print service. An invention is disclosed that enables printing from a printing device via a cloud print service.

However, in order to add an information processing apparatus that manages the electronic device, there is a problem that registration work is required in the electronic device. For example, when electronic devices are installed in a number of remote locations, the greater the number of electronic devices, the greater the burden of on-site registration work on workers.

SUMMARY OF THE INVENTION An object of an embodiment of the present invention is to reduce the workload of registering an electronic device in an information processing apparatus in view of the above technical problems.

In order to solve the above problems, an electronic device according to one embodiment of the present invention is an electronic device capable of communicating with a first information processing device and a second information processing device, comprising: an instruction receiving unit that receives from the second information processing apparatus a registration instruction including the registration number issued by the registration requesting unit that transmits a registration request including the registration number to the first information processing apparatus in response to the registration instruction; Prepare.

According to one embodiment of the present invention, it is possible to reduce the work load of registering an electronic device in an information processing apparatus.

It is a figure showing an example of the whole composition of a device management system in one embodiment. It is a figure which shows an example of the hardware constitutions of the computer in one embodiment. 1 is a diagram illustrating an example of a hardware configuration of an MFP in one embodiment; FIG. It is a figure showing an example of functional composition of a device management system in one embodiment. It is a figure which shows an example of the processing procedure of the device management method in one Embodiment. It is a figure which shows an example of the equipment management table in a 2nd management server. It is a figure which shows an example of the screen which a registration number issuing part displays. It is a figure which shows an example of a registration number management table. It is a figure which shows an example of a state management table. It is a figure which shows an example of the screen which a registration number input part displays. FIG. 10 is a diagram showing an example of a setting management table; FIG. It is a figure which shows an example of the equipment management table in a 1st management server.

BEST MODE FOR CARRYING OUT THE INVENTION Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. In the drawings, constituent parts having the same function are denoted by the same numbers, and redundant explanations are omitted.

[Embodiment]
An embodiment of the present invention is a device management system in which a plurality of management servers manage one or more electronic devices. In the device management system of this embodiment, a management server and electronic devices are installed at remote locations, and device management is performed by communicating with each other via a communication network.

The electronic device according to the present embodiment is installed at a site such as an office where the user is present. The management server in the present embodiment is installed at a base where no user exists, such as a data center.

In this embodiment, a configuration for registering one electronic device in two management servers in the device management system configured as described above will be described.

Conventionally, in order to register an electronic device in a management server, it has been necessary for a worker to perform registration work required for registration at a site where the electronic device is installed. In the device management system of this embodiment, an electronic device registered with a certain management server transmits a registration request to another management server in response to a registration instruction from the management server. As a result, according to the device management system of the present embodiment, the operator does not need to perform the registration work for the electronic device, which was required when adding a management server that manages the electronic device.

<Overall configuration of device management system>
First, the overall configuration of the device management system according to this embodiment will be described with reference to FIG. FIG. 1 is a block diagram showing an example of the overall configuration of a device management system 100 according to this embodiment.

As shown in FIG. 1, the device management system 100 in this embodiment includes two management servers 1 (a first management server 1-1 and a second management server 1-2) and one or more electronic devices. 2. The first management server 1-1, the second management server 1-2, and the electronic device 2 in this embodiment are each connected to the communication network N1.

Although FIG. 1 shows an example in which there are two management servers 1 and one electronic device 2, the number of management servers 1 and electronic devices 2 is not limited to this. The number of management servers 1 may be three or more, and the number of electronic devices 2 may be two or more.

The communication network N1 is configured so that connected devices can communicate with each other. The communication network N1 is constructed by a wired communication network such as the Internet, a LAN (Local Area Network), or a WAN (Wide Area Network).

The communication network N1 includes not only wired communication but also wireless LAN, wireless communication such as short-range wireless communication, WiMAX (Worldwide Interoperability for Microwave Access), LTE (Long Term Evolution), or 5G (5th Generation). of mobile communication networks may be included.

The management server 1 is an information processing device that manages the electronic equipment 2 via the communication network N1. An example of the management server 1 is a computer.

The management server 1 in this embodiment is a multi-tenant system. The electronic device 2 managed by the management server 1 is associated with one of tenants predefined in the management server 1 . It is assumed that the electronic device 2 is associated with one tenant and is not associated with multiple tenants.

The electronic devices 2 are various electronic devices used by users. An example of the electronic device 2 is an MFP (Multifunction Peripheral/Product/Printer). Other examples of the electronic device 2 are a printer, a FAX device, a scanner device, and the like.

Note that the management server 1 and the electronic device 2 are not limited to computers and MFPs as long as they are devices having a communication function. The management server 1 and the electronic device 2 are, for example, a PJ (Projector), an IWB (Interactive White Board: a whiteboard having an electronic blackboard function capable of mutual communication), an output device such as a digital signage, a HUD (Head Up Display) equipment, industrial machinery, imaging equipment, sound collecting equipment, medical equipment, network home appliances, automobiles (connected cars), notebook PCs (personal computers), mobile phones, smartphones, tablet terminals, game consoles, PDA (Personal Digital Assistant) , a digital camera, a wearable PC, a desktop PC, or the like.

In the device management system 100 of this embodiment, the electronic device 2 may be registered only with the first management server 1-1, registered only with the second management server 1-2, or registered with the first management server 1-2. It may be registered in both the server 1-1 and the second management server 1-2. In this embodiment, the case where the electronic device 2 is registered in the second management server 1-2 in advance and is newly registered in the first management server 1-1 will be described.

<Hardware configuration of device management system>
Next, the hardware configuration of the device management system according to this embodiment will be described with reference to FIGS. 2 and 3. FIG.

<<Computer hardware configuration>>
FIG. 2 is a block diagram showing an example of a hardware configuration when the management server 1 is realized by a computer. As shown in FIG. 2, the computer includes a CPU (Central Processing Unit) 501, ROM (Read Only Memory) 502, RAM (Random Access Memory) 503, HD (Hard Disk) 504, HDD (Hard Disk Drive) Controller 505, display 506, external device connection I/F (Interface) 508, network I/F 509, bus line 510, keyboard 511, pointing device 512, DVD-RW (Digital Versatile Disk Rewritable) drive 514, media I/F 516 I have.

Among these, the CPU 501 controls the operation of the entire computer. The ROM 502 stores programs used to drive the CPU 501, such as an IPL (Initial Program Loader). A RAM 503 is used as a work area for the CPU 501 . The HD 504 stores various data such as programs. The HDD controller 505 controls reading or writing of various data to/from the HD 504 under the control of the CPU 501 .

A display 506 displays various information such as cursors, menus, windows, characters, or images. The external device connection I/F 508 is an interface for connecting various external devices. The external device in this case is, for example, a USB (Universal Serial Bus) memory, a printer, or the like. A network I/F 509 is an interface for data communication using a communication network. A bus line 510 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 501 shown in FIG.

The keyboard 511 is a type of input means having a plurality of keys for inputting characters, numerical values, various instructions, and the like. The pointing device 512 is a kind of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, and the like. A DVD-RW drive 514 controls reading or writing of various data to a DVD-RW 513 as an example of a removable recording medium. It should be noted that not only DVD-RW but also DVD-R or the like may be used. A media I/F 516 controls reading or writing (storage) of data to a recording medium 515 such as a flash memory.

<<Hardware Configuration of MFP>>
FIG. 3 is a block diagram showing an example of a hardware configuration when the electronic device 2 is implemented by an MFP. As shown in FIG. 3, the MFP has a controller 910, a short-range communication circuit 920, an engine control section 930, an operation panel 940, and a network I/F 950.

Among these, the controller 910 includes a CPU 901, a system memory (MEM-P) 902, a north bridge (NB) 903, a south bridge (SB) 904, an ASIC (Application Specific Integrated Circuit) 906, a storage unit, which is the main part of the computer. A local memory (MEM-C) 907 , an HDD controller 908 , and an HD 909 as a storage unit, and the NB 903 and ASIC 906 are connected by an AGP (Accelerated Graphics Port) bus 921 .

Among these, the CPU 901 is a control unit that performs overall control of the MFP. The NB 903 is a bridge for connecting the CPU 901, the MEM-P 902, the SB 904, and the AGP bus 921, and is a memory controller that controls reading and writing with respect to the MEM-P 902, a PCI (Peripheral Component Interconnect) master, and an AGP target. have

The MEM-P 902 is composed of a ROM 902a, which is a memory for storing programs and data for realizing each function of the controller 910, and a RAM 902b, which is used as a drawing memory for expanding the programs and data and for memory printing. The program stored in the RAM 902b is configured to be provided by being recorded in a computer-readable recording medium such as a CD-ROM, CD-R, DVD, etc. as a file in an installable format or an executable format. You may

The SB 904 is a bridge for connecting the NB 903 with PCI devices and peripheral devices. The ASIC 906 is an image processing IC (Integrated Circuit) having hardware elements for image processing, and serves as a bridge that connects the AGP bus 921, PCI bus 922, HDD 908 and MEM-C 907, respectively. This ASIC 906 includes a PCI target and AGP master, an arbiter (ARB) that forms the core of the ASIC 906, a memory controller that controls the MEM-C 907, and multiple DMACs (Direct Memory Access Controllers) that perform image data rotation, etc. by hardware logic. , and a PCI unit that transfers data between the scanner unit 931 and the printer unit 932 via the PCI bus 922 . Note that the ASIC 906 may be connected to a USB (Universal Serial Bus) interface or an IEEE 1394 (Institute of Electrical and Electronics Engineers 1394) interface.

MEM-C 907 is a local memory used as an image buffer for copying and an encoding buffer. The HD 909 is a storage for accumulating image data, accumulating font data used for printing, and accumulating forms. The HD 909 controls reading or writing of data to or from the HD 909 under the control of the CPU 901 . The AGP bus 921 is a bus interface for graphics accelerator cards proposed to speed up graphics processing, and can speed up the graphics accelerator card by directly accessing the MEM-P 902 with high throughput. .

The near field communication circuit 920 also includes a near field communication circuit 920a. The short-range communication circuit 920 is a communication circuit for NFC, Bluetooth, or the like.

Furthermore, the engine control section 930 is configured by a scanner section 931 and a printer section 932 . The operation panel 940 displays a current setting value, a selection screen, and the like, and a panel display unit 940a such as a touch panel for receiving input from an operator, and setting values for image forming conditions such as density setting conditions. An operation panel 940b is provided which includes a numeric keypad for accepting a copy start instruction, a start key for accepting a copy start instruction, and the like. A controller 910 controls the entire MFP, such as drawing, communication, and input from an operation panel 940 . The scanner unit 931 or printer unit 932 includes an image processing part such as error diffusion and gamma conversion.

The MFP can switch and select the document box function, the copy function, the printer function, and the facsimile function in sequence using the application switching key on the operation panel 940 . The document box mode is set when the document box function is selected, the copy mode is set when the copy function is selected, the printer mode is set when the printer function is selected, and the facsimile mode is set when the facsimile mode is selected.

A network I/F 950 is an interface for data communication using a communication network. A short-range communication circuit 920 and a network I/F 950 are electrically connected to the ASIC 906 via a PCI bus 922 .

<Functional configuration of information processing system>
Next, the functional configuration of the device management system according to this embodiment will be described with reference to FIG. FIG. 4 is a block diagram showing an example of the functional configuration of each device included in the device management system 100 according to this embodiment.

In the following explanation, only the components necessary for the first management server 1-1 and the second management server 1-2 will be explained, but the first management server 1-1 and the second management server 1-2 It does not matter if they have the same configuration in which the components included in both are provided without duplication.

<<Functional configuration of the first management server>>
As shown in FIG. 4, the first management server 1-1 in this embodiment comprises a device information storage section 10, a device registration section 11 and a registration number issuing section 12. FIG.

The device registration unit 11 and the registration number issuing unit 12 are implemented, for example, by processing that is executed by the CPU 501, which is developed on the RAM 503 from the HD 504 shown in FIG.

The device information storage unit 10 is implemented using, for example, the HD 504 shown in FIG. Reading or writing of data stored in the HD 504 is performed via the HDD controller 505, for example.

The device information storage unit 10 stores device information related to the electronic devices 2 managed by the management server 1 . The device information in this embodiment is stored in a device management table that associates a device identification number that identifies the electronic device 2 with a tenant ID that identifies a predefined tenant.

Further, the device information storage unit 10 stores registration number information related to the registration number issued by the management server 1 . Registration number information in this embodiment is stored in a registration number management table that associates registration numbers with tenant IDs.

Furthermore, the device information storage unit 10 stores state information regarding the electronic devices 2 managed by the management server 1 . The state information in the present embodiment is a state in which a device identification number that identifies the electronic device 2, version information of the software module installed in the electronic device 2, and registration information that indicates the registration state with the other management server 1 are associated. Stored in the management table.

The device registration unit 11 receives a registration request from the electronic device 2 . A registration request in this embodiment includes a registration number, a device identification number, and version information. Also, the device registration unit 11 verifies the validity of the registration number included in the registration request.

If the registration number is valid, the device registration unit 11 stores the device information including the tenant ID and the device identification number in the device information storage unit 10 . Further, the device registration unit 11 stores state information including the device identification number and version information in the device information storage unit 10 .

The registration number issuing unit 12 issues a registration number according to the operation of the administrator of the device management system 100 . The registration number is issued by designating the tenant. The registration number issuing unit 12 also stores registration number information including the issued registration number and the tenant ID that identifies the designated tenant in the device information storage unit 10 .

<<Functional configuration of the second management server>>
As shown in FIG. 4, the second management server 1-2 in this embodiment includes a device information storage unit 10, a status acquisition unit 13, a registration number input unit 14, a setting information storage unit 15, a setting information generation unit 16 and a registration instruction unit 17 .

The status acquisition unit 13, the registration number input unit 14, the setting information generation unit 16, and the registration instructing unit 17 are realized by, for example, a process of causing the CPU 501 to execute a program developed on the RAM 503 from the HD 504 shown in FIG. be.

The device information storage unit 10 and the setting information storage unit 15 are implemented using, for example, the HD 504 shown in FIG. Reading or writing of data stored in the HD 504 is performed via the HDD controller 505, for example.

The state acquisition unit 13 transmits a state information acquisition request to the electronic device 2 . Also, the status acquisition unit 13 receives version information and registration information from the electronic device 2 . Further, the state acquisition unit 13 stores state information including version information and registration information received from the electronic device 2 and a device identification number for identifying the electronic device 2 in the device information storage unit 10 .

The registration number input unit 14 accepts input of a registration number according to an operation by the administrator of the device management system 100 . The registration number is entered by designating the device identification number.

The setting information storage unit 15 stores setting information for each version information. The setting information in this embodiment is a setting item name and a setting value representing settings for connecting the electronic device 2 to the first management server 1-1. The setting information in this embodiment is stored in a setting management table that associates version information, setting item names, and setting values.

The setting information generation unit 16 generates setting information to be set in the electronic device 2 based on the setting management table stored in the setting information storage unit 15 . The electronic device 2 for which the setting information is generated is the electronic device 2 identified by the device identification number for which the registration number input unit 14 has accepted the input of the registration number.

Registration instruction unit 17 transmits a registration instruction to electronic device 2 . The electronic device 2 that transmits the registration instruction is the electronic device 2 for which the setting information generation unit 16 has generated the setting information. The registration instruction in this embodiment includes the registration number input by the registration number input unit 14 and the setting information generated by the setting information generation unit 16 .

<<Functional configuration of electronic equipment>>
As shown in FIG. 4, the electronic device 2 in this embodiment includes a connection information storage unit 20, a status transmission unit 21, an instruction reception unit 22, a setting change unit 23, and a registration request unit 24.

The status transmitting unit 21, the instruction receiving unit 22, the setting changing unit 23, and the registration requesting unit 24 are implemented by, for example, a process of causing the CPU 901 to execute a program developed on the RAM 902b from the HD 909 shown in FIG.

The connection information storage unit 20 is implemented using, for example, the HD 909 shown in FIG. Reading or writing of data stored in the HD 909 is performed via the HDD controller 908, for example.

The connection information storage unit 20 stores connection information regarding the management server 1 . The connection information in this embodiment includes, for each management server 1, connection destination information representing the connection destination of the management server 1, registration status with respect to the management server 1, and setting information representing settings for connecting to the management server 1. including.

In response to the state information acquisition request received from the second management server 1-2, the state transmission unit 21 transmits the registration state stored in the connection information storage unit 20 and the version information regarding the electronic device 2 to the second management server 1-2. Send to the management server 1-2.

The instruction receiving unit 22 receives a registration instruction from the second management server 1-2. The registration instruction in this embodiment includes a registration number and setting information.

The setting change unit 23 changes the setting information regarding the first management server 1-1 stored in the connection information storage unit 20 according to the setting information included in the registration instruction received from the second management server 1-2.

The registration request unit 24 transmits a registration request to the first management server 1-1. The registration request in this embodiment includes the registration number received by the instruction receiving unit 22 , the device identification number for identifying the electronic device 2 , and version information regarding the electronic device 2 .

<Processing procedure of the device management system>
Next, a device management method executed by the device management system according to this embodiment will be described with reference to FIG. FIG. 5 is a flow chart showing an example of the processing procedure of the device management method executed by the device management system 100 according to this embodiment.

The electronic device 2 is registered in advance with the second management server 1-2. Device information about the electronic device 2 is stored in the device management table stored by the second management server 1-2. When registering the electronic device 2 with the first management server 1, the operator inputs the registration number issued by the management server 1 to the electronic device 2, Make settings.

Here, the device management table in this embodiment will be described with reference to FIG. FIG. 6 is a conceptual diagram showing an example of a device management table in the second management server 1-2.

As shown in FIG. 6, the device management table 1010B in the second management server 1-2 includes, as data items, an identification number (No) for identifying the device information, a device identification number for identifying the electronic device 2, It has a tenant ID that identifies a tenant, a customer name, and the like. The tenant ID and customer name are defined in advance by the administrator of the device management system 100 or the like. It should be noted that the tenant ID is assigned independently by the management server 1 and does not match tenant IDs defined in other management servers 1 .

In step S 1 , the registration number issuing unit 12 provided in the first management server 1 - 1 issues a registration number according to the operation of the administrator of the device management system 100 . The registration number issuing unit 12 displays a registration number issuing screen and a registration number display screen on the display 506 in order to issue a registration number.

Here, a screen displayed by the registration number issuing unit 12 in this embodiment will be described with reference to FIG.

FIG. 7A is a conceptual diagram showing an example of a registration number issuance screen. As shown in FIG. 7A, the registration number issue screen 110 has a tenant ID input field 111, a quantity input field 112, and an issue button 119. In the tenant ID input field 111, enter the tenant ID associated with the registration number to be issued. In the number entry field 112, the number of registration numbers to be issued is entered.

When the issuance button 119 is pressed on the registration number issuance screen 110 , the registration number issuance unit 12 generates the number of registration numbers that are not duplicated with the already issued registration numbers, as many as the number entered in the number input field 112 . Next, the registration number issuing unit 12 displays on the display 506 a registration number display screen for displaying the result of issuing the registration number.

FIG. 7B is a conceptual diagram showing an example of the registration number display screen. As shown in FIG. 7(B), the registration number display screen 120 has a registration number display field 121 and a confirmation button 129 . A list of registration numbers issued by the registration number issuing unit 12 is displayed in the registration number display field 121 .

When the confirmation button 129 is pressed on the registration number display screen 120, the registration number issuing unit 12 associates the registration number displayed in the registration number display field 121 with the tenant ID input in the tenant ID input field 111. , is stored in the registration number management table. The registration number issuing unit 12 then closes the registration number display screen 120 .

Here, the registration number management table in this embodiment will be described with reference to FIG. FIG. 8 is a conceptual diagram showing an example of a registration number management table in this embodiment.

As shown in FIG. 8, the registration number management table 1020 in this embodiment includes, as data items, a registration number issued by the management server 1, a tenant ID for identifying a tenant, and a status indicating validity of the registration number. , and the expiration date of the registration number, etc.

The status is either "valid" or "invalid", and in the case of "invalid", a reason for invalidation such as "expired" or "used" is set. "Expired" means that the expiration date has passed, and "Used" means that the same registration number has already been used. Immediately after issuing the registration number, the status is set to "valid", and the expiration date is set to the date when a predetermined valid period has passed from that day.

Returning to FIG. 5, description will be made. In step S2, the status acquisition unit 13 included in the second management server 1-2 transmits a status information acquisition request to the electronic device 2. FIG.

In step S3, the status transmission unit 21 included in the electronic device 2 receives the status information acquisition request from the second management server 1-2. Next, the status transmission unit 21 transmits the registration status of the first management server 1-1 and the version information of the electronic device 2 to the second management server 1-2 in response to the status information acquisition request.

In the second management server 1 - 2 , the status acquisition unit 13 receives the registration status and version information from the electronic device 2 . Next, the state acquisition unit 13 associates the registration state and version information received from the electronic device 2 with the device identification number that identifies the electronic device 2, and stores them in the state management table.

Here, the state management table in this embodiment will be described with reference to FIG. FIG. 9 is a conceptual diagram showing an example of the state management table in this embodiment.

As shown in FIG. 9, the state management table 1030 in this embodiment includes, as data items, an identification number (No) for identifying device information, a device identification number for identifying the electronic device 2, a version number for the electronic device 2 information, registration status from the electronic device 2 to the first management server 1-1, and the like.

It should be noted that, if there is state information about the electronic device 2 , the state acquisition unit 13 updates the state information with each piece of information received from the electronic device 2 .

Returning to FIG. 5, description will be made. In step S4, the registration number input unit 14 provided in the second management server 1-2 accepts the input of the registration number according to the operation of the administrator of the device management system 100. FIG. Registration number input unit 14 displays a device selection screen and a registration number input screen on display 506 in order to receive the input of the registration number.

Here, the screen displayed by the registration number input unit 14 in this embodiment will be described with reference to FIG.

FIG. 10A is a conceptual diagram showing an example of the device selection screen. As shown in FIG. 10A, the device selection screen 200 has a device identification number selection field 201 and a registration button 209 . The device identification number selection field 201 displays a list of device information related to the electronic device 2 managed by the second management server 1-2. The device identification number selection field 201 displays check boxes for selecting each device identification number. In the device identification number selection field 201, a device identification number to be entered as a registration number is selected.

When the registration button 209 is pressed on the device selection screen 200, the registration number input unit 14 displays on the display 506 a registration number input screen for inputting the registration number for the selected device identification number.

FIG. 10B is a conceptual diagram showing an example of the registration number input screen. As shown in FIG. 10B, the registration number entry screen 210 has a registration number entry field 211 and an execution button 219 . A list of device identification numbers selected on the device selection screen 200 is displayed in the registration number input field 211 . In the registration number entry field 211, the registration number displayed on the registration number display screen 120 is entered for each device identification number.

When the execution button 219 is pressed on the registration number input screen 210 , the registration number input unit 14 obtains a set of the registration number and the device identification number from the registration number input field 211 . Next, the registration number input unit 14 sends the combination of the obtained registration number and device identification number to the setting information generation unit 16 . Then, the registration number input unit 14 closes the registration number input screen 210 .

Returning to FIG. 5, description will be made. In step S5, the setting information generation section 16 provided in the second management server 1-2 receives a set of the registration number and the device identification number from the registration number input section . Next, the setting information generator 16 generates setting information to be set for the electronic device 2 identified by the device identification number based on the setting management table.

Specifically, the setting information generator 16 reads the state information specified by the device identification number from the state management table. Next, the setting information generating unit 16 reads setting information specified by the version information included in the read state information from the setting management table. Then, the setting information generation unit 16 adds the read setting information to a set of the registration number and the device identification number, and sends the combination to the registration instructing unit 17 .

Here, the setting management table in this embodiment will be described with reference to FIG. FIG. 11 is a conceptual diagram showing an example of the setting management table in this embodiment.

As shown in FIG. 11, the setting management table 1040 in this embodiment has version information, setting item names, setting values, etc. as data items.

Depending on the software module installed in the electronic device 2, even for settings that implement the same function, the setting item name or setting value may differ depending on the version. Therefore, the setting management table in this embodiment is configured to be able to store sets of setting item names and setting values for each piece of version information.

If the setting information corresponding to the version information included in the state information does not exist in the setting management table, the setting information generation unit 16 does not generate the setting information, and displays that fact on the display 506 . In this case, the operator manually performs the setting work for the electronic device 2 .

Returning to FIG. 5, description will be made. In step S6, the registration instructing unit 17 provided in the second management server 1-2 receives a set of registration number, device identification number, and setting information from the setting information generating unit 16. FIG. Next, the registration instruction unit 17 transmits a registration instruction to the electronic device 2 identified by the received device identification number. The registration instruction includes the registration number and setting information received from the setting information generating unit 16 . Further, the registration instruction may include information designating the management server 1 as the registration destination.

In step S7, the instruction reception unit 22 included in the electronic device 2 receives the registration instruction from the second management server 1-2. Next, the instruction receiving unit 22 determines the management server 1 to be registered.

Specifically, if there is a management server 1 whose registration status is unregistered stored in the connection information storage unit 20, the instruction receiving unit 22 determines that management server 1 as the management server 1 to be registered. If the registration instruction received from the second management server 1-2 contains information designating the management server 1 as the registration destination, the instruction receiving unit 22 assigns the management server 1 to the management server 1 as the registration destination. decide. In this embodiment, there are two management servers 1, and since they are already registered in the second management server 1-2, the instruction receiving unit 22 selects the first management server 1-1 as the registration destination management server 1. decide.

Next, the instruction receiving unit 22 sends the setting information included in the received registration instruction to the setting changing unit 23 . The instruction receiving unit 22 also sends the registration number included in the received registration instruction to the registration requesting unit 24 .

In step S<b>8 , the setting changer 23 included in the electronic device 2 receives the setting information from the instruction receiving unit 22 . Next, according to the received setting information, the setting change unit 23 updates the setting information for connecting to the first management server 1-1 stored in the connection information storage unit 20 with the received setting information.

In step S<b>9 , the registration requesting unit 24 included in the electronic device 2 receives the registration number from the instruction accepting unit 22 . Next, the registration request unit 24 uses the connection destination information stored in the connection information storage unit 20 to transmit a registration request to the first management server 1-1. The registration request includes the registration number received from the instruction receiving unit 22 , the device identification number for identifying the electronic device 2 , and version information regarding the electronic device 2 .

In step S10, the device registration unit 11 included in the first management server 1-1 receives a registration request from the electronic device 2. FIG. Next, the device registration unit 11 verifies the validity of the registration number included in the registration request. Verification of validity is performed based on the registration number management table. That is, the device registration unit 11 reads registration number information from the registration number management table using the registration number included in the registration request. Then, the device registration unit 11 determines whether the registration number is valid or invalid by referring to the status and expiration date included in the read registration number information.

If the registration number is valid, the device registration unit 11 associates the device identification number included in the registration request with the tenant ID and stores it in the device management table. The tenant ID associated with the device identification number is the tenant ID associated with the registration number included in the registration request in the registration number management table.

Here, the device management table in this embodiment will be described with reference to FIG. FIG. 12 is a conceptual diagram showing an example of a device management table in the first management server 1-1.

As shown in FIG. 12, the device management table 1010A in the first management server 1-1 has the same data items as the device management table 1010B in the second management server 1-2 shown in FIG.

Comparing the device management table 1010A shown in FIG. 12 with the device management table 1010B shown in FIG. It can be seen that different tenant IDs are assigned to . However, in either case, the device identification number is associated with the same customer name. This is issued by the first management server 1-1 with a registration number associated with the tenant ID, and for the device identification number associated with the tenant ID indicating the same customer in the second management server 1-2 This is achieved by entering the registration number.

<Effects of Embodiment>
The electronic device 2 in this embodiment transmits a registration request to the first management server 1-1 in response to the registration instruction received from the second management server 1-2. At this time, the second management server 1-2 includes the registration number issued by the first management server 1-1 in the registration instruction and transmits it to the electronic device 2, and the electronic device 2 requests registration of the registration number included in the registration instruction. , and transmitted to the first management server 1-1. Therefore, the registration work in the electronic device 2, which was necessary for registering the electronic device 2 in the first management server 1-1, becomes unnecessary.

Further, in the device management system 100 according to the present embodiment, the setting information corresponding to the version information regarding the electronic device 2 is included in the registration instruction transmitted by the second management server 1-2. Therefore, even if the setting work according to the version information is required in order to register the electronic device 2 in the first management server 1-1, the setting work in the electronic device 2 is unnecessary.

In particular, in the device management system 100 according to the present embodiment, the first management server 1-1 may execute the conventional registration function. Therefore, there is no need to add a new function to the first management server 1-1 in order to eliminate the registration work in the electronic device 2. FIG.

Furthermore, in the device management system 100 of this embodiment, the first management server 1-1 issues a registration number in association with the tenant. Therefore, even if tenants are managed independently by the first management server 1-1 and the second management server 1-2, the electronic device 2 can be associated with the same tenant (customer).

[supplement]
In each of the above embodiments, the first management server 1-1 is an example of the first information processing device and other information processing devices. The second management server 1-2 is an example of a second information processing device. The device management system 100 is an example of an information processing system. Version information is an example of model information. The device identification number is an example of identification information.

Each function of the embodiments described above may be implemented by one or more processing circuits. Here, the "processing circuit" in this specification means a processor programmed by software to perform each function, such as a processor implemented by an electronic circuit, or a processor designed to perform each function described above. ASICs (Application Specific Integrated Circuits), DSPs (digital signal processors), FPGAs (field programmable gate arrays) and devices such as conventional circuit modules.

The devices described in the embodiments are merely representative of one of several computing environments for implementing the embodiments disclosed herein. In one embodiment, the management server 1 includes multiple computing devices such as server clusters. Multiple computing devices are configured to communicate with each other over any type of communication link, including a network, shared memory, etc., to perform the processes disclosed herein.

Although the embodiments of the present invention have been described in detail above, the present invention is not limited to these embodiments, and various modifications or Change is possible.

1 Management server 2 Electronic device 10 Device information storage unit 11 Device registration unit 12 Registration number issuing unit 13 Status acquisition unit 14 Registration number input unit 15 Setting information storage unit 16 Setting information generation unit 17 Registration instruction unit 20 Connection information storage unit 21 Status Transmission unit 22 Instruction reception unit 23 Setting change unit 24 Registration request unit 100 Device management system

Japanese Patent Application Laid-Open No. 2020-87230

Claims (8)

An electronic device capable of communicating with a first information processing device and a second information processing device,
an instruction receiving unit that receives from the second information processing apparatus a registration instruction including a registration number issued by the first information processing apparatus;
a registration request unit that transmits a registration request including the registration number to the first information processing device in response to the registration instruction;
electronic equipment. The electronic device according to claim 1,
the registration instruction includes setting information for connecting to the first information processing device;
further comprising a setting change unit that changes settings of the electronic device according to the setting information;
Electronics. The electronic device according to claim 2,
further comprising a state transmission unit that transmits model information regarding the electronic device to the second information processing device;
the setting information is generated based on the model information;
Electronics. The electronic device according to claim 3,
The registration number is issued in association with the tenant defined in the first information processing device,
the registration request further includes identification information that identifies the electronic device;
The identification information is stored in the first information processing device in association with the tenant,
Electronics. An information processing device capable of communicating with an electronic device,
an input unit that displays an input screen for associating a registration number issued by another information processing device with the electronic device;
a registration instruction unit that transmits, to the electronic device, an instruction to register with the other information processing apparatus, including the registration number;
comprising
Information processing equipment. An information processing system in which an electronic device can communicate with a first information processing device and a second information processing device,
The second information processing device is
an input unit that displays an input screen for associating the registration number issued by the first information processing device with the electronic device;
a registration instruction unit that transmits an instruction to register with the first information processing apparatus, including the registration number, to the electronic device;
with
The electronic device
an instruction receiving unit that receives the registration instruction from the second information processing device;
a registration request unit that transmits a registration request including the registration number to the first information processing device in response to the registration instruction;
comprising
Information processing system. An electronic device capable of communicating with the first information processing device and the second information processing device,
an instruction receiving procedure for receiving from the second information processing apparatus a registration instruction including a registration number issued by the first information processing apparatus;
a registration request procedure for transmitting a registration request including the registration number to the first information processing apparatus in response to the registration instruction;
Management method to perform. In an electronic device capable of communicating with the first information processing device and the second information processing device,
an instruction receiving procedure for receiving from the second information processing apparatus a registration instruction including a registration number issued by the first information processing apparatus;
a registration request procedure for transmitting a registration request including the registration number to the first information processing apparatus in response to the registration instruction;
program to run the

Images