Ship acoustic compatibility management control method

Abstract

The invention discloses a ship acoustic compatibility management control method, and belongs to the technical field of ocean engineering platform acoustic compatibility, and the method comprises the steps: collecting the working parameters of each piece of acoustic equipment; based on the working parameters of each piece of acoustic equipment, determining whether each piece of working equipment triggers at least one conflict condition; if at least one conflict condition is triggered, respectively creating conflict nodes based on each triggered conflict condition, and adding each conflict node into a conflict linked list; and based on each conflict node in the conflict linked list, generating and executing a management control command corresponding to each conflict node to process each conflict node, and removing the processed conflict node from the conflict linked list until the conflict linked list is empty. Therefore, the method can comprehensively and timely manage and control the acoustic compatibility problem existing between the acoustic devices, and improves the management and control efficiency.

Description

Technical Field

[0001] The present invention belongs to the technical field of marine engineering platform acoustic compatibility, and in particular relates to a ship acoustic compatibility management and control method. Background Art

[0002] In fields such as ocean exploration and underwater engineering, marine engineering platforms (such as ships) require a large number of acoustic devices to perform functions such as target detection, communication, navigation, and ocean mapping. The large number of acoustic devices deployed on these platforms can easily lead to acoustic compatibility issues due to factors such as overlapping operating frequency bands and interference from transmitted sound waves. This is known as acoustic interference, which can lead to a decrease in the performance of the acoustic equipment. Existing technology typically involves operators, upon discovering acoustic compatibility issues with acoustic equipment on marine engineering platforms, adjusting the equipment to reduce acoustic interference between the various devices, achieve acoustic compatibility management and control, and thus ensure the performance of the acoustic equipment. However, this manual intervention method makes it difficult to comprehensively and timely manage and control acoustic compatibility issues between acoustic devices, resulting in low management and control efficiency.

[0003] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of this application, and therefore may include information that does not constitute prior art known to ordinary technicians in this field. Summary of the Invention

[0004] In order to provide a basic understanding of some aspects of the disclosed embodiments, a brief summary is given below. The summary is not an extensive review, nor is it intended to identify key / critical elements or delineate the scope of protection of these embodiments, but rather serves as a prelude to the detailed description that follows.

[0005] The embodiments of the present disclosure provide a method for managing and controlling acoustic compatibility of ships, so as to comprehensively and timely manage and control acoustic compatibility issues existing between acoustic devices, thereby improving the efficiency of management and control.

[0006] In some embodiments, a ship acoustic compatibility management and control method includes: step S101, collecting the working parameters of each acoustic device; step S102, based on the working parameters of each acoustic device, determining whether each working device triggers at least one conflict condition; wherein the working device represents an acoustic device in a working state; step S103, if at least one conflict condition is triggered, creating conflict nodes based on each triggered conflict condition, and adding each conflict node to a conflict list; wherein the conflict node includes a working device group that triggers the same conflict condition and the corresponding working parameters and processing strategies; step S104, based on each conflict node in the conflict list, generating and executing management control commands corresponding to each conflict node to process each conflict node, and removing the processed conflict nodes from the conflict list until the conflict list is empty.

[0007] The beneficial effects of the present invention are: The operating parameters of each acoustic device are collected, and it is determined whether the operating parameters of each working device trigger at least one conflict condition. If triggered, it indicates that there is acoustic interference between the working devices at this time, thereby enabling comprehensive and rapid detection of each working device with acoustic compatibility issues (i.e., acoustic interference). Conflict nodes are then constructed based on the triggered conflict conditions, and each conflict node is added to a conflict list. In order to generate and instruct corresponding management and control commands based on the working device groups and processing strategies of each conflict node in the conflict list, the processed conflict nodes are removed from the conflict list until the conflict list is empty. This allows comprehensive and timely adjustment of the operating parameters of the working device groups with acoustic interference to reduce acoustic interference between the working devices, ensure the working performance of the working devices, and achieve comprehensive and timely management and control of acoustic compatibility issues between working devices, thereby improving management and control efficiency.

[0008] The above general description and the following description are exemplary and explanatory only and are not intended to limit the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] One or more embodiments are exemplarily described by corresponding drawings. These exemplary descriptions and drawings do not limit the embodiments. Elements with the same reference numerals in the drawings are shown as similar elements. The drawings do not constitute a scale limitation. In addition, Figure 1 This is a flow chart of a ship acoustic compatibility management and control method provided by the present invention; Figure 2 This is a workflow diagram for mining frequent items in a global database provided by the present invention; Figure 3 This is a workflow diagram for mining frequent items in a conflict database provided by the present invention; Figure 4 This is a flow chart of clearing a conflict list provided by the present invention; Figure 5 This is another flow chart of clearing the conflict list provided by the present invention; Figure 6 This is another flow chart of clearing the conflict list provided by the present invention; Figure 7 This is a flow chart of another ship acoustic compatibility management and control method provided by the present invention. DETAILED DESCRIPTION

[0010] In order to be able to understand the features and technical content of the embodiments of the present disclosure in more detail, the implementation of the embodiments of the present disclosure is described in detail below in conjunction with the accompanying drawings. The accompanying drawings are for reference only and are not used to limit the embodiments of the present disclosure. In the following technical description, for the sake of convenience of explanation, a full understanding of the disclosed embodiments is provided through multiple details. However, one or more embodiments can still be implemented without these details. In other cases, to simplify the drawings, well-known structures and devices can be simplified for display.

