WO2024247124A1 - 機器管理システム、機器管理装置、中継装置、機器管理方法およびプログラム - Google Patents

機器管理システム、機器管理装置、中継装置、機器管理方法およびプログラム Download PDF

Info

Publication number
WO2024247124A1
WO2024247124A1 PCT/JP2023/020152 JP2023020152W WO2024247124A1 WO 2024247124 A1 WO2024247124 A1 WO 2024247124A1 JP 2023020152 W JP2023020152 W JP 2023020152W WO 2024247124 A1 WO2024247124 A1 WO 2024247124A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
relay
identification information
relay device
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2023/020152
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
崇 荻野
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Mitsubishi Electric Corp
Original Assignee
Mitsubishi Electric Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Mitsubishi Electric Corp filed Critical Mitsubishi Electric Corp
Priority to PCT/JP2023/020152 priority Critical patent/WO2024247124A1/ja
Priority to JP2023561896A priority patent/JP7466797B1/ja
Publication of WO2024247124A1 publication Critical patent/WO2024247124A1/ja
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements

Definitions

  • a system has been proposed that includes a relay device that can be connected to multiple devices, and a device control device connected to the relay device (see, for example, Patent Document 1).
  • the relay device searches for devices connected to the relay device and transmits address information of the searched devices to the device control device, and the device control device manages the address information of the searched devices received from the relay device in association with the address information of the relay device.
  • the device control device transmits a control message to the relay device that includes address information of a device that controls one of the searched devices, and the relay device converts the control message received from the device control device into a control message addressed to one device using a specified method and transmits it to one device.
  • This disclosure has been made in consideration of the above-mentioned reasons, and aims to provide a device management system, a device management device, a relay device, a device management method, and a program that can prevent devices from being operated inappropriately.
  • FIG. 1 is a schematic configuration diagram of a device management system according to a first embodiment of the present disclosure.
  • FIG. 1 is a block diagram showing a hardware configuration of a device management system according to a first embodiment.
  • FIG. 1 is a block diagram showing a functional configuration of a device management system according to a first embodiment;
  • FIG. 1 is a diagram showing an example of information stored in a device information storage unit according to the first embodiment;
  • FIG. 1 is a diagram showing an example of information stored in a device information storage unit according to the first embodiment;
  • FIG. 1 is a sequence diagram showing the operation of the device management system according to the first embodiment;
  • FIG. 1 is a sequence diagram showing the operation of the device management system according to the first embodiment;
  • FIG. 1 is a sequence diagram showing the operation of the device management system according to the first embodiment;
  • FIG. 1 is a sequence diagram showing the operation of the device management system according to the first embodiment;
  • FIG. 1 is a sequence diagram showing the operation of the device management system according to
  • FIG. 1 is a sequence diagram showing the operation of the device management system according to the first embodiment; 1 is a flowchart showing an example of a flow of relay processing executed by a relay device according to a first embodiment. 1 is a flowchart showing an example of the flow of a device management process executed by a cloud server according to the first embodiment.
  • FIG. 1 is a schematic configuration diagram of a device management system according to a second embodiment of the present disclosure.
  • FIG. 11 is a block diagram showing a functional configuration of a device management system according to a second embodiment.
  • FIG. 13 is a diagram showing an example of information stored in a device information storage unit according to the second embodiment;
  • FIG. 11 is a sequence diagram showing the operation of the device management system according to the second embodiment.
  • FIG. 11 is a sequence diagram showing the operation of the device management system according to the second embodiment.
  • 11 is a flowchart showing an example of a flow of relay processing executed by a relay device according to a second embodiment.
  • FIG. 13 is a schematic configuration diagram of a device management system according to a third embodiment of the present disclosure.
  • FIG. 11 is a block diagram showing a functional configuration of a device management system according to a third embodiment.
  • FIG. 13 is a diagram showing an example of information stored in a communication quality storage unit according to the third embodiment;
  • FIG. 11 is a sequence diagram showing the operation of the device management system according to the third embodiment.
  • FIG. 11 is a sequence diagram showing the operation of the device management system according to the third embodiment.
  • FIG. 11 is a flowchart showing an example of a flow of relay processing executed by a relay device according to a third embodiment.
  • FIG. 11 is a block diagram showing a functional configuration of a device management system according to a modified example.
  • FIG. 13 is a diagram showing an example of information stored in a delay time history storage unit according to a modified example.
  • 11 is a flowchart showing an example of the flow of a device management process executed by a cloud server according to a modified example.
  • the first relay device When the first relay device acquires device search request information, it transmits device information request information to a device capable of communicating with the first relay device via the first network, requesting that the device transmit second device information including device identification information, thereby acquiring second device information transmitted from the device via the first network, generating first device information including device identification information contained in the acquired second device information and transmitting it to the device management device, and when it acquires relay device information request information transmitted from the terminal device, requesting that the first relay device transmit relay device information including the first relay device identification information, it transmits the relay device information to the terminal device.
  • the terminal device acquires the relay device information, it transmits the first relay device identification information and user identification information contained in the acquired relay device information to the device management device.
  • the input unit 405 is, for example, a transparent touchpad arranged on top of the display unit 404.
  • the local communication unit 407 is connected to the local networks NW21 and NW22, and transmits information transferred from the CPU 401 to the relay device 1 via the local networks NW21 and NW22, and transfers information received from the relay device 1 via the local networks NW21 and NW22 to the CPU 401.
  • the local communication unit 407 communicates with the relay device 1 based on a first communication protocol conforming to the ECHONET Lite standard, for example.
  • the wide area communication unit 406 is connected to the wide area network NW1, and transmits information transferred from the CPU 401 to the cloud server 2 via the wide area network NW1, and transfers information received from the cloud server 2 via the wide area network NW1 to the CPU 401.
  • the connected device information acquisition unit 413 generates connected device information request information that includes the relay device identification information notified by the relay device search unit 412 and requests the cloud server 2 to send connected device information.
  • the connected device information includes device identification information of the relay device 1 identified by the relay device identification information included in the connected device information request information and each of the devices 3 that can communicate via the local networks NW21 and NW22.
  • the connected device information acquisition unit 413 then transmits the generated connected device information request information to the cloud server 2, thereby acquiring the connected device information sent from the cloud server 2, and stores the device identification information included in the acquired connected device information in the connected device information storage unit 431.
  • the device registration request unit 411 accepts the operation to request an update of the device to be registered and generates connected device information update request information including relay device identification information.
  • the connected device information acquisition unit 413 then transmits the generated connected device information update request information to the cloud server 2.
  • the cloud server 2 identifies the relay device to be updated for the connected device information update from the relay device identification information included in the connected device information update request information, and transmits device search request information to the relay device. Note that, although an example in which the cloud server 2 manages the connected device information has been shown in this embodiment, a configuration in which the connected device information is managed by the relay device and the terminal device 4 acquires the connected device information from the relay device 1 may also be used.
  • the cloud server 2 comprises a CPU 201, a main memory unit 202, an auxiliary memory unit 203, a communication unit 206, and a bus 209 that connects the various units.
  • the CPU 201 is, for example, a multi-core processor.
  • the main memory unit 202 is made up of a volatile memory, and is used as a working area for the CPU 201.
  • the auxiliary memory unit 203 is made up of a large-capacity non-volatile memory, and stores programs for realizing various functions of the cloud server 2.
  • the communication unit 206 is connected to the wide area network NW1.
  • the CPU 201 loads the program stored in the auxiliary storage unit 203 into the main storage unit 202 and executes it, thereby functioning as a device search request unit 211, a device information acquisition unit 212, a connected device information notification unit 213, a device information setting unit 214, an operation information acquisition unit 216, an authentication unit 217, a control information generation unit 218, and a control information notification unit 219, as shown in FIG. 3.
  • the auxiliary storage unit 203 shown in FIG. 2 also has a device information storage unit 231, as shown in FIG. 3.
  • the device information storage unit 231 stores the device identification information of the device 3, the relay device identification information of the relay device 1 that can be notified via the device 3 and the local networks NW21 and NW22, the user identification information, and the authentication information, in association with each other, as shown in FIG. 4A, for example.
  • the device information storage unit 231 may store only the user identification information. In this case, an authentication information storage unit (not shown) that stores the authentication information in association with the user identification information may be provided.
  • the device status storage unit 232 stores parameter information indicating at least one of the operating state of each device 3 and the surrounding environment of the device 3 in association with the device identification information of the device 3, as shown in FIG. 4B, for example.
  • the device search request unit 211 when the device search request unit 211 receives device registration request information transmitted from the terminal device 4, it generates device search request information that requests the relay device 1 to search for device 3 that can communicate with the relay device 1 via the local networks NW21 and NW22. The device search request unit 211 then transmits the generated device search request information to the relay device 1.
  • the device information acquisition unit 212 acquires device information transmitted from the relay device 1 by transmitting the device search request information to the relay device 1, extracts device identification information of device 3 and relay device identification information of relay device 1 that transmitted the device information, which are included in the acquired device information, and stores the extracted device identification information and relay device identification information in the device information storage unit 231 in association with each other.
  • the connected device information notification unit 213 acquires the aforementioned connected device information request information transmitted from the terminal device 4, it identifies, from the device identification information stored in the device information storage unit 231, device identification information corresponding to the relay device identification information included in the acquired connected device information request information. Then, the connected device information notification unit 213 generates connected device information including the identified device identification information and transmits it to the terminal device 4.
  • the device information setting unit 214 acquires the aforementioned registration target device notification information transmitted from the terminal device 4, it stores the user identification information and authentication information included in the acquired registration target device notification information in the device information storage unit 231 in association with a combination of the device identification information and relay device identification information included in the acquired registration target device notification information.
  • the authentication unit 217 refers to the user identification information and authentication information stored in the device information storage unit 231, and executes authentication processing based on the user identification information and authentication information included in the operation information.
  • the authentication unit 217 determines that the authentication is successful if the combination of the device identification information, user identification information, and authentication information of the device 3 to be operated, which is included in the operation information, exists among these combinations stored in the device information storage unit 231.
  • the authentication unit 217 determines that the authentication is unsuccessful if the combination of the device identification information, user identification information, and authentication information of the device 3 to be operated, which is included in the operation information, does not exist among these combinations stored in the device information storage unit 231. Then, when the authentication unit 217 determines that the authentication is successful, it notifies the control information generation unit 218 of the operation information.
  • the control information generating unit 218 generates control information for controlling the device 3 based on the operation content indicated by the notified operation information and the device identification information.
  • the relay device information notification unit 114 acquires the above-mentioned relay device information request information from the terminal device 4 via the local networks NW21 and NW22, it transmits relay device information including the relay device identification information stored in the relay device information storage unit 132 to the terminal device 4 in response to the acquisition.
  • the terminal device 4 accepts the device registration start operation and generates relay device information request information that requests the relay devices 1A and 1B with which the terminal device 4 can communicate via the local networks NW21 and NW22 to transmit relay device information (step S1).
  • the generated relay device information request information is transmitted from the terminal device 4 to the relay devices 1A and 1B (step S2).
  • the relay devices 1A and 1B acquire the relay device information request information, in response to this, the relay device information including the relay device identification information stored in the relay device information storage unit 132 is transmitted from the relay devices 1A and 1B to the terminal device 4 (step S3).
  • the terminal device 4 acquires the relay device information, it extracts the relay device identification information included in the acquired relay device information, and generates the above-mentioned device registration request information including the extracted relay device identification information (step S4). Next, the generated device registration request information is transmitted from the terminal device 4 to the cloud server 2 (step S5). Meanwhile, when the cloud server 2 acquires the device registration request information from the terminal device 4, it generates the above-mentioned device search request information in response to the device registration request information (step S6). Next, the generated device search request information is transmitted from the cloud server 2 to the relay devices 1A and 1B (step S7).
  • the relay devices 1A and 1B acquire the device information
  • the relay devices 1A and 1B store the device identification information of the devices 3A and 3B included in the acquired device information in the device information storage unit 131, and generate device information including the device identification information and the relay device identification information of the relay devices 1A and 1B (step S12).
  • the generated device information is transmitted from the relay devices 1A and 1B to the cloud server 2 (step S13).
  • the cloud server 2 acquires the device information, it extracts the device identification information and the relay device identification information included in the acquired device information, and stores the extracted device identification information and the relay device identification information in the device information storage unit 231 in association with each other (step S14).
  • the terminal device 4 also generates the above-mentioned connection device information request information including the relay device identification information (step S15).
  • the generated connection device information request information is then transmitted from the terminal device 4 to the cloud server 2 (step S16).
  • the cloud server 2 acquires the connection device information request information, it extracts the relay device identification information included in the acquired connection device information request information, and identifies the device identification information corresponding to the extracted relay device identification information from the device identification information stored in the device information storage unit 231.
  • the cloud server 2 generates connection device information including the identified device identification information (step S17).
  • the generated connection device information is transmitted from the cloud server 2 to the terminal device 4 (step S18).
  • the terminal device 4 acquires the connection device information, it uses the connection device identification information included in the acquired connection device information to form a connection device notification image and displays it on the display unit 404 (step S19).
  • the terminal device 4 accepts the registration device selection operation and generates registration target device notification information including the device identification information of the devices 3A and 3B selected by the registration device selection operation and the user identification information and authentication information stored in the user information storage unit 432 (step S20).
  • the generated registration target device notification information is transmitted from the terminal device 4 to the cloud server 2 (step S21).
  • the cloud server 2 acquires the registration target device notification information, it extracts the device identification information, user identification information, and authentication information included in the acquired registration target device notification information, and stores the extracted user identification information and authentication information in the device information storage unit 231 in association with the extracted device identification information (step S22).
  • the terminal device 4 accepts the device operation and generates operation information including information indicating the changed settings of the devices 3A and 3C, device identification information, user identification information, and authentication information (step S23), and the generated operation information is transmitted from the terminal device 4 to the cloud server 2 (step S24).
  • the cloud server 2 acquires the operation information, it executes an authentication process using the user identification information and authentication information included in the acquired operation information.
  • step S25 when the cloud server 2 determines that the authentication is successful (step S25), it generates control information for changing the settings of the devices 3A and 3C based on the operation information (step S26).
  • step S26 the generated control information is encapsulated and then transmitted from the cloud server 2 to the relay devices 1A and 1B (step S27).
  • the relay devices 1A and 1B acquire the control information, they decapsulate the acquired control information, and the decapsulated control information is transmitted from the relay devices 1A and 1B to the devices 3A and 3C (step S28).
  • the devices 3A and 3C acquire the control information, they start operating with the changed settings based on the acquired control information (step S29).
  • the devices 3A and 3C After that, when the aforementioned device status notification time arrives, as shown in FIG. 7, the devices 3A and 3C generate device status information (step S30), and the generated device status information is transmitted from the devices 3A and 3C to the relay devices 1A and 1B (step S31).
  • the relay devices 1A and 1B acquire the device status information, they perform encapsulation for transmitting the acquired device status information to the cloud server 2, and then the encapsulated device status information is transmitted from the relay devices 1A and 1B to the cloud server 2 (step S32).
  • the cloud server 2 acquires the device status information, it updates the parameter information of the devices 3A and 3C stored in the device status storage unit 232 using the parameter information and device identification information of the devices 3A and 3C included in the acquired device status information (step S33).
  • the devices 3B and 3D also generate device status information (step S34), and the generated device status information is transmitted from the devices 3B and 3D to the relay devices 1A and 1B (step S35).
  • the relay devices 1A and 1B acquire the device status information, they encapsulate the acquired device status information for transmission to the cloud server 2, and then transmit the encapsulated device status information from the relay devices 1A and 1B to the cloud server 2 (step S36).
  • the cloud server 2 determines that the authentication is successful (step S40), it generates device status notification information including the parameter information and device identification information of the devices 3A, 3C (3B, 3D) stored in the device status storage unit 232 based on the operation information (step S41). Then, the generated device status notification information is transmitted from the cloud server 2 to the terminal device 4 (step S42).
  • the terminal device 4 uses the parameter information and device identification information of the devices 3A and 3C (3B and 3D) contained in the acquired device status notification information to store the parameter information of the devices 3A and 3C (3B and 3D) in the device status storage unit 433, and forms a device status notification image based on the parameter information and device identification information stored in the device status storage unit 433 and displays it on the display unit 404 (step S43).
  • the search request acquisition unit 111 determines whether or not it has acquired device search request information transmitted from the cloud server 2 (step S101). If the search request acquisition unit 111 determines that it has not acquired device search request information (step S101: No), the process of step S105 described below is executed. On the other hand, if the search request acquisition unit 111 determines that it has acquired device search request information (step S101: Yes), it notifies the device search unit 112 of the acquired device search request information.
  • the device search unit 112 broadcasts the above-mentioned device information request information to all devices 3 connected to the local networks NW21 and NW22 to which the relay device 1 is connected (step S102). As a result, the device search unit 112 acquires the device information transmitted from each device 3, and stores the device identification information included in the acquired device information in the device information storage unit 131 (step S103). Next, the device information notification unit 113 generates device information including the device identification information stored in the device information storage unit 131, and transmits the generated device information to the cloud server 2 (step S104).
  • the device information acquisition unit 212 acquires the device information sent from the relay device 1, extracts the device identification information of the device 3 included in the acquired device information and the relay device identification information of the relay device 1 that sent the device information, and stores the extracted device identification information and relay device identification information in correspondence with each other in the device information storage unit 231 (step S203).
  • the device information setting unit 214 determines whether or not the above-mentioned registration target device notification information transmitted from the terminal device 4 has been acquired (step S206). If the device information setting unit 214 determines that the registration target device notification information has not been acquired (step S206: No), the process of step S208 described below is executed. On the other hand, if the device information setting unit 214 determines that the registration target device notification information has been acquired (step S206: Yes), it extracts the user identification information and authentication information included in the acquired registration target device notification information, and stores the extracted user identification information and authentication information in the device information storage unit 231 in association with the combination of the device identification information and relay device identification information included in the registration target device notification information (step S207).
  • the device status acquisition unit 226 determines whether or not it has acquired the encapsulated device status information transmitted from the relay device 1 (step S208). If the device status acquisition unit 226 determines that it has not acquired the device status information (step S208: No), the process of step S210 described below is executed. On the other hand, if the device status acquisition unit 226 determines that it has acquired the device status information (step S208: Yes), it updates the parameter information of the device 3 stored in the device status storage unit 232 and corresponding to the device identification information of the device 3 that transmitted the acquired device status information with the parameter information of the device 3 included in the device status information (step S209).
  • the operation information acquisition unit 216 judges whether or not it has acquired operation information indicating the above-mentioned device operation transmitted from the terminal device 4 (step S210).
  • the operation information acquisition unit 216 judges that it has not acquired operation information indicating device operation (step S210: No)
  • the process of step S213 described later is executed.
  • the operation information acquisition unit 216 judges that it has acquired operation information indicating device operation (step S210: Yes)
  • the authentication unit 217 refers to the user identification information and authentication information stored in the device information storage unit 231, executes authentication processing based on the user identification information and authentication information included in the operation information, and judges whether or not the authentication has been successful (step S211).
  • the device status notification unit 227 judges whether or not it has acquired operation information indicating the device status viewing operation transmitted from the terminal device 4 (step S213). If the device status notification unit 227 judges that it has not acquired operation information indicating the device status viewing operation (step S213: No), the process of step S201 is executed again. On the other hand, if the device status notification unit 227 judges that it has acquired operation information indicating the device status viewing operation (step S213: Yes), it notifies the authentication unit 217 of the acquired operation information. Then, the authentication unit 217 refers to the user identification information and authentication information stored in the device information storage unit 231, executes authentication processing based on the user identification information and authentication information included in the operation information, and judges whether or not the authentication has been successful (step S214).
  • the relay device information notification unit 114 of the relay device 1 acquires relay device information request information transmitted from the terminal device 4, it transmits the relay device information to the terminal device 4, and when the terminal device 4 acquires the relay device information, it transmits registration target device notification information including the relay device identification information and user identification information contained in the acquired relay device information to the cloud server 2. Then, when the device information setting unit 214 of the cloud server 2 acquires the registration target device notification information transmitted from the terminal device 4, it stores the user identification information and the relay device identification information contained in the acquired registration target device notification information in association with each other in the device information storage unit 231.
  • the device management system differs from the first embodiment in that it includes a second relay device capable of communicating with the device and the first relay device via the first network.
  • the device information storage unit stores, together with the device identification information, second relay device identification information for identifying the second relay device in association with the first relay device identification information.
  • the device management device transmits, to the first relay device, first device search request information requesting a search for a device and the second relay device capable of communicating with the first relay device via the first network, and transmits, via the first relay device, second device search request information requesting a search for a device capable of communicating with the second relay device via the first network, to the second relay device.
  • the second relay device acquires the fourth device information transmitted from the device via the first network by transmitting device information request information requesting transmission of fourth device information including device identification information to the device capable of communicating with the second relay device via the first network, and generates third device information including the device identification information included in the acquired fourth device information and transmits it to the device management device. Also, when the second relay device acquires relay device information request information transmitted from the terminal device requesting transmission of relay device information including the second relay device identification information to the second relay device, the second relay device transmits the relay device information to the terminal device.
  • the hardware configurations of the cloud server 2002 and the relay device 2005 are similar to those of the cloud server 2 and the relay device 1 described in the first embodiment, respectively. Therefore, the hardware configuration of the cloud server 2002 and relay device 2005 in this embodiment will be described using the symbols in FIG. 2 as appropriate.
  • the CPU 201 of the cloud server 2002 loads the program stored in the auxiliary memory unit 203 into the main memory unit 202 and executes it, so as to function as a device search request unit 211, a device information acquisition unit 212, a connected device information notification unit 213, a device information setting unit 214, an operation information acquisition unit 216, an authentication unit 217, a control information generation unit 218, a control information notification unit 219, a device status acquisition unit 226 and a device status notification unit 227, as shown in FIG. 11.
  • the auxiliary memory unit 203 also has a device information memory unit 2231 and a device status memory unit 232. As shown in FIG.
  • the device information storage unit 2231 stores the device identification information of device 3 and the relay device identification information "RADDR[1]" of relay device 2005 that can communicate with relay device 1 via local network NW2 in association with the relay device identification information of relay device 1 that can notify device 3 and relay device 2005 via local network NW2, user identification information, and authentication information.
  • auxiliary storage unit 103 shown in FIG. 2 has device information storage unit 131 and relay device information storage unit 132 as shown in FIG. 3.
  • relay device information notification unit 514 acquires the above-mentioned relay device information request information from terminal device 4 via local network NW2, it transmits relay device information including relay device identification information stored in relay device information storage unit 132 to terminal device 4 in response.
  • step S1 to step S7 a series of processes from step S1 to step S7 are executed, and when the relay device 1 acquires device search request information, the above-mentioned device information request information is broadcast from the relay device 1 to the devices 3A, 3B and the relay device 2005 that can communicate with them via the local network NW2 (steps S8, S2001).
  • step S10 device information including device identification information of the devices 3A and 3B is transmitted from the devices 3A and 3B to the relay device 1 (step S10).
  • step S2002 device information including the relay device identification information of the relay device 2005 is transmitted from the relay device 2005 to the relay device 1 (step S2002).
  • the relay device 1 acquires the device information, it stores the device identification information of the devices 3A and 3B or the relay device identification information of the relay device 2005 included in the acquired device information in the device information storage unit 131, and generates device information including the device identification information, the relay device identification information, and the relay device identification information of the relay device 1 (step S12). After that, a series of processes in steps S13 and S14 are executed.
  • the relay device 2005 when the relay device 2005 acquires the device information, the relay device 2005 stores the device identification information of the devices 3C and 3D included in the acquired device information in the device information storage unit 131, and generates device information including the device identification information and the relay device identification information of the relay device 2005 (step S2006). Thereafter, the generated device information is transmitted from the relay device 2005 to the cloud server 2002 via the relay device 1 (step S2007).
  • the cloud server 2002 acquires the device information, it extracts the device identification information and the relay device identification information included in the acquired device information, and stores the extracted device identification information and the relay device identification information in the device information storage unit 2231 in association with each other (step S2008).
  • step S25 when the cloud server 2002 determines that the authentication is successful (step S25), it generates control information for changing the settings of the devices 3C and 3D based on the operation information (step S2009). Next, the generated control information is encapsulated and then transmitted from the cloud server 2002 to the relay device 1 (step S2010). On the other hand, when the relay device 1 acquires the control information, the acquired control information is transmitted from the relay device 1 to the relay device 2005 (step S2011).
  • the relay device 2005 acquires the control information, it decapsulates the acquired control information, and the decapsulated control information is transmitted from the relay device 2005 to the devices 3C and 3D (step S2012).
  • devices 3C and 3D acquire the control information, they start operating with the changed settings based on the acquired control information (step S2013).
  • the relay device information notification unit 514 determines that it has acquired device information request information (step S2101: Yes)
  • it transmits device information including the relay device identification information stored in the relay device information storage unit 132 to the relay device 1 (step S2102).
  • a series of processes from step S105 to step S108 are executed.
  • the device status acquisition unit 121 determines whether or not the device status information transmitted from the device 3 has been acquired (step S2103). If the device status acquisition unit 121 determines that the device status information has not been acquired (step S2103: No), the process of step S101 is executed again. On the other hand, if the device status acquisition unit 121 determines that the device status information has been acquired (step S2103: Yes), it notifies the device status notification unit 522 of the acquired device status information. Then, the device status notification unit 522 transmits the notified device status information as is to the relay device 1 (step S2104). Next, the process of step S101 is executed again.
  • the device management system can associate each relay device 1, 2005 with user identification information even when multiple relay devices 1, 2005 form a so-called mesh network.
  • the device management system of this embodiment differs from embodiment 1 in that there are multiple first relay devices that can communicate with the device via the first network, and the device management device selects one of the multiple first relay devices based on communication quality information that indicates the communication quality of communication between the multiple first relay devices and the device.
  • the communication system includes a cloud server 3002, a plurality of relay devices 3001 (3001A, 3001B), and a terminal device 4.
  • the relay devices 3001 (3001A, 3001B) are capable of communicating with the devices 3 (3A, 3B) and the gateway device 8 via the local network NW2.
  • the cloud server 3002 is capable of communicating with the relay device 3001 via the wide area network NW1 and the gateway device 8.
  • the hardware configurations of the cloud server 3002 and the relay device 3001 according to the present embodiment are the same as those of the cloud server 2 and the relay device 1 described in the first embodiment.
  • the hardware configurations of the cloud server 3002 and the relay device 3001 according to the present embodiment will be described using the reference numerals in FIG. 2 as appropriate.
  • device 3 receives the control information transmitted from relay device 3001, device 3 transmits response information including device identification information of device 3 to relay device 3001, which is the source of the control information, notifying that the control information has been received.
  • the CPU 201 of the cloud server 3002 loads the program stored in the auxiliary storage unit 203 into the main storage unit 202 and executes it, so as to function as a device search request unit 3211, a device information acquisition unit 212, a connected device information notification unit 213, a device information setting unit 214, an operation information acquisition unit 216, an authentication unit 217, a control information generation unit 218, a control information notification unit 3219, a communication quality acquisition unit 3220, a relay device selection unit 3221, a response acquisition unit 3222, a connection status management unit 3223, a recovery monitoring unit 3224, a device status acquisition unit 226, and a device status notification unit 227, as shown in FIG. 17. Note that in FIG.
  • the auxiliary storage unit 203 also has a device information storage unit 231, a communication quality storage unit 3232, a connection status storage unit 3233, and a device status storage unit 232.
  • the communication quality storage unit 3232 stores communication quality information indicating the quality of communication between the device 3 and the gateway device 8 for each of the multiple relay devices 3001 in association with the relay device identification information of each of the multiple relay devices 3001.
  • the communication quality information may be, for example, information indicating the received signal strength indication (RSSI) of the wireless signal arriving from the device 3 and the gateway device 8 for each of the multiple relay devices 3001.
  • RSSI received signal strength indication
  • connection status storage unit 3233 stores connection status information indicating the connection status between the device 3 and the gateway device 8 for each of the multiple relay devices 3001 in association with the relay device identification information of each of the multiple relay devices 3001.
  • the device search request unit 3211 acquires device registration request information transmitted from the terminal device 4, the device search request unit 3211 generates device search request information that requests the relay device 3001 to search for devices 3 that can communicate with the relay device 3001 via the local network NW2. The device search request unit 3211 then transmits the generated device search request information to the relay device 3001 selected by the relay device selection unit 3221.
  • control information notification unit 3219 When the control information is notified from the control information generation unit 218, the control information notification unit 3219 notifies the relay device selection unit 3221 of the device identification information included in the notified control information. The control information notification unit 3219 then transmits the control information to the relay device 3001 selected by the relay device selection unit 3221.
  • the communication quality acquisition unit 3220 acquires communication quality information transmitted from each of the multiple relay devices 3001
  • the communication quality acquisition unit 3220 stores the acquired communication quality information in the communication quality storage unit 3232 in association with the relay device identification information of the relay device 3001 that is the source of the communication quality information added to the communication quality information.
  • the relay device selection unit 3221 selects one of the multiple relay devices 3001 based on the communication quality information stored in the communication quality storage unit 3232.
  • the relay device selection unit 3221 is notified of the device identification information included in the control information from the control information notification unit 3219, it identifies the relay device identification information corresponding to the notified device identification information from the relay device identification information stored in the device information storage unit 231.
  • the relay device selection unit 3221 selects, for example, the relay device 3001 with the largest RSSI indicated by the communication quality information from the multiple relay devices 3001 identified by the identified relay device identification information. Then, the relay device selection unit 3221 notifies the control information notification unit 3219 of the relay device identification information of the selected relay device 3001.
  • the relay device selection unit 3221 also refers to the connection state information stored in the connection state storage unit 3233, and excludes from the selection candidates the relay device 3001 identified by the relay device identification information corresponding to the connection state information indicating that communication is interrupted.
  • the response acquisition unit 3222 acquires the response information described below transmitted from the relay device 3001, it notifies the connection status management unit 3223 of the acquired response information. If the connection status management unit 3223 acquires the response information transmitted from the relay device 3001 within a preset response waiting time after the control information notification unit 3219 transmits the control information to the relay device 3001, it determines that communication is possible via the relay device 3001 between the cloud server 3002 and the device 3. Then, the connection status management unit 3223 stores the connection status information indicating that communication via the relay device 3001 is normal in the connection status storage unit 3233 in association with the relay device identification information of the relay device 3001.
  • connection status management unit 3223 determines that communication between the cloud server 3002 and the device 3 via the relay device 3001 has been interrupted.
  • the connection status management unit 3223 then stores connection status information indicating that communication via the relay device 3001 has been interrupted in the connection status storage unit 3233 in association with the relay device identification information of the relay device 3001.
  • the recovery monitoring unit 3224 periodically encapsulates response request information requesting the device 3 to transmit response information by adding header information for setting the relay device 3001, whose communication has been determined to be interrupted, as the destination, and transmits the encapsulated information to the relay device 3001.
  • the CPU 101 loads the program stored in the auxiliary memory unit 103 into the main memory unit 102 and executes it, thereby functioning as a search request acquisition unit 111, a device search unit 112, a device information notification unit 113, a relay device information notification unit 114, a control information acquisition unit 115, a control information transmission unit 116, a communication quality detection unit 3117, a communication quality notification unit 3118, a response acquisition unit 3119, and a response notification unit 3120.
  • the auxiliary memory unit 103 also has a device information storage unit 131 and a relay device information storage unit 132.
  • the communication quality detection unit 3117 detects the RSSI of a wireless signal arriving from the device 3 or the gateway device 8, generates communication quality information indicating the detected RSSI, and notifies the communication quality notification unit 3118.
  • the communication quality notification unit 3118 adds the relay device identification information of the relay device 3001 to the notified communication quality information, and then transmits it to the cloud server 3002.
  • the response acquisition unit 3119 acquires the response information transmitted from the device 3, it notifies the response notification unit 3120 of the acquired response information.
  • the response notification unit 3120 adds the relay device identification information of the relay device 3001 to the notified response information, performs an encapsulation process in which header information for setting the transmission destination to the cloud server 3002, and then transmits it to the cloud server 3002.
  • the cloud server 3002 acquires communication quality information transmitted from the relay devices 3001A and 3001B at a preset period, and stores the acquired communication quality information in the communication quality storage unit 3232 in sequence. Assume that the user performs a device operation on the input unit 405 of the terminal device 4 to change the settings of the device 3B when a communication failure occurs in the relay device 3001A.
  • the terminal device 4 accepts the device operation and generates the above-mentioned operation information (step S23), and the generated operation information is transmitted from the terminal device 4 to the cloud server 3002 (step S24).
  • the cloud server 3002 executes an authentication process using the user identification information and authentication information included in the acquired operation information and determines that the authentication is successful (step S25), it generates control information for changing the settings of the device 3B based on the operation information (step S26).
  • the cloud server 3002 selects one of the multiple relay devices 3001A and 3001B based on the communication quality information stored in the communication quality storage unit 3232 (step S3001).
  • the generated control information is encapsulated and then transmitted from the cloud server 3002 to the selected relay device 3001A (step S3002).
  • the cloud server 3002 determines that a preset response waiting time has elapsed without receiving response information transmitted from the relay device 3001A (step S3003).
  • the cloud server 3002 determines that communication between the cloud server 3002 and the devices 3A and 3B via the relay device 3001A has been interrupted, and updates the connection status information corresponding to the relay device identification information of the relay device 3001A to connection status information indicating that communication via the relay device 3001A has been interrupted (step S3004).
  • the cloud server 3002 again selects the relay device 3001B based on the updated connection state information stored in the connection state storage unit 3233 (step S3005).
  • the above-mentioned control information is then encapsulated and transmitted from the cloud server 3002 to the selected relay device 3001B (step S3006).
  • the relay device 3001B acquires the control information, it decapsulates the acquired control information, and the decapsulated control information is transmitted from the relay device 3001B to the device 3B (step S3007).
  • the device 3B acquires the control information, it starts operating with the changed settings based on the acquired control information (step S3008).
  • the device 3B when the device 3B acquires the control information, in response to this, the device 3B transmits response information to the relay device 3001B that transmitted the control information (step S3009).
  • the relay device 3001B acquires the response information, it encapsulates the acquired response information, and the encapsulated response information is transmitted from the relay device 3001B to the cloud server 3002 (step S3010).
  • the control information is transmitted from the cloud server 3002 to the relay device 3001B
  • the aforementioned response request information is periodically transmitted from the cloud server 3002 to the relay device 3001A (step S3011).
  • response request information is sent from cloud server 3002 to relay device 3001A (step S3012), and the response request information is decapsulated and then sent from cloud server 3002 to device 3B (step S3013).
  • device 3B acquires the response request information
  • response information is sent from device 3B to relay device 3001A in response thereto (step S3014).
  • relay device 3001A acquires the response information, it encapsulates the acquired response information, and the encapsulated response information is sent from relay device 3001A to cloud server 3002 (step S3015).
  • the cloud server 3002 when the cloud server 3002 receives the response information sent from the relay device 3001A, it determines that communication between the cloud server 3002 and the device 3B via the relay device 3001A has been restored, and updates the connection status information corresponding to the relay device identification information of the relay device 3001A to connection status information indicating that communication via the relay device 3001A is normal (step S3016).
  • the terminal device 4 accepts the device operation and generates the above-mentioned operation information (step S23), and the generated operation information is transmitted from the terminal device 4 to the cloud server 3002 (step S24).
  • the cloud server 3002 executes an authentication process using the user identification information and authentication information contained in the acquired operation information and determines that the authentication is successful (step S25), it generates control information based on the operation information (step S26).
  • the cloud server 3002 selects the relay device 3001A based on the communication quality information stored in the communication quality storage unit 3232 (step S3017).
  • the generated control information is encapsulated and then transmitted from the cloud server 3002 to the selected relay device 3001A (step S3018).
  • the relay device 3001A acquires the control information
  • the device 3B acquires the control information, it starts operating with the changed settings based on the acquired control information (step S3020).
  • the control information acquisition unit 115 determines whether or not it has acquired encapsulated control information or response request information transmitted from the cloud server 3002 (step S3101). Here, if the control information acquisition unit 115 determines that neither the control information nor the response request information has been acquired (step S3101: No), it executes the process of step S3103 described later.
  • control information acquisition unit 115 determines that it has acquired control information or response request information (step S3101: Yes)
  • the control information or response request information is sent to the device 3 identified by the device identification information (step S3102).
  • the response acquisition unit 3119 and the device status acquisition unit 121 respectively determine whether or not they have acquired the response information and device status information transmitted from the device 3 (step S3013). If the response acquisition unit 3119 and the device status acquisition unit 121 determine that they have not acquired the response information and device status information (step S3013: No), the process of step S101 is executed again. On the other hand, if the response acquisition unit 3119 and the device status acquisition unit 121 determine that they have acquired the response information and device status information (step S3013: Yes), they notify the response notification unit 3120 and the device status notification unit 122 of the acquired response information and device status information, respectively.
  • step S101 is executed again.
  • the device management process executed by the cloud server 3002 according to this embodiment will be described with reference to FIG. 22.
  • the same processes as those in the first embodiment are denoted by the same reference numerals as those in FIG. 9.
  • the communication quality acquisition unit 3220 acquires communication quality information periodically transmitted from the relay devices 3001A and 3001B in parallel with this device management process, and stores the acquired communication quality information in the communication quality storage unit 3232 in association with the relay device identification information of the relay device 3001 that is the sender of the communication quality information added to the communication quality information.
  • the device search request unit 211 determines whether or not it has acquired the above-mentioned device registration request information transmitted from the terminal device 4 (step S201).
  • step S3201 If it is determined that the device registration request information has been acquired (step S201: Yes), the device search request information is generated accordingly (step S3201).
  • the relay device selection unit 3221 selects one of the multiple relay devices 3001 based on the communication quality information stored in the communication quality storage unit 3232, and the device search request unit 3211 transmits the generated device search request information to the relay device 3001 selected by the relay device selection unit 3221 (step S3202). Then, a series of processes from steps S203 to S210 are executed.
  • the authentication unit 217 refers to the user identification information and authentication information stored in the device information storage unit 231, executes authentication processing based on the user identification information and authentication information included in the operation information, and determines that the authentication is successful (step S211: Yes).
  • the control information generation unit 218 generates control information for controlling the device 3 based on the operation content and device identification information indicated by the operation information (step S3203).
  • the relay device selection unit 3221 selects one of the multiple relay devices 3001 based on the communication quality information stored in the communication quality storage unit 3232.
  • the control information notification unit 3219 transmits the control information to the relay device 3001 selected by the relay device selection unit 3221 (step S3204).
  • the response acquisition unit 3222 determines whether or not it has acquired the response information transmitted from the relay device 3001 (step S3205). If the response acquisition unit 3222 determines that it has not acquired the response information (step S3205: No), it determines whether or not the response waiting time has elapsed (step S3206). If the response acquisition unit 3222 determines that the response waiting time information has not yet elapsed (step S3206: No), the process of step S3205 is executed again.
  • step S3206 determines that the response acquisition unit 3222 determines that the response waiting time information has elapsed.
  • the connection status management unit 3223 determines that the communication between the cloud server 3002 and the device 3 via the relay device 3001 has been interrupted, and updates the connection status information corresponding to the relay device identification information of the relay device 3001 stored in the connection status storage unit 3233 to connection status information indicating that the communication via the relay device 3001 has been interrupted (step S3207).
  • the recovery monitoring unit 3224 starts periodically sending response request information to the relay device 3001 for which communication has been determined to be cut off (step S3208). Then, the process of step S3203 is executed.
  • step S3205 determines in step S3205 that it has acquired response information (step S3205: Yes)
  • step S213 a series of processes from step S213 to S215 are executed.
  • step S3209 it is determined whether or not response information has been acquired from the relay device 3001 to which the response request information was sent by the recovery monitoring unit 3224.
  • step S3209 determines that response information has not been acquired from the relay device 3001 to which the response request information was sent.
  • step S3209: No the process of step S201 is executed again.
  • the response acquisition unit 3222 determines that response information has been acquired from the relay device 3001 to which the response request information was sent (step S3209: Yes).
  • the recovery monitoring unit 3224 determines that the state has been restored to a state in which communication between the cloud server 3002 and the device 3 is possible via the relay device 3001, and stops sending the response request information.
  • the connection status management unit 3223 updates the connection status information stored in the connection status storage unit 3233, which corresponds to the relay device identification information of the relay device 3001 to which the response request information is to be transmitted, to connection status information indicating that communication via the relay device 3001 is normal (step S3210). Next, the process of step S201 is executed again.
  • the device management system can maintain a relatively high level of quality of communication between the cloud server 3002 and the device 3 via the relay device 3001.
  • the cloud server 3002 also monitors whether communication with the device 3 via each of the multiple relay devices 3001 has been interrupted, and when it is determined that communication with the device 3 via the selected relay device 3001 has been interrupted, selects another relay device 3001. This allows the cloud server 3001 to maintain communication with the device 3 via one of the multiple relay devices 3001, thereby preventing a situation in which the device 3 cannot be operated or parameter information of the device 3 cannot be obtained due to a communication failure with the device 3.
  • the cloud server may calculate, for each relay device, a delay time from when it transmits device search request information to the relay device until it acquires device information transmitted from the relay device, and select a relay device based on the calculated delay time.
  • the device management system includes a cloud server 4002, a relay device 4001, and a terminal device 4, as shown in FIG. 23, for example.
  • a cloud server 4002 a relay device 4001, and a terminal device 4, as shown in FIG. 23, for example.
  • FIG. 23 the same components as those in the third embodiment are given the same reference numerals as those in FIG. 17.
  • the hardware configurations of the cloud server 4002 and the relay device 4001 are similar to the hardware configurations of the cloud server 2 and the relay device 1 described in the first embodiment, respectively. Therefore, the hardware configurations of the cloud server 4002 and the relay device 4001 according to this embodiment will be described using the reference numerals in FIG. 2 as appropriate.
  • the CPU 201 of the cloud server 4002 loads the programs stored in the auxiliary memory unit 203 into the main memory unit 202 and executes them, thereby functioning as a device search request unit 4211, a device information acquisition unit 4212, a connected device information notification unit 213, a device information setting unit 214, an operation information acquisition unit 216, an authentication unit 217, a control information generation unit 218, a control information notification unit 219, a relay device selection unit 4221, a response acquisition unit 3222, a connection status management unit 3223, a recovery monitoring unit 3224, a delay time calculation unit 4225, a device status acquisition unit 226, and a device status notification unit 227.
  • a device search request unit 4211 a device information acquisition unit 4212, a connected device information notification unit 213, a device information setting unit 214, an operation information acquisition unit 216, an authentication unit 217, a control information generation unit 218, a control information notification unit 219, a relay device selection unit 4221, a response acquisition unit 3222, a connection
  • the auxiliary memory unit 203 also has a device information storage unit 231, a connection status storage unit 3233, a delay time history storage unit 4234, and a device status storage unit 232.
  • the delay time history storage unit 4234 stores a history of delay time information indicating the above-mentioned delay time for each of the multiple relay devices 4001 in association with the relay device identification information of each of the multiple relay devices 4001.
  • the device discovery request unit 4211 transmits the device discovery request information to the relay device 4001
  • it notifies the delay time calculation unit 4225 of the relay device identification information of the relay device 4001 that is the destination of the device discovery request information.
  • the device information acquisition unit 4212 acquires the device information, it notifies the delay time calculation unit 4225 of the relay device identification information of the relay device 4001 that is the source of the device information.
  • the delay time calculation unit 4225 calculates the delay time for each relay device 4001 from when the device discovery request unit 4211 transmits device discovery request information to the relay device 4001 until when the device information acquisition unit 4212 acquires the device information transmitted from the relay device 4001.
  • the delay time calculation unit 4225 calculates the delay time from when the relay device identification information is notified from the device discovery request unit 4211 until when the same relay device identification information is notified from the device information acquisition unit 4212.
  • the delay time calculation unit 4225 stores delay time information indicating the calculated delay time in the delay time history storage unit 4234 in association with the relay device identification information that identifies the corresponding relay device 4001.
  • the relay device selection unit 4221 selects one of the multiple relay devices 4001 based on the delay time for each of the multiple relay devices 4001 stored in the delay time history storage unit 4234. Specifically, the relay device selection unit 4221 calculates the average delay time for each of the multiple relay devices 4001, and selects the relay device 4001 with the smallest average calculated delay time. Then, the relay device selection unit 4221 notifies the control information notification unit 3219 of relay device identification information that identifies the selected relay device 4001.
  • the CPU 101 loads the program stored in the auxiliary memory unit 103 into the main memory unit 102 and executes it, thereby functioning as a search request acquisition unit 111, a device search unit 112, a device information notification unit 113, a relay device information notification unit 114, a control information acquisition unit 115, a control information transmission unit 116, a response acquisition unit 3119, and a response notification unit 3120.
  • the auxiliary memory unit 103 also has a device information storage unit 131 and a relay device information storage unit 132.
  • the device search request unit 4211 determines whether the device registration request information transmitted from the terminal device 4 has been acquired (step S201). If it is determined that the device registration request information has been acquired (step S201: Yes), the device search request information is generated accordingly and transmitted to the relay device 4001 (step S202).
  • the device information acquisition unit 4212 acquires the device information transmitted from the relay device 4001, extracts the device identification information of the device 3 included in the acquired device information and the relay device identification information of the relay device 4001 that is the transmission source of the device information, and stores the extracted device identification information and the relay device identification information in the device information storage unit 231 in association with each other (step S203).
  • the delay time calculation unit 4225 calculates the above-mentioned delay time for each relay device 4001, and stores delay time information indicating the calculated delay time in the delay time history storage unit 4234 in association with relay device identification information that identifies the corresponding relay device 4001 (step S4201). Then, a series of processes from steps S204 to S210 are executed.
  • the authentication unit 217 refers to the user identification information and authentication information stored in the device information storage unit 231, executes authentication processing based on the user identification information and authentication information included in the operation information, and determines that the authentication is successful (step S211: Yes).
  • the control information generation unit 218 generates control information for controlling the device 3 based on the operation content and device identification information indicated by the operation information (step S3203).
  • the relay device selection unit 4221 selects one of the multiple relay devices 4001 based on the delay time for each of the multiple relay devices 4001 stored in the delay time history storage unit 4234.
  • the control information notification unit 3219 transmits the control information to the relay device 4001 selected by the relay device selection unit 4221 (step S4202).
  • a series of processes from steps S3205 to S3210 are executed.
  • This configuration can reduce the delay time of communication between the cloud server 4002 and device 3 via the relay device 4001, thereby improving the responsiveness of device 3.
  • the cloud server 2, 3002 may include a relay device communication availability storage unit (not shown) that stores communication availability information indicating whether the user can communicate with the device 3 via the relay device 1, 2005, 3001 in association with user identification information.
  • the communication availability information is determined based on, for example, the specifications of the relay device 1, 2005, 3001.
  • the device discovery request unit 211 may select the relay device 1, 2005, 3001 to which the device discovery request information is to be sent based on the communication availability information stored in the relay device communication availability storage unit, and transmit the device discovery request information only to the selected relay device 1, 2005, 3001.
  • the various functions of the relay devices 1, 2005, 3001, 4001 and cloud servers 2, 2002, 3002, 4002 may be realized by software, firmware, or a combination of software and firmware.
  • the software or firmware may be written as a program, and the program may be stored and distributed on a computer-readable recording medium such as a flexible disk, a CD-ROM (Compact Disc Read Only Memory), a DVD (Digital Versatile Disc), or an MO (Magneto-Optical Disc), and the program may be read and installed on a computer to configure a computer capable of realizing each of the above-mentioned functions.
  • a computer-readable recording medium such as a flexible disk, a CD-ROM (Compact Disc Read Only Memory), a DVD (Digital Versatile Disc), or an MO (Magneto-Optical Disc)
  • the program may be read and installed on a computer to configure a computer capable of realizing each of the above-mentioned functions.
  • OS Operating System
  • an application or by collaboration between an OS and an
  • each program can be superimposed on a carrier wave and distributed via a communications network.
  • the program can be posted on a bulletin board (BBS, Bulletin Board System) on the communications network and distributed via the network.
  • BBS Bulletin Board System
  • These programs can then be started and run under the control of the OS in the same way as other application programs, thereby enabling the above-mentioned processing to be performed.
  • This disclosure is suitable as a device management system that remotely controls devices from a cloud server via a relay device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
