Ship monitoring system and ship fault alarm method

Abstract

The invention relates to a ship monitoring technology, in particular to a ship monitoring system and a ship fault alarm method. The ship monitoring system comprises a data acquisition layer, a data management layer, a business logic layer and a user page layer which are in communication connection in sequence. The data acquisition layer is used for acquiring monitoring data of each detection component in ship hardware equipment in real time and uploading the monitoring data to the data management layer; the data management layer is used for managing monitoring data, and the business logic layer at least comprises an energy efficiency index calculation unit and a fault diagnosis unit; the energy index calculation unit is used for analyzing the energy consumption of each piece of ship hardware equipment according to the monitoring data and providing suggestions of an energy efficiency optimization strategy; the fault diagnosis unit is used for analyzing the condition of each piece of ship hardware equipment according to the monitoring data and diagnosing whether a fault occurs; and the user page layer is used for providing a visual interactive interface. Through the arrangement, the hierarchical division of the system is effectively realized, and the flexibility and expandability of the system are facilitated.

Description

Technical Field

[0001] The present invention relates to ship monitoring technology, and in particular to a ship monitoring system and a ship fault alarm method. Background Art

[0002] In the current shipping field, intelligence and digitalization have become the mainstream development trend. The intelligent system of ships can significantly improve the operational efficiency and safety of ships through real-time monitoring, data analysis and automatic control.

[0003] However, existing technologies face some challenges: First, the customization of ship projects and the closed nature of software systems limit data sharing and software portability between different projects. Software customized for specific ship projects generally lacks versatility and is difficult to share and reuse in different projects, which leads to waste of resources and repeated development. Secondly, the diverse communication protocols and data transmission methods in ship systems make it difficult for the system to adapt to changes in hardware configuration. Furthermore, most existing systems use a single-layer software structure, which makes it difficult for many subsystems in the ship monitoring system to share and interact with each other. Therefore, the current existing technology has obvious deficiencies in responding to the needs of diversified ship projects and improving system flexibility, and it is difficult to meet the long-term development needs of intelligent and digital ship projects. Summary of the invention

[0004] In view of at least one shortcoming of the above-mentioned prior art that is the lack of adaptability to the diversity of ship intelligent systems and the rapidly changing software requirements, the present invention aims to provide a ship monitoring system that improves the portability and flexibility of the software through software layered design, modular division and standardization of module basic functions, so that software modules can be quickly transplanted and reused in different ship projects, reducing development costs and time.

[0005] In a first aspect, the present invention provides a ship monitoring system, comprising at least a data acquisition layer, a data management layer, a business logic layer and a user page layer which are communicatively connected in sequence;

[0006] The data acquisition layer is used to obtain the monitoring data of each detection component in the ship's hardware equipment in real time and upload it to the data management layer;

[0007] The data management layer is used to store, read and back up the monitoring data uploaded by the data collection layer, and is also used to provide the business logic layer with the monitoring data required for calculation and receive and store the result data and fault information after the calculation and analysis by the business logic layer, so that different modules in the business logic layer can access the result data through the data management layer.

[0008] The business logic layer is used to obtain the monitoring data stored in the data management layer, and then perform calculations and analysis to provide auxiliary decision-making; the business logic layer includes at least an energy efficiency index calculation unit and a fault diagnosis unit; the energy index calculation unit includes multiple calculation modules for analyzing the energy consumption of each ship hardware device according to the monitoring data, and providing suggestions for energy efficiency optimization strategies; the fault diagnosis unit includes multiple diagnosis modules for analyzing the status of each ship hardware device according to the monitoring data and diagnosing whether it is faulty;

[0009] The user page layer is used to provide a visual interactive interface for human-computer interaction with the ship monitoring system.

[0010] In one embodiment, the data acquisition layer includes at least a CAN server, a serial port server, a high-frequency signal collector, and a low-frequency signal collector that are directly or indirectly connected to each detection component in the ship hardware equipment through a communication protocol to obtain the monitoring data of the detection component in real time and convert the monitoring data from physical parameters into digital signals.

[0011] In one embodiment, the data acquisition layer also includes a data processor, which includes at least one or more of a data acquisition module, a data analysis module, a data preprocessing module, and a data upload module; the data acquisition module is used to acquire monitoring data and verify the accuracy and completeness of the monitoring data; the data analysis module is used to parse monitoring data of different formats or protocols into a data format that can be processed by the system; the data preprocessing module is used to preprocess the monitoring data including at least one of data filtering, data smoothing, and outlier detection; the data upload module is used to match the processed monitoring data with the monitoring parameter code and upload it to the data management layer; the monitoring parameter code is a unique identification code for each type of monitoring data.

[0012] In one embodiment, the data management layer includes at least a centralized data management platform for centralized management of monitoring data and control of access rights; the centralized data management platform adopts a service-oriented architecture design and runs as a server, while communicating with the business logic layer and the data acquisition layer through the HTTP protocol, and using the JSON data format as the standard format for data exchange; the centralized data management platform also develops a number of standardized interfaces to provide data exchange functions with other levels and modules.

[0013] In one embodiment, the data management layer also includes a database, which is used to store result data and fault information and also to store and manage configuration information of the business logic layer and the data collection layer;

