Methods, devices and electronic equipment for exchanging information on water traffic control

The 19-bit CIMCS coding solves the problems of chaotic coding system and poor international compatibility in intelligent management and control of water traffic, and realizes the integration of unique data identification, standard traceability and communication adaptation, thereby improving the real-time performance and security of data transmission.

CN123123375APending Publication Date: 2026-11-17CHINA WATERBORNE TRANSPORT RES INST
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202610990321.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-07-03
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

The existing intelligent management and control coding system for water traffic is chaotic, has poor international compatibility, lacks communication adaptability, and cannot meet the requirements for real-time performance and security.

Method used

It adopts 19-bit CIMCS encoding, which includes subject field code, scene code, feature code, standard system code, security level code, protocol adaptation code and data element sequence number, to achieve unique identification of data, standard traceability and communication adaptation in one. By embedding transmission-related fields in the encoding, it automatically determines the transmission mode and channel resource allocation.

Benefits of technology

It provides a unique identifier for cross-scenario and cross-system data interaction, improves international mutual recognition rate and channel utilization, ensures the real-time performance and security of data transmission, and reduces transmission latency and redundancy.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123123375A_ABST
    Figure CN123123375A_ABST
Patent Text Reader

Abstract

This application provides a method, apparatus, and electronic device for exchanging maritime traffic control information. The method includes: acquiring control information carrying a 19-bit encoding, which includes a subject field code, scene code, characteristic code, standard system code, standard code, security level code, protocol adaptation code, and data element sequence number; determining the data format based on the standard system code and standard code, and the encoding-standard mapping relationship; determining the SECOM protocol transmission mode based on the security level code and protocol adaptation code, including connection-oriented (CON) mode and connectionless (CL) mode; and allocating channel resources for the control information based on the security level code. The encoding fields directly map to international standard systems and local specifications, balancing international mutual recognition with local needs; the encoding embeds transmission-related fields, allowing for transmission mode determination without additional parsing, supporting differentiated VDES channel scheduling, and improving channel utilization.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of water traffic control technology, and in particular to a method, apparatus and electronic device for exchanging water traffic control information. Background Technology

[0002] The current coding of intelligent water traffic management data faces three core problems: First, the coding system is chaotic, with different scenarios and systems using proprietary coding formats. Cross-scenario data interaction requires manual transcoding, which is inefficient and prone to errors. Second, there is insufficient international compatibility, as local coding is not precisely associated with international standards such as IHO / IMO / IALA, hindering international data mutual recognition. Third, there is a lack of communication adaptation features, as the coding does not incorporate information such as security level and transmission priority, making it unable to directly support differentiated scheduling of VDES narrowband channels.

[0003] Existing coding schemes mostly only meet the requirement of unique identification and do not achieve the integration of "business affiliation - standard traceability - communication adaptation". For example, international standard coding lacks local characteristic field association, and domestic coding does not embed security level and transmission mode information. This causes data to need to be parsed additionally when transmitted across systems, increasing transmission latency and redundancy, and failing to meet the real-time and security requirements of intelligent management and control of water traffic. Summary of the Invention

[0004] This application provides a method, device, and electronic device for exchanging water traffic control information, in order to solve the problems of chaotic coding system, poor international compatibility, and lack of communication adaptation in the existing system.

[0005] In a first aspect, this application provides a method for exchanging maritime traffic control information, applied to shore-based equipment, the method comprising:

[0006] Obtain control information, which carries a 19-bit code, including a 1-2 digit topic domain code, a 3-4 digit scene code, a 5-7 digit feature code, an 8-digit standard system code, a 9-10 digit standard code, an 11-12 digit security level code, a 13-14 digit protocol adaptation code, and a 15-19 digit data element sequence number.

[0007] The data format is determined based on the standard system code and standard code, as well as the preset encoding-standard mapping relationship;

[0008] Based on the security level code and the protocol adaptation code, the transmission mode of the SECOM protocol is determined, including connection-oriented CON mode and connectionless CL mode.

[0009] According to the security level code, channel resources are allocated to the control information;

[0010] According to the data format and the transmission mode, data is exchanged with the ship through the channel resources.

[0011] Furthermore, determining the SECOM protocol transmission mode based on the security level code and the protocol adaptation code includes:

[0012] If the security level code is 1-3, then the transmission mode is determined to be connection-oriented (CON) mode.

[0013] If the security level code is 4-12, then the transmission mode is determined to be connectionless CL mode;

[0014] If the protocol adaptation code indicates mandatory reliable transmission, then the transmission mode is determined to be connection-oriented (CON) mode.

[0015] Furthermore, the step of allocating channel resources for the control information based on the security level code includes:

[0016] If the security level code is 1-3, a VDE sub-channel with a bandwidth of 45kbps is allocated to the control information for emergency data transmission;

[0017] If the security level code is 4-12, maintain the current channel transmission.

[0018] Furthermore, the third bit of the feature code is the sampling frequency code, including high-frequency code and low-frequency code, and the method further includes:

[0019] If the characteristic code includes a high-frequency code, then a fixed time slot of the VDES channel is allocated to the control information;

[0020] If the characteristic code includes a low-frequency code, then the same time slot is allocated to multiple control information items.

[0021] Secondly, this application provides a method for exchanging maritime traffic control information, applied to ship equipment, the method comprising:

[0022] Obtain raw control data elements;

[0023] Based on the business attributes, scenario types, and preset standards of the original control data elements, a 19-bit CIMCS code is generated. The code includes a 1-2 digit topic domain code, a 3-4 digit scenario code, a 5-7 digit feature code, an 8-digit standard system code, a 9-10 digit standard code, an 11-12 digit security level code, a 13-14 digit protocol adaptation code, and a 15-19 digit data element sequence number.

[0024] Based on the security level code and the protocol adaptation code, the transmission mode of the SECOM protocol is determined according to a predefined mapping rule table; wherein, the transmission mode includes connection-oriented CON mode and connectionless CL mode;

[0025] The original control data elements are encapsulated according to the transmission mode to generate control information;

[0026] The control information is sent to the shore-based equipment.