[0011] In the description and claims of the embodiments of the present disclosure, as well as in the accompanying drawings, the terms "first," "second," and the like are used to distinguish similar items and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate to describe the embodiments of the present disclosure herein. In addition, the terms "including," "having," and any variations thereof are intended to cover non-exclusive inclusions.

[0012] Unless otherwise stated, the term "plurality" means two or more.

[0013] In the embodiment of the present disclosure, the character " / " indicates that the preceding and following objects are in an "or" relationship. For example, A / B means: A or B.

[0014] The term "and / or" describes an association between objects, indicating that three relationships can exist. For example, A and / or B means: A or B, or A and B.

[0015] The term "correspondence" may refer to an association relationship or a binding relationship. The correspondence between A and B means that there is an association relationship or a binding relationship between A and B.

[0016] Acoustic compatibility issues arise when multiple acoustic devices installed on an offshore platform interfere with each other (i.e., acoustic interference) when operating simultaneously due to factors such as sound wave radiation, signal characteristics, or spatial layout, resulting in some acoustic devices failing to function properly. Acoustic compatibility management and control involves adjusting the operating parameters of individual acoustic devices on an offshore platform (usually those already in operation) to ensure they function properly and are compatible with each other without causing acoustic interference.

[0017] Combine Figure 1 As shown, the embodiment of the present disclosure provides a ship acoustic compatibility management and control method, including: Step S101 collects the operating parameters of each acoustic device. These parameters include those that can easily cause acoustic interference between devices, such as operating mode, operating frequency band, transmit power, and beam direction. Acoustic interference occurs when sound waves emitted by an acoustic device or signals received by it affect or interfere with other acoustic devices, causing performance degradation of the acoustic devices themselves or each other. For example, if two devices operate in the same frequency band, they will cause acoustic interference.

[0018] Step S102: Based on the operating parameters of each acoustic device, determine whether each working device triggers at least one conflict condition. A conflict condition represents a condition that triggers an acoustic compatibility issue. A working device represents an acoustic device in an operating state. An operating state represents any state other than the shutdown state.

[0019] Step S103: If at least one conflict condition is triggered, conflict nodes are created based on each conflict condition that is triggered, and each conflict node is added to a conflict list. Conflict nodes include the working device group that triggers the same conflict condition and the corresponding working parameters and processing strategies.

[0020] As you can understand, a conflict list is a data structure for managing and resolving conflicts, typically storing information about conflicting nodes in a linked list format. A working device group represents a collection of working devices that trigger the same conflict condition. The operating parameters corresponding to a working device group represent the operating parameters of each working device within the working device group.

[0021] In some embodiments, the conflict status of each conflicting node (e.g., in progress, pending, processed) is also recorded in the conflict list to avoid repeated conflict processing. For example, when creating a conflicting node, the conflict status of the created conflicting node is set to "pending." During the process of generating and executing the management control command corresponding to the conflicting node, the conflict status of the conflicting node is updated to "in progress." The conflict status of the conflicting node corresponding to the executed management control command is updated to "processed." Typically, the conflicting node whose conflict status is updated to "processed" is removed from the conflict list.

[0022] In some embodiments, a method for managing and controlling ship acoustic compatibility further includes determining the conflict status of each conflicting node. Each conflicting node and its conflict status are displayed on a pre-set display interface. This allows personnel to promptly understand each current conflicting node and the handling status of each conflicting node. For example, the corresponding working equipment group, working equipment group operating parameters, handling strategy, and conflict status may be displayed for each conflicting node.

[0023] Step S104 : Based on each conflicting node in the conflict linked list, generate and execute a management control command corresponding to each conflicting node to process each conflicting node, and remove the processed conflicting node from the conflict linked list until the conflict linked list is empty.

[0024] In some embodiments, a management control command representation corresponding to a conflicting node is generated, and the working device group corresponding to the conflicting node is used as the target object of the management control command, and the corresponding processing strategy is used as the management control content of the management control command to generate a management control command. It can be understood that the command generation process is a conventional technology and will not be described in detail here. The execution of the management control command representation adjusts the working parameters of the corresponding working device group based on the management control command until the working parameters of the working device group do not trigger the target conflict condition, and then cancels the management control command. The target conflict condition represents the conflict condition corresponding to the management control command. For example, the working frequency band of working device A is 2000Hz to 3000Hz, and the working frequency band of working device B is 2800Hz to 3600Hz. At this time, there is an acoustic compatibility problem between working device A and working device B due to overlapping working frequency bands. The conflict triggering condition is that the working frequency bands of two working devices overlap, which is frequency interference. The handling strategy is frequency band time-division reuse: Set the operating times for the two devices to time slot 1 (for example, 0-10ms, 20-30ms) and time slot 2 (for example, 10-20ms, 30-40ms). After the adjustment is complete, if devices A and B no longer trigger the conflict condition, the management control command is canceled. Devices A and B now operate according to the adjusted parameters.

[0025] It is understood that an empty conflict list indicates that there are no conflict nodes in the conflict list that need to be processed, that is, there are no conflict nodes or the conflict status of each conflict node is being processed. Typically, when the conflict status of a conflict node is processed, the conflict node will be removed from the conflict list.

