Management system, management method, management program, terminal, terminal control method, and control program

Abstract

The present invention makes it easier to take measures when connection to an IoT device fails. In response to a failure of a connection means to connect to an IoT device designated by a request from a terminal of a user using a management system, the management system notifies the terminal of connection failure information indicating the failure to connect to the IoT device and positional information based on a connection point at which the connection means most recently connected to the IoT device.

Description

Management system, management method, management program, terminal, terminal control method, and control program

[0001] The present disclosure relates to a management system, a management method, a management program, and a terminal.

[0002] A technique for performing communication via a network between an IoT device and another device different from the IoT device is known. For example, Patent Document 1 describes a position identification device attached to an asset to be tracked. The position identification device transmits various information to a server or a mobile device via a network.

[0003] Japanese Patent Translation of PCT International Publication No. 2020-520581

[0004] By the way, due to a state failure such as a poor connection or a dead battery of the IoT device, the IoT device may not be able to connect to other devices. However, Patent Document 1 does not describe a technique for notifying a user that the connection between the IoT device and other devices has failed. Therefore, the user has to subjectively judge that the connection between the IoT device and other devices has failed, and then take measures against the assumed cause.

[0005] The present disclosure has been made in view of the above problems, and an exemplary object thereof is to provide a technique for facilitating measures when the IoT device cannot be connected.

[0006] An exemplary aspect of the present disclosure is a management system for managing one or more IoT devices (Internet of Things devices), comprising: a plurality of connection points for communicating with the one or more IoT devices; connection means for connecting to IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point; and connection control means for causing the connection means to connect to the IoT device specified by a request from a terminal of a user using the management system, wherein the connection control means notifies the terminal of connection failure information indicating that the connection to the IoT device has failed, and location information based on the connection point to which the connection means last connected with the IoT device, in response to the connection means failing to connect to the IoT device specified by the request from the terminal.

[0007] An exemplary management method relating to this disclosure is a management method performed by a management system for managing one or more IoT devices (Internet of Things devices), wherein the management system comprises a plurality of connection points for communicating with the one or more IoT devices, and the management method includes a connection process for connecting to IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point, and a connection control process that, in response to a request from a terminal of a user using the management system, causes the terminal to perform a connection with the IoT device specified by the request in the connection process, wherein the connection control process notifies the terminal of connection failure information indicating that the connection with the IoT device failed, and location information based on the connection point that last connected to the IoT device in the connection process.

[0008] An exemplary aspect of the present disclosure is a program that causes at least one processor to function as a management system for managing one or more IoT devices (Internet of Things devices), wherein the management system comprises a plurality of connection points for communicating with the one or more IoT devices, and causes the at least one processor to function as connection means for connecting IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point, and connection control means for causing the connection means to perform a connection with the IoT device specified by a request in response to a request from a terminal of a user using the management system, wherein the connection control means notifies the terminal of connection failure information indicating that the connection with the IoT device has failed, and location information based on the connection point to which the connection means last connected with the IoT device, in response to the connection means failing to connect with the IoT device specified by the request from the terminal.

[0009] An exemplary terminal relating to this disclosure is a terminal of a user using a management system that manages one or more IoT devices (Internet of Things devices), wherein the management system comprises a plurality of connection points for communicating with the one or more IoT devices, connection means for connecting to IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point, and connection control means for causing the connection means to perform a connection with a specific IoT device, and connection control means for notifying the terminal of connection failure information indicating that the connection means has failed to connect with the IoT device, and location information based on the connection point to which the connection means last connected with the IoT device, in response to the connection means failing to connect with the IoT device, wherein the terminal comprises providing means for providing the connection control means a request to specify an IoT device to connect with the connection means, and acquiring means for acquiring the notification of the connection failure information and the notification of the location information from the connection control means.

[0010] One exemplary aspect of this disclosure is that it can provide a technology that facilitates handling situations where connection to an IoT device fails.

[0011] This is a block diagram showing the configuration of the management system related to this disclosure. This is a flowchart showing the flow of the management method related to this disclosure. This is a block diagram showing the configuration of the management system related to this disclosure. This is a flowchart showing the flow of the management method related to this disclosure. This is a block diagram showing the configuration of the computer that functions as the management system related to this disclosure.

[0012] The following are examples of embodiments of the present invention. However, the present invention is not limited to the exemplary embodiments shown below, and various modifications are possible within the scope of the claims. For example, embodiments obtained by appropriately combining some or all of the technologies (things or methods) employed in each of the exemplary embodiments shown below may also be included in the scope of the present invention. Furthermore, embodiments obtained by appropriately omitting some of the technologies employed in each of the exemplary embodiments shown below may also be included in the scope of the present invention. In addition, the effects mentioned in each of the exemplary embodiments shown below are examples of effects that can be expected in that exemplary embodiment and do not define the scope of the present invention. That is, embodiments that do not produce the effects mentioned in each of the exemplary embodiments shown below may also be included in the scope of the present invention.

[0013] [First Exemplary Embodiment] A first exemplary embodiment, which is an example of an embodiment of the present invention, will be described in detail with reference to the drawings. This exemplary embodiment is the basic form for each of the exemplary embodiments described later. The scope of application of each technology adopted in this exemplary embodiment is not limited to this exemplary embodiment. That is, each technology adopted in this exemplary embodiment can also be adopted in other exemplary embodiments included in this disclosure, to the extent that no particular technical problems occur. Furthermore, each technology shown in the drawings referenced to explain this exemplary embodiment can also be adopted in other exemplary embodiments included in this disclosure, to the extent that no particular technical problems occur.

[0014] (Configuration of Management System 1) The configuration of Management System 1 will be explained with reference to Figure 1. Figure 1 is a block diagram showing the configuration of Management System 1. Management System 1 is a system that manages one or more IoT devices (Internet of Things devices) 3.