[0027] Furthermore, based on the security level code and the protocol adaptation code, and according to a predefined mapping rule table, the transmission mode of the SECOM protocol is determined, including:

[0028] Based on the security level code and the protocol adaptation code, the transmission mode is determined by querying the mapping rule table using a dynamic switching trigger integrated into the encapsulation layer.

[0029] Furthermore, if the security level code is 1-3, then the transmission mode is connection-oriented (CON) mode;

[0030] If the security level code is 4-12, then the transmission mode is determined to be connectionless CL mode;

[0031] If the protocol adaptation code indicates mandatory reliable transmission, then the transmission mode is determined to be connection-oriented (CON) mode.

[0032] Thirdly, this application provides an interactive device for water traffic control information, the device comprising:

[0033] The acquisition module is used to acquire control information, which carries a 19-bit code, including a 1-2 digit topic domain code, a 3-4 digit scene code, a 5-7 digit feature code, an 8-digit standard system code, a 9-10 digit standard code, an 11-12 digit security level code, a 13-14 digit protocol adaptation code, and a 15-19 digit data element sequence number.

[0034] The first determining module is used to determine the data format based on the standard system code and the standard code, as well as the preset encoding-standard mapping relationship;

[0035] The second determining module is used to determine the transmission mode of the SECOM protocol based on the security level code and the protocol adaptation code, wherein the transmission mode includes connection-oriented CON mode and connectionless CL mode.

[0036] A channel allocation module is used to allocate channel resources to the control information according to the security level code;

[0037] The data interaction module is used to interact with the ship through the channel resources according to the data format and the transmission mode.

[0038] Fourthly, this application provides an interactive device for water traffic control information, the device comprising:

[0039] The acquisition module is used to acquire raw control data elements;

[0040] The encoding generation module is used to generate a 19-bit CIMCS code based on the business attributes, scenario type, and preset standards of the original control data elements. The code includes a 1-2 digit topic domain code, a 3-4 digit scenario code, a 5-7 digit feature code, an 8-digit standard system code, a 9-10 digit standard code, an 11-12 digit security level code, a 13-14 digit protocol adaptation code, and a 15-19 digit data element sequence number.

[0041] The transmission mode determination module is used to determine the transmission mode of the SECOM protocol based on the security level code and the protocol adaptation code, according to a predefined mapping rule table; wherein, the transmission mode includes connection-oriented CON mode and connectionless CL mode;

[0042] The encapsulation module is used to encapsulate the original control data elements according to the transmission mode to generate control information;

[0043] The sending module is used to send the control information to the shore-based equipment.

[0044] Fifthly, this application provides an electronic device, including: a memory and a processor;

[0045] The memory stores computer-executed instructions;

[0046] The processor executes computer execution instructions stored in the memory, causing the processor to perform various possible implementations of the first and / or second aspects described above.

[0047] In a sixth aspect, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement various possible embodiments of the first and / or second aspects described above.

[0048] In a seventh aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements various possible implementations of the first and / or second aspects described above.

[0049] This application provides a method, apparatus, and electronic device for exchanging maritime traffic control information. The method includes: acquiring control information carrying a 19-bit code, the code comprising a 1-2 digit subject field code, a 3-4 digit scene code, a 5-7 digit characteristic code, an 8-digit standard system code, a 9-10 digit standard code, an 11-12 digit security level code, a 13-14 digit protocol adaptation code, and a 15-19 digit data element sequence number; determining a data format based on the standard system code and the standard code, and a preset code-standard mapping relationship; determining a SECOM protocol transmission mode based on the security level code and the protocol adaptation code, the transmission mode including a connection-oriented (CON) mode and a connectionless (CL) mode; allocating channel resources for the control information based on the security level code; and exchanging data with a vessel through the channel resources based on the data format and the transmission mode. The 19-bit encoding field directly maps to international standards and local specifications. Local supplementary fields can be distinguished by data element sequence numbers, taking into account both international mutual recognition and local needs. The encoding embeds transmission-related fields, which can determine the transmission mode and priority without additional parsing, supporting VDES channel differentiation scheduling and improving channel utilization. Attached Figure Description

[0050] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0051] Figure 1 A flowchart illustrating an interactive method for water traffic control information provided in this application;

[0052] Figure 2 A flowchart illustrating the encoding parsing and communication adaptation process provided for this application;

[0053] Figure 3 A schematic diagram of the structure of an interactive device for water traffic control information provided in this application. Figure 1 ;

[0054] Figure 4 A schematic diagram of the structure of an interactive device for water traffic control information provided in this application. Figure 2 ;

[0055] Figure 5 A schematic diagram of the structure of the electronic device provided in this application.

[0056] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0057] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0058] This invention aims to solve the problems of chaotic existing coding systems, poor international compatibility, and lack of communication adaptation. It provides a coding design scheme based on the Ship-Shore Intelligent Control Coding Specification (CIMCS) to achieve the integration of unique identification, standard traceability, business association, and communication adaptation of intelligent control data for water traffic.

[0059] The CIMCS coding specification does not exist in isolation, but rather deeply integrates the three core dimensions of data metadata standards. It concretizes the requirements of standard association, semantic specification, and quality constraints into fixed fields in the coding structure, so that the standardized attributes of data can be intuitively reflected through coding without the need for additional metadata queries. This design concept of "embedded standard attributes in coding" is different from the single function of traditional coding, which only serves as a unique identifier.

[0060] The core of the CIMCS coding system lies in addressing the three major pain points of maritime data management:

[0061] First, it solves the problem of "data silos" by using unified coding to achieve unique identification of data across scenarios and systems. For example, the "ship MMSI" is coded consistently in control, pilotage, and operation scenarios to ensure unambiguous data interaction.

[0062] Second, it supports "international mutual recognition". The "standard code" field in the encoding directly maps to international standard identifiers, enabling foreign systems to quickly identify the international standards associated with the data through encoding, reducing the cost of manual transcoding.

[0063] Third, it empowers "communication scheduling." The "security level code" in the encoding directly provides a basis for VDES channel scheduling, enabling priority transmission of emergency data without the need for additional data content parsing to determine transmission priority. This "one-time encoding, multi-dimensional adaptation" design significantly improves the management efficiency of the entire data lifecycle and is a significant breakthrough in data standardization technology in this research.

