Ecological environment quality monitoring system

Abstract

The embodiment of the invention provides an ecological environment monitoring system. The ecological environment monitoring system comprises gateway equipment which is deployed at a monitoring point position and is locally connected with data interfaces of environment monitoring equipment, and a remote server which is in communication connection with the gateway equipment through a communication network, the fault gateway device sends the reported data stored in the buffer mode to the replacement gateway device through the non-network interface, and the replacement gateway device forwards the reported data to the remote server. And the gateway equipment can be used as relay equipment to forward the reported data to a remote server after being replaced. Therefore, the temporary storage data of the fault gateway equipment can be stored without manual data reading, and the security of the data is ensured.

Description

Technical Field

[0001] The present disclosure relates to the technical field of Internet of Things, and in particular to an ecological environment quality monitoring system. Background Art

[0002] In order to reduce the problem of environmental monitoring data leakage and tampering caused by loopholes in the middle link, the relevant technology proposes an ecological environment monitoring system that adopts a remote server and a local gateway device architecture system, using the local gateway device as a data transmission relay to enable the remote server to directly control the local environmental monitoring equipment of the environmental monitoring site, and directly report the reported data generated by the local environmental monitoring device to the remote server. However, under the aforementioned monitoring system, it is inevitable that the gateway device cannot send the reported data generated by the environmental monitoring device to the remote server due to its own failure (mostly a network interface failure, that is, a network card failure). In actual applications, in this case, the gateway device generally cannot be replaced and updated immediately, but needs to continue to buffer and store data as a data relay device. When the equipment is replaced later, the buffered reported data will be exported and reported to the remote server. In this case, how to safely export the reported data buffered and stored by the gateway device is another issue that needs to be considered. Summary of the invention

[0003] In order to solve the problem of possible data leakage when replacing gateway devices in the existing environmental monitoring system, the embodiment of the present disclosure provides a new ecological environment quality monitoring system.

[0004] In a first aspect, an embodiment of the present disclosure provides an ecological environment monitoring system, including a gateway device deployed at a monitoring point and locally connected to a data interface of each environmental monitoring device, and a remote server connected to the gateway device via a communication network;

[0005] When the network interface between the faulty gateway device and the remote server fails and cannot upload the reported data sent by the environmental monitoring device, the replacement gateway device replaces the faulty gateway device to establish a trusted connection with the remote server, and after the faulty gateway device is connected to the non-network interface of the replacement gateway device, the faulty gateway device sends the buffered reported data to the replacement gateway device through the non-network interface, and the replacement gateway device forwards the reported data to the remote server.

[0006] Optionally, before the faulty gateway device forwards the buffered reported data to the replacement gateway device through the non-network interface, the method further includes:

[0007] The faulty gateway device generates a verification request message and sends it to the replacement gateway device;

[0008] After receiving the verification request message, the replacement gateway device sends the verification request message to the remote server;

[0009] When the remote server receives the verification request message and determines that the replacement gateway device has been remotely verified, it generates a return message based on the first dynamic ID and sends the return message to the replacement gateway device; the first dynamic ID is a dynamic ID generated by the remote server and sent to the faulty gateway device when the faulty gateway device is connected to the remote server before the communication failure occurs;

[0010] After receiving the return message, the replacement gateway device sends the return message to the faulty gateway device;

[0011] After receiving the return message, the faulty gateway device verifies whether the first dynamic ID is the same as the locally stored dynamic ID, and sends the reported data to the replacement gateway device if the first dynamic ID is the same as the locally stored dynamic ID.

[0012] Optionally, before sending the reported data to the replacement gateway device, the faulty gateway device encrypts the reported data using a target encryption strategy to obtain encrypted reported data; sending the reported data to the replacement gateway device is specifically: sending the encrypted reported data to the replacement gateway device;

[0013] The target encryption policy is an encryption policy for which only the remote server has a corresponding decryption policy, or an encryption policy for which only the remote server and the faulty gateway device have a corresponding decryption policy.

[0014] Optionally, before the faulty gateway device forwards the buffered reported data to the replacement gateway device through the non-network interface, the method further includes:

