A maritime emergency event-based three-dimensional digital twin linkage display system and method

Abstract

This invention discloses a method and system for three-dimensional digital twin linkage display based on maritime emergency events, comprising: acquiring multi-source heterogeneous maritime business data and standardizing it into a unified event object; generating differential instructions by comparing event identifiers and version information to drive subsequent linkage operations; parsing the event space index key and determining the associated three-dimensional objects and display strategies based on multi-dimensional mapping; generating and executing a rollbackable linkage action set according to the differential instructions, while recording action snapshots to support accurate rollback after the event is resolved; enabling local caching to maintain the display when data acquisition is abnormal, and achieving global state alignment through version comparison and differential replay after network recovery. This invention realizes automatic mapping, linkage display, and state synchronization between emergency events and three-dimensional scenes, solving problems such as ambiguous situational awareness, information disconnect, and abnormal interruptions in traditional systems, and effectively improving the intuitiveness, consistency, and reliability of maritime emergency command.

Description

Technical Field

[0001] This invention relates to the field of maritime emergency command and digital twin technology, specifically to a three-dimensional digital twin linkage display system and method based on maritime emergency events. Background Technology

[0002] Currently, maritime emergency command systems primarily acquire vessel position data through the Automatic Identification System (AIS) and combine it with distress information reported by crew members via satellite phone, high-frequency radio, and other means, displaying the data on a two-dimensional electronic nautical chart. The system is mainly used to view the planar position distribution of distressed vessels and surrounding rescue vessels.

[0003] The existing system focuses on two-dimensional location display, providing only basic location viewing functionality. It lacks the ability to display three-dimensional spatial scenes and has not established an automatic correlation mechanism between emergency events and spatial scenes. The system is mainly used for information retrieval and lacks the technical means to spatially represent and dynamically display emergency events. Event progress relies entirely on manual offline communication for confirmation. The reporting, collection, display, and dispatching stages are independent of each other, lacking unified information management and linkage logic, as well as data retention and status maintenance capabilities. When network or AIS data is abnormal, the system cannot view the positions of ships and rescue forces, and on-site spatial situational awareness is completely interrupted, relying solely on fragmented offline communication to obtain information.

[0004] Therefore, existing technologies are insufficient to meet the needs of maritime emergency scenarios for intuitive spatial display, event linkage presentation, and continuous and reliable perception under abnormal conditions. Summary of the Invention

[0005] This invention aims to solve the following technical problems existing in the prior art: the automatic mapping of maritime emergency events to spatial objects such as ships and rescue forces in 3D maritime scenes; the consistency of the linkage display of 3D scenes and UI prompts when the status of a maritime emergency event changes; the residual problem of various linkage display effects in 3D scenes after the maritime emergency event is resolved; and the continuity of 3D situation display and the consistency of status after network recovery when maritime network or AIS data is abnormal.

[0006] The technical solution adopted in this invention is a three-dimensional digital twin linkage display system based on maritime emergency events, comprising: an event standardization module, used to acquire multi-source heterogeneous maritime business data, perform standardization processing on it, and generate standardized event objects with a unified data structure; a state management module, used to establish an event state management container, manage the state of the standardized event objects, identify event state changes by comparing event identifiers and version information, and generate differential instructions for indicating linkage operations, the differential instructions including event addition, update, or removal; a spatial mapping module, used to parse the spatial index keys in the standardized event objects, determine the three-dimensional spatial objects associated with the event objects and the corresponding linkage display strategies based on preset multi-dimensional mapping relationships; a linkage execution module, used to generate and execute a set of rollbackable linkage actions according to the differential instructions and the determined linkage display strategies, and record the action snapshot of the current three-dimensional digital twin scene during execution; and an anomaly recovery module, used to enable local cached data to maintain the three-dimensional scene display when an abnormal data acquisition is detected; and to perform global state alignment based on event version comparison and differential replay after network recovery to ensure that the three-dimensional scene display state is consistent with the real event state.

