Device managing system, device managing apparatus, and program

Abstract

To provide a device managing system, a device managing apparatus, and a program allowing for managing a plurality of devices remotely.SOLUTION: A device managing system comprises a plurality of devices, a relay, and an information processing terminal. The relay connects to communicate with the plurality of devices. The information processing terminal connects to communicate with the relay but does not connect directly with the plurality of devices. Meanwhile, the relay acquires status information representative of a state of the plurality of devices from the plurality of devices. The information processing terminal acquires the status information of the plurality of devices from the relay and displays the acquired status information on a display unit.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a device management system, a device management apparatus, and a program. [Background technology]

[0002] Conventionally, various devices such as scanners and printers may be used as peripheral devices for POS (Point Of Sales) terminals used in stores, etc. When an error occurs in such various peripheral devices, for example, a store clerk or the like would inquire at a support center, or a service person (repair person, maintenance person, etc.) would visit the store.

[0003] However, when store clerks contacted the support center, it was sometimes difficult to accurately communicate the problem, such as an error. Also, when a service technician had to respond on-site, it required time and money to visit the store. For these reasons, there was a need for a system that could remotely manage various peripheral devices. Summary of the Invention [Problem to be solved by the invention]

[0004] The problem to be solved by the present invention is to provide a device management system, a device management apparatus, and a program that are capable of managing a plurality of devices from a remote location. [Means for solving the problem]

[0005] A device management system according to an embodiment includes a plurality of devices, a relay device, and an information processing terminal. The relay device is communicatively connected to the plurality of devices. The information processing terminal is communicatively connected to the relay device but is not directly connected to the plurality of devices. The relay device acquires status information representing the states of the plurality of devices from the plurality of devices. The information processing terminal acquires the status information of the plurality of devices from the relay device and displays the acquired status information on a display unit. [Brief explanation of the drawings]

[0006] [Figure 1] FIG. 1 is a diagram showing an example of a schematic configuration of a device management system according to this embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of the IOBOX according to the embodiment. [Figure 3] FIG. 3 is a functional block diagram illustrating an example of the function of a device broker realized by the control unit of the IOBOX according to the embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of a hardware configuration of a POS device management PC according to the embodiment. [Figure 5] FIG. 5 is a functional block diagram showing an example of functions of the device management server realized by the control unit of the POS device management PC according to the embodiment. [Figure 6] FIG. 6 is a functional block diagram showing an example of functions of the device management server realized by the control unit of the POS device management PC according to the embodiment. [Figure 7] FIG. 7 is a diagram illustrating an example of a management screen displayed on the display unit according to the embodiment. [Figure 8] FIG. 8 is a sequence diagram showing an example of the flow of a process for acquiring the setting file and status information of the peripheral device according to the embodiment. [Figure 9] FIG. 9 is a sequence diagram showing an example of the flow of restarting processing of a peripheral device according to this embodiment. [Figure 10] FIG. 10 is a sequence diagram showing an example of the flow of a process for editing a setting file for processing a peripheral device according to this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0007] Hereinafter, an embodiment of a device management system, a device management apparatus, and a program will be described with reference to the accompanying drawings. Note that the embodiment described below is an embodiment of a device management system, a device management apparatus, and a program, and does not limit the configuration, specifications, etc. of the device management system, the device management apparatus, and the program.

[0008] Fig. 1 is a diagram showing an example of the schematic configuration of a device management system 1 according to this embodiment. The device management system 1 includes, for example, various devices installed in a store 91 and various devices installed in a service center 92. Note that the number and combination of various devices shown in Fig. 1 are merely examples, and the number and combination of various devices are not limited to these examples.

[0009] The service center 92 can be installed in a location remote from the store 91. Although only one store 91 is shown in FIG. 1, one service center 92 may manage various devices installed in multiple stores 91.

[0010] The service center 92 is provided with, for example, a POS (Point Of Sales) device management PC (Personal Computer) 2 for remotely managing various devices installed in the store 91, and a router 81.

[0011] The store 91 is also provided with, for example, POS terminals 51 and 52, peripheral devices 61 to 65 for the POS terminals 51 and 52, IO (Input / Output) boxes 71 and 72, and a router 82.

[0012] The routers 81 and 82 mediate the connection between a network N such as the Internet and other devices. The router 81 provided on the service center 92 side and the router 82 provided on the store 91 side connect the POS device management PC 2 and the IOBOXes 71 and 72 so that they can communicate with each other.

[0013] The POS device management PC 2 manages the peripheral devices 61 to 65 via the IO boxes 71 and 72. As shown in Fig. 1, the POS device management PC 2 is not directly connected to the peripheral devices 61 to 65, but obtains information about the peripheral devices 61 to 65 and transmits commands to the peripheral devices 61 to 65 via the IO boxes 71 and 72. The POS device management PC 2 is operated by, for example, a maintenance manager. The POS device management PC 2 is an example of an information processing terminal and a device management apparatus in this embodiment.

[0014] The POS device management PC 2 of this embodiment has the functions of a device management server 3 and a device management client 4. The device management client 4 provides a user interface for a user such as a maintenance manager and accepts operations from the user. The device management server 3 manages peripheral devices 61 to 65 via IO boxes 71 and 72 based on the user operations accepted by the device management client 4. Note that, although an example will be described in this embodiment in which one POS device management PC 2 has the functions of the device management server 3 and the device management client 4, the device management server 3 and the device management client 4 may each be implemented as separate devices.

[0015] The POS terminals 51 and 52 are, for example, tablet-type POS terminals equipped with the functions of a POS register. The POS terminals 51 and 52 are capable of executing various applications that run on, for example, Java (registered trademark), Android (registered trademark), or IOS (registered trademark). The POS terminals 51 and 52 are communicatively connected to the IO boxes 71 and 72 via wired or wireless communication. In the example shown in FIG. 1, the POS terminals 51 and 52 are communicatively connected to the IO boxes 71 and 72 via wireless communication such as Wi-Fi (registered trademark).

[0016] The peripheral devices 61 to 65 are various devices communicably connected to the POS terminals 51 and 52 via the IO boxes 71 and 72. The peripheral devices 61 to 65 are, for example, but not limited to, a scanner, a printer, an automatic change dispenser, a card reader, an electronic money payment terminal, etc. The peripheral devices 61 to 65 are examples of devices in this embodiment.

