Remote management systems, routers, and remote management methods

Abstract

This invention provides a remote management system and method for establishing low-security communication sessions with network devices and performing remote management. [Solution] A remote management system 100 comprises a network device 20 connected to a private network 10, a router 30, and a remote management server 50 and an operation terminal 60 connected to the Internet 40. The network device randomly generates a UDP port number and an authentication key and sends them to the remote management server in advance. When the operation terminal requests an operation on the network device from the remote management server, the remote management server sends the authentication key to the network device. If the received authentication key matches the authentication key previously sent by the network device, a communication session is established between the network device and the remote management server, and the operation terminal performs remote management of the network device.

Description

Technical Field

[0001] The present invention relates to a remote management system and a remote management method for remotely managing network devices connected to a private network from the Internet.

Background Art

[0002] Regarding the remote management of network devices and the start of communication necessary for remote management, for example, the following inventions are disclosed.

[0003] Patent Document 1 (Japanese Unexamined Patent Application Publication No. 2023-61252) discloses an information processing system, an information processing device, a management server, and a program that enable log collection and investigation by remote maintenance operations of a device when a support request for the device is made. In the information processing system described in Patent Document 1, the target device constructs a communication session with the management server, receives a request from the management server that has constructed the communication session, responds to the request, and sends predetermined information. The disconnection processing unit of the management server or the target device discards the constructed communication session when a predetermined end condition is satisfied.

[0004] Also, Patent Document 2 (Japanese Unexamined Patent Application Publication No. 2023-52288) discloses a relay method that enables secure access to a target terminal for remote management. In the relay method described in Patent Document 2, when the connection management device of the relay system acquires terminal identification information for identifying the target terminal from the client terminal, it specifies a first relay device that relays communication, and specifies connection information for the client terminal to connect to the first relay device. The connection management device stores the specified connection information and the terminal identification information in association with each other in the storage unit, and notifies the client terminal of the specified connection information. When the specified first relay device receives an access based on the connection information from the client terminal, it relays communication between the client terminal and the target terminal based on the terminal identification information associated with the connection information.

[0005] Furthermore, Patent Document 3 (Japanese Unexamined Patent Publication No. 2020-160984) discloses a data collection device, such as an IoT device, that reduces security risks without compromising user convenience. The data acquisition device described in Patent Document 3 includes a command receiving unit that receives a port opening command specifying a port from a data utilization device via a wireless communication network, an authentication processing unit that performs authentication processing for the data utilization device that sent the port opening command, a command execution unit that executes the port opening command to open the port if the authentication of the data utilization device is successful, and a data communication unit that performs data communication using the port in response to a request from the data utilization device.

[0006] Furthermore, Patent Document 4 (International Publication No. 2016 / 207927) discloses a network connection technology for remotely controlling equipment located in a remote location via a network. The remote maintenance system described in Patent Document 4 comprises a maintenance management device connected to a user device and a communication relay device connected to a remotely controlled device. The maintenance management device transmits message data to the communication relay device, with a unique identifier of a mobile communication network pre-assigned to the communication relay device as the destination. In connection with receiving the message data, the communication relay device notifies the maintenance management device of an IP address dynamically assigned to it. The maintenance management device transmits information regarding remote operation received from the user device to the communication relay device, with the notified IP address as the destination, and the communication relay device relays the information regarding remote operation received from the maintenance management device to the remotely controlled device.

[0007] Patent Document 5 (Japanese Patent Publication No. 2013-201621) describes a port opening and closing control system that enables remote access from a user terminal to a port of an in-home gateway device using normal internet usage procedures, while avoiding the unnecessary opening of the port to the internet. In the port opening and closing control system described in Patent Document 5, the in-home gateway device closes its port to the internet. The command device has a DNS content server unit, and when a user terminal performs the normal internet usage procedure of specifying the hostname of the GW device, the terminal sends a name resolution request. Upon receiving this name resolution request, the command device replies with a DNS response with TTL=0 seconds, and also refers to a management table of the GW device's hostname and the address of the closed network to send a port opening request to the GW device via the closed network. The terminal accesses the port of the GW device using the global IP address obtained from the DNS response, and when this access is completed, the GW device closes that port.