[0007] Preferably, the linkage execution module is further configured to: when the differential instruction is to add or update, generate a linkage action set including at least one of camera pose change, 3D object highlighting, user interface prompt activation, and special effects playback, and record an action snapshot including the current camera state, highlighting state, user interface state, and special effects state; when the differential instruction is to remove, perform a reverse rollback operation of the linkage action set according to the previously recorded action snapshot to restore the 3D digital twin scene to the state before the event occurred.

[0008] Preferably, the preset multi-dimensional mapping relationships in the spatial mapping module include: mapping between spatial index keys and 3D object identifiers; mapping between event types and preset camera view strategies; mapping between event urgency and object highlighting style strategies; and mapping between event handling status and user interface resource strategies. Furthermore, the spatial mapping module is also used to execute a degradation strategy when the mapping relationship is missing. The degradation strategy includes using the default view, the default highlighting style, or only providing user interface prompts.

[0009] A method for interactive 3D digital twin display based on maritime emergency events includes the following steps: Step S1: Obtain multi-source heterogeneous maritime business data, perform standardization processing on it, and generate standardized event objects with a unified data structure; Step S2: Establish an event status management container to manage the status of the standardized event objects. By comparing event identifiers and version information, identify event status changes and generate differential instructions for indicating linkage operations. The differential instructions include event addition, update, or removal. Step S3: Parse the spatial index key in the standardized event object, and based on the preset multidimensional mapping relationship, determine the three-dimensional spatial object associated with the event object and the corresponding linkage display strategy; Step S4: Based on the differential instruction and the determined linkage display strategy, generate and execute a set of rollbackable linkage actions, and record the action snapshot of the current 3D digital twin scene during execution; Step S5: When an abnormal data acquisition is detected, local cached data is enabled to maintain the 3D scene display; when the network is restored, global state alignment is performed based on event version comparison and differential replay to ensure that the 3D scene display state is consistent with the real event state.

[0010] Preferably, step S2 specifically includes: maintaining a set of currently valid events and a set of deactivated events; comparing version stamps or timestamps for standardized event objects with the same event identifier; ignoring events if they have not changed; and generating differential instructions containing add, update, or remove operations to drive the differentiated execution of subsequent 3D linkage actions if events have changed.

[0011] Preferably, in step S4, a set of rollbackable linked actions is generated and executed, and a snapshot of the current 3D digital twin scene is recorded during execution. Specifically, this includes: when the differential instruction is to add or update, generating a set of linked actions that includes at least one of camera pose change, 3D object highlighting, user interface prompt activation, and special effects playback, and recording the action set that includes the current camera state, highlighting state, user interface state, and special effects state; when the differential instruction is to remove, performing a reverse rollback operation of the linked action set based on the previously recorded action snapshot to restore the 3D digital twin scene to the state before the event occurred.

[0012] Preferably, the preset multidimensional mapping relationships in step S3 include: the mapping between spatial index keys and three-dimensional object identifiers; the mapping between event types and preset camera view strategies; the mapping between event urgency and object highlighting style strategies; the mapping between event handling status and user interface resource strategies; and when the mapping relationships are missing, a degradation strategy is executed, which includes using the default view, the default highlighting style, or only providing user interface prompts.

[0013] Preferably, the global state alignment performed in step S5 specifically includes: after network recovery, obtaining the latest event data and comparing it with the locally cached event data; calculating a new differential instruction; performing a global reset on the current 3D digital twin scene; and re-executing the linkage action according to the new differential instruction to replay and synchronously display the state.

[0014] Preferably, the standardization process for multi-source heterogeneous maritime business data in step S1 includes: decrypting and cleaning the encrypted raw response data, wherein the cleaning includes removing byte order markers and filtering control characters; and normalizing the cleaned data with different source fields into standardized event objects containing event identifiers, event types, subtypes, urgency levels, handling status, spatial index keys, timestamps, and raw data payloads according to a preset unified field mapping logic.

