A remote upgrade system and method based on ship-shore integration

Abstract

This invention relates to a remote upgrade system and method based on ship-shore integration. The system includes modules: a shore-side management platform, a ship-side management platform, a shore-side application repository, a ship-side application repository, a client application service, an MQTT service, and an RSYNC service. The shore-side management platform pushes new version application or data package information to the ship-side management platform, and prompts the ship-side application repository to periodically pull new version application or data packages from the shore-side application repository. The client application service installs the new version application and deploys the new version data package, and provides real-time status feedback to both the shore-side and ship-side management platforms, thereby achieving remote upgrades of applications and data packages on both the shore and ship sides. This solves the problem of remote application upgrades on both the shore and ship sides, is highly practical, and allows shore-side administrators to monitor the installation and deployment status of ship-side applications and data packages in real time.

Description

Technical Field

[0001] This invention relates to an information system technology, and more particularly to a ship-shore integrated remote upgrade system and method. Background Technology

[0002] As large vessels accumulate data, iterate training, and undergo changes in ship condition during long-distance voyages, the corresponding applications or their associated model data packages need to be updated. Previously, this involved technicians boarding the vessel after arrival for maintenance and updates, but this method is inefficient, costly, and slow. With the increasing number of vessels and the growing complexity of the shipping environment, remote offshore upgrades are the future trend.

[0003] Invention patent 202111494458.3 discloses a remote upgrade system and method for shipborne equipment. The system includes: a cloud service platform, set up at a ground master station, configured with a mobile communication network and a satellite network, used to receive upgrade requests and send the corresponding upgrade software package to the shipborne switching equipment according to the upgrade request and the corresponding communication network; and a shipborne switching equipment, set up at the ship, configured with a mobile communication network and a satellite network, which receives the corresponding network parameters and upgrade software package, generates corresponding upgrade instructions according to the upgrade parameters, and transmits the upgrade instructions and upgrade software package to the corresponding target equipment to achieve remote upgrade.

[0004] Invention patent 202310003918.0 discloses a method for synchronizing ship-shore information in a web-based ship management platform. The method includes: initiating synchronization based on a scheduled synchronization time and a synchronization data range; the ship-side server initiating a synchronization request; the ship-side server acquiring and installing an upgrade information package; determining whether the ship-side server identifier matches the ship-side server's MAC address; if they do not match, synchronization is stopped and manually resumed; otherwise, the ship-side server acquires a shore-based database file package; determining whether the data packets in the ship-side server match the shore-based database file package; if they do not match, updating the data packets in the ship-side server according to the shore-based database file package; acquiring data packets within the synchronization data range from the ship-side server and treating them as data packets to be updated; transmitting these data packets to the shore-based server; and the shore-based server updating according to the data packets to be updated. This method improves data consistency and reliability between the shore-based server and multiple ship-side servers.

[0005] Invention patent 202111494458.3 mainly focuses on remote upgrades of shipborne equipment. The upgrade targets are the firmware of the shipborne equipment, and the upgrade content is written to the FLASH area. It cannot upgrade applications, data packets, or model files running on the ship's operating system.

[0006] Invention patent 202310003918.0 updates data packets in the ship-side server based on shore-based database file packages. It only supports updating data packet files and cannot upgrade or update applications and model files running on the ship-side operating system.

[0007] Currently, remote upgrades of shipboard equipment software packages are relatively mature, and there are many methods for updating data package files between ship and shore. However, for remote upgrades that simultaneously meet the requirements of ship-shore applications and data packages based on the operating system, the variety of application types and complex operating parameters make remote upgrades of these applications more difficult, and traditional remote upgrade methods are not applicable. Summary of the Invention

[0008] To address the issue of remote application upgrades on both shore and ship, a ship-shore integrated remote upgrade system and method are proposed, primarily solving the following technical problems:

[0009] 1. Solve the problem of remote upgrades for shore-based and ship-based applications based on the operating system, and on this basis, enable remote upgrades of data packets.

[0010] 2. Resolve upgrade issues for various application types on both shore and ship sides, including C / S architecture, B / S architecture, and Docker image applications. Implement version information management and upgrade status monitoring for these applications.

[0011] 3. Implement version information management for shore-based and ship-based applications and data packets, implement rollback functionality for upgrade failures, and enable real-time monitoring of ship-based application deployment status information from the shore.

