Remote upgrading system and method based on ship-shore fusion

Abstract

The invention relates to a remote upgrading system and method based on ship-shore fusion, and the system comprises modules: a shore-end management platform, a ship-end management platform, a shore-end application warehouse, a ship-end application warehouse, a client application service, an MQTT service, and an RSYNC service. And prompting the ship-end application warehouse to pull the new-version application program or data packet from the shore-end application warehouse at regular time. The application program of the new version is installed through the client application service, the data packet of the new version is deployed, and state information is fed back to the shore-end management platform and the ship-end management platform in real time, so that shore-end remote upgrading and ship-end remote upgrading of the application program and the data packet are realized. The problem of remote upgrading of shore-end and ship-end application programs is solved, the practicability is high, and shore-end managers can master the installation and deployment conditions of the ship-end application programs and data packets in real time.

Description

Technical Field

[0001] The present invention relates to an information system technology, and in particular to a remote upgrading system and method based on ship-shore integration. Background Art

[0002] As large ships accumulate data, iterate training, and change ship conditions during long-distance voyages, the corresponding applications or model data packages attached to them need to be updated. In the past, technicians would go on board to perform maintenance and updates after arriving at the shore, but this maintenance and update method has problems such as low efficiency, high cost, and slow response. With the increase in the number of ships and the complexity of the shipping environment, remote offshore upgrades are the future trend.

[0003] Invention patent 202111494458.3 discloses a system and method for remote upgrading of shipborne equipment, the system comprising: a cloud service platform, arranged at a ground master station, configured with a mobile communication network and a satellite network, for receiving upgrade requests, and selecting a corresponding communication network for sending a corresponding upgrade software package to a shipborne switching device according to the upgrade request; a shipborne switching device, arranged at the ship end, configured with a mobile communication network and a satellite network, receiving level parameters and upgrade software packages through corresponding networks, generating corresponding upgrade instructions according to the upgrade parameters, and transmitting the upgrade instructions and upgrade software packages to the corresponding target device to realize remote upgrading.

[0004] Invention patent 202310003918.0 discloses a ship-shore information synchronization method in a Web-based ship management platform, including: starting synchronization according to the scheduled synchronization time and the synchronization data range, the ship-side server initiating a synchronization request, the ship-side server obtaining an upgrade information package and installing it, judging whether the ship-side server identifier is consistent with the MAC address of the ship-side server, if not, stopping synchronization and synchronizing manually, on the contrary, the ship-side server obtains a shore-based database file package, judging whether the data packet in the ship-side server is consistent with the shore-based database file package, if not, updating the data packet in the ship-side server according to the shore-based database file package; obtaining the data packet in the ship-side server within the synchronization data range and treating it as a data packet to be updated, transmitting the data packet to be updated to the shore-based server, and the shore-based server updating according to the data packet to be updated. The data consistency and data reliability between the shore-based server and multiple ship-side servers are improved.

[0005] Invention patent 202111494458.3 is mainly for remote upgrade of shipborne equipment. The object of the upgrade is the firmware of the shipborne equipment. The upgrade content is written into the FLASH area and cannot upgrade the application programs, data packets, and model files running on the ship-side operating system.

[0006] Invention patent 202310003918.0 updates the data package in the ship-side server according to the shore-based database file package. It only supports the update of the data package file and cannot upgrade the application and model files running on the ship-side operating system.

[0007] At present, the remote upgrade of shipborne equipment software packages is relatively mature, and there are many methods for updating data package files between ships and shores. However, for the remote upgrade method that meets the needs of both ship-shore and shore-based applications and data packages based on the operating system, the traditional remote upgrade method is not applicable because of the large number of application types and complex operating parameters, which makes it difficult to remotely upgrade these applications. Summary of the invention

[0008] Aiming at the problem of remote upgrade of shore-side and ship-side applications, a remote upgrade system and method based on ship-shore integration is proposed, which mainly solves the following technical problems:

[0009] 1. Solve the problem that shore-side and ship-side applications based on the operating system cannot be remotely upgraded, and on this basis, realize the remote upgrade of data packets.

[0010] 2. Solve the upgrade problems of various types of applications on the shore and on the ship, including applications of C / S architecture, B / S architecture, and docker images. Implement version information management and upgrade status monitoring of the above-mentioned various applications.

[0011] 3. Realize the version information management of shore-side and ship-side applications and data packets, implement the rollback function of upgrade failure, and realize the real-time monitoring of ship-side application deployment status information by the shore side.