[0015] The beneficial effects of this invention are: 1. Improved situational awareness efficiency: By automatically mapping maritime emergency events to 3D spatial objects, and linking them to complete display actions such as camera activation, highlighting, and UI prompts, the manual positioning and secondary confirmation steps are eliminated, enabling commanders to intuitively and quickly grasp the on-site spatial situation. 2. Consistent display status: Through idempotent management of event status and a snapshot rollback mechanism for linked actions, synchronous updates when event status changes and residue-free resets after event resolution are achieved, ensuring the uniformity of the display status across multiple terminals and avoiding command misjudgments caused by inconsistent information. 3. Enhanced anomaly response capabilities: In the event of network or AIS data anomalies, the system can activate local caching to maintain continuous 3D situational awareness display; after recovery, global status alignment is achieved through version comparison and differential replay, solving the problems of perception interruption and lack of fallback solutions in traditional systems under abnormal circumstances. 4. Good scalability: By adopting standardized event processing and a unified multi-dimensional mapping and rollback strategy, the same framework can be compatible with backend automated events and frontend interactive events, adapting to various maritime emergency linkage display needs without large-scale modifications, demonstrating good system scalability. 5. Enhance the standardization of emergency response: Through automated event processing and coordinated display, the information transmission errors and delays caused by manual operation are reduced, and the reporting, collection, display and dispatch processes are closed-loop, which significantly improves the standardization and rapid response capabilities of maritime emergency command. Attached Figure Description

[0016] Figure 1 This is an overall flowchart of the three-dimensional digital twin linkage display method based on maritime emergency events in an embodiment of the present invention. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.

[0018] This embodiment provides a method for the coordinated display of three-dimensional digital twins based on maritime emergency events. This method can be applied to the search and rescue large-screen system of a maritime emergency command center, enabling automatic event mapping, three-dimensional coordinated display, status rollback, and network anomaly recovery for maritime emergency events such as ship collisions and ship fires.

[0019] Combination Figure 1 The method includes the following steps: Step S1: Standardize event processing.

[0020] This step aims to transform diverse and heterogeneous maritime operational data (such as SOS calls, incident reporting, and early warning drills) into unified event objects, providing standard input for subsequent digital twin collaboration. (Refer to...) Figure 1 The specific process is as follows: Multi-source data acquisition: The system acquires business data in real time via an HTTP polling mechanism. For example, it accesses the ` / sosReport / sosScreen` interface to obtain personnel distress call information (police / medical personnel); it accesses the ` / emergencyReport / page` interface to obtain reporting information such as cabin service and facility damage; and it accesses the ` / api / bShips / screen / getPublishItem` interface to obtain fire warnings and drill status. The acquisition frequency is controlled by a Timer, with a default interval of 3-5 seconds to ensure near real-time data accuracy.

[0021] Data Security Decryption and Cleaning: Due to the sensitivity of maritime data, the original response data is encrypted with AES. The system uses the AES-128-CBC standard for decryption, which includes Base64 decoding, AES decryption, and UTF8 encoding to obtain a plaintext JSON string. Data cleaning is then performed: Byte order markup (BOM) tags for UTF-8 / UTF-16 / UTF-32 are removed to prevent JSON parsing errors; regular expressions are used to remove ASCII control characters (keeping newline characters \n and tab characters \t) to maintain data structure; newline characters are standardized to \n and leading and trailing whitespace is removed to ensure cross-platform parsing consistency; finally, the API response status code is checked to be "00000" and the data field is not empty to complete integrity verification.

[0022] Normalization mapping: This maps source data fields with different structures to a unified StandardEvent structure. This structure includes, but is not limited to, the following unified fields: eventId (unique identifier), eventType (event type, such as "SOS", "REPORT", "FIRE"), subType (subtype), level (urgency level), status (handling status), spaceKey (spatial index, such as location name or ID), timestamp (occurrence time), and payload (raw data payload). Through this process, the system shields the differences in underlying business data, allowing subsequent three-dimensional linkage logic to reuse the same set of code.

[0023] Step S2: Idempotent management of event states.

[0024] An event state management container is established, including the currently active event set (ActiveSet) and the removed event set (RemovedSet). For standardized event objects with the same eventId, the system compares the version or timestamp. If there is no change, the update is ignored to avoid invalid operations; if there is a change, a differential instruction Δ = {add | update | remove} is generated. This differential mechanism is used to accurately indicate the operations that need to be performed in subsequent 3D linkage, avoiding duplicate execution and meaningless scene refreshes.