[0012] The technical solution of this invention is as follows:

[0013] A ship-shore integrated remote upgrade system includes the following modules:

[0014] The shore-based management platform, deployed on a shore-based server, provides shore-based administrators with a visual and user-friendly web interface and backend. All operations can be performed from the shore-based management platform. Operations include: viewing version information and deployment status of all applications and data packages on the shore and ship; adding new applications or data packages to the shore-based application repository; deleting applications or data packages from the shore-based application repository; remotely upgrading, uninstalling, and rolling back applications or data packages on the shore-based client; and pushing new applications or databases to the ship-based management platform.

[0015] The shipboard management platform, deployed on the shipboard server, provides shipboard administrators with a visual and user-friendly web interface and backend. All operations can be performed from the shipboard management platform. Operations include: viewing the version information of all shipboard applications and data packages and their deployment status on the shipboard, deleting shipboard applications or data packages, and remotely upgrading, uninstalling, and rolling back applications or data packages on the shipboard client.

[0016] The shore application repository, deployed on the shore server, is used to manage all applications and data packages based on the ship-shore integrated remote upgrade system, including the addition and deletion of new applications or data packages, and to manage the version information and deployment status information of applications or data packages added to the shore application repository. The deployment status information includes pending shore installation, pending ship-side push, and pending ship-side deployment.

[0017] The ship-side application repository, deployed on the ship-side server, is used to manage ship-side applications or data packages, including the deletion of ship-side applications or data packages, and to manage the version information and deployment status information of applications or data packages in the ship-side application repository. The deployment status information includes pending upgrades and updates, and the latest version.

[0018] Client application service, deployed on shore-side and ship-side clients, is used to manage the installation, uninstallation, and rollback of applications or data packages on shore-side and ship-side clients, and to send deployment status information to their respective shore-side or ship-side management platforms.

[0019] The MQTT service, deployed on a cloud server, is used for message passing between the shore-based management platform and the ship-based management platform.

[0020] RSYNC service, deployed on a cloud server, is used for file transfer between shore-based application repositories and ship-based application repositories.

[0021] The application includes at least the software package to be upgraded, as well as an installation script and an uninstallation script. The installation script performs the installation and configuration operations for the software package to be upgraded, and the uninstallation script performs the uninstallation operation for the software package. The data package includes the data package file to be upgraded and configuration parameters.

[0022] Furthermore, the types of applications include C / S architecture, B / S architecture, and Docker images.

[0023] Furthermore, when adding new applications or data packages to the shore application repository, the user needs to select the deployment location, whether it is shore-based or ship-based deployment; applications or data packages used on the shore should select shore-based deployment, and applications or data packages used on the ship should select ship-based deployment.

[0024] Furthermore, the shore-based management platform monitors the version information of applications and data packets in real time. When the shore-based management platform detects a new version of the current application or data packet, it prompts the user to install the application or data packet deployed on the shore; and prompts the user to push the application or data packet deployed on the ship.

[0025] Furthermore, after receiving an application or data packet installation request from the shore management platform, the client application service deployed on the shore client executes the application's installation script or deploys the data packet according to the configuration parameters, and sends the result information to the shore management platform. After receiving the information, the shore management platform provides real-time feedback on the installation or deployment results to the shore user.

[0026] Furthermore, after receiving the application or data package push information from the shore management platform, the ship-side application repository periodically pulls the application or data package from the shore application repository; the ship-side management platform supports users to set idle time settings and set the time period for the ship-side application repository to pull the application.

[0027] Furthermore, the shipboard management platform monitors the version information of applications and data packages in the shipboard application repository in real time. When the shipboard management platform detects a new version of an application or data package, it prompts the user to upgrade or update the application or data package. When the shipboard management platform does not detect a new version of an application or data package, the interface displays that the current version is the latest version.

[0028] Furthermore, after receiving a request from the shipside management platform for the installation of an application or data package, the client application service deployed on the shipside client executes the application's installation script or deploys the data package according to the configuration parameters, and sends the result information to the shipside management platform. After receiving the information, the shipside management platform provides real-time feedback on the installation or deployment results to the shore-side management platform and the shipside user.

[0029] A remote upgrade method based on ship-shore integration, implemented using the ship-shore integrated remote upgrade system as described above, includes the following steps:

[0030] Step S1: When the application repository on the shore receives a new application or data package, the user selects a deployment location. For applications, the user uploads the upgrade package and installation / uninstallation script; for data packages, the user uploads the upgrade data package and configuration parameters.

[0031] Step S2: After the shore-based management platform detects a new version of the application or data package, it determines the deployment location. For applications or data packages deployed on the shore, the shore-based management platform prompts the user to install them on the shore; for applications or data packages deployed on the ship, the shore-based management platform prompts the user to push them to the ship.

[0032] Step S3: After receiving the application or data package installation request from the shore management platform, the client application service deployed on the shore client executes the application installation script or deploys the data package and sends the result information to the shore management platform. After receiving the information, the shore management platform provides real-time feedback on the installation or deployment result to the shore user. If the installation or deployment fails, the application or data package is rolled back to the previous version and the version information is sent to the shore management platform.

[0033] Step S4: After receiving the new version push information of the application or data package from the shore management platform, the ship-side management platform will periodically pull the application or data package from the shore application repository according to the idle time settings.

[0034] Step S5: The shipboard management platform monitors the version information of applications and data packages in the shipboard application repository in real time. When the shipboard management platform detects a new version of an application or data package, it prompts the user to upgrade or update the application or data package on the shipboard. When the shipboard management platform does not detect a new version of an application or data package, the interface displays that the current version is the latest version.

[0035] Step S6: After receiving the application or data package installation request from the ship management platform, the client application service deployed on the ship client executes the application installation script or deploys the data package. If the installation or deployment fails, the application or data package is rolled back to the previous version, and the client application service sends the result information to the ship management platform.

[0036] In step S7, after receiving the information, the ship-side management platform will provide real-time feedback on the installation or deployment results to the shore-side management platform and the ship-side user.

[0037] The beneficial effects of this invention are as follows:

[0038] This invention discloses a ship-shore integrated remote upgrade system and method. The system pushes new version application or data package information from the shore-based management platform to the ship-based management platform, prompting the ship-based application repository to periodically pull the new version application or data package from the shore-based application repository. The new version application is installed and the new version data package is deployed through client application services, and real-time status information is fed back to both the shore-based and ship-based management platforms, thereby achieving remote upgrades of applications and data packages both on the shore and on the ship.

[0039] This invention simultaneously solves the problem of remote upgrades of applications and data packages based on operating systems, demonstrating strong practicality. Because the operating parameters of applications based on operating systems are complex, this invention uses installation scripts for remote upgrades, solving installation problems for various types of applications and possessing high reference value. Furthermore, this invention employs a collaborative approach of message passing and file transfer to complete the remote upgrade process, allowing the shore and ship to share application and data package version information and deployment and installation information. This enables shore-based administrators to monitor the installation and deployment status of ship-side applications and data packages in real time, further enhancing its practical value. Attached Figure Description

[0040] Figure 1 This is a diagram of the ship-shore integrated remote upgrade system of the present invention;

[0041] Figure 2 This is a flowchart illustrating the steps of the remote upgrade method based on ship-shore integration of the present invention. Detailed Implementation

[0042] The present invention will now be described in detail with reference to the accompanying drawings and specific embodiments. These embodiments are based on the technical solution of the present invention and provide detailed implementation methods and specific operating procedures. However, the scope of protection of the present invention is not limited to the following embodiments.

[0043] A remote upgrade system based on ship-shore integration, such as Figure 1 As shown, it includes the following modules:

[0044] The shore-based management platform, deployed on a shore-based server, provides shore-based administrators with a visual and user-friendly web interface and backend. All operations can be performed from the shore-based management platform. Operations include: viewing version information and deployment status of all applications and data packages on the shore and ship; adding new applications or data packages to the shore-based application repository; deleting applications or data packages from the shore-based application repository; remotely upgrading, uninstalling, and rolling back applications or data packages on the shore-based client; and pushing new applications or databases to the ship-based management platform.

[0045] The shipboard management platform, deployed on the shipboard server, provides shipboard administrators with a visual and user-friendly web interface and backend. All operations can be performed from the shipboard management platform. Operations include: viewing the version information of all shipboard applications and data packages and their deployment status on the shipboard, deleting shipboard applications or data packages, and remotely upgrading, uninstalling, and rolling back applications or data packages on the shipboard client.