[0015] As shown in Figure 1, the management system 1 comprises a connection point 4, a connection unit 11, and a connection control unit 12. The connection unit 11 is an example of a configuration that realizes a connection means, and the connection control unit 12 is an example of a configuration that realizes a connection control means. For example, if the management system 1 comprises at least one processor, the connection unit 11 and the connection control unit 12 are realized by the execution of a program by that at least one processor.

[0016] The management system 1 is equipped with multiple connection points 4. Each connection point 4 is a point for communicating with one or more IoT devices 3. The connection points 4 form a network to which IoT devices 3 and connection units 11 can connect. The network formed by the connection points 4 includes a mobile communication network. The communication method of the mobile communication network is not particularly limited, but one example is the 5G communication method. In this case, an example of a connection point 4 is a base station (gNB) that forms a 5G network. Note that in Figure 1, for the sake of clarity, only one connection point 4 is shown, and the other connection points 4 are omitted from the illustration.

[0017] IoT device 3 is a device equipped with wireless communication capabilities. IoT device 3 may also be a so-called ambient IoT (Ambient power-enabled Internet of Things) device. An ambient IoT device is a device that collects energy such as radio waves or light present in the surrounding environment and converts the collected energy into a power source for the device itself.

[0018] The connection unit 11 connects to IoT devices 3 within the connection range of each of the multiple connection points 4 via the corresponding connection point 4. That is, the connection unit 11 connects to IoT devices 3 within the connection range of a specific connection point 4 via that specific connection point 4. The connection control unit 12, in response to a request from the terminal 2, causes the connection unit 11 to perform a connection with the IoT device 3 specified by the request. That is, the connection unit 11 connects to a specific IoT device 3 in accordance with a request from the terminal 2.

[0019] The connection control unit 12 notifies the terminal 2 of connection failure information and location information when the connection unit 11 fails to connect with the IoT device 3 specified by the request from the terminal 2. The connection failure information indicates that the connection unit 11 failed to connect with the IoT device 3 specified by the request from the terminal 2. The location information is the location information based on the connection point 4 where the connection unit 11 last connected with the IoT device 3. The location information notified to the terminal 2 may indicate the location of the last connected connection point 4, or it may indicate the location of the IoT device 3 derived from the last connected connection point 4.

[0020] Terminal 2 is a user terminal for the management system 1 and is a device that can connect to a mobile communication network. Examples of terminal 2 include smartphones, tablet terminals, or personal computers. Terminal 2 connects to the management system 1 via each connection point 4. Terminal 2 comprises a providing unit 21 and an acquisition unit 22. The providing unit 21 is an example of a configuration that realizes the providing means. The acquisition unit 22 is an example of a configuration that realizes the acquisition means.

[0021] The providing unit 21 provides the connection control unit 12 with a request to specify the IoT device 3 to be connected to the connection unit 11. The acquisition unit 22 acquires connection failure information notification (hereinafter referred to as connection failure information notification) and location information notification (hereinafter referred to as location information notification) from the connection control unit 12.

[0022] (Flow of Management Method S1) The flow of management method S1 will be explained with reference to Figure 2. Figure 2 is a flowchart showing the flow of management method S1. As shown in Figure 2, management method S1 includes connection processing S11 and connection control processing S12.

[0023] In connection processing S11, at least one processor (for example, connection unit 11) connects to IoT devices 3 within the connection range of each of the multiple connection points 4 via the corresponding connection point 4. That is, in connection processing S11, connection unit 11 connects to IoT devices 3 within the connection range of a specific connection point 4 via that specific connection point 4. In connection control processing S12, at least one processor (for example, connection control unit 12) causes connection unit 11 to perform a connection with the IoT device 3 specified by the request from terminal 2 in response to a request from terminal 2. In connection control processing S12, connection control unit 12 receives a request from provision unit 21. In connection control processing S12, connection control unit 12 notifies terminal 2 of connection failure information and location information in response to the connection unit 11 failing to connect with the IoT device 3 specified by the request from terminal 2.

[0024] (Effects of Management System 1 and Management Method S1) As described above, in Management System 1 and Management Method S1, a configuration is adopted in which the connection control unit 12 notifies the terminal 2 that has failed to connect with a specific IoT device 3 of connection failure information and location information. The owner of terminal 2 can recognize that the connection between IoT device 3 and connection unit 11 has failed by the connection failure information notification. In addition, the owner of terminal 2 can check the status of IoT device 3 by finding IoT device 3 based on the location information notification. Therefore, the effect is obtained that it is possible to easily take action when it is not possible to connect to IoT device 3.

[0025] (Effects of Terminal 2) As described above, Terminal 2 employs a configuration in which the providing unit 21 provides a request to specify the IoT device 3 to connect to the connection unit 11, and the acquisition unit 22 acquires connection failure information notification and location information notification from the connection control unit 12. The owner of Terminal 2 can recognize that the connection between the IoT device 3 and the connection unit 11 has failed by the connection failure information notification. In addition, the owner of Terminal 2 can check the status of the IoT device 3 by finding the IoT device 3 based on the location information notification. Therefore, the effect is obtained that it is possible to easily deal with the situation when it is not possible to connect to the IoT device 3.

[0026] [Second Exemplary Embodiment] A second exemplary embodiment, which is an example of an embodiment of the present invention, will be described in detail with reference to the drawings. Components having the same function as those described in the above-described exemplary embodiment are denoted by the same reference numerals, and their descriptions are omitted as appropriate. The scope of application of each technology adopted in this exemplary embodiment is not limited to this exemplary embodiment. That is, each technology adopted in this exemplary embodiment can also be adopted in other exemplary embodiments included in this disclosure, to the extent that no particular technical problems arise. Furthermore, each technology shown in the drawings referenced to describe this exemplary embodiment can also be adopted in other exemplary embodiments included in this disclosure, to the extent that no particular technical problems arise.