[0017] Peripheral devices 61 to 65 are connected to IOBOX 71 and 72 by wire or wirelessly. In the example shown in Fig. 1, peripheral devices 61 to 63 are connected to IOBOX 71 by cables. Peripheral devices 64 and 65 are connected to IOBOX 72 by cables. In other words, peripheral devices 61 to 63 are under the control of IOBOX 71, and peripheral devices 64 and 65 are under the control of IOBOX 72.

[0018] Each of the peripheral devices 61 to 65 includes a processor such as a CPU (Central Processing Unit), a main storage device such as a ROM (Read Only Memory) and a RAM (Random Access Memory), and a non-volatile storage device such as a flash memory. The CPU, ROM, and RAM of the peripheral devices 61 to 65 are connected via a bus or the like to form a control unit of the peripheral devices 61 to 65. The peripheral devices 61 to 65 are capable of executing various application software that runs on, for example, the Windows (registered trademark) OS (Operating System). The non-volatile storage device is an example of a storage unit and storage means in the peripheral devices 61 to 65. The configuration of the peripheral devices 61 to 65 is not limited to this example.

[0019] The IO boxes 71 and 72 are connected to various devices by wire or wirelessly and receive input and output from the various devices. The IO boxes 71 and 72 function as device brokers. By using their device broker function, the IO boxes 71 and 72 are connected to a plurality of peripheral devices 61 to 65 so as to be able to communicate with each other, and act as an intermediary for communication between the POS device management PC 2 and the peripheral devices 61 to 65. For example, the IO boxes 71 and 72 acquire status information from the peripheral devices 61 to 65 and send it to the POS device management PC 2.

[0020] The status information is information that indicates the state (status) of the peripheral devices 61 to 65. Types of status include, for example, "IDLE (idle state)," "Running (normal operating state)," and "Error (error state)."

[0021] Furthermore, when the IO boxes 71 and 72 receive various commands for any of the peripheral devices 61 to 65 from the POS device management PC 2, they transmit the commands to the target peripheral device. The IO boxes 71 and 72 are examples of relay devices in this embodiment. The IO boxes 71 and 72 are also called peripheral device control devices because they receive commands from the POS device management PC 2 and control the peripheral devices 61 to 65 of the POS terminals 51 and 52.

[0022] Furthermore, the peripheral devices 61 to 65 each store setting files 601 to 605 in an internal storage device. The IO boxes 71 and 72 receive the setting files 601 to 605 from the peripheral devices 61 to 65 under their respective management, and transmit the setting files 601 to 605 to the POS device management PC 2 via the routers 81 and 82 and the network N. The device management client 4 of the POS device management PC 2 displays information based on the setting files 601 to 605 and status information on a management screen, allowing a user at the service center 92 to remotely monitor and manage the peripheral devices 61 to 65.

[0023] The setting files 601 to 605 are files that define the settings of the peripheral devices 61 to 65. The control units of the peripheral devices 61 to 65 control the operation of the peripheral devices 61 to 65 based on the setting files 601 to 605. The setting files 601 to 605 include information such as the type of the peripheral devices 61 to 65, the version name of the installed program, the logical name, the physical name, the category (the category to which the device type belongs), the device name (text name), and whether or not a log is output.

[0024] The IO boxes 71 and 72 are connected to the POS terminals 51 and 52 and mediate communication between the POS terminals 51 and 52 and the peripheral devices 61 to 65. In the example shown in FIG. 1, the POS terminals 51 and 52 are not directly connected to the peripheral devices 61 to 65, but can transmit and receive various data, commands, and the like via the IO boxes 71 and 72. For example, if the POS terminals 51 and 52 are tablet terminals, the number of I / O (Input / Output) ports to which the peripheral devices 61 to 65 can be connected is limited. In such a case, the number of peripheral devices 61 to 65 connectable to the POS terminals 51 and 52 can be expanded by connecting them via the IO boxes 71 and 72. Note that the POS terminals 51 and 52 may have peripheral devices connected without connecting them via the IO boxes 71 and 72, in addition to the peripheral devices 61 to 65 connected via the IO boxes 71 and 72. In this case, the peripheral devices connected without connecting them via the IO boxes 71 and 72 are not subject to management by the IO boxes 71 and 72.

[0025] Here, a detailed description will be given of the configuration and functions of the IOBOXes 71 and 72 in this embodiment. Since the IOBOXes 71 and 72 have the same configuration and functions, the following description will be given taking the IOBOX 71 as an example.

[0026] Fig. 2 is a diagram showing an example of the hardware configuration of the IOBOX 71 according to this embodiment. As shown in Fig. 2, the IOBOX 71 includes, for example, a CPU 701, a ROM 702, a RAM 703, an operation unit 704, a display unit 705, a first communication interface (I / F) 706, a second communication interface (I / F) 707, an input / output interface (I / F) 708, a storage unit 709, and a bus 711.

[0027] The CPU 701 is an example of a processor and controls the overall operation of the IO box 71. The ROM 702 stores various programs. The RAM 703 is a workspace where programs and various data are developed.

[0028] Note that, as the processor of the control unit 700, another processor may be provided instead of or in addition to the CPU 701. As the other processor, various processors such as a GPU (Graphics Processing Unit) or a DSP (Digital Signal Processor), or a dedicated arithmetic circuit realized by an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array) can be used as appropriate.

[0029] The CPU 701, ROM 702, and RAM 703 are connected via a bus 711 or the like to form a computer-configured control unit 700. In the control unit 700, the CPU 701 operates in accordance with a program stored in the ROM 702 or the storage unit 709 and loaded into the RAM 703, thereby executing various processes.

[0030] The storage unit 709 is a storage device equipped with a non-volatile storage medium such as a hard disk drive (HDD) or a solid state drive (SSD). The storage unit 709 stores programs that can be executed by the CPU 701 and various setting information. For example, the storage unit 709 stores a control program 720 for realizing the functional configuration described below. Note that each piece of data stored in the storage unit 709 may be acquired in advance from an external device via a network or the like, or may be input by an administrator or the like.