[0008] Furthermore, Patent Document 6 (Japanese Patent Publication No. 2013-206260) discloses an authentication method that allows communication to be initiated by an external request using a method with lower security risks, for initiating communication necessary for remote management. The authentication method described in Patent Document 6 involves recording a predetermined authentication format in a relay device, the external request terminal dividing the authentication data in accordance with the authentication format into sizes that can be embedded as port numbers in packets such as TCP or UDP, and sending them sequentially to the device in the order in which they are embedded in the port number portion of a series of packets, and the communication-enabled device monitoring the consecutive patterns of port numbers of packets received by the firewall, referring to the recorded authentication format, and if it detects that the pattern conforms to the authentication format, it opens a port for access in the firewall or starts predetermined software to accept access. [Prior art documents] [Patent Documents]

[0009] [Patent Document 1] Japanese Patent Publication No. 2023-61252 [Patent Document 2] Japanese Patent Publication No. 2023-52288 [Patent Document 3] Japanese Patent Publication No. 2020-160984 [Patent Document 4] International Publication No. 2016 / 207927 [Patent Document 5] Japanese Patent Publication No. 2013-201621 [Patent Document 6] Japanese Patent Publication No. 2013-206260 [Overview of the project] [Problems that the invention aims to solve]

[0010] Network devices connected to a private network are typically configured to avoid external security risks. This configuration allows network devices to connect to servers on the internet, but prevents servers on the internet from connecting to the network devices. However, when a support department remotely manages network devices connected to a private network, it becomes necessary to connect to the network devices from a server on the internet. Numerous patent documents disclose methods for connecting to network devices connected to a private network from such internet servers.

[0011] In the information processing system described in Patent Document 1, when a support staff member instructs a user to perform a predetermined support request operation on the control panel of the target device (for example, by long-pressing a certain button), the target device establishes a communication session with the management server, and thereafter the management server can communicate with the target device. This method poses a low security risk because a communication session is not established unless the user performs a specific support request operation on the target device's control panel. However, requiring users who have called the support line to perform further operations can be a significant burden for users unfamiliar with network device operation.

[0012] Therefore, Patent Document 2-6 describes a method for establishing a communication session between a network device and an external management server without requiring the user to perform a support request operation. In Patent Document 2, when a connection management device notifies the relay device of relay information including the port number of the target terminal associated with the relay device, the relay device establishes a connection between the relay device and the target terminal based on terminal identification information different from the private address and the port number used when the target terminal communicates. Although this method is relatively simple, the port number is in the range of 0 to 65535, and security may be compromised if the port number is detected by a port scan or if the port number happens to match.

[0013] In contrast, Patent Document 3 describes a method in which a data utilization device sends a port opening command to a data collection device via a wireless communication network. If the authentication of the data utilization device that sent the port opening command is successful, the port is opened, thereby mitigating the security risks faced by the data collection device. However, in this case, the data-consuming device will require a wireless communication network in addition to a regular internet connection.

[0014] In the remote maintenance system described in Patent Document 4, the maintenance management device sends a connection request message to a communication relay device to which unique identification information of the mobile communication network has been pre-assigned, using the SMS function of the mobile communication network. Patent Document 4 further reduces security risks by receiving a dynamically different IP address from the communication relay device each time a connection request message is sent, and relaying information regarding remote operation to the communication relay device based on the received IP address. However, in this case as well, the maintenance management device will require a wireless communication network in addition to a regular internet connection.

[0015] In the port opening and closing control system of Patent Document 5, the in-home gateway device does not directly accept open requests from user terminals. Instead, the command device stores the address of the in-home gateway device's private network in association with the hostname of the DNS registration request. When it receives a name resolution request for the hostname from the internet, it sends a port open request to the address of the in-home gateway device's private network stored in association with the hostname, thereby opening the available ports for the in-home gateway device. In this case as well, in addition to the regular internet, a closed network is required between the command device and the in-home gateway device.

[0016] The authentication method described in Patent Document 6 involves recording a predetermined authentication format on an external request terminal attempting to access from an external network and on a communication-enabled device equipped with a firewall that accepts such access. The external request terminal divides the authentication data into sizes that can be embedded as port numbers in packets such as TCP or UDP, embeds them in the port number portion of a series of packets, and sends them sequentially to the communication-enabled device. The communication-enabled device then monitors the consecutive patterns of port numbers in the received packets to perform authentication. This method does not require a wireless communication network or a private network, and since it authenticates by monitoring consecutive patterns of port numbers in received packets, it can reduce security risks compared to authentication using IP addresses or port numbers, as described in Patent Document 2. However, in this case, the authentication data embedded in the port number must be sent sequentially, which may take time to complete the authentication process. Furthermore, on the internet, the order in which authentication data is received may differ from the order in which it is sent, which can sometimes prevent smooth authentication.