[0027] (Configuration of Management System 1A) The configuration of Management System 1A will be explained with reference to Figure 3. Figure 3 is a block diagram showing the configuration of Management System 1A. Management System 1A is used, as an example, in a system for managing the inventory of goods. As shown in Figure 3, Management System 1A includes an inventory management platform 10.

[0028] The inventory management platform 10 is a management device that manages one or more IoT devices 3. The inventory management platform 10 may be, for example, a server installed in a cloud environment. The inventory management platform 10 connects to terminal 2 via a mobile communication network. The inventory management platform 10 and IoT devices 3 may communicate with each other via a 5G network 40. The 5G network 40 is, for example, a local 5G network. The 5G network 40 includes a 5GC 41 connected to a gNB 42. The 5GC 41 constructs a local 5G network.

[0029] gNB42 is a base station that constitutes a 5G Radio Access Network (5G-RAN). gNB42 is an example of a connection point. gNB42 is a connection point for communicating with one or more IoT devices 3. Management system 1A is equipped with multiple gNB42s. Note that in Figure 3, for the sake of clarity, only one gNB42 is shown, and the other gNB42s are omitted from the illustration.

[0030] 5GC41 includes AMF (Access and Mobility Management Function), SMF (Session Management Function), UDM (Unified Data Management), and UPF (User Plane Function) as network functions (NFs). AMF, SMF, and UDM function as C-Planes (Control Planes) for the communication of control signals. AMF manages registration, connections, and mobility. SMF manages sessions, etc. UDM holds various types of data. UPF functions as a U-Plane (User Plane) for the communication of user data. Note that 5GC41 may also include UDR (Unified Data Repository), AUSF (Authentication Server Function), and NSSF (Network Slice Selection Function) as NFs.

[0031] The inventory management platform 10 includes a registration unit 13 and a storage unit 14, in addition to the connection unit 11 and connection control unit 12 provided by the management system 1. The registration unit 13 is an example of a configuration that realizes a registration means. The registration unit 13 registers various information, for example, by storing various information in the storage unit 14. The storage unit 14 stores various information.

[0032] The registration unit 13 may register location information 15, which is information based on the gNB 42 that the connection unit 11 last connected to a specific IoT device 3. That is, the storage unit 14 may store location information 15. The registration unit 13 may also register location information 15 that is periodically provided by the 5GC 41. In this case, the registration unit 13 updates the registered location information 15.

[0033] The registration unit 13 may register connection failure cause information 16 indicating the reason why the connection between the connection unit 11 and the IoT device 3 failed. That is, the storage unit 14 may store the connection failure cause information 16. The connection failure cause information 16 includes information such as connection failure, poor condition, or loss of the IoT device 3. Poor condition of the IoT device 3 includes, for example, a dead battery in the IoT device 3.

[0034] (Flow of Management Method S1A) The management system 1A configured as described above executes management method S1A. The flow of management method S1A will be explained with reference to Figures 4 and 5. Figures 4 and 5 are flowcharts showing the flow of management method S1A. As shown in Figures 4 and 5, management method S1A includes steps S101 to S115 and steps S120 to S123.

[0035] Figure 4 shows the flow of management method S1A when the connection unit 11 successfully connects with the IoT device 3 specified by a subsequent request from terminal 2. The user of terminal 2 positions terminal 2 within the connection range of a gNB 42 that enables connection to a specific IoT device 3 from among multiple gNB 42s. That is, in the following management method S1A, terminal 2 attempts to connect to the specific IoT device 3 via a gNB 42 that enables connection to a specific IoT device 3 from among multiple gNB 42s.

[0036] As shown in Figure 4, in step S101, the connection control unit 12 obtains an inventory information request from the provisioning unit 21 via the gNB 42. That is, in step S101, the provisioning unit 21 provides an inventory information request to the connection control unit 12 via the gNB 42. In step S101, the provisioning unit 21 provides an inventory information request that includes specifying the IoT device 3 to be connected to the connection unit 11. The inventory information request is a request for the terminal 2 to obtain inventory information held by the IoT device 3.

[0037] In step S102, the connection unit 11 requests the 5GC41 to collect inventory information in response to the inventory information request. That is, in step S102, the connection unit 11 connects to the IoT device 3 within the connection range of the gNB42 via the gNB42. In step S102, the connection control unit 12, in response to the inventory information request from the terminal 2, causes the connection unit 11 to perform a connection with the IoT device 3 specified by the inventory information request. Step S102 is an example of a connection process and is also an example of a connection control process.

[0038] In step S103, 5GC41 provides an active control signal to the IoT device 3 specified by the inventory information request, in response to the acquisition of the inventory information acquisition request, to activate the IoT device 3. In step S104, 5GC41 has not yet received a response from the IoT device 3 specified by the inventory information request.

[0039] In step S105, the 5GC41 notifies the connection control unit 12 that the connection with the IoT device 3 specified by the inventory information request has failed. That is, in step S105, the connection control unit 12 receives a notification from the 5GC41 indicating that the connection with the IoT device 3 specified by the inventory information request has failed. In step S106, the connection unit 11 checks the location information 15 stored in the storage unit 14.

[0040] In step S107, the connection control unit 12 notifies the acquisition unit 22 via the gNB 42 of connection failure information indicating that it failed to connect to the IoT device 3 specified by the inventory information request, and location information 15 based on the gNB 42 that the connection unit 11 last connected to the IoT device 3 specified by the inventory information request. That is, in step S107, the acquisition unit 22 receives the connection failure information notification and the location information notification from the connection control unit 12 via the gNB 42. Step S107 is an example of connection control processing.