[0031] The operation unit 704 is an input interface that accepts operation inputs from the user and outputs the accepted operation content to the CPU 701. The operation unit 704 is, for example, a touch panel that is arranged on the display unit 705 and detects touch operations by the operator and outputs signals to the control unit 700. Note that the operation unit 704 may be provided with various input devices such as a keyboard, switches, and buttons, as appropriate.

[0032] The display unit 705 is a display device such as a liquid crystal display (LCD), an organic electroluminescence (EL) display, etc. The display unit 705 displays various types of information under the control of the CPU 701.

[0033] The first communication interface 706 is an interface for wirelessly connecting to various devices, for example, for connecting to the POS terminals 51 and 52. As a wireless communication standard, for example, Wi-fi (registered trademark) or Bluetooth (registered trademark) can be adopted, but there is no particular limitation.

[0034] The second communication interface 707 is an interface that uses a connector (communication port) for connecting to various devices via wires so that communication is possible. The second communication interface 707 is connected to the router 82 so that communication is possible, for example.

[0035] The input / output interface 708 is a connection interface that uses connectors (I / O ports) for communicatively connecting the peripheral devices 61 to 63. The peripheral devices 61 to 63 may be connected wirelessly.

[0036] Next, the device broker function of the IOBOX 71 will be described. FIG. 3 is a functional block diagram showing an example of the device broker function realized by the control unit 700 of the IOBOX 71 according to this embodiment. As shown in FIG. 3, the IOBOX 71 realizes a receiving unit 751 and a device control unit 752 by the control unit 700 operating in accordance with a control program 720 stored in the storage unit 709. More specifically, the control program 720 executed by the IOBOX 71 according to this embodiment has a modular configuration including the above-mentioned units (the receiving unit 751 and the device control unit 752). The CPU (processor) 701 reads the control program 720 from a storage medium such as the storage unit 709 and loads the above-mentioned units into a main storage device such as the RAM 703. As a result, the receiving unit 751 and the device control unit 752 are generated in the main storage device. The control program 720 according to this embodiment is assumed to be application software that runs on the Windows (registered trademark) OS, but is not limited thereto and may be application software that runs on other OSs.

[0037] The above-described functional units are merely examples, and the IOBOX 71 may further include other functions. The control program 720 may also include a module configuration other than those described above. For example, the control program 720 may include firmware such as a BIOS (Basic Input Output System) for starting an OS that controls the entire IOBOX 71. Other programs may also be stored in the ROM 702 or the storage unit 709.

[0038] The receiving unit 751 receives commands related to the management of the peripheral devices 61 to 63 under its management from the POS device management PC 2. The receiving unit 751 receives commands based on operations accepted by the device management client 4 of the POS device management PC 2 from a user via the device management server 3 of the POS device management PC 2.

[0039] The receiving unit 751 receives, from the POS device management PC 2, a request command for the setting files of the peripheral devices 61 to 63 under its management. In addition, for example, the receiving unit 751 receives, from the POS device management PC 2, a request command for status information of the peripheral devices 61 to 63 based on a user operation, a command to start processing of the peripheral devices 61 to 63 under its management, a command to stop processing, or a command to reset and restart processing, etc.

[0040] The receiving unit 751 also receives from the POS device management PC 2 commands to register a new peripheral device, commands to delete the registration of the peripheral devices 61 to 63 already registered as management targets, commands to disconnect the peripheral devices 61 to 63 from the POS terminals 51 and 52, and the like.

[0041] The receiving unit 751 also receives a command from the POS device management PC 2 to move the peripheral devices 61 to 63 under its control to a device under the control of another IOBOX 72.

[0042] The device control unit 752 controls the peripheral devices 61 to 63 under its control in accordance with various commands transmitted from the POS device management PC 2. The device control unit 752 also transmits the results of the control of the peripheral devices 61 to 63 to the POS device management PC 2.

[0043] For example, the device control unit 752 acquires the setting files 601-603 of the peripheral devices 61-63 under its management in accordance with a command transmitted from the POS device management PC 2, and transmits the acquired setting files 601-603 to the POS device management PC 2. The setting files 601-603 are used to display a management screen on the POS device management PC 2.

[0044] The receiving unit 751 also receives, from the POS device management PC 2, change information indicating the change made to the content of any of the setting files 601 to 603 by a user operation.

[0045] Furthermore, the device control unit 752, for example, in accordance with a command transmitted from the POS device management PC 2, acquires status information from the peripheral devices 61 to 63 under its control and transmits the acquired status information to the POS device management PC 2. Furthermore, for example, in accordance with a command transmitted from the POS device management PC 2, the device control unit 752 starts processing, stops processing, or resets and restarts processing of the peripheral devices 61 to 63 that are the target of the command.

[0046] The device control unit 752 also registers new peripheral devices as peripheral devices to be connected to the POS terminals 51 and 52 and as devices to be managed, for example, in accordance with a command transmitted from the POS device management PC 2. The device control unit 752 also deletes the registration of peripheral devices 61 to 63 that have already been registered as devices to be managed, for example, in accordance with a command transmitted from the POS device management PC 2. The device control unit 752 also releases the connections between the peripheral devices 61 to 63 and the POS terminals 51 and 52, for example, in accordance with a command transmitted from the POS device management PC 2.

[0047] Furthermore, the device control unit 752 moves the peripheral devices 61 to 63 under its control to the control of another IOBOX 72 in accordance with a command sent from the POS device management PC 2, for example.

[0048] Furthermore, the device control unit 752 changes the setting file stored in the storage unit of the peripheral device 61 to 63 that corresponds to the changed setting file, based on change information relating to a change to one of the setting files 601 to 603 transmitted from the POS device management PC 2. The above-described contents of the commands and controls are merely examples, and the processes that the IOBOX 71 can execute under the control of the POS device management PC 2 are not limited to these.

[0049] Next, the configuration and functions of the POS device management PC 2 in this embodiment will be described in detail.

[0050] 4 is a diagram showing an example of the hardware configuration of the POS device management PC 2 according to this embodiment. As shown in FIG. 4, the POS device management PC 2 includes a CPU 21, a ROM 12, a RAM 13, a storage unit 24, an operation unit 25, a display unit 26, and a communication unit 27.

[0051] The CPU 21 is an example of a processor and controls the overall operation of the POS device management PC 2. The ROM 22 stores various programs. The RAM 23 is a workspace where programs and various data are expanded.

