Web-based ship management platform and ship-shore information synchronization method

Abstract

The application discloses a ship-shore information synchronization method in a Web-based ship management platform, which comprises the following steps: starting synchronization according to a timing synchronization time and a synchronization data range, initiating a synchronization request by a ship-side server, acquiring an upgrade information package by the ship-side server and installing the upgrade information package, judging whether the ship-side server identification is consistent with the MAC address of the ship-side server, stopping synchronization and performing synchronization in a manual mode if the ship-side server identification is not consistent with the MAC address of the ship-side server, otherwise, acquiring a shore base database file package by the ship-side server, judging whether the data package in the ship-side server is consistent with the shore base database file package, updating the data package in the ship-side server according to the shore base database file package if the data package in the ship-side server is not consistent with the shore base database file package, acquiring the data package of the ship-side server in the synchronization data range and regarding the data package as a to-be-updated data package, transmitting the to-be-updated data package to a shore base server, and updating the shore base server according to the to-be-updated data package. The method improves the data consistency and the data reliability between the shore base server and the multiple ship-side servers.

Description

Technical Field

[0001] This invention relates to the field of data synchronization, and more particularly to a method for synchronizing ship-shore information in a Web-based ship management platform. Background Technology

[0002] Due to limitations in communication costs, it is difficult for ships on ocean voyages to maintain a constant connection with the computer networks of shore-based ship management companies. This results in ships being unable to access shore-based web servers in a timely manner. When data changes on the ship's server or on the shore-based server, data consistency cannot be maintained promptly. Shore-based ship management companies cannot effectively manage the ships, and ships cannot obtain the latest data in a timely manner. In other words, existing shore-based ship communication management systems are costly and the data they obtain is unreliable. Summary of the Invention

[0003] This invention provides a method for synchronizing ship-shore information in a web-based ship management platform to overcome the aforementioned technical problems.

[0004] A method for synchronizing ship-shore information in a web-based ship management platform, comprising:

[0005] Step 1: Set the scheduled synchronization time and data range in the ship's server. When the current time on the ship's server reaches the scheduled synchronization time, proceed to Step 2.

[0006] Step 2: The shipboard server initiates a synchronization request, checking if the shore-based server and the shipboard server are connected. If they are not connected, synchronization stops. If they are connected, it checks if the shore-based server is undergoing a server version iteration. If it is, synchronization stops. Otherwise, it retrieves the upgrade information packet from the shore-based server based on the shipboard vessel information and server version number stored on the shipboard server.

[0007] Step 3: The ship-side server obtains the upgrade information package and installs it. If the installation fails, synchronization stops. Otherwise, it obtains the ship-side server identifier stored in the shore-based server. The ship-side server identifier represents the MAC address of the ship-side server. It checks whether the ship-side server identifier and the ship-side server's MAC address are consistent. If they are inconsistent, synchronization stops and is performed manually. Otherwise, the ship-side server obtains the shore-based database file package and checks whether the data package in the ship-side server is consistent with the shore-based database file package. If they are inconsistent, the data package in the ship-side server is updated according to the shore-based database file package, and the process proceeds to Step 4. If they are consistent, the process proceeds directly to Step 4.

[0008] Step 4: Obtain data packets within the synchronization data range from the ship-based server. Treat the data packets within the synchronization data range as data packets to be updated and transmit them to the shore-based server. The shore-based server then updates the data packets based on the data packets to be updated.

[0009] Preferably, updating the data packets in the ship-side server based on the shore-based database file packets includes,

[0010] S1. Obtain the set of synchronization transactions and the set of synchronization times corresponding to the synchronization transactions based on the shore-based database file package.

[0011] S2. For each synchronization transaction in the synchronization transaction set, obtain the synchronization time of the synchronization transaction and use it as the start time of the update. Use the current time of the ship-side server as the end time of the update. Obtain the data table of the shore-based server according to the start time and end time. The ship-side server updates the data in the data packet according to the data table.

[0012] Preferably, the update performed by the shore-based server based on the data packet to be updated includes:

[0013] S11. The ship-side server generates a data packet to be updated based on the range of synchronized data. The data packet to be updated includes a set of synchronized transactions, a set of current version numbers corresponding to the synchronized transactions, and a set of previous version numbers.