[0017] The main objective of the present invention is to provide a remote management system and a remote management method that establish a low-security-risk communication session with a network device and remotely manage the network device without requiring the user to perform any special support request operations. Another object of the present invention is to provide a remote management system and a remote management method that construct a communication session with low security risk without providing a communication path other than the Internet between the network device and perform remote management of the network device.

Means for Solving the Problems

[0018] (1) A remote management system according to one aspect includes a network device connected to a private network, a router that relays the private network and the Internet, and a remote management server and an operation terminal connected to the Internet. The network device randomly generates a UDP port number and an authentication key of the network device and transmits them to the remote management server in a secure path together with the device-specific information of the network device in advance. When the remote management server receives the UDP port number, the authentication key, and the device-specific information of the network device, it stores the received UDP port number, the authentication key, and the device-specific information of the network device. When the operation terminal requests an operation on the network device to the remote management server, the remote management server transmits the authentication key to the UDP port of the network device corresponding to the device-specific information of the network device. When the authentication key received at the UDP port matches the previously transmitted authentication key, the network device constructs a communication session between the network device corresponding to the device-specific information and the remote management server, and the operation terminal performs remote management of the network device via the remote management server and the communication session.

[0019] Normally, a router that relays a private network and the Internet allows communication from the private network side to the Internet, but does not allow communication from the Internet side to the private network, except for the case of a reply to the communication from the private network side to the Internet. Therefore, when establishing a secure communication session using TLS or similar technologies between a network device and a remote management server, it is necessary to establish a communication session from the network device to the remote management server. This requires some operation from the user of the network device. However, many users of network devices are unfamiliar with operating them, and performing the operation required to establish a communication session can be a significant burden for them.

[0020] In this case, to avoid burdening users, it might be possible to allow communication from the internet to the private network by sharing the source and / or destination IP addresses and port numbers. However, port numbers are at risk of being detected through methods such as port scanning, and this is not a sufficient measure to reduce security risks. On the other hand, it is also conceivable that instructions to allow communication from the internet to the private network be sent not from the regular internet, but via a wireless communication network or a closed network. However, in this case, a wireless communication network or a closed network would be required between the remote management server and the network device, which would increase costs.

[0021] In a single-phase remote management system, a network device randomly generates its UDP port number and authentication key, and shares them with the remote management server in advance via a secure channel, along with the network device's device-specific information. When a communication session needs to be established, the remote management server sends the authentication key to the previously shared UDP port of the network device. The network device authenticates the authentication key, thereby transmitting a request to establish a communication session from the remote management server on the internet to the network device, and the network device establishes a communication session between itself and the remote management server. In this case, not only must the port numbers match, but the authentication keys must also match, thus reducing the risk of incorrect communication session creation due to cyberattacks, etc. Furthermore, it is desirable that the authentication key consist of binary data of, for example, 256 bits or more.

[0022] (2) The remote management system according to the second invention is a remote management system that follows one aspect, in which, when a UDP packet is sent from the internet side to the UDP port of the network device, the network device may not make any response or transmission.

[0023] If a UDP packet is sent to a UDP port shared with a remote management server, and the network device responds or sends any data, the port scanner will know that the port is listening, potentially leading to unauthorized intrusion using denial-of-service (DoS) attacks. In the remote management system according to the second invention, the network device does not make any responses or transmissions so that it is not detected that the port in question is in listening mode even when a port scan is performed.

[0024] (3) The remote management system according to the third invention, in one aspect, is the remote management system according to the second invention, wherein the network device may be a wireless LAN access point or a NAS.

[0025] In this case, the remote management system can remotely manage a wireless LAN access point or NAS. Other network devices may also include network cameras, network game consoles, etc.

[0026] (4) The remote management system according to the fourth invention is, in one aspect, a remote management system according to the second invention, in which the network device may include the function of a router.

[0027] Network devices include, for example, wireless LAN routers that include router functionality, or standalone routers. In this case, the remote management system can remotely manage the router.

[0028] (5) The remote management system according to the fifth invention, in one aspect of the remote management system according to the fourth invention, may use TLS (Transport Layer Security) for secure routes and communication sessions.