[0052] The CPU 21, ROM 22, and RAM 23 are connected via a bus or the like to form a computer-configured control unit 20. In the control unit 20, the CPU 21 operates in accordance with a program stored in the ROM 22 or the storage unit 24 and loaded into the RAM 23, thereby executing various processes.

[0053] The storage unit 24 has a storage medium such as a HDD or flash memory, and maintains its stored contents even when the power is turned off. The storage unit 24 stores programs that can be executed by the CPU 21 and various setting information. For example, the storage unit 24 stores a device management server program (PG) 241 and a device management application program (PG) 242 for realizing the functional configuration described below. Each piece of data stored in the storage unit 24 may be acquired in advance from an external device via a network or the like, or may be input by an administrator or the like.

[0054] The operation unit 25 is an input device such as a keyboard or a pointing device. The operation unit 25 outputs the operation content input via the input device to the CPU 21. The operation unit 25 may be a touch panel provided on the display unit 26.

[0055] The display unit 26 is a display device such as an LCD, etc. The display unit 26 displays various types of information under the control of the CPU 21.

[0056] The communication unit 27 is a communication interface that can be connected to a network N such as the Internet or a peripheral device under the control of the control unit 20. For example, the communication unit 27 is connected to the network N via a router 81.

[0057] The hardware configuration of the POS device management PC 2 is not limited to the example shown in FIG.

[0058] Next, the function of the POS device management PC 2 as the device management server 3 will be described. FIG. 5 is a functional block diagram showing an example of the function of the device management server 3 implemented by the control unit 20 of the POS device management PC 2 according to this embodiment. As shown in FIG. 5, the POS device management PC 2 implements an acquisition unit 301, a transmission unit 302, a reception unit 303, and a linking unit 304 by the control unit 20 operating in accordance with the device management server program 241 stored in the storage unit 24. More specifically, the device management server program 241 executed by the POS device management PC 2 according to this embodiment has a modular configuration including the above-mentioned units (acquisition unit 301, transmission unit 302, reception unit 303, and linking unit 304). The CPU (processor) 21 reads the device management server program 241 from a storage medium such as the storage unit 24 and loads the above-mentioned units into a main storage device such as the RAM 23. As a result, the acquisition unit 301, transmission unit 302, reception unit 303, and linking unit 304 are generated in the main storage device. These functional units are merely examples, and the device management server 3 may further include other functions.

[0059] The acquisition unit 301 acquires various commands based on user operations from the device management client 4. Information is exchanged between the device management client 4 and the device management server 3 via the storage unit 24, for example.

[0060] The transmitting unit 302 transmits commands to the IO boxes 71 and 72 that manage the peripheral devices 61 to 65 that are targets of the commands, based on various commands acquired from the device management client 4 and the designation of the peripheral devices 61 to 65 that are targets of the commands, via the network N. In other words, the transmitting unit 302 transmits commands for the peripheral devices 61 to 65 that are targets of the operations, based on user operations accepted by the device management client 4, to the IO boxes 71 and 72 that manage the peripheral devices 61 to 65 that are targets of the operations. The transmitting unit 302 is an example of a transmitting means in this embodiment.

[0061] The receiving unit 303 receives information about the peripheral devices 61 to 65 from the IO boxes 71 and 72 via the network N. Note that reception via the network N is an example of a method of acquiring information. For example, the receiving unit 303 acquires status information indicating the states of the peripheral devices 61 to 65 via the IO boxes 71 and 72. The receiving unit 303 is an example of an acquiring means in this embodiment.

[0062] The linking unit 304 links the information on the peripheral devices 61 to 65 acquired from the IO boxes 71 and 72, the processing results of the peripheral devices 61 to 65, and the like to the device management client 4 as data.

[0063] 5, the functional units are divided such that the transmitting unit 302 and the receiving unit 303 exchange information via the network N, and the acquiring unit 301 and the linking unit 304 exchange information between the device management client 4 in the POS device management PC 2 and the device management server 3. This division of the functional units is merely an example, and the configuration of the device management server program 241 is not limited to this. For example, if the device management server 3 and the device management client 4 are implemented as separate devices, the transmitting unit 302 may perform the function of the aforementioned acquiring unit 301, and the receiving unit 303 may perform the function of the aforementioned linking unit 304.

[0064] Next, the function of the POS device management PC 2 as the device management client 4 will be described. FIG. 6 is a functional block diagram showing an example of the function of the device management server 3 implemented by the control unit 20 of the POS device management PC 2 according to this embodiment. As shown in FIG. 6, the control unit 20 of the POS device management PC 2 operates in accordance with the device management application program 242 stored in the storage unit 24, thereby implementing a display control unit 401, a reception unit 402, an editing unit 403, a command unit 404, and an acquisition unit 405. More specifically, the device management application program 242 executed by the POS device management PC 2 according to this embodiment has a modular configuration including the above-mentioned units (the display control unit 401, the reception unit 402, the editing unit 403, the command unit 404, and the acquisition unit 405). The CPU (processor) 21 reads the device management application program 242 from a storage medium such as the storage unit 24 and loads the above-mentioned units into a main storage device such as the RAM 23. As a result, a display control unit 401, a reception unit 402, an editing unit 403, a command unit 404, and an acquisition unit 405 are generated on the main storage device. Note that these functional units are examples, and the device management client 4 may further include other functions.

[0065] The device management server program 241 and the device management application program 242 of this embodiment may be stored in the storage unit 24 in advance, or may be stored on another computer connected to a network N such as the Internet and provided by being downloaded to the POS device management PC 2 via the network. The device management server program 241 and the device management application program 242 executed by the POS device management PC 2 of this embodiment may be provided or distributed via a network such as the Internet. The device management server program 241 and the device management application program 242 executed by the POS device management PC 2 of this embodiment may be provided by being recorded in an installable or executable file format on a computer-readable recording medium. Some or all of the functional components of the POS device management PC 2 may be implemented as hardware, such as a dedicated circuit mounted on the POS device management PC 2.