[0015] Replace the gateway device to send a verification request message to the remote server;

[0016] After the remote server receives the verification request message, it generates a return message including a first dynamic ID and sends it to the remote server; the first dynamic ID is a dynamic ID generated by the remote server and sent to the faulty gateway device when the faulty gateway device is connected to the remote server before the communication failure occurs;

[0017] After receiving the return message, the update gateway device sends the return message to the faulty gateway device;

[0018] When verifying that the first dynamic ID of the returned message is the dynamic ID stored in the faulty gateway device, the faulty gateway device sends the reported data to the replacement gateway device.

[0019] Optionally, replace the failed gateway device to establish a trusted connection with the remote server, including:

[0020] Replace the gateway device to send its own fingerprint information to the remote server;

[0021] After the remote server receives the fingerprint information, it uses a private conversion algorithm to process the fingerprint information to obtain a replacement gateway ID, stores the association between the fingerprint information and the replacement gateway ID in a data table, and returns the gateway ID to the replacement gateway device;

[0022] After receiving the replacement gateway ID, the replacement gateway device determines to establish a trusted connection with the remote server.

[0023] Optionally, replace the gateway device to send its own fingerprint information to the remote server, including:

[0024] Encrypting the fingerprint information by a first encryption method to obtain first encrypted information, and sending the first encrypted information to a remote server;

[0025] Before using the private conversion algorithm to process the fingerprint information to obtain the replacement gateway ID, the remote server uses the first decryption means matching the first encryption means to process the first encrypted information to obtain the decrypted fingerprint information;

[0026] Returning the changed gateway ID to the gateway device includes: using a second encryption method to obtain second encrypted information from the changed gateway ID, and sending the second encrypted information to the gateway device;

[0027] After receiving the second encrypted information, the gateway device uses a second decryption means matching the second encryption means to decrypt the second encrypted information to obtain a replacement gateway ID.

[0028] Optionally, before the faulty gateway device sends the buffered reported data to the replacement gateway device through the non-network interface, the method further includes:

[0029] The replacement gateway device symmetrically encrypts its own fingerprint information to obtain a first encrypted fingerprint and sends the first encrypted fingerprint to the faulty gateway device; wherein the first encrypted fingerprint is obtained by performing an encryption operation on a hardware encryption and decryption chip of the replacement gateway device;

[0030] When the faulty gateway device receives the first encrypted fingerprint and uses its own hardware encryption chip to decrypt it to obtain the fingerprint information of the updated gateway device, the buffered reported data is sent to the replacement gateway device through the non-network interface.

[0031] Optionally, before the faulty gateway device sends the buffered reported data to the replacement gateway device through the non-network interface, the method further includes:

[0032] The faulty gateway device symmetrically encrypts its own fingerprint information to obtain a second encrypted fingerprint and sends the second encrypted fingerprint to the replacement gateway device; wherein the second encrypted fingerprint is obtained by performing an encryption operation on a hardware encryption and decryption chip of the faulty gateway device;

[0033] After the encryption gateway device receives the second encrypted fingerprint and uses its own hardware encryption chip to decrypt and obtain the fingerprint information of the faulty gateway device, it receives the reporting data sent by the faulty gateway device.

[0034] Optionally, after the replacement gateway device forwards all reported data to the remote server and receives successful reception indication information replied by the remote server, the replacement gateway device generates prompt information.

[0035] Optionally, after the replacement gateway device receives the successful reception indication information, the successful reception indication information is sent to the faulty gateway device;

[0036] After receiving the success indication information, the faulty gateway device deletes the reporting data stored in the local buffer.

[0037] In the ecological environment monitoring system provided by the embodiment of the present disclosure, the gateway device can be connected through a non-network interface, and the temporarily stored reported data can be sent to the replacement gateway device through the non-network interface. The corresponding replacement gateway device can also be used as a relay device to forward the reported data to the remote server. In this way, the storage of the temporarily stored data of the faulty gateway device can be realized without manual data reading, thereby ensuring the security of the data. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the prior art, the following briefly introduces the drawings required for use in the embodiments or the prior art description. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative labor, including

