A digital-twin-based aquaculture monitoring state visualization system

Abstract

The application relates to the technical field of emerging software and new information technology services, in particular to a breeding monitoring state visualization system based on digital twinning, which comprises the following steps: a registration module registers the area positions of sensors, a camera terminal and a collection gateway, reports intervals, waiting time lengths, retransmission upper limits and queue upper limits; a judgment module divides current effective data, delayed effective data and invalid data according to the time of generation, the time of reception, the number of retransmissions and the length of the queue; a window module generates a communication time sequence effective window and adds a delay label; a calibration module generates a regional state object and a node state object; and a display module organizes display records. In the application, through node constraint, time sequence verification, effectiveness grading and window screening, the lag data and the real-time data are distinguished before display, the interference of old data on judgment and synchronization is reduced, immediate sampling is triggered when there is a gap in key environmental data and the heartbeat is effective, and the visualization reliability is improved.

Description

Technical Field

[0001] This invention relates to the field of emerging software and new information technology service technology, and in particular to a visualization system for monitoring the status of aquaculture based on digital twins. Background Technology

[0002] The emerging software and new information technology service technology fields involve information technology services that use software systems to model, calculate, store, and display object status, process data, and display data. Among these, a traditional aquaculture monitoring status visualization system refers to a system where a server receives environmental data, equipment status data, and aquaculture object records uploaded from sensors, camera terminals, or data acquisition gateways in the aquaculture farm. After writing the data into a database, a computer program generates status objects, monitoring pages, and visualization layers according to a preset model, and displays the aquaculture area, equipment nodes, and status parameters through a client.

[0003] Traditional aquaculture monitoring and visualization systems typically write data uploaded from sensors, camera terminals, or data acquisition gateways into a unified database and then generate status pages according to a preset model. Data arrival time, forwarding wait time, retransmission count, and gateway queue congestion lack unified constraints in the display link. Clients are prone to mixing outdated data with real-time data, environmental anomaly judgments are interfered with by old data, the synchronization relationship between the online status of device nodes and the regional status is unclear, critical environmental data gaps are difficult to expose in a timely manner, and on-site handling is delayed. Summary of the Invention

[0004] The purpose of this invention is to overcome the shortcomings of existing technologies and propose a digital twin-based visualization system for monitoring the status of aquaculture.

[0005] To achieve the above objectives, the present invention adopts the following technical solution: a digital twin-based aquaculture monitoring status visualization system, the system comprising: The registration module is used to register the breeding area, node location, preset reporting interval, allowed waiting time, maximum number of retransmissions and maximum queue length of environmental sensors, camera terminals and data acquisition gateways, and output node registration records; The determination module, connected to the registration module, is used to receive data packets containing the data generation time, gateway forwarding time, server receiving time, number of data packet retransmissions, and gateway waiting queue length. Based on the node registration records, it compares the data arrival delay time, the number of data packet retransmissions, and the gateway waiting queue length, and outputs the currently valid data, delayed valid data, or invalid data. A window module, connected to the determination module, is used to generate a communication timing effective window based on the data generation time and the preset reporting interval, and to attach a delay mark to the delayed effective data. The calibration module, connected to the window module, is used to filter data falling into the effective window of the communication timing according to the time displayed by the client, generate aquaculture area status objects and equipment node status objects, and generate an immediate sampling command when there is a gap in critical environmental data and the heartbeat is valid. The display module, connected to the calibration module, is used to organize client-side display records according to the location of the breeding area, node location, and valid data category.

[0006] As a further aspect of the present invention, the registration module includes a region binding submodule, a node positioning submodule, a parameter configuration submodule, and a record output submodule; The region binding submodule receives the device identifiers of the environmental sensor, the camera terminal, and the data acquisition gateway, reads the aquaculture area number and the device affiliation relationship, establishes a binding relationship between the device identifiers and the aquaculture area number within the same aquaculture area, and generates a region affiliation result. The node positioning submodule obtains the region attribution result and node location, writes the node location into the node location field of the corresponding device identifier, and generates the node positioning result; The parameter configuration submodule obtains the node location result, preset reporting interval, allowed waiting time, maximum number of retransmissions and maximum queue length, writes the above parameters into the registration field of the corresponding device identifier, and generates the registration parameter result; The record output submodule generates node registration records based on the registration parameter results.

[0007] As a further embodiment of the present invention, the determination module includes a lag calculation submodule, a count comparison submodule, a queue comparison submodule, and a category output submodule; The lag calculation submodule receives a data packet containing the data generation time, gateway forwarding time, and server reception time. Based on the time difference between the server reception time and the data generation time, it determines the data arrival lag time and sends the data arrival lag time to the category output submodule. The retransmission comparison submodule obtains the number of retransmissions in the data packet and the upper limit of the retransmission count in the node registration record, compares the two, and outputs the retransmission comparison result. The queue comparison submodule obtains the gateway queue length to be sent in the data packet and the upper limit of the queue length in the node registration record, compares the two and outputs the queue comparison result. The category output submodule outputs currently valid data, delayed valid data, or invalid data based on the data arrival delay time, the retransmission comparison result, and the queue comparison result.

[0008] As a further embodiment of the present invention, the window module includes a reference determination submodule, a periodic alignment submodule, a boundary generation submodule, and a marker attachment submodule; The baseline determination submodule receives currently valid data or delayed valid data, reads the data generation time and the preset reporting interval in the node registration record, determines the data generation time as the window baseline time, and generates the baseline time result. The periodic alignment submodule obtains the reference time result and the preset reporting interval, performs periodic merging on the window reference time according to the preset reporting interval, determines the starting boundary of the corresponding communication period, and generates the periodic alignment result. The boundary generation submodule determines the start and end boundaries of the effective communication timing window based on the periodic alignment result and the preset reporting interval, and outputs the effective communication timing window. When the tag attachment submodule receives delayed valid data, it writes a delay tag to the category field of the delayed valid data.