[0066] The display control unit 401 displays a management screen on the display unit 26 that enables status monitoring and control of the peripheral devices 61 to 65 based on information acquired from the IO boxes 71 and 72. For example, the display control unit 401 displays, on the management screen on the display unit 26, status information of the peripheral devices 61 to 65 acquired from the device management server 3 by an acquisition unit 405 (described later) and acquired from the IO boxes 71 and 72 by the device management server 3. The display control unit 401 is an example of a display control means in this embodiment.

[0067] Fig. 7 is a diagram showing an example of a management screen 41 displayed on the display unit 26 according to the present embodiment. The management screen 41 is provided for each IOBOX 71, 72, and is a screen for displaying information about the peripheral devices 61 to 65 under the management of the target IOBOX 71, 72, and for accepting operations for the peripheral devices 61 to 65 under the management. Note that Fig. 7 is displayed in English, but this is just an example, and the display language of the management screen 41 is not limited.

[0068] For example, in accordance with the configuration illustrated in FIG. 1, the management screen 41 for the IOBOX 71 displays information about the peripheral devices 61 to 63 under the management of the IOBOX 71. The management screen 41 for the IOBOX 71 can also accept user operations on the peripheral devices 61 to 63. The management screen 41 for the IOBOX 72 displays information about the peripheral devices 64 and 65 under the management of the IOBOX 72. The management screen 41 for the IOBOX 72 can also accept user operations on the peripheral devices 64 and 65. FIG. 7 illustrates an example of the display content of the management screen 41 that is generally expected, without being limited to the configuration of the IOBOXes 71 and 72 and the peripheral devices 61 to 65 under their management.

[0069] Information about the IOBOXes 71 and 72 that are the display targets of the management screen 41 is displayed on the management screen 41. In the example shown in Fig. 7, the IOBOX information display field 49 displays the device broker version, IP address, port number, status information, etc. of the IOBOXes 71 and 72 that are the display targets.

[0070] Also, a "Register" button 43 for accepting an operation to add a new peripheral device to be managed is displayed on the management screen 41. When the user presses the button 43, the peripheral devices 61 to 65 connected by wire or wirelessly to the IOBOXes 71 and 72 targeted on the management screen, which have not yet been registered as management targets, are newly registered as peripheral devices to be connected to the POS terminals 51 and 52 and as management targets.

[0071] Also, on the management screen 41, an "Available Devices" field 45 is displayed, which displays information about the peripheral devices 61 to 65 under the management of the target IOBOX 71, 72. The information displayed in the Available Devices field 45 includes, for example, information written in the setting files 601 to 605 of the peripheral devices 61 to 65 under the management of the target IOBOX 71, 72 on the management screen, and current status information about the peripheral devices 61 to 65. In the example shown in FIG. 7, the Available Devices field 45 displays "Device (type of peripheral device)," "Version (version name of the installed program)," "Logical Name," "Physical Name," "Category (category to which the device type belongs)," "Device Name (text name)," "Terminal (connection destination terminal)," and the like. At the time of initial display, this information displayed in the Available Devices field 45 is information written in the setting files 601 to 605. Note that this information may be changed from the information written in the setting files 601 to 605 using an editing function of the management screen 41, which will be described later.

[0072] Additionally, the item "State" in the Available Devices column 45 displays the latest status information of the peripheral devices 61 to 65 under the management of the target IOBOX 71, 72. The latest status information of the peripheral devices 61 to 65 is acquired from the device management server 3 by an acquisition unit 405, which will be described later.

[0073] Additionally, in the "Action" item of the Available Devices column 45, a list box 47 that can accept user operations on the peripheral devices 61 to 65 is displayed for each of the peripheral devices 61 to 65. The list box 47 is initially displayed with the words "Select Action." When the user presses the list box 47, options such as "Start," "Stop," "Restart," "Un-Register," "Remove," "Move," and "Edit" are displayed. When the user selects one of the options, a command to the peripheral device corresponding to the list box 47 among the peripheral devices 61 to 65 is sent to the target IOBOX 71, 72.

[0074] "Start" means the start of processing of the target peripheral device 61 to 65. "Stop" means the stop of processing of the target peripheral device 61 to 65.

[0075] "Restart" means resetting and restarting the processing of the target peripheral device 61 to 65. "Restart" is executed by the user to recover from an error state when, for example, an error occurs in the peripheral device 61 to 65.

[0076] "Un-Register" means deleting the registration of the target peripheral device 61 to 65. More specifically, "Un-Register" means deleting the target peripheral device 61 to 65 from the targets displayed on the management screen 41. In this case, the peripheral device that is no longer displayed on the management screen 41 as a result of the user performing an operation to select "Un-Register" may continue to be connected to the IO boxes 71 and 72 and to the POS terminals 51 and 52 via the IO boxes 71 and 72.

[0077] "Remove" means to release the connection between the peripheral devices 61 to 63 and the POS terminals 51 and 52 via the IO boxes 71 and 72. When the user performs an operation to select "Remove" for any of the peripheral devices 61 to 65, not only will the target peripheral device no longer be displayed on the management screen 41, but communication with the POS terminals 51 and 52 via the IO boxes 71 and 72 will also stop.

[0078] "Move" means moving the peripheral devices 61 to 63 under management to the management of another IOBOX. For example, when the target of the management screen 41 is the IOBOX 71, if the user performs an operation to select "Move" for any of the peripheral devices 61 to 63 under management of the IOBOX 71, the peripheral device targeted by the operation is moved to the management of another IOBOX 72.

[0079] "Edit" means editing the information of the peripheral devices 61 to 65. The information to be edited is, for example, information acquired from the setting files 601 to 605. For example, when the user presses "Edit," the display control unit 401 displays an edit screen on the display unit 26 that allows the user to edit the information acquired from the setting files 601 to 605 (for example, the type of each peripheral device 61 to 65, the version name of the installed program, the logical name, the physical name, the category, the device name, whether or not a log is output, etc.). Furthermore, when the content of "Device," "Version," "Logical Name," "Physical Name," "Category," "Device Name," etc. is changed by the user's editing operation, the display control unit 401 updates the display of the Available Devices column 45 to reflect the changed content.

[0080] It is not necessary for the Available Devices field 45 to display the contents of all items described in the setting files 601 to 605. For example, in the example shown in Fig. 7, among the information included in the setting files 601 to 605, the presence or absence of log output is not displayed in the Available Devices field 45. It is noted that the items in the Available Devices field 45 shown in Fig. 7 are merely examples and are not limited to these items. Furthermore, the layout and display contents of the management screen 41 shown in Fig. 7 are merely examples and are not limited to these.