[0029] TLS is a widely adopted security protocol used, for example, for communication between network devices and the AWS cloud (AWS IoT Core). Using TLS enables secure, bidirectional communication between network devices and remote management servers.

[0030] (6) The remote management system according to the sixth invention, in one aspect of the remote management system according to the fifth invention, may discard the established communication session when a predetermined termination condition is met.

[0031] Although the communication session established by this invention poses a low security risk, maintaining the communication session at all times still carries a security risk. Therefore, it is desirable to terminate the communication session when the remote management work on the network device is completed. In this case, the predetermined termination conditions include, for example, the completion of the necessary remote operations, or the elapsed time since the network device stopped responding.

[0032] (7) A router following other configurations is a router that relays between a private network and the internet. It randomly generates a UDP port number and authentication key on the internet side, sends the generated UDP port number, authentication key, and its own device-specific information to a remote management server via a secure path, receives the authentication key sent from the remote management server at the UDP port of the UDP port number, and if the received authentication key matches the transmitted authentication key, establishes a communication session with the remote management server and accepts remote control of the operating terminal via the communication session.

[0033] A router that follows other phases is an invention of a router that corresponds to a case where a network device of a remote management system that follows one phase includes the functionality of a router.

[0034] (8) A remote management method that follows other aspects is a remote management method that performs remote management in a remote management system comprising a network device connected to a private network, a router that relays between the private network and the internet, and a remote management server and an operating terminal connected to the internet, and includes a security information transmission step in which the network device randomly generates a UDP port number and an authentication key for the network device and sends them to the remote management server in advance via a secure path along with the device-specific information of the network device; a security information storage step in which, upon receiving the UDP port number, authentication key and device-specific information of the network device, the remote management server stores the received UDP port number, authentication key and device-specific information of the network device; a remote operation request step in which the operating terminal requests an operation on the network device from the remote management server, and the remote management server sends an authentication key to the UDP port of the network device corresponding to the device-specific information of the network device; a communication session construction step in which, if the authentication key received on the UDP port matches the authentication key previously sent by the network device, a communication session is established between the network device corresponding to the device-specific information and the remote management server; and a remote management execution step in which the operating terminal performs remote management of the network device via the remote management server and the communication session.

[0035] A remote management method that follows other phases is an invention of a remote management method that corresponds to a remote management system that follows one phase. [Brief explanation of the drawing]

[0036] [Figure 1] This is a schematic diagram showing the overall configuration of the remote management system. [Figure 2] This is a schematic block diagram showing the configuration of a router. [Figure 3] This is a schematic block diagram showing the configuration of the remote management server. [Figure 4] This is a schematic block diagram showing the configuration of a network device (wireless LAN access point). [Figure 5] This is a schematic block diagram showing the configuration of the operating terminal. [Figure 6] This is a flowchart showing the flow of security information sharing. [Figure 7] This is a flowchart showing the flow of remote operation requests and remote management. [Figure 8] This flowchart shows the remote management flow involving restarting network devices. [Figure 9] This flowchart shows the flow for remote operation requests and remote management of modified versions. [Modes for carrying out the invention]

[0037] Embodiments of the present invention will be described below with reference to the drawings. In the following description, the same parts will be denoted by the same reference numerals. Furthermore, in the case of the same reference numerals, their names and functions are also the same. Therefore, detailed descriptions of them will not be repeated.