[0009] As a further embodiment of the present invention, the calibration module includes a display time matching submodule, a window filtering submodule, a status generation submodule, and an instruction triggering submodule; The display time matching submodule obtains the client display time and the start and end boundaries of the effective window of the communication timing, compares the client display time with the start and end boundaries for time assignment, and generates a display assignment result. The window filtering submodule obtains the display attribution result, the current valid data, and the delayed valid data with delay markers, filters the data that falls into the communication timing valid window, and generates window valid data; The status generation submodule generates aquaculture area status objects and equipment node status objects based on the valid data in the window; The instruction triggering submodule generates an immediate sampling instruction when there is a gap in critical environmental data and the heartbeat is valid.

[0010] As a further embodiment of the present invention, the display module includes a region mapping submodule, a node sorting submodule, a category arrangement submodule, and a record generation submodule; The region mapping submodule obtains the breeding region number and breeding region location from the breeding region status object, establishes a region display mapping relationship between the breeding region number and the breeding region location, and generates a region display index. The node sorting submodule obtains the device identifier and node position from the device node status object, writes the node position into the node display sequence of the corresponding breeding area according to the area display index, and generates the node sorting result. The category arrangement submodule obtains the node sorting result and the valid data category, writes the valid data category into the category display field of the corresponding device identifier, and generates the category arrangement result; The record generation submodule generates client-side display records based on the category arrangement results.

[0011] As a further embodiment of the present invention, the determination module is configured with a time verification unit; The timing verification unit obtains the data generation time, gateway forwarding time, and server receiving time from the data packet, and performs timing verification according to the order relationship that the data generation time is not later than the gateway forwarding time and the gateway forwarding time is not later than the server receiving time. When any time does not meet the order relationship, a timing abnormality mark is generated, and the data packet with the timing abnormality mark is handed over to the determination module to be determined as invalid data.

[0012] As a further embodiment of the present invention, the determination module is configured with a node matching unit; The node matching unit obtains the device identifier, acquisition gateway identifier, and aquaculture area number carried in the data packet, matches the device identifier with the registered device identifier in the node registration record, and matches the acquisition gateway identifier with the registered gateway identifier in the node registration record. When both the device identifier and the acquisition gateway identifier match and the aquaculture area number is consistent, a judgment status is output; otherwise, a source mismatch status is output and the corresponding data packet is identified as invalid data.

[0013] As a further aspect of the present invention, the state generation submodule specifically comprises: Obtain the device identifier, breeding area number, node position, data validity category and environmental value fields from the valid data of the window. Write the environmental value field corresponding to the same breeding area number into the breeding area status cache according to the node position, and write the data validity category corresponding to the same device identifier into the device node status cache. When there is current valid data and delayed valid data in the same communication time sequence valid window, use the current valid data as the main display value and retain the delay mark to generate breeding area status object and device node status object. The aquaculture area status object and the device node status object are each configured with a status update time field; After writing the main display value, the status generation submodule writes the client display time into the status update time field. When the data generation time of the subsequent window's valid data falls within the same communication timing window and the server's receiving time is later than the server's receiving time of the written data, the written data is replaced with the subsequent window's valid data, and the status update time field is refreshed.

[0014] As a further aspect of the present invention, the category arrangement submodule specifically comprises: Obtain the data validity categories corresponding to the current valid data, delayed valid data with delay markers, and failed data; associate the data validity categories with the device identifier; and determine the category writing position according to the breeding area location and node location. When the same device identifier corresponds to multiple data validity categories, determine the main category value of the category display field according to the order of the current valid data, delayed valid data, and failed data, and generate the category arrangement result. The category display field specifically includes: The category arrangement submodule, after determining the main category value, writes the currently valid data into the main category field, writes the delay flag of the delayed valid data into the delay flag field, and writes the failure reason corresponding to the failed data into the failure flag field, thereby generating a category display field record.

[0015] The working principle and advantages of this invention are as follows: In this invention, the breeding area, node location, reporting rhythm, waiting threshold, retransmission boundary, and queue boundary are defined by node registration records. The timeliness of data is then verified by the data generation time, forwarding time, receiving time, retransmission status, and pending queue. This ensures that real-time data, delayed data, and invalid data are separated before being displayed. The effective window of communication timing constrains the range of data that can participate in modeling at the client display time. Delayed data carries a marker to participate in status generation. Critical environmental data gaps are combined with heartbeat validity to trigger immediate sampling, ensuring that the regional status, node status, and visualization records are consistent in time, reducing the misleading effect of old data, and improving the reliability of anomaly identification and on-site scheduling. Attached Figure Description

[0016] Figure 1 This is a flowchart of the visualization process for monitoring aquaculture status in this invention. Figure 2 This is a schematic diagram illustrating the structure and data interaction effect of the aquaculture monitoring system of the present invention; Figure 3 This is a schematic diagram illustrating the effectiveness of the data valid category determination method in this invention. Figure 4 This is a schematic diagram illustrating the effective window for communication timing and the calibration effect of the present invention; Figure 5 This is a schematic diagram illustrating the digital twin status display effect on the client side of this invention. Detailed Implementation

[0017] The technical solution of the present invention will now be described with reference to the accompanying drawings.

[0018] In embodiments of the present invention, words such as "exemplarily," "for example," etc., are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" in the present invention should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word "exemplary" is intended to present the concept in a concrete manner. Furthermore, in embodiments of the present invention, the meaning expressed by "and / or" can be both, or either one.

[0019] Example Please see Figures 1 to 5 This embodiment provides a digital twin-based aquaculture monitoring status visualization system. In practical applications, for example, during the continuous operation of the aquaculture farm digital twin monitoring platform, environmental sensors collect environmental data such as temperature, humidity, gas concentration, and water status in the aquaculture area. The camera terminal collects image or video status data of the aquaculture area. The acquisition gateway undertakes the forwarding of device-side messages and the management of the queue to be sent. The server side forms digital twin display data. The client presents the device operating status and data validity category according to the location of the aquaculture area and node. The system includes a registration module, a judgment module, a window module, a calibration module, and a display module.

