IoT DEVICE, IoT SYSTEM, AND METHOD FOR CONTROLLING IoT DEVICE

Abstract

This IoT device is connected to a communication network and comprises: a communication unit (11) for communicating with another IoT device different from the subject IoT device; and a control unit (15) for controlling the communication unit (11). When a predetermined procedure is yet to be completed, the control unit (15) causes transmission of a beacon (Bc), requesting the predetermined procedure, via the communication unit (11). When the predetermined procedure is already completed, the control unit (15) does not cause transmission of the beacon (Bc).

Description

IoT device, IoT system, and method for controlling IoT device

[0001] The present disclosure relates to an Internet of Things (IoT) device, an IoT system, and a method for controlling an IoT device.

[0002] 2. Description of the Related Art Conventionally, IoT devices connected to a communication network have been known. Patent Literature 1 discloses a system that supports connecting smart home appliances, which are an example of IoT devices, to a communication network.

[0003] Japanese Patent Application Laid-Open No. 2021-77035

[0004] Conventional systems may not be able to fully utilize the convenient functions that utilize communication networks.

[0005] The present disclosure provides IoT devices and the like that can enable convenient functions that utilize a communication network.

[0006] An IoT device according to one aspect of the present disclosure is an IoT device connected to a communication network, and includes a communication unit for communicating with other IoT devices different from the IoT device, and a control unit for controlling the communication unit, wherein the control unit transmits a beacon via the communication unit requesting a specified procedure if the specified procedure has not been completed, and does not transmit the beacon if the specified procedure has been completed.

[0007] An IoT system according to one aspect of the present disclosure includes a first IoT device that is the above-mentioned IoT device, a second IoT device that is the other IoT device, and a server device that communicates with the first IoT device and the second IoT device via the communication network.

[0008] A control method for an IoT device according to one aspect of the present disclosure is a method for controlling an IoT device connected to a communication network, and includes a step of determining whether a specified procedure has been completed, and a step of transmitting a beacon requesting the specified procedure if the specified procedure has not been completed.

[0009] According to the IoT device etc. of the present disclosure, it is possible to use convenient functions that utilize a communication network.

[0010] FIG. 1 is a schematic diagram showing an IoT system according to an embodiment, as well as a first IoT device, a second IoT device, and a server device included in the IoT system. FIG. 2 is a block diagram of the IoT system. FIG. 3 is a diagram showing an example of log information of the first IoT device. FIG. 4 is a sequence diagram showing initial operations of the first IoT device and the second IoT device. FIG. 5 is a sequence diagram showing operations executed by the first IoT device, the second IoT device, and the server device to proceed with a predetermined procedure. FIG. 6 is a diagram showing an example of a screen displayed on the second IoT device. FIG. 7 is a diagram showing license information stored in the server device. FIG. 8 is a flowchart showing a method for controlling the first IoT device. FIG. 9 is a flowchart showing a method for controlling the second IoT device. FIG. 10 is a block diagram of an IoT system according to a modified example of the embodiment. FIG. 11 is a diagram showing an example of a screen displayed on the second IoT device according to the modified example of the embodiment.

[0011] (Background to the present disclosure) Conventionally, IoT devices connected to a communication network have been known. In addition, the Matter standard has been proposed as a communication standard for communication between IoT devices. The Matter standard is a standard for smart homes established by the Connectivity Standards Alliance (CSA). By using the Matter standard, multiple IoT devices from different manufacturers can be easily connected to each other for communication.

[0012] However, in communications using the Matter standard, it may not be possible to fully utilize convenient functions that utilize communication networks among the functions originally built into IoT devices.

[0013] For example, when an IoT device is connected to a communication network, a situation may arise in which the log information of the IoT device is read by an external computer and used. To prevent this situation from developing into a major problem, certain procedures, such as obtaining consent regarding the use of the log information, are carried out in advance. However, in communications using the Matter standard, these certain procedures may not be carried out smoothly. Furthermore, if these certain procedures are not carried out, the external computer will not be able to actively use the log information, and it will not be possible to provide useful information using the log information to users of the IoT device.

[0014] Therefore, the IoT device etc. of the present disclosure has the following configuration to enable convenient functions that utilize a communication network.

[0015] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. Note that each of the embodiments described below represents a preferred specific example of the present disclosure. The shapes, components, component placement positions, and connection configurations shown in the following embodiments are merely examples and are not intended to limit the present disclosure. Furthermore, among the components in the following embodiments, components that are not described in the independent claims that represent the highest concept of the present disclosure will be described as optional components that constitute a more preferred embodiment. Furthermore, each figure is a schematic diagram and is not necessarily an exact illustration.

[0016] (Embodiment) [Overall Configuration of IoT System] The overall configuration of an IoT system according to an embodiment will be described with reference to FIGS. 1 and 2. FIG.

[0017] Fig. 1 is a schematic diagram showing an IoT system 1 according to an embodiment, and a first IoT device 10, a second IoT device 20, and a server device 50 included in the IoT system 1. Fig. 2 is a block diagram of the IoT system 1.

[0018] 1 and 2 includes an IoT device, another IoT device different from the first IoT device, and a server device 50. Hereinafter, the IoT device will be referred to as a first IoT device 10, and the other IoT device will be referred to as a second IoT device. The first IoT device 10, the second IoT device 20, and the server device 50 are capable of communicating with each other via a communication network Nw.

[0019] The first IoT device 10 is an electrical device installed in a building such as a house, an apartment, or a facility. The first IoT device 10 may be installed inside or outside the building. For example, the first IoT device 10 is a device that does not have a display for displaying images, such as a washer / dryer, a refrigerator, an air conditioner, a lighting device, a television, a microwave, a rice cooker, a washlet, or a vacuum cleaner. Although FIG. 2 shows one first IoT device 10, the IoT system 1 may include multiple first IoT devices 10 as shown in FIG. 1. In this embodiment, the term "IoT device" simply refers to the first IoT device 10.

[0020] The second IoT device 20 is a device different from the first IoT device 10 and transmits and receives signals for controlling the first IoT device 10. The second IoT device 20 is an information terminal (or IoT device) portable by a user of the IoT system 1. For example, the second IoT device 20 is a device having a display (e.g., an active matrix display) 28 for displaying images, such as a smartphone, a tablet terminal, or a mobile computer. Note that the second IoT device 20 may also be a device having a display, such as a television, a refrigerator, or an intercom.