[0038] [composition] Figure 1 is a schematic diagram showing the overall configuration of the remote management system 100. In Figure 1, the remote management system 100 comprises a network device 20 connected to a private network 10, a router 30 that relays communication between the private network 10 and the internet 40, and a remote management server 50 and an operation terminal 60 connected to the internet 40. In the following embodiment, the case where the target of remote control is a network device 20 is illustrated, but the present invention also includes the case where the target of remote control is a router 30. When the target of remote control is a network device 20, the pre-shared UDP port number (and authentication key and device-specific information) is the UDP port number (and authentication key and device-specific information) of the network device 20 located within the private network 10. When the target of remote control is a router 30, the pre-shared UDP port number (and authentication key and device-specific information) is the WAN-side UDP port number (and authentication key and device-specific information) of the router 30. In Figure 1, one network device 20 is connected to the router 30, but multiple network devices 20 may be connected to the router 30. Also, in Figure 1, one private network 10 and one router 30 are connected to the internet 40, but multiple private networks 10 and multiple routers 30 may be connected to the internet 40. Figure 2 is a schematic block diagram showing the configuration of router 30. In Figure 2, router 30 includes a WAN-side communication unit 31, a LAN-side communication unit 32, a control unit 33, a storage unit 34, a display unit 35, and an operation unit 36. The WAN-side communication unit 31 is connected to the internet 40, and the LAN-side communication unit 32 is connected to a private network 10. The display unit 35 is composed of, for example, a small liquid crystal display, LEDs, etc., and the operation unit 36 ​​is composed of, for example, toggle switches, push switches, etc. Figure 3 is a schematic block diagram showing the configuration of the remote management server 50. In Figure 3, the remote management server 50 includes a communication unit 51, a control unit 53, a storage unit 54, a display unit 55, and an operation unit 56. The communication unit 51 is connected to the Internet 40. The remote management server 50 may also be a personal computer. In some cases, communication equipment such as a router may be connected between the communication unit 51 and the Internet 40.

[0039] Figure 4 is a schematic block diagram showing the configuration of network device 20. While the network device 20 in Figure 4 is an example of a wireless LAN access point, network device 20 could also be a NAS (Network Attached Storage), a network camera, a network game console, etc. Furthermore, network devices 20 that include the functions of a router 30, such as a wireless LAN router, and a standalone router 30 are also included in network device 20. The network device 20 (wireless LAN access point) in Figure 4 includes a wireless communication unit 41, a LAN-side communication unit 42, a control unit 43, a storage unit 44, a display unit 45, and an operation unit 46. The display unit 45 is composed of, for example, a small liquid crystal display or LEDs, and the operation unit 46 is composed of, for example, a toggle switch or a push switch. In some cases, the wireless LAN access point may be integrated with a router 30 and configured as a wireless LAN router. Figure 5 is a schematic block diagram showing the configuration of the operating terminal 60. In Figure 5, the operating terminal 60 includes a communication unit 61, a control unit 63, a storage unit 64, a display unit 65, and an operation unit 66. The communication unit 61 is connected to the Internet 40. The operating terminal 60 may also be a personal computer. In addition, communication equipment such as a router may be connected between the communication unit 61 and the Internet 40.

[0040] [Operation Flow] The following describes the remote management operation flow in the remote management system 100 based on a flowchart. Figure 6 is a flowchart showing the flow of security information sharing, Figure 7 is a flowchart showing the flow of remote operation requests and remote management, and Figure 8 is a flowchart showing the flow of remote management involving the restart of network device 20. In the remote management system 100 of the present invention, security information of the network device 20 (UDP port number, authentication key, and device-specific information) is shared between the network device 20 and the remote management server 50. When the support department for the network device 20 sends a remote operation request to the remote management server 50 from the operation terminal 60 that corresponds to specific device-specific information for the network device 20, the remote management server 50 sends an authentication key to the UDP port of the network device 20. If the authentication key matches a previously shared authentication key, the network device 20 establishes a communication session for remote operation between the network device 20 and the remote management server 50, and the support department remotely manages the network device 20 from the operation terminal 60 via the communication session. Remote management includes, for example, obtaining logs from network device 20 and, if necessary, restarting network device 20 and verifying its settings.

[0041] First, we will explain the security information sharing flow step by step, based on the flowchart in Figure 6. (S1) Network device 20 generates a UDP port number and an authentication key. The UDP port number is the number of the UDP port used by the remote management server 50 to send authentication keys to the network device 20, and is randomly selected from 32768-60999. The authentication key should preferably consist of binary data of 256 bits or more. (S2) The network device 20 sends the UDP port number and authentication key, along with the device-specific information of the network device 20, to the remote management server 50 in advance via a secure route. If the network device 20 does not include the functionality of the router 30 and is connected to the private network 10 side of the router 30, the UDP port number, authentication key, and device-specific information of the network device 20 are NAPT translated by the router 30 and sent to the remote management server 50. In this case, it is preferable for the router 30 to keep the WAN port open for connection to the network device 20. Unique information can include, for example, the model number and serial number of the network device 20, and its MAC address (if the MAC address is fixed). For a secure connection, it is desirable to use MQTT communication with enhanced security through encrypted communication, specifically TLS (Transport Layer Security). Steps S1-S2 correspond to the security information transmission step. (S3) The remote management server 50 stores the received UDP port number and authentication key in the storage unit 54, associating them with the device-specific information of the network device 20. Step S3 corresponds to the security information storage step.