[0020] The registration module is used to register the breeding area, node location, preset reporting interval, allowed waiting time, maximum retransmission count, and maximum queue length of environmental sensors, camera terminals, and data acquisition gateways, and outputs node registration records. The node registration record is a data object within the system used to describe the legal ownership, communication configuration, and display location of the equipment. It consists of a device identifier, breeding area number, registration gateway identifier, node location field, preset reporting interval field, allowed waiting time field, maximum retransmission count field, maximum queue length field, and record status field. The device identifier comes from the factory identifier or platform-assigned identifier of the environmental sensors and camera terminals; the registration gateway identifier comes from the gateway identity information submitted when the data acquisition gateway connects to the platform; the breeding area number comes from the digital twin space management data of the breeding farm; and the node location comes from the equipment installation registration or on-site maintenance data.

[0021] The registration module does not handle data validity category determination, nor does it generate client display records. Its output serves only as the basic configuration for calls to the judgment module, window module, calibration module, and display module. Preset reporting intervals, allowed waiting time, maximum retransmission counts, and maximum queue length are all stored as configurable fields in the node registration record. Field boundaries are derived from device communication protocol configurations, gateway forwarding policies, and farm operation and maintenance rules. Field updates are triggered by device access configuration, maintenance changes, or regional adjustments. The registration module synchronously generates a registration status when writing records. The registration status indicates whether a record is completed, pending completion, or deactivated. Subsequent modules only access completed and deactivated records.

[0022] The region binding submodule receives device identifiers from environmental sensors, camera terminals, and data acquisition gateways. It reads the aquaculture region number and the device affiliation relationship, establishes a binding relationship between device identifiers and aquaculture region numbers within the same aquaculture region, and generates a region affiliation result. The region affiliation result is an affiliation data object between the device identifier and the aquaculture region number, carrying the aquaculture region to which the device belongs, the device access source, and the binding status. The data received by this submodule comes from the device access registration table, the aquaculture region management table, and the gateway access table. During processing, it first checks whether the device identifier already exists within the platform's registration range, then checks whether the device affiliation relationship points to a valid aquaculture region. If a device identifier is duplicated, the confirmed binding status is retained and the duplicate source is recorded. If a device identifier cannot match an aquaculture region, it is written to a pending completion status and does not proceed to subsequent node positioning processing.

[0023] The region binding submodule outputs the region attribution result and transmits it to the node positioning submodule. The binding status in the region attribution result is used to limit the matching range of subsequent data packet sources, preventing unregistered devices or cross-regional gateway data from entering the status display link. The binding relationship between the acquisition gateway and environmental sensors and camera terminals in the same region serves as the basis for the subsequent judgment module to verify the acquisition gateway identifier.

[0024] The node positioning submodule acquires the area attribution result and node location, writes the node location into the node location field of the corresponding device identifier, and generates the node positioning result. The node location is a positioning field used within the digital twin aquaculture area to determine the device's display location and status aggregation location. Its data comes from device installation location records, aquaculture area spatial archives, or positioning data submitted by the maintenance terminal. The node location is not used to represent specific coordinate value examples, but rather to indicate the device's display attribution point, monitoring coverage point, and status landing point in the digital twin space of the aquaculture area.

[0025] When processing area attribution results, the node positioning submodule first confirms that the binding status is locatable, and then reads the node location corresponding to the device identifier. If a node location is missing, the node positioning result is written to a pending confirmation status, and a location status that cannot be directly displayed is passed to the record output submodule; the subsequent display module will not add the device to the node display sequence. When the node location does not match the aquaculture area number, the node positioning submodule retains the device identifier and the source of the conflict, and outputs the abnormal location status for platform maintenance, but does not rewrite the already confirmed area binding results.

[0026] The parameter configuration submodule acquires node location results, preset reporting intervals, allowed waiting time, maximum retransmission count, and maximum queue length. It then writes these parameters into the registration field of the corresponding device identifier, generating the registration parameter result. The preset reporting interval field indicates the periodic reporting rules for device-side messages; the allowed waiting time field indicates the boundary for the server to accommodate communication lag when receiving data; the maximum retransmission count field indicates the configuration boundary for allowed retransmissions of data packets in the communication link; and the maximum queue length field indicates the configuration boundary for the collection gateway's pending-send queue to enter congestion judgment. All of these fields are derived from device protocol configuration, gateway queue policies, or platform operation and maintenance configurations, and specific numerical examples are not included in the implementation process.

[0027] The parameter configuration submodule first uses the device identifier from the node location result as an index, and then writes each configuration field into the same registration field set. If a configuration field is missing, the registration parameter result is marked as configuration to be completed, and the obtained fields are retained in the registration cache. The subsequent judgment module does not perform a valid category output for the data packet of that device, but instead transfers the data packet to the source confirmation processing link. If the configuration field format is inconsistent with the platform field specification, the parameter configuration submodule retains the original field source and generates a configuration exception state to avoid abnormal configuration affecting the generation of the effective window for communication timing.

[0028] The record output submodule generates node registration records based on the registration parameter results. These records are written to the system registration storage area and provided to the judgment module for source matching and valid category determination, to the window module for determining the effective communication timing window, and to the display module for organizing the location of the breeding area and nodes. When generating node registration records, the record output submodule simultaneously writes the record version status, record effectiveness status, and change source status. The record version status distinguishes newly written records from maintenance change records, the record effectiveness status determines whether subsequent data packets can enter the judgment link, and the change source status traces the maintenance path of the registration fields.

[0029] The output module also handles registration gaps during the startup phase. When devices are first connected to the system, devices that have completed area binding but not node positioning are kept in the registration cache and their records are not displayed on the client. Devices that have completed node positioning but lack communication configuration enter a pending configuration state and do not trigger the generation of a communication validity window. The determination module only reads the node registration record after all fields of the registration record have a callable state.

[0030] The judgment module, connected to the registration module, receives data packets containing the data generation time, gateway forwarding time, server reception time, number of data packet retransmissions, and gateway queue length. Based on node registration records, it compares data arrival lag time, data packet retransmission count, and gateway queue length, outputting currently valid data, delayed valid data, or invalid data. The data packet is a communication message object forwarded from the acquisition gateway to the server, carrying the device identifier, acquisition gateway identifier, aquaculture area number, environmental value field, image status field, data generation time, gateway forwarding time, server reception time, number of data packet retransmissions, and gateway queue length. Currently valid data represents data objects with matching sources, normal timing, and communication status meeting the current display requirements; delayed valid data represents data objects with matching sources, normal timing, but with a delayed arrival status; invalid data represents data objects whose source, timing, or communication status does not meet the requirements for entering the state generation link.

