Building material supply chain data synchronization method, system and device and storage medium

Abstract

The invention relates to a building material supply chain data synchronization method, and the method comprises the steps: collecting real-time data of an SAAS platform, a local ERP system and a third-party data source through a multi-protocol adapter, and the real-time data comprises building material inventory, logistics vehicle coordinates, order state change and enterprise industry and commerce information change; dynamically converting the collected real-time data to generate a standardized data packet; the dynamic conversion comprises field mapping, unit standardization and data traceability label addition; selecting an encryption strategy according to the data sensitivity level, and encrypting the standardized data packet to obtain an encrypted data packet; and constructing a synchronous topology network based on a data dependency relationship among multiple platforms, and distributing the encrypted data packet to a target platform based on the synchronous topology network for data synchronization.

Description

Technical Field

[0001] This application relates to the field of building materials supply chain data management, and in particular to a method, system, device and storage medium for synchronizing building materials supply chain data. Background Technology

[0002] The building materials supply chain typically involves multiple stakeholders, including suppliers, manufacturers, logistics providers, and contractors. Data is scattered across heterogeneous systems such as ERP, WMS, and TMS, leading to issues like inconsistent data formats and update delays. Traditional data synchronization technologies (such as ETL tools and database triggers) rely on timed batch transmissions, which cannot meet the needs of real-time collaboration and can easily result in inconsistent inventory information and delayed order status.

[0003] Therefore, it is necessary to provide a method, system, equipment, and storage medium for synchronizing data in the building materials supply chain to improve the effectiveness and security of data synchronization in the building materials supply chain. Summary of the Invention

[0004] This application provides a method, system, and storage medium for synchronizing data in the building materials supply chain, in order to improve the effectiveness and security of data synchronization in the building materials supply chain.

[0005] Firstly, this application provides a method for synchronizing data in a building materials supply chain, the method comprising:

[0006] Real-time data is collected from the SaaS platform, local ERP system and third-party data sources through a multi-protocol adapter. The real-time data includes building material inventory, logistics vehicle coordinates, order status changes and changes in enterprise business registration information.

[0007] The collected real-time data is dynamically transformed to generate standardized data packets; the dynamic transformation includes field mapping, unit standardization, and the addition of data traceability tags;

[0008] Based on the data sensitivity level, an encryption strategy is selected to encrypt the standardized data packet, resulting in an encrypted data packet;

[0009] A synchronous topology network is constructed based on the data dependencies between multiple platforms, and the encrypted data packets are distributed to the target platform for data synchronization based on the synchronous topology network.

[0010] In some embodiments, the method further includes:

[0011] Obtain the data packet signature information returned by each target platform;

[0012] Based on the data packet signature information and the preset version verification mechanism, the data packets received by each target platform are subjected to consistency verification.

[0013] When a data conflict is detected across multiple platforms, a conflict resolution strategy based on business rules is triggered to complete the data synchronization across multiple platforms based on the conflict resolution strategy.

[0014] In some embodiments, the conflict resolution strategy based on business rules includes conflict resolution priorities;

[0015] The conflict resolution priority is determined by the following formula:

[0016]

[0017] Among them, P k S represents the priority score for platform k; a higher value indicates higher priority. k T represents the permission level of platform k, which is the default value. current T is the system's unified timestamp when a conflict detection occurs. k T is the timestamp for the operation that resolves execution conflicts on platform k. max λ represents the maximum allowable time window, and θ represents the balance coefficients, which are preset values.

[0018] In some embodiments, the step of dynamically transforming the collected real-time data to generate standardized data packets includes:

[0019] Build a cross-platform field mapping rule library;

[0020] Based on the mapping rule base, various types of data in the real-time data are converted to fields in the local database table;

[0021] A globally unique synchronization identifier is added to the converted data to obtain the standardized data packet.

[0022] In some embodiments, constructing a synchronous topology network based on data dependencies between multiple platforms includes:

[0023] A candidate directed edge set is generated based on the data dependencies between the multiple platforms;

[0024] The path weights of each path in the candidate directed edge set are calculated in real time, and the target directed edge set is determined based on the path weights.

[0025] Based on the target set of directed edges, the synchronous topology network is constructed.

[0026] In some embodiments, distributing the encrypted data packets to the target platform for data synchronization based on the synchronization topology network includes:

[0027] Obtain the current network connection status between each target platform;

[0028] Based on the network connection state, calculate the transmission cost of the transmission path corresponding to each directed edge in the synchronous topology network;

[0029] Obtain the historical reliability score of the transmission path corresponding to each directed edge;

[0030] Based on the network connection status, the transmission cost, and the historical reliability score, the target transmission path corresponding to each target platform is determined.

[0031] The encrypted data packet is distributed to the corresponding target platform through the target transmission path.

[0032] In some embodiments, determining the target transmission path corresponding to each target platform based on the network connection status, the transmission cost, and the historical reliability score includes:

[0033] The path score for each transmission path is calculated using the following formula, and the target transmission path is determined based on the path score.

[0034]

[0035] Among them, S ij For the path score of the transmission path ij from platform i to platform j, D ij D represents the network connection status corresponding to transmission path ij. max C is the maximum allowable network latency. ij C represents the transmission cost corresponding to transmission path ij. max To the maximum allowed transmission cost, R ij The reliability history score for transmission path ij is given, where α1, α2, and α3 are balance coefficients, and the sum of α1, α2, and α3 is 1.

[0036] Secondly, this application provides a building materials supply chain data synchronization system, the system comprising:

[0037] The data acquisition module is used to collect real-time data from the SAAS platform, the local ERP system and third-party data sources through a multi-protocol adapter. The real-time data includes building material inventory, logistics vehicle coordinates, order status changes and changes in enterprise business registration information.

[0038] The data conversion module is used to dynamically convert the collected real-time data to generate standardized data packets; the dynamic conversion includes field mapping, unit standardization, and data traceability tag addition;

[0039] The data encryption module is used to select an encryption strategy according to the data sensitivity level and encrypt the standardized data packet to obtain an encrypted data packet;

[0040] The data synchronization module is used to construct a synchronization topology network based on the data dependencies between multiple platforms, and to distribute the encrypted data packets to the target platform for data synchronization based on the synchronization topology network.

[0041] Thirdly, an electronic device is provided, including a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0042] Memory, used to store computer programs;

[0043] When a processor executes a program stored in memory, it implements the steps of the building materials supply chain data synchronization method according to any embodiment of the first aspect.

[0044] Fourthly, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the building materials supply chain data synchronization method as described in any embodiment of the first aspect.

[0045] Compared with the prior art, the technical solutions provided in this application have the following advantages: By constructing a cross-platform field mapping rule base, efficient integration of multi-source heterogeneous data is achieved; combined with a dynamic data conversion engine, unit / format differences are eliminated, ensuring data consistency; the intelligent path selection mechanism based on a synchronous topology network (network status awareness, transmission cost optimization, and reliability scoring) effectively reduces the latency of critical business data transmission and improves the accuracy of path decision-making; through a globally unique synchronization identifier and a multi-version storage architecture, end-to-end data lineage tracing is achieved, improving conflict detection efficiency and reducing the need for manual intervention; hierarchical encryption strategies and dynamic routing adaptation reduce the risk of sensitive data leakage, providing a highly secure, highly compatible, and adaptive data collaboration infrastructure for the digitalization of the building materials supply chain. Attached Figure Description

[0046] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0047] 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, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0048] Figure 1 A flowchart illustrating a data synchronization method for a building materials supply chain provided in this application embodiment;

[0049] Figure 2 A schematic flowchart illustrating the conflict detection method provided in this application embodiment;

[0050] Figure 3 A flowchart illustrating the data synchronization method based on a synchronous topology network provided in this application embodiment;