[0041] In step S107, if connection failure cause information 16 is registered for the IoT device 3 specified by the inventory information request, the connection control unit 12 may additionally notify the acquisition unit 22 of the connection failure cause information 16 registered together with the connection failure information. That is, in step S107, the acquisition unit 22 may acquire a notification of the connection failure cause information 16 from the connection control unit 12. By step S107, the owner of the terminal 2 to which the connection failure information and the position information 15 are notified can take measures to solve the connection problem for the IoT device 3 specified by the inventory information request. Also, by notifying the connection failure cause information 16 in step S107, the owner of the terminal 2 can take measures to solve the connection problem of the IoT device 3 based on the past connection failure causes.

[0042] In step S108, the connection control unit 12 acquires a new inventory information request from the providing unit 21 via the gNB 42. That is, in step S108, the providing unit 21 provides a new inventory information request to the connection control unit 12 via the gNB 42. In step S108, the providing unit 21 provides an inventory information request including the specification of the IoT device 3 connected to the connection unit 11. Step S108 is executed after the owner of the terminal 2 has taken measures to eliminate the connection problem for the IoT device 3 found based on the position information 15.

[0043] In step S109, the connection unit 11 requests inventory information collection from the 5GC 41 in response to the new inventory information request. That is, in step S109, the connection unit 11 connects to the IoT devices 3 within the connection range of the gNB 42 via the gNB 42. In step S109, the connection control unit 12 causes the connection unit 11 to execute a connection to the IoT device 3 specified by the new inventory information request in response to the new inventory information request from the terminal 2.

[0044] In step S110, the 5GC 41 provides an active control signal for activating the IoT device 3 to the IoT device 3 specified by the inventory information request in response to the acquisition of the inventory information collection request.

[0045] In step S111, IoT device 3 provides a notification to 5GC41 indicating that it has activated itself in accordance with the acquired active control signal. In step S111, IoT device 3 may also provide status information of itself to 5GC41. The status information of IoT device 3 includes communication information of IoT device 3, such as radio wave strength, and operation information of IoT device 3, such as battery level.

[0046] In step S112, the 5GC41, upon receiving a notification from the IoT device 3 indicating that it has become active, provides the connection control unit 12 with a notification indicating that the connection with the IoT device 3 specified in the subsequent inventory information request has been successful. That is, in step S112, the connection control unit 12 receives a notification from the 5GC41 indicating that the connection between the IoT device 3 specified in the inventory information request and the connection unit 11 has been successful. In step S112, the connection control unit 12 may also receive status information of the IoT device 3 specified in the subsequent inventory information request from the 5GC41.

[0047] In step S113, the connection control unit 12 notifies the acquisition unit 22 of connection success information indicating that the connection with the IoT device 3 has been successfully established, in response to the connection unit 11 successfully establishing a connection with the IoT device 3 specified by the re-inventory information request. The connection control unit 12 notifies the acquisition unit 22 of the connection success information via the gNB 42. That is, in step S113, the acquisition unit 22 receives the notification of connection success information from the connection control unit 12 via the gNB 42. In step S113, the acquisition unit 22 may also obtain status information of the IoT device 3 specified by the re-inventory information request from the connection control unit 12.

[0048] In step S114, the connection control unit 12 acquires a registration request for the connection failure cause information 16 provided from the providing unit 21 via the gNB 42. That is, in step S114, the providing unit 21 provides the registration request for the connection failure cause information 16 to the connection control unit 12 via the gNB 42. The registration request for the connection failure cause information 16 in step S114 includes the assumed connection failure causes from the series of processes from step S101 to step S113. In step S114, the providing unit 21 may include, in the registration request, that the connection of the IoT device 3 is poor or the state of the IoT device 3 is poor as the connection failure cause information 16 based on the acquired state information of the IoT device 3.

[0049] In step S115, the registration unit 13 registers the connection failure cause information 16 in response to the acquired registration request. In step S115, the registration unit 13 registers that the connection of the IoT device 3 specified by the re - inventory information request is poor or the state of the IoT device 3 is poor as the connection failure cause information 16. In step S115, the registration unit 13 may register that the connection of the IoT device 3 is poor or the state of the IoT device 3 is poor based on the acquired state information of the IoT device 3.

[0050] FIG. 5 shows the flow of the management method S1A when the connection of the connection unit 11 with the IoT device 3 specified by the re - request from the terminal 2 fails. As shown in FIG. 5, steps S101 to S110 are the same as steps S101 to S110 shown in FIG. 4, so the description is omitted. After step S110, steps S120 to S123 are performed.

[0051] In step S120, the 5GC 41 has not acquired a response from the IoT device 3 specified by the re - inventory information request. In step S121, the 5GC 41 notifies the connection control unit 12 that the connection with the IoT device 3 specified by the re - inventory information request has failed. That is, in step S121, the connection control unit 12 acquires a notification indicating that the connection with the IoT device 3 specified by the re - inventory information request has failed from the 5GC 41.

[0052] In step S122, the registration unit 13 registers that the IoT device 3 has been lost as connection failure cause information 16, in response to the failure to connect to the IoT device 3 specified by the second inventory information request. In step S123, the connection control unit 12 notifies the acquisition unit 22 via the gNB 42 of the second connection failure information, indicating that it failed to reconnect to the IoT device 3 specified by the second inventory information request, and loss information, indicating that the IoT device 3 has been lost. That is, in step S123, the acquisition unit 22 receives the notification of the second connection failure information and the notification of the loss information, indicating that the IoT device 3 has been lost, from the connection control unit 12 via the gNB 42.

[0053] (Effects of Management System 1A) As described above, Management System 1A employs a configuration in which the connection control unit 12 notifies the terminal 2 of connection failure information and location information 15. This makes it possible to obtain the same effects as Management System 1.