[0021] The second IoT device 20 has application software installed therein that enables two-way communication with the first IoT device 10. The second IoT device 20 reads a two-dimensional barcode or the like attached to an instruction manual or the like of the first IoT device 10, and accesses the read URL (Uniform Resource Locator) to download the application software. By installing the application software, the second IoT device 20 is configured to execute commands transmitted from the first IoT device 10.

[0022] The server device 50 is a host computer installed on the cloud. The server device 50 is an information processing device that communicates with the first IoT device 10, the second IoT device 20, etc., manages information for managing the first IoT device 10 and the second IoT device 20, and is configured to provide useful information to users under predetermined conditions. The server device 50 is, for example, a server on the cloud, and has functions of managing certificate information defined in a predetermined communication standard (e.g., the Matter standard), distributing the latest EULA (End User License Agreement) to IoT devices, and managing pairing information.

[0023] [Configurations and Operations of First IoT Device, Second IoT Device, and Server Device] The configurations and operations of the first IoT device 10, second IoT device 20, and server device 50 will be described with reference to FIGS. 2 to 7. FIG.

[0024] As shown in FIG. 2 , the first IoT device 10 according to this embodiment includes a communication unit 11 , an input unit 12 , a control unit 15 , and a storage unit 16 .

[0025] The communication unit 11 is a communication module that performs wired or wireless communication. The communication unit 11 can communicate with the second IoT device 20 and the server device 50 via the communication network Nw. The communication unit 11 can also perform direct wireless communication with the second IoT device 20 via wireless r1. For wireless communication between the first IoT device 10 and the second IoT device 20, a communication method such as BLE (Bluetooth Low Energy (registered trademark)) is used. Note that, for wireless communication, a communication method such as Zigbee (registered trademark) or Wi-Fi (registered trademark) may also be used.

[0026] The input unit 12 is a switch or the like that performs input for operating the first IoT device 10. The input unit 12 has, for example, a power switch for turning on the power of the first IoT device 10 and an operation switch for causing the first IoT device 10 to perform a predetermined operation.

[0027] The control unit 15 is a processor that executes a program that describes the operation of the first IoT device 10. The control unit 15 controls the operations of the input unit 12, the communication unit 11, and the storage unit 16. The control content of the control unit 15 will be described later.

[0028] The storage unit 16 is a storage medium for temporarily or non-temporarily storing data. The storage medium is, for example, a flash memory, a RAM (Random Access Memory), a hard disk, or the like. The storage unit 16 stores a program describing the operation of the first IoT device 10. The storage unit 16 also stores an ID (Identification) that is identification information of the first IoT device 10. The ID may be a device ID assigned by the manufacturer of the first IoT device 10, a communication address, or a MAC (Media Access Control) address.

[0029] Data is written to and read from storage unit 16 by control unit 15. For example, log information of first IoT device 10 is stored in storage unit 16. The log information is information relating to the usage history of the device, and includes an operation log, an authentication log, an access log, an event log, a system log, and the like.

[0030] The second IoT device 20 includes a communication unit 21, an input unit 22, a control unit 25, a storage unit 26, and a display 28. The storage unit 26 stores identification information of the second IoT device 20 and a pre-set communication ID. The communication ID is, for example, an SSID (Service Set Identifier) ​​and a password of a home network connected to the Internet. The second IoT device 20 connects to the home network using this communication ID, and is able to communicate with the server device 50.

[0031] The server device 50 includes a control unit 55 and a storage unit 56. The storage unit 56 stores, as license information Li, certificate information defined by a predetermined communication standard (for example, the Matter standard) and the latest EULA (End User License Agreement) for utilizing the first IoT device 10, and also stores pairing information indicating which user (identified by a user ID) is using the pair of the first IoT device 10 and the second IoT device.

[0032] FIG. 3 is a diagram showing an example of the log information Lg of the first IoT device 10.

[0033] 3 shows log information Lg when the first IoT device 10 is a washer / dryer. The figure shows, as the log information Lg of the first IoT device 10, information such as the ID of the user paired with and operating the first IoT device 10, the device ID identifying the first IoT device 10, the date and time of the event, and the event content. The event content includes information regarding the loading, washing, drying, and unloading of clothes, the weight of the clothes, the type of detergent, and operational errors. For example, by analyzing the log information Lg, it is possible to provide the user with convenient ways to use the first IoT device 10.

[0034] On the other hand, since the log information Lg is part of personal information, it must not be collected or analyzed without the user's permission. Therefore, before collecting or using the log information Lg of the first IoT device 10 for analysis, etc., it is necessary to go through a predetermined procedure, such as obtaining consent regarding the use of the log information Lg of the first IoT device 10. Specifically, the predetermined procedure is a procedure for obtaining consent to a software license agreement for the first IoT device 10, i.e., consent to an EULA (End User License Agreement).

[0035] In order to obtain consent for the above-mentioned predetermined procedure, in this embodiment, an initial operation is performed between the first IoT device 10 and the second IoT device 20, and then the predetermined procedure is carried out.

[0036] First, an initial operation performed between the first IoT device 10 and the second IoT device 20 will be described.

[0037] When the first IoT device 10 is purchased and used for the first time, the first IoT device 10 cannot communicate with the server device 50. Therefore, as an initial operation, the first IoT device 10 performs pairing with the second IoT device 20, permits operation from the second IoT device 20, and acquires a communication ID required to communicate with the server device 50.

[0038] FIG. 4 is a sequence diagram showing the initial operations of the first IoT device 10 and the second IoT device 20. As shown in FIG.

[0039] 4, the control unit 15 of the first IoT device 10 transmits a beacon Bc to the outside via the communication unit 11 (step S10). For example, the control unit 15 causes the communication unit 11 to transmit the beacon Bc using a communication method such as BLE. The control unit 15 causes the first IoT device 10 to transmit the beacon Bc when the first IoT device 10 is powered on. The power may be turned on by turning on a power switch or by connecting a power plug to a power outlet.