[0031] The determination module first receives data packets and reads node registration records, then performs time verification, node matching, lag identification, retransmission status comparison, queue status comparison, and category output. The determination module does not directly generate a valid communication timing window, nor does it rewrite the client display records; its output data valid categories are passed to the window module and the display module. When a data packet is missing a necessary field, the determination module generates a reason for the missing field and marks the data packet as invalid. When a data packet arrives repeatedly, the determination module forms a duplicate identification object based on the device identifier, data generation time, gateway forwarding time, and server reception time, retains traceable records, and hands the duplicate records over to the category output submodule for processing according to the server's reception order.

[0032] Timing Verification Unit: This unit acquires the data generation time, gateway forwarding time, and server reception time from the data packet. It performs timing verification according to the order that the data generation time is no later than the gateway forwarding time, and the gateway forwarding time is no later than the server reception time. If any time does not meet the order requirement, a timing anomaly flag is generated, and the data packet with the timing anomaly flag is handed over to the judgment module for identification as invalid data. The data generation time comes from the message header of the environmental sensor or camera terminal acquisition side; the gateway forwarding time comes from the forwarding field written when the acquisition gateway forwards the message; and the server reception time comes from the receive field written when the server access interface receives the message.

[0033] The timing verification unit performs the same sequential verification during the startup and communication recovery phases. If a device cold start causes timing gaps in the data, the data packet enters the missing field failure link. If gateway cache retransmission causes the server's received timing to be later than the original acquisition timing, the data packet is not invalidated by the retransmission itself, but continues to enter the lag calculation submodule. The subsequent category output submodule, combined with the allowed waiting time field, determines the valid category. The timing anomaly flag is written as the failure cause into the failure data and passed to the failure flag field of the display module.

[0034] Node matching unit: This unit acquires the device identifier, data acquisition gateway identifier, and aquaculture area number carried in the data packet. It matches the device identifier with the registered device identifier in the node registration record, and also matches the data acquisition gateway identifier with the registered gateway identifier in the node registration record. If both the device identifier and data acquisition gateway identifier match, and the aquaculture area number is consistent, it outputs a "determinable" status. Otherwise, it outputs a "source mismatch" status and identifies the corresponding data packet as invalid. Device identifier matching confirms that the data originates from a registered environmental sensor or camera terminal; data acquisition gateway identifier matching confirms that the data is forwarded via a registered link; and the consistent aquaculture area number confirms that the data has not been mixed into other aquaculture areas.

[0035] When the node matching unit discovers that a device identifier exists but the gateway identifier is inconsistent, it does not hand the data packet over to the delayed calculation submodule. Instead, it generates a failure reason for gateway source mismatch. When it discovers that a device identifier is not registered, it generates a failure reason for device not being registered. When it discovers that the aquaculture area number is inconsistent with the registration record, it generates a failure reason for inconsistent area affiliation. All of the above failure reasons are added as category information for the failure data, which is written into the failure flag field by the display module and used for log traceability.

[0036] The lag calculation submodule receives data packets containing the data generation time, gateway forwarding time, and server reception time. Based on the interval between the server reception time and the data generation time, it determines the data arrival lag duration and sends this lag duration to the category output submodule. The data arrival lag duration is an intermediate field describing the communication lag between data generation by the device and data reception by the server. It originates from time fields whose sequence has been confirmed as normal by the time verification unit; it does not use time-series abnormal data to generate this field.

[0037] The lag calculation submodule only generates a lag status field and does not independently determine whether it is currently valid or delayed. This field, along with the allowed waiting time field in the node registration record, is entered into the category output submodule. If a data packet lacks any time field, the lag calculation submodule does not generate a lag status field and transmits the field missing status to the category output submodule. If the gateway retransmits historical data, the lag calculation submodule still generates a lag status field using the data generation time and the server reception time, ensuring that the retransmitted data can be processed for delay marking according to the same criteria.

[0038] The retransmission count comparison submodule retrieves the retransmission count from the data packet and the maximum retransmission count in the node registration record, compares the two, and outputs the retransmission comparison result. The data packet retransmission count is the link retransmission status field carried in the message by the gateway or communication protocol, and the maximum retransmission count is a configuration field in the node registration record, derived from the gateway communication policy or platform operation and maintenance configuration. The retransmission comparison result is used to indicate whether the data packet has entered the retransmission anomaly boundary during transmission.

[0039] The retransmission count comparison submodule does not modify the data packet content; it only sends the retransmission comparison result to the category output submodule. If the retransmission count field of the data packet is missing or its format does not conform to the message field specification, the retransmission count comparison submodule outputs an abnormal status for the retransmission field, and the category output submodule treats this status as a failure cause. If the retransmission comparison result is within the allowable boundaries, the data packet still needs to undergo a joint judgment of the lag status and queue status; it cannot enter the current valid category solely based on the retransmission comparison result.

[0040] The queue comparison submodule retrieves the gateway's pending-send queue length from the data packet and the upper limit of the queue length in the node registration record, compares the two, and outputs the queue comparison result. The gateway's pending-send queue length is collected from the queue status field carried by the gateway during forwarding, describing the congestion state of packets yet to be sent in the gateway's cache. The upper limit of the queue length is a configuration field in the node registration record, derived from the gateway's caching policy and platform communication configuration. The queue comparison result indicates whether the gateway queue is in an acceptable sending state when the data packet arrives.

[0041] When processing queue fields, the queue comparison submodule first confirms that the field belongs to the queue status written by the acquisition gateway and does not accept queue fields backed up by the client or device. If a queue field is missing, the queue comparison submodule outputs an abnormal queue field status; if the queue comparison result exceeds the configuration boundary, the category output submodule transfers the data packet to the invalid data or delayed valid data determination branch, the specific branch being jointly defined by the lag status, retransmission status, and node registration record.