[0025] Step S3: Spatial mapping resolution.

[0026] Create and query a multidimensional mapping table M. This table defines the following key mappings: 1. spaceKey → 3D object identifier (such as the 3D model ID of a specific ship or facility) 2. eventType → Camera perspective strategy (e.g., for a "fire" event, the camera should focus on the deck of the vessel involved in the incident). 3. Level → Highlighting style strategy (e.g., "Emergency" events are highlighted in red). 4. Status → UI resource strategy (e.g., displaying specific icons and tooltips for "Pending" status) If a mapping relationship is missing, the system executes a fallback strategy: using the default global view, the default highlighting style, or only providing hints through the UI list, to ensure that the system can still run when some information is missing.

[0027] Table 1 shows how the normalization mapping logic maps source data with different structures to a unified StandardEvent structure.

[0028] Step S4: Arrangement and execution of linked actions.

[0029] When the differential command Δ is received, the system responds as follows: If the action is "add" or "update": The system generates a linked ActionSet, which encapsulates a series of atomic operations, such as: 1. Camera pose change (flying to the incident location); 2. Highlighting 3D objects (blinking or outlining); 3. Enabling UI prompts (displaying an event details pop-up); 4. Playing special effects (simulating fire or smoke). Simultaneously, the system generates an ActionSnapshot, recording the scene state before these actions were executed, including cameraState, highlightState, uiState, and effectState.

[0030] If the action is "remove": the system performs a precise rollback operation based on the previously stored snapshot for the event: restoring the camera to its original position, disabling object highlighting, hiding associated UI elements, and disabling effects. This mechanism ensures that no state remains in the 3D scene after the event is resolved, avoiding interference with subsequent command and decision-making.

[0031] Step S5: Align abnormal rollback and recovery.

[0032] When a network error occurs or data acquisition fails, the system immediately uses the most recent valid event set in the local cache to drive the display of the 3D scene, thereby maintaining the continuity of situational awareness and avoiding the screen from "freezing" or "blank".

[0033] Once the network is restored, the system executes a state alignment process: First, it acquires the latest event data and compares it with the locally cached event data; then, it calculates the difference Δ' between the old and new states; next, it performs a global reset on the current 3D digital twin scene, clearing all possible temporary states; finally, based on the newly calculated difference Δ', it re-executes the linkage action in step S4 to complete the state replay and synchronization. The entire process is automated, ensuring that the displayed state ultimately matches the event state in the real world.

[0034] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely illustrative of the principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the present invention as claimed. The scope of protection of this invention is defined by the appended claims and their equivalents.

Claims

1. A three-dimensional digital twin linkage display system based on maritime emergency events, characterized in that, include: The event standardization module is used to acquire multi-source heterogeneous maritime business data, standardize it, and generate standardized event objects with a unified data structure. The status management module is used to establish an event status management container, manage the status of the standardized event objects, identify event status changes by comparing event identifiers and version information, and generate differential instructions for indicating linkage operations. The differential instructions include event addition, update, or removal. The spatial mapping module is used to parse the spatial index key in the standardized event object, and determine the three-dimensional spatial object associated with the event object and the corresponding linkage display strategy based on the preset multi-dimensional mapping relationship. The linkage execution module is used to generate and execute a set of rollbackable linkage actions according to the differential instructions and the determined linkage display strategy, and to record the action snapshot of the current three-dimensional digital twin scene during execution. abnormal The recovery module is used to maintain the 3D scene display by caching local data when an abnormal data acquisition is detected; after the network is restored, it performs global state alignment based on event version comparison and differential replay to ensure that the 3D scene display state is consistent with the real event state.

2. The three-dimensional digital twin linkage display system based on maritime emergency events according to claim 1, characterized in that, The linkage execution module is further configured to: when the differential instruction is to add or update, generate a linkage action set including at least one of camera pose change, 3D object highlighting, user interface prompt activation, and special effects playback, and record an action snapshot including the current camera state, highlighting state, user interface state, and special effects state; when the differential instruction is to remove, perform a reverse rollback operation of the linkage action set based on the previously recorded action snapshot to restore the 3D digital twin scene to the state before the event occurred.