[0040] This beacon Bc is a signal for pairing with the second IoT device 20. However, the beacon Bc is transmitted around the first IoT device 10 without specifying a target device to receive the signal. The beacon Bc includes identification information of the first IoT device 10, and also includes a pairing request signal s1 that requests the return of identification information of the second IoT device 20. The pairing between the first IoT device 10 and the second IoT device 20 is, for example, pairing based on the Matter standard.

[0041] The control unit 25 of the second IoT device 20 receives the beacon Bc transmitted from the first IoT device 10 via the communication unit 21. The control unit 25 stores the identification information of the first IoT device 10 included in the beacon Bc in the storage unit 26.

[0042] Furthermore, the control unit 25 outputs a reply signal s2 via the communication unit 21 based on the pairing request signal s1 included in the beacon Bc (step S20). The reply signal s2 includes identification information of the second IoT device 20 and a communication ID required for communicating with the server device 50.

[0043] The control unit 15 of the first IoT device 10 receives the reply signal s2 output from the second IoT device 20 via the communication unit 11. The first IoT device 10 acquires the identification information of the second IoT device 20 contained in the reply signal s2, thereby achieving pairing with the second IoT device 20. That is, the first IoT device 10 and the second IoT device 20 are paired by each having the other's identification information (step S30).

[0044] The first IoT device 10 also acquires the communication ID contained in the reply signal s2 and establishes a communication path to the server device 50 (step S40). This enables the first IoT device 10 to communicate with the server device 50 via the communication network Nw, and to confirm with the server device 50 whether or not a predetermined procedure has been completed.

[0045] Next, the operations executed to proceed with a predetermined procedure will be described.

[0046] FIG. 5 is a sequence diagram showing operations executed by the first IoT device 10, the second IoT device 20, and the server device 50 to proceed with a predetermined procedure.

[0047] The control unit 15 of the first IoT device 10 outputs a first confirmation signal s3 at a predetermined timing to confirm whether or not the predetermined procedure has been completed (step S110). The control unit 15 outputs the first confirmation signal s3 to the server device 50 via the communication unit 11 and the communication network Nw. The predetermined timing is, for example, when the first IoT device 10 is powered on, or at a regular interval (e.g., once every 30 minutes) starting from the time the first IoT device 10 is powered on. In this case, whether or not the predetermined procedure has been completed refers to whether or not EULA consent has been obtained for the first IoT device 10. Note that the first confirmation signal s3 includes identification information for the first IoT device 10.

[0048] When the control unit 55 of the server device 50 receives the first confirmation signal s3, it reads information about whether the predetermined procedure has been completed, stored in the storage unit 56, and transmits information indicating whether the predetermined procedure has been completed (e.g., whether or not consent to the EULA) to the first IoT device 10 (step S120). Note that, if both new and old versions of the EULA exist, the server device 50 outputs information indicating whether or not consent to the new version of the EULA has been provided. In this way, the first IoT device 10 confirms with the server device 50 whether the predetermined procedure has been completed, and the server device 50 returns information indicating whether or not the predetermined procedure has been completed to the first IoT device 10.

[0049] The control unit 15 of the first IoT device 10 receives the information transmitted from the server device 50 and determines whether the predetermined procedure has been completed (step S130). If the predetermined procedure has not been completed (No in S130), the control unit 15 transmits a beacon Bc requesting the predetermined procedure via the communication unit 11 (step S140). In other words, if the predetermined procedure has not been completed, the first IoT device 10 enters a beacon transmission mode in which it is capable of transmitting a beacon Bc. In this beacon transmission mode, the first IoT device 10 transmits a beacon Bc multiple times (e.g., three times) within a specific period (e.g., nine minutes), with each transmission time being a specific transmission time (e.g., 30 seconds). Furthermore, the first IoT device 10 transmits a beacon Bc every predetermined time (e.g., 30 minutes), with each transmission of the multiple beacons Bc being considered as one set. The beacon Bc transmitted in S140 of FIG. 5 and the pairing request signal s1 transmitted in S10 of FIG. 4 can be distinguished by specifying a message type in the data field of the beacon, for example.

[0050] On the other hand, if the predetermined procedure has been completed (Yes in S130), the control unit 15 does not transmit the beacon Bc because there is no need to perform the predetermined procedure. In other words, if the predetermined procedure has been completed, the first IoT device 10 enters a beacon stop mode in which the beacon Bc is not transmitted, and this sequence ends. Note that the sequence shown in FIG. 5 is executed again from step S110 when a predetermined timing arrives.

[0051] The following describes the operation that is performed when the predetermined procedure has not been completed and a beacon Bc is transmitted.

[0052] When the control unit 25 of the second IoT device 20 receives the beacon Bc transmitted from the first IoT device 10 via the communication unit 21, it transmits a second confirmation signal s4 to the server device 50 via the communication network Nw to confirm the current status of the predetermined procedure (step S150). The second IoT device 20 is pre-installed with application software required for EULA consent. The second IoT device shown in FIG. 5 does not necessarily have to be the same device as the first IoT device that performed the initial operation described in FIG. 4; it may be a different device with equivalent functions. The second IoT device 20 is configured to output the second confirmation signal s4 when it receives the beacon Bc transmitted from the first IoT device 10. For example, the second confirmation signal s4 includes a device ID for identifying the first IoT device 10 and a user ID of the user logged in to the second IoT device.

[0053] Upon receiving the second confirmation signal s4, the server device 50 returns current status information of the predetermined procedure to the second IoT device 20 via the communication network Nw (step S160). The current status information of the predetermined procedure includes information regarding whether or not the user has agreed to the EULA. In this embodiment, the current status information of the predetermined procedure includes information regarding whether or not the user has agreed to the latest version of the EULA. For example, the server device 50 manages whether or not the user has agreed to the EULA based on whether or not the user identified by the user ID has agreed to the latest version of the EULA of the first IoT device 10.

[0054] When the second IoT device 20 receives the current status information, it outputs a request signal s5 to the server device 50, requesting that the server device 50 submit a procedure document (electronic document) for performing a predetermined procedure (step S170). For example, the second IoT device 20 requests the server device 50 to send the latest version of the EULA.