[0014] S12. For each synchronization transaction in the synchronization transaction set, obtain the current version number and the previous version number of the synchronization transaction, obtain the data table of the ship-side server based on the current version number and the previous version number, and update the data in the database of the shore-based server based on the data table.

[0015] Preferably, the step of obtaining data packets from the ship-based server within the synchronization data range includes the user adjusting the synchronization data range through the shore-based server, obtaining data packets from the ship-based server according to the adjusted synchronization data range, and treating data packets within the synchronization data range as data packets to be updated.

[0016] Preferably, the manual synchronization includes,

[0017] S21. Based on the vessel number corresponding to the ship-side server, obtain the ship's shore-based data packet and upgrade information packet. The user imports the shore-based data packet and upgrade information packet into the ship-side server. The ship-side server updates the data packet based on the shore-based data packet and upgrades the ship-side server based on the upgrade information packet.

[0018] S22. The user exports all data from the ship's server and imports it into the shore-based server. The shore-based server updates the database based on all the data corresponding to the ship's server.

[0019] This invention provides a method for synchronizing ship-shore information in a web-based ship management platform. It involves deploying a shore-based server and database, and also deploying a ship-based server and database on each ocean-going vessel. When communication between the shore-based server and the ship-based server is lost, the ship-based server and the shore-based server operate independently. Once communication is established, the information between the ship-based server and the shore-based server is automatically synchronized, improving data consistency between the shore-based server and multiple ship-based servers. When automatic synchronization is not possible, manual synchronization can be used to synchronize the data in the shore-based server and the data in the ship-based server, thus improving data reliability. Attached Figure Description

[0020] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a flowchart of the method of the present invention;

[0022] Figure 2 This is a flowchart of the upgrade and synchronization process between the ship-based server and the shore-based server in this invention;

[0023] Figure 3 This is a schematic diagram of the shipboard server upgrade process of the present invention. Detailed Implementation

[0024] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0025] Figure 1 This is a flowchart of the method of the present invention, as shown below. Figure 1 As shown, the method in this embodiment may include:

[0026] A method for synchronizing ship-shore information in a web-based ship management platform, comprising:

[0027] Step 1: Set the scheduled synchronization time and data range in the ship's server. When the current time on the ship's server reaches the scheduled synchronization time, proceed to Step 2. This synchronization method will automatically upgrade the ship's service and then synchronize the data. Users do not need to pay attention to the process. It is suitable for users with a stable network or those who have a fixed time to connect to the internet.

[0028] Step 2: The ship-based server initiates a synchronization request and checks whether the shore-based server and the ship-based server are connected. If they are not connected, synchronization stops. If they are connected, it determines whether the shore-based server is undergoing server version iteration. If it is, synchronization stops. Otherwise, it retrieves the upgrade information package from the shore-based server based on the ship information and server version number stored in the ship-based server. Retrieving the upgrade information package includes downloading the upgrade information package with breakpoint resume, decompressing the upgrade information package through the ship-based server, and repeatedly installing the upgrade information package. If the upgrade fails, synchronization stops, and the error information is stored in an error table for manual handling by the user.

[0029] Step 3: The ship-based server obtains the upgrade information package and installs it. If the installation fails, synchronization stops. Otherwise, it obtains the ship-based server identifier stored in the shore-based server. The ship-based server identifier represents the MAC address of the ship-based server. It checks whether the ship-based server identifier and the ship-based server's MAC address are consistent. If they are inconsistent, synchronization stops and manual synchronization is performed. This synchronization method requires the user to export the data packet from the shore-based server to form an encrypted data packet containing the upgrade information package and the data packet. Offline personnel can transfer the data packet via mobile devices and import the data packet into the ship-based server. Conversely, the ship-based data packet is exported and then imported into the shore-based server. This method is suitable for users without network access. The manual synchronization includes:

[0030] S21. Based on the vessel corresponding to the ship-side server, obtain the ship's shore-based data packet and upgrade information packet. Return the upgrade information packet and shore-based data packet to the front-end page and display them to the user. The shore-based data packet can be all data in the shore-based server, or it can be a range of data packets selected by the user for export. Combine the shore-based data packet and upgrade information packet into a single encrypted DAT file and export it. The user sends the file to the ship-side server via a mobile device. The user imports the shore-based data packet and upgrade information packet into the ship-side server. The ship-side server updates the data packet based on the shore-based data packet and upgrades the ship-side server based on the upgrade information packet.

