TWI465071B - Remote messaging system and its connection method - Google Patents

Description

Remote communication system and its connection method

A remote message communication system and a connection method thereof, in particular, a system for guiding at least one remote device, a connection server, and a near-end device connection target by using a management server, and a connection method.

Due to the rapid development of network technology, many electronic products can be connected to the Internet with remote monitoring, online updates or online services provided by other operators. For example, U.S. Patent No. 6,373,851, the disclosure of which is incorporated herein by reference. A communication system is disclosed that includes a first communication medium, an ethernet polling server, and a plurality of ethernet client stations. The Ethernet server includes a transmitter connected to the first transmission medium, and the transmitter transmits a signal bidirectionally with the first transmission medium. And the plurality of Ethernet device terminals are connected to each other, and each of the Ethernet device devices has a transmitter, the transmitter includes a second transmission medium, and the second transmission medium is only in the Ethernet server. A signal is transmitted to the first transmission medium when requested, but the second transmission medium can receive the signal from the first transmission medium at any time. US 6,373,851 is based on traffic control equipment and is limited by the minimum transmission rate of the Ethernet and the recommended maximun recommended distance. Therefore, the foregoing proposal proposes the aforementioned design to provide a larger transmittable range and avoid collision and delay of device-side transmission.

The connection between the near-end device and the device end through the Internet is a commonly used technology. If the home appliance product is to be promoted, the home appliance product needs to be routed to cause complicated wiring and increase construction trouble. Therefore, another technology that utilizes a power network as a communication network, such as the US Patent No. US2005/0047379, discloses a patent that utilizes broadband wireless/ Power line communication system technology for transmitting audio and video content. One of the data servers receives the video and audio message and converts it into a PLC compatible signal. The PLC represents Power-line communication. And the former case provides a power transmission/broadband wireless transmission module (PLC/UWB module), and establishes a data connection with the signal transceiver of an electrical device through the power transmission/broadband wireless. Therefore, the electrical device can receive the network message and be remotely monitored, and transmitted through the power line, without the need to pull the network route.

A technique for providing transmission using a power line also includes a prior art patent of US 2004/0186908, which discloses a power plug including an AC power line, a network data line, and a power line network adapter. In another embodiment of the prior invention, the power plug includes an AC-DC conversion component in addition to the AC power line, the network data line, and the power line network adapter.

This type of power line transmission technology is applied to the prior art of the security surveillance system, such as the "Camera System and Camera Control Method" of the People's Republic of China Authorized Notice No. CN 100389602. The foregoing case discloses that a camera module is connected to a power line communication camera adapting module, and the power line communication camera adapting module receives the audio/video information recorded by the camera module, and modulates the audio/video information and inputs the power line. transmission. At the same time, the modulation signal transmitted by the power line is demodulated to obtain a control signal, and the camera module is controlled by the control signal. The power line communication camera adaptation module includes an image signal processing unit, a digital multimedia information compression processing unit, an Ethernet adapter unit, and a first power line communication modulation and demodulation unit. The image signal processing unit and the digital multimedia information compression processing unit compress or convert the image signal format output by the camera module. The Ethernet adaptation unit is further converted into an Ethernet signal, and the first power line communication modem unit loads the Ethernet signal onto the power carrier for transmission. With the foregoing structure, the video signal of the camera module can be transmitted to the monitoring terminal through the power line.

Electrical equipment can solve the problem of network route troubles by connecting to the power line. Various electrical equipment or security alarm devices can be accessed directly through the power line. However, when implementing remote monitoring, the following problems still exist: First, through the conventional network connection means, the electrical devices allocate an IP (possibly fixed IP or floating IP) through a router, and then need to be built. A server accepts the electrical device end and the monitoring end (user end) to exchange data in the server. The problem faced by the conventional architecture is that the monitoring terminal needs to remember the electrical name of the electrical device or the server, or the IP address of the server can be connected. In addition to the memory address, the user or the server needs to be troubled. When expanding the number or changing the address, all the domain name or IP address needs to be updated by the user, which is very troublesome and causes troubles when the system is expanded. Furthermore, since the electrical name or IP address of the electrical device or the server is publicly disclosed, it is susceptible to being recorded or destroyed by the hacker, and the security is insufficient.