[0064] CIMCS encoding is the core identification system for data elements. The encoding system adopts a "hierarchical and progressive, multi-dimensional association" design approach. The 19-bit encoding structure consists of "subject domain code, scenario code, characteristic code, standard system code, standard code, security level code, protocol adaptation code, and data element sequence number." CIMCS encoding achieves integrated identification of "business affiliation - standard traceability - transmission priority." The encoding parsing logic and example are as follows:

[0065] Subject domain code (1-2 digits): 01=Environmental perception domain, 02=Navigation support domain, 03=Control and management service domain, and newly added 04-09 reserved domains;

[0066] Scene code (3-4 digits): Scene number under the theme domain (e.g., 0102 = Ice Condition Scene). Added 14-15 scene codes (14 = Navigation Beacon Failure Alarm, 15 = Intelligent Berthing Dispatch) to adapt to emergency and safety scenarios.

[0067] Feature code (5-7 digits, newly added): Timeliness (1-3: Real-time / Near-real-time / Regular) + Security (1-4: Urgent / Important / Regular / Public) + Frequency (1-3: High frequency / Medium frequency / Low frequency);

[0068] Standard system code (8 digits, newly added): 1=IHO S-100, 4=IHO S-127, 5=IALA S-212, 6=IMO UMDM, directly associated with the international standard system;

[0069] Standard code (9-10 digits, newly added): corresponds to the standard chapter number;

[0070] Security level code (digits 11-12): IALA S-212 Security Level 12 (01=Level 1 Extreme Emergency, 12=Level 12 Normal), 00 indicates no association;

[0071] Protocol adapter code (bits 13-14, newly added): SECOM data object code (02=navigation parameters, 03=safety warnings, 04=equipment status).

[0072] Data element sequence number (15-19 bits): 00000-00999 = required for international standards, 01000-09999 = required for local supplements, 10000-99999 = extended data element.

[0073] Coding Example Analysis 1 (Emergency Scenario)

[0074] The data metadata code for the extreme emergency malfunction alarm of navigation aids is “021412140601030015”. The parsing link is: 02 (navigation support domain) → 14 (navigation aid malfunction alarm scenario) → 121 (real-time / important / high frequency) → 4 (S-127) → 06 (corresponding chapter number of S-127) → 01 (S-212 security level) → 03 (SECOM security warning object) → 0015 (required for local supplementation), which fully matches the requirements of S-127 and S-212.

[0075] Encoding Example Analysis 2 (Common Scenario)

[0076] The Yangtze River main channel navigation permit number data element code "0301112139006020001" has the following parsing link: 03 (control service domain) → 01 (control scenario) → 112 (real-time / normal / medium frequency) → 1 (S-100 system) → 39 (JT / T 1390) → 06 (S-212) → 02 (SECOM navigation parameter object) → 0001 (international standard required), realizing the integration of international standards and local regulations.

[0077] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0078] Figure 1 A flowchart illustrating an interactive method for water traffic control information provided in this application is shown below. Figure 1 As shown, the steps on the shipboard equipment side include S101-S105, and the steps on the shore-based equipment side include S106-S110. The specific steps are as follows:

[0079] S101. Obtain the original control data elements.

[0080] The original control data elements include at least one of the following: environmental perception data, with data sources including meteorological satellites, hydrological monitoring stations, ice condition radar, etc.; navigation support data, with data sources including navigation aids, electronic chart systems, pilot terminals, etc.; and control service data.

[0081] Real-time monitoring: Obtain vessel dynamics (position, heading, speed, IMO number, call sign, etc.), traffic flow density, and conflict warning level from VTS workstations, radar tracking servers, and AIS base stations.

[0082] Instructions / Notifications: Traffic organization instructions, anchorage allocation, port entry / exit permits, special operations permits, and weather / sea condition warnings generated by VTS operators or automated systems.

[0083] Event-triggered messages include: distress (MAYDAY), emergency (PAN-PAN), and security (SECURITY) messages, as well as reports of abnormalities by the vessel (such as loss of control or grounding risk).

[0084] Periodic reports include: port status, tides, hydrology, visibility, and changes in temporary navigation aids.

[0085] Data cleaning and standardization: unify coordinate system (WGS84), timestamp (UTC), units (knots, degrees, meters), and ship identification (MMSI / IMO), eliminate invalid / duplicate data, and form structured "data elements".

[0086] Based on the collected data, one or more custom structured raw control data elements are obtained, which may include: message type (distress / instruction / notification / report), priority / urgency level (preliminary assessment), target object (all vessels / specific MMSI / a certain sea area), effective time window, and specific content (text, latitude and longitude sequence, numerical value, etc.).

[0087] S102. Based on the business attributes, scenario types, and preset standards of the original control data elements, generate a 19-bit CIMCS code. The code includes a 1-2 digit topic domain code, a 3-4 digit scenario code, a 5-7 digit characteristic code, an 8-digit standard system code, a 9-10 digit standard code, an 11-12 digit security level code, a 13-14 digit protocol adaptation code, and a 15-19 digit data element sequence number.

[0088] In this step, the raw data elements are compressed and mapped in a "self-describing" manner into 19-bit fixed-length CIMCS codes, serving as an "identity card + intent tag" for the transmitted metadata. This allows the receiving end to quickly parse the intent and transmission requirements without having to parse the complete payload each time. Specifically, the process involves: determining the subject domain code and scenario code based on the data element's "message / content keywords / triggering conditions" through table lookup or rule matching; determining the characteristic code based on whether a receipt is required, timeliness requirements, frequency, and whether broadcasting is involved; filling in the standard system code and standard code according to applicable international / national standards; mapping the security level code according to the business urgency level (distress > collision avoidance instruction > general warning > periodic report); and filling in the protocol adaptation code according to mandatory standards or special business requirements.

[0089] Pre-set preset standards can automatically identify and convert raw control data elements to generate CIMCS codes. The preset standards are introduced below.

