CN117615351A

CN117615351A - VDES shore-based integrated management system

Info

Publication number: CN117615351A
Application number: CN202311568252.XA
Authority: CN
Inventors: 张建东; 胡青; 冯晓蕊; 李徽; 李钰庚; 李洋; 云泽雨
Original assignee: Tianjin Communication Center Navigation Guarantee Center Of North China Sea Mot
Current assignee: Tianjin Communication Center Navigation Guarantee Center Of North China Sea Mot
Priority date: 2023-11-23
Filing date: 2023-11-23
Publication date: 2024-02-27

Abstract

The invention discloses a VDES shore-based integrated management system, which comprises a base station operation support system, a data management system and a shore-based interface service system; the base station operation support system is used for guaranteeing stable operation of the base station and providing functional support of base station driving management, AIS/ASM/VDE communication data exchange, operation log acquisition and base station configuration for VDES shore-based comprehensive management and control; the data management system is used for processing various data transmitted by the base station and specifically comprises AIS/ASM/VDE access service, data access buffer, distributed data storage and processing, data integrity monitoring, legal user and authority management of the base station and the like; the shore-based interface service system is used for carrying out information interaction between the shore and the user, and specific service functions comprise an interconnection and intercommunication platform service interface and a man-machine interaction service interface. The invention can comprehensively carry out VDES shore-based comprehensive management.

Description

VDES shore-based integrated management system

Technical Field

The invention relates to the field of VDES shore-based management and security, in particular to a VDES shore-based integrated management system.

Background

The VDES shore-based system is a key for acquiring and utilizing VDES data as an offshore information infrastructure necessary for constructing the VDES system. At present, research is mainly conducted on aspects of VDES space-based systems, terminal equipment, standard formulation and the like by research institutions at home and abroad, but research is less on aspects of VDES ground management system architecture and implementation technology, so that a VDES shore-based integrated management system is provided.

Disclosure of Invention

The technical problems to be solved by the invention are as follows: how to solve the problems in the aspects of the architecture and the realization technology of the VDES ground management system, and provides a VDES shore-based integrated management system.

The technical problems are solved by the following technical scheme, and the method comprises a base station operation supporting system, a data management system and a shore-based interface service system;

the base station operation support system is used for guaranteeing stable operation of the base station and providing functional support of base station driving management, AIS/ASM/VDE communication data exchange, operation log acquisition and base station configuration for VDES shore-based comprehensive management and control;

the data management system is used for processing various data transmitted by the base station and specifically comprises AIS/ASM/VDE access service, data access buffer, distributed data storage and processing, data integrity monitoring, legal user and authority management of the base station and the like;

the shore-based interface service system is used for carrying out information interaction between the shore and the user, and specific service functions comprise an interconnection and intercommunication platform service interface and a man-machine interaction service interface.

The base station operation support system further comprises functions of providing base station terminal interface service, AIS message support service, ASM message support service, VDE message support service, base station monitoring management support service and message receiving and transmitting service.

The content of the base station terminal interface service comprises connection service, statement sending, statement receiving, statement cleaning and base station data recovery;

the content of the AIS message support service comprises AIS data statement adaptation and encapsulation, AIS statement adaptation and receiving data;

the content of the ASM message support service comprises ASM data statement adaptation and encapsulation, and ASM statement adaptation and receiving data;

the content of the VDE message support service comprises VDE data statement adaptation and encapsulation, and VDE statement adaptation and received data;

the content of the base station monitoring management support service comprises base station monitoring management data statement adaptation and encapsulation, and base station monitoring management statement adaptation and analysis data;

the message receiving and transmitting service AIS channel service information transmitting content comprises ASM channel service information transmitting, VDE channel service information transmitting, base station configuration instruction transmitting, base station monitoring instruction receiving, received VDES information transmitting kafka, received batch VDES information transmitting kafka, received service response information transmitting kafka and received configuration response information transmitting kafka.

Further, the functions of the data management system include data access/buffer management services, distributed data processing services, distributed data storage services, data services, and environmental monitoring services.

Further, the data access/buffer management service data access content AIS data buffer, ASM data buffer, VDE data buffer, other data buffer, bulk AIS data buffer, bulk ASM data buffer, bulk VDE data buffer, bulk other data buffer;

the distributed data processing service comprises AIS data processing, SM data processing, VDE data processing and other data processing;

the content of the distributed data storage service comprises distributed file storage and distributed data storage;

the content of the data service comprises a data service interface, an AIS data service, an ASM data service, a VDE data service, a data analysis service and an application analysis service;

the content of the environment monitoring service comprises operating system monitoring and middleware monitoring.

The shore-based interface service system further comprises functions of a VDES service platform interface service, a man-machine interaction service, a VDES message background processing service, a base station configuration background processing service, a base station monitoring background service, a user and authority management service, a chart engine background service and an operation log service.

The content of the VDES service platform interface service comprises external interface service, service registration, service release and base station management background processing service;

The content of the man-machine interaction service comprises a chart engine, base station management, base station configuration service, base station monitoring service and background management service;

the content of the VDES message background processing service comprises AIS service message sending, ASM service message sending, VDE service message sending, AIS data query, ASM data query and VDE data query;

the base station configuration background processing service comprises AIS working frequency configuration, AIS broadcasting rule configuration, AIS berth frequency assignment, AIS berth frequency reservation, AIS report frequency group assignment, ASM working frequency configuration, ASM broadcasting rule configuration, ASM berth frequency reservation, VDE working frequency configuration, TBB frequency configuration, ASC frequency configuration and ship-to-ship VDE communication configuration;

the content of the base station management background processing service comprises communication protocol filtering rule configuration, remote control, message filtering rule configuration, base station driving management, IP pool management, port management, base station registration, asset retrieval, base station basic information retrieval, chart initialization configuration, fault and alarm management, mechanism management, base station data dictionary management, equipment identity information management, communication priority management, report management and service access management;

The content of the base station monitoring background service comprises base station basic monitoring, channel management, VDE access monitoring and interface service monitoring;

the content of the user and authority management service comprises user management, authority management, menu management and user group management;

the service content of the sea chart engine background service comprises the acquisition of ship berth data and the acquisition of base station data;

the service content of the running log service comprises a system operation log, a business message log and log archiving.

Compared with the prior art, the invention has the following advantages: the VDES shore-based integrated management system has good maintainability: the design adopts a modular design concept, and a shore-based management system is formed by a series of loosely coupled assemblies. Aiming at the characteristics of the VDES shore-based management system, the main business functions are split into individual components, and the development, testing and other stages of each individual component are independent of other services. In addition, when a new demand arises, problems of each party such as compatibility, influence degree and the like need to be considered, and the modular development can directly and rapidly modify the demand change. Each component is fine particles, a large-scale system is split into a plurality of components, so that the components are completely independent of each other and can communicate with each other, the maintainability of the system is improved, and the system is more worth popularizing and using;

The reliability is high: the reliability of the system needs to take the reliability as a core quality standard, and proper software development and testing technology is selected, so that the reliability of the VDES shore-based management system is improved by fault tolerance, restorability design and other methods.

The safety is good: in order to prevent the information of the system from being modified and destroyed, the security of the system needs to be designed. The invention mainly uses encryption technology, user authority control and original data and log information retention.

Drawings

FIG. 1 is a diagram of the overall logic architecture of a VDES shore-based management system of the present invention;

FIG. 2 is a diagram of the overall physical architecture of the VDES shore-based management system of the present invention;

FIG. 3 is a user interface versus system operational data flow diagram of the present invention;

FIG. 4 is a data flow diagram of the user interface of the present invention operating with a base station terminal;

fig. 5 is a data flow diagram of a base station terminal transmitting VDES data according to the present invention;

FIG. 6 is a data flow diagram of a user interface of the present invention for query service operations;

FIG. 7 is a data flow diagram of a system response VDES base station test system request service operation of the present invention;

fig. 8 is a flowchart of a base station terminal interface service module according to the present invention;

fig. 9 is a sequence diagram of a connection model established with a base station terminal device according to the present invention;

FIG. 10 is a sequence diagram of a message data transmission model of the present invention;

FIG. 11 is a sequence diagram of a message data reception model according to the present invention;

FIG. 12 is a sequence diagram of a base station data recovery processing model of the present invention;

FIG. 13 is a block diagram of AIS message support service components of the present invention;

FIG. 14 is a sequence diagram of a base station terminal vendor parameter model of the present invention;

FIG. 15 is a sequence diagram of ASM information conversion message data and transmission model according to the present invention;

FIG. 16 is a sequence diagram of an ASM message data receiving and information converting model according to the present invention;

FIG. 17 is a block diagram of a VDE message support service of the invention;

FIG. 18 is a sequence diagram of a base station terminal vendor parameter model of the present invention;

FIG. 19 is a sequence diagram of a VDE message data transfer and model transfer according to the present invention;

FIG. 20 is a sequence diagram of a message data receiving and information converting model according to the present invention;

FIG. 21 is a block diagram of a base station monitoring management support service of the present invention;

FIG. 22 is a sequence diagram of a manufacturer parameter model of a base station monitoring management terminal according to the present invention;

FIG. 23 is a sequence diagram of a base station configuration, management instruction information conversion message data and transmission model according to the present invention;

FIG. 24 is a sequence diagram of a base station answer and status monitoring message data reception and information conversion model of the present invention;

Fig. 25 is a block diagram showing the constitution of an information transmitting-receiving service according to the present invention;

fig. 26 is a sequence diagram of a traffic information transmission model of the present invention;

fig. 27 is a sequence diagram of a VDES information transfer model of the present invention;

FIG. 28 is a sequence diagram of a response message transmission model of the present invention;

FIG. 29 is a block diagram of a VDES message background processing service of the invention;

FIG. 30 is a sequence diagram of a user send information model of the present invention;

FIG. 31 is a sequence diagram of a user query information model of the present invention;

FIG. 32 is a block diagram of a base station management background processing service composition of the present invention;

FIG. 33 is a sequence diagram of a base station terminal configuration and control model of the present invention;

fig. 34 is a sequence diagram of a base station terminal management model of the present invention;

FIG. 35 is a block diagram of a base station configuration background processing service composition of the present invention;

FIG. 36 is a sequence diagram of a base station configuration model of the present invention;

FIG. 37 is a block diagram of a base station monitoring background processing service composition of the present invention;

FIG. 38 is a sequence diagram of a query monitoring result model of the present invention;

FIG. 39 is a sequence diagram of a real-time push monitoring result model of the present invention;

FIG. 40 is a sequence diagram of a database monitoring result model of the present invention;

FIG. 41 is a block diagram of a travel log service composition of the present invention;

FIG. 42 is a sequence diagram of a log query model of the present invention;

FIG. 43 is a diagram of the background service components of the chart engine of the present invention;

FIG. 44 is a sequence diagram of a monitoring data acquisition model of the present invention;

FIG. 45 is a sequence diagram of a query data acquisition model of the present invention;

FIG. 46 is a block diagram of a user and rights management service composition of the present invention;

FIG. 47 is a sequence diagram of a user and rights data storage model of the present invention;

FIG. 48 is a sequence diagram of a user and rights data acquisition model of the present invention;

FIG. 49 is a block diagram illustrating the data access/buffer management service components of the present invention;

FIG. 50 is a block diagram of a distributed data processing service composition of the present invention;

FIG. 51 is a sequence diagram of a cache read model of the present invention;

FIG. 52 is a sequence diagram of a data processing model of the present invention;

FIG. 53 is a block diagram of a distributed data storage service of the present invention;

FIG. 54 is a block diagram of a data service composition of the present invention;

FIG. 55 is a sequence diagram of a shore information acquisition model of the present invention;

FIG. 56 is a sequence diagram of a historical data acquisition model of the present invention;

fig. 57 is a block diagram of the environment monitoring service composition of the present invention.

Detailed Description

The following describes in detail the examples of the present invention, which are implemented on the premise of the technical solution of the present invention, and detailed embodiments and specific operation procedures are given, but the scope of protection of the present invention is not limited to the following examples.

As shown in fig. 1, this embodiment provides a technical solution: a VDES shore-based integrated management system comprises a base station operation support system, a data management system and a shore-based interface service system;

the shore-based interface service system is used for carrying out information interaction between a shore and a user, and specific service functions comprise an interconnection and interworking platform service interface and a man-machine interaction service interface;

the software development of the VDES shore-based management system comprises a base station operation support subsystem, a base station data management subsystem and an interface service subsystem, wherein the base station terminal interface service, the AIS message support service, the ASM message support service, the VDE message support service and other 20 services are formed. The logical architecture design of the whole VDES shore-based management system is shown in FIG. 1.

1. Ship-shore communication system

a) The base station system expands 4-base-station-base VDES base stations on the basis of the existing three base stations, has a complete AIS, ASM, VDE function, and provides network environment support for VDES system test research;