[0040] Figure 1 is a structural diagram of an ecological environment quality monitoring system provided by an embodiment of the present disclosure;

[0041] Figure 2 is a flow chart of a method for implementing replacement gateway device verification in some embodiments;

[0042] Figure 3 is a flow chart of a method for implementing verification of replacing a gateway device in some other embodiments;

[0043] Figure 4 It is a flow chart of a method for replacing gateway device authentication provided by some embodiments. DETAILED DESCRIPTION

[0044] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments described herein, which are instead provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0045] The term "including" and its variations used in this document are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one other embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions of other terms will be given in the description below. In this document, relational terms such as "first" and "second" are merely used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0046] Figure 1 Schematic diagram of the structure of the ecological environment quality monitoring system provided by the embodiment of the present disclosure. Figure 1 As shown, the ecological environment quality monitoring system 100 provided in the embodiment of the present disclosure includes an environmental monitoring device 101, a gateway device 102 and a remote server 103.

[0047] The aforementioned environmental monitoring devices 101 and gateway devices 102 are both deployed as local devices at the environmental monitoring point. In a specific implementation, one environmental monitoring point can deploy multiple different types of environmental monitoring devices 101 and one gateway device 102. The monitoring device connection interface of the aforementioned gateway device 102 is connected to the data IO interface of each environmental monitoring device 101, and data transmission with each environmental monitoring device 101 is realized through a local communication link.

[0048] Each environmental monitoring device 101 can be connected in series with the gateway device 102 (that is, only one environmental monitoring device 101 is directly connected to the gateway device 102, and other environmental monitoring devices 101 communicate with the gateway device 102 through the aforementioned environmental monitoring device 101), or can be connected in parallel with the gateway device 102 (that is, each environmental monitoring device 101 is connected to the gateway device 102 through an independent monitoring device connection interface), which is not limited in the embodiments of the present disclosure. In some embodiments, while ensuring the security and reliability of data communication, the gateway device 102 and the environmental monitoring device 101 can also be connected using short-range wireless communication.

[0049] In the disclosed embodiment, the gateway device 102 does not have the function of directly controlling the environment monitoring device 101 , that is, the gateway device 102 does not have the monitoring device control software for directly controlling the environment monitoring device 101 installed therein.

[0050] The remote server 103 is a server that is not deployed at the environmental monitoring point, but is installed with the monitoring device control software. The remote server 103 can send control instructions to the environmental monitoring device 101 through network communication, and receive the reported data reported by the environmental monitoring device 101. In specific implementation, the remote server 103 is mostly deployed in the server room of the environmental supervision entity.

[0051] like Figure 1 As shown, in the embodiment of the present disclosure, the remote server 103 is not directly connected to the aforementioned environment monitoring device 101, but is indirectly connected to the environment monitoring device 101 through the gateway device 102. Specifically, the gateway device 102, as an intermediate communication device, forwards the control instructions issued by the remote server 103 to the corresponding environment monitoring device 101, and reports various reporting data output by the environment monitoring device 101 to the remote server 103.

[0052] In a specific implementation, when the network card device or interface in the gateway device that communicates with the remote server 103 is damaged and cannot send the reported data to the remote server, and can only buffer the reported data in the local cache, the forwarding and uploading of the reported data can be achieved through the embodiment of the present disclosure.

[0053] For convenience, the aforementioned network card device or the gateway device with a damaged interface is referred to as a faulty gateway device, and replacing the faulty gateway device is referred to as replacing the gateway device.

[0054] In a specific implementation, if a report message sent by a certain gateway device is not received for a certain set period of time (for example, 2 consecutive hours), it can be generally determined that the aforementioned gateway device is faulty, that is, a faulty gateway device has occurred. In this case, the equipment operation and maintenance personnel will go to the corresponding environmental monitoring point to perform on-site equipment maintenance and replace the faulty gateway device with a replacement gateway device.