[0051] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

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

[0053] Figure 1 This is a flowchart illustrating a data synchronization method for a building materials supply chain, provided as an embodiment of this application. In some embodiments, Figure 1 The process shown can be performed by electronic devices, such as... Figure 1 As shown, the process may include the following operations:

[0054] Step 101: Collect real-time data from the SaaS platform, local ERP system and third-party data sources through a multi-protocol adapter.

[0055] The real-time data includes building material inventory, logistics vehicle coordinates, order status changes, and changes in enterprise registration information.

[0056] A multi-protocol adapter is an interface conversion device that supports multiple communication protocols and is used to unify access to data sources on different platforms.

[0057] SaaS platforms are cloud-based supply chain management systems that provide online resource management, order processing, and other functions. For example, Alibaba Cloud's building materials supply chain management platform supports multi-tenant data isolation.

[0058] A local ERP system is a resource planning and management system deployed on an enterprise's internal server, used to manage core business processes such as production, inventory, and procurement. For example, the Yonyou U8 ERP system is accessed via the intranet.

[0059] Third-party data sources are interface services provided by external data providers (such as logistics companies and business information platforms). Examples include SF Express's logistics tracking API and Qichacha's enterprise information interface.

[0060] Real-time data is data collected in real time. Real-time data includes building material inventory, logistics vehicle coordinates, order status changes, and changes to company registration information.

[0061] Building material inventory includes the real-time quantity of building materials currently in the warehouse (e.g., 500 tons of cement). Logistics vehicle coordinates include GPS location data of transport vehicles (e.g., latitude and longitude 116.40, 39.90). Order status changes include order lifecycle events (e.g., "shipped" or "delivered"). Enterprise business information changes include changes to enterprise registration information (e.g., changes in registered capital).

[0062] In some embodiments, protocol adaptation is performed by listening on the protocol ports of various platforms (such as HTTP port 80, MQTT port 1883) through an adapter. Data can then be collected through SaaS platforms, local ERP systems, and data interfaces provided by third parties.

[0063] Step 102: Dynamically transform the real-time data to generate standardized data packets.

[0064] The dynamic transformation includes field mapping, unit standardization, and the addition of data traceability tags.

[0065] Dynamic transformation is the process of converting heterogeneous data formats into a unified structure. Standardized data packets are datasets obtained after dynamically transforming (standardizing) real-time data.

[0066] Field mapping maps field names from different platforms to a unified field name. For example, it maps the product_id of a SaaS platform to the standard field resource_id.

[0067] Unit standardization is the process of converting different units into international standard units. For example, converting "ten thousand tons" to "ton" (10,000 tons → 10^4 tons).

[0068] Data source tags are metadata tags that record the data source, generation time, and operator. For example, {source:"SAAS",timestamp:1630000000000,operator:"user_01"}.

[0069] A standardized data packet is a data unit that includes uniform fields, standard units, and traceability information.

[0070] In some embodiments, real-time data can be dynamically transformed through methods such as field mapping, unit conversion, and adding traceability tags to obtain standardized data packets.

[0071] In some embodiments, the dynamic transformation of the collected real-time data to generate standardized data packets may include the following operations.

[0072] S10, build a cross-platform field mapping rule library.

[0073] Cross-platform fields are different names for the same business entity across different data sources (such as SaaS platforms and ERP systems). For example, a SaaS platform field might be `product_id` (product ID); while an ERP system field might be `item_code` (product code).

[0074] A mapping rule base is a database or configuration file that stores field correspondences and defines the mapping logic between source fields and target fields.

[0075] In some embodiments, rule configuration can be performed by manually defining or automatically extracting field correspondences through machine learning (such as based on field semantic similarity), supporting hot updates, and dynamically expanding the rule base when a new data source is added.

[0076] S11, Based on the mapping rule base, convert various types of data in the real-time data with fields in the local database table.