b) And the ship end system is used for installing 10 sets of shipborne VDES (virtual double-deck) shipborne terminals on the working ship of the North sea navigation security center, the working ship of the Tianjin maritime office and the commercial ship which is partly voluntarily tested on the basis of being compatible with all the existing AIS shipplatforms, and supporting the test research of the VDES shore-based communication network.

2. Data storage

a) And Kafka cache, respectively storing the structured data through different topics according to different service requirements. The method comprises the steps that Kafka refers to an object which issues a message to a certain topic as a data producer, an object which uses data on the certain topic as a data consumer, different topic data are input by the corresponding data producer, meanwhile, the corresponding consumer monitors the data state, the data flow is controlled by Kafka cache, the data flow is divided into a queue and a subscription mode, the processing mode of the queue is that a group of consumers read the message from a server, and only one consumer of the message is used for processing; in the subscription mode, each message is broadcast to all consumers subscribing to the message, which can be processed by the consumer receiving the message;

b) The redis cache is mainly used for caching ship states, storing a current latest ship state list according to integration of ship dynamic and static AIS data, and providing page display and calculation and use;

c) The relational database Mysql is mainly used for storing system operation basic data, test results and alarm state data, such as user information, system configuration information, system operation records, base station disconnection information and the like;

d) The non-relational large database hadoop is mainly used for storing dynamic and static historical information of the ship and is used for searching and analyzing historical airlines and the like;

e) And the big data calculation engine Spark is used for calculating the service data through the distributed data processing component by using Apache Spark as the big data calculation engine.

3. Business service component

a) The base station terminal interface service, the base station management system core service, the function of connecting, communicating, statement cleaning, base station data recovery and the like with the VDES base station terminal;

b) AIS message support service is mainly responsible for statement adaptation, analysis, encapsulation and other core functions of AIS channel messages;

c) ASM message support service is mainly responsible for statement adaptation, analysis, encapsulation and other core functions of ASM channel messages;

d) The VDE message support service is mainly responsible for core functions such as statement adaptation, analysis and encapsulation of VDE channel messages;

e) The base station monitoring management support service is mainly responsible for statement adaptation, analysis, encapsulation and other core functions of the base station monitoring management message;

f) Information receiving and transmitting service, which is responsible for the interface function of the information and data management subsystem which are sent by the system to the base station terminal and fed back by the base station terminal to the system;

g) The VDES message background processing service is responsible for sending and receiving the AIS/ASM/VDE service message and inquiring the AIS/ASM/VDE history message;

h) The base station management background processing service is responsible for providing management service functions such as asset retrieval, base station registration and maintenance, base station drive management, mechanism management, equipment identity information and the like;

i) The base station configures background processing service and is responsible for providing base station configuration functions such as working channels, message broadcasting rules, VDE bulletin boards and the like of the base station;

j) The base station monitors background service and is responsible for monitoring the operation information of various index items such as the working state, the message receiving and transmitting quantity, the channel occupation condition and the like of each base station;

k) The operation log service is responsible for the collection of operation logs and business logs and the archiving function of the logs;

l) a marine chart engine background service, which is responsible for providing data displayed based on a GIS map, such as AIS ship dynamic data, navigation aid equipment data, shore station data, ship positioning, ship history track inquiry and the like;

m) user and authority management service, responsible for authority management functions of users, roles, menus, user groups and the like;

n) data access/buffer management service, which is responsible for accessing the operation support subsystem and carrying out classified buffer on the received data;

o), the distributed data processing service is used for processing various AIS, ASM, VDE business data received in real time;

p), the distributed data storage service is responsible for carrying out distributed storage on the accessed original service data, various data indexes processed by the distributed data processing service and batch processing operation results;

q), the data service is in charge of receiving external requests, calling corresponding resources to complete corresponding calculation or realize access and request of specific data resources according to request information, and returning result data;

r), environment monitoring service, which is responsible for the environment monitoring of each node of the whole shore-based test system, such as CPU occupancy rate, memory occupancy rate, hard disk service condition, running state of specific service and the like of each server;

s), VDES service platform interface service, offer interface function with the marine intercommunication platform, including registration, release and connection state of the service monitor;

t), man-machine interaction service, through the user interaction page, realizing the display of the foreground function of the base station management system.

The functions of the base station operation support system comprise providing base station terminal interface service, AIS message support service, ASM message support service, VDE message support service, base station monitoring management support service and message receiving and transmitting service.

The functions of the data management system include data access/buffer management services, distributed data processing services, distributed data storage services, data services, and environmental monitoring services.

The data access/buffer management service data access content AIS data buffer, ASM data buffer, VDE data buffer, other data buffer, batch AIS data buffer, batch ASM data buffer, batch VDE data buffer, batch other data buffer;

The functions of the shore-based interface service system comprise VDES service platform interface service, man-machine interaction service, VDES message background processing service, base station configuration background processing service, base station monitoring background service, user and authority management service, sea chart engine background service and operation log service.

According to the management range of a North sea navigation support center and the responsibility range of a Tianjin communication center, four shore-based VDES base stations are built by reasonably measuring and calculating the effective acting distance of a shore-based VDES base station and the base station site of an AIS shore-based network system in a North sea area in the same place, and an old iron mountain base station, a North dry moat outside a city wall city base station, a North Changshan radar base station and a island base station are selected in engineering, and an demonstration network is formed by utilizing the existing AIS private network. The exemplary network can fully verify VDES related technology standards and provide support for future nationwide VDES network construction by accumulating experience with system operation. The system physical architecture is shown in fig. 2.

The system mainly builds cluster deployment by using virtualized examples, each cluster is relatively independent, capacity expansion is carried out in the clusters according to service pressure requirements, data communication is carried out among the clusters through an intranet, management is convenient, and usability, concurrency and stability are improved. User and interface access through HTTPS (hypertext transfer security protocol) is through a firewall to access the system, thereby ensuring data security and quality of service. The system deployment networking is mainly divided into an application service cluster, a big data platform cluster and a data storage cluster:

1. the application service cluster is divided into four parts, namely an operation support service cluster, a data management service cluster, a background business processing service cluster and a management system man-machine interaction cluster:

(a) The operation support service cluster is communicated with the base station equipment and is responsible for data access, receiving and transmitting, message processing and the like, and at least two examples require high IO and multithreading computation intensive examples;

(b) The data management service cluster is responsible for storing, processing, analyzing and managing various services and operation data, and at least two instances require high IO, large memory and multithreading computation intensive instances;

(c) Background business processing service clusters are responsible for background processing of business functions such as base station management, base station configuration, base station monitoring and the like, and at least two examples require high IO and multithread compute-intensive examples;

(d) And the management system man-machine interaction cluster is responsible for man-machine interaction of the management systems such as a chart engine, data monitoring, management configuration page and the like, and is at least two examples.

2. Big data platform cluster is divided into three parts, and Kafka, spark, hadoop is deployed respectively:

(a) At least three examples of the Kafka cluster require multithreading, large memory and IO intensive examples, and the Kafka cluster is deployed;

(b) Spark clusters, at least three instances, requiring high IO, large memory, multi-threaded compute intensive instances, deploying Spark clusters;

(c) And the Hadoop cluster is deployed by at least three examples, namely, a large memory, a large hard disk and an IO intensive example.

3. The data storage cluster is divided into two parts, and Redis and MySQL are deployed respectively:

(a) At least two examples of Redis clusters, namely a large memory, a large hard disk and IO intensive examples, are required to be deployed;

(b) MySQL clusters, at least two instances, requiring large memory, large hard disk, IO intensive instances, deploy MySQL clusters.

According to the system operation state, as shown in fig. 3-7, the data flows of the system are classified into the following 5 types: 1) The base station terminal feeds back AIS/ASM/VDE channel data users in real time and carries out configuration management of the system through a man-machine interaction interface;

2) The user configures the base station terminal and establishes connection through the man-machine interaction interface;

3) The base station terminal feeds back AIS/ASM/VDE channel data in real time;

4) The user performs system query service (including monitoring result query) operation through a man-machine interaction interface;

5) The system responds to the VDES base station to test the system for service operation.

The technical development scheme for realizing the VDES shore-based test system is divided into the following parts according to the design of a service architecture:

1) Front page

a) Realizing a page frame by using Html5, javaScript, vue. Js and LayUI, and displaying a basic page;

b) Realizing chart display by using Echarts, realizing chart display based on the development of the leaf components, and displaying superimposed objects;

c) The method comprises the steps that foreground and background data communication uses an Ajax to call a rear-end HTTP REST interface, real-time data pushing uses a WebSocket interface, and the data format is Json;

d) The front-to-back office authentication uses JWT.

2) Backend services

a) The system development uses a Sprint Boot framework for development, and the logic business processing is realized by using Java language;

b) The deployment container uses Apache Tomcat to communicate with each other by using HTTP REST interface;

c) The back end provides HTTP REST interface for the front stage, and exchanges request and data with the front stage via the interface, and provides the same time

The WebSocket interface is used for pushing data for the foreground;

d) And realizing the sea chart service of the WMS interface by using the ChartServer.

3) Big data processing

a) Real-time calculation is realized by Spark streaming, real-time data in the cache are consumed according to batches at regular time according to task scheduling, and the result is output to a relational database;

b) And the batch processing calculation is realized by using Spark core, historical data in Hadoop is read according to task scheduling to calculate, and the result is output to a relational database.

4) Data storage

a) Using Redis to record state data of the ship and the shore station, and providing the latest states of the ship and the shore station for real-time calculation, batch processing calculation and page display;

b) And running basic data, analysis results and alarm state data by using a MySQL storage system.

Service identification

As shown in fig. 8, the service identifier is: baseDeviceInterfaceLevice

Purpose of service

The service provides link layer connection and message interaction between the system and the base station terminal.

List of functions of a service

1) The method comprises the steps of obtaining a database, and obtaining an address and a port parameter of terminal equipment of a physical connection base station;

2) Establishing and maintaining a connection state with a base station terminal device which is physically connected;

3) Feeding back a connection state with a base station terminal;

4) Completing protocol exchange with a base station terminal;

5) Forwarding the received original data so as to complete the storage of the original data;

6) Monitoring base station data recovery port information, finishing reading recovery data according to conditions, and forwarding the recovery data to finish original data storage;

7) The received real-time data/recovery data is filtered according to the configuration parameters;

8) Forwarding the filtered data;

9) And receiving data to be transmitted by the base station terminal and forwarding the data to the base station terminal.

Service composition framework

The service consists of 5 modules, of which:

1) And connecting the service module. Connection establishment between the management system and the appointed base station terminal is realized, and hoisting connection is initiated after connection interruption; feedback of connection status; actual sending and receiving of sentences;

2) And a statement sending module. The interface is connected with the service module to realize the transmission of the function statement to the appointed terminal equipment;

3) And a sentence receiving module. The interface is connected with the service module to realize the function statement receiving of the terminal equipment; on one hand, storing the original data of all received sentences, and on the other hand, sending the received sentences to a sentence cleaning module for processing;

4) And a statement cleaning module. The interface is connected with the statement receiving module to realize statement conditions under the condition of specified statement cleaning rules, the received statement meeting the cleaning rules is filtered, and the filtered message is sent to subsequent service processing according to the message type;

5) And a base station data recovery module. And the interface is connected with a base station data recovery file server, monitors the port of the server, and reads the recovery data file in the server in a file reading mode after receiving the recovery data request.

As shown in FIGS. 9-12, a service transaction model

1) Establishing a connection model with a base station terminal device

And after the interface service is started, reading the address and port configuration information records of the base station managed by the system in the database, establishing connection with the base station terminal according to the given address and port, and feeding back the connection state to the system.

2) Message data transmission model

After receiving the data of the statement sending module, the interface service sends the data to be sent to the appointed address and the port in sequence. When a channel is blocked, a rearrangement mechanism based on priority (AIS > ASM > VDE) is supported to be implemented in a connection service module.

3) A message data receiving model;

4) And recovering the base station data to a processing model.

Description of the algorithm

1) VDES base station communication

a) Acquiring base station connection information through base station management, testing whether the base station can be connected or not, and returning a test connection result;

b) And acquiring a base station connection information list through base station management, establishing connection SOCKET connection with the VDES base station terminal equipment through the designated IP and port, and keeping long connection. If the current VDES equipment cannot be connected, reconnecting until the connection is successful;

c) After successful connection with the VDES base station terminal equipment, writing the connection success state into a relational database (base station disconnection information table);

d) Monitoring the connection state, if the intermediate connection is disconnected, writing the connection disconnection state into a relational database (a base station disconnection information table);

e) After the connection is disconnected, the system automatically starts a reconnection mechanism until the reconnection with the SOCKET server is successful. Writing the connection success state into a relational database (a base station disconnection information table);