[0055] When the server device 50 receives the request signal s5, it transmits a consent form (EULA) for carrying out a predetermined procedure to the second IoT device 20 via the communication network Nw (step S180). The consent form contains the contents of the latest version of the EULA.

[0056] The control unit 25 of the second IoT device 20 displays the consent form transmitted from the server device 50 on the display 28, which is a touch panel (step S190).

[0057] FIG. 6 is a diagram showing an example of a screen displayed on the second IoT device 20.

[0058] Figure 6 shows the procedure for requesting EULA consent for the first IoT device 10. Specifically, the procedure for requesting consent includes the user ID of the user who will use the first IoT device 10, the device ID of the first IoT device 10, an external view of the device, and the EULA.

[0059] The user inputs consent to the EULA based on the screen shown in Fig. 6. When the control unit 25 receives the input of consent to the EULA from the touch panel display 28 or the input unit 22 (step S200), the control unit 25 outputs a consent signal s6 to the server device 50 to indicate consent to the EULA (step S210). Specifically, the control unit 25 transmits the consent signal s6 to the server device 50 via the communication unit 21 and the communication network Nw. The consent signal s6 includes information such as the user ID of the user currently logged in to the second IoT device 20, the device ID of the first IoT device 10 to be consented to, and the version of the EULA that has been consented to.

[0060] When the server device 50 receives the consent signal s6, it generates information indicating that a predetermined procedure has been completed (for example, that the EULA has been consented to) (step S220) and stores the information in the storage unit 56. Note that when the EULA has been changed from an old version to a new version and consent to the new version has not been obtained, the server device 50 generates information indicating that the EULA has not been consented to and stores the information in the storage unit 56.

[0061] FIG. 7 is a diagram showing the license information Li stored in the server device 50. As shown in FIG.

[0062] The license information Li in the figure includes information about a user ID, a device ID, and an EULA.

[0063] For example, if the "User ID" and "Device ID" fields are blank, the server device 50 determines that the EULA has not been agreed to. Furthermore, if the "Agreed EULA" field is blank, the server device 50 determines that the EULA has not been agreed to. The license information Li also includes information regarding the "latest version of the EULA." If an older version of the EULA is registered, the latest version of the EULA has not been agreed to.

[0064] In other words, the server device 50 determines that the EULA has been agreed upon if the license information Li contains the device ID of the first IoT device 10, if there is an agreed-upon EULA, and if the version of the agreed-upon EULA is the latest version of the EULA.

[0065] In this way, the server device 50 updates the license information Li based on the information transmitted from the second IoT device 20 and stores the updated license information Li in the storage unit 16 .

[0066] The first IoT device 10 checks at a predetermined timing whether a predetermined procedure has been completed, and therefore similarly checks even after the updated license information Li is stored in the server device 50 as described above.

[0067] The first IoT device 10 outputs a first confirmation signal s3 at a predetermined timing to confirm whether the predetermined procedure has been completed (see step S110). The control unit 15 outputs the first confirmation signal s3 to the server device 50 via the communication unit 11 and the communication network Nw.

[0068] When the server device 50 receives the first confirmation signal s3, it reads information about whether the predetermined procedure has been completed, which is stored in the storage unit 56, and transmits information indicating whether the predetermined procedure has been completed (e.g., whether consent to the EULA has been obtained) to the first IoT device 10 (see step S120). Note that, when both new and old versions of the EULA exist, the server device 50 outputs information indicating whether consent to the new version of the EULA has been obtained.

[0069] The first IoT device 10 receives the information transmitted from the server device 50 and determines whether the predetermined procedure has been completed (see step S130). In this case, since the EULA consent was given in step S210 and the predetermined procedure has been completed, the first IoT device 10 stops transmitting the beacon Bc. In other words, the first IoT device 10 enters the beacon stop mode, and this sequence ends.

[0070] For example, if the EULA is updated to a new version, the first IoT device 10 determines that the predetermined procedure has not been completed when it executes the processes of steps S110 to S130 at a predetermined timing. In this case, the first IoT device 10 enters a beacon transmission mode and transmits a beacon Bc via the communication unit 11, requesting the predetermined procedure.

[0071] In this way, the first IoT device 10 transmits a beacon Bc at predetermined timings if the predetermined procedure has not been completed at the predetermined timing. The reason for transmitting a beacon Bc at predetermined timings is to provide multiple opportunities to perform the predetermined procedure. For example, if the first IoT device 10 is paired with another IoT device other than the second IoT device 20 according to the Matter standard, the first IoT device 10 may stop transmitting a beacon Bc. Therefore, the first IoT device 10 of the present embodiment enters a beacon transmission mode and continues to transmit a beacon Bc until the predetermined procedure is completed.

[0072] As described above, the control unit 15 transmits a beacon Bc when the first IoT device 10 is powered on and the predetermined procedure has not been completed. However, the control unit 15 is configured to transmit a beacon Bc only for a predetermined period from the start date of use of the first IoT device 10, rather than always transmitting a beacon Bc when the first IoT device 10 is powered on. From a security standpoint, the predetermined period is set to a period until the user becomes familiar with the first IoT device 10, for example, three months. Meanwhile, the control unit 15 resets and restarts the predetermined period when it receives a signal from the second IoT device 20 to access the first IoT device 10 via the communication unit 11. In other words, the predetermined period for continuing to transmit a beacon Bc is reset each time a control command from the second IoT device 20 is received.

[0073] Furthermore, the control unit 15 transmits a beacon Bc when the first IoT device 10 is powered on and a predetermined procedure has not been completed. However, the control unit 15 does not transmit a beacon Bc every time the first IoT device 10 is powered on, but rather does not transmit a beacon Bc until a certain period of time has elapsed since the beacon B was transmitted. The certain period of time is set to, for example, 24 hours from the viewpoint of reducing standby power consumption. The certain period of time may be expressed as a number of times per day, such as once per day.

[0074] The IoT device according to this embodiment is an IoT device (first IoT device 10) connected to a communication network, and includes a communication unit 11 for communicating with another IoT device (second IoT device 20) different from the IoT device itself, and a control unit 15 for controlling the communication unit 11. When a predetermined procedure has not been completed, the control unit 15 causes the communication unit 11 to transmit a beacon Bc requesting a predetermined procedure, and when the predetermined procedure has been completed, the control unit 15 does not cause the communication unit 11 to transmit the beacon Bc.