[0054] As described above, in management system 1A, the connection control unit 12 notifies terminal 2 of a connection success notification when it is possible to connect IoT device 3 specified by the re-inventory information request with inventory management platform 10. Therefore, in addition to the effects of management system 1, management system 1A provides the effect of being able to recognize that the connection problem with IoT device 3 has been resolved.

[0055] Furthermore, in management system 1A, a configuration is adopted in which the registration unit 13 registers connection failure cause information 16. Therefore, in addition to the effects achieved by management system 1, management system 1A provides the effect of being able to manage connection problems of IoT device 3. If connection problems of IoT device 3 can be managed, for example, the inventory management platform 10 can troubleshoot based on the registered connection failure cause information 16.

[0056] Furthermore, in the management system 1A, the registration unit 13 is configured to register, as connection failure cause information 16, that the IoT device 3 is either poorly connected or in a bad state, in response to the connection unit 11 successfully connecting with the IoT device 3 specified by the inventory management request. Therefore, in addition to the effects of the management system 1, the management system 1A also has the effect of being able to register the cause of the connection failure information 16 when the connection problem of the IoT device 3 is resolved.

[0057] Furthermore, in the management system 1A, the registration unit 13 registers that the IoT device 3 has been lost as connection failure cause information 16, and the connection control unit 12 notifies the terminal 2 of the second connection failure information and the information that the IoT device 3 has been lost. Therefore, in addition to the effects achieved by the management system 1, the management system 1A has the effect of making it easier to deal with the situation when it is not possible to reconnect with the IoT device 3.

[0058] [Example of implementation by software] Some or all of the functions of the management systems 1, 1A (hereinafter also referred to as "each of the above devices") may be implemented by hardware such as integrated circuits (IC chips) or by software.

[0059] In the latter case, each of the above devices is implemented, for example, by a computer that executes instructions for a program, which is software that realizes each function. An example of such a computer (hereinafter referred to as computer C) is shown in Figure 6. Figure 6 is a block diagram showing the hardware configuration of computer C, which functions as each of the above devices.

[0060] Computer C comprises at least one processor C1 and at least one memory C2. Memory C2 stores a program P for operating Computer C as each of the above-mentioned devices. In Computer C, the processor C1 reads and executes the program P from memory C2, thereby realizing each of the above-mentioned devices.

[0061] For processor C1, for example, a CPU (Central Processing Unit), GPU (Graphic Processing Unit), DSP (Digital Signal Processor), MPU (Micro Processing Unit), FPU (Floating Point Number Processing Unit), PPU (Physics Processing Unit), TPU (Tensor Processing Unit), quantum processor, microcontroller, or a combination thereof can be used. For memory C2, for example, flash memory, HDD (Hard Disk Drive), SSD (Solid State Drive), or a combination thereof can be used.

[0062] Furthermore, computer C may also be equipped with RAM (Random Access Memory) for loading program P at runtime and for temporarily storing various data. Computer C may also be equipped with a communication interface for sending and receiving data with other devices. Furthermore, computer C may also be equipped with an input / output interface for connecting input / output devices such as a keyboard, mouse, display, and printer.

[0063] Furthermore, program P can be recorded on a non-temporary, tangible recording medium M that is readable by computer C. Such recording medium M can include, for example, tape, disk, card, semiconductor memory, or programmable logic circuitry. Computer C can acquire program P via such recording medium M. Program P can also be transmitted via a transmission medium. Such transmission mediums can include, for example, a communication network or broadcast waves. Computer C can also acquire program P via such transmission medium.

[0064] Furthermore, each of the above functions of each of the above devices may be implemented by a single processor in a single computer, by multiple processors in a single computer working together, or by multiple processors in each of multiple computers working together. In addition, the programs for implementing each of the above functions in each of the above devices may be stored in a single memory in a single computer, distributed and stored in multiple memories in a single computer, or distributed and stored in multiple memories in each of multiple computers.

[0065] [Addendum A] This disclosure includes the technologies described in the following addendums. However, the present invention is not limited to the technologies described in the following addendums, and various modifications are possible within the scope of the claims.

[0066] (Appendix A1) A management system for managing one or more IoT devices (Internet of Things devices), comprising: a plurality of connection points for communicating with the one or more IoT devices; connection means for connecting to IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point; and connection control means for causing the connection means to perform a connection with the IoT device specified by a request from a terminal of a user using the management system, wherein the connection control means notifies the terminal of connection failure information indicating that the connection with the IoT device has failed, and location information based on the connection point to which the connection means last connected with the IoT device, in response to the connection means failing to connect with the IoT device specified by the request from the terminal.

[0067] (Appendix A2) The management system according to Appendix A1, wherein the connection control means notifies the terminal of connection success information indicating that the connection has been successfully established with the IoT device specified by the subsequent request from the terminal.

[0068] (Appendix A3) The management system according to Appendix A1 or A2, further comprising registration means for registering connection failure cause information indicating the reason why the connection between the connection means and the IoT device failed.

[0069] (Appendix A4) The management system described in Appendix A3, wherein the registration means registers, in response to the connection means successfully connecting with the IoT device specified by the subsequent request from the terminal, that the IoT device is not connected or is in a bad state as connection failure cause information.

[0070] (Appendix A5) The management system as described in Appendix A3, wherein the registration means registers that the IoT device is lost as connection failure cause information in response to the connection means failing to connect to the IoT device specified by the subsequent request from the terminal, and the connection control means notifies the terminal of subsequent connection failure information indicating that reconnection to the IoT device has failed, and loss information indicating that the IoT device has been lost.

[0071] [Addendum B] This disclosure includes the technologies described in the following addendums. However, the present invention is not limited to the technologies described in the following addendums, and various modifications are possible within the scope of the claims.