f) After the connection is successfully established, the received sending statement of other services is sent to the appointed VDES base station terminal equipment;

g) After the connection is successfully established, the input data is continuously received. Respectively sending the received data containing the receiving time to a statement cleaning flow and storing the data into Kafka VDES original message data;

h) And acquiring updated base station connection information sent by the base station management, updating and maintaining the current connected base station according to the updated information, interrupting the non-existing base station connection, reestablishing a new SOCKET connection, and feeding back the base station connection maintenance result to the system.

2) Statement cleaning

a) Acquiring a message statement (containing information of data recovery) sent by a base station;

b) Performing exclusive OR check on the message statement;

c) Performing statement format verification according to the message statement prefix;

d) Checking whether the message length and the message number are abnormal or not according to the message number;

e) If the verification fails, storing the failed statement in a relational database (statement cleaning data table) according to types;

f) The sentence passed by the verification is stored in Kafka VDES effective message data;

g) AIS sentences in the effective message data are output to AIS message supporting service for adaptation and analysis;

h) Outputting ASM sentences in the effective message data to ASM message support service for adaptation and analysis;

i) Outputting VDE sentences in the effective message data to a VDE message support service for adaptation and analysis;

j) And outputting the base station monitoring management statement in the effective message data to the base station monitoring management message support service for adaptation and analysis.

3) Base station data recovery

a) After the base station management system and the base station successfully establish SOCKET connection, the base station transmits data in the disconnection period to a designated data recovery file server;

b) After the connection is restored with the base station, acquiring a designated file from a data restoration file server according to a default rule for reading, and acquiring data in a disconnection period;

c) And respectively sending the acquired data in the disconnection period to a statement cleaning flow and Kafka VDES original message data.

The service interface base station terminal interface service and external service interfaces are as follows:

1) And the interface between the terminal interface service of the base station and MySQL are used for completing the storage of the base station disconnection information and the like.

2) Interface with Kafka interface base station terminal interface service interfaces with Kafka, through which storage of Kafka VDES original message and the like is completed.

3) Interface base station terminal interface service with message support service and interface of message support service, and the adaptation and analysis of different types of sentences are completed through the interface.

4) Interface base station terminal interface service with file recovery server and interface with file recovery server, and data recovery input/output during base station disconnection is completed through the interface

1) Input device

a) The encapsulated AIS transmits data;

b) The encapsulated ASM transmits data;

c) The encapsulated VDE sends data;

d) The encapsulated base station monitors and manages the sending data;

e) Base station connection information;

f) And recovering the file during the disconnection period of the base station.

2) Output of

a) A base station disconnection information table;

b) Statement cleaning data table;

c) Kafka VDES original message data;

d) Kafka VDES effective message data.

Service external interface configuration description:

service external interface configuration description:

AIS message support service scheme

Service identification

The service identifier is as follows: AISSAGESSUPPORtService

Purpose of service

The service provides bidirectional conversion between AIS information format supported by the system and message format supported by the base station terminal, and compatibility processing of some messages which have not formed standard for different manufacturers.

List of service functions

1) Reading a database to obtain configuration parameters (manufacturer code numbers, statement mapping and the like) of all base station terminal manufacturers supported by the system;

2) Receiving AIS service information from an information receiving and transmitting service;

3) Performing message conversion on AIS service information according to manufacturer parameters of a base station terminal;

4) The converted message is sent to a base station terminal interface service;

5) Receiving AIS message data from base station terminal interface service;

6) Information conversion is carried out on AIS message data according to manufacturer parameters of a base station terminal;

7) And the converted business information is sent to the information receiving and transmitting service.

Service composition framework

The service consists of 3 modules, of which:

and a parameter management module. The processing of obtaining, caching, updating and the like of configuration parameters of a base station terminal manufacturer is realized;

1) And (5) adapting and packaging the module by AIS data sentences. Vendor adaptation is carried out on the sending information, a corresponding message is generated, and the generated message is sent to a corresponding interface;

the AIS statement adapts and parses the data module. And according to the analysis of the message completed by the manufacturer of the base station terminal, generating corresponding service information, and transmitting the generated service information to a corresponding interface.

The module component frame is shown in fig. 13.

14-16, service transaction model

1) Acquiring a base station terminal manufacturer parameter model

The information receiving and transmitting service sends information to the parameter management module, and the parameter management module stores terminal manufacturer parameter information and responds the response to the information receiving and transmitting service.

2) AIS information conversion message data and transmission model

The information receiving and transmitting service sends information to an AIS data statement adapting and packaging module, after the module obtains the information, the parameter management module obtains the configuration parameters of the base station terminal, and the statement after adapting and packaging is transmitted to the base station terminal interface service.

3) AIS message data receiving and information converting model

The base station terminal interface service sends sentences to the AIS data sentence adapting and analyzing module, which obtains the configuration parameters of the base station terminal through the parameter management module, then analyzes the data, and sends the information to the information receiving and transmitting service.

Description of the algorithm

1) ASM data encapsulation statement adaptation and encapsulation

a) Carrying out data analysis and data verification on received ASM transmission data (JSON format);

b) According to the information of the sending base station, performing adaptation and distinguishing packaging sentences;

c) According to the respective packaging rules, data packaging is carried out to form sentences;

d) And sending the message to the packaged ASM statement through the base station terminal interface service.

2) Statement adaptation and parsing of ASM data

a) Received ASM message data (including recovery data);

b) Receiving base station information according to the message, performing adaptation, and distinguishing analysis sentences;

c) Analyzing the sentences according to the message and the message rule;

d) And outputting the analyzed ASM data (JSON format) to an information receiving and transmitting service.

Service interface

The ASM message support service and external service interface is as follows:

1) Interface for interfacing services with a base station terminal

And the ASM message support service and the interface of the base station terminal interface service complete the transmission of the ASM message through the interface.

2) Interface with information receiving and transmitting service

And the ASM message support service and the information receiving and transmitting service are connected through the interface, so that the ASM information is received and transmitted.

Input/output

1) Input device

a) ASM service message information and ASM channel base station configuration information sent by the service component;

b) ASM original message information reported by each VDES base station.

2) Output of

a) And (5) carrying time and source JSON data after ASM channel analysis.

VDE message support service scheme

Service identification

The service identifier is as follows: VDEMessageSupportService

Purpose of service

The service provides bidirectional conversion between the VDE information format supported by the system and the message format supported by the base station terminal, and compatibility processing of some messages which are not formed into standards for different manufacturers.

List of service functions

2) Receiving VDE service information from an information receiving and transmitting service;

3) Performing message conversion on the VDE service information according to manufacturer parameters of the base station terminal;

4) The converted message is sent to a base station terminal interface service;

5) Receiving VDE message data from a base station terminal interface service;

6) Converting the VDE message data according to manufacturer parameters of the base station terminal;

Service composition framework

The service consists of 3 modules, of which:

1) And a parameter management module. The processing of obtaining, caching, updating and the like of configuration parameters of a base station terminal manufacturer is realized;

2) The VDE adapts and encapsulates the module according to statements. Vendor adaptation is carried out on the sending information, a corresponding message is generated, and the generated message is sent to a corresponding interface;

3) The VDE sentence is adapted and parsed into the data module. And according to the analysis of the message completed by the manufacturer of the base station terminal, generating corresponding service information, and transmitting the generated service information to a corresponding interface.

The module component frame is shown in fig. 17.

As shown in FIGS. 18-20, a service transaction model

1) Acquiring a base station terminal manufacturer parameter model

2) VDE information conversion message data and transmission model

The information receiving and transmitting service sends information to the VDE data statement adapting and packaging module, after the module obtains the information, the module obtains the configuration parameters of the base station terminal through the parameter management module, and the statement after adapting and packaging is transmitted to the base station terminal interface service.

3) VDE message data receiving and information converting model

The base station terminal interface service sends sentences to the VDE data sentence adapting and analyzing module, which obtains the configuration parameters of the base station terminal through the parameter management module, then completes the data analysis and sends the information to the information receiving and transmitting service.

Description of the algorithm

1) VDE data encapsulation statement adaptation and encapsulation

a) Carrying out data analysis and data verification on received VDE transmission data (JSON format);

d) And sending the message to the packaged VDE statement through the interface service of the base station terminal.

2) Statement adaptation and parsing of VDE data

a) Received VDE message data (including recovery data);

c) Analyzing the sentences according to the message and the message rule;

d) And outputting the analyzed VDE data (JSON format) to an information receiving and transmitting service.

Service interface

The VDE message support service and external service interface is as follows:

1) Interface for interfacing services with a base station terminal

And the VDE message supports the interface between the service and the base station terminal interface service, and the transmission of the VDE message is completed through the interface.

2) Interface with information receiving and transmitting service

And the interface of the VDE message supporting service and the information receiving and transmitting service is used for receiving and transmitting the VDE information.

Input/output

1) Input device

a) VDE service message information and VDE channel base station configuration information sent by the service component;

b) And the VDE original message information reported by each VDES base station.

2) Output of

a) And (5) carrying time and source VDE channel analysis JSON data.

3.5 base station monitoring management support service scheme

3.5.1 service identification

The service identifier is as follows: MCMessageSupportService

3.5.2 service purposes

The service provides the conversion from the management information of the base station terminal equipment to the management message, and the conversion from the response message and the monitoring message of the base station terminal to the monitoring information. And supporting compatibility processing for terminal equipment of different factories.

List of service functions

2) Receiving configuration and management instruction information from a base station terminal of an information receiving and transmitting service;

3) Message conversion is carried out on the instruction information according to manufacturer parameters of the base station terminal;

4) The converted message is sent to a base station terminal interface service;

5) Receiving a response message and a monitoring message from a base station terminal interface service;

6) Information conversion is carried out on the response and monitoring message data according to manufacturer parameters of the base station terminal;

7) And the converted response and monitoring information is sent to the information receiving and transmitting service.

Service composition framework

The service consists of 3 modules, of which:

2) And the base station monitors the management data statement adaptation and encapsulates the module. Vendor adaptation is carried out on configuration and management control information of the base station terminal, corresponding messages are generated, and the generated messages are sent to corresponding interfaces;

3) The base station monitoring management statement adapts and parses the data module. And according to the response and analysis of the monitoring message completed by the manufacturer of the base station terminal, generating corresponding monitoring information, and transmitting the generated monitoring information to the corresponding interface.

The module component frame is shown in fig. 21.

As shown in FIGS. 22-24, a service transaction model

1) Acquiring a base station terminal manufacturer parameter model

2) Base station configuration and management instruction information conversion message data and transmission model

The information receiving and transmitting service sends information to the base station monitoring management data statement adapting and packaging module, after the module obtains the information, the parameter management module obtains the configuration parameters of the base station terminal, and the statement after adapting and packaging is transmitted to the base station terminal interface service.

3) Base station response and state monitoring message data receiving and information conversion model

The base station terminal interface service sends a statement to the base station monitoring management statement adapting and analyzing module, and the module obtains the configuration parameters of the base station terminal through the parameter management module, then completes data analysis and sends information to the information receiving and transmitting service.

Description of the algorithm

1) Base station monitoring management data encapsulation statement adaptation and encapsulation

a) Carrying out data analysis and data verification on received base station monitoring management transmission data (JSON format);

d) And sending the message through the base station terminal interface service by the packaged base station monitoring management statement.

2) Statement adaptation and parsing of base station monitoring management data

a) The received base station monitors the management message data (including recovery data);

c) Analyzing the sentences according to the message and the message rule;

d) And outputting the analyzed base station monitoring management data (JSON format) to the information receiving and transmitting service.

Service interface

The interface between the base station monitoring management message supporting service and the external service is as follows:

1) Interface for interfacing services with a base station terminal

And the base station monitoring management message supports an interface between the service and the interface service of the base station terminal, and the transmission of the base station monitoring management message is completed through the interface.

2) Interface with information receiving and transmitting service

And the interface of the base station monitoring management message supporting service and the information receiving and transmitting service is used for completing the receiving and transmitting of the base station monitoring management information.

Input/output

1) Input device

a) Base station monitoring management service message information and base station monitoring management channel base station configuration information sent by a service component;

b) The base station monitoring and managing original message information reported by each VDES base station.

2) Output of

a) And (5) carrying time and source resolved JSON data.

Information receiving and transmitting service scheme

Service identification

The service identifier is as follows: informationTransferService

Purpose of service

The service provides the interface function of the information and data management system, wherein the information is sent to the base station terminal by the system, and the information is fed back to the system by the base station terminal.

List of service functions

1) Receiving configuration and management instruction information of a base station terminal from a data management system, and forwarding the configuration and management instruction information to a base station monitoring management support service;

2) Receiving the sending information of the channels AIS, ASM, VDE and the like from the data management system and forwarding the sending information to the corresponding support service;