[0031] S22. The user exports all data from the ship-side server or selects a portion of the data as needed and imports it into the shore-based server. The shore-based server updates the database based on all the data corresponding to the ship-side server.

[0032] Conversely, the ship-based server retrieves the shore-based database file packet and determines whether the data packet on the ship-based server matches the shore-based database file packet. If they do not match, the data packet on the ship-based server is updated according to the shore-based database file packet, and the process proceeds to step four. Simultaneously, it checks again whether there is an upgrade information packet that needs to be upgraded. If so, the upgrade information packet is stored in the data packet, and the data packet is downloaded and resumed from where it left off to perform the upgrade and synchronize the shore-based data. If they match, the process proceeds directly to step four.

[0033] The step of updating the data packets in the ship-side server based on the shore-based database file packets includes...

[0034] S1. Obtain the set of synchronization transactions and the set of synchronization times corresponding to the synchronization transactions based on the shore-based database file package.

[0035] S2. For each synchronization transaction in the synchronization transaction set, obtain the synchronization time of the synchronization transaction as the start time of the update, take the current time of the ship-side server as the end time of the update, obtain the data table of the shore-based server according to the start time and end time, and update the data in the data packet according to the data table.

[0036] The specific implementation process of updating the data packets in the ship-side server based on the shore-based database file packets is as follows:

[0037] Check if a back.zip file, left over from previous manual data synchronization or initialization imports, exists in the fixed receipt folder \web\temp\backData. If a back.zip receipt file exists, unzip it.

[0038] web

[0039] temp

[0040] backData

[0041] back

[0042] CONT0001.zip

[0043] CONT0002.zip

[0044] CONT0003.zip

[0045] …

[0046] PICC1000.zip

[0047] common.txt

[0048] back.zip

[0049] Check if the version number in the common.txt file matches the latest version number on the current server. If they match, retrieve the synchronization time from common.txt and record the synchronization time of each transaction to the shore server.

[0050] CONT0001 2013-08-1814:00:35 CONT0002 2013-08-1814:00:35 CONT0003 2013-08-1814:00:35 …

[0051] The system retrieves the set of transactions that need to be synchronized from the shore server to the ship server from the synchronization transaction table. It then loops through this set and sends synchronization requests to the ship server sequentially (using CONT0001 as an example). The ship server uses the requested synchronization transaction ID to obtain the last synchronization time of that transaction as the start time condition for the differential data. It also obtains the current system time as the end time condition for the differential data. Finally, it retrieves all tables involved in the transaction. It then loops through all tables, differentially extracts data where [last synchronization time] < update time < [current system time], and generates a CSV file.

[0052] web

[0053] temp

[0054] COMP000000000000001

[0055] VESL0001

[0056] CONT0001

[0057] CONT0001

[0058] table1.csv

[0059] table2.csv

[0060] …

[0061] Package the CONT0001 folder into a zip archive, encrypt it into a .dat file, and then delete the CONT0001 folder. Convert the CONT0001.dat file into a data stream and return it to the ship's server. If the ship's server returns data, it converts the data stream into a .dat file. Decode the CONT001.dat file into a zip archive and then delete the .dat file. Decompress the CONT0001.zip archive. Loop through all CSV files and update the data in each CSV file to the ship's server's database, synchronously generating corresponding data receipt files.

[0062] The process involves sequentially updating the data in the CSV file to the ship's server database. This includes checking if a record exists in the ship's server database based on the primary key. If the record exists on the ship's server and its current version is less than the current version on the shore-based server, the previous version number of the ship's server data is set to match the current version number, and the data is updated in the ship's server database. If the record does not exist on the ship's server, the previous version number of the shore-based server data is set to match the current version number, and the data is inserted into the ship's server database. The ship's server is then notified to record the synchronization version number of the current transaction data and to delete the temporary folder.