[0075] According to the IoT device (first IoT device 10) having the above configuration, a beacon Bc is transmitted when a predetermined procedure has not been completed. Therefore, it is possible to provide an opportunity for another IoT device (second IoT device 20) to which the beacon Bc is sent to perform the predetermined procedure as needed. As a result, it is possible to use convenient functions that utilize the communication network Nw after completing the predetermined procedure.

[0076] [Control Method of First IoT Device] A control method of the first IoT device 10 will be described with reference to FIG. 8 .

[0077] FIG. 8 is a flowchart showing a control method for the first IoT device 10.

[0078] In an initial state (e.g., a product shipping state), consent to the EULA has not been obtained for the first IoT device 10, and information indicating that consent to the EULA has been obtained is not recorded in the storage unit 16 of the first IoT device 10. Furthermore, since the first IoT device 10 is unused, the storage unit 16 does not record the date and time when the beacon Bc was transmitted for pairing with the second IoT device 20, and the countdown of the predetermined period for transmitting the beacon Bc has not been executed.

[0079] In this state, when the first IoT device 10 is powered on (step S310), it performs an initial operation. First, the first IoT device 10 determines whether or not it is time to transmit a beacon Bc now that the power has been turned on (step S320). For example, the first IoT device 10 determines whether or not it is time to transmit a beacon Bc by determining, based on the transmission record of the beacon Bc stored in the storage unit 16, whether or not a predetermined period has passed since the first transmission of the beacon Bc, whether or not the beacon Bc has already been transmitted today, and so on.

[0080] If it is not now the timing to transmit a beacon Bc (No in S320), the first IoT device 10 performs the processes from step S350 onwards.

[0081] On the other hand, if it is now time to transmit a beacon Bc (Yes in S320), the first IoT device 10 transmits the beacon Bc via the communication unit 11 (step S330). For example, if three months have not passed since the first IoT device 10 first transmitted a beacon Bc and if the first IoT device 10 has not yet transmitted a beacon Bc today, the first IoT device 10 determines that it is now time to transmit a beacon Bc. The first IoT device 10 transmits the beacon Bc using a communication method such as BLE. The beacon Bc includes identification information of the first IoT device 10 and a pairing request signal s1 for pairing with the second IoT device 20.

[0082] The first IoT device 10 also stores information relating to the transmission date and time of the beacon Bc in the storage unit 16 (step S340). Step S340 may be executed simultaneously with step S330.

[0083] Next, the first IoT device 10 determines whether or not a reply signal s2 has been received from the second IoT device 20 (step S350). The reply signal s2 is a signal transmitted from the second IoT device 20 to the first IoT device 10 when the second IoT device 20 agrees to pairing with the first IoT device 10.

[0084] If the reply signal s2 has not been received (No in S350), the process proceeds to step S370. Note that the case where the reply signal s2 has not been received also includes the case where the first IoT device 10 never transmitted the beacon Bc in the first place.

[0085] On the other hand, when the reply signal s2 is received (Yes in S350), the first IoT device 10 performs a pairing process with the second IoT device 20 and stores information indicating that pairing has been established in the storage unit 16 (step S360). The first IoT device 10 also stores information indicating that the beacon Bc was transmitted today in the storage unit 16. This completes the initial operation of the first IoT device 10.

[0086] Next, the first IoT device 10 determines whether the predetermined procedure has been completed (step S370). Whether the predetermined procedure has been completed is determined, for example, based on whether the EULA has been agreed to. Whether the predetermined procedure has been completed is confirmed based on a first confirmation signal s3 sent from the first IoT device 10 to the server device 50.

[0087] If the predetermined procedure has been completed (Yes in S370), the first IoT device 10 returns to step S320 and determines whether or not it is now the time to transmit a beacon Bc. If the result in S370 is Yes, the predetermined procedure has been completed and there is no need to transmit a beacon Bc again, so in step S320 the first IoT device 10 determines that it is not now the time to transmit a beacon Bc. In this case, unless the EULA version is updated, for example, the processing in this flow essentially ends.

[0088] On the other hand, if the predetermined procedure has not been completed (No in S370), the first IoT device 10 resets and restarts the predetermined period for transmitting the beacon Bc (step S380). The restarted predetermined period is set to, for example, three months. After restarting the predetermined period, the first IoT device 10 returns to step S320 and executes the processes from step S320 onward. By restarting the predetermined period, the period for completing the predetermined procedure can be extended.

[0089] The control method for an IoT device according to this embodiment is a method for controlling an IoT device (first IoT device 10) connected to a communication network, and includes a step of determining whether a specified procedure has been completed, and a step of transmitting a beacon Bc requesting the specified procedure if the specified procedure has not been completed.

[0090] According to the above-described control method for IoT devices, a beacon Bc is transmitted when a predetermined procedure has not been completed. Therefore, for example, an opportunity to perform the predetermined procedure on another IoT device (second IoT device 20) different from the IoT device (first IoT device 10) can be provided as needed. This allows convenient functions using the communication network Nw to be used after the predetermined procedure has been completed.

[0091] [Control Method of Second IoT Device] A control method of the second IoT device 20 will be described with reference to FIG.

[0092] FIG. 9 is a flowchart showing a control method for the second IoT device 20.

[0093] Before the start (for example, before the application software is installed), the user who can be identified by the user ID has not consented to the EULA regarding the first IoT device 10, and the memory unit 26 of the second IoT device 20 does not record information indicating that consent has been given to the EULA.

[0094] In this state, application software required for consenting to the EULA is installed in the second IoT device 20 (step S410). When the user logs in to the second IoT device 20 using the user ID, the second IoT device 20 records the user ID that identifies the user in the storage unit 26.

[0095] Next, the second IoT device 20 determines whether or not the second IoT device 20 has received the pairing beacon Bc from the first IoT device 10 (step S420).

[0096] If the beacon Bc has not been received (No in S420), the process returns to step S420 and waits until the beacon Bc is received.