3) And receiving the business class information and the monitoring class information from each support service, and forwarding the business class information and the monitoring class information to a data management system.

Service composition framework

The service consists of 7 modules, of which:

1) And the AIS channel service information sending module. Transmitting AIS information to be transmitted and corresponding auxiliary information to an AIS message supporting service;

2) And the ASM channel service information sending module. Transmitting ASM information to be transmitted and corresponding auxiliary information to ASM message support service;

3) And a VDE channel service information sending module. Transmitting the VDE information to be transmitted and corresponding auxiliary information to a VDE message support service;

4) And the base station monitors the management information sending module. The base station monitoring management information to be sent and corresponding auxiliary information are sent to the base station monitoring management support service;

5) The base station configures the instruction sending module. Transmitting the configuration information of the base station terminal to be transmitted to a base station monitoring management support service;

6) And a VDES information transmission module. Receiving information from AIS, ASM, VDE message support service, and sending the information to a data management system after time sequencing;

7) And the response information transmission module. And receiving information from the support service, judging and acquiring response information of the sending service message, and sending the response information to the data management system after time sequencing.

The module component frame is shown in fig. 25.

As shown in FIGS. 26-28, a service transaction model

1) Service information transmission model

The business information sending model sends the information sent by the data management system to the message supporting service, and simultaneously sends the information to the response information transmission module.

2) VDES information transmission model

And receiving the information from the AIS, ASM, VDE message support service, and sending the information to a data management system after time sequencing and simultaneously sending the information to a response information transmission module.

3) Response information transmission model

And receiving the information from the VDES information transmission module, performing service judgment through the received information of the information transmission module, generating response information, and sending the response information to the data management system after time sequencing.

Description of the algorithm

1) Service and monitoring management data transceiver

a) Monitoring service information in a buffer memory of Kafka service message sending data received by Kafka, and classifying according to service types;

b) Transmitting the AIS service message through AIS message support service;

c) Carrying out service message sending on ASM service messages through ASM message supporting service;

d) The VDE service message is sent through a VDE message support service;

e) Monitoring configuration data in a cache of Kafka base station configuration distribution data received by Kafka, and classifying according to service types;

f) Performing base station configuration work on the appointed base station through AIS message supporting service by using AIS service related configuration information;

g) Performing base station configuration work on the appointed base station through ASM message support service by using ASM service related configuration information;

h) The relevant configuration information of the VDE service is processed through the VDE message supporting service to carry out base station configuration work on the appointed base station;

i) The base station monitoring management related configuration information is used for carrying out base station configuration work on the appointed base station through the base station monitoring management message supporting service;

j) Monitoring test request data in a cache of Kafka test service request data received by Kafka, and classifying according to service types;

k) Carrying out corresponding test on the specified base station by AIS service related test information through AIS message supporting service;

l) carrying out corresponding test on the appointed base station by ASM service related test information through ASM message support service;

m) carrying out corresponding test on the appointed base station by the VDE service related test information through the VDE message support service;

n) correspondingly testing the appointed base station by the base station monitoring management related test information through the base station monitoring management message supporting service;

o) receiving information through an AIS message support service, and storing the received information into a Kafka cache (storing non-test base station real-time received data into Kafka VDES structured data according to the type of a data source, storing loss connection recovery data into Kafka VDES structured data batch, and storing test base station received data into Kafka test message received data);

p) receiving information through an ASM message support service, and storing the received information into a Kafka cache (storing non-test base station real-time received data into Kafka VDES structured data according to the type of a data source, storing loss connection recovery data into Kafka VDES structured data batch, and storing test base station received data into Kafka test message received data);

q) receiving information through the VDE message supporting service, and storing the received information into a Kafka cache (storing non-test base station real-time received data into Kafka VDES structured data according to the data source type, storing the loss connection recovery data into Kafka VDES structured data batch, and storing test base station received data into Kafka test message received data);

r) receiving information through a base station monitoring management message supporting service, and storing the received information into a Kafka cache (non-test base station real-time received data are stored into Kafka VDES structured data according to the data source type, loss connection recovery data are stored into Kafka VDES structured data batch, and test base station received data are stored into Kafka test message received data);

s) if the received data is judged to be the response of the sending service message, the response message is cached in Kafka service message response data;

t) if it is judged that the received data is a response to transmitting the configuration information, the response message is buffered in Kafka base station configuration response data.

Service interface

The information transmitting and receiving service and external service interface is as follows:

1) Interface to Kafka service

And the information receiving and transmitting service and the Kafka service are connected through the interface, and the monitoring and storage of the statement are completed.

Input/output

1) Input device

a) Kafka service message transmission data

The Kafak service message sending data input information is as follows:

b) Kafka base station configuration distribution data

The Kafak base station configuration distribution data input information is as follows:

fields	Description of the invention
		serviceId	Base station configuration service ID
shoreMmsi	Receiving base station MMSI
		uuid	Unique identifier
data	Base station configuration service transmission data (JSON format)

2) Output of

a) Kafka VDES structured data input information

The Kafak VDES structured data input information is as follows:

fields	Description of the invention
		type	Data type (AIS, ASM, VDE, others)
receiveTime	Message reception time
		shoreMmsi	Receiving base station MMSI
data	VDES structured data (JSON format)

b) The Kafka VDES structured data is bulk-fed with information (consistent with the Kafak VDES structured data).

Configuration item description

Service external interface configuration description:

parameter name	Description of the invention
		Kafka Cluster IP	IP address and port number of Kafka cluster
Kafka cluster topic	Topic name of Kafka cluster requiring transmission/reception of data

VDES message background processing service scheme

Service identification

The service identifier is as follows: VDESOPERATION ProcessService

Purpose of service

The present service provides for the handling of VDES operations from different initiators, including platform interface services and man-machine interaction platforms. Including information transmissions of different channels and data queries of different channels.

List of service functions

1) Receiving a service information sending request from a platform interface service and forwarding the service information sending request to a data management system;

2) Receiving an information inquiry request from a platform interface service and forwarding the information inquiry request to a data management system;

3) Receiving a service information sending request from a man-machine interaction platform and forwarding the service information sending request to a data management system;

4) And receiving an information inquiry request from the man-machine interaction platform and forwarding the information inquiry request to a data management system.

3.7.4 service composition framework

The service consists of 6 modules, of which:

1) And the AIS service information processing module. Receiving AIS service information sending requests from a platform interface and a man-machine interaction platform, extracting service information and forwarding the service information to a data management system;

2) And the ASM service information processing module. Receiving ASM service information sending requests from a platform interface and a man-machine interaction platform, extracting service information and forwarding the service information to a data management system;

3) And a VDE service information processing module. Receiving a VDE service information sending request from a platform interface and a man-machine interaction platform, extracting service information and forwarding the service information to a data management system;

4) AIS information inquiry module. Receiving AIS service information inquiry requests from a platform interface and a man-machine interaction platform, forwarding the requests to a data management system, and feeding back response results of the data management system to a requester;

5) And the ASM information query module. Receiving ASM service information inquiry requests from a platform interface and a man-machine interaction platform, forwarding the requests to a data management system, and feeding back response results of the data management system to a requester;

6) And a VDE information query module. And receiving a VDE service information inquiry request from the platform interface and the man-machine interaction platform, forwarding the request to the data management system, and feeding back a response result of the data management system to the requester.

The module component frame is shown in fig. 29.

As shown in fig. 30 and 31, the service transaction model includes a user transmission information model and a user query information model.

Description of the algorithm

1) AIS service message transmission

a) Acquiring AIS sending message information of a front-end HTTP request, and judging whether the message information is complete;

b) Calculating a transmitting base station according to message information (broadcasting or addressing, destination MMSI of addressing);

c) AIS sends message to store to relational database (send message information table);

d) And (3) packaging the AIS sending message information into JSON format data (adding a unique message identifier) and sending the JSON format data to Kafka service message sending data. Transmitting a message by an information transmitting and receiving service;

e) Monitoring the AIS message response result (acquired according to the unique identifier) received by Kafka service message response data, and storing the response result in a relational database (transmitting message information table);

f) And returning the response result to the browser foreground.

2) ASM service messaging

a) Acquiring ASM sending message information of a front-end HTTP request, and judging whether the message information is complete;

c) ASM sends message to store in relational database (send message information table);

d) And (3) packaging the ASM sending message information into JSON format data (adding a message unique identifier symbol) and sending the JSON format data to Kafka service message sending data. Transmitting a message by an information transmitting and receiving service;

e) Monitoring the response result (acquired according to the unique identifier) of the ASM message received by Kafka service message response data, and storing the response result in a relational database (a message information table is sent);

f) And returning the response result to the browser foreground.

3) VDE service messaging

a) Obtaining VDE sending message information of a front-end HTTP request, and judging whether the message information is complete;

c) The VDE sends the message to store in the relational database (send message information table);

d) And the VDE sending message information is packaged in JSON format data (added with a message unique identifier) and sent to Kafka service message sending data. By 06.01: the business and monitoring management data are received and transmitted, monitored, obtained and sent;

e) Monitoring the response result (obtained according to the unique identifier) of the received VDE message of Kafka service message response data, and storing the response result in a relational database (a message information table is sent);

f) And returning the response result to the browser foreground.

4) AIS historical data query background processing

a) Acquiring browser input AIS historical data query conditions such as start time, end time, MMSI, message number, ship name, call sign and the like;

b) And acquiring an AIS historical data information list by calling an AIS historical data query interface in the AIS data service, and outputting the AIS historical data information list to a browser foreground.

5) ASM historical data query background processing

a) Acquiring the query conditions of ASM historical data input by a browser, such as start time, end time, MMSI, message number and the like;

b) And acquiring an ASM historical data information list by calling an ASM historical data query interface in the ASM data service, and outputting the ASM historical data information list to a browser foreground.

6) VDE history data query background processing

a) Obtaining the query conditions of the VDE history data input by the browser, such as the start time, the end time, the MMSI and the like;

b) And acquiring a VDE history data information list by calling a VDE history data query interface in the VDE data service, and outputting the VDE history data information list to a browser foreground.

Service interface

The interface between the VDES message background processing service and the external service is as follows:

1) Interface to MySQL

And the VDES message background processing service is connected with the MySQL interface, and the storage of the service message channel sending data is completed through the interface.

2) Interface to Kafka

And the VDES message background processing service is connected with the interface of the Kafka, and the storage of the Kafka service message sending data and the Kafka service message response data is completed through the interface.

3.7.9 input/output

1) Input device

a) The man-machine interaction business message sends data;

b) The man-machine interaction history message retrieves data.

2) Output of

a) The Kafka service message transmits data.

Configuration item description

Service external interface configuration description:

parameter name	Description of the invention
		Data storage service IP	IP address and port number requiring data storage service
User name password for data storage service	User name and password for data storage services
		Kafka Cluster IP	IP address and port number of Kafka cluster
Kafka cluster topic	Topic name of Kafka cluster requiring transmission/reception of data

Base station management background processing service scheme

Service identification

The service identifier is as follows: shorStationananage service

Purpose of service

The present service provides for the handling of VDES base station management from a man-machine interaction platform. The processing result is stored in a database, and after the system is started or the management setting is changed, the data management system sends the related information to the required module for use.

The service access management is arranged for providing the external service of the system transition period, and the function is realized by a marine intercommunication platform (MCP) under the e-navigation architecture.

List of service functions

1) Receiving IP pool and port management information data from a man-machine interaction platform and storing the IP pool and port management information data into a database;

2) Receiving an IP pool and port management data query request from a man-machine interaction platform, and acquiring and feeding back a query result through a database;

3) Receiving base station registration and maintenance information from a man-machine interaction platform, verifying that the base station registration and maintenance information meets the IP pool and port management requirements, storing the base station registration and maintenance information in a database, and forwarding the base station registration and maintenance information to a data management system;

4) Receiving a base station information query request from a man-machine interaction platform, and acquiring a query result through a database and feeding back the query result;

5) Receiving base station control operation information from a man-machine interaction platform and forwarding the information to a data management system;

6) Receiving chart initialization information from a man-machine interaction platform and storing the chart initialization information into a database;

7) Receiving a chart initialization information query request from a man-machine interaction platform, and acquiring a query result through a database and feeding back the query result;

8) Receiving a fault and alarm information query request from a man-machine interaction platform, and acquiring a query result through a database and feeding back the query result;

9) Receiving information of each base station fault and alarm manager from a man-machine interaction platform and storing the information into a database;

10 After receiving the fault and alarm information sent by the data management system, sending the fault and alarm information to a designated mailbox according to the alarm receiving mail information of the base station;

11 Receiving the mechanism management newly-increased and maintenance information from the man-machine interaction platform and storing the newly-increased and maintenance information into a database;