[0014] The database is configured with at least a data coding table module, a fault coding table module, a storage rule module, and a data access rule configuration module; the data coding table module is used to define and store the coding standards and mapping relationships between various types of monitoring data and monitoring parameter coding; the fault coding table module is used to define and store the coding standards and mapping relationships between various types of fault information and fault codes; the storage rule module is used to set the storage format, encryption method, storage location and storage cycle rules of the monitoring data; the data access rule configuration module is used to set the data access rights, access frequency restrictions and data access scope of each module.

[0015] In one embodiment, the storage cycle includes at least one of the following rules: determining different storage cycle rules based on different types of monitoring data; shortening the storage cycle of the monitoring data of the detected device when a device fault is detected based on associated fault information; shortening the storage cycle of a certain type of monitoring data when the type of monitoring data is in a preset high-frequency change based on the operating requirements of each ship hardware equipment.

[0016] In one embodiment, the data management layer further configures a buffer with a lock mechanism for each type of monitoring data, and the buffer is used to record and temporarily store the monitoring data; the database regularly stores the data in the buffer permanently in the database according to the storage rules of the storage rule module;

[0017] When the data management layer receives a request to submit monitoring data, the data access rule configuration module verifies whether the request complies with the preset access rules. If the verification succeeds, the monitoring data in the buffer is updated according to the request. When the data management layer receives a request to obtain monitoring data, the data access rule configuration module also verifies whether the request complies with the preset access rules. If the verification succeeds, the monitoring data is read from the buffer and responded to according to the request.

[0018] In one embodiment, the database also includes a configuration file management module for managing the configuration information of the newly added functional modules in the business logic layer and the data acquisition layer; the configuration file management module updates the contents of the data coding table module, the fault coding table module, the storage rule module, and the data access rule configuration module according to the configuration information of the newly added functional modules in the business logic layer and the data acquisition layer, and automatically deploys the newly added functional modules in the business logic layer and the data acquisition layer based on the configuration information.

[0019] In one embodiment, the specific steps of adding a new function module to the business logic layer are: determining a unique identification code for the new function module and determining a unique data code for the new monitoring data of the new function module, wherein a specific bit of the data code is used to identify the monitoring location; completing the relevant configuration of the new function module in the database based on the identification code and the new data code; and automatically deploying the new function module on the business logic layer based on the relevant configuration of the new monitoring data in the database;

[0020] The specific steps for adding a new functional module to the data acquisition layer are: determining a unique identification code for the new functional module and a unique data code for the new monitoring data of the new functional module, and a specific bit of the data code is used to identify the monitoring location; completing the configuration of the new monitoring data in the database based on the identification code and the new data code; automatically deploying the new functional module on the data acquisition layer based on the configuration information; the configuration of the new monitoring data in the database includes at least the following information: the association between the new monitoring data and the fault information, the byte length required for the new monitoring data, the storage rules for the new monitoring data, and the identification code of the detection component from which the new monitoring data comes.

[0021] In a second aspect, the present invention further provides a ship fault alarm method, using the ship monitoring system of any of the above embodiments, comprising the following steps:

[0022] Data collection step: the data collection layer obtains the monitoring data of each detection component in the ship's hardware equipment in real time and uploads it to the data management layer;

[0023] Data management step: the data management layer stores the uploaded monitoring data;

[0024] In the logical judgment step, the fault diagnosis unit of the business logic layer sends a request to the data management layer to obtain relevant monitoring data, and performs analysis and diagnosis based on the relevant monitoring data obtained in the request; if a fault is diagnosed, the fault information is submitted to the data management layer;

[0025] In the alarm step, the user page layer visualizes the fault information and related monitoring data.

[0026] Based on the above, compared with the prior art, the ship monitoring system provided by the present invention effectively realizes the hierarchical division of the system through the design of data acquisition layer, data management layer, business logic layer and user page layer; and there is only data transmission but no process coupling between the layers, which can facilitate the addition, collection and data sharing of various modules, equipment, protocols, business functions and fault types in the ship system, which is beneficial to the flexibility and scalability of the system, so that software modules at different levels can be independently developed, tested, deployed and migrated.

[0027] Other features and beneficial effects of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other beneficial effects of the present invention can be realized and obtained by the structures particularly pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. The positional relationships described in the drawings in the following description are based on the directions in which the components are drawn in the diagrams, unless otherwise specified.

[0029] Figure 1 A structural block diagram of a ship monitoring system provided by an embodiment of the present invention;

[0030] Figure 2 A structural block diagram of a ship monitoring system provided by another embodiment of the present invention;

[0031] Figure 3 A flow chart of the steps of a ship fault alarm method provided by one embodiment of the present invention. DETAILED DESCRIPTION

[0032] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, rather than all the embodiments; the technical features designed in different implementation modes of the present invention described below can be combined with each other as long as they do not conflict with each other; based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0033] In the description of the present invention, it should be noted that all terms used in the present invention (including technical terms and scientific terms) have the same meanings as those generally understood by ordinary technicians in the field to which the present invention belongs, and cannot be understood as limiting the present invention; it should be further understood that the terms used in the present invention should be understood to have the same meanings as these terms in the context of this specification and in the relevant fields, and should not be understood in an idealized or overly formal sense, unless explicitly defined in the present invention.