[0042] The category output submodule outputs currently valid data, delayed valid data, or invalid data based on data arrival lag time, retransmission comparison results, and queue comparison results. The category output submodule first handles pre-failure states such as timing anomalies, source mismatches, missing fields, and format anomalies. If no pre-failure state exists, it then reads the allowed waiting time field, retransmission comparison results, and queue comparison results. Currently valid data is output when the data arrival lag state is within the allowed waiting boundary, and both the retransmission comparison result and the queue comparison result are within the configured boundary. Delayed valid data is output when both the data source and timing are valid, but the arrival state needs to retain a lag indication in the display. Invalid data is output when any pre-failure state or the communication state does not meet the criteria for entering the display link.

[0043] The category output submodule writes the output data to the data validity category field. Currently valid data retains the original environmental value field or image status field and writes it to the current valid category; delayed valid data retains the original acquired content and adds a delay flag to the window module; failed data retains the failure cause field, device identifier, and receiving link field, but does not enter the window valid data filtering in the calibration module. The above category output results are simultaneously written to the judgment log, which records the source field, category field, anomaly cause field, and call destination field for subsequent traceability.

[0044] Window Module: Connected to the decision module, this module generates a valid communication timing window based on the data generation time and a preset reporting interval, and adds a delay marker to delayed valid data. The valid communication timing window is a time-attributed object formed around the device data generation time and the preset reporting interval in the node registration record. It includes the window reference time, communication cycle start boundary, communication cycle end boundary, device identifier, aquaculture area number, and window status. This object is used by the calibration module to filter data according to the client display time, ensuring that data retrieved at the same display time comes from a matching communication cycle range.

[0045] The window module only accepts currently valid data and delayed valid data, and does not accept invalid data into the window generation link. If a historical window has not yet been formed during the startup phase, the window module establishes an initial window baseline based on the time of data generation that has entered the judgment link and has normal timing, and gradually fills in the window state as subsequent data arrives. If the time of subsequent data generation falls into an existing valid communication timing window, the window module maintains the original window boundary and updates the data set within the window; if the time of subsequent data generation enters a new communication cycle, the window module generates a new valid communication timing window and moves the old window to a displayable or archived state.

[0046] The baseline determination submodule receives currently valid data or delayed valid data, reads the data generation time and the preset reporting interval in the node registration record, determines the data generation time as the window baseline time, and generates the baseline time result. The window baseline time is the starting reference field for generating the effective window of communication timing. It comes from the generation time of the actual collected or captured message on the device side, and does not use the server receiving time as a substitute to prevent the gateway cache retransmission from changing the collection cycle assignment.

[0047] When receiving data, the baseline determination submodule first checks whether the data has already been output as currently valid data or delayed valid data by the determination module, and then checks whether the node registration record has an effective preset reporting interval field. If the preset reporting interval field is missing, the baseline determination submodule does not generate a baseline time result and transfers the data to the window configuration missing state; if the data has a missing time or does not meet the order relationship confirmed by the time verification unit, the data does not enter the baseline determination submodule. The baseline time result is then passed to the period alignment submodule.

[0048] The periodic alignment submodule acquires the baseline time result and the preset reporting interval, performs periodic merging of the window baseline times according to the preset reporting interval, determines the starting boundary of the corresponding communication cycle, and generates a periodic alignment result. Periodic merging is a text rule process that classifies data generated by the same device under the same reporting rule into the corresponding communication cycle. During processing, it reads the device identifier, data generation time, and preset reporting interval fields, and checks the existing window status for the same device. If an existing window covers the data generation time, the periodic alignment result points to that existing window; otherwise, the periodic alignment result forms the starting boundary of a new communication cycle.

[0049] The periodic alignment submodule does not mix or merge data from different devices or different aquaculture areas. Even if environmental sensors and camera terminals are located in the same aquaculture area, they generate corresponding periodic alignment results according to their respective device identifiers and registration fields. When the data acquisition gateway retransmits data, periodic alignment is still based on the time when the data is generated on the device side, and the window assignment is not changed by the order of arrival of the retransmission. The periodic alignment results are passed to the boundary generation submodule.

[0050] The boundary generation submodule determines the start and end boundaries of the effective communication timing window based on the period alignment result and the preset reporting interval, and outputs the effective communication timing window. The start and end boundaries are the boundary fields in the window state object, used for subsequent client display time attribution comparison. The boundary generation submodule reads the communication period start boundary from the period alignment result and forms the end boundary of the same communication period according to the preset reporting interval field. The output data object includes device identifier, aquaculture area number, node location reference, window state, start boundary, and end boundary.

[0051] When handling window overlaps or gaps, the boundary generation submodule uses the registration records of the same device as the boundary source. If maintenance changes cause changes to the preset reporting interval field, the boundary generation submodule maintains the original boundaries of windows already formed before the change, generates a new window state for newly entered data after the change, and writes the configuration change source into the window state. If window generation fails, the window module outputs an abnormal window state, and the calibration module does not write this data into the aquaculture area status object.

[0052] The tag attachment submodule: Upon receiving delayed valid data, it writes a delay tag to the category field of the delayed valid data. The delay tag is a status identifier used for client display and status cache identification, including the carrier device identifier, aquaculture area number, original data valid category, delay source, and window affiliation. The delay source comes from the category output submodule's judgment result on the lag status, retransmission status, or queue status, and the window affiliation comes from the communication timing valid window generated by the boundary generation submodule.

[0053] The tag appending submodule does not modify the environmental value field, image status field, or original time field of the delayed valid data; it only appends a delay tag to the category field and passes this data to the calibration module. If the delayed valid data does not generate a valid communication timing window, the tag appending submodule retains the delay category but writes the window's abnormal state, and the subsequent window filtering submodule will not consider this data as valid window data. Currently valid data is not written with delay tags, but the data validity category field is still retained for the display module's arrangement.

[0054] Calibration Module: Connected to the window module, this module filters data falling within the communication timing validity window according to the client's display time, generates aquaculture area status objects and device node status objects, and generates an immediate sampling command when there is a gap in critical environmental data and the heartbeat is valid. The client display time is the display time assigned when the client requests to refresh the digital twin screen or when the server pushes a display frame, originating from the display service's request entry or push scheduling entry. The aquaculture area status object is a data object describing the environmental and spatial display status within the aquaculture area, carrying fields for aquaculture area number, aquaculture area location, node location, environmental value, image status, data validity category, and status update time. The device node status object is a data object describing the communication and display status of a single device node, carrying fields for device identifier, node location, data validity category, delay flag, failure reason reference, and status update time.