[0077] Local database table fields are structured fields used to store data in the target database (such as MySQL or Oracle). For example, the fields in the inventory table are: item_code (text type) and stock_qty (integer type).

[0078] Field conversion is the process of converting the field name and data type of the source platform into the field of the target database. For example, SAAS field capacity:500 (unit: tons) → ERP field stock_qty:500 (no unit).

[0079] In some embodiments, field names can be replaced according to the rule base (e.g., product_id → item_code), invalid characters can be deleted (e.g., remove the text "tons" from the capacity field and keep only the numbers), and then data type conversion can be performed.

[0080] S12, Add a globally unique synchronization identifier to the converted data to obtain the standardized data packet.

[0081] A globally unique synchronization identifier (UUID) is a cross-platform unique identifier for data packets used to track data synchronization paths. For example, a UUID format like 550e8400e29b41d4a716446655440000.

[0082] In some embodiments, a UUID algorithm (such as UUIDv4) can be used to generate a unique identifier.

[0083] In this embodiment, seamless mapping of fields across multiple platforms is achieved through a rule base, which reduces the amount of manual configuration. The GUID identifier ensures end-to-end tracking of data packets, which can improve the efficiency of locating synchronization problems. At the same time, it supports the rapid access of new data sources, reducing the time required for rule base expansion.

[0084] Step 103: Select an encryption strategy based on the data sensitivity level to encrypt the standardized data packet, thereby obtaining an encrypted data packet.

[0085] Data sensitivity levels are classifications of data confidentiality, which can include highly sensitive data such as corporate social credit codes and financial data, and moderate data such as inventory levels and logistics coordinates.

[0086] Encryption strategies select encryption algorithms and transmission channels based on the sensitivity level. For example, highly sensitive data uses the Chinese national standard SM4 algorithm via a dedicated line. Ordinary data uses the AES256 algorithm via the public internet.

[0087] An encrypted data packet is a data packet that has been encrypted. In some embodiments, the encrypted data packet may be decryptable only by the target platform. For example, a standardized data packet can be encrypted using a public key provided by the target platform, in which case only the target platform can decrypt the encrypted data packet using the corresponding private key.

[0088] In some embodiments, sensitivity levels can be automatically classified according to field type (e.g., field_type:"credit_code" → high sensitivity). Based on the sensitivity level classification result, an encryption library (e.g., OpenSSL) can be called to encrypt standardized data packets according to the corresponding encryption algorithm.

[0089] Step 104: Construct a synchronization topology network based on the data dependencies between multiple platforms, and distribute the encrypted data packets to the target platform for data synchronization based on the synchronization topology network.

[0090] Data dependencies refer to the data connections between platforms. For example, order data needs to be synchronized to both systems, and inventory data needs to be pushed to the logistics scheduling system.

[0091] Synchronous topology is a directed graph structure that describes the data distribution path, where nodes are platforms and edges are synchronization paths (transmission paths).

[0092] The target platform is the terminal system to which the data packet needs to reach. For example, order data needs to be synchronized to both the SaaS platform and the customer's ERP system.

[0093] Data synchronization is the process by which a target platform receives and updates local data.

[0094] In some embodiments, the platform configuration file can be parsed to generate a set of directed edges (e.g., SAAS→ERP), the data transmission path can be determined based on parameters such as network latency, and the encrypted data packets can be pushed to the target platform via a message queue (e.g., Kafka) through the determined data transmission path.

[0095] In some embodiments, the construction of a synchronous topology network based on data dependencies between multiple platforms may include the following operations.

[0096] S20, Generate a set of candidate directed edges based on the data dependencies between the multiple platforms.

[0097] Data dependencies between multiple platforms refer to the dependencies in data flow between different systems, and can be used to describe the direction of data transmission from the source platform to the target platform. For example, order data on a SaaS platform depends on inventory data in the local ERP system (inventory needs to be verified before an order is generated); another example is that transportation status data on a logistics platform depends on order numbers on the SaaS platform (transport orders need to be linked to orders).