[0034] In order to solve the problem that the existing technology lacks adaptability to the diversity of ship monitoring systems and rapidly changing software requirements, the present invention provides a ship monitoring system and a ship fault alarm method. Through software layered design, modular division and standardization of module basic functions, the portability and flexibility of the software are improved, so that the software modules can be quickly transplanted and reused in different ship projects, reducing development costs and time. At the same time, the formulation of standardized interfaces and data encoding rules enhances the openness of system data, facilitates data sharing and interoperability between various ship systems, and improves the overall performance and efficiency of the system.

[0035] See also Figure 1 , a ship monitoring system provided by an embodiment of the present invention comprises a data acquisition layer, a data management layer, a business logic layer and a user page layer which are sequentially communicatively connected;

[0036] The data acquisition layer is used to obtain the monitoring data of each detection component in the ship's hardware equipment in real time and upload it to the data management layer.

[0037] Specifically, the data acquisition layer is connected to the bottom layer of the detection component, and its communication protocol and communication method depend on the type of each detection component, such as MODBUS, CAN, analog current, etc. The detection component includes various sensor devices to monitor the parameters of various hardware devices in the ship, such as exhaust temperature sensor, air pressure sensor, oil viscosity sensor, ferromagnetic particle sensor, torsional vibration sensor, vibration sensor, etc., which are designed according to the actual working needs of the ship.

[0038] The data acquisition layer is responsible for real-time collection of various sensor data in the ship. Preferably, the data acquisition layer can also use hardware and software to convert, pre-process, and analyze the sensor data into digital signals.

[0039] In specific implementation, the data acquisition layer at least includes a CAN server, a serial port server, a high-frequency signal collector, and a low-frequency signal collector that are directly or indirectly connected to each detection component in the ship's hardware equipment through a communication protocol to obtain the monitoring data of the detection components in real time and convert the monitoring data from physical parameters into digital signals.

[0040] Among them, CAN server is a device based on CAN (Control Area Network) bus technology. Therefore, the CAN server is connected to the detection component that supports CAN bus for data transmission in the ship hardware equipment through the CAN bus to realize the real-time collection and transmission of monitoring data. The serial port server is a network device that allows the serial port (COM port) device to be shared to multiple users or applications through a network connection. The serial port server can support a variety of serial port protocols (such as RS-232, RS-422, RS-485, etc.) and can be compatible with various serial port devices. Therefore, the serial port server is used to connect the detection component that supports serial port communication to the network, so that the monitoring data on these detection components can be transmitted to the data acquisition layer in real time through the network. The high-frequency signal collector is used to collect high-frequency band signals, and can accurately capture and convert high-frequency signals into digital signals. The low-frequency signal collector is used to collect low-frequency band signals, and through precise sensors and signal processing circuits, these weaker low-frequency signals are converted into analyzable digital signals. It should be noted that the specific models of the high-frequency signal collector and the low-frequency signal collector can be reasonably selected according to actual work needs.

[0041] In a preferred embodiment, see Figure 2 The data acquisition layer also includes a data processor, which includes at least one or more of a data acquisition module, a data analysis module, a data preprocessing module, and a data upload module. The data processor is the core component of the data acquisition layer, including but not limited to a data acquisition module, a data analysis module, a data preprocessing module, and a data upload module. These modules can be flexibly combined according to actual needs to realize customized data acquisition and processing processes.

[0042] The data acquisition module is used to obtain monitoring data and verify the accuracy and completeness of the monitoring data. Specifically, the data acquisition module is used to obtain monitoring data from CAN servers, serial port servers, high-frequency signal collectors, low-frequency signal collectors and other devices. The data acquisition module has a built-in data verification mechanism, which uses preset verification rules to verify the accuracy and completeness of the acquired data, including whether the monitoring data is fully received and whether it conforms to the expected format and range.

[0043] The data parsing module is used to parse monitoring data of different formats or protocols into data formats that can be processed by the system. Specifically, for the diverse data formats and communication protocols from different devices or systems, the module can intelligently identify, decode, and convert formats, convert the original data into a data format that can be uniformly processed within the system, and eliminate the processing obstacles caused by data format differences.

[0044] The data preprocessing module is used to preprocess the monitoring data, including at least one of data filtering, data smoothing, and outlier detection. Before uploading the monitoring data, the module performs in-depth processing on the parsed monitoring data, including but not limited to data filtering (removing noise data), data smoothing (reducing data fluctuations), outlier detection (identifying and processing abnormal data points), etc., to improve the quality and consistency of the data and provide a more accurate data basis for subsequent analysis.