[0090] The subject domain is the top-level classification of the dataset, representing the aggregation of common business characteristics across scenario clusters. Based on the common business characteristics and control objectives of 10 core scenarios, it is divided into three major categories: "Environmental Awareness Domain (01)," "Navigation Support Domain (02)," and "Control Service Domain (03)." The domains are coded using two-digit identifiers to ensure concise classification and ease of expansion. The classification is based on the core functions of each scenario.

[0091] 1. The environmental perception domain focuses on "navigation environment situational awareness," covering three scenarios: meteorology, ice conditions, and hydrology. It provides basic environmental data such as wind, waves, ice, and water to support the prediction of ship risks.

[0092] 2. The navigation support domain focuses on "navigation process support," covering three scenarios: navigation aids, nautical charts, and pilotage. It primarily provides navigation data such as navigation marks, electronic nautical charts, and pilotage services to support precise navigation.

[0093] 3. The control and management service domain focuses on "proactive control and emergency response", covering four types of scenarios: control, operation, warning and maintenance. It provides core control data such as navigation instructions, operation status and emergency warnings to support efficient scheduling and risk management.

[0094] Table 1. Correspondence between subject areas and scene classes and coding rules

[0095]

[0096] Scenario-based business coverage (excluding extended or non-core businesses):

[0097] Meteorological Scenario (0101): The business scope is "meteorological element monitoring (wind speed / visibility / air pressure) + special weather warning (typhoon / rainstorm / fog)", with the core output being navigation meteorological support data; excluding non-maritime businesses such as scientific research analysis of meteorological data (such as climate modeling) and agricultural meteorological services.

[0098] Ice Condition Scenario (0102): The business scope is "real-time monitoring of ice thickness / ice speed + ice condition level assessment (S-212 standard) + navigation recommendations in ice areas", focusing on supporting navigation safety in ice areas; excluding ice area ecological protection data (belonging to the extended fields of hydrological scenarios) and ice operation scheduling (non-maritime core business).

[0099] Hydrological Scenario (0103): The business scope is "monitoring of hydrological elements (water level / flow velocity / sediment content) + estuary tide forecasting + collection of basic water quality indicators (COD / dissolved oxygen)", supporting waterway depth assurance and pollution prevention early warning; excluding ecological businesses such as water conservancy project scheduling and aquatic life protection without hydrological data.

[0100] Navigation assistance scenario (0201): The business boundary is "navigation mark status monitoring (light cycle / fault type) + navigation assistance information release (navigation mark position / range) + AtoN device remote diagnosis", with the core guarantee of navigation accuracy; excluding the maintenance of navigation mark physical entities (belonging to the maintenance scenario) and the management of non-standard navigation assistance facilities (such as temporary buoys).

[0101] Chart Scenario (0202): The business scope is "electronic chart update (S-57 format vector data) + channel depth marking + no-navigation zone marking", providing standardized basic navigation data; excluding personalized editing of chart data (such as marking of ship-owned routes) and historical chart archive query.

[0102] Pilotage Scenario (0203): The business scope is "pilot request acceptance + pilot dispatch (experience level matching) + boarding position confirmation + service quality feedback", covering the entire pilotage service process; it shares ship MMSI data with the control scenario, but does not include pilot qualification training.

[0103] Control scenario (0301): The business scope is "navigation permit approval + traffic dispatch instruction issuance + vessel violation recording and handling", focusing on waterway traffic order control; excluding port internal berth allocation (belonging to the operation scenario) and vessel safety inspection.

[0104] Operation Scenario (0302): The business boundary is "port operation scheduling (berth allocation / lifting plan) + dangerous goods loading and unloading status monitoring + operation progress feedback", which is corely connected to port production and maritime safety; it does not include operation equipment maintenance and ship cargo customs declaration.

[0105] Warning Scenario (0303): The business boundary is "emergency risk warning (oil spill / collision / sudden ice condition change) + warning information release (affected area coordinate marking) + emergency response linkage notification", focusing on rapid risk transmission; excluding emergency rescue command (under the Maritime Emergency Center) and accident investigation and tracing.

[0106] Maintenance Scenario (0304): The business scope is "navigation aid maintenance plan formulation + equipment failure repair record + maintenance quality assessment (S-421 indicator)", which supports the continuous effectiveness of navigation aids / general aviation facilities; excluding maintenance material procurement and large equipment upgrades and renovations.

[0107] The above shows the correspondence between data elements and subject domain codes and scene codes.

[0108] Each scenario category clearly defines the corresponding core international standards / local specifications to ensure that data requirements are accurately aligned with standards and avoid "standards being out of touch with scenarios".

[0109] S103. Based on the security level code and protocol adaptation code, determine the transmission mode of the SECOM protocol according to the predefined mapping rule table; wherein, the transmission mode includes connection-oriented CON mode and connectionless CL mode.

[0110] Based on the key fields in the encoding, it automatically determines whether to use SECOM's connection-oriented (CON) or connectionless (CL) mode, and can also determine the corresponding parameters (priority, number of retransmissions, timeout, queue, etc.).

[0111] The mapping rule table defines the transmission modes corresponding to different codes.

[0112] In one implementation, if the protocol adaptation code is 01, indicating mandatory reliable transmission, then the transmission mode is determined to be connection-oriented (CON) mode.

[0113] When the protocol adaptation code is non-mandatory reliable transmission, if the security level code is 1-3, the transmission mode is connection-oriented (CON) mode; if the security level code is 4-12, the transmission mode is determined to be connectionless (CL) mode.

[0114] In some embodiments, different retransmission counts are set for different protocol adapter codes and security level codes in the mapping rule table, and the corresponding retransmission count can be determined based on the encoding.

[0115] S104. Encapsulate the original control data elements according to the transmission mode to generate control information.

[0116] The original control data elements and the generated CIMCS encoded header are packaged according to the SECOM protocol format to generate complete control information (SECOM PDU / message packet), ready to be sent to the VDES physical layer sending module.

[0117] If in CON mode, establish / reuse a SECOM session (involving handshake, authentication, and key negotiation). Encapsulation: SECOM header (containing message ID, sequence number, and CIMCS 19-bit encoding) + encrypted payload (raw data elements, possibly compressed / fragmented) + MIC (Message Integrity Code), and add an ARQ (Automatic Retransmission Request) mechanism.