[0042] The timing for sharing security information (pre-sharing of UDP port numbers, authentication keys, etc.) is preferably when the network device 20 is installed on the private network 10 and can access the internet (WAN). Furthermore, security information may also be shared when there is a change in the WAN or private IP address, and may be done regularly, such as daily, weekly, or monthly.

[0043] Next, we will explain the flow of remote operation requests and remote management based on the flowchart in Figure 7. (S4) The operating terminal 60 sends a request to the remote management server 50 for remote operation of a specific network device 20. (S5) The remote management server 50 retrieves the UDP port number and authentication key corresponding to the device-specific information of the network device 20 that received the remote operation request from the storage unit 54, and sends the authentication key to the corresponding UDP port of the router 30. In this case as well, if the network device 20 is a network device connected to the private network 10 side of the router 30, the router 30 performs NAPT translation and sends it to the network device 20. Steps S4-S5 correspond to the remote control request step. (S6) The network device 20 checks whether the authentication key sent to the UDP port of the previously transmitted number matches the authentication key previously transmitted. (S7, S8) If the authentication key matches, the network device 20 establishes a remote control communication session with the remote management server 50; otherwise, it terminates the process. Steps S6-S8 correspond to the communication session establishment steps. (S9) The operating terminal 60 instructs the remote management server 50 to perform the necessary remote operations via the communication session. Step S9 corresponds to the remote management execution step. (S10, S11) Once the necessary remote operations are complete, the network device 20 discards the communication session. Furthermore, the termination of the communication session is consistent with normal TCP operation; for example, even if the network device 20 stops responding for some reason, the communication session will terminate after a predetermined period of time has elapsed. Therefore, the predetermined termination conditions include the completion of the necessary remote operations or the elapsed time since the network device 20 stopped responding.

[0044] Restarting network device 20 via remote management will terminate the communication session. Therefore, a special workflow is required for remote management when restarting network device 20. Figure 8 shows the remote management flow when the network device 20 is restarted. (S21) When restarting network device 20, first network device 20 saves the data of the communication session. (S22) Restart network device 20. (S23) After the network device 20 has restarted successfully, it checks whether there is any saved data for the communication session. If there is no saved data, it terminates the process. (S24) If there is saved data, the communication session is rebuilt using that data. The subsequent steps S9-S11 are identical to those in Figure 7.

[0045] (Security of remote management system 100) For the security of the remote management system 100, it is important that the UDP port number of the network device 20 is not detected externally, and that the authentication key is not deciphered. First, regarding port number detection, there is port scanning. This involves sending UDP packets or similar to a target port to detect the status of services listening on that port. In response, network device 20 does not send or respond to any packets sent to the relevant port, so as not to be distinguished from other ports that are not listening on anything. Furthermore, regarding the confidentiality of authentication keys, the authentication keys are composed of binary data of 256 bits or more, reducing the risk of security being compromised by the transmission of random authentication keys.

[0046] (Variations to improve security) Figure 9 is a flowchart showing the flow of remote operation requests and remote management for modified versions to improve security. In the flow shown in Figure 7, after authentication with the authentication key sent to the relevant UDP port, the network device 20 immediately establishes a communication session. However, in the modified flow shown in Figure 9, after authentication with the authentication key sent to the relevant UDP port, the newly generated UDP port number and authentication key are sent to the remote management server 50, and the communication session is established after re-authentication with the authentication key returned from the remote management server 50. In this case, in addition to requiring twice the time to discover the port number and decrypt the authentication key via UDP scanning, the security level can be further improved because the second port number and authentication key are generated immediately beforehand, eliminating any time for discovery, decryption, or leakage. The flowchart in Figure 9 will be explained step by step below. S1–S7 are identical to the flowchart in Figure 7. (S31) If the authentication keys match, the network device 20 randomly generates a second UDP port number and a second authentication key. (S32) The network device 20 sends the generated second UDP port number and second authentication key, along with the network device 20's device-specific information, to the remote management server 50 via a secure route. (S33) The remote management server 50 sends the received second authentication key to the corresponding UDP port of the network device 20. (S34, S35) The network device 20 compares the second authentication key it sent with the second authentication key it received, and terminates the process if they do not match. Steps S8-S11 when the authentication key matches are the same as in Figure 7. By using the modified flow described above, the level of security can be further improved.