[0045] The data upload module is used to match the processed monitoring data with the monitoring parameter code and upload it to the data management layer; the monitoring parameter code is a unique identification code for each type of monitoring data, which is used to identify different monitoring parameters and data types. Specifically, the pre-processed monitoring data is accurately matched with the monitoring parameter code to ensure that each type of monitoring data can be uniquely identified. Subsequently, the data is uploaded to the data management layer through a secure and reliable transmission protocol (such as the HTTP protocol) for subsequent data analysis, storage and management. In addition, the introduction of the matching of monitoring data and monitoring parameter codes is conducive to the classified storage and rapid retrieval of data, so that the system can quickly identify which type of monitoring parameters the received data belongs to, so as to perform corresponding processing and analysis, and also provides a favorable basis for the subsequent addition or modification of functional modules.

[0046] The data management layer is used to store, read and back up the monitoring data uploaded by the data collection layer, and is also used to provide the business logic layer with the monitoring data required for calculation and receive and store the result data and fault information after the calculation and analysis by the business logic layer, so that different modules in the business logic layer can access the result data through the data management layer. Figure 2 The data management layer at least includes a centralized data management platform and a database. The centralized data management platform is used to centrally manage monitoring data and control access rights. The database is used to store result data and fault information, and also to store and manage configuration information of the business logic layer and the data acquisition layer.

[0047] Specifically, the centralized data management platform adopts a service-oriented architecture design (SOA), which can support the encapsulation of various functions of the centralized data management platform into a series of reusable service components. These service components are deployed and run independently, supporting loosely coupled system expansion and maintenance. Through the flexible combination and call of service components, complex data processing and management tasks can be achieved. At the same time, it runs as a server, supporting concurrent access and efficient processing. By establishing communication connections with other layers or modules such as the business logic layer and data acquisition layer, real-time data transmission and interaction can be achieved. In addition, the server operation mode also has load balancing and fault-tolerant processing mechanisms to ensure that stable data services can be provided under high load conditions.

[0048] The centralized data management platform also communicates with the business logic layer and the data collection layer through the HTTP protocol, using the JSON data format as the standard format for data exchange. The JSON format is lightweight, easy to read and write, and can support the representation and transmission of complex data structures, effectively ensuring the convenience and compatibility of data exchange.

[0049] Furthermore, the centralized data management platform also develops several standardized interfaces to provide data exchange functions with other levels and modules, realize data query, upload, download and update operations, and facilitate the integration and docking of the centralized data management platform with other levels and modules. Among them, the standardized interface can provide the following functions: 1. Obtain or submit the real-time value of the specified monitoring data according to the monitoring parameter code. 2. Obtain all parameters related to a monitored device according to the monitoring location information contained in the monitoring parameter code. 3. Submit fault information based on the fault code. 4. The request contains the unique identification code of the module so that the data management layer can verify the legitimacy of data access in combination with the configuration information and IP whitelist method.

[0050] Preferably, the data management layer determines the TCP connection mode according to the acquisition / submission frequency configured by each module, and supports TCP long connection for modules with high data interaction frequency, thereby optimizing the performance of network communication.

[0051] Specifically, the data management layer collects data interaction information between modules in real time by monitoring network ports or querying internal logs, including the number of interactions, data volume, timestamp, etc., and determines the data interaction frequency of each module according to a preset threshold or algorithm. At the same time, the data management layer also compares the calculated data interaction frequency with the preset threshold. If the data interaction frequency of a module exceeds the high threshold, the data management layer sends an instruction to the network communication interface to adjust the TCP connection mode of the module to a long connection to reduce the overhead caused by frequent establishment and disconnection of connections and optimize network communication performance. If the data interaction frequency of a module is lower than the low threshold and lasts for a period of time (such as within a preset time window), the data management layer also sends an instruction to the network communication interface to adjust the TCP connection mode of the module to a short connection to release unnecessary network resources. The network communication interface dynamically adjusts the TCP connection mode of the corresponding module according to the received instruction, effectively solving the performance bottleneck problem of the traditional TCP communication method in complex data processing systems. This method not only improves the efficiency and stability of network communication, but also enhances the flexibility and scalability of the system.

[0052] The database is configured with at least a data coding table module, a fault coding table module, a storage rule module, and a data access rule configuration module.

[0053] The data coding table module is used to define and store the coding standards and mapping relationships of various monitoring data and monitoring parameter codes. In the specific implementation, firstly, a complete set of coding specifications is designed according to the actual needs of ship monitoring, including data type coding, parameter coding, etc. Then, these coding standards are entered into the data coding table module, and a corresponding mapping relationship table is established so that the system can automatically convert the original monitoring data with the standardized coded data. Through a unified coding standard, it is ensured that monitoring data from different sources and different types can be accurately and quickly identified, processed and transmitted, thereby improving operational efficiency. As far as JSON data transmission is concerned, the monitoring parameter code is used in the transmitted data packet to replace the original complex code, and the monitoring parameter code is converted back to the original complex code during parsing, which can greatly reduce the space occupied by transmission and improve transmission efficiency.