12 Receiving an information query request from a human-computer interaction platform mechanism, acquiring a query result through a database and feeding back the query result;

13 Receiving the addition, deletion, modification and search operation of the data dictionary file and the code information from the man-machine interaction platform, and storing the code information into a database after the analysis of the digital dictionary file;

14 Receiving the operations of adding, deleting, modifying and checking other types of equipment (such as AtoN) accessed to the VDES system from the man-machine interaction platform, and storing the equipment information into a database;

15 Receiving classification configuration of the VDE channel information from the man-machine interaction platform, designating different types of VDE messages with different priorities, and storing configuration results in a database;

16 Receiving management information of the report form from the man-machine interaction platform, including information such as report time, statistical time period, report sender and the like, and storing configuration results into a database;

17 Receiving management information about external access from a man-machine interaction platform, including information about whether access is allowed or not, whether access IP is allowed, access authority and the like, and storing configuration results in a database.

Module frame

The service consists of 20 modules, which make up the framework shown in fig. 32.

As shown in FIGS. 33-34, a service transaction model

1) The base station terminal configures and controls the model, the HTTP service sends the configuration data or control instruction to the corresponding processing module, and after the processing of the module, the HTTP service is sent to the kafka through the base station configuration data sending module.

2) Base station terminal management model

The HTTP service sends the management data to the corresponding processing module, and after the management data are processed by the processing module, the management data are sent to the database through the base station configuration data sending module.

Description of the algorithm

1) IP pool and port management

a) Acquiring the IP and port range data of the shore-based management system through a relational database (IP port range table), and outputting the data to the front end of the browser for modifying the IP and the port range;

b) Acquiring IP range data (IP upper limit and IP lower limit) input by a browser;

c) Acquiring port range data (port upper limit and port lower limit) input by a browser;

d) Verifying whether the IP and the port data are legal or not;

e) When maintaining the IP range data and the port range data, firstly verifying whether the managed base station collides with the IP range and the port range, if so, the IP and the port data can be maintained after the base station information is adjusted;

f) The IP range data (IP upper limit, IP lower limit) and the port range data (port upper limit, port lower limit) are stored in a relational database (IP port filter table).

2) Base station management

a) Monitoring a request for acquiring a base station information list by an operation support system from Kafka base station configuration response data;

b) Acquiring a base station connection information list through a relational database (base station information table), packaging the information list into JSON data (adding a message unique identifier symbol), sending the JSON data to Kafka base station configuration distribution data, and completing the connection of the base stations by an operation support system;

c) Receiving IP and port information input by a browser, and verifying whether the IP pool and port management requirements are met;

d) Packaging the IP and port parameters into JSON data (adding a message unique identifier symbol), sending the JSON data to Kafka base station configuration distribution data, completing whether the base station can be successfully connected currently by an operation support system, and returning a connection result to the front end of a browser;

e) Acquiring registration information of a base station, carrying out IP pool and port management verification on an IP and a port, and storing the base station information into a relational database (base station information table) after meeting the requirements;

f) Acquiring base station maintenance information, carrying out IP pool and port management verification on the IP and the port, and updating the base station maintenance information to a relational database (base station information table) after meeting the requirements;

g) According to the search condition, searching a relational database (base station information table), acquiring corresponding base station information, and returning to the front end of the browser;

h) When the base station information is newly added, modified and deleted, the latest base station connection information list is packaged into JSON data (adding a message unique identifier symbol), the JSON data is sent to Kafka base station configuration distribution data, and the operation support system is used for maintaining the base station connection again;

i) Receiving a base station restarting or base station resetting command initiated by a browser, packaging relevant information into JSON format data (adding a message unique identifier symbol), sending the JSON format data to Kafka base station configuration distribution data, monitoring and obtaining by an information receiving and transmitting service, and sending the message;

j) Monitoring the response data of Kafka base station configuration, receiving the response result of the base station restarting or resetting command (obtained according to the unique identifier), and returning the response result to the front end of the browser.

3) Chart initialization configuration

a) Acquiring center coordinates (longitude and latitude) and zoom level information through a relational database (chart initialization table) and outputting the center coordinates and the zoom level information to the front end of the browser;

b) Updating the central coordinates (longitude and latitude) input by the browser to a relational database (chart initialization table);

c) The zoom level input by the browser is updated to the relational database (chart initialization table).

4) Fault and alarm management

a) Acquiring fault and alarm information of each base station through a relational database (fault and alarm information table) according to the retrieval conditions;

b) Acquiring fault and alarm manager information of each base station through a relational database (base station alarm manager information table) according to the retrieval conditions;

c) Storing each base station alarm receiving mailbox information input by a browser into a relational database (base station alarm manager information table);

d) And after receiving the fault and alarm information, sending the fault and alarm information to a designated mailbox according to the alarm receiving mail information of the base station.

5) Organization management

a) Storing mechanism information (including upper and lower relationships of mechanisms) input by a browser into a relational database (mechanism information table);

b) Obtaining a mechanism information list through a relational database (mechanism information table) according to the retrieval condition and outputting the mechanism information list to the front end of the browser;

c) The organization maintenance information is acquired and updated to a relational database (organization information table).

6) Base station data dictionary management

a) Storing the base station data dictionary information input by the browser into a relational database (base station data dictionary table);

b) Updating the acquired base station data dictionary maintenance information to a relational database (base station data dictionary table);

c) Acquiring corresponding base station data dictionary information through a relational database (base station data dictionary table) according to the retrieval condition, and returning to the front end of the browser;

d) The base station data dictionary information of excel batch import is stored in a relational database (base station data dictionary table).

7) Device identity information management

a) Storing navigation aid information input by a browser into a relational database (an equipment identity information table);

b) Updating the acquired maintenance information of the navigation aid to a relational database (an equipment identity information table);

c) And acquiring corresponding navigation aid retrieval information through a relational database (equipment identity information table) according to the retrieval conditions, and returning to the front end of the browser.

8) Communication priority management

a) The communication priority information (high, medium and low) is updated to a relational database (service priority information table) through various VDE data services (aviation information, hydrological information and the like) input by a browser;

b) When the message broadcasting is carried out on various data services, the broadcasting is carried out from high to low according to the priority setting.

9) Communication protocol filtering rule configuration

a) Storing the specified base station communication protocol (TCP, UDP, SFTP, SMTP) filtering information input by the browser into a relational database (base station communication protocol information table);

b) The communication protocol filtering information is sent to Kafka base station configuration distribution data by JSON format data (added with a message unique identifier), and information is obtained by monitoring of an information receiving and transmitting service and sent;

c) Monitoring the filtering response result (obtained according to the unique identifier) of the communication protocol received by Kafka base station configuration response data, storing the response result in a relational database (base station communication protocol information table) and returning the response result to the front end of the browser.

10 Message filtering rule configuration

a) One or more filtering rules configured for the appointed base station are input into the browser and stored in a relational database (base station message filtering rule table);

b) Transmitting the message filtering rule to Kafka base station configuration distribution data in JSON format data (adding a message unique identifier), and monitoring and acquiring and transmitting the message by an information receiving and transmitting service;

c) And monitoring a response result (acquired according to the unique identifier) of a received message filtering rule of Kafka base station configuration response data, storing the response result into a relational database (a base station message filtering rule table) and returning the response result to the front end of the browser.

11 Base station drive management)

a) The method comprises the steps that drive uploading/management information is obtained through a foreground page, wherein the drive information mainly comprises a local drive file, a drive name, a device manufacturer, a model number, a version number, a drive description and the like;

b) Uploading the local drive file to an SFTP server service directory;

c) Storing the driving information in a relational database (base station driving information table);

d) The driving information list and the driving details are acquired through a relational database (base station driving information table). The information list can be paged and inquired;

e) The driver upgrade needs to judge whether the upgrade version is the latest version, for example, the driver of the non-latest version (judged according to the name and the version number of the driver) and the upgrade is allowed after confirmation;

f) Transmitting the designated base station and the upgrade drive information to Kafka base station configuration distribution data in JSON format data (adding a message unique identifier symbol), and monitoring, acquiring and transmitting the message by an information receiving and transmitting service;

g) Monitoring Kafka base station configuration response data, receiving a base station drive upgrade response result (acquired according to a unique identifier), storing the response result in a relational database (base station drive information table) and returning to the front end of the browser.

12 Report management

a) According to the retrieval conditions, a list of various statistical report configuration information (report names, report mail receivers, report sending or not and the like) is obtained through a relational database (report configuration information table) and returned to the front end of the browser;

b) Acquiring report information data by calling a related interface in a data analysis service according to a report name and a report query time range input by a browser;

c) Storing various statistical report configuration information input by a browser into a relational database (report configuration information table);

d) And executing a report statistics function at regular time every day, and according to the information of the relational database (report configuration information table), generating a report by calling a related interface in the data analysis service to send the report data to a designated report receiver.

13 Service access management)

a) Whether the service interface input through the browser allows access or not, and the interface accesses the white list setting information to store the white list setting information in a relational database (interface access condition table);

the interface access condition information list is acquired through a relational database (interface access condition table) and returned to the front end of the browser.

Service interface

The interfaces between the base station management background service and the external service are as follows:

1) Interface to MySQL

And the base station manages the interface between the background service and the MySQL, and finishes the inquiry and storage of data through the interface.

2) Interface to Kafka service

And the interface of the base station terminal interface service and the Kafka service is used for completing the monitoring and storage of the received sentences.

3.9 base station configuration background processing service scheme

Service identification

The service identifier is as follows: shorStationConfigureService

Purpose of service

The service provides for the processing of the VDES base station operating attribute configuration from the human-machine interaction platform. The processing result is sent to the information receiving and transmitting service through the data bus and is transmitted to the base station terminal equipment, and the processing result is stored in the database at the same time.

List of service functions

1) Receiving and processing a configuration instruction for the AIS channel working mode from the man-machine interaction platform, and forwarding a processing result to a data management system for database storage and sending to a base station terminal;

2) Receiving and processing a configuration instruction of an ASM channel working mode from a man-machine interaction platform, and forwarding a processing result to a data management system for database storage and sending to a base station terminal;

3) And receiving and processing a configuration instruction for the VDE channel working mode from the man-machine interaction platform, and forwarding the processing result to a data management system for database storage and sending to a base station terminal.

Service composition framework

The service consists of 13 modules, which make up the framework shown in fig. 35.

As shown in fig. 36, the HTTP service sends configuration instructions to the corresponding processing modules, and after the processing by the modules, the configuration instructions are sent to the kafka and database by the VDES channel configuration instruction sending module.

Description of the algorithm

1) Working channel management configuration

a) Acquiring input AIS channel working frequency channel, ASM channel working frequency channel, VDE channel working frequency channel, transmitting power information and VDE bandwidth configuration information from a browser, and storing the configuration information into a relational database (working frequency channel configuration information table);

b) Transmitting the working channel information to Kafka base station configuration distribution data in JSON format data (added with a message unique identifier), and monitoring and acquiring and transmitting the information by an information receiving and transmitting service;

c) Monitoring the response data of Kafka base station configuration, receiving the response result of the working channel (obtained according to the unique identifier), storing the response result in a relational database (working channel configuration information table) and returning to the front end of the browser.

2) Message broadcast rule configuration

a) Acquiring input information of AIS channel selection, initial time slot number, time slot bias and time slot number configured by broadcasting rules from a browser, wherein the information is used for completing time slot reservation configuration;

b) Configuring information through a browser, wherein the configurable information is information No. 4, no. 20, no. 22 and No. 23;

c) Configuring a message sending rule by a browser, wherein the message sending rule comprises starting UTC minutes, referring to time slots, time slot intervals and the like;

d) If the message is configured as the 22 # message, information such as a sending frequency channel, a channel A, a channel B, tx/Rx, power and the like needs to be configured;

e) If the message is configured as the message number 23, the station type, the ship type and the cargo type, the latitude of the northeast corner, the latitude of the southeast corner, the latitude of the southwest corner, the reporting interval, the Tx/Rx mode and the silence time information need to be configured;

f) Storing AIS channel selection, initial time slot number, time slot bias and time slot number information into a relational database (message broadcast rule configuration information table);

g) Storing the message number, the initial UTC minutes, the reference time slots and the time slot interval information into a relational database (message sending rule configuration information table);

h) Configuring the message as 22 # message information such as transmission channel, channel a, channel B, tx/Rx, power, etc. information to a relational database (slipway channel assignment information table);

i) Configuring the message as 23-number message information such as station type, ship type and cargo type, northeast angular longitude, northeast angular latitude, southwest angular longitude, southwest angular latitude, reporting interval, tx/Rx mode, silence time information is stored in a relational database (station report frequency group assignment information table);

j) And transmitting the message broadcasting rule configuration information to Kafka base station configuration distribution data in JSON format data (adding a message unique identifier). Monitoring, acquiring and sending a message by an information receiving and sending service;

