A logistics data processing burden reduction method based on end-cloud collaborative computing

Abstract

The application relates to the technical field of data processing load reduction, and particularly discloses a logistics data processing load reduction method based on end-cloud collaborative calculation, which comprises the following steps: step S1: receiving waybill state information on the end side, aggregating data in the same preset time sequence window into a window message set, carrying out forward checking on each two adjacent waybill state information after time sorting, and judging whether the adjacent state information belongs to legal migration; step S2: if all adjacent states in the set are legal migration, the state is determined as a forward state link, valid incremental messages are screened out, the rest of the data is discarded, and the valid incremental messages are stored on the end side; step S3: if there is any one group of illegal migration, all the messages are marked as abnormal retention messages and stored on the end side; and step S4: the valid incremental messages and the abnormal retention messages are uploaded to the cloud end together, and the waybill state is updated.

Description

Technical Field

[0001] This invention relates to the field of data processing burden reduction technology, specifically to a method for reducing the burden of logistics data processing based on edge-cloud collaborative computing. Background Technology

[0002] Currently, the digital operation and maintenance system of the logistics industry has generally adopted a data processing model of terminal collection and centralized cloud processing. Through the terminal, massive amounts of logistics data are collected in real time to provide data support for logistics.

[0003] Existing technologies mostly adopt a processing method of full reporting from terminals and unified parsing and storage in the cloud, without setting up a refined data identification and filtering mechanism. It can comprehensively retain data from the entire logistics operation process, ensure the integrity and traceability of logistics business data, and is widely used in various logistics scenarios.

[0004] However, existing full-data processing methods have significant technical flaws. Logistics operations generate massive amounts of redundant data, including frequently reported duplicate coordinate points from GPS, invalid messages with unchanged operational status, and repeatedly pushed waybill change messages from the platform, significantly increasing the load on data transmission, storage, and cloud computing power. Furthermore, current technology cannot accurately distinguish between redundant data and valid incremental data. Many seemingly repetitive messages and trajectory data often contain subtle changes in operational and location status. Using simple, crude methods of data discarding and filtering can easily lead to the loss of critical business details, resulting in errors in waybill status assessment, distorted trajectory tracking, and difficulty in defining logistics responsibility. Summary of the Invention

[0005] The purpose of this invention is to provide a method for reducing the burden of logistics data processing based on edge-cloud collaborative computing, and to solve the following technical problems.

[0006] The objective of this invention can be achieved through the following technical solutions: A method for reducing the burden of logistics data processing based on edge-cloud collaborative computing includes the following steps: Step S1: The end device receives the waybill status information and aggregates the waybill status information whose reception time falls within the same preset time window into a window message set; sorts the waybill status information in the window message set in chronological order, and performs a positive verification on each pair of adjacent waybill status information to determine whether the two waybill status information are valid migrations. Step S2: If all two adjacent waybill status information in the window message set are valid migrations, then all waybill status information in the window message set is determined to be a forward status link; the valid incremental message in the forward status link is determined, and all waybill status information in the window message set except for the valid incremental message is discarded, while the valid incremental message is retained in the end-side device; Step S3: If any two adjacent waybill status information entries in the window message set are illegally migrated, then all waybill status information entries in the window message set are marked as abnormal retention messages and retained in the end-side device. Step S4: The terminal device uploads the valid incremental message and the abnormal retention message to the cloud, and updates the status of the waybill.

[0007] As a further aspect of the present invention: the waybill status information specifically includes: The waybill status information consists of several fields, including a waybill identifier, a cloud status identifier, and a status change timestamp. The waybill identifier is a unique waybill number for the waybill status information. The waybill status identifies the logistics node status of the waybill, including "order placed," "picked up," "in transit," "delivered," "signed for," and "abnormal." Each logistics node status also includes several sub-status, which are several sibling statuses within the same logistics node status. The status change timestamp is the actual time the waybill status information corresponds to.

[0008] As a further aspect of the present invention: the setting process of the preset timing window includes: setting the minimum state maintenance time required for the normal flow of the waybill status, and setting the duration of the preset timing window to the minimum state maintenance time.