[0054] The fault coding table module is used to define and store the coding standards and mapping relationships between various types of fault information and fault codes. In specific implementation, first collect various types of fault information that may occur in the ship, and assign a unique fault code to each type of fault information. Then, these fault codes are entered into the fault coding table module together with the corresponding fault description, processing suggestions and other fault information. Of course, an additional fault knowledge base can be established in the database, and the relevant fault knowledge and processing suggestions corresponding to the fault information can be entered into the fault knowledge base, so that the system can submit the fault information of the fault diagnosis result according to the fault code and respond to the relevant information in the fault knowledge base. When the system detects that a certain equipment has a fault, it will automatically convert the fault information into the corresponding fault code, and obtain a detailed fault description and processing suggestions by querying the fault coding table module. In this way, not only the efficiency of troubleshooting is improved, but also the subsequent fault statistics, analysis and maintenance work are facilitated. In addition, the module also supports custom expansion of fault coding to meet the specific needs of different ships.

[0055] The storage rule module is used to set the rules for the storage format, encryption method, storage location and storage period of monitoring data. In specific implementation, different storage strategies can be formulated according to different types of monitoring data, which can be dynamically adjusted according to business needs. For storage format and encryption method, appropriate storage format and encryption method can be selected according to the sensitivity and importance of the data. For example, for key data related to ship safety, encrypted storage can be used to ensure data security. For storage location, data can be stored in a suitable physical location according to the frequency of data access and storage space requirements. For example, frequently accessed data is stored in a high-speed storage database to improve data access efficiency. For storage period, it can be flexibly configured according to the needs of the actual ship system.

[0056] Optionally, the storage cycle includes at least one of the following rules: 1. Determine different storage cycle rules according to different types of monitoring data to optimize storage space utilization. For example, for conventional monitoring data, such as ship position, heading, etc., a longer storage cycle can be set, such as storing once a day or a week. For another example, the temperature, pressure and other data related to the ship diesel generator set should be stored according to the diesel engine working condition. 2. According to the associated fault information, when a certain equipment fault is detected, the storage cycle of the detected monitoring data of the equipment is shortened to facilitate tracing the cause of the fault when the fault occurs; such as shortening the storage cycle to every hour or every minute, so as to analyze the cause of the fault in time. 3. According to the working condition requirements of each ship hardware equipment, when a certain type of monitoring data is in a preset high frequency change, the storage cycle of such monitoring data is shortened to ensure the timeliness and accuracy of the data. For example, for a tugboat, when it is in a towing operation, the load changes greatly at a high frequency, and the storage cycle should be appropriately shortened to reduce the occupation of storage resources. It should be noted that based on the above rules on the storage cycle, those skilled in the art can pre-set the initial storage cycle value and the storage cycle value that changes after the rule conditions are met according to the actual situation.

[0057] The data access rule configuration module is used to set the data access rights, access frequency limits and data access scope of each module. In specific implementation, the corresponding data access rights can be assigned to different modules according to their needs and responsibilities. Through refined permission control, the security and privacy of data are ensured. At the same time, it supports flexible adjustment of access frequency to balance data access efficiency and system load, prevent excessive system load caused by excessive data access, and reduce the operation and storage burden of the data management layer.

[0058] The above modular design of the database enables comprehensive and refined management of ship monitoring data. It not only improves the efficiency and accuracy of data processing, but also enhances the security and privacy of data. At the same time, flexible storage rules and access rights configuration enable the system to be customized according to the specific needs of different ships and different working conditions to meet diverse monitoring needs.

[0059] Furthermore, the data management layer also configures a buffer with a lock mechanism for each type of monitoring data. The buffer is used to record and temporarily store the monitoring data; the database regularly stores the data in the buffer in the database for a long time according to the storage rules of the storage rule module. In specific implementation, a fine-grained lock mechanism, such as a read-write lock, is used inside the buffer to optimize concurrent access performance. When data is written, a write lock is automatically added to prevent other read and write operations; when data is read, a read lock can be added to allow multiple read operations to be performed simultaneously, but write operations are blocked, thereby improving system throughput while ensuring data consistency. The buffer can be designed as a circular queue or linked list structure to cyclically record the newly arrived monitoring data in a fixed-size memory space. When the buffer is full, the old data is eliminated or stored for a long time according to the preset strategy (such as FIFO, priority, etc.) to ensure that the new data can be recorded in time.

[0060] When the data management layer receives a request to submit monitoring data, the data access rule configuration module verifies whether the request complies with the preset access rules. If the verification is successful, the monitoring data in the buffer is updated according to the request. When the data management layer receives a request to obtain monitoring data, the data access rule configuration module also verifies whether the request complies with the preset access rules. If the verification is successful, the monitoring data is read and responded from the buffer according to the request. The verification content includes but is not limited to the identity, authority, request data type, time range, etc. of the requesting module. All operations are performed when the verification is successful and the lock mechanism allows, to ensure data security and access compliance. In addition, whenever the preset storage period is reached or the buffer reaches a certain threshold, the data management layer triggers the data migration task and writes the valid data in the buffer into the database in batches according to the configuration of the storage rule module.

[0061] By introducing a buffer with a locking mechanism, the system's efficiency and security in data processing and storage are effectively improved.

[0062] In some preferred embodiments, the database also includes a configuration file management module for managing the configuration information of new functional modules in the business logic layer and the data acquisition layer; the configuration file management module updates the contents of the data coding table module, the fault coding table module, the storage rule module, and the data access rule configuration module according to the configuration information of the new functional modules in the business logic layer and the data acquisition layer, and automatically deploys the new functional modules in the business logic layer and the data acquisition layer based on the configuration information.