In order to improve the lack of scalability and security of the conventional connection method, the purpose of this case is to propose an improved connection and monitoring system, and to make the system expandable and enhanced security.

The present invention is a remote message communication system and a connection method thereof, wherein the connection method comprises the following steps: A. at least one remote device requests a management server to provide at least one connection supporting the remote device through the Internet. The address of the server; B. the remote device logs the information of the remote device to the connection server according to the address provided by the management server; C. a near-end device communicates to the management server through the Internet Presenting a request to find the designated remote device; D. the management server will respond to the near-end device by the address of the connection server to which the specified remote device is logged; E. the near-end device responds The address of the connection server to the connection server to the designated remote device; F. the connection server establishes the connection between the near-end device and the designated remote device according to the request of the near-end device line.

The foregoing method can be implemented by the remote message communication system proposed in the present application. The remote message communication system includes: a management server, at least one connection server, at least one remote device, and the monitoring system is acceptable. One or more near-end devices are connected. Which should The management server stores a server list and a device list, and the connection server logs into the server list to the management server, and the remote device requests the management server to request the connection server address. And being logged in the device list, so that the management server stores information about all the connection servers and remote devices in the remote monitoring device. In addition, the management server responds to the request of the remote device and responds to the address of one of the connected servers, so that the remote device logs the information of the remote device according to the responded address to one of the connected servers. In the device. And a near-end device requests the management server to find the designated remote device, and the management server responds to the connection server that is logged in by the designated remote device, so that the near-end device passes the management. The connection server provided by the server establishes a connection with the designated remote device.

In a specific implementation manner, the management server includes at least one management server, the number of the management server can be expanded according to requirements, and the management server stores a servo that memorizes one or more connection servers. List of devices, as well as a list of devices that memorize one or more remote devices. The connection server includes at least one connection server. The number of the connection server and the remote device can also be continuously expanded. When the number of the connection server and the connection server connection information are changed, the device list and the server of the management server can be updated. Add a supported device to the list. The server list may include a connection server operated by a plurality of connection server different service providers, and the management server may assign the remote device to log in according to a different service provider supporting the remote device. Different connection servers. The management server may also assign the remote device to log in to a different connection server according to the product type of the remote device or the geographical location of the remote device. The near-end device has an Application Programming Interface (API) for the user to request to find any remote device. After the near-end device finds the connection server registered by the designated remote device through the management server, the near-end device requests the connection server to connect with the designated remote device, and the connection server The device first performs a hole punching technique between the near-end device and the designated remote device, attempting to establish a relationship between the near-end device and the designated remote device. The point-to-point connection, if the connection server does not complete the hole punching procedure for the two, the data packet of the near-end device and the designated remote device is mutually forwarded through the connection server.

The aforementioned remote device can be a security alarm device or an electrical device. The remote device re-registers the information of the remote device with the connection server assigned by the management server after a period of time, so that the connection server frequently updates the latest state of the remote device. When the remote device changes, or the connection server to which the remote device is logged changes, the remote device may request the management server to provide at least one connection server that supports the remote device. The address of the device, and the remote device logs its information back to the provided connection server again.

Through the foregoing technology, the remote device and the connection server do not need to directly expose their IP address or Domain name to reduce the risk of being invaded by the hacker. Similarly, the near-end device does not need to have a fixed IP, nor does it need to memorize a fixed IP address or a domain name, and only through the management server can find the connection server to which the specific remote device belongs. Therefore, the near-end device only needs to have an Application Programming Interface (API) supported by the management server to request the management server to query the connection address. Moreover, the system allows the number, specifications, and categories of the remote device and the connection server to be expanded and changed according to requirements, and only needs to log in to the management server to update the server list and device list. The manufacturer of the connection server or remote device can vary depending on the amount of equipment load.