[0046] The shore-based application repository, deployed on a shore-based server, manages all applications and data packages based on the ship-shore integrated remote upgrade system. This includes adding new applications or data packages, deleting applications or data packages, and managing the version information and deployment status information of applications or data packages added to the shore-based application repository. The deployment status information includes pending shore-based installation, pending ship-based push, and pending ship-based deployment.

[0047] The ship-side application repository, deployed on the ship-side server, is used to manage ship-side applications or data packages, including the deletion of ship-side applications or data packages, and to manage the version information and deployment status information of applications or data packages in the ship-side application repository. The deployment status information includes pending upgrades and updates, and the latest version.

[0048] The client application service is deployed on both shore-based and ship-based clients. It manages the installation, uninstallation, and rollback of applications or data packages on both shore-based and ship-based clients, and sends deployment status information to their respective shore-based or ship-based management platforms.

[0049] The MQTT service, deployed on a cloud server, is used for message passing between the shore-based management platform and the ship-based management platform.

[0050] RSYNC service, deployed on a cloud server, is used for file transfer between shore-based application repositories and ship-based application repositories.

[0051] The application types include C / S architecture, B / S architecture, and Docker images; the application includes at least the software package to be upgraded, as well as installation and uninstallation scripts. The installation script performs the installation and configuration operations for the software package to be upgraded, and the uninstallation script performs the uninstallation operation for the software package; the data package includes the data package file to be upgraded and configuration parameters.

[0052] When adding a new application or data package to the shore application repository, the user needs to select the deployment location: shore deployment or ship deployment. Applications or data packages intended for shore deployment should be selected as shore deployment, while those intended for ship deployment should be selected as ship deployment.

[0053] The shore-based management platform monitors the version information of applications and data packets in real time. When the shore-based management platform detects a new version of the current application or data packet, it prompts the user to install the application or data packet deployed on the shore; for applications or data packets deployed on the ship, it prompts the user to push the application or data packet to the ship.

[0054] After receiving push notifications for applications or data packages from the shore-based management platform, the shipboard application repository periodically retrieves the application or data package from the shore-based application repository and prompts the user to install it on the ship. The shipboard management platform allows users to configure off-peak hours and set time periods for the application repository to retrieve data.

[0055] The shipboard management platform monitors the version information of applications and data packages in the shipboard application repository in real time. When the shipboard management platform detects a new version of an application or data package, it prompts the user to upgrade or update the application or data package. When the shipboard management platform does not detect a new version of an application or data package, the interface displays that the current version is the latest version.

[0056] After receiving an application or data package installation request from the shore management platform, the client application service deployed on the shore client executes the application's installation script or deploys the data package according to the configuration parameters, and sends the result information to the shore management platform. After receiving the information, the shore management platform provides real-time feedback on the installation or deployment results to the shore user.

[0057] After receiving a request from the shipside management platform for the installation of an application or data package, the client application service deployed on the shipside client executes the application's installation script or deploys the data package according to the configuration parameters, and sends the result information to the shipside management platform. Upon receiving the information, the shipside management platform provides real-time feedback on the installation or deployment results to the shore-side management platform and the shipside user.

[0058] The shore-based management platform and the ship-based management platform communicate via the MQTT protocol, while the shore-based application repository and the ship-based application repository transfer files via the RSYNC protocol.

[0059] A remote upgrade method based on ship-shore integration, such as Figure 2 As shown, it includes the following steps:

[0060] In step S1, when the application repository on the shore receives a new application or data package, the user selects a deployment location. For applications, the user uploads the upgrade package and installation / uninstallation script; for data packages, the user uploads the upgrade data package and configuration parameters.

[0061] In step S2, after the shore-based management platform detects a new version of the application or data package, it determines the deployment location. For applications or data packages deployed on the shore, the shore-based management platform prompts the user to install them on the shore; for applications or data packages deployed on the ship, the shore-based management platform prompts the user to push them to the ship.

[0062] Step S3: After receiving the application or data package installation request from the shore management platform, the client application service deployed on the shore client executes the application installation script or deploys the data package and sends the result information to the shore management platform. After receiving the information, the shore management platform provides real-time feedback on the installation or deployment result to the shore user. If the installation or deployment fails, the application or data package is rolled back to the previous version and the version information is sent to the shore management platform.

[0063] In step S4, after the ship-side management platform receives the new version push information of the application or data package from the shore-side management platform, the ship-side application repository will periodically pull the application or data package from the shore-side application repository according to the idle time settings.