[0063] Step 4: Obtain data packets from the ship-based server within the synchronization data range. Treat these data packets as data packets to be updated and transmit them to the shore-based server. The shore-based server then updates the data packets based on these data packets. Obtaining data packets from the ship-based server within the synchronization data range includes adjusting the synchronization data range via the shore-based server, obtaining the data packets to be updated from the ship-based server based on the adjusted synchronization data range, transmitting these data packets to the shore-based server, and then updating the data packets based on these data packets.

[0064] The shore-based server updates the data packets to be updated, including...

[0065] S11. The ship-side server generates a data packet to be updated based on the synchronization data range, and uploads the data packet to the specified directory on the shore-based server using a breakpoint resume method. After the upload is complete, the ship-side server is notified to parse the data packet and put the data into the database. The data packet to be updated includes a set of synchronization transactions, a set of current version numbers corresponding to the synchronization transactions, and a set of previous version numbers.

[0066] S12. For each synchronization transaction in the synchronization transaction set, obtain the current version number and the previous version number of the synchronization transaction, obtain the data table of the ship-side server based on the current version number and the previous version number, and update the data in the database of the shore-based server based on the data table.

[0067] The shore-based server updates according to the data packet to be updated, specifically by checking if a back.zip file, a receipt file left over from previous manual synchronization or initialization data imports, exists in the fixed receipt folder \web\temp\backData. If a back.zip receipt file exists, then back.zip is unzipped.

[0068] web

[0069] temp

[0070] backData

[0071] back

[0072] CONT0001.zip

[0073] CONT0002.zip

[0074] CONT0003.zip

[0075] table1.csv

[0076] table2.csv

[0077] PICC1000.zip

[0078] common.txt

[0079] back.zip

[0080] Check if the version number in the common.txt file matches the latest version number on the ship's server. If they match, unzip the files under the `back` folder to obtain each CSV file, and update the version number of the corresponding data using the CSV file ID. Locate the record in the shore-based server's database based on the primary key. Set the previous version number of the data in the shore-based server's database to match the current version number of the data in the CSV file, and update the ship's server's database accordingly.

[0081]

[0082]

[0083] Retrieve the set of transactions that need to be synchronized from all ship-based servers using the synchronization transaction table. Loop through the transaction set and synchronize the data to the shore-based servers sequentially (taking CONT0001 as an example). Retrieve all tables involved in the CONT0001 transaction. Loop through all tables, differentiate the data where the current version is greater than the previous version, and generate a CSV file.

[0084] web

[0085] temp

[0086] COMP000000000000001

[0087] VESL0001

[0088] CONT0001

[0089] CONT0001

[0090] table1.csv

[0091] table2.csv

[0092] …

[0093] Package the CONT0001 folder into a zip archive, encrypt it into a .dat file, and then delete the CONT0001 folder. Convert the CONT0001.dat file into a data stream and send it to the shore server. The shore server converts the data stream back into a .dat file. Decode the CONT001.dat file into a zip archive. Decompress the CONT0001.zip file. Loop through all CSV files and update the data in each CSV file to the shore server's database, synchronously generating corresponding data receipt files.

[0094] The step of sequentially updating the data in the CSV to the shore-based server's database includes: checking if a record exists in the shore-based server's database based on the primary key of the data. If it exists in the shore-based server's database, and the current version of the data on the shore-based server is less than the current version of the data on the ship-based server, then the previous version number of the data on the ship-based server is set to match the current version number, and the data is updated in the shore-based server's database. If it does not exist in the shore-based server's database, then the previous version number of the data on the ship-based server is set to match the current version number, and the data is inserted into the shore-based server's database. The shore-based server is notified to record the synchronization time of the current transaction. The temporary folder is deleted.