[0012] The technical solution of the present invention is:

[0013] A remote upgrade system based on ship-shore integration, including the following modules:

[0014] The shore management platform is deployed on the shore server. It is used to provide a visual and convenient web interface and backend for shore management personnel. All operations can be performed from the shore management platform. The operations include: viewing the version information of all applications and data packages and their deployment status on the shore and ship, adding new applications or data packages to the shore application warehouse, deleting applications or data packages in the shore application warehouse, remotely upgrading, uninstalling, and rolling back applications or data packages on the shore client, and pushing new applications or databases to the ship management platform.

[0015] The ship-side management platform is deployed on the ship-side server. It is used to provide a visual and convenient web interface and backend for the ship-side management personnel. All operations can be performed from the ship-side management platform. The operations include: viewing the version information of all ship-side applications and data packages and their deployment status on the ship-side, deleting ship-side applications or data packages, and remotely upgrading, uninstalling, and rolling back applications or data packages on the ship-side client.

[0016] The shore application warehouse is deployed on the shore server and 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 the management of the version information and deployment status information of the applications or data packages added to the shore application warehouse. The deployment status information includes waiting for shore installation, waiting for ship push and waiting for ship deployment;

[0017] The ship-side application warehouse is deployed on the ship-side server and is used to manage the ship-side applications or data packages, including the deletion of the ship-side applications or data packages, and the management of the version information and deployment status information of the applications or data packages in the ship-side application warehouse. The deployment status information includes the version to be upgraded and the latest version;

[0018] Client application service, deployed on the shore client and the ship client, is used to manage the installation, uninstallation, and rollback of application programs or data packages on the shore client and the ship client, and send the deployment status information to the corresponding shore management platform or ship management platform;

[0019] MQTT service, deployed on the cloud server, is used for message transmission between the shore-side management platform and the ship-side management platform;

[0020] RSYNC service, deployed on the cloud server, is used for file transfer between the shore-side application warehouse and the ship-side application warehouse;

[0021] The application program at least includes a software package to be upgraded, an installation script and an uninstallation script. The installation script executes the installation configuration operation of the software package to be upgraded, and the uninstallation script executes the uninstallation operation of the software package. The data package includes a data package file to be upgraded and configuration parameters.

[0022] Furthermore, the types of the application include C / S architecture, B / S architecture and docker image.

[0023] Furthermore, when the shore-side application warehouse adds a new application or data package, the user is required to select the deployment location, shore-side deployment or ship-side deployment; for applications or data packages used for the shore side, choose shore-side deployment, and for applications or data packages used for the ship side, choose ship-side deployment.

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

[0025] Furthermore, after the client application service deployed on the shore client receives the shore installation request for the application or data packet issued by the shore management platform, it executes the installation script of the application, 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 will provide real-time feedback of the installation or deployment results to the shore user.

[0026] Furthermore, after the ship-side management platform receives the push information of the application or data packet from the shore-side management platform, the ship-side application warehouse periodically pulls the application or data packet from the shore-side application warehouse; the ship-side management platform supports users to set up idle time and set the scheduled pulling period of the ship-side application warehouse.

[0027] Furthermore, the ship-side management platform detects the version information of the application and data package in the ship-side application warehouse in real time. When the ship-side management platform detects a new version of the application or data package, it prompts the user to upgrade the application or data package. When the ship-side management platform does not detect a new version of the application and data package, the interface displays that the current version is the latest version.

[0028] Furthermore, after the client application service deployed on the ship-side client receives the ship-side installation request for the application or data packet sent by the ship-side management platform, it executes the installation script of the application, or deploys the data packet according to the configuration parameters, and sends the result information to the ship-side management platform. After receiving the information, the ship-side management platform will provide real-time feedback of the installation or deployment results to the shore-side management platform and the ship-side user.

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

[0030] Step S1: When the shore-side application warehouse receives a new application or data package, the user selects a deployment location, and for an application, uploads an upgrade package and installation / uninstallation scripts; for a data package, uploads an upgrade package and configuration parameters;

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

[0032] Step S3, after receiving the shore installation request of the application or data package sent by 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 feeds back the installation or deployment result to the shore user in real time. If the installation or deployment fails, the application or data package rolls back to the previous version, and sends the version information to the shore management platform;

[0033] 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 warehouse periodically pulls the application or data package from the shore-side application warehouse according to the idle time setting;