[0081] Returning to FIG. 6 , the reception unit 402 receives a user operation for any of the peripheral devices 61 to 65. For example, the reception unit 402 receives an operation in which the user designates any of the IO boxes 71 and 72 and opens the management screen 41. For example, when the user first opens the management screen 41 for the IO boxes 71 and 72, the setting files 601 to 605 of the peripheral devices 61 to 65 to be managed and displayed on the management screen 41 are acquired. Note that the trigger for the process of acquiring the setting files 601 to 605 is not limited to this. Furthermore, each time the user opens the management screen 41 for the IO boxes 71 and 72, status information of the peripheral devices 61 to 65 to be managed is acquired. The operation also requests acquisition of the setting files 601 to 605 and status information of the peripheral devices 61 to 65 to be managed for the IO boxes 71 and 72 to be displayed on the management screen 41.

[0082] Furthermore, for example, the reception unit 402 receives an operation performed by the user on the management screen 41 for any of the peripheral devices 61 to 65. More specifically, the reception unit 402 receives an operation by the user to select an option in the list box 47, and an operation to select "Edit" from the options and edit information about the peripheral devices 61 to 65. The reception unit 402 is an example of a reception means in this embodiment.

[0083] The editing unit 403 changes the setting files 601 to 605 based on a user operation. For example, when the accepting unit 402 accepts an editing operation in which the user selects "Edit" in the list box 47 of the management screen 41, the editing unit 403 changes the setting files 601 to 605 based on the operation.

[0084] The command unit 404 transmits commands based on user operations to the device management server 3. For example, based on user operations received by the reception unit 402, the command unit 404 transmits commands to the device management server 3, such as a request to send the setting files 601 to 605, a command to start processing, stop processing, or reset and restart processing of any of the peripheral devices 61 to 65, a command to newly add or delete the peripheral devices 61 to 65 to be managed, a command to disconnect the POS terminals 51 and 52 from the peripheral devices 61 to 65, a command to move the peripheral devices 61 to 65 under the management of the IO boxes 71 and 72, a command to change information about the peripheral devices 61 to 65, and the like.

[0085] Furthermore, the command unit 404 transmits a command to the device management server 3 requesting status information on the peripheral devices 61 to 65 to be managed, for example, at regular time intervals, regardless of user operation.

[0086] The acquisition unit 405 acquires from the device management server 3 information on the peripheral devices 61 to 65 acquired by the device management server 3 from the IO boxes 71 and 72, processing results of the peripheral devices 61 to 65, and the like.

[0087] Next, the flow of management processing for the peripheral devices 61 to 65 executed by the device management system 1 configured as above will be described with reference to Figures 8 to 10. As an example, Figures 8 to 10 describe processing executed by the device management client 4 and device management server 3 of the POS device management PC 2, the IOBOX 71, and the peripheral device 61. It is assumed that similar processing can be executed for the other IOBOX 72 and other peripheral devices 62 to 65 included in the device management system 1.

[0088] 8 is a sequence diagram showing an example of the flow of a process for acquiring the setting file 601 and status information of the peripheral device 61 according to this embodiment. The process shown in the sequence diagram starts, for example, when the user opens the management screen 41 of the target IOBOX 71, 72 for the first time.

[0089] First, the command unit 404 of the device management client 4 of the POS device management PC 2 transmits a command requesting the setting file 601 and status information of the peripheral device 61 to the device management server 3 (S101). The command includes identification information capable of identifying the target peripheral device 61 and identification information capable of identifying the IOBOX 71 that manages the peripheral device 61. Then, the acquisition unit 301 of the device management server 3 acquires the command.

[0090] Then, the transmitting unit 302 of the device management server 3 transmits a command requesting the setting file 601 and status information to the IOBOX 71 that manages the peripheral device 61 that is the target of the command, based on the various commands acquired from the device management client 4 and the designation of the peripheral device 61 that is the target of the command, via the network N (S102). Then, the receiving unit 751 of the IOBOX 71 receives the command requesting the setting file 601 and status information.

[0091] Then, the device control unit 752 of the IOBOX 71 transmits a command to the peripheral device 61 requesting the setting file 601 and status information (S103).

[0092] Then, the peripheral device 61 transmits the setting file 601 and the status information to the IOBOX 71 under the control of the IOBOX 71 (S104).

[0093] The device control unit 752 of the IOBOX 71 then transmits the setting file 601 and status information received from the peripheral device 61 to the device management server 3 of the POS device management PC 2 (S105). While FIG. 8 illustrates the peripheral device 61 as an example, the device control unit 752 of the IOBOX 71 also transmits the setting files 602 and 603 and status information for the peripheral devices 62 and 63 under the management of the IOBOX 71 to the device management server 3 of the POS device management PC 2. That is, the IOBOX 71 compiles the setting files 601-603 and status information for the multiple peripheral devices 61-63 under its management and transmits them to the device management server 3 of the POS device management PC 2. The receiving unit 303 of the device management server 3 receives the setting file 601 and status information transmitted from the IOBOX 71. The IOBOX 71 may previously acquire the setting file 601 from the peripheral device 61 and store it in a storage unit or the like. In this case, the device control unit 752 of the IOBOX 71 may transmit the previously stored setting file 601 to the POS device management PC 2.

[0094] Then, the linking unit 304 of the device management server 3 links the setting file 601 and the status information received from the IOBOX 71 to the device management client 4 (S106). The acquisition unit 405 of the device management client 4 acquires the setting file 601 and the status information from the device management server 3.

[0095] The display control unit 401 of the device management client 4 causes the display unit 26 to display the management screen 41 described in Fig. 7 based on the setting file 601 and status information acquired from the device management server 3 (S107). At this point, the processing of this sequence diagram ends.

[0096] 8 is an example, and is not limited to when the user opens the management screen 41. For example, the process shown in FIG. 8 may start when the POS device management PC 2 and the IOBOXes 71 and 72 are connected for the first time.

[0097] 9 is a sequence diagram showing an example of the flow of restarting the processing of the peripheral device 61 according to this embodiment. As a premise of the processing in FIG. 9, it is assumed that the processing in FIG. 8 has been executed and the management screen 41 is displayed on the display unit 26 of the POS device management PC 2.