[0072] (Appendix B1) A management method performed by a management system for managing one or more IoT devices (Internet of Things devices), wherein the management system comprises a plurality of connection points for communicating with the one or more IoT devices, the management method includes: a connection process for connecting to IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point, and a connection control process that, in response to a request from a terminal of a user using the management system, causes the terminal to perform a connection with the IoT device specified by the request in the connection process, wherein the connection control process, in response to a failure to connect to the IoT device specified by the request from the terminal in the connection process, notifies the terminal of connection failure information indicating that the connection with the IoT device failed, and location information based on the connection point that last connected to the IoT device in the connection process.

[0073] (Appendix B2) The management method described in Appendix B1, wherein in the connection control process, in response to the successful connection with the IoT device specified by the subsequent request from the terminal in the connection process, connection success information indicating that the connection with the IoT device has been successful is notified to the terminal.

[0074] (Appendix B3) The management method according to Appendix B1 or B2, further comprising a registration process for registering connection failure cause information indicating the reason why the connection between the connection means and the IoT device failed.

[0075] (Appendix B4) The management method described in Appendix B3, wherein in the registration process, in response to the successful connection with the IoT device specified by the subsequent request from the terminal in the connection process, the connection failure cause information is registered as either a connection failure of the IoT device or a state defect of the IoT device.

[0076] (Appendix B5) The management method described in Appendix B3, wherein in the registration process, in response to the failure of the connection to the IoT device specified by the subsequent request from the terminal in the connection process, the loss of the IoT device is registered as the cause of the connection failure, and in the connection control process, the terminal is notified of a second connection failure indicating that reconnection to the IoT device failed, and loss information indicating that the IoT device has been lost.

[0077] [Addendum C] This disclosure includes the technologies described in the following addendums. However, the present invention is not limited to the technologies described in the following addendums, and various modifications are possible within the scope of the claims.

[0078] (Appendix C1) A program that causes at least one processor to function as a management system for managing one or more IoT devices (Internet of Things devices), wherein the management system comprises a plurality of connection points for communicating with the one or more IoT devices, the at least one processor to function as connection means for connecting IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point, and connection control means for causing the connection means to perform a connection with the IoT device specified by a request in response to a request from a terminal of a user using the management system, wherein the connection control means notifies the terminal of connection failure information indicating that the connection with the IoT device has failed, and location information based on the connection point to which the connection means last connected with the IoT device, in response to the connection means failing to connect with the IoT device specified by the request from the terminal.

[0079] (Appendix C2) The connection control means is a management program as described in Appendix C1, which notifies the terminal of connection success information indicating that the connection has been successfully established with the IoT device specified by the subsequent request from the terminal.

[0080] (Appendix C3) The management program according to Appendix C1 or C2, wherein the at least one processor further functions as a registration means for registering connection failure cause information indicating the cause of the connection failure between the connection means and the IoT device.

[0081] (Appendix C4) The management program described in Appendix C3, wherein the registration means registers, in response to the connection means successfully connecting with the IoT device specified by the subsequent request from the terminal, that the IoT device is not connected or is in a bad state as connection failure cause information.

[0082] (Appendix C5) The management program as described in Appendix C3, wherein the registration means registers that the IoT device has been lost as connection failure cause information when the connection means fails to connect to the IoT device specified by the subsequent request from the terminal, and the connection control means notifies the terminal of a second connection failure information indicating that reconnection to the IoT device has failed, and loss information indicating that the IoT device has been lost.

[0083] [Addendum D] This disclosure includes the technologies described in the following addendums. However, the present invention is not limited to the technologies described in the following addendums, and various modifications are possible within the scope of the claims.

[0084] (Appendix D1) A terminal of a user that uses a management system for managing one or more IoT devices (Internet of Things devices), wherein the management system comprises: a plurality of connection points for communicating with the one or more IoT devices; connection means for connecting to IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point; connection control means for causing the connection means to perform a connection with a specific IoT device, and which, in response to the connection means failing to connect with the IoT device, notifies the terminal of connection failure information indicating that the connection with the IoT device has failed, and location information based on the connection point to which the connection means last connected with the IoT device, wherein the terminal comprises: providing means for providing the connection control means a request to specify an IoT device to connect with the connection means; and acquiring means for acquiring the notification of the connection failure information and the notification of the location information from the connection control means.

[0085] (Note D2) The terminal as described in Note D1, wherein the connection control means notifies the terminal of connection success information indicating that the connection has been successfully established with the IoT device specified by the subsequent request from the terminal, the providing means provides the connection control means again with a request specifying the IoT device to be connected to the connection means, and the acquiring means acquires the notification of connection success information from the connection control means.

[0086] (Note D3) The management system further comprises registration means for registering that the IoT device is lost as connection failure cause information indicating the reason for the failure of the connection between the connection means and the IoT device, in response to the connection means failing to connect to the IoT device specified by the subsequent request from the terminal; the connection control means notifies the terminal of subsequent connection failure information indicating that reconnection to the IoT device has failed, and loss information indicating that the IoT device has been lost; and the terminal acquisition means acquires the notification of the loss information from the connection control means, as described in Note D1 or D2.

[0087] [Addendum E] This disclosure includes the technologies described in the following addendums. However, the present invention is not limited to the technologies described in the following addendums, and various modifications are possible within the scope of the claims.

[0088] (Appendix E1) A management device provided in a management system for managing one or more IoT devices (Internet of Things devices), wherein the management system comprises a plurality of connection points for communicating with the one or more IoT devices, the management device comprises connection means for connecting to IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point, and connection control means for causing the connection means to perform a connection with the IoT device specified by a request from a terminal of a user using the management system, wherein the connection control means notifies the terminal of connection failure information indicating that the connection with the IoT device has failed, and location information based on the connection point to which the connection means last connected with the IoT device, in response to the connection means failing to connect with the IoT device specified by the request from the terminal.