[0055] The calibration module does not re-determine the source of data packets and the valid communication category. Instead, it reads the valid communication timing window, currently valid data, and delayed valid data with delay markers output by the window module. Failed data is not included in the window's valid data set, but the cause of failure is retained for the display module to generate the category display field. A critical environmental data gap indicates that the aquaculture area status object lacks an environmental field configured as necessary for display by the platform within the corresponding window at the display time. This necessary field originates from the aquaculture area monitoring template. A valid heartbeat indicates that the heartbeat message from the acquisition gateway or device side passes source matching and timing verification, indicating that the device communication link is still reachable.

[0056] The display time matching submodule retrieves the client's display time and the start and end boundaries of the communication timing window. It then compares the client's display time with these boundaries to determine its time allocation, generating a display allocation result. This result is a data object describing which communication timing window the client's display time belongs to, containing the device identifier, aquaculture area number, window reference, and display allocation status. This submodule only compares communication timing windows that have already been output by the window module and are in a normal state; windows with abnormal states are not included in the allocation comparison.

[0057] When the display time matching submodule has not yet formed a complete window during the startup phase, it reads the existing initial window state and the cache of the previous valid state. If the client's display time does not fall within any generated window, the display assignment result is written to the "no window assignment" state, and the window filtering submodule is notified to maintain the display using the inheritance rule of the previous valid state. If the display time falls within a window but the data in the window has not yet arrived, the display assignment result is written to the "waiting for data" state, and the subsequent instruction triggering submodule combines the heartbeat state to determine whether to generate an immediate sampling instruction.

[0058] The window filtering submodule retrieves the displayed attribution results, currently valid data, and delayed valid data with delay markers. It then filters data falling within the communication timing valid window and generates window valid data. Window valid data is the set of data that can enter the status generation submodule at the displayed time, carrying device identifier, aquaculture area number, node location, environmental value field, image status field, data validity category, delay marker, and server reception time. During filtering, the window reference in the displayed attribution results is used as the basis; only data within that window that matches the device identifier and aquaculture area number is read.

[0059] When processing duplicate data, the window filtering submodule does not directly overwrite data packets in the order they arrive. Instead, it reads the data generation time, the server reception time, and the data validity category. If the same window contains both currently valid data and delayed valid data from the same device, the window filtering submodule retains their category information and passes it to the status generation submodule, which determines the display master value and how to retain the delay flag. If data is missing from the window, the window filtering submodule outputs the window data gap status and passes the gap field name, device identifier, and window reference to the instruction triggering submodule.

[0060] The status generation submodule generates aquaculture area status objects and device node status objects based on valid window data. This submodule retrieves the device identifier, aquaculture area number, node position, data validity category, and environmental value fields from the valid window data. It writes the environmental value fields corresponding to the same aquaculture area number into the aquaculture area status cache according to the node position, and writes the data validity category corresponding to the same device identifier into the device node status cache. When both currently valid data and delayed valid data exist within the same communication timing window, the currently valid data is used as the main display value, and the delay flag is retained to generate aquaculture area status objects and device node status objects.

[0061] Before writing to the status cache, the status generation submodule checks the integrity of the fields of the valid data in the window. If an environmental value field is missing, the aquaculture area status cache records the missing field and retains a reference to the previous valid status. If a node location is missing, the device node status cache records the abnormal location status and does not add the device to the area node display sequence. If a valid data category is missing, the status generation submodule does not generate a node status object and writes a category missing status. Both the aquaculture area status object and the device node status object are configured with a status update time field. This field represents the status update record written at the time of client display and indicates which display refresh the status object serves.

[0062] After writing the main display value, the state generation submodule writes the client display time to the state update time field. When the generation time of valid data in subsequent windows falls within the same communication timing window and the server's reception time is later than the server's reception time of the already written data, the valid data of the subsequent window replaces the already written data and refreshes the state update time field. During replacement, the category trajectory of the original data is not deleted; instead, the reception status of the original data is retained in the change record of the state cache, ensuring that the client display record reflects the data retransmission and update process within the same window. If the valid data in subsequent windows is delayed valid data, the state generation submodule only replaces the cached content when it meets the window ownership and reception time update rules, and retains the delay flag.

[0063] The instruction triggering submodule generates an immediate sampling instruction when there is a gap in critical environmental data and a valid heartbeat. The immediate sampling instruction is a control signaling object sent from the server to the acquisition gateway or device, carrying the device identifier, aquaculture area number, gap field, trigger source, instruction status, and feedback reception status. Critical environmental data gaps are identified from the gap status output by the window filtering submodule, and valid heartbeats are identified through source matching, timing verification, and the most recent valid status record of the heartbeat message. This submodule only generates the instruction when the gap field is a required field in the aquaculture area monitoring template and the device link is reachable.

[0064] After the instruction triggering submodule generates an immediate sampling instruction, it writes the instruction status to the control instruction record and sends the instruction to the corresponding acquisition gateway. If the acquisition gateway confirms receipt, the instruction status changes to "sent"; if the interface returns an exception or the instruction is not confirmed, the instruction status is written as "sent exception," and a gap status is reserved for the next display cycle to continue using the previous valid status or wait for new data. The immediate sampling instruction does not directly modify the aquaculture area status object; only after subsequent device sampling data is processed by the judgment module, window module, and calibration module does it enter the status cache update link.

[0065] Display Module: Connected to the calibration module, this module organizes client-side display records according to aquaculture area location, node location, and valid data category. Client-side display records are display data objects sent to the client's digital twin interface, containing aquaculture area number, aquaculture area location, equipment identifier, node location, main category field, delay flag field, failure flag field, status update time field, and display status. The display module reads aquaculture area status objects, equipment node status objects, failure reasons from failure data, and area and node display information output by the registration module, organizing the display data in the order of area to node to category field.