[0026] A ship acoustic compatibility management and control method provided by an embodiment of the present disclosure collects the operating parameters of each acoustic device and determines whether the operating parameters of each working device trigger at least one conflict condition. If triggered, it indicates that there is acoustic interference between the working devices at this time, thereby enabling comprehensive and rapid detection of each working device with acoustic compatibility issues (i.e., acoustic interference). Conflict nodes are then constructed based on the triggered conflict conditions, and each conflict node is added to a conflict list. In order to generate and instruct corresponding management and control commands based on the working device groups and processing strategies of each conflict node in the conflict list, the processed conflict nodes are removed from the conflict list until the conflict list is empty. This allows comprehensive and timely adjustment of the operating parameters of the working device groups with acoustic interference to reduce acoustic interference between the working devices, ensure the working performance of the working devices, achieve comprehensive and timely management and control of acoustic compatibility issues between the working devices, and improve management and control efficiency.

[0027] Preferably, based on the working parameters of each acoustic device, determining whether each working device triggers at least one conflict condition includes: determining each working device based on the working parameters of each acoustic device. Based on a preset conflict rule library, detecting whether the working parameters of each working device trigger an interference condition of at least one conflict rule; wherein the conflict rule library contains multiple conflict rules, and the conflict rules include interference conditions and processing strategies; if the interference condition of at least one conflict rule is triggered, it is determined that at least one conflict condition is triggered; wherein one conflict rule corresponds to one conflict condition. The interference condition represents the condition that causes acoustic compatibility issues. The processing strategy represents a strategy for adjusting the working parameters of a group of working devices that meet the corresponding interference condition so that the group of working devices no longer meets the interference condition.

[0028] In this way, by detecting whether the working parameters of each working device trigger the interference conditions of each conflict rule in the conflict rule library, if the interference condition is triggered, it means that there is acoustic interference between the various working devices that meet the interference condition, so that it is possible to comprehensively, quickly and timely detect whether there are acoustic compatibility issues between the various working devices.

[0029] It is understandable that acoustic interference generally occurs between multiple working devices.

[0030] In some embodiments, conflict rules can be set based on expert experience. For example, conflict rule 1: Interference condition: The operating frequency bands of working device A and working device B overlap, which is frequency interference; the processing strategy is frequency band time-division multiplexing: the working time of the two working devices is set to time slot 1 (even time period, such as 0-10ms, 20-30ms) and time slot 2 odd time period, such as 10-20ms, 30-40ms, which is related to the working cycle and transmission pulse width of the two devices. Conflict rule 2: Interference condition: The beam pointing of working device C and working device D overlaps in space, which is airspace interference; processing strategy: adjust the beam pointing of one working device to avoid the main lobe area of ​​the other working device.

[0031] In other embodiments, the interference condition in the conflict rule is determined by: obtaining multiple historical operating events on the entire ship; wherein the historical operating events include acoustic conflict labels and operating parameters of each working equipment within the historical period. Based on the multiple historical operating events, a global database and a conflict database are respectively constructed; wherein the global database includes data corresponding to all historical operating events, and the conflict database includes data corresponding to historical operating events with an acoustic conflict label of yes. The data includes acoustic conflict labels and operating parameters of each working equipment. The Apriori algorithm is used to perform frequent item mining on the operating parameters of each data in the global database and the conflict database, respectively, to obtain corresponding global frequent item sets and conflict frequent item sets, and the global frequent item sets and conflict frequent item sets are merged to obtain a target frequent item set. Based on the parameter items in the target frequent items and the acoustic conflict label of yes, each candidate association rule is generated, and based on the confidence and lift of each candidate association rule, each target association rule is determined and used as the interference condition.

[0032] Among them, the acoustic conflict label includes yes and no. When the acoustic conflict label = yes, it indicates that there is an acoustic compatibility conflict in the historical operation event, that is, there is an acoustic compatibility problem; when the acoustic conflict label = no, it indicates that there is no acoustic compatibility conflict in the historical operation event. For example, in the historical operation event A, acoustic equipment A, acoustic equipment B, acoustic equipment C, and acoustic equipment D are all in working condition, and the working data of acoustic equipment B is obviously different from the normal data (such as noise exceeds the standard), then the acoustic conflict label of the historical operation event is yes, and the working equipment is acoustic equipment A, acoustic equipment B, acoustic equipment C, and acoustic equipment D. For another example, in the historical operation event B, acoustic equipment A, acoustic equipment B, acoustic equipment C, and acoustic equipment D are all in working condition, and the working data of acoustic equipment A to D are normal data, then the acoustic conflict label of the historical operation event is no, and the working equipment is acoustic equipment A, acoustic equipment B, acoustic equipment C, and acoustic equipment D.

[0033] By constructing a global database and a conflict database, and using the Apriori algorithm to mine frequent items for each operating parameter, we can identify common combinations of operating parameters across acoustic devices. The global frequent itemset reflects global characteristics, while the conflict frequent itemset reflects acoustic compatibility conflict characteristics. This prevents the omission of operating parameter combinations that are clearly correlated with acoustic compatibility conflict characteristics when mining the global frequent itemset. Interference conditions are identified by generating candidate association rules and determining target association rules based on their confidence and lift. This approach balances the global characteristics of historical operating events with acoustic compatibility conflict characteristics, allowing for more accurate mining of interference conditions.

[0034] For example, conflict rule 2: [Interference condition: working device C = working mode_mode 1, beam direction_direction 1, working device D = working mode_mode 2, beam direction_direction 1 → acoustic conflict occurs; processing strategy: adjust the beam direction_direction 2 of working device C, or adjust the beam direction_direction 2 of working device D].