This case is a remote message communication system and its connection method. The following describes the technology of this case in conjunction with each figure.

First, the present disclosure defines a remote messaging system including at least one remote device, a management server, and at least one connection server, and the remote communication system accepts a request from at least one near-end device to make the near-end A connection method between the device and the remote device, and a connection method of the remote communication system, the method includes the following steps: A. at least one remote end The device requests the management server to provide at least one address of the connection server supporting the remote device through the Internet; B. the remote device logs in to the remote device according to the address provided by the management server. Information on the connection server; C. A near-end device requests the management server to locate the designated remote device through the Internet; D. The management server will be designated to log in to the remote device The address of the server is replied to the near-end device; E. the near-end device requests the connection server to connect to the designated remote device according to the responded address; F. the connection server is based on The connection of the near-end device to the designated remote device is established by the request of the near-end device. The technical focus of the method is that the connection server and the remote device do not need to directly disclose their IP address or Domain name. All the near-end devices can only request the management server to find the designated remote device first. The address of the connection server provided by the management server is requested by the near-end device to establish a connection. Therefore, the connection server and the remote device can be reduced to reduce the risk of being invaded by the hacker. From the perspective of the near-end device, the near-end device does not need to have a fixed IP, nor does it need to memorize a fixed IP address or a domain name, which can save a lot of technical problems of connection settings for users of the near-end device. .

In order to more specifically describe the foregoing method, the present disclosure further discloses a remote message communication system that specifically implements the method, the remote message communication system including at least one management server, at least one connection server, and at least one remote device. . Please refer to FIG. 1. FIG. 1 is a schematic diagram showing the architecture of the remote message communication system. In Figure 1, it can be seen that the two management servers 11, 12 form a management server group 1 for mutual backup. The management server 11, 12 stores a device list and a server list, and the device list stores information of a plurality of remote devices that are allowed to log in. The server list stores information about the multiple connection servers. In a specific implementation manner, the server list may include multiple connection servers operated by different service providers, or multiple connection servers with different supported device types, or multiple locations. A different connection server. Further, there is a correspondence between the device list and the server list, which will be described in detail later. In Figure 1 It can be seen that the remote communication system further has a connection server 201 and a connection server 211. In this embodiment, the connection server 201 and the connection server 202 can be belonged to different service providers. Operation. Moreover, it can be seen in FIG. 1 that the connection server 201 can form a connection server group A 20 with another connection server 202 for mutual backup; similarly, the connection server 211 is connected to another connection. The server 212 constitutes a connection server group B 21 to be mutually redundant. In order to facilitate the description of the technology of the present invention, the following connection objects will directly represent the server to which the server group 1 and the connection server group A 20 and the connection server group B 21 belong. The remote communication system further includes a remote device A 31, a remote device B 32, and a remote device C 33. As described above, the device list has information of a plurality of remote devices, and the remote devices A~C 31, 32, and 33 each have their unique serial number (Unique ID), and the remote devices A~C 31 The messages of the service providers to which the 32 and 33 belong are pre-stored in the device list stored in the management server group 1. When the connection server group A 20, the connection server group B 21, and the remote device A 31, a remote device B 32, and a remote device C 33 are connected to the Internet. The connection server group A 20 and the connection server group B 21 transmit a server login information 92 to the management server group 1 via the Internet to log in the address and configuration information (model, connection) Status and other information). The management server group 1 verifies whether the connection server group A 20 and the connection server group B 21 are legitimate devices that are pre-stored in the server list, and if the connection server group A 20 is replied to The connection server group B 21 has been successfully logged in. In order to find a server that can be supported, the remote device A 31 to the remote device C 33 respectively send a server query information 91 to the management server group 1 through the Internet. The management server group 1 After verifying whether the remote device A 31 to the remote device C 33 are pre-stored in the device list, the remote device A 31 to the remote device C 33 respectively reply to the connected target.