[0055] After replacing the failed gateway device with the replacement gateway device (specifically, after connecting the network interface of the replacement gateway device to the communication network), the replacement gateway device can establish a trusted connection with the remote server based on the internal configuration data and firmware program. In addition, after replacing the failed gateway device with the replacement gateway device, the operation and maintenance personnel will also connect the failed gateway device with the non-network interface of the replacement gateway device, so that the failed gateway device sends the buffered report data to the replacement gateway device through the non-network interface; correspondingly, the replacement gateway device sends the report data to the remote server, so that the remote server obtains the environmental monitoring data during the network communication failure stage of the failed gateway device.

[0056] As analyzed above, in the ecological environment monitoring system provided by the embodiment of the present disclosure, the gateway device can be connected through a non-network interface, and the temporarily stored reported data can be sent to other gateway devices through the non-network interface. The corresponding other gateway devices can also act as relay devices to forward the reported data to the remote server. In this way, the storage of the temporarily stored data of the faulty gateway device can be realized without manual data reading, ensuring the security of the data.

[0057] In the specific implementation, the problem that the replacement gateway device is a hacked gateway device or an illegal gateway device may occur. In this case, the reporting data sent by the faulty gateway device to the replacement gateway device may be leaked. To solve this problem, it is necessary to verify that the replacement gateway device is a legally authenticated security network device.

[0058] Figure 2 1 is a flow chart of a method for implementing gateway device replacement verification in some embodiments. Figure 2 As shown, in some embodiments, the ecological environment monitoring system uses the following S110-S150 to enable the faulty gateway device to determine whether the replacement gateway device is a legal device.

[0059] S110: The faulty gateway device generates a verification request message and sends it to a replacement gateway device.

[0060] The verification request message is a message sent by the faulty gateway device to the remote server to verify whether the replacement of the gateway device is legal. The verification request message mentioned here can be a plaintext message or a ciphertext message, which is not limited in the embodiments of the present disclosure.

[0061] S120: After receiving the verification request message, the replacement gateway device sends the verification request message to the remote server.

[0062] S130: When the remote server receives the verification request message and determines that the replaced gateway device has been remotely verified, the remote server generates a return message based on the first dynamic ID and sends the return message to the replaced gateway device.

[0063] The first dynamic ID is a dynamic ID generated by the remote server and sent to the faulty gateway device when it is connected to the remote server before the communication failure of the faulty gateway device occurs. The first dynamic ID is an ID known only by the remote server and the faulty gateway device. It should be noted here that because the faulty gateway device has disconnected the network connection with the remote server, the remote server cannot obtain its heartbeat signal, so it does not use the first dynamic ID as a legally usable verification ID, but only stores the first dynamic ID as historical data. Even if other gateway devices obtain the first dynamic ID, they cannot forge and replace the faulty gateway device to access the network. Accordingly, the first dynamic ID can be transmitted in plain text or in encrypted text, which is not limited by the embodiments of the present disclosure.

[0064] S140: After receiving the return message, the replacement gateway device sends the return message to the faulty gateway device.

[0065] S150: After receiving the return message, the faulty gateway device verifies whether the first dynamic ID is the same as the locally stored dynamic ID.

[0066] After the faulty gateway device receives the return message, it verifies whether the first dynamic ID is the same as the locally stored dynamic ID. If they are the same, it indicates that the first dynamic ID is sent by the remote server, and the corresponding replacement gateway device has been authenticated by the remote server; at this time, the reported data can be sent to the replacement gateway device. If the first dynamic ID is different from the locally stored dynamic ID, it indicates that the received first dynamic ID is a fake dynamic ID, so the reported data will not be sent to the replacement gateway device.

[0067] Figure 3 1 is a flow chart of a method for implementing a replacement gateway device verification method in some other embodiments. Figure 3 As shown, in some embodiments, the ecological environment monitoring system uses the following S210-S240 to enable the faulty gateway device to determine whether the replacement gateway device is a legal device, and then determine whether to send the reported data to the replacement gateway device.

[0068] S210: The gateway device is replaced to send a verification request message to the remote server.

[0069] In the disclosed embodiment, the verification request message is actively generated by the replacement gateway device and sent to the remote server, rather than being actively generated by the faulty gateway device as in the previous embodiment.

[0070] S220: After the remote server receives the verification request message, a return message including the first dynamic ID is generated and sent to the remote server.

[0071] The first dynamic ID is a dynamic ID generated by the remote server and sent to the faulty gateway device when it was connected to the remote server before the communication failure of the faulty gateway device. The first dynamic ID is an ID known only by the remote server and the faulty gateway device. It should be noted here that because the faulty gateway device has disconnected the network connection with the remote server, the remote server cannot obtain its heartbeat signal, so it will not use the first dynamic ID as a legally usable verification ID, but only store the first dynamic ID as historical data. Even if other gateway devices obtain the first dynamic ID, they cannot forge and replace the faulty gateway device to access the network.

[0072] S230: After receiving the return message, the updated gateway device sends the return message to the faulty gateway device.

[0073] S240: The faulty gateway device verifies whether the first dynamic ID is the same as the dynamic ID stored in itself.

[0074] After the faulty gateway device receives the return message, it verifies whether the first dynamic ID is the same as the locally stored dynamic ID. If they are the same, it indicates that the first dynamic ID is sent by the remote server, and the corresponding replacement gateway device has been authenticated by the remote server; at this time, the reported data can be sent to the replacement gateway device. If the first dynamic ID is different from the locally stored dynamic ID, it indicates that the received first dynamic ID is a fake dynamic ID, so the reported data will not be sent to the replacement gateway device.

[0075] In a specific implementation, the faulty gateway device will generate a reporting message based on the reported data, and then send the reporting message to the replacement gateway device.

[0076] In actual applications, the faulty gateway device may be an illegal device, but it may be disguised as a legitimate device and verified by a remote server. In this case, in order to ensure the security of the report message, the faulty gateway device first uses the target encryption strategy to encrypt the report data to obtain encrypted report data; then the encrypted report data is formed into a report message and sent to the replacement gateway device.

[0077] The aforementioned target encryption strategy is an encryption strategy for which only the remote server has a corresponding decryption strategy, or an encryption strategy for which only the remote server and the faulty gateway device have a corresponding decryption strategy. For example, the faulty server may use the public key of the remote server to encrypt the reported data, in which case only the remote server can decrypt the encrypted data. For another example, the faulty server may use a symmetric encryption key to encrypt the reported data, and the aforementioned symmetric encryption key is only known by the faulty gateway device and the remote server.

[0078] In the above solution, the above verification operation can only be performed after the gateway device is replaced and a trusted connection with the remote server is established. Figure 4 1 is a flow chart of a method for replacing gateway device authentication provided by some embodiments. Figure 4 As shown, the ecological environment monitoring system uses the following S310-S330 to implement verification of the replacement gateway device: S310: The replacement gateway device sends its own fingerprint information to the remote server.

[0079] Fingerprint information is information that characterizes the identity of the replaced gateway device. In a specific implementation, the fingerprint information may be a unique identifier such as the MAC address of the replaced gateway device, or may be identification information generated using the aforementioned unique identifier, or may include temporarily assigned identification information such as a dynamic IP address. In a specific implementation, the replaced gateway device may generate fingerprint information based on the aforementioned MAC address by executing a fingerprint generation program.

[0080] After the fingerprint information is generated, the replacement gateway device sends the fingerprint information to the server. In a specific implementation, in order to ensure the security of the fingerprint information, the replacement gateway device uses an encryption algorithm (first encryption means) to encrypt the fingerprint information to obtain the encrypted fingerprint information. In a specific implementation, the replacement gateway device can use an asymmetric encryption algorithm to encrypt the fingerprint information, that is, use the public key of the remote server to encrypt the fingerprint information.

[0081] After receiving the fingerprint information, the remote server executes S320.

[0082] S320: Use a private conversion algorithm to process the fingerprint information to obtain a replacement gateway ID, store the association between the fingerprint information and the replacement gateway ID in a data table, and return the gateway ID to the replacement gateway device.

[0083] The private conversion algorithm is a conversion algorithm that only the remote server has, which means that only the remote server can determine the corresponding gateway ID based on the fingerprint information, while other devices cannot determine the gateway ID based on the fingerprint information. After the remote server obtains the gateway ID, it will store the gateway ID and the corresponding fingerprint information in the relational data table for the purpose of verifying the legitimacy of subsequent reported messages.

[0084] As analyzed above, when the gateway device is replaced to encrypt the fingerprint information to obtain the encrypted fingerprint information, the remote server first decrypts the encrypted fingerprint information (specifically, uses the first decryption method corresponding to the first encryption method to decrypt), obtains the decrypted fingerprint information, and then obtains the replacement gateway ID based on the decrypted fingerprint information. Corresponding to the above-mentioned use of the public key of the remote server to encrypt the fingerprint information, the remote server uses its own private key to decrypt the encrypted fingerprint information.

[0085] Similarly, in order to ensure the security of replacing the gateway ID, in the specific implementation, the remote server encrypts the replacement gateway ID (using the second encryption means), and then sends the encrypted replacement gateway ID to the replacement gateway device. For example, the gateway ID is encrypted using the public key of the replacement gateway device (using the second decryption means corresponding to the second encryption means), and then the encrypted ID is sent to the replacement gateway device.

[0086] After the replacement gateway device receives the replacement gateway ID, the replacement gateway device executes S330 .

[0087] S330: After receiving the replacement gateway ID, the replacement gateway device determines to establish a trusted connection with the remote server.

[0088] Based on the aforementioned replacement gateway ID, the replacement gateway device can determine a trusted connection with the remote server. Specifically, the replacement gateway device establishes a trusted connection with the remote server by generating a report message based on the replacement gateway ID, fingerprint information, and the report data sent by the environmental monitoring device, and then sending the report message to the remote server.

[0089] As mentioned above, the remote server uses a private conversion algorithm to process the fingerprint information to obtain the replacement gateway ID. In a specific implementation, the remote server can use the following S321-S322 to obtain the replacement gateway ID.

[0090] S321: Process the fingerprint information based on a private conversion algorithm to obtain a random private key.

[0091] S322: Generate a corresponding encrypted public key based on the random private key, and use the encrypted public key as the replacement gateway ID.

[0092] In a specific implementation, the fingerprint information is processed based on a private conversion algorithm to obtain a random key, and the fingerprint information can be used to generate a random number based on a random number generation algorithm to obtain a private key. Alternatively, the remote server assigns a random number to the fingerprint information as the corresponding random private key. After obtaining the random private key, the remote server can process the random private key according to the adopted asymmetric encryption algorithm to obtain an encrypted public key, and use the encrypted public key as a replacement gateway ID.

[0093] In the case where the aforementioned encryption public key is used as the replacement gateway ID, after the replacement gateway device obtains the aforementioned replacement gateway ID, the replacement gateway ID encrypts the fingerprint information and the received forwarding report data based on the replacement gateway ID to obtain an encrypted message, and adds the fingerprint information to the header of the encrypted message; then the message is used as a report message to send the encrypted message to the remote server. In other words, the replacement gateway ID is used as the encryption public key to encrypt the fingerprint information and the report message. In this case, only the remote server holding the random private key can decrypt the encrypted message.

[0094] As mentioned above, after the replacement gateway device is connected to the faulty gateway device through a non-network interface, data can be transmitted between them. In practical applications, in order to ensure data security, it is necessary to prevent other devices disguised as gateway devices from establishing a connection with the faulty gateway device and obtaining data. Before the aforementioned reported data is transmitted between the two, the replacement gateway device needs to be authenticated. Specifically, it includes the following S410-S420.

[0095] S410: The replaced gateway device symmetrically encrypts its own fingerprint information to obtain a first encrypted fingerprint and sends the first encrypted fingerprint to the faulty gateway device.

[0096] S420: The faulty gateway device receives the first encrypted fingerprint and uses its own hardware encryption chip to decrypt it to obtain fingerprint information of the updated gateway device, and sends the buffered reported data to the replacement gateway device through the non-network interface.

[0097] The aforementioned first encrypted fingerprint is obtained by performing an encryption operation on the hardware encryption and decryption chip of the replaced gateway device. Similarly, the faulty gateway device needs to use the decryption program on its own hardware encryption chip to decrypt the first encrypted fingerprint to obtain the corresponding decryption information. Only when the aforementioned hardware encryption chip is cracked can the aforementioned verification method be cracked. However, it is very difficult to crack the hardware encryption chip, so the aforementioned verification method can ensure that the replacement gateway device is authenticated by the faulty gateway device.

[0098] Similar to the above method, replacing the gateway device can also realize the authentication of the faulty gateway device, and then the report message including the report data forwarded by the gateway device will be received. Specifically, it includes the following S430-S440.

[0099] S430: The faulty gateway device symmetrically encrypts its own fingerprint information to obtain a second encrypted fingerprint and sends the second encrypted fingerprint to a replacement gateway device.

[0100] S440: After the encryption gateway device receives the second encrypted fingerprint and uses its own hardware encryption chip to decrypt to obtain the fingerprint information of the faulty gateway device, it receives the reporting data sent by the faulty gateway device.

[0101] In a specific implementation, through the method described above, the faulty gateway device can successfully send the reported data to the remote server. After completing the sending of all reported data, the faulty gateway device will send a message including a data sending completion mark to the replacement gateway device; the corresponding replacement gateway device will forward the aforementioned message including the data sending completion mark to the remote server. After the remote server determines that the reported data has been received, it will generate a successful reception indication message and send it to the replacement gateway device. After receiving the success indication message, the replacement gateway device generates a corresponding prompt message through its own hardware device, and prompts that the data has been transmitted and can disconnect the connection with the faulty gateway device.

[0102] In some embodiments, after receiving the success prompt information, the replacement gateway device also sends the success prompt information to the faulty gateway device. After receiving the success indication information, the faulty gateway device deletes the reported data stored in the local buffer to prevent other personnel from obtaining the aforementioned data later.

[0103] The foregoing text mentions the replacement of the communication connection between the gateway device and the remote server. In the specific implementation, in order to achieve the decoupling of the two, the replacement gateway device and the remote server can adopt a topic-subscription mechanism, and the proxy service can be used to realize the data transmission. Specifically, the replacement gateway device publishes the corresponding reported data to the corresponding publishing topic, and the remote server obtains the reported data by subscribing to the corresponding topic; similarly, the remote server publishes the corresponding instructions or data to its own publishing topic, and the remote server obtains the aforementioned instructions or data by subscribing to the corresponding topic. The above is only a specific implementation method of the present disclosure, so that those skilled in the art can understand or implement the present disclosure. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to these embodiments herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. An ecological environment monitoring system, characterized in that: It includes a gateway device deployed at the monitoring point and locally connected to the data interface of each environmental monitoring device, and a remote server connected to the gateway device through a communication network; When the network interface between the faulty gateway device and the remote server fails and cannot upload the reported data sent by the environmental monitoring device, the replacement gateway device replaces the faulty gateway device to establish a trusted connection with the remote server, and after the faulty gateway device is connected to the non-network interface of the replacement gateway device, the faulty gateway device sends the buffered reported data to the replacement gateway device through the non-network interface, and the replacement gateway device forwards the reported data to the remote server.

2. The monitoring system according to claim 1, characterized in that: Before the faulty gateway device forwards the buffered reported data to the replacement gateway device through the non-network interface, the method further includes: The faulty gateway device generates a verification request message and sends it to the replacement gateway device; After receiving the verification request message, the replacement gateway device sends the verification request message to the remote server; When the remote server receives the verification request message and determines that the replacement gateway device has been remotely verified, it generates a return message based on the first dynamic ID and sends the return message to the replacement gateway device; the first dynamic ID is a dynamic ID generated by the remote server and sent to the faulty gateway device when the faulty gateway device is connected to the remote server before the communication failure occurs; After receiving the return message, the replacement gateway device sends the return message to the faulty gateway device; After receiving the return message, the faulty gateway device verifies whether the first dynamic ID is the same as the locally stored dynamic ID, and sends the reported data to the replacement gateway device if the first dynamic ID is the same as the locally stored dynamic ID.

3. The monitoring system according to claim 2, characterized in that: Before sending the reported data to the replacement gateway device, the faulty gateway device encrypts the reported data using a target encryption strategy to obtain encrypted reported data; sending the reported data to the replacement gateway device, specifically: sending the encrypted reported data to the replacement gateway device; The target encryption policy is an encryption policy for which only the remote server has a corresponding decryption policy, or an encryption policy for which only the remote server and the faulty gateway device have a corresponding decryption policy.

4. The monitoring system according to claim 1, characterized in that: Before the faulty gateway device forwards the buffered reported data to the replacement gateway device through the non-network interface, the method further includes: Replace the gateway device to send a verification request message to the remote server; After the remote server receives the verification request message, it generates a return message including a first dynamic ID and sends it to the remote server; the first dynamic ID is a dynamic ID generated by the remote server and sent to the faulty gateway device when the faulty gateway device is connected to the remote server before the communication failure occurs; After receiving the return message, the update gateway device sends the return message to the faulty gateway device; When verifying that the first dynamic ID of the returned message is the dynamic ID stored in the faulty gateway device, the faulty gateway device sends the reporting data to the replacement gateway device.

5. The monitoring system according to any one of claims 1 to 4, characterized in that: Replace the gateway device to replace the faulty gateway device and establish a trusted connection with the remote server, including: Replace the gateway device to send its own fingerprint information to the remote server; After the remote server receives the fingerprint information, it uses a private conversion algorithm to process the fingerprint information to obtain a replacement gateway ID, stores the association between the fingerprint information and the replacement gateway ID in a data table, and returns the gateway ID to the replacement gateway device; After receiving the replacement gateway ID, the replacement gateway device determines to establish a trusted connection with the remote server.

6. The monitoring system according to claim 5, characterized in that: Replace the gateway device to send its own fingerprint information to the remote server, including: Encrypting the fingerprint information by a first encryption method to obtain first encrypted information, and sending the first encrypted information to a remote server; Before using the private conversion algorithm to process the fingerprint information to obtain the replacement gateway ID, the remote server uses the first decryption means matching the first encryption means to process the first encrypted information to obtain the decrypted fingerprint information; Returning the changed gateway ID to the gateway device includes: using a second encryption method to obtain second encrypted information from the changed gateway ID, and sending the second encrypted information to the gateway device; After receiving the second encrypted information, the gateway device uses a second decryption means matching the second encryption means to decrypt the second encrypted information to obtain a replacement gateway ID.

7. The monitoring system according to any one of claims 1 to 4, characterized in that: Before the faulty gateway device sends the buffered reported data to the replacement gateway device through the non-network interface, the method further includes: The replacement gateway device symmetrically encrypts its own fingerprint information to obtain a first encrypted fingerprint and sends the first encrypted fingerprint to the faulty gateway device; wherein the first encrypted fingerprint is obtained by performing an encryption operation on a hardware encryption and decryption chip of the replacement gateway device; When the faulty gateway device receives the first encrypted fingerprint and uses its own hardware encryption chip to decrypt it to obtain the fingerprint information of the updated gateway device, the buffered reported data is sent to the replacement gateway device through the non-network interface.

8. The monitoring system according to claim 7, characterized in that: Before the faulty gateway device sends the buffered reported data to the replacement gateway device through the non-network interface, the method further includes: The faulty gateway device symmetrically encrypts its own fingerprint information to obtain a second encrypted fingerprint and sends the second encrypted fingerprint to the replacement gateway device; wherein the second encrypted fingerprint is obtained by performing an encryption operation on a hardware encryption and decryption chip of the faulty gateway device; After the encryption gateway device receives the second encrypted fingerprint and uses its own hardware encryption chip to decrypt and obtain the fingerprint information of the faulty gateway device, it receives the reporting data sent by the faulty gateway device.

9. The monitoring system according to any one of claims 1 to 4, characterized in that: After the replacement gateway device forwards all reported data to the remote server and receives the successful reception indication information replied by the remote server, the replacement gateway device generates prompt information.

10. The monitoring system according to claim 9, characterized in that: After the replacement gateway device receives the successful reception indication information, the successful reception indication information is sent to the faulty gateway device; After receiving the success indication information, the faulty gateway device deletes the reporting data stored in the local buffer.

Images