[0035] In this embodiment, experts determine corresponding processing strategies based on each interference condition. The interference condition and the corresponding processing strategy are used together as conflict rules. Consequently, when an acoustic compatibility conflict is detected between operating acoustic devices, a target management control command is automatically generated based on the corresponding processing strategy to adjust the operating parameters of the conflicting devices to achieve acoustic compatibility. This reduces operator workload and ensures the vessel's (the entire ship's) underwater combat effectiveness.

[0036] Preferably, the conflict rule also includes a conflict type. Based on expert experience, the conflict type to which the interference condition belongs is determined. That is, the conflict type, interference condition, and corresponding handling strategy are combined as conflict rules. The conflict type characterizes the type of acoustic compatibility conflict, such as operating mode conflict or airspace conflict.

[0037] For example, conflict rule 2: [Interference condition: working device C = working mode_mode 1, beam direction_direction 1, working device D = working mode_mode 2, beam direction_direction 1 → acoustic conflict occurs; processing strategy: adjust the beam direction_direction 2 of working device C, or adjust the beam direction_direction 2 of working device D; conflict type: airspace conflict].

[0038] Preferably, a global database and a conflict database are constructed based on multiple historical operating events. This includes discretizing the operating parameters of each device within each historical operating event. For each historical operating event, the discretized data and the acoustic conflict label are combined as a single data point to construct the basic data and conflict data. Each historical operating event corresponds to one piece of data.

[0039] For example, discretization processing includes: operating mode (e.g., Mode 1, Mode 2), operating frequency band (e.g., Band 1, Band 2), transmit power (e.g., 100W, 200W), and beam direction (e.g., Direction 1, Direction 2). The discretized data of a historical operation event is used as a single data point to construct basic data and conflict data. For example, Data 1: {Operating Parameters [Acoustic Device A = (Operating Mode_Mode1, Operating Frequency Band_Band1, Transmit Power_100W, Beam Direction_Direction1), Acoustic Device B = (Operating Mode_Mode2, Operating Frequency Band_Band2, Transmit Power_200W, Beam Direction_Direction2)], Acoustic Conflict Label = 1}. Data 2: {operating parameters [acoustic device A = (operating mode_mode3, operating frequency band_band2, transmit power_100W, beam direction_direction3), acoustic device B = (operating mode_mode2, operating frequency band_band2, transmit power_200W, beam direction_direction2)], acoustic conflict label = 0}.

[0040] Preferably, combined Figure 2 As shown, the embodiment of the present disclosure provides a workflow diagram for mining frequent items in a global database. The Apriori algorithm is used to mine frequent items from the working parameters of each piece of data in the global database to obtain the corresponding global frequent item set, including: Step S301 : Scan each piece of data in the global database, extract all single parameter items corresponding to the working parameters in each piece of data, and obtain a first candidate item set.

[0041] Step S302 : Calculate the support of each parameter item in the first candidate item set, and take the set of parameter items in the first candidate item set whose support satisfies the first support condition as the first frequent itemset.

[0042] Step S303: self-connect the first frequent itemset and prune it using the Apriori algorithm to generate a new first candidate itemset.

[0043] Step S304: Calculate the support of each parameter item in the new first candidate item set, and take the set of parameter items in the new first candidate item set whose support satisfies the first support condition as a new first frequent item set.

[0044] Step S305 , iteratively executing steps S303 to S304 until no new first frequent item set can be obtained, and merging all first frequent item sets to obtain a global frequent item set.

[0045] In this way, the Apriori algorithm is used to mine the frequent items corresponding to the working parameters in the global database, so that the common working parameter combinations of various acoustic equipment on the entire ship can be obtained, so as to mine accurate interference conditions based on all historical operating events.

[0046] In this embodiment, the single parameter item corresponding to the working parameter is, for example, acoustic device A_working mode = mode 1, acoustic device A_working frequency band = frequency band 1, etc. The first support condition indicates that the support is less than a first support threshold.

[0047] In some embodiments, the support of each parameter item in the first candidate item set is calculated using the following formula: in, is the support of parameter item X, In the global database, including parameter items X The number of data items, The total number of data in the global database.

[0048] Preferably, combined Figure 3 As shown, the embodiment of the present disclosure provides a workflow diagram for mining frequent items in a conflict database. The Apriori algorithm is used to mine frequent items of the working parameters of each data in the conflict database to obtain the corresponding conflict frequent item set, including: Step S401 : Scan each piece of data in the conflict database, extract all single parameter items corresponding to the working parameters in each piece of data, and obtain a second candidate item set.

[0049] Step S402 : Calculate the support of each parameter item in the second candidate item set, and take the set of parameter items in the second candidate item set whose support satisfies the second support condition as the second frequent itemset.

[0050] Step S403: self-connect the second frequent itemset and prune it using the Apriori algorithm to generate a new second candidate itemset.

[0051] Step S404: Calculate the support of each parameter item in the new second candidate item set, and take the set of parameter items in the new second candidate item set whose support satisfies the second support condition as a new second frequent item set.

[0052] Step S405 , iteratively executing steps S403 to S404 until no new second frequent item set can be obtained, merging all second frequent item sets to obtain a conflicting frequent item set.