[0095] This embodiment also includes automatic (manual) synchronization: This synchronization method requires the user to manually click to synchronize and will not automatically upgrade the ship-side server during synchronization. If an upgrade is required, an upgrade message will be displayed, redirecting the user to the upgrade page. Data synchronization will then resume after the ship-side server is upgraded. This is suitable for users who have been unable to connect to the internet for extended periods, have limited network access, or cannot connect at fixed or short intervals. Specifically, the user enters the synchronization page, clicks the synchronize data option, the ship-side server initiates a synchronization request, checks if the shore-based server and the ship-side server are connected. If they are not connected, synchronization stops. Otherwise, the ship-side server initiates a request, checks if the shore-based server is undergoing version iteration. If it is, the synchronization stops, and a prompt message appears informing the user that the shore-based server is upgrading and to try synchronizing data again later. Otherwise, it verifies if the ship-side server identifier (MAC address) matches the shore-based server record. If they do not match, the synchronization stops, the error information is stored in an error table, and a prompt message appears: "This client is not authenticated on the shore-based service; please contact customer service to authenticate the client." Otherwise, it obtains the upgrade package information for this vessel from the shore-based server using the ship information and version number of the ship-side server. Upon receiving upgrade package information, a pop-up notification appears, informing the user that the ship-side server needs an upgrade and requesting them to proceed to the upgrade page. The system checks for files requiring continued transmission and any unprocessed retrieval data files from other synchronization methods. It processes the retrieval files from both sides, updating them in the corresponding server databases. Based on the shore-based database file package, it updates the data packets in the ship-side server, displaying the ship-side and shore-based data names on the page for the user to select the synchronization range. Based on the user's selection, it uploads the ship-side data packets to the shore-based server using a resume-from-breakpoint method, then downloads the shore-based data packets to the ship-side server using the same resume-from-breakpoint method. It processes each data packet separately, decrypting and decompressing them, and finally updates the data in the corresponding databases, inserting the corresponding synchronization records. A synchronization success message pops up for the user.

[0096] The specific application process of the ship-shore information synchronization method in the web-based ship management platform in this embodiment is as follows: Figure 2 As shown, specifically, the ship-side server initiates synchronization, obtains the differential module, which includes a shore-based database file package, determines whether there is a new differential module, and if so, obtains the upgrade package for the new module and determines whether to upgrade. If so, the ship-side server initiates the upgrade, downloads the upgrade package, installs the upgrade package, and restarts the service; otherwise, it differentiates the data at both ends, which are the data from the shore-based server and the ship-side server, selects the data to be synchronized, and synchronizes the shore-based data to the ship-side server and the ship-side data to the shore-side server.

[0097] The process of upgrading the ship's server according to the upgrade information package is as follows: Figure 3As shown, specifically, the ship-side server sends an upgrade request, which includes the company ID, ship ID, and current version number. The shore-based server receives the request and analyzes the ship-side server's version information to check for updates. If no update is found, it returns the message: "No new version update." If there is an update but no newly enabled modules, it iterates through the upgrade history information table to find the upgrade package to be downloaded for this upgrade. If there is both an update and newly enabled modules, it compares the company service information table and the ship module information table, retrieves the modules that differ in version number (i.e., it determines if the ship-side server's version number is less than the shore-based server's version number), and obtains the upgrade package to be downloaded based on the version number. For example, assuming the current ship-side server version is 1.01 and the latest version of the shore-based server is 1.03, the version difference between the ship-side server and the shore-based server is calculated. The upgrade package to be downloaded based on the version number is as follows:

[0098] patch_1.01-1.02.zip

[0099] patch_1.02-1.03.zip

[0100] Based on the version differences, requests are made to the shore-based server in sequence to download the upgrade package.

[0101] Tomcat 6.0.20

[0102] patch

[0103] patch_1.01-1.02.zip

[0104] patch_1.02-1.03.zip

[0105] In the Tomcat 6.0.20 directory, generate the batch file updateAll.bat to install the upgrade package.

[0106] The content is: cd / d%1%

[0107] .\\7z\\7za.exex. / patch / patch_1.01-1.02.zip-o. / patch /

[0108] .\\7z\\7za.exex. / patch / patch_1.02-1.03.zip-o. / patch /

[0109] start / waitcall.\\patch\\patch_1.01-1.02\\update.bat

[0110] start / waitcall.\\patch\\patch_1.01-1.02\\update.bat

[0111] del / s / q.\\patch\\patch_1.01-1.02.zip

[0112] del / s / q.\\patch\\patch_1.02-1.03.zip

[0113] rd / s / q.\\patch\\patch_1.01-1.02

[0114] rd / s / q.\\patch\\patch_1.02-1.03

[0115] Tomcat 6.0.20

[0116] patch

[0117] patch_1.01-1.02.zip

[0118] patch_1.02-1.03.zip

[0119] updateAll.bat