[0064] Step S5: The shipboard management platform monitors the version information of applications and data packages in the shipboard application repository in real time. When the shipboard management platform detects a new version of an application or data package, it prompts the user to upgrade or update the application or data package on the shipboard. When the shipboard management platform does not detect a new version of an application or data package, the interface displays that the current version is the latest version.

[0065] Step S6: After receiving the application or data package installation request from the ship management platform, the client application service deployed on the ship client executes the application's installation script or deploys the data package. If the installation or deployment fails, the application or data package is rolled back to the previous version, and the client application service sends the result information to the ship management platform.

[0066] In step S7, after receiving the information, the ship-side management platform will provide real-time feedback on the installation or deployment results to the shore-side management platform and the ship-side user.

[0067] The above-described embodiments are merely one implementation of the present invention, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of the invention. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of the present invention, and these all fall within the protection scope of the present invention. Therefore, the protection scope of this invention should be determined by the appended claims.

Claims

1. A ship-shore fusion-based remote upgrading system, characterized by, The application comprises the following modules: a shore-end management platform deployed on a shore-end server, which is used to provide a shore-end manager with a visual and convenient web interface and a back end, and all operations can be performed on the shore-end management platform; the operations include: viewing version information of all application programs and data packages and deployment states on the shore-end and the ship-end, adding new application programs or data packages to a shore-end application warehouse, deleting application programs or data packages in the shore-end application warehouse, remotely upgrading, uninstalling and rolling back application programs or data packages on a shore-end client, and pushing new application programs or data packages to a ship-end management platform; a ship-end management platform deployed on a ship-end server, which is used to provide a ship-end manager with a visual and convenient web interface and a back end, and all operations can be performed on the ship-end management platform; the operations include: viewing version information of all application programs and data packages on the ship-end and deployment states on the ship-end, deleting application programs or data packages, and remotely upgrading, uninstalling and rolling back application programs or data packages on a ship-end client; a shore-end application warehouse deployed on a shore-end server, which is used to manage all application programs and data packages based on a ship-shore fusion remote upgrading system, including adding new application programs or data packages, deleting application programs or data packages, and managing version information and deployment state information of application programs or data packages added to the shore-end application warehouse, the deployment state information including shore-end installation, ship-end pushing and ship-end deployment; a ship-end application warehouse deployed on a ship-end server, which is used to manage application programs or data packages on the ship-end, including deleting application programs or data packages on the ship-end, and managing version information and deployment state information of application programs or data packages in the ship-end application warehouse, the deployment state information including upgrading and updating and the latest version; a client application service deployed on a shore-end client and a ship-end client, which is used to manage installation, uninstallation and rollback operations of application programs or data packages on the shore-end client and the ship-end client, and send deployment state information to respective shore-end management platforms or ship-end management platforms; an MQTT service deployed on a cloud server, which is used for message transmission between the shore-end management platform and the ship-end management platform; an RSYNC service deployed on a cloud server, which is used for file transmission between the shore-end application warehouse and the ship-end application warehouse; the application programs include software packages to be upgraded, installation scripts and uninstallation scripts, the installation scripts perform installation and configuration operations of the software packages to be upgraded, and the uninstallation scripts perform uninstallation operations of the software packages; and the data packages include data package files to be upgraded and configuration parameters.

2. The ship-shore fusion based remote upgrading system as claimed in claim 1, wherein: the types of the application programs include C / S architecture, B / S architecture and docker images.

3. The ship-shore fusion based remote upgrading system as claimed in claim 1, wherein: when the shore-end application warehouse adds new application programs or data packages, a user needs to select a deployment location, shore-end deployment or ship-end deployment; application programs or data packages for the shore-end are selected for shore-end deployment, and application programs or data packages for the ship-end are selected for ship-end deployment.

4. The ship-shore fusion based remote upgrading system as claimed in claim 1, wherein: The shore management platform detects the version information of the application program and the data packet in real time, and when the shore management platform detects a new version of the current application program and the data packet, the shore management platform prompts the user to perform shore installation for the application program or the data packet deployed on the shore, and prompts the user to perform ship end pushing for the application program or the data packet deployed on the ship end.

5. The ship-shore converged remote upgrading system according to claim 4, wherein: After the client application service deployed on the shore end client receives the shore installation request of the application program or the data packet sent by the shore management platform, the installation script of the application program is executed, or the data packet is deployed according to the configuration parameter, and the result information is sent to the shore management platform, and the shore management platform feeds back the installation or deployment result to the shore user in real time after receiving the information.