[0009] As a further aspect of the present invention: the process of performing forward verification on each pair of adjacent waybill status information includes: Set a one-way flow sequence for the waybill status, which is: ordered, picked up, in transit, being delivered, and signed for. Set flow rules for the one-way flow sequence, which include prohibiting any logistics node status from changing backward to the upstream logistics node status in the one-way flow sequence, and allowing each sub-status to change back and forth within the same logistics node status. A preset status transition permission lookup table and priority weight table are used. For two adjacent waybill status information, the waybill status information with the earlier status change timestamp is recorded as the currently stored message, and the waybill status information with the later status change timestamp is recorded as the newly arrived message. Based on the priority weight table, the waybill status of the currently stored message and the newly arrived message are compared. If the priority of the logistics node status of the newly arrived message is higher than that of the logistics node status of the currently stored message, then the two waybill status information are determined to be a valid migration.

[0010] As a further aspect of the present invention, the process of performing positive verification on each pair of adjacent waybill status information further includes determining that if the priority of the logistics node status of the newly arrived message is lower than the priority of the logistics node status of the currently stored message, the newly arrived message is an out-of-order old message.

[0011] As a further aspect of the present invention, the process of performing forward verification on each pair of adjacent waybill status information also includes: If the priority of the logistics node status of the newly arrived message is the same as the priority of the logistics node status of the currently stored message, then a determination is made based on the status transition permission lookup table. When the change of the sub-state is a back-and-forth change within the same logistics node status, the newly arrived message is determined to be redundant at the same level. When the change of the sub-state is not a back-and-forth change within the same logistics node status, the two waybill status information are determined to be illegally migrated.

[0012] As a further aspect of the present invention: the preset process for the state transition permission lookup table and priority weight table includes: The status transition permission lookup table is a two-dimensional array, with the current logistics node status of the stored message as the horizontal axis and the logistics node status of the newly arrived message as the vertical axis. Each element in the status transition permission lookup table is pre-marked as one of positive update, same-level redundancy, or illegal migration. In the priority weight table, the highest priority is for signed-for items, followed by those in delivery, in transit, picked up, and ordered.

[0013] As a further aspect of the present invention: the process of determining the valid incremental message in the forward state link includes: When the window message set contains several waybill status messages with the same logistics node status, the waybill status message with the earliest status change timestamp is taken as the full baseline message. For several waybill status messages with status change timestamps later than the full baseline message, the waybill status messages are compared with the full baseline message, and the fields in the waybill status messages that differ from the full baseline message are extracted and recorded as placeholder records. If no changed fields exist, the status change timestamp of the waybill status message is recorded as a placeholder record. The full baseline message and all placeholder records are recorded as valid incremental messages within the preset time sequence window.

[0014] The beneficial effects of this invention are: This invention achieves accurate identification and burden reduction of redundant logistics data through a short-time window aggregation and positive status verification mechanism in a cloud-edge collaborative manner, without relying on a global deduplication fingerprint database. For the large number of duplicate waybill status change messages generated by message middleware retries and business interface re-pushes, it leverages the business principle that waybill status only flows in a positive direction. On the edge, it aggregates the same waybill message within a short time window and performs positive verification using a two-level structure of logistics node status and sub-status, along with a status flow permission lookup table. This filters out duplicate pushes and duplicate intermediate status messages while fully preserving genuine status changes and anomaly rollbacks. The system tracks and avoids the loss of business information due to brute-force deduplication. For multiple messages in the same logistics node status within a window, a storage mode of full data for the first message plus differential data for subsequent messages is adopted, retaining only changed fields and timestamps. This not only removes redundant duplicate fields but also completely preserves the business change traces in the same logistics node status, solving the problem of key information updates in the same status being easily filtered out. The data processed on the client side only contains valid incremental messages and a small number of abnormal retained messages, significantly reducing the amount of data uploaded to the cloud, alleviating the pressure on cloud storage, computing, and network transmission, while improving the accuracy of logistics status tracking and the efficiency of anomaly investigation. Attached Figure Description

[0015] The invention will now be further described with reference to the accompanying drawings.

[0016] Figure 1 This is a schematic diagram illustrating the steps of a logistics data processing burden reduction method based on edge-cloud collaborative computing according to the present invention. Figure 2 This is a flowchart illustrating a method for reducing the burden of logistics data processing based on edge-cloud collaborative computing according to the present invention. Detailed Implementation

[0017] 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, and 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.