[0098] The candidate directed edge set is a set of directed edges consisting of all possible data transmission paths, with each edge representing the data flow from one platform to another.

[0099] In some embodiments, API call logs or data flow configurations between platforms can be parsed to identify data dependency directions (e.g., ERP→SAAS indicates that ERP is the data source for SAAS). Candidate directed edges are created for each pair of platforms with a dependency relationship, and the metadata of the edges (such as data type and transmission frequency) is recorded to obtain a set of candidate directed edges.

[0100] S21, calculate the path weight of each path in the candidate directed edge set in real time, and determine the target directed edge set based on the path weight.

[0101] Path weight is a metric that quantifies path priority, calculated based on parameters such as transmission delay, throughput, and error rate.

[0102] The target directed edge set is the set of high-weight paths retained after filtering, used for actual data transmission.

[0103] In some embodiments, the real-time performance metrics of the path can be obtained through a monitoring system, the weight of each edge can be dynamically calculated using a preset formula, edges with weights higher than a threshold (e.g., weight > 5) can be retained, or the Top N paths can be sorted by weight to obtain the target directed edge set.

[0104] S22, Based on the target directed edge set, the synchronous topology network is constructed.

[0105] Synchronous topology networks are mesh structures composed of directed edges representing the actual data transmission paths used.

[0106] In some embodiments, the target directed edge can be loaded into a graph database (such as Neo4j) to build the association between nodes and edges, and the topology can be dynamically adjusted according to real-time weight changes (such as removing low-weight edges and adding high-weight edges).

[0107] In this embodiment, a complete chain of protocol adaptation → dynamic conversion → hierarchical encryption → topology distribution is used to achieve real-time, secure, and accurate synchronization of data across multiple platforms in the building materials supply chain, thus solving the problems of data silos and collaborative efficiency.

[0108] Figure 2 This is a schematic flowchart illustrating the conflict detection method provided in an embodiment of this application. In some embodiments, Figure 2 The process shown can be performed by electronic devices, such as... Figure 2 As shown, the process may include the following operations:

[0109] Step 201: Obtain the data packet signature information returned by each target platform.

[0110] Data packet signature information is a digital signature used to verify data integrity and origin, and can be generated by a hash algorithm. For example, a hash value e3b0c44298fc1c14... generated based on SHA256. The signature information includes metadata such as the signature value, signature algorithm identifier, and timestamp.

[0111] In some embodiments, the target platform's signature interface can be polled via API (e.g., once every second). After receiving the data, the target platform actively calls the callback interface to return signature information. For example, after receiving the encrypted data packet, the logistics platform calls the SaaS platform's / callback / sign interface to return the signature 0x1A3F...

[0112] Step 202: Perform consistency verification on the data packets received by each target platform based on the data packet signature information and the preset version verification mechanism.

[0113] Version verification mechanisms are rules used to check data version consistency, including timestamp comparison and sequence number increment verification. For example, timestamp comparison requires that the signature timestamp returned by the target platform differs from the source data timestamp by no more than 5 seconds. Sequence number verification requires that the data packet version number strictly increment (e.g., version:1024→1025).

[0114] Consistency verification is the process of verifying whether the data received by the target platform is completely consistent with the original data. For example, it compares whether the hash value of the source data is the same as the hash value returned by the target platform.

[0115] In some embodiments, the hash value of the data packet generated by the source system (e.g., H1) can be compared with the hash value generated and received by the target platform (e.g., H2). If H1 ≠ H2, it is determined that the data is inconsistent.

[0116] In some embodiments, the version number of the data packet can be checked to see if they are consecutive (e.g., if the current version is 100 and the target platform version is 99, it is determined to be outdated). For example, if the source data packet version is 105 and an ERP system returns version 104, a version inconsistency alarm is triggered.

[0117] Step 203: When a multi-platform data conflict is detected, a conflict resolution strategy based on business rules is triggered to complete the multi-platform data synchronization based on the conflict resolution strategy.