[0098] First, the reception unit 402 of the device management client 4 of the POS device management PC 2 receives an operation in which the user selects "Restart" in the list box 47 on the management screen 41 (S201).

[0099] In this case, the command unit 404 of the device management client 4 transmits a command to restart (reset and restart the processing of the peripheral device 61) to the device management server 3 (S202). The command includes identification information that can identify the target peripheral device 61 and identification information that can identify the IOBOX 71 that manages the peripheral device 61. The acquisition unit 301 of the device management server 3 acquires the restart command.

[0100] Then, the transmitting unit 302 of the device management server 3 transmits a Restart command to the IOBOX 71 (S203). The receiving unit 751 of the IOBOX 71 receives the Restart command.

[0101] The device control unit 752 of the IOBOX 71 transmits a restart command to the peripheral device 61 (S204).

[0102] Then, the peripheral device 61 resets and restarts the process under the control of the IOBOX 71 (S205). Then, the peripheral device 61 transmits a Return signal indicating that the process has been reset and restarted to the IOBOX 71 (S206).

[0103] Then, the device control unit 752 of the IOBOX 71 transmits the Return signal received from the peripheral device 61 to the device management server 3 of the POS device management PC 2 (S207). The receiving unit 303 of the device management server 3 receives the Return signal transmitted from the IOBOX 71.

[0104] The linking unit 304 of the device management server 3 then links the Return signal received from the IOBOX 71 to the device management client 4 (S208). The acquiring unit 405 of the device management client 4 acquires the Return signal from the device management server 3.

[0105] The display control unit 401 of the device management client 4 updates the status information on the management screen 41 based on the Return signal acquired from the device management server 3 (S209). For example, the display control unit 401 changes the display of the status information of the peripheral device 61, which was "Error" before the restart, to "Running (normal operating state)." At this point, the processing of this sequence diagram ends.

[0106] 10 is a sequence diagram showing an example of the flow of the process of editing the setting file 601 of the processing of the peripheral device 61 according to this embodiment. As a premise of the process of FIG. 10, it is assumed that the process of FIG. 8 has been executed and the management screen 41 is displayed on the display unit 26 of the POS device management PC 2.

[0107] First, the reception unit 402 of the device management client 4 of the POS device management PC 2 receives an edit start operation in which the user selects "Edit" in the list box 47 of the management screen 41 (S301). In this case, the display control unit 401 of the device management client 4 causes the display unit 26 to display an edit screen on which the information acquired from the setting file 601 can be edited (S302).

[0108] Then, the accepting unit 402 of the device management client 4 accepts the user's editing operation on the editing screen (S303).

[0109] Then, the command unit 404 of the device management client 4 transmits the changed configuration file 601, which has been changed by the user's editing operation, to the device management server 3 together with a command to reflect the changes in the peripheral device 61 from which the configuration file 601 was obtained (S304). The command includes identification information that can identify the target peripheral device 61 and identification information that can identify the IOBOX 71 that manages the peripheral device 61. The acquisition unit 301 of the device management server 3 acquires the changed configuration file 601 and the command to reflect the changes.

[0110] Then, the transmitting unit 302 of the device management server 3 transmits the changed setting file 601 and a command to reflect the changes to the IOBOX 71 (S305). The receiving unit 751 of the IOBOX 71 receives the changed setting file 601 and the command to reflect the changes.

[0111] The device control unit 752 of the IOBOX 71 transmits the changed setting file 601 and a command to reflect the changes to the peripheral device 61 (S306).

[0112] Then, under the control of the IOBOX 71, the peripheral device 61 overwrites and updates the setting file 601 stored in the storage unit with the changed setting file 601 received from the IOBOX 71 (S307). Then, the peripheral device 61 transmits a Return signal indicating completion of updating the setting file 601 to the IOBOX 71 (S308).

[0113] Then, the device control unit 752 of the IOBOX 71 transmits the Return signal received from the peripheral device 61 to the device management server 3 of the POS device management PC 2 (S309). The receiving unit 303 of the device management server 3 receives the Return signal transmitted from the IOBOX 71.

[0114] Then, the linking unit 304 of the device management server 3 links the Return signal received from the IOBOX 71 to the device management client 4 (S310). Here, the processing of this sequence diagram ends.

[0115] 10 describes a method for updating the setting file 601 of the peripheral device 61 with the changed setting file 601, but the method for updating the setting file 601 of the peripheral device 61 is not limited to this. For example, the device management client 4 may share only the changed items in the setting file 601 with the device management server 3. In this case, the device management server 3 and the IOBOX 71 transmit only information about the changed parts, rather than the entire changed setting file 601. The changed setting file 601 and information about the changed parts are an example of change information according to this embodiment.

[0116] As described above, in the device management system 1 of this embodiment, the IO boxes 71 and 72 acquire status information from the peripheral devices 61 to 65 and transmit the acquired status information to the POS device management PC 2. The POS device management PC 2 acquires the status information of the peripheral devices 61 to 65 from the IO boxes 71 and 72 and displays the acquired status information on the display unit 26. Therefore, according to the device management system 1 of this embodiment, a user such as a maintenance manager can understand the processing status of the peripheral devices 61 to 65 by looking at the display unit 26 of the POS device management PC 2, without the need for a service person or the like to visit the store 91 or for a store clerk to contact a support center. In other words, according to the device management system 1 of this embodiment, the POS device management PC 2 can collectively manage the peripheral devices 61 to 65 from a remote location via the IO boxes 71 and 72.

[0117] Furthermore, in the device management system 1 of this embodiment, the POS device management PC 2 transmits to the IO boxes 71 and 72, based on a user's operation, a command instructing at least one of starting a process, stopping a process, or resetting and restarting the process of one of the peripheral devices 61 to 65. The IO boxes 71 and 72 then start a process, stop a process, or reset and restart the process of the corresponding peripheral device in accordance with the command transmitted from the POS device management PC 2. Therefore, according to the device management system 1 of this embodiment, the POS device management PC 2 can remotely control the processes of the peripheral devices 61 to 65 without the need for a serviceman or the like to visit the store 91 and operate the peripheral devices 61 to 65.