[0018] Please see Figure 1 As shown, this invention is a method for reducing the burden of logistics data processing based on edge-cloud collaborative computing, including the following steps: Step S1: The end device receives the waybill status information and aggregates the waybill status information whose reception time falls within the same preset time window into a window message set; sorts the waybill status information in the window message set in chronological order, and performs a positive verification on each pair of adjacent waybill status information to determine whether the two waybill status information are valid migrations. Specifically, the edge devices are deployed in the field data collection environment at each node of the logistics operation, connecting to various operation data collection terminals and business interfaces to obtain waybill status information in real time. According to preset time-series window configuration rules, the edge devices aggregate the status information of the same waybill within the same time-series window based on the message reception time, forming a corresponding window message set. After aggregation, the edge devices sort all information in the window message set according to the status change timestamp in each waybill status message, ensuring the message sequence corresponds to the actual order of business occurrence. The edge devices sequentially perform forward verification on each pair of adjacent waybill status messages, judging whether the transition between adjacent states conforms to legal flow logic based on pre-configured status transition rules and judgment criteria, thus completing the initial compliance screening of messages within the window. In a preferred embodiment of the present invention, the waybill status information specifically includes: The waybill status information consists of several fields, including a waybill identifier, a cloud status identifier, and a status change timestamp. The waybill identifier is a unique waybill number for the waybill status information. The waybill status identifies the logistics node status of the waybill, including "order placed," "picked up," "in transit," "delivered," "signed for," and "abnormal." Each logistics node status also includes several sub-status, which are several sibling statuses within the same logistics node status. The status change timestamp is the actual time the corresponding waybill status information occurred. In a preferred embodiment of the present invention, the setting process of the preset timing window includes: setting the minimum state maintenance time required for the normal flow of the waybill status; and setting the duration of the preset timing window to the minimum state maintenance time. In a preferred embodiment of the present invention, the process of performing forward verification on each pair of adjacent waybill status information includes: Set a one-way flow sequence for the waybill status, which is: ordered, picked up, in transit, being delivered, and signed for. Set flow rules for the one-way flow sequence, which include prohibiting any logistics node status from changing backward to the upstream logistics node status in the one-way flow sequence, and allowing each sub-status to change back and forth within the same logistics node status. A preset status transition permission lookup table and priority weight table are used. For two adjacent waybill status information, the waybill status information with the earlier status change timestamp is recorded as the currently stored message, and the waybill status information with the later status change timestamp is recorded as the newly arrived message. Based on the priority weight table, the waybill status of the currently stored message and the newly arrived message are compared. If the priority of the logistics node status of the newly arrived message is higher than that of the logistics node status of the currently stored message, then the two waybill status information are determined to be a valid migration. The process of performing positive verification on each pair of adjacent waybill status information also includes determining that if the priority of the logistics node status of the newly arrived message is lower than the priority of the logistics node status of the currently stored message, the newly arrived message is an out-of-order old message. The process of performing forward verification on each pair of adjacent waybill status information also includes: If the priority of the logistics node status of the newly arrived message is the same as the priority of the logistics node status of the currently stored message, then the determination is made based on the status flow permission lookup table. When the change of the sub-state is a back-and-forth change within the same logistics node status, the newly arrived message is determined to be redundant at the same level. When the change of the sub-state is not a back-and-forth change within the same logistics node status, the two waybill status information are determined to be illegal migrations. The preset process for the state transition permission lookup table and priority weight table includes: The status transition permission lookup table is a two-dimensional array, with the current logistics node status of the stored message as the horizontal axis and the logistics node status of the newly arrived message as the vertical axis. Each element in the status transition permission lookup table is pre-marked as one of positive update, same-level redundancy, or illegal migration. In the priority weight table, the highest priority is for signed-for items, followed by those in delivery, in transit, picked up, and ordered. Step S2: If all two adjacent waybill status information in the window message set are valid migrations, then all waybill status information in the window message set is determined to be a forward status link; the valid incremental message in the forward status link is determined, and all waybill status information in the window message set except for the valid incremental message is discarded, while the valid incremental message is retained in the end-side device; Specifically, when all adjacent waybill status information within the window message set is determined to be a legitimate migration after positive verification, the end device will determine the entire window message set as a positive status link, confirming that the waybill status flow within the preset time window conforms to the normal business flow pattern. The edge device performs incremental extraction processing on the waybill status information in the forward state link, filters and determines the valid incremental messages, and discards the remaining waybill status information in the window message set that does not have incremental value, retaining only the valid incremental messages locally on the edge. For several waybill status messages in the same logistics node state, a base message combined with differential placeholder records is used for storage, which fully retains the time node and field difference information of the status change, and eliminates data redundancy caused by duplicate fields. Under the premise of fully retaining the business status change traces, the amount of redundant data in the window is greatly compressed, which reduces the local storage overhead on the edge and the scale of data uploaded to the cloud. In a preferred embodiment of the present invention, the process of determining the valid incremental message in the forward state link includes: When the window message set contains several waybill status messages with the same logistics node status, the waybill status message with the earliest status change timestamp is taken as the full baseline message. For several waybill status messages with status change timestamps later than the full baseline message, the waybill status messages are compared with the full baseline message, and the fields in the waybill status messages that differ from the full baseline message are extracted and recorded as placeholder records. If no changed fields exist, the status change timestamp of the waybill status message is recorded as a placeholder record. The full baseline message and all placeholder records are recorded as valid incremental messages within the preset time sequence window. Step S3: If any two adjacent waybill status information entries in the window message set are illegally migrated, then all waybill status information entries in the window message set are marked as abnormal retention messages and retained in the end-side device. Specifically, when any pair of adjacent waybill status information in the window message set is determined to be illegally migrated, the terminal device does not perform deletion or compression processing on the messages in that window. Instead, it marks all waybill status information in the window message set as abnormal retention messages and saves them completely in the local storage medium on the terminal. For messages suspected of abnormal transfer, all original data and timing information are retained to avoid the loss of abnormal business leads due to data reduction and filtering. Step S4: The terminal device uploads the valid incremental message and the abnormal retention message to the cloud, and updates the status of the waybill; Specifically, after completing the data processing flow on the edge, the edge device uploads the generated valid incremental messages and abnormal retention messages to the cloud through the edge-cloud communication link; after receiving the data, the cloud parses and synchronizes the valid incremental messages to complete the status update of the corresponding waybill; and performs business verification and problem location for the abnormal retention messages. When data is uploaded to the cloud for processing, the end-side device adopts a hierarchical transmission strategy for valid incremental messages and abnormal retained messages. Valid incremental messages are uploaded first through the real-time transmission channel to ensure the timeliness of waybill status updates. Abnormal retained messages are uploaded through a reliable transmission channel, and network idle time periods are determined and uploaded in an orderly manner during the network idle time periods to avoid abnormal data crowding out the main service transmission bandwidth. After receiving the data, the cloud performs a routing process. Valid incremental messages are directly synchronized to the waybill logistics node status database to complete the normal update of the waybill status. Abnormal retained messages are transferred to an independent abnormal data verification queue without interfering with the status flow of the main business process. The cloud-based abnormal verification module combines the full-link waybill data and cross-node business information to perform a second review of the abnormal migration. Data that is determined to be out of order or has a verification error is updated to complete the status and the abnormal mark is removed. This invention utilizes an edge-cloud collaborative processing architecture to move most data verification and load reduction tasks to the edge, allowing the cloud to process only compressed incremental data and a small amount of abnormal data. This significantly reduces the network transmission pressure, data storage pressure, and computational processing pressure on the cloud, while ensuring the accuracy of logistics waybill status updates and the efficiency of response to abnormal events.