[0118] Data conflict refers to the existence of different versions or contents of the same data entity across multiple platforms. For example, inventory conflict: the SaaS platform shows cement inventory as 500 tons, while the local ERP shows 450 tons. Another example is order conflict: the logistics platform marks an order as "delivered," while the customer's system marks it as "in transit."

[0119] Conflict resolution strategies are a set of methods for automatically or manually resolving data conflicts based on preset rules. For example, a priority strategy: data from the SaaS platform has higher priority than data from the local ERP system. Another example is a timestamp strategy: selecting the data version with the latest timestamp.

[0120] Business rules are the conflict handling logics established by an enterprise related to its business processes. For example, financial data takes precedence: when invoice amounts conflict, the data from the financial system prevails. Another example is strong inventory consistency: when inventory data conflicts, manual review is triggered.

[0121] In some embodiments, the conflict resolution strategy based on business rules includes conflict resolution priorities.

[0122] The conflict resolution priority is determined by the following formula (1).

[0123]

[0124] Among them, P k S represents the priority score for platform k; a higher value indicates higher priority. k T represents the permission level of platform k, which is the default value. current T is the system's unified timestamp when a conflict detection occurs. k T is the timestamp for the operation that resolves execution conflicts on platform k. max λ represents the maximum allowable time window, and θ represents the balance coefficients, which are preset values.

[0125] In some embodiments, conflict detection can be performed by comparing data versions and field values ​​(such as inventory levels and order status) across multiple platforms. When a conflict is detected, a conflict resolution strategy is executed. For example, automatic resolution: overwrite conflicting data according to rules (such as forcibly synchronizing the SaaS platform version). Another example is manual intervention: push an alert to the administrator's terminal and wait for manual confirmation.

[0126] In this embodiment, signature verification can ensure that the data is not tampered with during transmission, achieve eventual consistency of data across multiple platforms, and avoid business logic errors caused by version lag.

[0127] Figure 3 This is a flowchart illustrating a data synchronization method based on a synchronous topology network provided in an embodiment of this application. In some embodiments, Figure 3 The process shown can be performed by electronic devices, such as... Figure 3 As shown, the process may include the following operations.

[0128] Step 301: Obtain the current network connection status between each target platform.

[0129] Network connectivity status is a set of parameters that describe the quality of real-time network communication between target platforms, including metrics such as latency, bandwidth, and packet loss rate.

[0130] Step 302: Based on the network connection state, calculate the transmission cost of the transmission path corresponding to each directed edge in the synchronous topology network.

[0131] Transmission cost is a metric that quantifies the economics and efficiency of a data transmission path. It can be calculated based on factors such as latency, bandwidth cost, and priority weights. For example, the cost formula is: Transmission Cost = 0.5(Latency / 100ms) + 0.3(1 / Bandwidth) + 0.2(Packet Loss Rate). If latency = 50ms, bandwidth = 100Mbps, and packet loss rate = 0.1%, then the cost...

[0132] =0.5(0.5)+0.3(0.01)+0.2(0.001)=0.253.

[0133] In some embodiments, parameters with different dimensions such as delay and bandwidth can be mapped to the [0,1] interval (e.g., delay / maximum allowable delay), and the comprehensive transmission cost can be calculated based on preset weights.

[0134] Step 303: Obtain the historical reliability score of the transmission path corresponding to each directed edge.

[0135] The historical reliability score is a path reliability score (0-1) calculated based on indicators such as historical transmission success rate and error recovery time.

[0136] In some embodiments, transmission records from the past 30 days can be extracted from the log database to calculate success rate and recovery time. The score is updated after each transmission is completed (e.g., using a sliding window mechanism to retain only the most recent N transmission records).

[0137] Step 304: Based on the network connection status, the transmission cost, and the historical reliability score, determine the target transmission path corresponding to each target platform.