[0118] In CL mode, no session is required; single packets or a small number of retransmissions are performed directly. Encapsulation: SECOM datagram header + CIMCS encoding + payload (plaintext optional) + optional checksum.

[0119] S105. Send control information to shore-based equipment.

[0120] Control information is transmitted via the VDES wireless link.

[0121] S106. The shore-based equipment acquires control information. The control information carries a 19-bit code, which includes a 1-2 digit subject domain code, a 3-4 digit scene code, a 5-7 digit characteristic code, an 8-digit standard system code, a 9-10 digit standard code, an 11-12 digit security level code, a 13-14 digit protocol adaptation code, and a 15-19 digit data element sequence number.

[0122] The shore-based system receives radio signals via a pre-configured radio frequency channel (VDES VDE-TER, satellite link, or others). Signal demodulation, synchronization, error correction, and frame extraction are performed to obtain a complete SECOM (or compatible) PDU. The crucial 19-bit encoding is then extracted from the message.

[0123] S107. Determine the data format based on the standard system code and standard code, as well as the preset encoding-standard mapping relationship.

[0124] The shore-based system queries its internally pre-built "encoding-standard mapping table" and determines the specific data format / encoding rule that the payload should adopt based on the standard hierarchical code (8th bit) + standard code (9th-10th bits) (e.g., 1=IHO S-100, 4=IHO S-127, 5=IALA S-212, 6=IMO UMDM). It then loads the corresponding decoder / parser module to prepare for structured parsing of the payload.

[0125] S108. Determine the transmission mode of the SECOM protocol based on the security level code and protocol adaptation code. The transmission modes include connection-oriented CON mode and connectionless CL mode.

[0126] Read the security level code (bits 11-12) and protocol adaptation code (bits 13-14) from the 19-bit encoding. A protocol adaptation code of 0 or 1 indicates mandatory reliable transmission, thus determining the transmission mode as connection-oriented (CON) mode. If the protocol adaptation code indicates non-mandatory reliable transmission, and the security level code is 1-3, the transmission mode is connection-oriented (CON) mode; if the security level code is 4-12, the transmission mode is connectionless (CL) mode.

[0127] A dynamic switching trigger for the SECOM protocol based on CIMCS encoding is designed. This trigger is integrated into the protocol encapsulation layer and automatically adjusts the SECOM transmission mode and parameter configuration by parsing the feature code and security level code of the CIMCS encoding, without manual intervention. For example, in a port pilotage scenario, when a ship sends a "pilotage request" data (CIMCS encoding 131412140602060001, feature code 131 represents "real-time / important / medium frequency", security level 006), the trigger identifies its "control class" attribute, automatically starts the SECOM CON mode and configures the retransmission count to 2, ensuring that the request is accurately received by the VTS center. When the VTS center reports "pilot has been dispatched and is expected to arrive in 30 minutes," the trigger detects the "feedback stage" attribute and automatically switches to CL mode. Only one-way transmission of results is required, reducing channel occupancy by 50%. The mode switching time is ≤0.3s, far less than the data transmission cycle, and does not affect the normal transmission of subsequent data.

[0128] S109. Allocate channel resources for control information according to the security level code.

[0129] The "golden time" for maritime emergency response is typically no more than 5 minutes. Therefore, it is crucial to ensure channel access for Level 1 data (such as red ice warnings and ship collision alerts) to avoid delays in emergency information caused by regular data occupying the channel. This solution adheres to the principle of "life first, safety paramount," and constructs a three-level channel preemption rule based on the CIMCS security level code. Hardware-level signal triggering ensures the transmission priority of Level 1 data. The specific mechanism is as follows:

[0130] 1) Preemption Trigger. When Level 1 data (security level code 001-003) arrives at the channel scheduling module, the module immediately sends a "breakpoint save + channel release" signal to the Level 2 / 3 data currently occupying the channel, forcibly interrupting the transmission and saving the breakpoint information of the current data (such as the number of bytes transmitted and the check bit), ensuring that subsequent transmission can be resumed. The preemption trigger response time is ≤0.1s.

[0131] 2) Channel Allocation. A dedicated VDE sub-channel (45kbps bandwidth) is allocated for Level 1 data. This channel is normally used only for emergency data transmission and is not allowed to be used by Level 2 / 3 data. After the emergency data transmission is completed (usually ≤2s), the channel scheduling module immediately releases the VDE channel and calls the breakpoint resume mechanism to restore the interrupted Level 2 / 3 data transmission to avoid data loss.

[0132] 3) Preemption constraint. To avoid conflicts caused by multiple emergency data concurrently preempting, a "single channel, single preemption" rule is set, allowing only one Level 1 data to occupy the VDE channel at the same time; when multiple Level 1 data arrive concurrently, they are scheduled by FIFO (first-in, first-out) queue and transmitted in order of data reception time, with queue waiting delay ≤0.5s, ensuring that all emergency data can be transmitted in a timely manner.

[0133] S110. Based on the data format and transmission mode, conduct data interaction with the ship through channel resources.

[0134] The shore-based system has already determined the data format and transmission mode. If it is in CON mode and the service requires confirmation / acknowledgment / command, the shore-based system constructs a response message (also carrying 19-bit encoding), organizes the payload according to the same or negotiated format, and sends it to the ship through the allocated (or newly allocated) channel resources.

[0135] If it is in CL mode or one-way reporting, the main tasks are receiving, parsing, and recording, and downlink response may not be generated.

[0136] The entire interaction is based on VDES or other links to complete physical layer round trips.

[0137] This solution has the following advantages:

[0138] Unique Identifier and Business Association: The 19-bit hierarchical coding enables precise positioning of data elements based on their business affiliation and scenario type. The coding itself is "self-descriptive," containing all key information related to business, standards, security, and transmission, ensuring unambiguous data interaction across scenarios and systems.

[0139] International compatibility and local adaptation: The coded fields directly map to international standard systems and local specifications, with an international standard compatibility rate of ≥99%. International vessels can recognize S-127 / S-212 data by looking at the first half (subject-standard system code-standard code). Local supplementary fields can be distinguished by data element sequence numbers, taking into account both international mutual recognition and local needs.