PCT/JP2023/020152 2023-05-30 2023-05-30 機器管理システム、機器管理装置、中継装置、機器管理方法およびプログラム Ceased WO2024247124A1 (ja)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/JP2023/020152 WO2024247124A1 (ja) 2023-05-30 2023-05-30 機器管理システム、機器管理装置、中継装置、機器管理方法およびプログラム
JP2023561896A JP7466797B1 (ja) 2023-05-30 2023-05-30 機器管理システム、機器管理装置、中継装置、機器管理方法およびプログラム

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2023/020152 WO2024247124A1 (ja) 2023-05-30 2023-05-30 機器管理システム、機器管理装置、中継装置、機器管理方法およびプログラム

Publications (1)

Publication Number Publication Date
WO2024247124A1 true WO2024247124A1 (ja) 2024-12-05

Family

ID=90622483

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2023/020152 Ceased WO2024247124A1 (ja) 2023-05-30 2023-05-30 機器管理システム、機器管理装置、中継装置、機器管理方法およびプログラム

Country Status (2)

Country Link
JP (1) JP7466797B1 (https=)
WO (1) WO2024247124A1 (https=)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119728203A (zh) * 2024-12-12 2025-03-28 北京天融信网络安全技术有限公司 设备接入方法、通信系统、电子设备、存储介质及程序产品

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022074727A1 (ja) * 2020-10-06 2022-04-14 三菱電機株式会社 制御システム、サーバ、制御装置、通信制御方法およびプログラム
WO2022091405A1 (ja) * 2020-11-02 2022-05-05 三菱電機株式会社 制御システム、制御装置、機器制御方法およびプログラム

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5435618B2 (ja) * 2009-03-02 2014-03-05 Necカシオモバイルコミュニケーションズ株式会社 携帯端末装置及びプログラム
JP7452397B2 (ja) * 2020-11-27 2024-03-19 株式会社デンソー 電子制御装置、時刻情報提供方法、時刻情報提供プログラム、及び電子制御システム

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022074727A1 (ja) * 2020-10-06 2022-04-14 三菱電機株式会社 制御システム、サーバ、制御装置、通信制御方法およびプログラム
WO2022091405A1 (ja) * 2020-11-02 2022-05-05 三菱電機株式会社 制御システム、制御装置、機器制御方法およびプログラム

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119728203A (zh) * 2024-12-12 2025-03-28 北京天融信网络安全技术有限公司 设备接入方法、通信系统、电子设备、存储介质及程序产品