[0063] During specific implementation, the configuration file management module receives the client's new functional module configuration requirements and configuration information through a standardized interface. The configuration information may include the location information of the newly added monitored equipment, the newly added monitoring data and the corresponding monitoring parameter codes, the data access rules of the newly added modules, the storage rules of the newly added modules, and the relevant fault information and fault codes of the newly added monitored equipment, etc.

[0064] In some embodiments, the specific steps of adding a new function module to the business logic layer are: determining a unique identification code for the new function module and determining a unique data code for the new monitoring data of the new function module, and a specific bit of the data code is used to identify the monitoring location to facilitate subsequent data analysis and processing. Based on the identification code and the new data code, the relevant configuration of the new function module is completed in the database; based on the relevant configuration of the new monitoring data in the database, the new function module is automatically deployed on the business logic layer;

[0065] The specific steps for adding a new functional module to the data acquisition layer are: determining a unique identification code for the new functional module and a unique data code for the new monitoring data of the new functional module, and a specific bit of the data code is used to identify the monitoring location; completing the configuration of the new monitoring data in the database based on the identification code and the new data code; automatically deploying the new functional module on the data acquisition layer based on the configuration information; the configuration of the new monitoring data in the database includes at least the following information: the association between the new monitoring data and the fault information, the byte length required for the new monitoring data, the storage rules for the new monitoring data, and the identification code of the detection component from which the new monitoring data comes.

[0066] Through the above settings, the automatic and efficient configuration and deployment of new functional modules in the business logic layer and data acquisition layer of the system can be achieved, which greatly improves the scalability and flexibility of the system.

[0067] The business logic layer is used to obtain the monitoring data stored in the data management layer, and then perform calculations and analysis to provide auxiliary decision-making; please refer to Figure 1 , Figure 2 The business logic layer at least includes an energy efficiency index calculation unit and a fault diagnosis unit; the energy index calculation unit includes multiple calculation modules for analyzing the energy consumption of each ship hardware device according to the monitoring data and providing suggestions for energy efficiency optimization strategies; the fault diagnosis unit includes multiple diagnosis modules for analyzing the status of each ship hardware device according to the monitoring data and diagnosing whether there is a fault.

[0068] Specifically, the business logic layer contains a series of modules responsible for processing the core functions of the software system, such as energy efficiency index calculation, fault diagnosis, and decision support. This layer communicates with the data management layer through the HTTP protocol to obtain monitoring parameter data for calculation and analysis; a unique code is assigned to each monitoring parameter based on elements such as device type and device serial number, and a fault code is formulated based on the fault type and fault-related monitoring parameters; different systems can quickly realize data request and data transmission through data coding tables and fault coding tables, and realize unified data access and fault alarm. The calculation results can be written to the data management layer or displayed in the user page layer. The modules of this layer adopt a modular design to provide system flexibility and scalability.

[0069] Among them, the energy efficiency index calculation unit is used to obtain and analyze the energy consumption data of hardware equipment such as diesel engines, battery packs, propulsion motors, etc. in real time; evaluate the ship's emissions, effective energy utilization efficiency ratio, power consumption of various parts of the power system, etc.; optimize energy utilization efficiency, reduce emissions, and provide suggestions for energy efficiency optimization strategies. The fault diagnosis unit includes multiple modules, such as the diesel unit fault diagnosis module and the power system fault diagnosis module. Among them, the diesel unit fault diagnosis module is used to obtain data such as cylinder exhaust temperature, torsion angle, vibration acceleration, load, etc., analyze the unit's operating status, and detect whether there are faults such as cylinder pull and flameout. The power system fault diagnosis module is used to obtain power system-related data such as voltage, current, power, frequency, etc., analyze the load condition of the ship's power system, and detect whether there is an overload or imbalance in the power load.

[0070] The user page layer is used to provide a visual interactive interface for human-computer interaction with the ship monitoring system.

[0071] Specifically, the user page layer is the outermost layer of the system, providing users with a graphical user interface (GUI) so that they can interact with the ship monitoring system. This layer is mainly responsible for receiving user input, displaying information, providing user requirements to the business logic layer, and displaying calculation results. The user page layer communicates with the business logic layer. The user page layer presents monitoring parameters and diagnostic results in a visual way, allowing operators to intuitively understand the system status. At the same time, the user page layer should perform authentication and role-based access control for operations involving configuration modifications. Administrator identity is required to modify important configuration information to improve system security.

[0072] In order to effectively illustrate the partial working principle of the above system, this case takes the process of completing lubricating oil monitoring as an example. The complete data monitoring process is as follows: according to the temperature, pressure sensors, viscosity, and metal particle number in the detection component, data is collected, and 4-20mA analog current signal is output to the low-frequency signal collector of the data acquisition layer. The low-frequency signal collector outputs the digital measurement results to the data processor via the MODBUS protocol. After parsing and preprocessing, the data processor submits the data to the data management layer. After verifying the access rights, the data management layer writes the current monitoring parameter value to the buffer and completes the timed storage. The lubricating oil analysis and diagnosis module in the fault diagnosis unit of the business logic layer sends a request to the data management layer to obtain the monitoring data such as lubricating oil temperature, pressure, viscosity, and metal particle number monitored by the above modules, and integrates multiple data for analysis and diagnosis. If faults such as lubricating oil contamination and mechanical component wear are diagnosed, the fault information indexed by the fault code is submitted to the data management layer and the recommended treatment measures and other information are obtained from the fault knowledge base or fault code table module. Finally, the alarm information is displayed on the user interface layer.