[0019] The foregoing has provided a detailed description of one embodiment of the present invention, but this description is merely a preferred embodiment and should not be construed as limiting the scope of the invention. All equivalent variations and modifications made within the scope of the present invention should still fall within the scope of the present invention.

Claims

1. A method for reducing the burden of logistics data processing based on edge-cloud collaborative computing, characterized in that, Includes the following steps: Step S1: The end device receives the waybill status information and aggregates the waybill status information whose reception time falls within the same preset time window into a window message set; The status information of each waybill in the window message set is sorted in chronological order, and a positive check is performed on each pair of adjacent waybill status information to determine whether the two waybill status information are valid migrations. Step S2: If all two adjacent waybill status information in the window message set are valid migrations, then all waybill status information in the window message set is determined to be a forward status link; the valid incremental message in the forward status link is determined, and all waybill status information in the window message set except for the valid incremental message is discarded, while the valid incremental message is retained in the end-side device; Step S3: If any two adjacent waybill status information entries in the window message set are illegally migrated, then all waybill status information entries in the window message set are marked as abnormal retention messages and retained in the end-side device. Step S4: The terminal device uploads the valid incremental message and the abnormal retention message to the cloud, and updates the status of the waybill.

2. The method for reducing the burden of logistics data processing based on edge-cloud collaborative computing according to claim 1, characterized in that, In step S1, the waybill status information specifically includes: The waybill status information consists of several fields, including a waybill identifier, a cloud status identifier, and a status change timestamp. The waybill identifier is a unique waybill number for the waybill status information. The waybill status identifies the logistics node status of the waybill, including "order placed," "picked up," "in transit," "delivered," "signed for," and "abnormal." Each logistics node status also includes several sub-status, which are several sibling statuses within the same logistics node status. The status change timestamp is the actual time the waybill status information corresponds to.