k) Monitoring a message broadcasting rule configuration response result (acquired according to a unique identifier) received from Kafka base station configuration response data, storing the response result in a relational database (a message broadcasting rule configuration information table) and returning the response result to the front end of the browser.

3) VDE bulletin board configuration

a) Obtaining input VDE bulletin board configuration information such as bulletin board sending rules, versions, start-to-take time, effective duration, TDMA frame length, longitude and latitude of the northeast corner of a control area, longitude and latitude of the southwest corner of the control area and the like from a browser, and storing the configuration information into a relational database (TBB channel configuration information table);

b) The VDE bulletin board configuration information is transmitted to Kafka base station configuration distribution data in JSON format data (adding a message unique identifier). Monitoring, acquiring and sending a message by an information receiving and sending service;

c) Monitoring the configuration response data of the Kafka base station, receiving the configuration response result (acquired according to the unique identifier) of the VDE bulletin board, storing the response result into a relational database (TBB channel configuration information table) and returning to the front end of the browser.

4) Bulletin signaling channel configuration

a) Acquiring input bulletin signaling channel configuration information such as short message sending time limit, system state, RA algorithm selection interval and maximum short message number information per frame from a browser, and storing the configuration information into a relational database (ASC channel configuration information table);

b) The bulletin signaling channel configuration information is sent to Kafka base station configuration distribution data in JSON format data (adding a message unique identifier). Monitoring, acquiring and sending a message by an information receiving and sending service;

c) Monitoring the Kafka base station configuration response data, receiving the bulletin signaling channel configuration response result (acquired according to the unique identifier), storing the response result in a relational database (ASC channel configuration information table) and returning to the front end of the browser.

5) Ship-to-ship VDE communication configuration

a) The browser acquires input ship-to-ship VDE communication configuration information such as the TDMA channel 1, the TDMA channel 2, the TDMA channel 3, the TDMA channel 4 and the TDMA channel 1 information, and stores the configuration information into a relational database (VDE communication configuration information table);

b) And transmitting the ship-to-ship VDE communication configuration information to Kafka base station configuration distribution data in JSON format data (adding a message unique identifier). Monitoring, acquiring and sending a message by an information receiving and sending service;

c) Monitoring the response result (obtained according to the unique identifier) of the ship-to-ship VDE communication configuration of the Kafka base station configuration response data, storing the response result into a relational database (VDE communication configuration information table) and returning the response result to the front end of the browser.

Service interface

The base station configures a background processing service and an external service interface as follows:

1) Interface to MySQL

And the base station configures an interface between the background processing service and MySQL, and the storage and the inquiry of the base station configuration information are completed through the interface.

2) Interface to Kafka service

And the base station configures an interface between the background processing service and the Kafka service, and monitors and stores sentences through the interface.

Base station monitoring background service scheme

Service identification

The service identifier is as follows: shorStationMonitoringService

Purpose of service

The service receives a system state query request from the man-machine interaction platform, acquires a state result from the data management system according to the request, and sends the result to the man-machine interaction platform. Meanwhile, push data from the data management system is received, and push information is sent to the man-machine interaction platform.

3.10.3 service function list

1) Receiving a monitoring state query request from a man-machine interaction platform;

2) Sending a query request to a data management system;

3) The query result is sent to a man-machine interaction platform;

4) Receiving monitoring information pushing from a data management system in real time;

5) And the pushed monitoring information is sent to the man-machine interaction platform.

Service composition framework

The service consists of 4 modules, of which:

1) And the base station basic monitoring module. And receiving a basic monitoring state query request of the base station from the man-machine interaction platform, wherein the basic monitoring state query request comprises a base station signal-to-noise ratio, working states of AIS/ASM/VDE functional modules, receiving and transmitting amounts of AIS/ASM messages, VDE ship connection numbers, VDE message data amounts and the like, and forwarding the request to data service of a data management system. After receiving the query result, feeding back to the man-machine interaction platform;

2) And a channel monitoring module. And receiving a time slot use request of a channel from the man-machine interaction platform, wherein the time slot use request comprises a time slot condition used by a base station in one frame, a time slot condition used by a shipway and the like, and forwarding the request to a data service of a data management system. Receiving a query result and feeding back to the man-machine interaction platform;

3) The VDE is connected to the monitoring module. And receiving a VDE channel access state query request from the man-machine interaction platform, wherein the VDE channel access state query request comprises the ship condition of accessing a specified base station, the identity information of the ship, the generated data flow and the like, and forwarding the request to a data service of a data management system. Receiving a query result and feeding back to the man-machine interaction platform;

4) And the interface service monitoring module. And receiving an external user access information query request from the man-machine interaction platform, wherein the request comprises whether an external service interface is available, external call data statistics and the like. And feeding back the query result to the man-machine interaction platform after receiving the query result.

The module component frame is shown in fig. 37.

As shown in FIGS. 38-40, a service transaction model

1) Query monitoring result model

Including base station basic monitoring, channel monitoring, VDE access monitoring. The HTTP service sends the request instruction to the corresponding processing module, the request instruction is processed by the module and then sent to the data service through the monitoring data distribution module, and the data service inquires the monitoring result and feeds the result back to the monitoring data distribution module and feeds back to the HTTP service.

2) Real-time push monitoring result model

Including base station basic monitoring, channel monitoring, VDE access monitoring. The data service pushes the monitoring data to the monitoring data distribution module in real time, and the monitoring data is processed by the functional processing module and then sent to the HTTP service.

3) Database query monitoring result model

Interface service monitoring is included. The HTTP service sends the request instruction to the corresponding processing module, the corresponding data is read from the database through the monitoring data distribution module after the request instruction is processed by the module, and the monitoring result is inquired and then fed back to the HTTP service.

Description of the algorithm

1) Base station basic monitoring background processing

a) Acquiring real-time monitoring data comprising latest signal-to-noise ratio, AIS working state, ASM working state and VDE working state information of each base station through a relational database (base station running state table);

b) Acquiring AIS message transmission quantity, ASM message transmission quantity and VDE message transmission quantity information in a designated time period (defaulting to the last hour) through a relational database (a message transmission information table);

c) Acquiring AIS message receiving quantity in a designated time period (the last hour of defaults) through an AIS historical data query interface;

d) Acquiring ASM message receiving quantity in a specified time period (the latest hour by default) through an ASM historical data query interface;

e) Obtaining the VDE message receiving quantity in a specified time period (the last hour of defaults) through a VDE historical data query interface;

f) Acquiring the current ship connection number through a current ship information inquiry interface;

g) Outputting the real-time monitoring state information to the front end of the browser;

h) When the real-time monitoring data is displayed, the system executes the steps a) to f) every minute to acquire the real-time monitoring data information and pushes the real-time monitoring data information to the front end of the browser;

i) Inquiring historical running states to obtain inquiry parameters such as base station MMSI, starting time, ending time and the like input by a browser;

j) Acquiring latest signal-to-noise ratio, AIS working state, ASM working state and VDE working state information of a base station in a query range through a relational database (base station running state table);

k) Acquiring AIS message transmission quantity, ASM message transmission quantity and VDE message transmission quantity information in a query range through a relational database (a message transmission information table);

l) acquiring AIS message receiving quantity in a query range through an AIS historical data query interface;

m) acquiring ASM message receiving quantity in a query range through an ASM historical data query interface;

n) obtaining the VDE message receiving quantity in the query range through a VDE historical data query interface;

o) acquiring the ship connection number in the query range through a historical ship data query interface;

p) outputting the history monitoring state information to the front end of the browser.

2) Channel monitoring background processing

a) Inquiring a relational database (base station information table) to obtain a base station information list connected with a current management system and output the base station information list to the front end of a browser;

b) Acquiring an MMSI parameter of a query base station (a default page is input into a first base station MMSI) input by a browser;

c) Acquiring the occupation details of AIS A channels, AIS B channels, ASM A channels, ASM B channels, VDE A channels and VDE B channels of the query base station through a relational database (a time slot occupation list);

d) Acquiring the correct received packet number and the Bit Error number of the inquiring base station through a relational database (a received data packet statistical information table);

e) Outputting the query result to the front end of the browser;

f) And c) executing the steps c) to d) every minute according to the MMSI parameter of the query base station to acquire channel monitoring data information and pushing the channel monitoring data information to the front end of the browser when the channel monitoring display is carried out.

3) VDE access monitoring function

a) Acquiring parameters such as a base station MMSI, a starting time, an ending time and the like input by a browser;

b) Acquiring ship data in a query range through a historical ship data query interface;

c) Acquiring the number of occupied time slots per minute in a query range through a relational database (a time slot occupation list);

d) And outputting the acquired ship data and the occupied time slot number per minute to the front end of the browser.

4) Service monitoring background processing

a) Receiving search conditions (such as a start date and an end date) of a foreground browser;

b) And acquiring the current service running state and service access amount information through a relational database (an interface call information table and an interface access condition table), and returning to the front end of the browser.

Service interface

The interface service of the base station terminal and the external service interface are as follows:

1) Interface to MySQL

And the base station monitoring background service is connected with the MySQL interface, and the storage and the inquiry of the base station monitoring information are completed through the interface.

2) Interface to Kafka service

The base station monitors the interface between the background interface service and the Kafka service, and queries sentences through the interface.

Operation log service scheme

Service identification

The service identifier is as follows: system Journ service

Purpose of service

The service provides log record, archive and storage operation for system operation, service message and other information.

List of service functions

1) Recording, archiving and storing information of various operations of the system;

2) Recording, archiving and storing information processed by the business process.

Service composition framework

The service consists of 3 modules, of which:

1) And a system operation log module. And receiving system operation log archiving configuration from the man-machine interaction platform, forwarding configuration information to a log archiving module, monitoring the system operation condition in real time, and sending a monitoring result to the archiving module for archiving according to the configuration. Forwarding a log query request from a man-machine interaction platform, and feeding back log data acquired through an archiving module to the man-machine interaction platform;

2) And a service message log module. Receiving service message log archiving configuration from a man-machine interaction platform, forwarding configuration information to a log archiving module, simultaneously monitoring the condition of the system operation service message in real time, and sending a monitoring result to the archiving module for archiving according to the configuration. Forwarding a log query request from a man-machine interaction platform, and feeding back log data acquired through an archiving module to the man-machine interaction platform;

3) And a log archiving module. Processing according to the received log archiving configuration information, and completing log archiving according to the configuration information, wherein the received system operation record and the system service message operation record. And extracting corresponding log information for feedback according to the received log query request.

The above module composition frame is shown in fig. 41.

As shown in FIG. 42, a service transaction model

1) Generating a log model

The log module monitors the system running operation and the business message operation in real time. Generating a log for the generated operation information according to the configuration requirement.

2) Log query model

The HTTP service sends a log query request and query conditions, and the running log service feeds back the HTTP service after acquiring a query result from the database.

Description of the algorithm

1) System operation log collection

a) Listening to system operation steps (e.g., creating user operations);

b) Information such as the monitored operation, the operation user, the operation time and the like is stored in a relational database (operation log table).

2) System operation log background retrieval

a) Acquiring conditions retrieved by a browser, such as a time range, an operator and the like;

b) Acquiring a corresponding information list from a relational database (operation log table) according to the retrieval condition;

c) And outputting the retrieved operation log information list to a browser foreground.

3) Service message log collection

a) Monitoring a message receiving and transmitting service;

b) And storing the monitored service message logs, such as a data management system of message sending/receiving, time sending/receiving, a bank station MMSI, a message type, message content and the like, into an Hbase database.

4) Background search for business message log

a) Acquiring conditions retrieved by a browser, such as a time range, a shore-based MMSI, a message behavior (receiving/transmitting), a message type and the like;

b) Acquiring a corresponding service message log information list through a service analysis service according to the retrieval condition;

c) And outputting the searched business message log information list to a browser foreground.

5) Log archive period configuration

a) Acquiring operation log and message log module filing period information through a browser;

b) The archive period information is updated to a relational database (archive period table).

6) Log archiving process

a) The log archiving processing function is executed regularly every day;

b) Respectively acquiring operation logs and message log archiving period configuration in a relational database (log archiving periodic table);

c) When the operation log content meets the operation log filing period configuration condition, filing the operation log, and storing the filing file to a designated storage position;

d) And when the content of the business message log meets the message log archiving period configuration condition, archiving the business message log, and storing the archived file in a designated storage position.

Service interface

The operation log service interfaces with external services as follows:

1) Interface to MySQL

And the interface of the operation log service and the data storage service is used for completing the storage and inquiry of log information.

2) Interface to a data management system

And the operation log service is connected with the interface of the data management system, and the storage and the inquiry of the service message are completed through the interface.

3.12 chart Engine background service scheme