[0138] The target transmission path is the optimal data transmission path selected after considering both transmission cost and reliability score. For example, candidate paths: Path A: cost = 0.57, score = 0.88; Path B: cost = 0.62, score = 0.92; choose Path B (higher score, acceptable cost).

[0139] In some embodiments, determining the target transmission path corresponding to each target platform based on the network connection status, the transmission cost, and the historical reliability score includes: calculating the path score corresponding to each transmission path using the following formula (2), and determining the target transmission path based on the size of the path score;

[0140]

[0141] Among them, S ij For the path score of the transmission path ij from platform i to platform j, D ij D represents the network connection status corresponding to transmission path ij. max C is the maximum allowable network latency. ij C represents the transmission cost corresponding to transmission path ij. max To the maximum allowed transmission cost, R ij The reliability history score for transmission path ij is given, where α1, α2, and α3 are balance coefficients, and the sum of α1, α2, and α3 is 1.

[0142] Step 305: Distribute the encrypted data packet to the corresponding target platform through the target transmission path.

[0143] In some embodiments, data packets can be encapsulated according to protocols supported by the target platform, and then encrypted data can be transmitted through the target transmission path.

[0144] Based on the same inventive concept, this application also provides a building materials supply chain data synchronization system, the system comprising:

[0145] The data acquisition module is used to collect real-time data from the SAAS platform, the local ERP system and third-party data sources through a multi-protocol adapter. The real-time data includes building material inventory, logistics vehicle coordinates, order status changes and changes in enterprise business registration information.

[0146] The data conversion module is used to dynamically convert the collected real-time data to generate standardized data packets; the dynamic conversion includes field mapping, unit standardization, and data traceability tag addition;

[0147] The data encryption module is used to select an encryption strategy according to the data sensitivity level and encrypt the standardized data packet to obtain an encrypted data packet;

[0148] The data synchronization module is used to construct a synchronization topology network based on the data dependencies between multiple platforms, and to distribute the encrypted data packets to the target platform for data synchronization based on the synchronization topology network.

[0149] like Figure 4 As shown in the figure, this application provides an electronic device, including a processor 111, a communication interface 112, a memory 113, and a communication bus 114, wherein the processor 111, the communication interface 112, and the memory 113 communicate with each other through the communication bus 114.

[0150] Memory 113 is used to store computer programs;

[0151] In one embodiment of this application, when the processor 111 executes the program stored in the memory 113, it implements the method for synchronizing building material supply chain data provided in any of the foregoing method embodiments, including:

[0152] Real-time data is collected from the SaaS platform, local ERP system and third-party data sources through a multi-protocol adapter. The real-time data includes building material inventory, logistics vehicle coordinates, order status changes and changes in enterprise business registration information.

[0153] The collected real-time data is dynamically transformed to generate standardized data packets; the dynamic transformation includes field mapping, unit standardization, and the addition of data traceability tags;

[0154] Based on the data sensitivity level, an encryption strategy is selected to encrypt the standardized data packet, resulting in an encrypted data packet;

[0155] A synchronous topology network is constructed based on the data dependencies between multiple platforms, and the encrypted data packets are distributed to the target platform for data synchronization based on the synchronous topology network.

[0156] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the building materials supply chain data synchronization method provided in any of the foregoing method embodiments.

[0157] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0158] The above description is merely a specific embodiment of the present invention, enabling those skilled in the art to understand or implement the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A method for synchronizing data in a building materials supply chain, characterized in that, The method includes: Real-time data is collected from the SaaS platform, local ERP system and third-party data sources through a multi-protocol adapter. The real-time data includes building material inventory, logistics vehicle coordinates, order status changes and changes in enterprise business registration information. The collected real-time data is dynamically transformed to generate standardized data packets; the dynamic transformation includes field mapping, unit standardization, and the addition of data traceability tags; An encryption strategy is selected based on the data sensitivity level, and the standardized data packet is encrypted to obtain an encrypted data packet; A synchronization topology network is constructed based on the data dependencies between multiple platforms, and the encrypted data packets are distributed to the target platform for data synchronization based on the synchronization topology network.