[0034] Step S5, the ship-side management platform detects the version information of the application and data package in the ship-side application warehouse in real time. When the ship-side management platform detects a new version of the application or data package, it prompts the user to perform ship-side upgrade of the application or data package. When the ship-side management platform does not detect a new version of the application and data package, the interface displays that the current version is the latest version;

[0035] Step S6, after receiving the ship-side installation request of the application or data package sent by the ship-side management platform, the client application service deployed on the ship-side client executes the installation script of the application or deploys the data package. If the installation or deployment fails, the application or data package rolls back to the previous version, and the client application service sends the result information to the ship-side management platform;

[0036] Step S7: After receiving the information, the ship-side management platform will feed back the installation or deployment results to the shore-side management platform and the ship-side user in real time.

[0037] The beneficial effects of the present invention are:

[0038] The present invention provides a ship-shore integrated remote upgrade system and method, which pushes new version application or data packet information to the ship-side management platform through the shore-side management platform, prompting the ship-side application warehouse to regularly pull the new version of the application or data packet from the shore-side application warehouse. The new version of the application is installed through the client application service, the new version of the data packet is deployed, and the status information is fed back to the shore-side management platform and the ship-side management platform in real time, thereby realizing the shore-side remote upgrade and ship-side remote upgrade of the application and data packet.

[0039] The invention solves the problem of ship-shore integrated remote upgrade of applications and data packets based on the operating system at the same time, and is highly practical. Since the operating parameters of applications based on the operating system are relatively complex, the invention uses installation scripts for remote upgrades, which solves the problem of installing various types of applications and has a high reference value. The invention uses message passing and file transfer to work together to complete the remote upgrade process, and the shore and ship sides share the version information and deployment and installation information of applications and data packets, so that shore-side managers can grasp the installation and deployment status of ship-side applications and data packets in real time, and has a high practical value. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0041] Figure 2 The present invention is a flowchart of the steps of the remote upgrade method based on ship-shore integration. DETAILED DESCRIPTION

[0042] The present invention is described in detail below in conjunction with the accompanying drawings and specific embodiments. This embodiment is implemented based on the technical solution of the present invention, and provides a detailed implementation method and specific operation process, but the protection scope 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 management platform is deployed on the shore server. It is used to provide a visual and convenient web interface and backend for shore management personnel. All operations can be performed from the shore management platform. The operations include: viewing the version information of all applications and data packages and their deployment status on the shore and ship, adding new applications or data packages to the shore application warehouse, deleting applications or data packages in the shore application warehouse, remotely upgrading, uninstalling, and rolling back applications or data packages on the shore client, and pushing new applications or databases to the ship management platform.

[0045] The ship-side management platform is deployed on the ship-side server. It is used to provide a visual and convenient web interface and backend for the ship-side management personnel. All operations can be performed from the ship-side management platform. The operations include: viewing the version information of all ship-side applications and data packages and their deployment status on the ship-side, deleting ship-side applications or data packages, and remotely upgrading, uninstalling, and rolling back applications or data packages on the ship-side client.

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

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

[0048] Client application services are deployed on shore-side clients and ship-side clients. They are used to manage the installation, uninstallation, rollback and other operations of applications or data packages on shore-side clients and ship-side clients, and send deployment status information to their corresponding shore-side management platform or ship-side management platform.

[0049] MQTT service, deployed on the cloud server, is used for message transmission between the shore-side management platform and the ship-side management platform.

[0050] RSYNC service, deployed on the cloud server, is used for file transfer between the shore-side application warehouse and the ship-side application warehouse.

[0051] The types of applications include C / S architecture, B / S architecture and docker image; the application includes at least a software package to be upgraded and an installation script and an uninstallation script, the installation script executes the installation configuration operation of the software package to be upgraded, and the uninstallation script executes the uninstallation operation of 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 warehouse, the user needs to select the deployment location, shore deployment or ship deployment. For applications or data packages used on the shore, select shore deployment; for applications or data packages used on the ship, select ship deployment.

[0053] The shore management platform detects the version information of applications and data packages in real time. When the shore management platform detects the new version of the current application and data package, for applications or data packages deployed on the shore, the shore management platform prompts the user to install them on the shore; for applications or data packages deployed on the ship, the shore management platform prompts the user to push them on the ship.

[0054] After the ship-side management platform receives the push information of the application or data package from the shore-side management platform, the ship-side application warehouse periodically pulls the application or data package from the shore-side application warehouse and prompts the user to install it on the ship. The ship-side management platform supports users to set idle time settings and set the ship-side application warehouse to pull the application or data package periodically.