[0120] The updateAll.bat command is invoked to perform the upgrade. The ship's server updates to the latest version number, notifies the shore-based server to update to the latest version number for the ship, restarts the ship service, and the upgrade is complete.

[0121] Overall beneficial effects:

[0122] This invention provides a method for synchronizing ship-shore information in a web-based ship management platform. It involves deploying a shore-based server and database, and also deploying a ship-based server and database on each ocean-going vessel. When communication between the shore-based server and the ship-based server is lost, the ship-based server and the shore-based server operate independently. Once communication is established, ship-shore information is automatically synchronized, improving data consistency between the shore-based server and multiple ship-based servers. When automatic synchronization is not possible, manual synchronization can be used to synchronize data between the shore-based server and the ship-based server, improving data reliability.

[0123] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for synchronizing ship-shore information in a web-based ship management platform, characterized in that, include, Step 1: Set the scheduled synchronization time and data range in the ship's server. When the current time on the ship's server reaches the scheduled synchronization time, proceed to Step 2. Step 2: The shipboard server initiates a synchronization request, checking if the shore-based server and the shipboard server are connected. If they are not connected, synchronization stops. If they are connected, it checks if the shore-based server is undergoing a server version iteration. If it is, synchronization stops. Otherwise, it retrieves the upgrade information packet from the shore-based server based on the shipboard vessel information and server version number stored on the shipboard server. Step 3: The ship-side server obtains the upgrade information package and installs it. If the installation fails, synchronization stops. Otherwise, it obtains the ship-side server identifier stored in the shore-based server. The ship-side server identifier represents the MAC address of the ship-side server. It checks whether the ship-side server identifier and the ship-side server's MAC address are consistent. If they are inconsistent, synchronization stops and is performed manually. Otherwise, the ship-side server obtains the shore-based database file package and checks whether the data package in the ship-side server is consistent with the shore-based database file package. If they are inconsistent, the data package in the ship-side server is updated according to the shore-based database file package, and the process proceeds to Step 4. If they are consistent, the process proceeds directly to Step 4. The manual synchronization method includes... S21. Based on the vessel number corresponding to the ship-side server, obtain the ship's shore-based data packet and upgrade information packet. The user imports the shore-based data packet and upgrade information packet into the ship-side server. The ship-side server updates the data packet based on the shore-based data packet and upgrades the ship-side server based on the upgrade information packet. S22. The user exports all the data from the ship's server and imports it into the shore-based server. The shore-based server updates the database based on all the data corresponding to the ship's server. Step 4: Obtain data packets within the synchronization data range from the ship-based server. Treat the data packets within the synchronization data range as data packets to be updated and transmit them to the shore-based server. The shore-based server then updates the data packets based on the data packets to be updated.

2. The method of claim 1, wherein the synchronization of the ship-shore information in the Web-based ship management platform is characterized by, The step of updating the data packets in the ship-side server based on the shore-based database file packets includes... S1. Obtain the set of synchronization transactions and the set of synchronization times corresponding to the synchronization transactions based on the shore-based database file package. S2. For each synchronization transaction in the synchronization transaction set, obtain the synchronization time of the synchronization transaction and use it as the start time of the update. Use the current time of the ship-side server as the end time of the update. Obtain the data table of the shore-based server according to the start time and end time. The ship-side server updates the data in the data packet according to the data table.

3. The method of claim 1, wherein the synchronization of the ship-shore information in the Web-based ship management platform is characterized by, The shore-based server updates the data packets to be updated, including... S11. The ship-side server generates a data packet to be updated based on the range of synchronized data. The data packet to be updated includes a set of synchronized transactions, a set of current version numbers corresponding to the synchronized transactions, and a set of previous version numbers. S12. For each synchronization transaction in the synchronization transaction set, obtain the current version number and the previous version number of the synchronization transaction, obtain the data table of the ship-side server based on the current version number and the previous version number, and update the data in the database of the shore-based server based on the data table.

4. The method of claim 1, wherein the synchronization of the ship-shore information in the Web-based ship management platform is characterized by, The process of obtaining data packets from the ship-based server within the synchronization data range includes the user adjusting the synchronization data range through the shore-based server, obtaining data packets from the ship-based server based on the adjusted synchronization data range, and treating data packets within the synchronization data range as data packets to be updated.

Images