[0073] In summary, the embodiment of the present invention proposes a hierarchical and modular ship monitoring system design method, which realizes only data transmission without process coupling between layers, determines the basic functional requirements of each layer, and designs a standardized interface for data transmission, thereby improving the portability and flexibility of the software project, making it easier to meet the needs of different ships, and providing a more flexible and efficient solution for the development of ship monitoring systems.

[0074] See also Figure 3 The present invention also provides a ship fault alarm method, which adopts the ship monitoring system of any of the above embodiments, comprising the following steps:

[0075] In the data collection step, the data collection layer obtains the monitoring data of each detection component in the ship's hardware equipment in real time and uploads it to the data management layer.

[0076] Among them, each detection component is installed on the key hardware equipment of the ship (such as engines, generators, steering gears, pumps, etc.) to collect key parameters such as temperature, pressure, current, voltage, speed, vibration, etc. in real time. Each detection component has independent data acquisition capabilities, collects relevant data through timing or triggering, and transmits these data to the data acquisition layer to convert them into digital signals for preliminary processing. The processed data is uploaded to the data management layer in real time through the ship's internal network, wired or wireless communication technology to ensure the timeliness and accuracy of the data.

[0077] In the data management step, the data management layer stores the uploaded monitoring data. The data management layer is used to store, read and back up the monitoring data uploaded by the data collection layer based on the corresponding storage rules and data access rules.

[0078] In the logical judgment step, the fault diagnosis unit of the business logic layer sends a request to the data management layer to obtain relevant monitoring data, and performs analysis and diagnosis based on the relevant monitoring data obtained in the request; if a fault is diagnosed, the fault information is submitted to the data management layer; the data management layer provides a standardized interface for access by the business logic layer, and supports querying and retrieving data in multiple ways such as by time, equipment, and parameters.

[0079] In the alarm step, the user page layer visualizes the fault information and related monitoring data. That is, the user page layer displays the fault information and related monitoring data to the user in an intuitive and easy-to-understand way through the graphical user interface (GUI). The user can confirm the fault, silence the alarm, generate a fault diagnosis report, and other operations through the user page layer. Of course, the system can also be set to support advanced functions such as user-defined alarm thresholds and setting fault notification methods (such as email, SMS, voice notification, etc.).

[0080] Among them, the principles, functions and effects of the specific steps can be referred to the implementation methods of the aforementioned ship monitoring system, and will not be repeated here.

[0081] In summary, the ship fault alarm method of the present invention realizes real-time monitoring of ship hardware equipment and rapid response to faults by constructing an efficient data acquisition, storage, analysis and visual display mechanism, providing a strong guarantee for the safe operation of the ship.

[0082] In addition, those skilled in the art should understand that, although there are many problems in the prior art, each embodiment or technical solution of the present invention can be improved in only one or several aspects, without having to solve all the technical problems listed in the prior art or background technology at the same time. Those skilled in the art should understand that the content not mentioned in a claim should not be used as a limitation on the claim.

[0083] Although the terms such as data acquisition layer, data management layer, business logic layer, user page layer, etc. are used more frequently in this article, the possibility of using other terms is not excluded. These terms are used only to more conveniently describe and explain the essence of the present invention; interpreting them as any additional restrictions is contrary to the spirit of the present invention; the terms "first", "second", etc. (if any) in the description and claims of the embodiments of the present invention and the above drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0084] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein with equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A ship monitoring system, characterized in that: include: The data collection layer, data management layer, business logic layer and user page layer are connected in sequence; The data acquisition layer is used to obtain the monitoring data of each detection component in the ship hardware equipment in real time and upload it to the data management layer; The data management layer is used to store, read and back up the monitoring data uploaded by the data acquisition layer, and is also used to provide the business logic layer with the monitoring data required for calculation and receive and store the result data and fault information after the calculation and analysis by the business logic layer, so that different modules in the business logic layer can access the result data through the data management layer. The business logic layer is used to obtain the monitoring data stored in the data management layer, and then perform calculations and analysis to provide auxiliary decision-making; the business logic layer at least includes an energy efficiency index calculation unit and a fault diagnosis unit; the energy index calculation unit includes a plurality of calculation modules for analyzing the energy consumption of each ship hardware device according to the monitoring data, and providing suggestions for energy efficiency optimization strategies; the fault diagnosis unit includes a plurality of diagnosis modules for analyzing the status of each ship hardware device according to the monitoring data and diagnosing whether there is a fault; The user page layer is used to provide a visual interactive interface for human-computer interaction with the ship monitoring system.