3.12.1 service identification

The service identifier is as follows: chartEngineService

3.12.2 service purposes

The service provides real-time and query processing of the access base station and the access ship information, and is used for the chart engine to call and display.

List of service functions

1) Real-time inquiring of access base station information;

2) Accessing real-time query of ship information;

3) Accessing the information of the navigation aid in real time.

Service composition framework

The service consists of 3 modules, of which:

1) And the base station data acquisition module. The information of the current system access base station is queried from the data service in real time, wherein the information comprises MMSI, connection state, position, alarm and the like, and the query result is fed back to the chart engine for display. Receiving a designated query request from a chart engine, and feeding back a query result to the chart engine for display;

2) And the slipway data acquisition module. The information of the current system access base station, including static information, dynamic information and the like, is queried from the data service in real time, and the query result is fed back to the chart engine for display. Receiving a designated query request from a chart engine, and feeding back a query result to the chart engine for display;

3) And other access equipment data acquisition modules. And inquiring information of other types of equipment accessed by the current system in real time from the data service, including MMSI, connection state, position, alarm and the like, and feeding back the inquiry result to the chart engine for display. And receiving a designated query request from the chart engine, and feeding back the query result to the chart engine for display.

The above modules constitute a frame as shown in fig. 43.

As shown in fig. 44 and 45, the service transaction model

1) Monitoring type data acquisition model

The background service of the chart engine inquires information of the accessed base station, the shipway and other access equipment from the data service in real time, and the inquired result is fed back to the chart engine for display.

2) Query type data acquisition model

The chart engine sends a query situation aiming at a specific object, the chart engine background service queries corresponding object information to the data service, and the query result is fed back to the chart engine for display.

3.12.7 Algorithm description

1) Slipway data acquisition

a) Acquiring a ship dynamic and static information list through a current ship information query interface in application analysis service and outputting the list to the front end of a browser;

b) Acquiring an information list of navigation aid equipment through an information inquiry interface of the navigation aid equipment in the application analysis service and outputting the information list to the front end of the browser;

c) And calling a ship history track query interface in the AIS data service to acquire ship history track data information through ship history track query parameters (such as ship MMSI, starting time and ending time) input by the browser, and outputting the ship history track data information to the front end of the browser.

2) Base station data acquisition

a) Acquiring a base station information list through a base station information inquiry interface in application analysis service;

b) And outputting the acquired base station information list to the front end of the browser.

Service interface

The chart engine background service interfaces with external services as follows:

1) Interface to a data management system

And the marine chart engine background service is connected with the interface of the data management system, and the inquiry of the ship dynamic and static information, navigation aid equipment information and base station equipment information is completed through the interface.

User and authority management service scheme

Service identification

The service identifier is as follows: userRighttsManagementService

Purpose of service

The service provides registration and maintenance of system users, allocation of user rights, assignment of different roles with different system function access or operation rights, and allocation of corresponding user group rights to users or roles.

List of service functions

1) Registering and maintaining user information;

2) User permission distribution;

3) Creating and maintaining roles;

4) Allocating corresponding menu rights for the roles;

5) Creating and maintaining a menu;

6) Creating and maintaining a user group;

7) And maintaining the relationship between the user and the role and the user group.

Service composition framework

The service consists of 4 modules, of which:

1) And a user management module. For configuring information such as a user, password, etc. that allows access to the system. The method comprises the functions of newly creating a user, editing user information, disabling the user, setting user roles, setting user groups, modifying passwords and the like;

2) And a role management module. The page right possessed by the character is specified. The method comprises the steps of creating roles, editing a role list, deleting the roles, setting a user group, distributing corresponding function menus according to the roles and the like;

3) And a menu module. For configuring menu functions provided by the system. The method comprises the functions of creating a menu, editing menu information, deleting the menu, maintaining the upper and lower relationships of the menu and the like;

4) And a user group management module. Different roles may form a user group, and a user may have one role or belong to one user group. The method comprises the functions of creating a user group, editing user group information, deleting the user group, checking the corresponding roles of the user group, user information and the like.

The module component frame is shown in fig. 46.

As shown in FIGS. 47-48, a service transaction model

1) User and rights data storage model

The HTTP service sends the user and the authority management data to the corresponding processing module, and the user and the authority management data are sent to the database after being processed by the processing module.

2) User and rights data acquisition model

The HTTP service sends a user and authority management data query request, the user and the authority management service query corresponding data information through a database, and query results are fed back to the HTTP service.

Description of the algorithm

1) User management background processing

a) User information received from the browser, including user name, password, mailbox, telephone, affiliated institution, affiliated role, affiliated user group, etc.;

b) Wherein the password field is required to be encrypted;

c) Storing the processed user basic information into a relational database (user table);

d) Storing the user and the role information to a relational database (user role relation table);

e) Storing the user and the user group information to a relational database (user group relational table);

f) Acquiring a user information list through a relational database (a user table, a user role relational table and a user group relational table) according to the retrieval condition, and outputting the user information list to the front end of the browser;

g) Updating the user maintenance information received from the browser to a relational database (user table, user role relationship table, user group relationship table);

h) User disable/user restore request data received from the browser, updating user disable field attributes to a relational database (user table);

i) The password update request received from the browser encrypts the password field and updates it to the relational database (user table).

2) Role management background processing

a) Character information received from the browser comprises character names, user groups, menu items and the like;

b) Storing the character basic information into a relational database (character table);

c) Storing the roles and the menu item information to a relational database (a role menu relational table);

d) Acquiring a role information list through a relational database (a role table, a role menu relational table and a role user group relational table) according to the search condition, and outputting the list to the front end of the browser;

e) The character maintenance information received from the browser is updated to the relational database (character table, character menu relationship table, character user group relationship table).

3) Menu management background processing

a) Receiving menu information sent by a browser, wherein the menu information comprises menu names, father menus, menu addresses and the like;

b) Storing the menu information in a relational database (menu table);

c) Acquiring a menu information list through a relational database (menu list) according to the search condition, and outputting the menu information list to the front end of the browser;

d) The menu maintenance information received from the browser is updated to the relational database (menu table).

4) User group management background processing

a) Receiving user group information sent by a browser, wherein the user group information comprises information such as user group names, user group descriptions and the like;

b) Storing the user group information to a relational database (user group table);

c) Storing the user group and the affiliated role information into a relational database (a role user group relational table);

d) Storing the user group and the contained user information in a relational database (user group relational table);

e) Acquiring a user group information list and user information contained in the user group through a relational database (a user group table, a user group relational table and a role user group relational table) according to the retrieval condition, and outputting the user group information list and the user information contained in the user group to the front end of the browser;

The user group maintenance information received from the browser is updated to the relational database (user group table).

Service identification

The service identifier is as follows: dataAccessBufferService

Purpose of service

The service provides for receiving data packets from the messaging service and forwarding the data to each input buffer queue according to the type.

List of service functions

1) Monitoring a Kafka cache queue in real time to acquire a base station real-time data message;

2) Monitoring a Kafka cache queue in real time to acquire a base station recovery data message;

3) And classifying the received data message, and caching the classified data message into a corresponding buffer queue.

Service composition framework

The service consists of 2 modules, of which:

1) And a data access module. Real-time monitoring of Kafka cache is realized, and data packets sent by each base station terminal (containing base station recovery data) are obtained;

2) And a data buffer module. And classifying the data access information according to the data types, and buffering the data access information to corresponding buffer queues.

The module component frame is shown in fig. 49.

3.15 distributed data processing service scheme

3.15.1 service identification

The service identifier is as follows: dataProcessService

3.15.2 service purposes

The service provides real-time processing of various data such as various AIS, ASM, VDE business data, base station running state data, base station monitoring data and the like received, so as to generate and store indexes for business analysis and statistical data.

List of service functions

1) Monitoring a Kafka cache, and acquiring corresponding service data in real time;

2) Acquiring AIS service data through data processing, and forwarding the AIS service data to a distributed data storage service for storage;

3) Acquiring ship dynamic information (class A ship and class B ship) through AIS service data processing, storing the information in a Redis cache, and forwarding the information to a distributed data storage service for storage;

4) Acquiring static information (class A ship and class B ship) of the ship through AIS service data processing, and storing the static information into a Redis cache;

5) Acquiring base station information by processing AIS service data and storing the base station information into a Redis cache;

6) Acquiring navigation aid equipment information by processing AIS service data and storing the navigation aid equipment information into a Redis cache;

7) Acquiring base station alarm information through processing AIS service data, and storing the base station alarm information into a database;

8) Acquiring time slot occupation information through AIS service data processing, and storing the time slot occupation information into a database;

9) ASM service data is obtained through data processing and is forwarded to a distributed data storage service for storage;

10 Obtaining VDE service data through data processing and forwarding the VDE service data to a distributed data storage service for storage;

11 Acquiring the running state information of the base station through data processing and storing the running state information into a database;

12 The base station statistical analysis data information is obtained through data processing and stored in a database.

3.15.4 service composition framework

The service consists of 9 modules, of which:

1) Kafka caches the read module. Realizing real-time monitoring of Kafka cache and acquiring AIS, ASM, VDE and other service data;

2) And the AIS data processing module. The AIS information processing module is used for processing AIS information sent by VDES equipment of different types and different manufacturers in real time, and processing slipway dynamic information, ship static information, base station information, navigation aid equipment information, base station alarm information, AIS channel time slot occupation information and the like in the AIS information;

3) ASM data processing module. The method is used for processing ASM messages sent by VDES equipment of different types and different manufacturers in real time, and processing ASM service data and ASM channel time slot occupation information;

4) And a VDE data processing module. The method is used for processing VDE messages sent by VDES equipment of different types and different manufacturers in real time, and processing VDE service data and VDE channel time slot occupation information;

5) The base station monitors and manages the data processing module. The base station monitoring management data (except AIS/ASM/VDE) information which is used for processing the base station monitoring management data (except AIS/ASM/VDE) information and the base station statistical analysis data information and the like which are sent by different types of VDES equipment of different manufacturers in real time;

6) And the AIS data batch processing module. The module functions are the same as the AIS data processing module;

7) ASM data batch processing module. The module functions are the same as the ASM data processing module;

8) And a VDE data batch processing module. The module functions are the same as the VDE data processing module;

9) And the base station monitors and manages the data batch processing module. The module functions as a base station monitoring management data processing module.

The module component frame is shown in fig. 50.

As in fig. 51 and 52, the service transaction model

1) Cache read model

And monitoring Kafka cache data in real time, acquiring corresponding cache information, and transmitting the corresponding cache information to the designated data processing module.

2) Data processing model

And receiving the cache information acquired by the cache reading module, and performing data classification processing.

3.16 distributed data storage service scheme

3.16.1 service identification

The service identifier is as follows: datastorage service

3.16.2 service purposes

The service provides the functions of distributed data storage and distributed file storage, and provides a highly reliable, high-performance, column-oriented and scalable distributed storage environment for the accessed original message data, various data indexes after distributed data processing and batch processing operation results.

List of service functions

1) Monitoring a Kafka cache, and acquiring original message data in real time and storing the original message data into an HDFS;

2) Monitoring a Kafka cache, acquiring effective message data after message cleaning in real time, and storing the effective message data into an HBASE and an HDFS respectively;

3) Receiving ship dynamic information from a distributed data processing service and storing the information in an HBASE database;

4) Receiving AIS business data information from a distributed data processing service and storing the AIS business data information into an HBASE database;

5) Receiving ASM business data information from a distributed data processing service and storing the ASM business data information into an HBASE database;

6) And receiving VDE business data information from the distributed data processing service and storing the VDE business data information in an HBASE database.

Service composition framework

The service consists of 2 modules, of which:

1) And a distributed file storage module. The method is used for storing the full-volume VDES original message, and aims to effectively manage the full-volume data in the service range of AIS, ASM, VDE and the like, and provide basis for centralized analysis, efficient access and unified decision of the data;

2) And a distributed data storage module. The method is used for storing mass data such as ship dynamic information and AIS/ASM/VDE historical data and providing a reading and writing function for the mass data.

The above module composition frame is shown in fig. 53.

Data service scheme

Service identification

The service identifier is as follows: dataService

Purpose of service

The service provides external requests initiated by different services, and according to the request information, corresponding resources are called to complete corresponding statistical analysis and calculation, and result data is returned.

List of service functions

1) Receiving a historical route query request from a marine chart engine background service, acquiring and processing a query result through an HBASE database, packaging into JSON data and feeding back the JSON data;

2) Receiving a query request of AIS historical data from a VDES message background processing service, acquiring a query result through an HBASE database, processing the query result, packaging the query result into JSON data and feeding back the JSON data;

3) Receiving a historical ship data query request from a base station monitoring background processing service, acquiring and processing a query result through an HBASE database, packaging into JSON data and feeding back the JSON data;