[0097] On the other hand, when the beacon Bc is received (Yes in S420), the second IoT device 20 determines whether or not pairing with the first IoT device 10 has been completed (step S430). For example, the second IoT device 20 determines whether or not pairing has been completed based on whether or not the identification information of the first IoT device 10 included in the beacon Bc is stored in the storage unit 26.

[0098] If pairing has been established (Yes in S430), the process proceeds to step S480, which will be described later.

[0099] On the other hand, if pairing has not been completed (No in S430), the second IoT device 20 executes pairing processing and transmits a reply signal s2 to the first IoT device 10 (step S440). The second IoT device 20 transmits the reply signal s2 using a communication method such as BLE. The reply signal s2 includes identification information of the second IoT device 20. The second IoT device 20 also stores the execution result of the pairing processing in the storage unit 26. Information indicating that pairing has been completed is saved in the storage unit 26.

[0100] Next, the second IoT device 20 determines whether or not a beacon Bc for starting a predetermined procedure has been received from the first IoT device 10 (step S450).

[0101] If the beacon Bc has not been received (No in S450), the process returns to step S450 and waits until the beacon Bc is received.

[0102] When the beacon Bc is received (Yes in S450), the second IoT device 20 transmits a second confirmation signal s4 to the server device 50 to confirm the current status of the specified procedure. The server device 50 transmits current status information of the specified procedure to the second IoT device 20, and the second IoT device 20 requests the presentation of procedural documents (electronic documents) for performing the specified procedure based on the current status information of the specified procedure. The server device 50 transmits a consent form, which is the procedural document, to the second IoT device 20. The second IoT device 20 displays the consent form output from the server device 50 on the display 28. The consent form includes information regarding the EULA.

[0103] The second IoT device 20 determines whether consent input for a predetermined procedure (e.g., consent input for the latest version of UELA) has been received (step S460). If consent input has not yet been received (No in S460), the second IoT device 20 returns to step S460 and waits for input. If consent input has been received (Yes in S460), the second IoT device 20 outputs consent signal s6 (step S470) and returns to step S420.

[0104] The flow of step S480 is a processing flow when pairing with the first IoT device 10 has already been established.

[0105] In this step, the second IoT device 20 determines whether or not consent input for a predetermined procedure (e.g., consent input for the latest version of EULA) has been received (step S480). If consent input has been received (Yes in S480), the second IoT device 20 outputs consent signal s6 (step S500) and returns to step S420.

[0106] If consent input for the latest version of the EULA has not been received (No in S480), the second IoT device 20 acquires the latest version of the EULA from the server device 50 and displays it on the display 28. Then, the second IoT device 20 receives consent input for the latest version of the EULA (step S490) and outputs a consent signal s6 (step S500). After outputting the consent signal s6, the second IoT device 20 returns to step S420 and executes the processes from step S420 onwards.

[0107] The control of the second IoT device 20 is executed by the processing of steps S410 to S500.

[0108] The control method of the second IoT device 20 includes the steps of receiving a beacon Bc output from the first IoT device 10, accepting content related to a specified procedure output from an external device (e.g., a server device 50) after receiving the beacon Bc from the first IoT device 10 and displaying the content related to the specified procedure, and outputting a consent signal s6 indicating consent to the specified procedure by accepting input indicating agreement to the content related to the specified procedure.

[0109] According to the above-described control method for the second IoT device 20, information regarding the content of a predetermined procedure can be acquired by the second IoT device 20, and consent to the predetermined procedure can be given based on the information. As a result, after the predetermined procedure has been completed, convenient functions that utilize the communication network Nw can be used.

[0110] Although the above example shows a case where the number of first IoT devices 10 that transmits the beacon Bc is one, the present invention is not limited to this. For example, when the second IoT device 20 receives beacons Bc from multiple first IoT devices 10, the second IoT device 20 may operate to obtain EULA consent from the first first IoT device 10 and then obtain EULA consent from the second first IoT device 10. The EULA consent from the second first IoT device 10 may be obtained at the timing of performing the second round of the flow.

[0111] [Modification] The IoT system 1 according to a modification of the embodiment will be described below. In the modification, the second IoT device is an electrical device such as a smart home appliance.

[0112] FIG. 10 is a block diagram of an IoT system 1 according to a modified example of the embodiment.

[0113] 10 , the IoT system 1 of the modified example includes a first IoT device 10, a second IoT device 20A, and a server device 50. The first IoT device 10, the second IoT device 20A, and the server device 50 are capable of communicating with each other via a communication network Nw. The configurations of the first IoT device 10 and the server device 50 are the same as those in the embodiment, and therefore, description thereof will be omitted.

[0114] The second IoT device 20A is an electrical device installed in a building such as a house, an apartment, or a facility. The second IoT device 20A is installed inside the building. For example, the second IoT device 20A is a device that has a display 28 that displays images, such as a television, an intercom, or a refrigerator.

[0115] Application software that enables two-way communication via wired and wireless communication is installed on each of the first IoT device 10 and the second IoT device 20A. The second IoT device 20A is configured to execute commands transmitted from the first IoT device 10.

[0116] As shown in FIG. 10, the second IoT device 20A includes a communication unit 21, an input unit 22, a control unit 25, a storage unit 26, and a display 28.

[0117] The control unit 25 of the second IoT device 20A receives the beacon Bc transmitted from the first IoT device 10 via the communication unit 21. The control unit 25 stores the identification information of the first IoT device 10 included in the beacon Bc in the storage unit 26.

[0118] The control unit 25 of the second IoT device 20A receives the beacon Bc transmitted from the first IoT device 10 via the communication unit 21, and transmits a second confirmation signal s4 to the server device 50 via the communication network Nw to confirm the current status of the specified procedure (see S140 in Figure 5).

[0119] When the server device 50 receives the second confirmation signal s4, it returns the current status information of the predetermined procedure to the second IoT device 20A via the communication network Nw (see S150 in FIG. 5). The current status information of the predetermined procedure includes information on whether or not the user has agreed to the EULA. In this modification, the current status information of the predetermined procedure includes information on whether or not the user has agreed to the latest version of the EULA.

[0120] When the second IoT device 20A receives the current status information, it outputs a request signal s5 to the server device 50, requesting that an electronic document for carrying out a predetermined procedure be returned (see S160 in FIG. 5 ). For example, the second IoT device 20A requests the server device 50 to send the latest version of the EULA.