3. The three-dimensional digital twin linkage display system based on maritime emergency events according to claim 1, characterized in that, The preset multi-dimensional mapping relationships in the spatial mapping module include: the mapping between spatial index keys and 3D object identifiers; the mapping between event types and preset camera view strategies; the mapping between event urgency and object highlighting style strategies; and the mapping between event handling status and user interface resource strategies. Furthermore, the spatial mapping module is also used to execute a degradation strategy when the mapping relationship is missing. The degradation strategy includes using the default view, the default highlighting style, or only providing user interface prompts.

4. A method for the linked display of three-dimensional digital twins based on maritime emergency events, characterized in that, Includes the following steps: Step S1: Obtain multi-source heterogeneous maritime business data, perform standardization processing on it, and generate standardized event objects with a unified data structure; Step S2: Establish an event status management container to manage the status of the standardized event objects. By comparing event identifiers and version information, identify event status changes and generate differential instructions for indicating linkage operations. The differential instructions include event addition, update, or removal. Step S3: Parse the spatial index key in the standardized event object, and based on the preset multidimensional mapping relationship, determine the three-dimensional spatial object associated with the event object and the corresponding linkage display strategy; Step S4: Based on the differential instruction and the determined linkage display strategy, generate and execute a set of rollbackable linkage actions, and record the action snapshot of the current 3D digital twin scene during execution; Step S5: When an abnormal data acquisition is detected, local cached data is enabled to maintain the 3D scene display; when the network is restored, global state alignment is performed based on event version comparison and differential replay to ensure that the 3D scene display state is consistent with the real event state.

5. The method for three-dimensional digital twin linkage display based on maritime emergency events according to claim 1, characterized in that, Step S2 specifically includes: maintaining a set of currently valid events and a set of deactivated events; comparing version stamps or timestamps for standardized event objects with the same event identifier; ignoring event objects if they have not changed; and generating differential instructions containing add, update, or remove operations to drive the differentiated execution of subsequent 3D linkage actions if the event objects have changed.

6. The method for three-dimensional digital twin linkage display based on maritime emergency events according to claim 5, characterized in that, In step S4, a set of rollbackable linked actions is generated and executed, and a snapshot of the current 3D digital twin scene is recorded during execution. Specifically, when the differential instruction is to add or update, a set of linked actions is generated that includes at least one of camera pose change, 3D object highlighting, user interface prompt activation, and special effects playback, and the action snapshot including the current camera state, highlighting state, user interface state, and special effects state is recorded. When the differential instruction is to remove, the reverse rollback operation of the linked action set is executed according to the previously recorded action snapshot to restore the 3D digital twin scene to the state before the event occurred.

7. The method for three-dimensional digital twin linkage display based on maritime emergency events according to claim 5, characterized in that, The preset multi-dimensional mapping relationships in step S3 include: the mapping between spatial index keys and three-dimensional object identifiers; the mapping between event types and preset camera view strategies; the mapping between event urgency and object highlighting style strategies; the mapping between event handling status and user interface resource strategies; and when the mapping relationships are missing, a degradation strategy is executed, which includes using the default view, the default highlighting style, or only providing user interface prompts.

8. A method for three-dimensional digital twin linkage display based on maritime emergency events according to claim 5, characterized in that, Step S5 involves performing global state alignment, specifically including: after network recovery, acquiring the latest event data and comparing it with the locally cached event data; calculating a new differential instruction; performing a global reset on the current 3D digital twin scene; and re-executing the linkage action according to the new differential instruction to replay and synchronously display the state.

9. A method for three-dimensional digital twin linkage display based on maritime emergency events according to claim 5, characterized in that, The standardization process for multi-source heterogeneous maritime business data in step S1 includes: decrypting and cleaning the encrypted raw response data, wherein the cleaning includes removing byte order markers and filtering control characters; and normalizing the cleaned data with different source fields into standardized event objects containing event identifiers, event types, subtypes, urgency levels, handling status, spatial index keys, timestamps, and raw data payloads according to a preset unified field mapping logic.

Images