[0053] In this way, the Apriori algorithm is used to mine the frequent items corresponding to the working parameters in the conflict database, so that the common working parameter combinations of various acoustic equipment on the entire ship can be obtained in the event of acoustic compatibility conflicts, so as to mine accurate interference conditions based on historical operating events where acoustic compatibility conflicts occurred.

[0054] In some embodiments, the second support condition represents that the support is less than a second support threshold.

[0055] In some embodiments, generating each candidate association rule based on the parameter item and the conflict label in the target frequent item includes: constructing the candidate association rule: the antecedent of the candidate association rule → the consequent of the association rule, taking the parameter item of the target frequent item as the antecedent of the candidate association rule, and taking the conflict label = yes as the consequent of the candidate association rule.

[0056] In some embodiments, the confidence and lift of a candidate association rule are calculated using the following formula: in, Candidate association rules The confidence level, The representation also includes parameter terms X and conflicting tags Y support, For parameter items X support, Candidate association rules The degree of improvement, Conflict Label =Yes support, In the global database, including conflicting labels For The number of data items, The total number of data in the global database.

[0057] It is understandable that . In the global database, it contains both parameter item X and conflict label For The number of data items.

[0058] In some embodiments, merging the global frequent itemset and the conflicting frequent itemset to obtain a target frequent itemset includes: treating the same parameter items in the conflicting frequent itemset as those in the global frequent itemset as consistent parameter items, treating all parameter items in the conflicting frequent itemset other than the consistent parameter items as inconsistent parameter items, and treating all inconsistent parameter items in the conflicting frequent itemset and all parameter items in the global frequent itemset as parameter items of the target frequent itemset to obtain the target frequent itemset.

[0059] In some embodiments, at least one target association rule is determined based on the confidence and lift of each candidate association rule: each candidate rule having a confidence greater than a preset confidence and a lift greater than a preset lift is determined as each target association rule.

[0060] Preferably, combined Figure 4 As shown, the embodiment of the present disclosure provides a flowchart for clearing a conflict list. Based on each conflict node in the conflict list, a management control command corresponding to each conflict node is generated and executed to process each conflict node, and the processed conflict node is removed from the conflict list until the conflict list is empty, including: Step S201: determining at least one target conflict node based on each conflict node in the conflict linked list.

[0061] Step S202 : Generate and execute management control commands corresponding to each target conflicting node to process each target conflicting node.

[0062] Because a conflicting node includes a working device group and a handling policy, generating a management control command corresponding to the target conflicting node represents generating a corresponding management control command based on the working device group and handling policy corresponding to the target conflicting node. For example, if the working device group corresponding to the target conflicting node is working device A and working device B, and the handling policy is to adjust the beam direction of working device A to direction 2, the generated management control command is to adjust the beam direction of working device A to direction 2.

[0063] Step S203: remove each processed target conflict node from the conflict linked list.

[0064] Step S204: update the conflict list, and repeat steps S201 to S204 until the conflict list is empty.

[0065] In this way, by determining at least the target conflict node from each conflict node in the conflict list, and then generating and executing the management control command corresponding to each target conflict node, the working device groups within the target conflict node no longer interfere with each other and are mutually compatible. The processed target conflict node is then removed from the conflict list to avoid repeated processing of the conflict node. The conflict list is updated, a new target conflict node is determined, and a management control command for the new target conflict node is generated and executed. The processed new target conflict node is removed from the conflict list. This process is repeated until the conflict list is empty, thereby enabling the various conflict nodes in the conflict list to be processed in an orderly manner according to the connections between the conflict nodes.

[0066] Preferably, the method of determining at least one target conflict node based on each conflict node in the conflict list includes: mapping each conflict node in the conflict list to a graph node; constructing undirected edges based on the shared device relationship between the working device groups in each conflict node, calculating the edge weights between adjacent graph nodes, and obtaining an undirected conflict graph; wherein the shared device is a working device shared by two working device groups; and determining at least one target conflict node based on the edge weights in the undirected conflict graph.

[0067] In this way, by constructing an undirected conflict graph, the connections between conflicting nodes can be quantified. The target conflict node is then determined based on the edge weights. This target conflict node is the conflict node with the most significant impact within the conflict list, making it easier to select the appropriate target conflict node based on the connections between conflicting nodes. Addressing the acoustic compatibility issues associated with this target conflict node can effectively mitigate the impact of this working device group on other working devices.

[0068] In some embodiments, combined Figure 5 As shown, the embodiment of the present disclosure provides another flow chart for clearing the conflict list. Based on each conflict node in the conflict list, a management control command corresponding to each conflict node is generated and executed to process each conflict node, and the processed conflict node is removed from the conflict list until the conflict list is empty, including: Step S501: Map each conflict node in the conflict list to a graph node.

[0069] Step S502: construct undirected edges based on the shared device relationships between the working device groups in each conflict node, calculate the edge weights between adjacent graph nodes, and obtain an undirected conflict graph, wherein the shared devices are working devices shared by the two working device groups.

[0070] Step S503: determining at least one target conflict node based on the weights of each edge in the undirected conflict graph.

[0071] Step S504 : Generate and execute management control commands corresponding to each target conflicting node to process each target conflicting node.

[0072] Step S505: remove each processed target conflict node from the conflict list.

[0073] Step S506 , updating the conflict list, and repeating steps S501 to S506 until the conflict list is empty.

[0074] Preferably, calculating the edge weights between adjacent graph nodes includes: respectively obtaining the number of shared devices between adjacent graph nodes; taking the conflict type of each conflicting node as the node type of the corresponding graph node; and respectively calculating the edge weights between adjacent graph nodes based on the number of shared devices between adjacent graph nodes and the node type corresponding to each graph node.