[0121] Upon receiving the request signal s5, the server device 50 transmits a consent form for carrying out a predetermined procedure to the second IoT device 20A via the communication network Nw (see S170 in FIG. 5 ). The consent form contains the contents of the latest version of the EULA.

[0122] Control unit 25 of second IoT device 20A displays the consent form transmitted from server device 50 on display 28, which is a touch panel (see S180 in FIG. 5).

[0123] FIG. 11 is a diagram showing an example of a screen displayed on the second IoT device 20A according to the modification of the embodiment.

[0124] 11 shows the procedure for requesting consent for an EULA for the first IoT device 10, and the procedure for requesting consent includes the user ID of the user who uses the first IoT device 10, the device ID, device name, device external view, and EULA of the first IoT device 10. The display 28 also displays the device name and device external view so that it can be seen that the EULA displayed on the screen is for the first IoT device 10 and not for the second IoT device 20A.

[0125] When the control unit 25 receives an input agreeing to the EULA via the display 28 or the input unit 22, the control unit 25 outputs a consent signal s6 to the server device 50 via the communication unit 21. The operation after outputting the consent signal s6 is the same as in the embodiment.

[0126] The IoT device according to the modified example of the embodiment is an IoT device (first IoT device 10) connected to a communication network, and includes a communication unit 11 for communicating with another IoT device (second IoT device 20A) different from the first IoT device, and a control unit 15 for controlling the communication unit 11. When a predetermined procedure has not been completed, the control unit 15 causes the communication unit 11 to transmit a beacon Bc requesting a predetermined procedure, and when the predetermined procedure has been completed, the control unit 15 does not cause the communication unit 11 to transmit the beacon Bc.

[0127] According to the IoT device (first IoT device 10) having the above configuration, a beacon Bc is transmitted when a predetermined procedure has not been completed. Therefore, it is possible to provide an opportunity for another IoT device (second IoT device 20A) to which the beacon Bc is sent to perform the predetermined procedure as needed. As a result, it is possible to use convenient functions that utilize the communication network Nw after completing the predetermined procedure.

[0128] (Summary) An example of an IoT device according to one aspect of the present disclosure will be described.

[0129] The IoT device of Example 1 is an IoT device connected to a communication network, and includes a communication unit 11 for communicating with another IoT device (second IoT device 20) different from the IoT device (first IoT device 10), and a control unit 15 that controls the communication unit 11. When a predetermined procedure has not been completed, the control unit 15 causes the communication unit 11 to transmit a beacon Bc requesting a predetermined procedure, and when the predetermined procedure has been completed, the control unit 15 does not cause the communication unit 11 to transmit the beacon Bc.

[0130] According to the IoT device (first IoT device 10) having the above configuration, a beacon Bc is transmitted when a predetermined procedure has not been completed. Therefore, it is possible to provide an opportunity for another IoT device (second IoT device 20) to which the beacon Bc is sent to perform the predetermined procedure as needed. As a result, it is possible to use convenient functions that utilize the communication network Nw after completing the predetermined procedure.

[0131] The IoT device of Example 2 is the IoT device described in Example 1, and the predetermined procedure may be a procedure for obtaining EULA consent for the IoT device (first IoT device 10).

[0132] According to this, the beacon Bc is transmitted until the procedure for obtaining EULA consent is accepted. Therefore, it is possible to provide an opportunity for another IoT device (second IoT device 20) to obtain EULA consent as appropriate. As a result, it is possible to use convenient functions that utilize the communication network Nw after obtaining EULA consent.

[0133] The IoT device of Example 3 is the IoT device described in Example 1, and the predetermined procedure may be a procedure for obtaining consent regarding the use of the log information Lg of the IoT device (first IoT device 10).

[0134] According to this, the beacon Bc is transmitted until the procedure for obtaining consent to use of the log information Lg is accepted. Therefore, it is possible to provide an opportunity for another IoT device (the second IoT device 20) to obtain consent to use of the log information Lg as needed. As a result, it is possible to use convenient functions that utilize the communication network Nw after obtaining consent to use of the log information Lg.

[0135] The IoT device of Example 4 is an IoT device described in any of Examples 1 to 3, and the control unit 15 may output a signal to the server device 50 connected via the communication network Nw at a predetermined timing to confirm whether a predetermined procedure has been completed.

[0136] In this way, by outputting a signal requesting a predetermined procedure via the communication unit 11, it is possible to request another IoT device (second IoT device 20) to perform the predetermined procedure. Therefore, it is possible to provide an opportunity for the other IoT device (second IoT device 20) to perform the predetermined procedure as needed. As a result, it is possible to use convenient functions that utilize the communication network Nw after completing the predetermined procedure.

[0137] The IoT device of Example 5 is the IoT device described in Example 4, and the specified timing may be when the IoT device (first IoT device 10) is powered on, or may be a timing at a fixed cycle starting from the time the IoT device is powered on.

[0138] This allows a signal to be output at an appropriate time to confirm whether a predetermined procedure has been completed, and a request to perform the predetermined procedure on another IoT device (the second IoT device 20) can be made. Therefore, an opportunity to perform the predetermined procedure on the other IoT device (the second IoT device 20) can be provided as needed. As a result, after the predetermined procedure has been completed, convenient functions using the communication network Nw can be used.

[0139] The IoT device of Example 6 is an IoT device described in any of Examples 1 to 4, and the control unit 15 may transmit a beacon Bc for a predetermined period from the start date of use of the IoT device and when predetermined procedures have not been completed.

[0140] This makes it possible to prevent the security of the IoT device (first IoT device 10) from being lowered more than necessary.

[0141] The IoT device of Example 7 is the IoT device described in Example 6, and the control unit 15 may reset and restart the specified period when it receives a signal to access the IoT device (first IoT device 10) from another IoT device (second IoT device 20) via the communication unit 11.

[0142] By restarting the predetermined period in this way, it is possible to extend the period during which a predetermined procedure is performed in another IoT device (second IoT device 20). As a result, after the predetermined procedure is completed, convenient functions that utilize the communication network Nw can be used.