[0047] (Support for Dynamic DNS) In recent years, the global IP addresses of routers and other devices are often reassigned by the provider, mainly when the router is powered off or when there has been no communication for a certain period of time. Therefore, in communication between the network device 20 and the remote management server 50, the source and / or destination IP addresses change dynamically. In this case, by specifying a domain name instead of an IP address for the source and / or destination, and by using Dynamic DNS (Dynamic Domain Name System), the IP addresses of the source and / or destination can be reliably specified. In the remote management system 100 of the present invention, domain names and Dynamic DNS are used to communicate between the network device 20 and the remote management server 50.

[0048] In the present invention, the remote management system 100 corresponds to the "remote management system," the private network 10 corresponds to the "private network," the network device 20 corresponds to the "network device," the internet 40 corresponds to the "internet," the router 30 corresponds to the "router," the remote management server 50 corresponds to the "remote management server," and the operation terminal 60 corresponds to the "operation terminal."

[0049] While the above describes a preferred embodiment of the present invention, the invention is not limited thereto. It will be understood that various other embodiments can be made without departing from the spirit and scope of the invention. Furthermore, although the operation and effects of the configuration of the present invention are described in this embodiment, these operations and effects are examples and do not limit the invention. [Explanation of Symbols]

[0050] 10 Private Network 20 Network Devices 30 routers 40 Internet 50 Remote Management Servers 60 Operating terminals 100 Remote Management Systems

Claims

1. A remote management system comprising a network device connected to a private network, a router that relays the private network and the internet, and a remote management server and operating terminal connected to the internet, The network device randomly generates its UDP port number and authentication key and transmits them to the remote management server in advance via a secure route along with the network device's device-specific information. When the remote management server receives the UDP port number, the authentication key, and the device-specific information of the network device, it stores the received UDP port number, the authentication key, and the device-specific information of the network device. When the operating terminal requests the remote management server to perform an operation on the network device, the remote management server transmits the authentication key to the UDP port of the network device corresponding to the device-specific information of the network device. If the authentication key received on the UDP port matches the authentication key previously transmitted by the network device, the network device establishes a communication session between the network device and the remote management server corresponding to the device-specific information. The aforementioned operating terminal is a remote management system that remotely manages the network device via the remote management server and the communication session.

2. The remote management system according to claim 1, wherein when a UDP packet is sent from the internet side to the UDP port of the network device, the network device does not make any response or transmission.

3. The remote management system according to claim 1, wherein the network device is a wireless LAN access point or a NAS.

4. The remote management system according to claim 1, wherein the network device includes the functions of the router.

5. The remote management system according to claim 1, wherein TLS (Transport Layer Security) is used for the secure route and the communication session.

6. The remote management system according to claim 1, wherein the remote management server or the network device discards the established communication session when a predetermined termination condition is met.

7. A router that relays between a private network and the internet, The UDP port number and authentication key on the internet side are randomly generated. The generated UDP port number, the authentication key, and the device's own device-specific information are sent to the remote management server via a secure route. On the UDP port of the aforementioned UDP port number, if the authentication key transmitted from the remote management server is received and the received authentication key matches the transmitted authentication key, a communication session is established with the remote management server. A router that accepts remote control of an operating terminal via the aforementioned communication session.

8. A remote management method for performing remote management in a remote management system comprising a network device connected to a private network, a router that relays between the private network and the internet, and a remote management server and operating terminal connected to the internet, The security information transmission step involves the network device randomly generating the network device's UDP port number and authentication key and sending them in advance to the remote management server via a secure route along with the network device's device-specific information. When the remote management server receives the UDP port number, the authentication key, and the device-specific information of the network device, it performs a security information storage step of storing the received UDP port number, the authentication key, and the device-specific information of the network device. A remote operation request step in which the operating terminal requests the remote management server to perform an operation on the network device, and the remote management server transmits the authentication key to the UDP port of the network device corresponding to the device-specific information of the network device, If the network device receives the authentication key on the UDP port and the authentication key sent in advance matches the authentication key, the network device establishes a communication session corresponding to the device-specific information between the network device and the remote management server (component of the remote management server). A remote management method comprising: a remote management execution step in which the operating terminal remotely manages the network device via the remote management server and the communication session.

Images