[0075] In this way, the edge weights between adjacent graph nodes are determined based on the number of shared devices between them and the node types corresponding to each graph node, so that the edge weights can reflect the degree of influence of the shared devices on the adjacent graph nodes, thereby quantifying the correlation and influence intensity between conflicting nodes.

[0076] In some embodiments, based on the number of shared devices between adjacent graph nodes and the node type corresponding to each graph node, the edge weights between adjacent graph nodes are calculated using the following formula: in, Represents the edge weight between adjacent graph nodes x and y, Represents the number of shared devices between adjacent graph nodes x and y, The node type representing the graph node x, The node type representing the graph node y. It is a preset value, determined based on the degree of difference between the conflict types, and can also be set based on expert experience.

[0077] In some embodiments, graph node 1 and graph node 2 are adjacent graph nodes, and the working device group corresponding to graph node 1 is device A, device B, and device C. The working device group corresponding to graph node 1 is device A and device D. The shared device is device A, and the number of shared devices is 1.

[0078] Preferably, determining at least one target conflict node based on the edge weights within an undirected conflict graph includes: identifying conflict clusters within the undirected conflict graph and calculating the sum of the edge weights within each conflict cluster; selecting the conflict cluster with the largest sum of edge weights as the target conflict cluster; and calculating the sum of the edge weights of each graph node within the target conflict cluster, selecting the conflict node corresponding to the graph node with the largest sum of edge weights as the target conflict node, thereby obtaining at least one target conflict node. A conflict cluster refers to a closely connected subgraph formed by multiple graph nodes connected by edges.

[0079] By identifying conflict clusters in an undirected conflict graph and selecting the conflict cluster with the largest sum of edge weights as the target conflict cluster, we can quickly determine the conflict cluster with the greatest impact on the entire undirected conflict graph. Furthermore, by selecting the conflict node corresponding to the graph node with the largest sum of edge weights within the target conflict cluster as the target conflict node, we can further determine the graph node with the greatest impact within the target conflict cluster, ensuring that this graph node becomes a critically influential graph node in the entire undirected conflict graph.

[0080] Preferably, based on each conflict node in the conflict list, at least one target conflict node is determined, including: grouping based on the conflict type of each conflict node in the conflict list to obtain multiple conflict node groups; wherein the conflict node also includes the conflict type; selecting a conflict node from at least one conflict node group to determine at least one target conflict node.

[0081] In this way, conflict nodes within the conflict list are grouped based on their conflict types, ensuring that each conflict node group has a different conflict type. Target conflict nodes are then selected from different conflict node groups, ensuring that each target conflict node also has a different conflict type. This allows for parallel processing of target conflict nodes, improving the efficiency of handling acoustic compatibility issues and effectively improving management and control efficiency while also effectively minimizing the impact on each other and minimizing the risk of causing new acoustic compatibility issues.

[0082] Combine Figure 6 As shown, the embodiment of the present disclosure provides another flow chart for clearing the conflict list. Based on each conflict node in the conflict list, a management control command corresponding to each conflict node is generated and executed to process each conflict node, and the processed conflict node is removed from the conflict list until the conflict list is empty, including: Step S601 : grouping the conflict nodes in the conflict linked list based on their conflict types to obtain a plurality of conflict node groups; wherein the conflict nodes also include conflict types.

[0083] Step S602: Select a conflict node from at least one conflict node group and determine at least one target conflict node; Step S603: Generate and execute management control commands corresponding to each target conflict node to process each target conflict node; Step S604, removing each processed target conflict node from the conflict list; Step S605: Update the conflict list, and repeat steps S601 to S605 until the conflict list is empty.

[0084] Preferably, determining at least one target conflict node based on each conflict node in the conflict list includes randomly selecting a preset number of conflict nodes as target conflict nodes based on each conflict node in the conflict list, or arranging the conflict times of the conflict nodes in descending order and selecting a preset number of conflict nodes ranked highest as target conflict nodes. The conflict time is one of a time when a conflict rule is triggered, a time when a conflict node is created, and a time when the conflict node is added to the conflict list.

[0085] In this way, by selecting a preset number of conflict nodes as target conflict nodes, each target conflict node can be processed in parallel, thereby improving the efficiency of management and control.

[0086] Preferably, updating the conflict linked list includes: using the conflict linked list after removing the target conflict node as the updated conflict linked list.

[0087] In this way, the conflict linked list after removing the processed target conflict nodes is used as the updated conflict linked list, which facilitates orderly processing of the target conflict nodes determined in each cycle and avoids repeated processing of the same conflict node.

[0088] For example, the conflict list contains conflict nodes 1, 2, 3, and 4. The target conflict node is 1. Then the conflict nodes in the updated conflict list are 2, 3, and 4.

[0089] Preferably, updating the conflict list includes: using the conflict list after removing the target conflict node as the first conflict list. Re-collecting the working parameters of each working device. Determining whether at least one conflict condition is met based on the re-collected working parameters of each working device. If at least one conflict condition is met, generating each candidate conflict node to obtain a candidate conflict node set. Comparing the candidate conflict node set with the conflict nodes in the first conflict list. If the comparison result shows that the conflict nodes in the first conflict list are inconsistent with the candidate conflict node set, adding the candidate conflict nodes that exist in the candidate conflict node set but not in the first conflict list to the first conflict list, and removing the conflict nodes that exist in the first conflict list but not in the candidate conflict node set from the first conflict list to obtain a second conflict list, and using the second conflict list as the updated conflict list. If the comparison result shows that the conflict nodes in the first conflict list are consistent with the candidate conflict node set, using the first conflict list as the updated conflict list.