[0140] Highly efficient communication adaptation: The encoding embeds transmission-related fields, which can determine the transmission mode and priority without additional parsing. It supports VDES channel-differentiated scheduling, with emergency data latency ≤3s and channel utilization ≥85%.

[0141] Full-process traceability: The standard basis, collection characteristics, and security level of data elements can be traced through the coded fields, and the data quality can be controlled to meet the requirements of the S-421 standard.

[0142] Cross-system zero-ambiguity interaction: Maritime systems from different manufacturers and provinces can be used directly without manual transcoding as long as the CIMCS parsing module is implemented.

[0143] VDES friendly: Security level code + feature code directly map to SECOM mode (CON / non-acknowledgment / broadcast), priority queue, and repetition count.

[0144] The VDES system transmits data by dividing the VHF DATA EXCHANGE (VDE, bandwidth 45kbps), AIS1 (161.975MHz), and AIS2 (162.025MHz) into three sub-channels. The total available bandwidth is limited and susceptible to electromagnetic interference from ship radar (X / S band), port VHF communications, fishery radios, and other equipment. In densely populated shipping areas such as ports, the bit error rate caused by channel interference can reach 10%. -4 This far exceeds the requirements for secure transmission. Based on the priority and transmission characteristics of the scenario data, this solution designs a collaborative scheduling strategy of "priority preemption + time slot allocation" to improve channel utilization and transmission reliability.

[0145] It should be noted that the priority corresponds to the security level, with security level codes ranging from 1 to 3, corresponding to the highest priority.

[0146] Figure 2 The flowchart illustrating the encoding parsing and communication adaptation provided in this application is as follows: Figure 2 As shown, the process includes: after inputting the encoded data, performing feature encoding parsing, and then determining the security level. Based on the security level determination, SECOM protocol mode and VDES channel scheduling are then performed.

[0147] Example of implementation method:

[0148] Encoding system construction: Based on GB / T 18391.1-2022 and international standards, the length, value range and encoding rules of each field of the 19-bit encoding are determined, and an encoding dictionary is established.

[0149] Encoding generation: When data elements are collected, the encoding rules are automatically matched to generate CIMCS codes based on information such as their subject domain, scenario, and associated standards. For example, the data element code for an extreme emergency fault alarm of a navigation beacon is "021412140601030015".

[0150] Encoding and parsing: The receiving end extracts information from each field through the encoding and parsing module to determine the business attributes, standard basis, and transmission requirements of the data elements.

[0151] Standard association and communication adaptation implementation: Locate the standard clause by querying the mapping table through the encoding field; trigger the SECOM protocol dynamic switching trigger, and configure the transmission mode and parameters according to the encoding field. For example, Level 1 security data uses CON mode and the number of retransmissions is 3.

[0152] Encoding verification: The verification module performs format, range, and association verification on the encoding. Encodings that do not meet the rules are marked as abnormal, triggering the correction mechanism.

[0153] The channel allocation method has already been introduced in step S109. The time slot allocation will be further introduced below.

[0154] The VDES channel uses a fixed 12.5ms time slot structure. Traditional random time slot allocation methods easily lead to the problem of "high-frequency data queuing and low-frequency data wasting time slots." This solution, based on the scene data acquisition frequency (corresponding to the third bit of the feature code in CIMCS encoding: high frequency 1 / medium frequency 2 / low frequency 3), adopts a hybrid allocation mode of "fixed time slot + dynamic time slot," improving channel utilization through "on-demand allocation and precise scheduling." The specific strategy is as follows:

[0155] Dedicated fixed time slots are allocated for high-frequency routine data (collection frequency ≤ 10 minutes, such as meteorological every 5 minutes and hydrological every 10 minutes). The time slot position is synchronized with the collection frequency. For example, meteorological data is fixed in the 1st to 3rd time slots at 00 / 05 / 10 / 15 minutes of each hour (each time slot is 12.5ms, totaling 37.5ms). The time slot length is dynamically adjusted according to the data volume (usually 2-5 time slots) to ensure stable transmission of periodic data and avoid transmission delays caused by time slot contention.

[0156] Dynamic time slots are allocated for data in sudden scenarios (without a fixed collection frequency, such as navigational aid malfunctions or temporary pilotage requests), using a "request-as-you-go - allocate-release-after-use" mechanism. Upon arrival, data sends a time slot request to the scheduling module. The module detects available time slots and allocates resources within 10ms, with a request response time of ≤0.2s. The time slot is released immediately after data transmission is complete, avoiding the waste of fixed time slots.

[0157] For low-frequency data (collection frequency ≥ 1 hour, such as daily updates of nautical charts and hourly updates of ship static information), time slot multiplexing technology is used to package multiple low-frequency data into one VDES long frame (≤ 1024 bytes), which shares the same time slot with other low-frequency data for transmission, reducing channel fragmentation occupation. For example, three ship static information (200 bytes each) can be packaged into one 600-byte long frame, which only occupies one time slot to complete the transmission, saving two time slots compared to transmitting them separately.

[0158] The SECOM protocol, defined by the IEC 63173-2 standard as a dedicated maritime data transmission protocol, possesses two core modes: "Connection-Oriented (CON)" and "Connectionless (CL)". However, traditional applications often use a single mode to transmit all data, leading to the problem of "high packet loss rate for emergency data in CL mode and excessive bandwidth consumption for routine data in CON mode". This solution, based on the characteristics of the SECOM protocol and combined with the structured information of CIMCS encoding, establishes a four-dimensional dynamic encoding-standard mapping relationship: "CIMCS encoding characteristics - SECOM transmission mode - data priority - protocol parameters". This achieves precise matching between protocol configuration and scenario data characteristics, ensuring the reliability of high-security data while improving the transmission efficiency of routine data. The mapping rules and technical details are as follows:

[0159] Table 2. Protocol Layer Mapping Rules and Technical Details

[0160]

[0161] During encoding, based on the matching scenario and channel characteristics, and combining the transmission requirements of 10 scenarios (emergency / regular / interactive) with the narrowband channel characteristics of VDES (45-90kbps), differentiated technical parameters are designed to ensure "low latency for emergency data, high compression for regular data, and strong correlation for interactive data":