4) Receiving a query request of ASM historical data from a VDES message background processing service, acquiring a query result through an HBASE database, processing the query result, packaging the query result into JSON data and feeding back the JSON data;

5) Receiving a VDE historical data query request from a VDES message background processing service, acquiring a query result through an HBASE database, processing the query result, packaging the query result into JSON data and feeding back the JSON data;

6) Receiving a query request of processing service report data from a base station management background, acquiring a query result through an HBASE database, analyzing, counting and feeding back;

7) Receiving a current ship information query request from a marine chart engine background service, acquiring a query result through Redis, processing the query result, packaging the query result into JSON data and feeding back the JSON data;

8) Receiving a current base station information query request from a chart engine background service, acquiring a query result through Redis, processing the query result, packaging the query result into JSON data and feeding back the JSON data;

9) Receiving an information query request of current navigation aid equipment from a marine chart engine background service, acquiring a query result through Redis, processing the query result, packaging the query result into JSON data and feeding back the JSON data.

Service composition framework

The service consists of 5 modules, of which:

1) And the AIS data service module. The function of providing service by utilizing AIS message data mainly comprises ship historical track inquiry service, AIS historical data inquiry service, historical ship data inquiry service and the like;

2) ASM data service module. A function of providing service by using ASM message data, such as ASM historical data inquiry service;

3) And a VDE data service module. The function of providing services by using VDE message data, such as VDE historical data query service;

4) And the data analysis service module. The AIS/ASM/VDE message data is utilized to carry out a statistical analysis function, so that the data quantity receiving statistics of each base station, the data generation quantity statistics of each ship berth, the data quantity statistics of each channel and the broadcasting quantity statistics of each safety message are completed;

5) And an application analysis service module. And providing supporting data for the sea chart engine service by utilizing the ship dynamic information, the base station information and the navigation aid information. The information of the ship point position, the base station point position and the navigation aid point position is included.

The above module composition frame is shown in fig. 54.

As shown in FIGS. 55 and 56, a service transaction model

1) Latest ship information acquisition model

The marine chart engine background service obtains the latest data of ships, base stations, navigation aid equipment and the like.

2) Historical data acquisition model

And acquiring ship historical data, ship historical airlines and AIS/ASM/VDE historical data information.

Environment monitoring service scheme

Service identification

The service identifier is as follows: environmental monitor service

Purpose of service

The service provides environment monitoring for each node of the whole shore-based test system, such as CPU occupancy rate, memory occupancy rate, hard disk service condition, running state of specific service and the like of each server.

List of service functions

1) Monitoring indexes such as the total number of processes of an operating system, the CPU utilization rate, the memory utilization rate, the total hard disk, the hard disk utilization rate, the network IO state and the like is realized;

2) And the monitoring of the state of the service middleware such as Tomcat, hadoop, kafka, mysql, redis is realized.

Service composition framework

The service consists of 2 modules, of which:

1) And an operating system monitoring module. Monitoring operation system monitoring indexes of each server through zabbix service, and embedding the monitoring indexes into a foreground page of a shore-based management system;

2) And the middleware state monitoring module. And monitoring the running state of each middleware through zabbix service, and embedding the middleware into a foreground page of the shore-based management system.

The above module composition frame is shown in fig. 57 below.

Database storage architecture scheme

SUMMARY

According to the functions of the shore-based management system, the requirements of the project on the speed, efficiency, capacity and the like of the database are met through the logical structure, the physical structure and the construction of the database.

The database not only meets the requirements of real-time analysis of online data on throughput, response time and high concurrency, but also meets the requirements of offline large-data batch processing calculation on capacity scalability and elastic expansion capacity, and simultaneously can conveniently provide result data for display to the outside, so that the durability and consistency of the data are ensured.

According to the system business meter, the data are respectively stored according to different states, and the final data storage is divided into a Kafka cache, an HDFS distributed file storage, an Hbase distributed big data storage, a Redis state data storage and a MySQL relational data storage.

Database environment

According to the overall system architecture and the performance requirements, the database system uses a deployment architecture of a distributed cluster, and exerts the advantages of deployment on demand, expansion on demand, high availability, storage integration and the like. The four different types of storage environments also differ.

1) The Kafka cache cluster uses a distributed, partition-supporting and multi-copy memory database, and is characterized by high throughput and low delay, and is used for storing real-time data and calculation process data;

2) HDFS distributed file storage clusters, using a distributed file system (Hadoop Distributed File System), HDFS for short. HDFS is characterized by high fault tolerance and is designed to be deployed on inexpensive hardware; and it provides high throughput access to application data for storing system raw message data;

3) Hbase distributed data storage cluster is a distributed, column-oriented storage system built on top of HDFS. The system is used for storing AIS, ASM, VDE historical information and ship dynamic information, and realizing real-time read-write and random access of ultra-large-scale data;

4) The Redis state data cluster can also be stored in a lasting manner based on a memory, and the Key-Value database is suitable for storing the real-time state data of the ship, so that the state is convenient to update and inquire;

5) MySQL relational database cluster, completely support SQL, support complicated inquiry, support ACID transaction, support strong isolation level, stability, durability is good, is used for storing calculation result data.

Database construction

According to the design of the database architecture and the analysis of the data flow, the following construction scheme is adopted in actual deployment:

1) In order to meet the requirements of multithreading and high concurrency, the cache cluster is built by using an IO intensive server, a large memory and an SSD hard disk, at least two servers are used for installing a message middleware Kafka, and a master server and a slave server are arranged;

2) In order to meet the storage and query of mass data, the big data storage cluster uses an IO intensive server, a big memory and an HDD hard disk, at least 3 servers are provided with Hadoop, one server is used as NameNode, and the other server is used as DataNode to construct a Hadoop cluster;

3) Redis cluster, at least three examples, set up the master-slave node, require the intensive examples of large memory, large hard disk, IO, dispose;

in order to improve fault tolerance and high performance, the relational database cluster uses IO intensive servers, a large memory and an HDD hard disk, at least 4 servers are provided with MySQL clusters, master and slave nodes are arranged, and a MySQL storage cluster is built.

Maintainability of

The design of the system adopts a modular design concept, and a shore-based management system is formed by a series of loosely coupled assembly sets. Aiming at the characteristics of the VDES shore-based management system, the main business functions are split into individual components, and the development, testing and other stages of each individual component are independent of other services. In addition, when a new demand arises, problems of each party such as compatibility, influence degree and the like need to be considered, and the modular development can directly and rapidly modify the demand change.

Each component is fine-grained, splitting a large system into many components, making them completely independent of each other, and capable of communicating with each other, improving maintainability of the system.

Reliability of

The reliability of the system needs to take the reliability as a core quality standard, and proper software development and testing technology is selected, so that the reliability of the VDES shore-based management system is improved by fault tolerance, restorability design and other methods.

Establishing reliability-based quality standards

The reliability-based quality standard is established in the planning and demand analysis stage of the VDES shore-based management system. This quality criterion includes functionality, reliability, maintainability, portability, safety, etc., with a certain index specifying the baseline of the criterion. Quality management is carried out in each development stage, and quality assurance is carried out in a mode of demand analysis result measurement, design result measurement, test result measurement and acceptance result measurement.

Selection of appropriate software development and testing techniques

The data amount input by each base station in the project is particularly large, and a proper software development technology is required to be selected to improve the reliability aiming at the characteristics. In the planning and design stage of the VDES shore-based management system, the framework of big data and assembly is decided to be used as a technical framework. In addition, in order to further improve the reliability of the software, the software needs to be subjected to multi-dimensional and deep test, errors in the software are found to the maximum extent, the reliability of the software is improved, and the complete test is performed through the high coverage rate of the software functions.

Fault tolerance and restorability design

Fault tolerance design is an important factor in improving software reliability. Appropriate interface requirements specifications are used during the design phase of the system to verify the possibility and completeness of the interface implementation and to track the cause of the submersion defect during the software development process, starting from the design and coding architecture. When the system fails, the fault processing technology of error recovery is adopted to ensure the recovery and normal operation of the system.

Safety of

In order to prevent the information of the system from being modified and destroyed, the security of the system needs to be designed. The project is mainly controlled by the encryption technology and the user authority, and original data and log information are reserved.

Encryption technology

In order to ensure the safety of the system, an information encryption technology is adopted to disguise important information, so that an illegal information stealer cannot understand the true meaning of the information, a verification code or a feature vector of the information is extracted by an encryption algorithm and is packaged with related information, the integrity of the information can be verified by a legal owner of the information by utilizing the feature code, and the identity of an information user is authenticated, identified and confirmed by the encryption algorithm so as to control the use of the information.

User rights management

The users of the VDES shore-based management system are controlled by rights management of different rights. The general user cannot operate the functions of the system administrator, and the system administrator can solve the work which the general user cannot complete to the maximum extent.

The access rights of data are effectively managed in two layers of system application and database access, different personnel set different rights, effective identity information is verified through a rights management module, and corresponding functions can be used by verified users.

Preserving raw data and log information

The variety of input information of the VDES shore-based management system is quite various and the quantity is quite large, so that the original data is kept so that the data can be conveniently re-analyzed and utilized at a later stage.

Based on the analysis, kafka distributed storage is adopted, so that the retention of all data input by the system without processing is ensured. In addition, in order to ensure effective tracking and solving of the problems when the system abnormality occurs, the main behaviors of the system are output in a log form, so that the problems are solved as soon as possible, and the safety is ensured.

Portability (Portability)

The software development language of the VDES shore-based management system mainly adopts the main Java development technology which is mainstream at present, the portability of Java comes from the neutrality of the architecture, and in addition, the Java strictly prescribes the length of each basic data type. The Java system has strong portability, a Java compiler is realized by Java, and a Java running environment is realized by ANSI C.

Based on the characteristics of Java development language, the VDES shore-based management system can be conveniently transplanted into one operating system after being developed on the other operating system. When the system is deployed under the Linux operating system in the early stage, the demand changes in the future, and the system can be conveniently deployed into the Windows operating system, so that the portability of the system is greatly facilitated.

Ease of use

The usability of the system mainly comprises three aspects of conciseness, consistency and user experience.

Conciseness of

The simplicity is mainly achieved by adopting a gradual exposure method, and the elements of the interface are displayed to the user until the elements are used, so that important functions are highlighted. The common function menu is used as far as possible, so that the uniformity and the integrity of the system are ensured.

Consistency of

The appearance, behavior, and operation of the VDES shore-based management system are consistent throughout, with the same behavior producing the same effect. The position of the standard element, the function of the interface element should not change.

User experience

Creating appropriate grouping, paging, etc. functions. And carrying out presentation and management of data by using a proper information presentation mode such as a chart, a table and the like. The operation of the user is prompted by clear, accurate, short and easy-to-understand language characters. The response time of the system should not exceed 3 seconds when the user operates the key service.

Furthermore, the terms "first," "second," and the like, are used for descriptive purposes only and are not to be construed as indicating or implying a relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include at least one such feature. In the description of the present invention, the meaning of "plurality" means at least two, for example, two, three, etc., unless specifically defined otherwise.

In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms are not necessarily directed to the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. Furthermore, the different embodiments or examples described in this specification and the features of the different embodiments or examples may be combined and combined by those skilled in the art without contradiction.

While embodiments of the present invention have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the invention, and that variations, modifications, alternatives and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the invention.

Claims

1. The VDES shore-based integrated management system is characterized by comprising a base station operation support system, a data management system and a shore-based interface service system;

2. A VDES shore-based integrated management system according to claim 1, characterized in that: the functions of the base station operation support system comprise providing base station terminal interface service, AIS message support service, ASM message support service, VDE message support service, base station monitoring management support service and message receiving and transmitting service.

3. A VDES shore-based integrated management system according to claim 2, characterized in that: the content of the base station terminal interface service comprises connection service, statement sending, statement receiving, statement cleaning and base station data recovery;

4. A VDES shore-based integrated management system according to claim 1, characterized in that: the functions of the data management system include data access/buffer management services, distributed data processing services, distributed data storage services, data services, and environmental monitoring services.

5. The VDES shore-based integrated management system of claim 4, wherein: the data access/buffer management service data access content AIS data buffer, ASM data buffer, VDE data buffer, other data buffer, batch AIS data buffer, batch ASM data buffer, batch VDE data buffer, batch other data buffer;

6. A VDES shore-based integrated management system according to claim 1, characterized in that: the functions of the shore-based interface service system comprise VDES service platform interface service, man-machine interaction service, VDES message background processing service, base station configuration background processing service, base station monitoring background service, user and authority management service, sea chart engine background service and operation log service.

7. The VDES shore-based integrated management system of claim 6, wherein: the content of the VDES service platform interface service comprises external interface service, service registration, service release and base station management background processing service;