6. The ship-shore converged remote upgrading system according to claim 4, wherein: After the ship end management platform receives the pushing information of the application program or the data packet of the shore management platform, the ship end application warehouse pulls the application program or the data packet from the shore application warehouse at a regular time; the ship end management platform supports the user to set the idle time, and sets the time period of the ship end application warehouse pulling at a regular time.

7. The ship-shore converged remote upgrading system according to claim 6, wherein: The ship end management platform detects the version information of the application program and the data packet in the ship end application warehouse in real time, and when the ship end management platform detects a new version of the application program or the data packet, the user is prompted to perform the upgrade of the application program or the data packet, and when the ship end management platform does not detect a new version of the application program and the data packet, the interface displays that the current version is the latest version.

8. The ship-shore converged remote upgrading system according to claim 7, wherein: After the client application service deployed on the ship end client receives the ship end installation request of the application program or the data packet sent by the ship end management platform, the installation script of the application program is executed, or the data packet is deployed according to the configuration parameter, and the result information is sent to the ship end management platform, and the ship end management platform feeds back the installation or deployment result to the shore management platform and the ship end user in real time after receiving the information.

9. A ship-shore fusion-based remote upgrading method, characterized in that: The ship end management platform detects the version information of the application program and the data packet in real time, and when the ship end management platform detects a new version of the current application program and the data packet, the shore management platform prompts the user to perform shore installation for the application program or the data packet deployed on the shore, and prompts the user to perform ship end pushing for the application program or the data packet deployed on the ship end. After the client application service deployed on the shore end client receives the shore installation request of the application program or the data packet sent by the shore management platform, the installation script of the application program is executed, or the data packet is deployed according to the configuration parameter, and the result information is sent to the shore management platform, and the shore management platform feeds back the installation or deployment result to the shore user in real time after receiving the information. After the ship end management platform receives the pushing information of the application program or the data packet of the shore management platform, the ship end application warehouse pulls the application program or the data packet from the shore application warehouse at a regular time; the ship end management platform supports the user to set the idle time, and sets the time period of the ship end application warehouse pulling at a regular time. The ship end management platform detects the version information of the application program and the data packet in the ship end application warehouse in real time, and when the ship end management platform detects a new version of the application program or the data packet, the user is prompted to perform the upgrade of the application program or the data packet, and when the ship end management platform does not detect a new version of the application program and the data packet, the interface displays that the current version is the latest version. After the client application service deployed on the ship end client receives the ship end installation request of the application program or the data packet sent by the ship end management platform, the installation script of the application program is executed, or the data packet is deployed according to the configuration parameter, and the result information is sent to the ship end management platform, and the ship end management platform feeds back the installation or deployment result to the shore management platform and the ship end user in real time after receiving the information. The ship end management platform detects the version information of the application program and the data packet in real time, and when the ship end management platform detects a new version of the current application program and the data packet, the shore management platform prompts the user to perform shore installation for the application program or the data packet deployed on the shore, and prompts the user to perform ship end pushing for the application program or the data packet deployed on the ship end. After the client application service deployed on the shore end client receives the shore installation request of the application program or the data packet sent by the shore management platform, the installation script of the application program is executed, or the data packet is deployed according to the configuration parameter, and the result information is sent to the shore management platform, and the shore management platform feeds back the installation or deployment result to the shore user in real time after receiving the information. Step S4, after the ship end management platform receives the application program or data package new version push information of the shore end management platform, the ship end application warehouse pulls the application program or data package from the shore end application warehouse according to the idle time setting; Step S5, the ship end management platform detects the version information of the application program and data package in the ship end application warehouse in real time, when the ship end management platform detects the new version of the application program or data package, prompts the user to perform the ship end upgrade update of the application program or data package, when the ship end management platform does not detect the new version of the application program and data package, the interface displays the current version as the latest version; Step S6, after the client application service deployed on the ship end client receives the ship end installation request of the application program or data package sent by the ship end management platform, executes the installation script of the application program or deploys the data package, if the installation or deployment fails, the application program or data package is rolled back to the previous version, and the client application service sends the result information to the ship end management platform; Step S7, the ship end management platform receives the information and feeds back the installation or deployment result to the shore end management platform and the ship end user in real time.

Images