In a specific implementation manner, the connection server group A 20 and the connection server group B 21 may be operated by different service providers respectively. Therefore, the management server group 1 will be remotely located. Device A 31 assigns a connection to the service provider supporting remote device A 31 Connected server group A 20. Similarly, based on the service provider, the remote device B 32 and the remote device C 33 are assigned by the management server group 1 to the service provider supporting the remote device B 32 and the remote device C 33. The connected server group B 21 that is operated. However, the remote messaging system also includes different implementations. The management server group 1 may also assign the remote device separately because the remote device A 31 to the remote device C 33 are different product types. A 31 to the remote device C 33 log in to the connection server group A 20 or the connection server group B 21 . Another different implementation manner is that the management server group 1 can also be assigned to connect to the closer connection server group A 20 according to the geographical location of the remote device A 31 to the remote device C 33 itself. Connect to server group B 21.

Referring to FIG. 2, based on the connection address that the management server group 1 responds, the remote device A 31 is connected to the connection server group A 20 and logs in the information of the remote device A 31. Connect to server group A 20. Similarly, according to the connection address that the management server group 1 responds, the remote device B 32 and the remote device C 33 are connected to the connection server group B 21, and log in their own information to the connection. In server group B 21 . Let the connection server group A 20 know the network address of the remote device A 31; the connection server group B 21 knows the network of the remote device B 32 and the remote device C 33 Address.

Referring to FIG. 3, the remote communication system can connect one or more near-end devices 4, and the near-end device 4 needs to have an application interface program supporting the connection with the management server group 1 (Application Programming) Interface, API), the near-end device 4 can select a designated remote device through the application interface program. It is assumed that the near-end device 4 is connected to the remote device A 31 through the application interface program, and the near-end device 4 sends a link query information 94 to the management server group 1 through the application interface program to query the management server. What is the connection server group that can be connected to the remote device A 31? The management server group 1 provides the location of the connection server group A 20 to which the designated remote device (the remote device A 31) is registered. Therefore, the application interface program of the near-end device 4 is further connected to the connection server group A 20 according to the address of the management server group 1 replying, The near-end device 4 issues a connection request message 95 to be connected to the remote device A 31. Referring to FIG. 5, the connection server group A 20 preferentially uses a hole punching technique to transmit a dozen holes connection messages 960 and 961 to the near-end device 4 and the remote device A 31, respectively. Having the near-end device 4 establish a point-to-point transmission connection 97 with the designated remote device A 31, the near-end device 4 can obtain information of the remote device A 31 through a point-to-point transmission technology, or the remote device A 31 controls. The aforementioned hole punching technique can be referred to the Patent No. 200935808 of the Republic of China, or the patent of the Republic of China Patent No. M382669. Since the hole punching technique is not a technical feature claimed in the present case, the technical content thereof will not be described again. . Alternatively, as shown in FIG. 6, if the connection server group A 20 does not complete the hole punching procedure for both, the near-end device 4 and the designated one are mutually forwarded through the connection server group A 20 The data packet of the remote device A 31.

Since the near-end device 4 needs to obtain the connection address of the connection server group A 20 and the connection server group B 21 through the management server group 1, the connection server group A 20 The address and mechanical specification change of the connection server group B 21 does not prevent the near-end device 4 from finding a connection object. Based on this feature, the architecture (quantity, specification, category, etc.) of the connection server group B 21 can be changed according to the needs of the market. For example, when the number of online products of a certain type of products increases, the support for such products can be increased. The number of connected servers to match the device load. You only need to update the server list when adding a connection server group or changing the connection information of the connection server group (such as IP address change) or changing the number of machines in the connection server group. Let the connection server group send the server login information 92 to the management server group 1 again to log in. Similarly, when the number and type of remote devices change, or when the connection server group to which the remote device is logged changes, the device list is also updated, and the remote device again provides the provided connection servo. The group asks for the connection server group information for the connection.