2. The method according to claim 1, characterized in that, The method further includes: Obtain the data packet signature information returned by each target platform; Based on the data packet signature information and the preset version verification mechanism, the data packets received by each target platform are subjected to consistency verification. When a data conflict is detected across multiple platforms, a conflict resolution strategy based on business rules is triggered to complete the data synchronization across multiple platforms based on the conflict resolution strategy.

3. The method according to claim 2, characterized in that, The conflict resolution strategy based on business rules includes conflict resolution priorities; The conflict resolution priority is determined by the following formula: Among them, P k S represents the priority score for platform k; a higher value indicates higher priority. k T represents the permission level of platform k, which is the default value. current T is the system's unified timestamp when a conflict detection occurs. k T is the timestamp for the operation that resolves execution conflicts on platform k. max λ represents the maximum allowable time window, and θ represents the balance coefficients, which are preset values.

4. The method according to claim 1, characterized in that, The step of dynamically transforming the collected real-time data to generate standardized data packets includes: Build a cross-platform field mapping rule library; Based on the mapping rule base, various types of data in the real-time data are converted to fields in the local database table; A globally unique synchronization identifier is added to the converted data to obtain the standardized data packet.

5. The method according to claim 1, characterized in that, The construction of a synchronous topology network based on data dependencies between multiple platforms includes: A candidate directed edge set is generated based on the data dependencies between the multiple platforms; The path weights of each path in the candidate directed edge set are calculated in real time, and the target directed edge set is determined based on the path weights. Based on the target set of directed edges, the synchronous topology network is constructed.

6. The method according to claim 5, characterized in that, The step of distributing the encrypted data packets to the target platform for data synchronization based on the synchronization topology network includes: Obtain the current network connection status between each target platform; Based on the network connection state, calculate the transmission cost of the transmission path corresponding to each directed edge in the synchronous topology network; Obtain the historical reliability score of the transmission path corresponding to each directed edge; Based on the network connection status, the transmission cost, and the historical reliability score, the target transmission path corresponding to each target platform is determined. The encrypted data packet is distributed to the corresponding target platform through the target transmission path.

7. The method according to claim 6, characterized in that, The process of determining the target transmission path corresponding to each target platform based on the network connection status, transmission cost, and historical reliability score includes: The path score for each transmission path is calculated using the following formula, and the target transmission path is determined based on the path score. Among them, S ij For the path score of the transmission path ij from platform i to platform j, D ij D represents the network connection status corresponding to transmission path ij. max C is the maximum allowable network latency. ij C represents the transmission cost corresponding to transmission path ij. max To the maximum allowed transmission cost, R ij The reliability history score for transmission path ij is given, where α1, α2, and α3 are balance coefficients, and the sum of α1, α2, and α3 is 1.

8. A building materials supply chain data synchronization system, characterized in that, The system includes: The data acquisition module is used to collect real-time data from the SAAS platform, the local ERP system and third-party data sources through a multi-protocol adapter. The real-time data includes building material inventory, logistics vehicle coordinates, order status changes and changes in enterprise business registration information. The data conversion module is used to dynamically convert the collected real-time data to generate standardized data packets; the dynamic conversion includes field mapping, unit standardization, and data traceability tag addition; The data encryption module is used to select an encryption strategy according to the data sensitivity level and encrypt the standardized data packet to obtain an encrypted data packet; The data synchronization module is used to construct a synchronization topology network based on the data dependencies between multiple platforms, and to distribute the encrypted data packets to the target platform for data synchronization based on the synchronization topology network.

9. An electronic device, characterized in that, It includes a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; Memory, used to store computer programs; When a processor executes a program stored in memory, it implements the steps of the building materials supply chain data synchronization method according to any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the building materials supply chain data synchronization method as described in any one of claims 1-7.

Images