[0162] 1. Emergency-related data elements (ice thickness, collision warning):

[0163] Accuracy: 0.1m (ice thickness), 1m (collision distance);

[0164] Data collection frequency: 1 second / time (in case of an emergency), 5 seconds / time (in case of a routine emergency);

[0165] Data volume: ≤256 bytes / data (ASN.1 PER encoding, 40% compression rate improvement over XML);

[0166] Transmission mode: SECOM CON mode (with retransmission mechanism, packet loss rate ≤0.5%).

[0167] 2. Conventional data elements (meteorological "wind speed", hydrological "water level"):

[0168] Accuracy: 0.1m / s (wind speed), 0.01m (water level);

[0169] Data collection frequency: 5 min / time (meteorological), 10 min / time (hydrological);

[0170] Data volume: ≤1024 bytes / strip (JSON format, differential encoding compression, redundancy <10%).

[0171] Transmission mode: SECOM CL mode (connectionless, channel utilization increased to 88%).

[0172] 3. Interactive data elements (pilotage "boarding position", operations "berth occupancy status"):

[0173] Accuracy: 0.00001° (wheel-mounting coordinates), 1% (work progress);

[0174] Data collection frequency: 1 time / piloting process (boarding position), 1 minute / time (operation status);

[0175] Data volume: ≤512 bytes / data item (JSON-LD format, supports semantic association);

[0176] Transmission mode: SECOM CON / CL dual mode (CON is used for pilotage requests, and CL is used for status feedback).

[0177] For raw control data elements, the source device and verification rules must be clearly defined to avoid problems such as "unreliable data" and "inconsistent format".

[0178] Data source:

[0179] Environmental sensing equipment: meteorological satellites, X-band ice condition radar, and hydrological monitoring stations;

[0180] Navigation support equipment: navigation aid terminal (IALA AtoN standard), electronic chart system (S-57 format), pilot handheld terminal (compliant with JT / T 1455-2023);

[0181] Control and management services: VTS system (IHO S-127 compatible), port operation platform (GB / T 37948-2019).

[0182] Verification rules:

[0183] Format validation: Timestamps must conform to the UTC standard, and location data must be WGS84 coordinates. If they do not conform, mark them as "to be cleaned".

[0184] Range verification: Data with wind speed > 70m / s and ice thickness > 3m are considered outliers and trigger the retransmission mechanism;

[0185] Association verification: The navigation permit number must be associated with the vessel's MMSI. If there is no match, the entry will be rejected to avoid "permit mismatch with vessel".

[0186] Based on the four-in-one architecture of "basic data element (S-100) - VTS data element (S-127) - security data element (S-212) - extended data element (UMDM / CMDS)," a dynamic association mechanism between data elements and standards is established. Each data element adds "standard system identifier" and "encryption trigger rule" fields. The association table is as follows:

[0187] Table 3. Data Elements and their Correspondence with S-127 / S-212 Standards

[0188]

[0189] Below, using two typical maritime business operations as examples, a full-link association table is constructed to intuitively demonstrate the practical value of CIMCS coding:

[0190] Table 4. End-to-End Association Table

[0191]

[0192] Figure 3 A schematic diagram of the structure of an interactive device for water traffic control information provided in this application. Figure 1 The device 30 includes:

[0193] The acquisition module 301 is used to acquire control information. The control information carries a 19-bit code, which includes a 1-2 digit topic domain code, a 3-4 digit scene code, a 5-7 digit feature code, an 8-digit standard system code, a 9-10 digit standard code, an 11-12 digit security level code, a 13-14 digit protocol adaptation code, and a 15-19 digit data element sequence number.

[0194] The first determining module 302 is used to determine the data format based on the standard system code and the standard code, as well as the preset encoding-standard mapping relationship;

[0195] The second determining module 303 is used to determine the transmission mode of the SECOM protocol based on the security level code and the protocol adaptation code. The transmission modes include connection-oriented CON mode and connectionless CL mode.

[0196] The channel allocation module 304 is used to allocate channel resources for control information according to the security level code;

[0197] The data interaction module 305 is used to interact with the ship via channel resources according to the data format and transmission mode.

[0198] Optionally, the channel allocation module 304 is also used for:

[0199] If the security level code is 1-3, a VDE sub-channel with a bandwidth of 45kbps is allocated for control information and used for emergency data transmission;

[0200] If the security level code is 4-12, continue transmission on the current channel.

[0201] Optionally, the third bit of the feature code is the acquisition frequency code, including high-frequency code and low-frequency code. The device also includes a time slot allocation module 306, used for:

[0202] If the feature code includes a high-frequency code, then a fixed time slot of the VDES channel is allocated for the control information;

[0203] If the feature code includes a low-frequency code, then the same time slot is allocated to multiple control information.

[0204] The device provided in this embodiment is used to execute the method on the shore-based equipment side in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0205] Figure 4 A schematic diagram of the structure of an interactive device for water traffic control information provided in this application. Figure 2 ,like Figure 4 As shown, the device 40 includes:

[0206] Module 401 is used to acquire raw control data elements;

[0207] The encoding generation module 402 is used to generate a 19-bit CIMCS code based on the business attributes, scenario type and preset standards of the original control data elements. The code includes a 1-2 digit topic domain code, a 3-4 digit scenario code, a 5-7 digit feature code, an 8-digit standard system code, a 9-10 digit standard code, an 11-12 digit security level code, a 13-14 digit protocol adaptation code, and a 15-19 digit data element sequence number.

[0208] The transmission mode determination module 403 is used to determine the transmission mode of the SECOM protocol based on the security level code and protocol adaptation code, according to a predefined mapping rule table; wherein, the transmission mode includes connection-oriented CON mode and connectionless CL mode;

[0209] The encapsulation module 404 is used to encapsulate the original control data elements according to the transmission mode to generate control information;

[0210] The sending module 405 is used to send control information to shore-based equipment.

[0211] Transmission mode determination module 403 is used for:

[0212] Based on security level codes and protocol adaptation codes, a dynamic switching trigger integrated into the encapsulation layer queries a mapping rule table to determine the transmission mode and parameter configuration.

[0213] The apparatus provided in this embodiment is used to execute the method on the ship equipment side in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.

[0214] Figure 5 A schematic diagram of the electronic device provided in this application. This electronic device can be marine equipment or shore-based equipment. Figure 5 As shown, the electronic device 50 provided in this embodiment includes at least one processor 501 and a memory 502. Optionally, the device 50 further includes a communication component 503. The processor 501, memory 502, and communication component 503 are connected via a bus 504.

[0215] In a specific implementation, at least one processor 501 executes computer execution instructions stored in memory 502, causing at least one processor 501 to perform the above-described method.

[0216] The specific implementation process of processor 501 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0217] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0218] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0219] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0220] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described method.

[0221] This application also provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the above-described method.

[0222] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.

[0223] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.

[0224] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.

[0225] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0226] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0227] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0228] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.

[0229] Finally, it should be noted that other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This invention is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein, and is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.

Claims

1. A method for exchanging information on water traffic control, characterized in that, Applied to shore-based equipment, the method includes: Obtain control information, which carries a 19-bit code, including a 1-2 digit topic domain code, a 3-4 digit scene code, a 5-7 digit feature code, an 8-digit standard system code, a 9-10 digit standard code, an 11-12 digit security level code, a 13-14 digit protocol adaptation code, and a 15-19 digit data element sequence number. The data format is determined based on the standard system code and standard code, as well as the preset encoding-standard mapping relationship; Based on the security level code and the protocol adaptation code, the transmission mode of the SECOM protocol is determined, including connection-oriented CON mode and connectionless CL mode. According to the security level code, channel resources are allocated to the control information; According to the data format and the transmission mode, data is exchanged with the ship through the channel resources.

2. The method according to claim 1, characterized in that, The step of determining the SECOM protocol transmission mode based on the security level code and the protocol adaptation code includes: If the security level code is 1-3, then the transmission mode is determined to be connection-oriented (CON) mode. If the security level code is 4-12, then the transmission mode is determined to be connectionless CL mode; If the protocol adaptation code indicates mandatory reliable transmission, then the transmission mode is determined to be connection-oriented (CON) mode.

3. The method according to claim 1, characterized in that, The step of allocating channel resources for the control information according to the security level code includes: If the security level code is 1-3, a VDE sub-channel with a bandwidth of 45kbps is allocated to the control information for emergency data transmission; If the security level code is 4-12, maintain the current channel transmission.

4. The method according to any one of claims 1-3, characterized in that, The third bit of the characteristic code is the sampling frequency code, which includes high-frequency code and low-frequency code. The method also includes: If the characteristic code includes a high-frequency code, then a fixed time slot of the VDES channel is allocated to the control information; If the characteristic code includes a low-frequency code, then the same time slot is allocated to multiple control information items.

5. A method for exchanging information on water traffic control, characterized in that, Applied to marine equipment, the method includes: Obtain raw control data elements; Based on the business attributes, scenario types, and preset standards of the original control data elements, a 19-bit CIMCS code is generated. The code includes a 1-2 digit topic domain code, a 3-4 digit scenario code, a 5-7 digit feature code, an 8-digit standard system code, a 9-10 digit standard code, an 11-12 digit security level code, a 13-14 digit protocol adaptation code, and a 15-19 digit data element sequence number. Based on the security level code and the protocol adaptation code, the transmission mode of the SECOM protocol is determined according to a predefined mapping rule table; wherein, the transmission mode includes connection-oriented CON mode and connectionless CL mode; The original control data elements are encapsulated according to the transmission mode to generate control information; The control information is sent to the shore-based equipment.

6. The method according to claim 5, characterized in that, Based on the security level code and the protocol adaptation code, the transmission mode of the SECOM protocol is determined according to a predefined mapping rule table, including: Based on the security level code and the protocol adaptation code, the transmission mode is determined by querying the mapping rule table using a dynamic switching trigger integrated into the encapsulation layer.

7. The method according to claim 6, characterized in that, If the security level code is 1-3, then the transmission mode is connection-oriented (CON) mode; If the security level code is 4-12, then the transmission mode is determined to be connectionless CL mode; If the protocol adaptation code indicates mandatory reliable transmission, then the transmission mode is determined to be connection-oriented (CON) mode.

8. An interactive device for water traffic control information, characterized in that, The device includes: The acquisition module is used to acquire control information, which carries a 19-bit code, including a 1-2 digit topic domain code, a 3-4 digit scene code, a 5-7 digit feature code, an 8-digit standard system code, a 9-10 digit standard code, an 11-12 digit security level code, a 13-14 digit protocol adaptation code, and a 15-19 digit data element sequence number. The first determining module is used to determine the data format based on the standard system code and the standard code, as well as the preset encoding-standard mapping relationship; The second determining module is used to determine the transmission mode of the SECOM protocol based on the security level code and the protocol adaptation code, wherein the transmission mode includes connection-oriented CON mode and connectionless CL mode. A channel allocation module is used to allocate channel resources to the control information according to the security level code; The data interaction module is used to interact with the ship through the channel resources according to the data format and the transmission mode.

9. An interactive device for water traffic control information, characterized in that, The device includes: The acquisition module is used to acquire raw control data elements; The encoding generation module is used to generate a 19-bit CIMCS code based on the business attributes, scenario type, and preset standards of the original control data elements. The code includes a 1-2 digit topic domain code, a 3-4 digit scenario code, a 5-7 digit feature code, an 8-digit standard system code, a 9-10 digit standard code, an 11-12 digit security level code, a 13-14 digit protocol adaptation code, and a 15-19 digit data element sequence number. The transmission mode determination module is used to determine the transmission mode of the SECOM protocol based on the security level code and the protocol adaptation code, according to a predefined mapping rule table; wherein, the transmission mode includes connection-oriented CON mode and connectionless CL mode; The encapsulation module is used to encapsulate the original control data elements according to the transmission mode to generate control information; The sending module is used to send the control information to the shore-based equipment.

10. An electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-4, or the method as described in any one of claims 5-7.