[0089] (Appendix E2) The management device as described in Appendix E1, wherein the connection control means notifies the terminal of connection success information indicating that the connection has been successfully established with the IoT device specified by the subsequent request from the terminal.

[0090] (Appendix E3) The management device according to Appendix E1 or E2, further comprising registration means for registering connection failure cause information indicating the reason why the connection between the connection means and the IoT device failed.

[0091] (Appendix E4) The management device as described in Appendix E3, wherein the registration means registers, in response to the connection means successfully connecting with the IoT device specified by the subsequent request from the terminal, that the IoT device is not connected or is in a bad state as connection failure cause information.

[0092] (Appendix E5) The management device as described in Appendix E3, wherein the registration means registers that the IoT device is lost as connection failure cause information in response to the connection means failing to connect to the IoT device specified by the subsequent request from the terminal, and the connection control means notifies the terminal of a second connection failure information indicating that reconnection to the IoT device has failed, and loss information indicating that the IoT device has been lost.

[0093] [Addendum F] This disclosure includes the technologies described in the following addendums. However, the present invention is not limited to the technologies described in the following addendums, and various modifications are possible within the scope of the claims.

[0094] (Appendix F1) A management system for managing one or more IoT devices (Internet of Things devices), comprising: a plurality of connection points for communicating with the one or more IoT devices; and at least one processor, wherein the at least one processor performs: connection processing to connect to IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point; and connection control processing to perform connection with the IoT device specified in the connection processing in response to a request from a terminal of a user using the management system, and in the connection control processing, in response to a failure to connect to the IoT device specified in the request from the terminal in the connection processing, connection failure information indicating that the connection with the IoT device failed, and location information based on the connection point that last connected to the IoT device in the connection processing, is notified to the terminal.

[0095] (Appendix F2) The management system described in Appendix F1, wherein in the connection control process, in response to the successful connection with the IoT device specified by the subsequent request from the terminal in the connection process, the management system notifies the terminal of connection success information indicating that the connection with the IoT device has been successful.

[0096] (Appendix F3) The management system according to Appendix F1 or F2, wherein at least one processor further performs a registration process to register connection failure cause information indicating the reason why the connection between the connection means and the IoT device failed.

[0097] (Appendix F4) The management system described in Appendix F3, wherein in the registration process, in response to the successful connection with the IoT device specified by the subsequent request from the terminal in the connection process, the management system registers as connection failure cause information that the IoT device is not connected or is in a bad state.

[0098] (Appendix F5) The management system described in Appendix F3, wherein in the registration process, in response to the failure of the connection to the IoT device specified by the subsequent request from the terminal in the connection process, the system registers that the IoT device has been lost as the cause of the connection failure, and in the connection control process, the system notifies the terminal of a second connection failure indicating that reconnection to the IoT device failed, and loss information indicating that the IoT device has been lost.

[0099] [Addendum G] This disclosure includes the technologies described in the following addendums. However, the present invention is not limited to the technologies described in the following addendums, and various modifications are possible within the scope of the claims.

[0100] (Appendix G1) A non-temporary recording medium that records a management program, which causes at least one processor to function as a management system for managing one or more IoT devices (Internet of Things devices), wherein the management system comprises a plurality of connection points for communicating with the one or more IoT devices, and causes the at least one processor to execute a connection process for connecting to IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point, and a connection control process in response to a request from a terminal of a user using the management system, causing the terminal to execute a connection with the IoT device specified in the connection process, and in the connection control process, in response to a failure to connect to the IoT device specified in the request from the terminal in the connection process, connection failure information indicating a failure to connect to the IoT device, and location information based on the connection point that last connected to the IoT device in the connection process, the management program.

[0101] This application claims priority based on Japanese Patent Application No. 2024-172759, filed on 1 October 2024, and incorporates all of its disclosures herein.

[0102] 1.1A Management system 2. Terminal 3. IoT device 4. Connection point 10. Inventory management platform 11. Connection unit 12. Connection control unit 13. Registration unit 15. Location information 16. Connection failure cause information 21. Provision unit 22. Acquisition unit 40. 5G network

Claims