2. The ship monitoring system according to claim 1, characterized in that: The data acquisition layer at least includes a CAN server, a serial port server, a high-frequency signal collector, and a low-frequency signal collector that are directly or indirectly connected to the various detection components in the ship hardware equipment through a communication protocol to obtain the monitoring data of the detection components in real time and convert the monitoring data from physical parameters into digital signals.

3. The ship monitoring system according to claim 2, characterized in that: The data acquisition layer also includes a data processor, which includes at least one or more of a data acquisition module, a data analysis module, a data preprocessing module, and a data upload module; the data acquisition module is used to acquire monitoring data and verify the accuracy and completeness of the monitoring data; the data analysis module is used to parse monitoring data of different formats or protocols into a data format that can be processed by the system; the data preprocessing module is used to preprocess the monitoring data including at least one of data filtering, data smoothing, and outlier detection; the data upload module is used to match the processed monitoring data with the monitoring parameter code and upload it to the data management layer; the monitoring parameter code is a unique identification code for each type of monitoring data.

4. The ship monitoring system according to claim 1, characterized in that: The data management layer at least includes a centralized data management platform for centralized management of monitoring data and control of access rights; the centralized data management platform adopts a service-oriented architecture design and runs as a server, and communicates with the business logic layer and the data acquisition layer through the HTTP protocol, using the JSON data format as the standard format for data exchange; The centralized data management platform also develops several standardized interfaces to provide data exchange functions with other levels and modules.

5. The ship monitoring system according to claim 4, characterized in that: The data management layer also includes a database, which is used to store result data and fault information and also to store and manage configuration information of the business logic layer and the data acquisition layer; The database is at least configured with a data coding table module, a fault coding table module, a storage rule module, and a data access rule configuration module; the data coding table module is used to define and store the coding standards and mapping relationships between various types of monitoring data and monitoring parameter codes; The fault coding table module is used to define and store the coding standards and mapping relationships between various types of fault information and fault codes; The storage rule module is used to set the storage format, encryption method, storage location and storage period rules of the monitoring data; the data access rule configuration module is used to set the data access rights, access frequency restrictions and data access scope of each module.

6. The ship monitoring system according to claim 5, characterized in that: The storage cycle includes at least one of the following rules: Determine different storage cycle rules according to different types of monitoring data; According to the associated fault information, when a certain device fault is detected, the storage period of the monitoring data of the detected device is shortened; According to the working condition requirements of each ship's hardware equipment, the storage period of a certain type of monitoring data is shortened when the data changes at a preset high frequency.

7. The ship monitoring system according to claim 5, characterized in that: The data management layer also configures a buffer with a lock mechanism for each type of monitoring data, and the buffer is used to record and temporarily store the monitoring data; the database regularly stores the data in the buffer in the database permanently according to the storage rules of the storage rule module; When the data management layer receives a request to submit monitoring data, the data access rule configuration module verifies whether the request complies with the preset access rules. If the verification succeeds, the monitoring data in the buffer is updated according to the request. When the data management layer receives a request to obtain monitoring data, the data access rule configuration module also verifies whether the request complies with the preset access rules. If the verification succeeds, the monitoring data is read from the buffer and responded to according to the request.

8. The ship monitoring system according to claim 5, characterized in that: The database also includes a configuration file management module for managing the configuration information of the newly added functional modules in the business logic layer and the data acquisition layer; the configuration file management module updates the contents of the data coding table module, the fault coding table module, the storage rule module, and the data access rule configuration module according to the configuration information of the newly added functional modules in the business logic layer and the data acquisition layer, and automatically deploys the newly added functional modules in the business logic layer and the data acquisition layer based on the configuration information.

9. The ship monitoring system according to claim 8, characterized in that: The specific steps of adding a new function module to the business logic layer are: determining a unique identification code for the new function module and determining a unique data code for the new monitoring data of the new function module, wherein a specific bit of the data code is used to identify the monitoring position; completing the relevant configuration of the new function module in the database based on the identification code and the new data code; and automatically deploying the new function module on the business logic layer based on the relevant configuration of the new monitoring data in the database; The specific steps of adding a new functional module to the data acquisition layer are: determining a unique identification code for the new functional module and determining a unique data code for the new monitoring data of the new functional module, wherein a specific bit of the data code is used to identify the monitoring location; and completing the configuration of the new monitoring data in the database based on the identification code and the new data code; Automatically deploy new functional modules on the data collection layer based on configuration information; the configuration of the new monitoring data in the database includes at least the following information: the association between the new monitoring data and the fault information, the byte length required for the new monitoring data, the storage rules for the new monitoring data, and the identification code of the detection component from which the new monitoring data comes.

10. A ship fault alarm method, characterized in that: The ship monitoring system according to any one of claims 1 to 9 comprises the following steps: Data collection step, the data collection layer acquires the monitoring data of each detection component in the ship hardware equipment in real time and uploads it to the data management layer; A data management step, wherein the data management layer stores the uploaded monitoring data; In a logic judgment step, the fault diagnosis unit of the business logic layer sends a request to the data management layer to obtain relevant monitoring data, and performs analysis and diagnosis based on the relevant monitoring data obtained in the request; if a fault is diagnosed, the fault information is submitted to the data management layer; In the alarm step, the user page layer displays the fault information and related monitoring data visually.

Images