3. The method for reducing the burden of logistics data processing based on edge-cloud collaborative computing according to claim 1, characterized in that, In step S1, the process of setting the preset timing window includes setting the minimum state maintenance time required for the normal flow of the waybill status, and setting the duration of the preset timing window to the minimum state maintenance time.

4. The method for reducing the burden of logistics data processing based on edge-cloud collaborative computing according to claim 2, characterized in that, In step S1, the process of performing a forward verification on each pair of adjacent waybill status information includes: Set a one-way flow sequence for the waybill status, which is: ordered, picked up, in transit, being delivered, and signed for. Set flow rules for the one-way flow sequence, which include prohibiting any logistics node status from changing backward to the upstream logistics node status in the one-way flow sequence, and allowing each sub-status to change back and forth within the same logistics node status. A preset status transition permission lookup table and priority weight table are used. For two adjacent waybill status information, the waybill status information with the earlier status change timestamp is recorded as the currently stored message, and the waybill status information with the later status change timestamp is recorded as the newly arrived message. Based on the priority weight table, the waybill status of the currently stored message and the newly arrived message are compared. If the priority of the logistics node status of the newly arrived message is higher than that of the logistics node status of the currently stored message, then the two waybill status information are determined to be a valid migration.

5. The method for reducing the burden of logistics data processing based on edge-cloud collaborative computing according to claim 4, characterized in that, In step S1, the process of performing positive verification on each pair of adjacent waybill status information also includes determining that if the priority of the logistics node status of the newly arrived message is lower than the priority of the logistics node status of the currently stored message, the newly arrived message is an out-of-order old message.

6. The method for reducing the burden of logistics data processing based on edge-cloud collaborative computing according to claim 4, characterized in that, In step S1, the process of performing forward verification on each pair of adjacent waybill status information also includes: If the priority of the logistics node status of the newly arrived message is the same as the priority of the logistics node status of the currently stored message, then a determination is made based on the status transition permission lookup table. When the change of the sub-state is a back-and-forth change within the same logistics node status, the newly arrived message is determined to be redundant at the same level. When the change of the sub-state is not a back-and-forth change within the same logistics node status, the two waybill status information are determined to be illegally migrated.

7. The method for reducing the burden of logistics data processing based on edge-cloud collaborative computing according to claim 4, characterized in that, In step S1, the preset process for the state transition permission lookup table and priority weight table includes: The status transition permission lookup table is a two-dimensional array, with the current logistics node status of the stored message as the horizontal axis and the logistics node status of the newly arrived message as the vertical axis. Each element in the status transition permission lookup table is pre-marked as one of positive update, same-level redundancy, or illegal migration. In the priority weight table, the highest priority is for signed-for items, followed by those in delivery, in transit, picked up, and ordered.

8. The method for reducing the burden of logistics data processing based on edge-cloud collaborative computing according to claim 1, characterized in that, In step S2, the process of determining the valid incremental message in the forward state link includes: When the window message set contains several waybill status messages with the same logistics node status, the waybill status message with the earliest status change timestamp is taken as the full baseline message. For several waybill status messages with status change timestamps later than the full baseline message, the waybill status messages are compared with the full baseline message, and the fields in the waybill status messages that differ from the full baseline message are extracted and recorded as placeholder records. If no changed fields exist, the status change timestamp of the waybill status message is recorded as a placeholder record. The full baseline message and all placeholder records are recorded as valid incremental messages within the preset time sequence window.

Images