[0066] The display module does not accept direct writes from unregistered devices into the display record, nor does it write the environmental value field of failed data into the main display value. Failed data is only entered into the failure flag field by the failure reason, delayed valid data is entered into the delay flag field by the delay flag, and currently valid data is entered into the main category field. After the client display record is generated, it is written to the display cache, and the client renders the digital twin status according to the aquaculture area location and node location.

[0067] The region mapping submodule retrieves the breeding region number and location from the breeding region status object, establishes a region display mapping relationship between the breeding region number and the breeding region location, and generates a region display index. The region display index is a region-level positioning object in the client display record, carrying the breeding region number, breeding region location, display level, and status object reference. The breeding region location originates from the registration module and digital twin space management data, while the breeding region status object comes from the status generation submodule of the calibration module.

[0068] When processing aquaculture region status objects, the region mapping submodule first confirms that the aquaculture region number already exists in the region attribution result generated by the registration module, and then confirms that the aquaculture region location has a displayable status. If the aquaculture region location is missing, the region display index is written to the region location pending confirmation status, and the node sorting submodule does not write the nodes in that region into the client display record. If the status update time field of the aquaculture region status object is empty, the region mapping submodule retains the region display index, but writes the region display status into the waiting status.

[0069] The node sorting submodule retrieves the device identifier and node position from the device node status object, writes the node positions into the node display sequence of the corresponding aquaculture area according to the region display index, and generates the node sorting result. The node display sequence is an object that displays the arrangement of device nodes within the same aquaculture area to the client, carrying the aquaculture area number, device identifier, node position, device node status reference, and display order. Node sorting does not depend on specific coordinate value examples, but is organized based on the relative display affiliation of the node position field in the digital twin space.

[0070] The node sorting submodule only processes devices with valid node positions in the device node status object. If a device node status object has a valid data category but the node position is yet to be confirmed, the node sorting result is written as an abnormal node position, and the device is added to the maintenance prompt record and not included in the normal node display sequence. If the same device identifier has node states from different windows, the node sorting submodule reads the status update time field and window reference, and selects the node state that matches the client's display time to enter the node sorting result.

[0071] The category arrangement submodule retrieves the node sorting results and valid data categories, writes the valid data categories into the category display field of the corresponding device identifier, and generates the category arrangement result. The category display field includes a main category field, a delay flag field, and a failure flag field. The submodule retrieves the valid data categories corresponding to the currently valid data, delayed valid data with delay flags, and failed data. It associates the valid data categories with the device identifier and determines the category writing position according to the aquaculture area location and node location. When the same device identifier corresponds to more than one valid data category, the main category value of the category display field is determined according to the order of the currently valid data, delayed valid data, and failed data, generating the category arrangement result.

[0072] After determining the main category value, the category arrangement submodule writes the currently valid data to the main category field, the delay flag of the delayed valid data to the delay flag field, and the failure reason corresponding to the failed data to the failure flag field, generating a category display field record. If the same device has both currently valid data and delayed valid data within the same communication timing window, the main category field retains the currently valid category, and the delay flag field retains the delay status, allowing the client to identify communication lag while ensuring the displayed main value is not overwritten by delayed data. If the same device only has failed data, the main category field does not write the currently valid category, the failure flag field writes the failure reason, and the device node is displayed as unavailable. If the failure reason stems from source mismatch, timing anomaly, field missing, or window anomaly, the category arrangement submodule writes the corresponding textual reason, without using numerical error codes to replace the failure description.

[0073] The record generation submodule generates client-side display records based on the category arrangement results. It reads the region display index, node sorting results, and category arrangement results, organizing the aquaculture area location, node location, equipment identifier, status update time field, main category field, delay flag field, and failure flag field into client-readable display data objects. After the client-side display records are written to the display cache, the client display service reads and displays the corresponding aquaculture area and node status.

[0074] The record generation submodule synchronously writes the display record source when generating client display records. Sources include registration record references, window references, state object references, and category orchestration references. If the display cache write fails, the record generation submodule retains the category orchestration result and writes the cache exception status. The client display service continues to read the previous valid display record, while retaining the exception status for maintenance personnel to view. If the display time requested by the client is later than the current state cache, the record generation submodule determines the display record's ownership based on the state update time field output by the calibration module, and does not directly call data packets that have not undergone window filtering. Through field-level connections between registration, judgment, window, calibration, and display, the system establishes a definite data destination and display status under various operating states, including gateway retransmission, queue congestion, valid device heartbeats but missing critical environmental data, device source mismatch, and timing anomalies.

[0075] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A digital twin-based visualization system for monitoring the status of aquaculture, characterized in that, The system includes: The registration module is used to register the breeding area, node location, preset reporting interval, allowed waiting time, maximum number of retransmissions and maximum queue length of environmental sensors, camera terminals and data acquisition gateways, and output node registration records; The determination module, connected to the registration module, is used to receive data packets containing the data generation time, gateway forwarding time, server receiving time, number of data packet retransmissions, and gateway waiting queue length. Based on the node registration records, it compares the data arrival delay time, the number of data packet retransmissions, and the gateway waiting queue length, and outputs the currently valid data, delayed valid data, or invalid data. A window module, connected to the determination module, is used to generate a communication timing effective window based on the data generation time and the preset reporting interval, and to attach a delay mark to the delayed effective data. The calibration module, connected to the window module, is used to filter data falling into the effective window of the communication timing according to the time displayed by the client, generate aquaculture area status objects and equipment node status objects, and generate an immediate sampling command when there is a gap in critical environmental data and the heartbeat is valid. The display module, connected to the calibration module, is used to organize client-side display records according to the location of the breeding area, node location, and valid data category.

2. The aquaculture monitoring status visualization system based on digital twins according to claim 1, characterized in that, The registration module includes a region binding submodule, a node positioning submodule, a parameter configuration submodule, and a record output submodule; The region binding submodule receives the device identifiers of the environmental sensor, the camera terminal, and the data acquisition gateway, reads the aquaculture area number and the device affiliation relationship, establishes a binding relationship between the device identifiers and the aquaculture area number within the same aquaculture area, and generates a region affiliation result. The node positioning submodule obtains the region attribution result and node location, writes the node location into the node location field of the corresponding device identifier, and generates the node positioning result; The parameter configuration submodule obtains the node location result, preset reporting interval, allowed waiting time, maximum number of retransmissions and maximum queue length, writes the above parameters into the registration field of the corresponding device identifier, and generates the registration parameter result; The record output submodule generates node registration records based on the registration parameter results.