Please refer to FIG. 7. FIG. 7 is an embodiment of the extension of the remote communication system. The embodiment adds a remote device D 34, which can be updated even if the number or address changes are increased. This manages the device list of server group 1 and increases the number of supported remote devices (or specifications). Both the remote device A 31 and the remote device D 34 can re-query the connectable connection server group by the management server group 1 through the process of transmitting the server query information 91. Similarly, in FIG. 7, it can be seen that the connection server group B 21 adds a connection server 213, and a new connection server group C composed of connection servers 221, 222, and 223 is added. 22. Similarly, the number of connection servers entering the remote messaging system is amplified by updating the server list of the management server group 1. Therefore, the remote communication system allows the number, specifications, and categories of the remote device and the connection server group to be expanded and changed according to requirements, and only needs to update the server list, the device list, and again to the management server group. Group 1 login is sufficient, so that the manufacturer of the connection server group or the remote device can be changed according to the load of the device.

The remote communication system allows multiple connection servers to accept the same remote device login. Referring to FIG. 8, FIG. 8 discloses that the remote communication system includes connection server groups A, D, and E20. 23, 24, the connection server group D 23 is composed of connection servers 231, 232, and the connection server group E 24 is composed of connection servers 241, 242. After the remote device A 31 queries the management server group 1 by issuing the server query information 91, the management server group 1 replies to the remote device A 31 and the connection server groups A and D. , E 20, 23, 24 to log in. Through this feature, the different connection server groups A, D, E 20, 23, 24 can support the remote device A 31 together. The remote device A 31 can still log in to one of the connection server group D 23 or the connection server group E 24 assuming that the connection server group A 20 is faulty or other reasons are offline. It is also assumed that the remote device A 31 is a mobile device, and the remote device A 31 can be connected to any of the connected server groups whose physical distance is closest through the allocation of the management server group 1.

The correspondence between the plurality of remote devices and the connection server group is as shown in Table 1:

Taking Table 1 as an example, the server list of the foregoing management server may store the connection servers Ser01~Ser05 operated by the service provider A and the connection servers Ser11~Ser12 operated by the service provider B. The connection server Ser01~Ser03 is assigned to the remote device D01~D05 to log in, where D01~D05 are the serial numbers of the remote devices. As described earlier, each remote device has its unique serial number for Used by the management server or connection server to verify and identify the identity of the remote device. The connection servers Ser01~Ser03 receive the request of the near-end device to establish a connection with the remote devices D01~D05. Since the connection server Ser01~Ser03 can perform the same function, the connection server Ser01~Ser03 can be mutually redundant, and the connection server Ser01~Ser03 can be set to different positions, for example, connection. The servers Ser01~Ser03 are located in Shanghai, Tokyo, and Los Angeles, and the remote devices D01~D05 can be registered in the connection server that is close to the geographical location. Similarly, the remote devices D04~D05 accept the remote devices D06~D09 to log in. The connection server Ser11~Ser12 operated by the service provider B accepts the login of the remote devices D11~D14. Therefore, for the management server, as long as the remote device D01 goes online to query the connection server, the management server can simultaneously provide the location of the connection server Ser01~Ser05 to the remote The end device D01 allows the remote device D01 to find a working connection server at any time.

Thereby, the plurality of connection server groups in the remote communication system can be mutually supported, and the connection server group includes a plurality of connection servers that can be mutually redundant. The multiple backup architecture makes the remote messaging system very stable and does not affect operation due to a few mechanical failures.

Referring to FIG. 9, the operation between the foregoing connection server and the management server is as shown in FIG. 9. First, when one or more connection servers are online (step S01) or one or more connections. When the IP or Port of the line server is changed (step S02), the connection server needs to connect to the management server via the Internet, and sends the server login information to the management server (step S03). The management server verifies whether the content of the server login information is legal in the server list (step S04). If the verification is successful, it means that the connection server is indeed a legitimate server in the server list, according to the servo. The server login information updates the server list (step S05), and the management server replies with the login success message (step S06), the connection server receives the reply message (step S07), and ensures that the management server can be connected. The latest state of the line server group will repeat the step S03 to resend the server login information every time a predetermined time elapses (step S09). If it is verified in step S04 that the server login information is failed, it means that the connection server is not in the server list, and is an illegal connection server, and also replies with the login failure message (step S08), and the connection server is connected. The reply message is received (step S07).