[0055] The ship-side management platform detects the version information of the application and data package in the ship-side application warehouse in real time. When the ship-side management platform detects a new version of the application or data package, it prompts the user to upgrade the application or data package. When the ship-side management platform does not detect a new version of the application and data package, the interface displays that the current version is the latest version.

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

[0057] After the client application service deployed on the ship-side client receives the ship-side installation request for the application or data packet sent by the ship-side management platform, it executes the installation script of the application, or deploys the data packet according to the configuration parameters, and sends the result information to the ship-side management platform. After receiving the information, the ship-side management platform will provide real-time feedback of the installation or deployment results to the shore-side management platform and ship-side users.

[0058] The shore-side management platform and the ship-side management platform transmit messages through the MQTT protocol, and the shore-side application warehouse and the ship-side application warehouse transfer files through the RSYNC protocol.

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

[0060] Step S1: When the shore-side application warehouse receives a new application or data package, the user selects the deployment location. For the application, the upgrade software package and installation / uninstallation script are uploaded; for the data package, the upgrade data package and configuration parameters are uploaded.

[0061] Step S2, after the shore management platform detects the new version of the application or data package, it determines the deployment location. For the application or data package deployed on the shore, the shore management platform prompts the user to install it on the shore; for the application or data package deployed on the ship, the shore management platform prompts the user to push it on the ship.

[0062] Step S3, after the client application service deployed on the shore client receives the shore installation request for the application or data packet sent by the shore management platform, it executes the application installation script or deploys the data packet and sends the result information to the shore management platform. After receiving the information, the shore management platform will provide real-time feedback of the installation or deployment results to the shore user. If the installation or deployment fails, the application or data packet will be rolled back to the previous version and the version information will be sent to the shore management platform.

[0063] 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 warehouse periodically pulls the application or data package from the shore-side application warehouse according to the idle time settings.

[0064] Step S5, the ship-side management platform detects the version information of the application and data package in the ship-side application warehouse in real time. When the ship-side management platform detects a new version of the application or data package, it prompts the user to perform ship-side upgrade of the application or data package. When the ship-side management platform does not detect a new version of the application and data package, the interface displays that the current version is the latest version.

[0065] Step S6, after the client application service deployed on the ship-side client receives the ship-side installation request for the application or data packet sent by the ship-side management platform, it executes the installation script of the application or deploys the data packet. If the installation or deployment fails, the application or data packet rolls back to the previous version, and the client application service sends the result information to the ship-side management platform.

[0066] Step S7: After receiving the information, the ship-side management platform will feed back the installation or deployment results to the shore-side management platform and the ship-side user in real time.

[0067] The above-mentioned embodiment only expresses one implementation mode of the present invention, and its description is relatively specific and detailed, but it cannot be understood as limiting the scope of the invention patent. It should be pointed out that for ordinary technicians in this field, several modifications and improvements can be made without departing from the concept of the present invention, which all belong to the protection scope of the present invention. Therefore, the protection scope of the patent of the present invention shall be based on the attached claims.

Claims

1. A remote upgrade system based on ship-shore integration, characterized in that: Includes the following modules: The shore management platform is deployed on the shore server. It is used to provide a visual and convenient web interface and backend for shore management personnel. All operations can be performed from the shore management platform. The operations include: viewing the version information of all applications and data packages and their deployment status on the shore and ship, adding new applications or data packages to the shore application warehouse, deleting applications or data packages in the shore application warehouse, remotely upgrading, uninstalling, and rolling back applications or data packages on the shore client, and pushing new applications or databases to the ship management platform. The ship-side management platform is deployed on the ship-side server. It is used to provide a visual and convenient web interface and backend for the ship-side management personnel. All operations can be performed from the ship-side management platform. The operations include: viewing the version information of all ship-side applications and data packages and their deployment status on the ship-side, deleting ship-side applications or data packages, and remotely upgrading, uninstalling, and rolling back applications or data packages on the ship-side client. The shore application warehouse is deployed on the shore server and 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 the management of the version information and deployment status information of the applications or data packages added to the shore application warehouse. The deployment status information includes waiting for shore installation, waiting for ship push and waiting for ship deployment; The ship-side application warehouse is deployed on the ship-side server and is used to manage the ship-side applications or data packages, including the deletion of the ship-side applications or data packages, and the management of the version information and deployment status information of the applications or data packages in the ship-side application warehouse. The deployment status information includes the version to be upgraded and the latest version; Client application service, deployed on the shore client and the ship client, is used to manage the installation, uninstallation, and rollback of application programs or data packages on the shore client and the ship client, and send the deployment status information to the corresponding shore management platform or ship management platform; MQTT service, deployed on the cloud server, is used for message transmission between the shore-side management platform and the ship-side management platform; RSYNC service, deployed on the cloud server, is used for file transfer between the shore-side application warehouse and the ship-side application warehouse; The application includes a software package to be upgraded, an installation script and an uninstallation script. The installation script executes the installation configuration operation of the software package to be upgraded, and the uninstallation script executes the uninstallation operation of the software package. The data package includes a data package file to be upgraded and configuration parameters.