3. The aquaculture monitoring status visualization system based on digital twins according to claim 1, characterized in that, The determination module includes a lag calculation submodule, a count comparison submodule, a queue comparison submodule, and a category output submodule; The lag calculation submodule receives a data packet containing the data generation time, gateway forwarding time, and server reception time. Based on the time difference between the server reception time and the data generation time, it determines the data arrival lag time and sends the data arrival lag time to the category output submodule. The retransmission comparison submodule obtains the number of retransmissions of the data packet in the data packet and the upper limit of the retransmission count in the node registration record, compares the two and outputs the retransmission comparison result. The queue comparison submodule obtains the gateway queue length to be sent in the data packet and the upper limit of the queue length in the node registration record, compares the two and outputs the queue comparison result. The category output submodule outputs currently valid data, delayed valid data, or invalid data based on the data arrival delay time, the retransmission comparison result, and the queue comparison result.

4. The aquaculture monitoring status visualization system based on digital twins according to claim 1, characterized in that, The window module includes a baseline determination submodule, a periodic alignment submodule, a boundary generation submodule, and a marker attachment submodule; The baseline determination submodule receives currently valid data or delayed valid data, reads the data generation time and the preset reporting interval in the node registration record, determines the data generation time as the window baseline time, and generates the baseline time result. The periodic alignment submodule obtains the reference time result and the preset reporting interval, performs periodic merging on the window reference time according to the preset reporting interval, determines the starting boundary of the corresponding communication period, and generates the periodic alignment result. The boundary generation submodule determines the start and end boundaries of the effective communication timing window based on the periodic alignment result and the preset reporting interval, and outputs the effective communication timing window. When the tag attachment submodule receives delayed valid data, it writes a delay tag into the category field of the delayed valid data.

5. The aquaculture monitoring status visualization system based on digital twins according to claim 1, characterized in that, The calibration module includes a display time matching submodule, a window filtering submodule, a status generation submodule, and a command triggering submodule; The display time matching submodule obtains the client display time and the start and end boundaries of the effective window of the communication timing, compares the client display time with the start and end boundaries for time assignment, and generates a display assignment result. The window filtering submodule obtains the display attribution result, the current valid data, and the delayed valid data with delay markers, filters the data that falls into the communication timing valid window, and generates window valid data; The status generation submodule generates aquaculture area status objects and equipment node status objects based on the valid data in the window; The instruction triggering submodule generates an immediate sampling instruction when there is a gap in critical environmental data and the heartbeat is valid.

6. The aquaculture monitoring status visualization system based on digital twins according to claim 1, characterized in that, The display module includes a region mapping submodule, a node sorting submodule, a category arrangement submodule, and a record generation submodule; The region mapping submodule obtains the breeding region number and breeding region location from the breeding region status object, establishes a region display mapping relationship between the breeding region number and the breeding region location, and generates a region display index. The node sorting submodule obtains the device identifier and node position from the device node status object, writes the node position into the node display sequence of the corresponding aquaculture area according to the area display index, and generates the node sorting result. The category arrangement submodule obtains the node sorting result and the valid data category, writes the valid data category into the category display field of the corresponding device identifier, and generates the category arrangement result; The record generation submodule generates client-side display records based on the category arrangement results.

7. The aquaculture monitoring status visualization system based on digital twins according to claim 3, characterized in that, The determination module is equipped with a time verification unit; The timing verification unit obtains the data generation time, gateway forwarding time, and server receiving time from the data packet, and performs timing verification according to the order relationship that the data generation time is not later than the gateway forwarding time and the gateway forwarding time is not later than the server receiving time. When any time does not meet the order relationship, a timing abnormality mark is generated, and the data packet with the timing abnormality mark is handed over to the determination module to be determined as invalid data.

8. The aquaculture monitoring status visualization system based on digital twins according to claim 3, characterized in that, The determination module is equipped with a node matching unit; The node matching unit obtains the device identifier, acquisition gateway identifier, and aquaculture area number carried in the data packet, matches the device identifier with the registered device identifier in the node registration record, and matches the acquisition gateway identifier with the registered gateway identifier in the node registration record. When both the device identifier and the acquisition gateway identifier match and the aquaculture area number is consistent, a judgment status is output; otherwise, a source mismatch status is output and the corresponding data packet is identified as invalid data.

9. The aquaculture monitoring status visualization system based on digital twin according to claim 5, characterized in that, The state generation submodule is specifically as follows: Obtain the device identifier, breeding area number, node position, data validity category and environmental value fields from the valid data of the window. Write the environmental value field corresponding to the same breeding area number into the breeding area status cache according to the node position, and write the data validity category corresponding to the same device identifier into the device node status cache. When there is current valid data and delayed valid data in the same communication time sequence valid window, use the current valid data as the main display value and retain the delay mark to generate breeding area status object and device node status object. The aquaculture area status object and the device node status object are each configured with a status update time field; After writing the main display value, the status generation submodule writes the client display time into the status update time field. When the data generation time of the subsequent window's valid data falls within the same communication timing window and the server's receiving time is later than the server's receiving time of the written data, the written data is replaced with the subsequent window's valid data, and the status update time field is refreshed.

10. The aquaculture monitoring status visualization system based on digital twin according to claim 6, characterized in that, The category arrangement submodule is specifically as follows: Obtain the data validity categories corresponding to the current valid data, delayed valid data with delay markers, and failed data; associate the data validity categories with the device identifier; and determine the category writing position according to the breeding area location and node location. When the same device identifier corresponds to multiple data validity categories, determine the main category value of the category display field according to the order of the current valid data, delayed valid data, and failed data, and generate the category arrangement result. The category display field specifically includes: The category arrangement submodule, after determining the main category value, writes the currently valid data into the main category field, writes the delay flag of the delayed valid data into the delay flag field, and writes the failure reason corresponding to the failed data into the failure flag field, thereby generating a category display field record.

Images