[0143] The IoT device of Example 8 is the IoT device described in Example 4, and the control unit 15 may perform pairing with another IoT device (second IoT device 20) to acquire the communication ID when a network connection necessary for communicating with the server device 50 has not been established. The communication ID is, for example, an SSID and a password for connecting to a home network connected to the Internet.

[0144] This allows the server device 50 to check whether the predetermined procedure has been completed. Therefore, if the predetermined procedure has not been completed, a beacon Bc is transmitted, and an opportunity to perform the predetermined procedure in another IoT device (second IoT device 20) that is the destination of the beacon Bc is given as needed. This allows convenient functions that use the communication network Nw to be used after the predetermined procedure has been completed.

[0145] The IoT device of Example 9 is the IoT device according to any one of Examples 1 to 7, and the pairing may be based on the Matter standard.

[0146] According to the IoT device (first IoT device 10) having the above configuration, even when pairing based on the Matter standard is performed, it is possible to provide an opportunity to perform a predetermined procedure in another IoT device (second IoT device 20) as needed. This makes it possible to use convenient functions that utilize the communication network Nw after completing the predetermined procedure.

[0147] The IoT system 1 of Example 10 includes a first IoT device 10 which is the above-mentioned IoT device, a second IoT device 20 which is another IoT device, and a server device 50 which communicates with the first IoT device 10 and the second IoT device 20 via a communication network Nw.

[0148] According to this IoT system 1, after going through a predetermined procedure, convenient functions that utilize the communication network Nw can be used.

[0149] The IoT system 1 of Example 11 is the IoT system described in Example 10, and the second IoT device 20 is a device having a display 28 that displays images, and may display information regarding a specified procedure on the display 28.

[0150] In this way, by displaying information about the predetermined procedure on the display 28, it is possible to provide an opportunity to perform the predetermined procedure at the second IoT device 20 as needed. As a result, after completing the predetermined procedure, it is possible to use convenient functions that utilize the communication network Nw.

[0151] The IoT system 1 of Example 12 is the IoT system described in Example 10 or 11, in which the first IoT device 10 is an electrical device installed in a building, and the second IoT device 20 may be an information terminal that transmits and receives signals to control the electrical device.

[0152] According to this configuration, the first IoT device can be controlled using the second IoT device 20.

[0153] The control method for an IoT device in Example 13 is a method for controlling an IoT device connected to a communication network Nw, and includes a step of determining whether a specified procedure has been completed, and a step of transmitting a beacon Bc requesting the specified procedure if the specified procedure has not been completed.

[0154] According to the above-described control method for IoT devices, a beacon Bc is transmitted when a predetermined procedure has not been completed. Therefore, for example, an opportunity to perform the predetermined procedure on another IoT device (second IoT device 20) different from the IoT device (first IoT device 10) can be provided as needed. This allows convenient functions using the communication network Nw to be used after the predetermined procedure has been completed.

[0155] (Other Embodiments) Although the embodiments have been described above, the present disclosure is not limited to the above-described embodiments.

[0156] In the above embodiment, an example is shown in which a beacon Bc is transmitted when the agreed-upon EULA version is different from the latest version, but this is not limiting. For example, if sufficient agreement has been obtained regarding the use of log information Lg even with an older version of the EULA, there is no need to transmit a beacon Bc again.

[0157] In addition, this disclosure also includes forms obtained by making various modifications to the embodiments that a person skilled in the art would think of, and forms realized by arbitrarily combining the components and functions of each embodiment within the scope of the present disclosure.

[0158] 1 IoT system 10 First IoT device (IoT device) 11 Communication unit 12 Input unit 15 Control unit 16 Storage unit 20, 20A Second IoT device 21 Communication unit 22 Input unit 25 Control unit 26 Storage unit 28 Display 50 Server device 55 Control unit 56 Storage unit Bc Beacon Lg Log information Li License information Nw Communication network r1 Wireless s1 Pairing request signal s2 Reply signal s3 First confirmation signal s4 Second confirmation signal s5 Request signal s6 Agreement signal

Claims

1. An IoT (Internet of Things) device connected to a communication network, comprising: a communication unit for communicating with other IoT devices different from the IoT device; and a control unit for controlling the communication unit, wherein the control unit transmits a beacon via the communication unit to request a specified procedure if the specified procedure has not been completed, and does not transmit the beacon if the specified procedure has been completed.

2. The IoT device according to claim 1, wherein the predetermined procedure is a procedure for obtaining consent for an EULA (End User License Agreement) regarding the IoT device.

3. The IoT device according to claim 1, wherein the predetermined procedure is a procedure for obtaining consent regarding the use of log information of the IoT device.

4. The IoT device according to claim 1, wherein the control unit outputs a signal to a server device connected via the communication network at a predetermined timing to confirm whether the predetermined procedure has been completed.

5. The IoT device according to claim 4, wherein the predetermined timing is when the IoT device is powered on or at a fixed cycle starting from the time the IoT device is powered on.

6. An IoT device according to any one of claims 1 to 3, wherein the control unit transmits the beacon for a predetermined period from the start date of use of the IoT device and when the predetermined procedure has not been completed.

7. The IoT device according to claim 6, wherein the control unit resets and restarts the predetermined period when it receives a signal from the other IoT device to access the IoT device via the communication unit.

8. The IoT device according to claim 4, wherein, when the control unit does not possess a communication ID (Identification) required to communicate with the server device, the control unit pairs with the other IoT device to obtain the communication ID.

9. The IoT device according to claim 8, wherein the pairing is based on the Matter standard.

10. An IoT system comprising: a first IoT device that is an IoT device according to any one of claims 1 to 3; a second IoT device that is the other IoT device; and a server device that communicates with the first IoT device and the second IoT device via the communication network.

11. The IoT system according to claim 10, wherein the second IoT device is a device having a display for displaying images, and information relating to the specified procedure is displayed on the display.

12. The IoT system described in claim 10, wherein the first IoT device is an electrical device installed in a building, and the second IoT device is an information terminal that sends and receives signals to control the electrical device.

13. A method for controlling an IoT (Internet of Things) device connected to a communication network, comprising: a step of determining whether a predetermined procedure has been completed; and a step of transmitting a beacon requesting the predetermined procedure if the predetermined procedure has not been completed.

Images