[0090] After addressing the target conflict node, new acoustic compatibility issues may arise, or the working equipment group in an existing conflict node (non-target conflict node) may no longer meet the corresponding conflict conditions. Therefore, by re-collecting various acoustic operating parameters and determining new conflict nodes (i.e., candidate conflict nodes), each candidate conflict node is then compared with the first conflict list. Conflict nodes that no longer meet the conflict conditions are removed from the first conflict list, and newly generated conflict nodes are added to the first conflict list. This allows for comprehensive and timely resolution of all acoustic compatibility issues on offshore platforms.

[0091] For example, the conflict list contains conflict nodes 1, 2, 3, and 4. The target conflict node is conflict node 1. Therefore, the conflict nodes in the first conflict list are conflict nodes 2, 3, and 4. The candidate conflict node set includes candidate conflict node 1, 2, and 3. Through comparison, it is found that candidate conflict node 2 is consistent with conflict node 2 in the first conflict list, and candidate conflict node 3 is consistent with conflict node 3 in the first conflict list. Therefore, candidate conflict node 1 is added to the first conflict list and conflict node 4 is removed from the first conflict list, resulting in a second conflict list (which includes conflict nodes 2, 3, and candidate conflict node 1). The second conflict list is used as the updated conflict list.

[0092] Preferably, collecting the working parameters of each acoustic device includes: collecting the working parameters of each acoustic device in response to the status detection instruction; and updating and displaying the collected working parameters of each acoustic device on a preset display interface.

[0093] In this way, the current operating parameter information of each acoustic device is detected in response to the status detection instruction, and the information is updated and displayed on the preset display interface, so that the operator can intuitively understand the current operating parameter information of each working device. Then enter the acoustic compatibility conflict detection process: based on the operating parameters of each acoustic device... create conflict nodes... generate and execute corresponding management control commands, and remove the processed conflict nodes from the conflict list until the conflict list is empty (see the detailed process for details). Figure 1 ), so that the acoustic compatibility issues between working equipment can be managed and controlled comprehensively and timely, and the efficiency of management and control can be improved.

[0094] It is understandable that updating the display representation means updating the operating parameters of each acoustic device to the currently collected operating parameters on the preset display interface.

[0095] Preferably, the working parameters of each acoustic device are collected, including: collecting the working parameters of each acoustic device, including: responding to a shutdown instruction, controlling the acoustic device pointed to by the shutdown instruction to shut down; collecting the working parameters of each acoustic device; updating and displaying the collected working parameters of each acoustic device on a preset display interface.

[0096] In this way, in response to the shutdown command, the corresponding acoustic device is shut down, and the operating parameters of each acoustic device are updated and displayed, so that the operator can intuitively understand the current operating parameter information of each acoustic device. Then enter the acoustic compatibility conflict detection process: based on the operating parameters of each acoustic device... create conflict nodes... generate and execute the corresponding management control command, and remove the processed conflict nodes from the conflict list until the conflict list is empty (for detailed process, see Figure 1), so that the acoustic compatibility issues between working equipment can be managed and controlled comprehensively and timely, and the efficiency of management and control can be improved.

[0097] Preferably, a ship acoustic compatibility management and control method further comprises: updating a timer of each acoustic device in response to a management confirmation instruction.

[0098] In this way, based on the timer of each acoustic device, it is possible to determine whether each acoustic device has a fault, so that the faulty acoustic device can be discovered in time, making it easier for operators to perform troubleshooting and other operations.

[0099] Specifically, in response to the management confirmation command, the timer of each acoustic device is updated. This includes: sending the management confirmation command to each acoustic device, receiving a confirmation message from each acoustic device based on the management confirmation command, and using the time difference between sending the confirmation command and receiving the confirmation message from each acoustic device as the timer for each acoustic device. For each acoustic device, if the timer (i.e., response time) exceeds a preset time period, or if no confirmation message is received within the preset time period, the acoustic device is determined to be faulty.

[0100] Preferably, a ship acoustic compatibility management and control method further includes: in response to a status feedback instruction, sending the status feedback instruction to each acoustic device, and receiving working parameters fed back by each acoustic device based on the status feedback instruction.

[0101] Combine Figure 7 As shown, the embodiment of the present disclosure provides another ship acoustic compatibility management and control method, including: Step S701: When receiving a command, determine the command type. If the command type is a status feedback command, execute step S702; if the command type is a status detection command, execute step S703; if the command type is a shutdown command, execute step S704; if the command type is a management confirmation command, execute step S707.

[0102] Step S702: Send the state feedback instruction to each acoustic device, and receive the working parameters fed back by each acoustic device based on the state feedback instruction.

[0103] Step S703: collect the working parameters of each acoustic device, update and display the collected working parameters of each acoustic device on a preset display interface, and then execute step S705.

[0104] Step S704: Control the acoustic device indicated by the shutdown instruction to shut down, collect the working parameters of each acoustic device, and update and display the collected working parameters of each acoustic device on a preset display interface. Then, step S705 is executed.