[0118] Furthermore, in the device management system 1 of this embodiment, the POS device management PC 2 transmits to the POS device management PC 2 a command to add or delete the peripheral devices 61 to 65 connected to the POS terminals 51 and 52. The IO boxes 71 and 72 execute new addition or deletion of the peripheral devices connected to the POS terminals 51 and 52 via the IO boxes 71 and 72 in accordance with the command. Therefore, according to the device management system 1 of this embodiment, operations such as new registration or deletion of the peripheral devices 61 to 65 connected to the POS terminals 51 and 52 can be remotely managed in a centralized manner.

[0119] In the device management system 1 of this embodiment, the IO boxes 71 and 72 acquire the setting files 601 to 605 from each of the multiple peripheral devices 61 to 65. The POS device management PC 2 changes the setting files 601 to 605 based on a user operation, and transmits change information indicating the changes to the setting files 601 to 605 to the IO boxes 71 and 72. Based on the change information transmitted from the POS device management PC 2, the IO boxes 71 and 72 select the peripheral devices among the multiple peripheral devices 61 to 65 that correspond to the changed setting files 601 to 605. Therefore, according to the device management system 1 of this embodiment, the settings of the peripheral devices 61 to 65 can also be changed remotely by the POS device management PC 2.

[0120] (Variation) In the above embodiment, the transmitting unit 302, which is a function of the device management server 3, is an example of a transmitting means, but the communication unit 27, which is a hardware configuration of the POS device management PC 2, may also be an example of a transmitting means. Alternatively, the command unit 404, which is a function of the device management client 4, may also be an example of a transmitting means.

[0121] In the above embodiment, the receiving unit 303, which is a function of the device management server 3, is an example of an acquisition unit, but the communication unit 27 may be an example of an acquisition unit. Alternatively, the acquisition unit 405, which is a function of the device management client 4, may be an example of an acquisition unit.

[0122] In the above embodiment, when the content of the setting files 601-605 is changed by the user's "Edit" operation, the change is reflected in the peripheral devices 61-65 from which the setting files 601-605 were acquired. However, the change does not necessarily have to be reflected in the setting files 601-605 of the peripheral devices 61-65 from which the setting files 601-605 were acquired. For example, when the user changes the "Device (type of peripheral device)," "Version (version name of the installed program)," "Logical Name," "Physical Name," "Category (category to which the device type belongs)," "Device Name (text name)," etc., the display on the management screen 41 is updated with the changed content, and the change does not necessarily have to be reflected in the peripheral devices 61-65 from which the setting files 601-605 were acquired. In this case, the information that can be edited by the user may be only the content displayed in the "Available Devices" column 45, rather than all the content written in the setting files 601-605. Furthermore, the user may be able to select whether or not to reflect the changes in the setting files 601 to 605 of the peripheral devices 61 to 65 from which the changes were obtained.

[0123] As described above, according to the above embodiment and modifications, it is possible to provide a device management system, a device management apparatus, and a program that are capable of managing a plurality of devices from a remote location.

[0124] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These novel embodiments can be embodied in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, and are also included in the scope of the invention and its equivalents as defined in the claims. [Explanation of symbols]

[0125] 1. Device Management System 2 POS device management PC 3. Device Management Server 4 Device Management Client 20 Control Unit 24 Memory section 25 Control section 26 Display section 27 Communications Department 41 Management screen 43 Button 45 Available Devices column 47 List Box 49 IOBOX information display field 51,52 POS terminals 61~65 Peripheral equipment 71,72 IOBOX 81,82 Router 91 stores 92 Service Center 241 Device Management Server Program 242 Device management application program 301 Acquisition Department 302 Transmission Unit 303 Receiving Unit 304 Collaboration Department 401 Display control unit 402 Reception 403 Editorial Department 404 Command section 405 Acquisition Department 601~605 Configuration files 700 control section 704 Operation section 705 Display section 706 First Communication Interface 707 Second Communication Interface 708 Input / Output Interface 709 Storage section 711 Bus 720 Control Program 751 Receiving unit 752 Device control unit 2014 Patent EL Organic IOBOX71 IOBOX72 N Network [Prior art documents] [Patent documents]

[0126] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-149602

Claims

1. Multiple devices and a relay device communicably connected to the plurality of devices; an information processing terminal that is communicatively connected to the relay device but is not directly connected to the plurality of devices; the relay device acquires status information representing states of the plurality of devices from the plurality of devices; the information processing terminal acquires the status information of the plurality of devices from the relay device, and displays the acquired status information on a display unit. Device management system.

2. the information processing terminal transmits to the relay device, based on a user's operation, a command instructing at least one of starting a process, stopping a process, or resetting and restarting a process of any of the plurality of devices; the relay device executes one of starting a process, stopping a process, or resetting and restarting a process of the corresponding device in accordance with the command transmitted from the information processing terminal; The device management system of claim 1 .

3. the plurality of devices are connected to a POS (Point of Sales) terminal via the relay device; the information processing terminal transmits to the relay device a command to add or delete a device connected to the POS terminal; The relay device executes a new addition or deletion of a device connected to the POS terminal via the relay device in accordance with the command. The device management system of claim 1 .

4. the relay device acquires, from each of the plurality of devices, a setting file in which settings of the plurality of devices are described; the information processing terminal modifies the configuration file based on a user operation, and transmits modification information indicating the modification content of the configuration file to the relay device; the relay device modifies the configuration file stored in a device corresponding to the modified configuration file among the plurality of devices based on the modification information transmitted from the information processing terminal. The device management system of claim 1 .

5. an acquisition means for acquiring status information representing the states of a plurality of devices via a relay device communicably connected to the plurality of devices; a display control means for displaying the acquired status information of the plurality of devices on a display unit; a receiving means for receiving a user's operation on any one of the plurality of devices; a transmitting means for transmitting a command to the relay device for the device that is the target of the operation based on the operation; A device management apparatus comprising:

6. an acquisition step of acquiring status information representing states of the plurality of devices via a relay device communicably connected to the plurality of devices; a display control step of displaying the acquired status information of the plurality of devices on a display unit; a receiving step of receiving a user operation for any one of the plurality of devices; a transmitting step of transmitting a command to the relay device for the device that is the target of the operation based on the operation; A program that causes a computer to execute the following.

Images