Next, FIG. 10 shows a process in which the remote device and the management server are connected to request to reply to the connection server. First, the remote device sends a message asking the server address (step S11), the management server verifies whether the message sent by the remote device is valid (step S12), and if the verification is successful, the management server replies with a connection. The address of the server is given to the remote device (step S13); if the verification fails, the management server replies with a reject request message to the remote device (step S14). Then, the remote device needs to be connected to the connection server that the management server replies. The remote device sends a login message of the remote device (step S15), and connects The server group receives the login message (step S16), and then the connection server replies with a response message to the remote device (step S17). Therefore, the connection server can know the IP address of the remote device to contact the necessary information of the remote device. In order to ensure that the connection server can find the remote device, after each predetermined time (which can be preset every 10 minutes), the remote device needs to return to step S15 to re-send its own information message (step S18). So that the connection server can obtain the update status of the remote device from time to time. Moreover, the remote device can re-interrogate the management server every time (for example, every 24 hours can be preset) (step S19), so that the management server provides the latest connection server address setting information.

Finally, the process of requesting the near-end device to connect to the remote device can be seen in FIG. 11. The user specifies a remote device through an application interface program (API) of the near-end device, and the near-end device passes the application interface program ( The API) submits a request for finding the designated remote device to the management server (step S21), and the management server returns the address of the connection server that the remote device logs in to the near-end device (step S22), so The near-end device can get a connection to which connection server to find the designated remote device. Then, the near-end device requests the connection server to connect to the remote device (step S23), and the connection server preferentially selects a hole punching process for the near-end device and the remote device (step S24), if If successful, the near-end device and the remote device may perform point-to-point transmission (step S25); if it fails, the data packet of the near-end device and the remote device is forwarded through the connection server (step S26).

Through the foregoing technology, the remote device and the connection server do not need to directly expose their IP address or Domain name to reduce the risk of being invaded by the hacker. Similarly, the near-end device does not need to have a fixed IP, nor does it need to memorize a fixed IP address or a domain name, and only through the management server can find the connection server to which the specific remote device belongs. Therefore, the near-end device only needs to have an application programming interface (API) supported by the management server to request the management server to query the connection address, and the user only needs to select one of the remote devices. The program that communicates with the management server and the connection server can be automatically processed by the application interface program to Simplify the complexity of user operations. Moreover, the system allows the number, specifications, and categories of the remote device and the connection server to be expanded and changed according to requirements, and only needs to log in to the management server to update the server list and device list. The manufacturer of the connection server or remote device can vary depending on the amount of equipment load. The aforementioned remote device may be a security alarm system, such as a surveillance photographic equipment, an alarm, a smoke fire alarm, etc.; or an electrical device such as a refrigerator, an air conditioner, or the like. Furthermore, the near-end device should have audio and video playback functions, such as a mobile phone with audio and video playback capabilities, a computer, a personal digital assistant (PDA), and the like.

Although the present invention has been disclosed above in the preferred embodiment, it is not intended to limit the present invention. Anyone who is familiar with this skill and does not deviate from the spirit and scope of this case, and some of the changes and refinements should be covered in this case. Therefore, the scope of protection of this case is subject to the definition of the patent application scope attached.

In summary, this case enhances the above-mentioned effects compared with the well-known creations. It should fully comply with the statutory innovation patent requirements of novelty and progressiveness. If you apply in accordance with the law, you are requested to approve the application for this invention patent to encourage creation. Debian.

1‧‧‧Manage server group

11, 12, 13‧‧‧Management Server

20‧‧‧Connection Server Group A

201, 202‧‧‧ connection server

21‧‧‧Connection Server Group B

211, 212, 213‧‧‧ connection server

22‧‧‧Connected Server Group C

221, 222, 223‧‧‧ connection server

23‧‧‧Connected Server Group D

231, 232‧‧‧ connection server

24‧‧‧Connection Server Group E

241, 242‧‧‧ connection server