A management system for managing one or more IoT devices (Internet of Things devices), Multiple connection points for communicating with the aforementioned one or more IoT devices, Connection means for connecting IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point, The system includes connection control means that, in response to a request from a terminal of a user using the management system, causes the connection means to perform a connection with the IoT device specified by the request, The connection control means is a management system that, in response to the connection means failing to connect to the IoT device specified by the request from the terminal, notifies the terminal of connection failure information indicating that the connection to the IoT device failed, and location information based on the connection point where the connection means last connected to the IoT device. 　 The management system according to claim 1, wherein the connection control means notifies the terminal of connection success information indicating that the connection has been successfully established with the IoT device specified by the subsequent request from the terminal. 　 The management system according to claim 1 or 2, further comprising a registration means for registering connection failure cause information indicating the reason why the connection between the connection means and the IoT device failed. 　 The management system according to claim 3, wherein the registration means registers, in response to the connection means successfully connecting with the IoT device specified by the subsequent request from the terminal, that the IoT device is not connected or is in a bad state as connection failure cause information. 　 The registration means, in response to the connection means failing to connect with the IoT device specified by the subsequent request from the terminal, registers as the loss of the IoT device as the cause of the connection failure information. The management system according to claim 3, wherein the connection control means notifies the terminal of a second connection failure indicating that reconnection with the IoT device has failed, and a loss information indicating that the IoT device has been lost. 　 A management method performed by a management system that manages one or more IoT devices (Internet of Things devices), The management system includes multiple connection points for communicating with the one or more IoT devices. The aforementioned management method is, A connection process that connects IoT devices within the connection range of each of the aforementioned plurality of connection points via the corresponding connection point, The connection control process includes, in response to a request from a user's terminal using the management system, causing the connection process to execute a connection with the IoT device specified by the request, In the connection control process, a management method is provided which, in response to a failure in connecting to the IoT device specified by the request from the terminal during the connection process, the terminal is notified of connection failure information indicating that it failed to connect to the IoT device, and location information based on the connection point to which it last connected during the connection process. 　 The management method according to claim 6, wherein in the connection control process, in response to the successful connection with the IoT device specified by the subsequent request from the terminal in the connection process, connection success information indicating that the connection with the IoT device has been successful is notified to the terminal. 　 The management method according to claim 6 or 7, further comprising a registration process for registering connection failure cause information indicating the reason why the connection process between the connection process and the IoT device failed. 　 The management method according to claim 8, wherein in the registration process, in response to the successful connection with the IoT device specified by the subsequent request from the terminal in the connection process, the connection failure cause information is registered as either a connection failure of the IoT device or a state defect of the IoT device. 　 In the registration process, if the connection to the IoT device specified by the subsequent request from the terminal fails in the connection process, the loss of the IoT device is registered as the cause of the connection failure. The management method according to claim 8, wherein the connection control process notifies the terminal of a further connection failure information indicating that reconnection with the IoT device has failed, and a loss information indicating that the IoT device has been lost. 　 A program that causes at least one processor to function as a management system for managing one or more IoT devices (Internet of Things devices), The management system includes multiple connection points for communicating with the one or more IoT devices. The aforementioned at least one processor, Connection means for connecting IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point, In response to a request from a terminal of a user using the management system, the connection control means is configured to cause the connection means to perform a connection with the IoT device specified by the request. The connection control means is a management program that, in response to the connection means failing to connect to the IoT device specified by the request from the terminal, notifies the terminal of connection failure information indicating that the connection to the IoT device failed, and location information based on the connection point where the connection means last connected to the IoT device. 　 The management program according to claim 11, wherein the connection control means notifies the terminal of connection success information indicating that the connection has been successfully established with the IoT device specified by the subsequent request from the terminal. 　 The management program according to claim 11 or 12, wherein the at least one processor further functions as a registration means for registering connection failure cause information indicating the cause of a connection failure between the connection means and the IoT device. 　 The management program according to claim 13, wherein the registration means registers, in response to the connection means successfully connecting with the IoT device specified by the subsequent request from the terminal, that the IoT device is not connected or is in a bad state as connection failure cause information. 　 The registration means, in response to the connection means failing to connect with the IoT device specified by the subsequent request from the terminal, registers as the loss of the IoT device as the cause of the connection failure information. The management program according to claim 13, wherein the connection control means notifies the terminal of further connection failure information indicating that reconnection with the IoT device has failed, and loss information indicating that the IoT device has been lost. 　 A terminal used by a user of a management system that manages one or more IoT devices (Internet of Things devices), The aforementioned management system is Multiple connection points for communicating with the aforementioned one or more IoT devices, Connection means for connecting IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point, Connection control means for causing the connection means to perform a connection with a specific IoT device, comprising connection control means for notifying the terminal of connection failure information indicating that the connection means failed to connect with the IoT device, and location information based on the connection point where the connection means last connected with the IoT device, in response to the connection means failing to connect with the IoT device, The aforementioned terminal is A providing means that provides the connection control means with a request to specify an IoT device to be connected to the connection means, A terminal comprising: an acquisition means for obtaining notification of connection failure information and notification of location information from the connection control means. 　 The connection control means, in response to the successful connection of the IoT device specified by the subsequent request from the terminal, notifies the terminal of connection success information indicating that the connection to the IoT device has been successful. The providing means again provides the connection control means with a request to specify the IoT device to be connected to the connection means. The terminal according to claim 16, wherein the acquisition means acquires notification of connection success information from the connection control means. 　 The aforementioned management system is The connection means further includes a registration means that, in response to the failure of the connection means to connect with the IoT device specified by the subsequent request from the terminal, registers the loss of the IoT device as connection failure cause information indicating the reason for the failure of the connection between the connection means and the IoT device. The connection control means notifies the terminal of a second connection failure indicating that reconnection with the IoT device has failed, and a loss information indicating that the IoT device has been lost. The terminal according to claim 16 or 17, wherein the acquisition means acquires notification of the loss information from the connection control means. 　 A terminal control method for controlling a terminal of a user using a management system that manages one or more IoT devices (Internet of Things devices), wherein the terminal is connected to the management system, The aforementioned management system is Multiple connection points for communicating with the aforementioned one or more IoT devices, Connection means for connecting IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point, Connection control means for causing the connection means to perform a connection with a specific IoT device, comprising connection control means for notifying the terminal of connection failure information indicating that the connection means failed to connect with the IoT device, and location information based on the connection point where the connection means last connected with the IoT device, in response to the connection means failing to connect with the IoT device, The aforementioned terminal is A request is provided to the connection control means to specify the IoT device to be connected to the connection means. A terminal control method that obtains notification of connection failure information and notification of location information from the connection control means. A control program that controls a computer that connects to a management system for managing one or more IoT devices (Internet of Things devices) and operates as a terminal for a user using the management system, The aforementioned management system is Multiple connection points for communicating with the aforementioned one or more IoT devices, Connection means for connecting IoT devices within the connection range of each of the plurality of connection points via the corresponding connection point, Connection control means for causing the connection means to perform a connection with a specific IoT device, comprising connection control means for notifying the computer of connection failure information indicating that the connection means failed to connect with the IoT device, and location information based on the connection point where the connection means last connected with the IoT device, in response to the connection means failing to connect with the IoT device, The aforementioned control program, A provisioning process that provides the connection control means with a request to specify an IoT device to be connected to the connection means, A control program that causes the computer to perform an acquisition process to acquire notification of connection failure information and notification of location information from the connection control means.

Images