Also Published As

Publication number Publication date
JPWO2024247124A1 (https=) 2024-12-05
JP7466797B1 (ja) 2024-04-12

Similar Documents

Publication Publication Date Title
US8788567B2 (en) Information processing apparatus, information processing system, information processing method, and program
JP4644940B2 (ja) 課金方法、並びにスクリプト変換システム及び方法
US7848311B2 (en) Communication apparatus
US20040024912A1 (en) Device-sharing system, device administration terminal, gateway terminal, device, terminal program and device program, and method for providing a device-sharing service
AU2007201980B2 (en) Information-processing system, method, and program for controlling provision of information or processing service
US6882840B2 (en) Communication system capable of reducing communication load
CN113727325B (zh) 会话处理方法及相关设备
JP2003067527A (ja) コンテンツアクセス管理装置及びそれに用いるコンテンツアクセス管理方法並びにそのプログラム
JP7466797B1 (ja) 機器管理システム、機器管理装置、中継装置、機器管理方法およびプログラム
KR20020029441A (ko) 분산 서버 시스템 및 이를 이용한 데이터 제공 방법
JPH11215174A (ja) ネットワーク接続装置
JP2000217169A (ja) 映像監視システム
JP2000330938A (ja) 情報処理端末
JPH11306069A (ja) 送信装置および送信方法、受信装置および受信方法、並びに送受信システムおよび送受信方法
US8456671B2 (en) Communication system, information storage device, management device, and terminal device
EP1232631B1 (en) Internet receiving arrangement having quality test means
US7606220B2 (en) Communication apparatus having an indicator that indicates a function service of a terminal apparatus
EP1473905B1 (en) Information management apparatus and method for facilitating the search of horizontal services
WO2003056440A1 (en) Method and apparatus for obtaining internet content for a wireless device
JP2013011969A (ja) 代理アクセスを許可するサーバ,そのプログラム,そのシステム及びその方法
KR101535808B1 (ko) 컨텐츠 서비스 시스템 및 방법
JP2022129170A (ja) 処理装置、名前解決サーバ、端末装置、方法およびプログラム
JP2005276058A (ja) ファームウェア更新システム、ファームウェア更新方法及び通信端末装置
JP4680172B2 (ja) サービス提供システムおよびサービス提供方法
US20250294246A1 (en) Camera control device, camera control method, and non-transitory computer readable storage medium

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2023561896

Country of ref document: JP

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23939602

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE