Device collection is not always online continuously. After the network is interrupted, only saving the last state will lose the production process; re-uploading indiscriminately after the connection is restored may cause repeated counting. The collection end and the server end need to jointly define the supplementary transmission rules.

How to arrange recording and operation

Each piece of data has a device number, collection time and traceable record identification. The collection end saves the data to be sent according to the allowed capacity, and the server removes duplication through identification and records the reception time at the same time. Expired data and real-time data are processed separately to avoid historical downtime events from overwriting the current operating status.

The remaining space of the cache should be monitorable and prompt the maintenance personnel when it is close to the capacity limit. The record to be uploaded must be removed only after receiving clear confirmation from the collection end. Otherwise, network interruptions may cause hard-to-find losses. For pulse counting, it is also necessary to agree whether the cumulative value or the interval increment is uploaded, which directly determines the statistical algorithm during the disconnection period. Supplementary transmission after the connection is restored can be performed in batches, and real-time data is retained in an independent channel to avoid a large number of historical records that make the current status unable to be refreshed for a long time.

Specific scenarios that need to be checked

The test can temporarily cut off the connection, allow the device side to continue to generate records, and then restore the network to check the number and time sequence. Device clock skew and cache exhaustion should also be simulated. The dashboard displays the data update time, so managers know whether they are seeing the current status or the historical status to be uploaded.