2. A remote upgrade system based on ship-shore integration as claimed in claim 1, characterized in that: The types of the application include C / S architecture, B / S architecture and docker image.

3. The ship-shore fusion remote upgrade system according to claim 1, characterized in that: When adding a new application or data package to the shore application warehouse, the user needs to select the deployment location, shore deployment or ship deployment; for applications or data packages used on the shore, choose shore deployment; for applications or data packages used on the ship, choose ship deployment.

4. The ship-shore fusion remote upgrade system according to claim 1, characterized in that: The shore management platform detects the version information of the application and data packet in real time. When the shore management platform detects the new version of the current application and data packet, for the application or data packet deployed on the shore, the shore management platform prompts the user to install it on the shore; for the application or data packet deployed on the ship, the shore management platform prompts the user to push it on the ship.

5. A ship-shore fusion remote upgrade system as claimed in claim 4, characterized in that: After the client application service deployed on the shore client receives the shore installation request for the application or data packet sent by the shore management platform, it executes the installation script of the application, 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 will provide real-time feedback of the installation or deployment results to the shore user.

6. A ship-shore fusion remote upgrade system as claimed in claim 4, characterized in that: After the ship-side management platform receives the push information of the application or data packet from the shore-side management platform, the ship-side application warehouse periodically pulls the application or data packet from the shore-side application warehouse; the ship-side management platform supports users to set up idle time and set the scheduled pulling period of the ship-side application warehouse.

7. A remote upgrade system based on ship-shore integration as claimed in claim 6, characterized in that: The ship-side management platform detects the version information of the application and data package in the ship-side application warehouse in real time. When the ship-side management platform detects a new version of the application or data package, it prompts the user to upgrade the application or data package. When the ship-side management platform does not detect a new version of the application and data package, the interface displays that the current version is the latest version.

8. The ship-shore fusion remote upgrade system according to claim 7, characterized in that: After the client application service deployed on the ship-side client receives the ship-side installation request for the application or data packet sent by the ship-side management platform, it executes the installation script of the application, or deploys the data packet according to the configuration parameters, and sends the result information to the ship-side management platform. After receiving the information, the ship-side management platform will provide real-time feedback of the installation or deployment results to the shore-side management platform and ship-side users.

9. A remote upgrade method based on ship-shore integration, characterized in that: The implementation of the ship-shore fusion remote upgrade system according to any one of claims 1 to 8 comprises the following steps: Step S1: When the shore-side application warehouse receives a new application or data package, the user selects a deployment location, and for an application, uploads an upgrade package and installation / uninstallation scripts; for a data package, uploads an upgrade package and configuration parameters; Step S2: After the shore management platform detects the new version of the application or data package, it determines the deployment location. For the application or data package deployed on the shore, the shore management platform prompts the user to install it on the shore; for the application or data package deployed on the ship, the shore management platform prompts the user to push it on the ship; Step S3, after receiving the shore installation request of the application or data package sent by 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 feeds back the installation or deployment result to the shore user in real time. If the installation or deployment fails, the application or data package rolls back to the previous version, and sends the version information to the shore management platform; 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 warehouse periodically pulls the application or data package from the shore-side application warehouse according to the idle time setting; Step S5, the ship-side management platform detects the version information of the application and data package in the ship-side application warehouse in real time. When the ship-side management platform detects a new version of the application or data package, it prompts the user to perform ship-side upgrade of the application or data package. When the ship-side management platform does not detect a new version of the application and data package, the interface displays that the current version is the latest version; Step S6, after receiving the ship-side installation request of the application or data package sent by the ship-side management platform, the client application service deployed on the ship-side client executes the installation script of the application or deploys the data package. If the installation or deployment fails, the application or data package rolls back to the previous version, and the client application service sends the result information to the ship-side management platform; Step S7: After receiving the information, the ship-side management platform will feed back the installation or deployment results to the shore-side management platform and the ship-side user in real time.

Images