31‧‧‧ Remote Device A

32‧‧‧Remote device B

33‧‧‧Remote device C

34‧‧‧Remote device D

4‧‧‧ Near-end equipment

91‧‧‧Server query information

92‧‧‧Server Login Information

93‧‧‧Remote device information

94‧‧‧Contact information

95‧‧‧Connection request information

960, 961‧‧‧ hole connection message

97‧‧‧ Point-to-point transmission connection

98, 99‧‧‧ generation forwarding data packets

S01~S09‧‧‧Steps

S11~S19‧‧‧Steps

S21~S26‧‧‧Steps

Fig. 1 is a schematic view showing the state of the first embodiment (1).

Fig. 2 is a schematic view showing the state of the first embodiment (2).

Fig. 3 is a schematic view showing the state of the first embodiment (3).

Fig. 4 is a schematic view showing the state of the first embodiment (4).

Fig. 5 is a schematic view showing the state of the first embodiment (5).

Fig. 6 is a schematic view showing the state of the first embodiment (6).

Fig. 7 is a schematic view showing the state of the first embodiment (7).

FIG. 8 is a schematic diagram of a plurality of connection server groups for a remote device to log in.

Figure 9 is a flow chart of the connection between the connection server and the management server.

Figure 10 is a flow chart showing the connection between the remote device and the connection server.

Figure 11 is a flow chart showing the connection of the near-end device requesting connection with the remote device.

1‧‧‧Manage server group

11, 12‧‧‧Management Server

20‧‧‧Connection Server Group A

201, 202‧‧‧ connection server

21‧‧‧Connection Server Group B

211, 212‧‧‧Connected server

31‧‧‧ Remote Device A

32‧‧‧Remote device B

33‧‧‧Remote device C

4‧‧‧ Near-end equipment

960, 961‧‧‧ hole connection message

97‧‧‧ Point-to-point transmission connection

Claims (30)