[0105] In step S705, the operating parameters of each acoustic device are collected. Based on the operating parameters of each acoustic device, it is determined whether each operating device triggers at least one conflict condition. If at least one conflict condition is triggered, conflict nodes are created based on each triggered conflict condition and added to a conflict list. Based on each conflict node in the conflict list, management control commands corresponding to each conflict node are generated and executed to resolve each conflict node. Removing resolved conflict nodes from the conflict list until the conflict list is empty. Step S706 is then executed.

[0106] Step S706 : Visualizing the acoustic compatibility conflict detection and processing process on a preset display interface.

[0107] In some embodiments, the acoustic compatibility conflict detection and processing process is visualized: the working device group corresponding to the conflict node being processed, the working parameters of each working device in the working device group, the triggered conflict conditions, the processing strategy and the processing progress (such as the conflict status of the conflict node) are displayed.

[0108] Step S707: Update the timer of each acoustic device.

[0109] Finally, it should be noted that the above preferred embodiments are only used to illustrate the technical solutions of the present invention and are not limiting. Although the present invention has been described in detail through the above preferred embodiments, those skilled in the art should understand that various changes can be made in form and details without departing from the scope defined by the claims of the present invention.

Claims

1. A ship acoustic compatibility management and control method, characterized in that: include: Step S101, collecting operating parameters of each acoustic device; Step S102: determining whether each working device triggers at least one conflict condition based on working parameters of each acoustic device; wherein the working device represents an acoustic device in a working state; Step S103: If at least one conflict condition is triggered, conflict nodes are created based on each conflict condition that is triggered, and each conflict node is added to a conflict list; wherein the conflict node includes the working device group that triggers the same conflict condition and the corresponding working parameters and processing strategy; Step S104 : Based on each conflicting node in the conflict linked list, generate and execute a management control command corresponding to each conflicting node to process each conflicting node, and remove the processed conflicting node from the conflict linked list until the conflict linked list is empty.

2. The method according to claim 1, characterized in that The determining, based on the operating parameters of each acoustic device, whether each operating device triggers at least one conflict condition includes: Determining each working device based on the working parameters of each acoustic device; Based on a preset conflict rule library, detecting whether the working parameters of each working device trigger an interference condition of at least one conflict rule; wherein the conflict rule library contains multiple conflict rules, and the conflict rules include interference conditions and processing strategies; If the interference condition of at least one conflicting rule is triggered, it is determined that at least one conflicting condition is triggered; wherein one conflicting rule corresponds to one conflicting condition.

3. The method according to claim 1, characterized in that The generating and executing management control commands corresponding to the conflicting nodes in the conflict linked list to process the conflicting nodes, and removing the processed conflicting nodes from the conflict linked list until the conflict linked list is empty, includes: Step S201, determining at least one target conflict node based on each conflict node in the conflict linked list; Step S202: Generate and execute management control commands corresponding to each target conflict node to process each target conflict node; Step S203, removing each processed target conflict node from the conflict list; Step S204: update the conflict list, and repeat steps S201 to S204 until the conflict list is empty.

4. The method according to claim 3, characterized in that The determining of at least one target conflict node based on each conflict node in the conflict linked list includes: Map each conflict node in the conflict list to a graph node; Based on the shared device relationships between the working device groups in each conflict node, undirected edges are constructed, and the edge weights between adjacent graph nodes are calculated to obtain an undirected conflict graph; wherein the shared devices are working devices shared by the two working device groups; At least one target conflict node is determined based on the weights of each edge in the undirected conflict graph.

5. The method according to claim 4, characterized in that Calculating edge weights between adjacent graph nodes includes: Get the number of shared devices between adjacent graph nodes respectively; The conflict type of each conflict node is used as the node type of the corresponding graph node; wherein the conflict node also includes the conflict type; Based on the number of shared devices between adjacent graph nodes and the node type corresponding to each graph node, the edge weights between adjacent graph nodes are calculated separately.

6. The method according to claim 4, characterized in that The determining of at least one target conflict node based on the weights of each edge in the undirected conflict graph includes: Identify conflict clusters in an undirected conflict graph and calculate the sum of edge weights within each conflict cluster; The conflict cluster with the largest sum of edge weights is taken as the target conflict cluster; The sum of the edge weights of each graph node in the target conflict cluster is calculated, and the conflict node corresponding to the graph node with the largest sum of edge weights is used as the target conflict node to obtain at least one target conflict node.

7. The method according to claim 3, characterized in that The determining of at least one target conflict node based on each conflict node in the conflict linked list includes: Grouping the conflict nodes in the conflict list based on their conflict types to obtain multiple conflict node groups; wherein the conflict nodes also include conflict types; A conflict node is selected from at least one conflict node group, and at least one target conflict node is determined.

8. The method according to any one of claims 1 to 7, characterized in that The collecting of the working parameters of each acoustic device includes: In response to the status detection instruction, collecting the operating parameters of each acoustic device; The collected working parameters of each acoustic device are updated and displayed on the preset display interface.

9. The method according to any one of claims 1 to 7, characterized in that The collecting of the working parameters of each acoustic device includes: In response to a shutdown instruction, controlling the acoustic device directed by the shutdown instruction to shut down; Collect the working parameters of each acoustic device; The collected working parameters of each acoustic device are updated and displayed on the preset display interface.

10. The method according to any one of claims 1 to 7, characterized in that Also includes: In response to the management confirmation instruction, the timer of each acoustic device is updated.

Images