A method for connecting a remote message communication system, the method comprising the following steps: A. at least one remote device requests an administrative server to provide at least one address of a connection server supporting the remote device through an internet network B. The remote device logs the information of the remote device to the connection server according to the address of the connection server provided by the management server; C. a near-end device transmits the information through the Internet The management server makes a request to find the designated remote device; D. the management server responds to the request for the designated remote device, and the connection server to which the remote device is logged in Responding to the near-end device; E. the near-end device submits a request to the connection server to connect to the designated remote device according to the address of the connected server; and F. The connection server establishes a connection between the near-end device and the designated remote device according to the request of the near-end device; wherein the remote device sends another Internet request after the predetermined time passes To the management server to Connection to the server after the address of a new update of the at least one query of the address of the remote device to support the connection server and the management server in response to the received Internet request further backhaul. The method for connecting a remote message communication system according to claim 1, wherein the plurality of management servers can form a management server group, and the plurality of management servers in the same management server group are mutually redundant. And the management servers store a list of servers that memorize one or more connection servers, and a list of devices that memorize one or more remote devices. The method for connecting a remote message communication system according to claim 2, wherein the management server provides a different address for the remote device to log in according to the different service provider supporting the remote device. To a different connection server. The method for connecting a remote message communication system as described in claim 2, wherein the tube The server provides distinct addresses for the remote device to log in to a different connection server based on the product type of the remote device. The method for connecting a remote message communication system according to claim 2, wherein the management server provides a different address according to the geographical location of the remote device for the remote device to log in to the different device. Connection server. The method for connecting a remote message communication system according to claim 1, wherein the plurality of connection servers can form a connection server group, and the plurality of connection servos in the same connection server group The devices are mutually redundant. The method for connecting a remote message communication system according to claim 2, wherein the management server updates the server list and the device list content to add or change the connection server and the remote device. The method for connecting a remote message communication system according to claim 1, wherein the near device has an Application Programming Interface for the user to make a request to find any remote device. The method for connecting a remote message communication system according to claim 1, wherein the connection between the near-end device and the designated remote device is performed by the connection server (Hole) Punching) causes the near-end device to perform point-to-point transmission with the designated remote device. The method for connecting a remote message communication system according to claim 1, wherein the connection between the near-end device and the designated remote device forwards the near-end device to each other through the connection server. The data packet of the specified remote device. The method for connecting a remote message communication system according to claim 1, wherein the connection between the near-end device and the designated remote device is first performed by the connection server to the near-end device The designated remote device performs the hole punching technique. If the connection server does not complete the hole punching process for the two, the data packet of the near device and the designated remote device is mutually forwarded through the connection server. For example, the connection method of the remote message communication system described in claim 1 of the patent scope, wherein the far After a period of time, the end device re-registers the information of the remote device with the connection server assigned by the management server according to the address of the updated connection server returned by the management server. The method for connecting a remote message communication system according to claim 1, wherein the remote device can again request the management server to provide at least one address server supporting the remote device, and The remote device logs its information back to the provided connection server again. The method of connecting a remote message communication system according to any one of claims 1 to 13, wherein the remote device is a security alarm device. The method of connecting a remote message communication system according to any one of claims 1 to 13, wherein the remote device is an electrical device. The method of connecting a remote message communication system according to any one of claims 1 to 13, wherein the near-end device has a video playback function. The method for connecting a remote message communication system according to any one of the preceding claims, wherein before the step A, the connection server transmits the management server to the management server through the Internet. Server login information for the management server to verify the connection server and log in the address and configuration information of the connection server to the management server, and the management server is provided to support the remote device The address of the connection server successfully verified and logged in to the remote device. A remote message communication system includes: at least one management server, the management server stores a server list and a device list; at least one connection server, the connection server is connected to the management server In the server list; at least one remote device, the remote device requests a connection server address from the management server to be logged in the device list, and each remote device responds according to a connection position of the management server Addressing the information of the remote device to one of the connection servers; wherein the management server accepts a request from the near end device to find the designated remote device Providing a connection server registered by the designated remote device, the near-end device establishing a connection with the designated remote device through a connection server provided by the management server; and wherein the remote device passes through After the predetermined time, the remote device sends a request to the management server to re-query the address of the at least one connection server supporting the remote device and receives an update sent back by the management server in response to the request. The address of the subsequent connection server. The remote message communication system according to claim 18, wherein the plurality of management servers can form a management server group, and the plurality of management servers in the same management server group are mutually redundant, and the The management server stores a list of servers that memorize one or more connection servers, and a list of devices that memorize one or more remote devices. For example, the remote message communication system described in claim 18, wherein the plurality of connection servers can form a connection server group, and the plurality of connection servers in the same connection server group are mutually redundant. . The remote message communication system of claim 20, wherein the plurality of connection servers are divided into a plurality of connection servers operated by different service providers. The remote message communication system according to claim 20, wherein the plurality of connection servers are divided into a plurality of connection servers supporting remote devices of different product types. The remote message communication system according to claim 20, wherein the plurality of connection servers are divided into a plurality of connection servers disposed in different geographical locations. The remote message communication system according to claim 18, wherein the near-end device has an Application Programming Interface for the user to make a request for finding the designated remote device. The remote message communication system of claim 18, wherein the connection between the near-end device and the designated remote device is performed by the connection server to perform a hole punching The near-end device performs point-to-point transmission with the designated remote device. The remote message communication system of claim 18, wherein the connection between the near-end device and the designated remote device forwards the near-end device to each other through the connection server The data packet of the specified remote device. The remote message communication system of any one of claims 18 to 26, wherein the remote device is a security alert device. The remote message communication system of any one of claims 18 to 26, wherein the remote device is an electrical device. The remote message communication system according to any one of claims 18 to 26, wherein the near-end device is a device having a video playback function. The remote message communication system according to any one of claims 18 to 26, wherein the connection server transmits a server login information to the management server for the management server to verify the Connecting the server and logging in the address and configuration information of the connection server, and the management server is providing the address of the connection server that supports the remote device and has successfully verified and logged in to the remote end. device.