Logistics information processing method and device

Abstract

The application discloses a kind of logistics information processing method and device, it is related to wisdom logistics technical field.The specific embodiment of the method includes: receiving the logistics parameter report information sent by logistics operation client;Logistics parameter report information includes: pre-acquired, the measured data of the logistics parameter of goods in current logistics link, the record data of the logistics parameter of goods in historical logistics link, the responsibility subject associated with record data and responsibility type;There is deviation between measured data and record data;Determine the responsibility type corresponding to the mapping relationship between the responsibility type and the action of determining responsibility in advance configured in logistics parameter report information, obtain the result of determining responsibility using the action of determining responsibility determined and logistics parameter report information;In response to the result of determining responsibility indicates that responsibility subject is responsible, generate logistics expense recovery task and send to the terminal of responsibility subject.This embodiment can form reusable logistics parameter report system.

Description

Technical Field

[0001] This invention relates to the field of smart logistics technology, and in particular to a logistics information processing method and apparatus. Background Technology

[0002] In logistics processes such as pickup, sorting, and transportation, there are instances of weight theft and under-weighting of goods. This occurs when logistics operators, seeking undue profit or due to measurement errors, record logistics parameters such as weight and volume that are lower than the actual values ​​(or higher if measurement errors occur), resulting in losses for the logistics platform. Currently, logistics platforms have established reporting systems for logistics parameters to address this issue. If operators at any stage of the logistics process discover significant deviations in the logistics parameter values ​​of a particular item throughout its historical logistics history, they can file a report through the system. In practice, however, reporting systems are typically customized for specific scenarios, such as types of liability (e.g., exceeding weight or volume limits) and / or logistics types (e.g., cold chain express, fresh produce express). This approach suffers from poor reusability, low development efficiency, and difficulty in maintenance. Summary of the Invention

[0003] In view of this, embodiments of the present invention provide a logistics information processing method and apparatus, which can form a reusable logistics parameter reporting system.

[0004] To achieve the above objectives, according to one aspect of the present invention, a logistics information processing method is provided.

[0005] The logistics information processing method of this invention includes: receiving logistics parameter reporting information sent by a logistics operation client; wherein the logistics parameter reporting information includes: pre-collected measured data of logistics parameters of goods in the current logistics stage, recorded data of logistics parameters of goods in historical logistics stages, the responsible entity and responsibility type associated with the recorded data; there is a deviation between the measured data and the recorded data; based on a pre-configured mapping relationship between responsibility type and judgment action, determining the judgment action corresponding to the responsibility type in the logistics parameter reporting information, obtaining the judgment result using the determined judgment action and the logistics parameter reporting information; in response to the judgment result indicating that the responsible entity is liable, generating a logistics cost collection task and sending it to the terminal of the responsible entity.

[0006] Optionally, the method further includes: before receiving the logistics parameter reporting information sent by the logistics operation client, receiving a logistics reporting request for goods sent by the logistics operation client; obtaining the original data of the goods' logistics parameters and the goods' logistics type from an external warehouse management system; obtaining the excess judgment rule corresponding to the goods' logistics type based on a pre-configured mapping relationship between logistics type and excess judgment rule; obtaining the recorded data of the goods' logistics parameters at any historical logistics stage; determining the excess judgment result using the obtained excess judgment rule, the recorded data of the historical logistics stage, and the original data; and returning a reporting success notification to the logistics operation client in response to the excess judgment result indicating a deviation between the recorded data of the historical logistics stage and the original data; the logistics parameter reporting information is generated and sent by the logistics operation client after receiving the reporting success notification.

[0007] Optionally, the method further includes: before returning a successful report notification to the logistics operation client, determining the responsible party and the type of responsibility in the historical logistics process to which the recorded data that deviates from the original data belongs, and including the determined responsible party, type of responsibility, recorded data, and original data in the successful report notification.

[0008] Optionally, the logistics parameters corresponding to the pre-collected measured data include weight parameters and volume parameters; the method further includes: before acquiring the raw data, determining the bubble coefficient corresponding to the logistics type of the goods based on a pre-configured mapping relationship between logistics type and bubble coefficient, and using the determined bubble coefficient to convert the measured data of volume parameters into volumetric weight data; if the volumetric weight data is greater than the measured data of weight parameters, determining the volume parameters as target parameters; if the volumetric weight data is not greater than the measured data of weight parameters, determining the weight parameters as target parameters; and the logistics parameters corresponding to the raw data, the logistics parameters corresponding to the recorded data processed using the exceedance judgment rules, and the logistics parameters in the logistics parameter reporting request are the target parameters.

[0009] Optionally, the logistics parameter reporting information further includes: an image of the goods in the current logistics process; the liability assessment action includes: direct third-party liability assessment, or a combination of mutual liability assessment and third-party liability assessment; and obtaining a liability assessment result using the determined liability assessment action and the logistics parameter reporting information, including: in the case of direct third-party liability assessment, generating a liability assessment request and sending it to an external liability assessment system to obtain a liability assessment result in response to the request; wherein, the liability assessment request includes: logistics parameter reporting information and an image; in the case of mutual liability assessment and third-party liability assessment, interacting with the terminal of the responsible party to obtain the mutual liability assessment result; if the mutual liability assessment result indicates that the responsible party confirms liability, then generating a corresponding liability assessment result; if the mutual liability assessment result indicates that the responsible party confirms no liability, then generating a liability assessment request and sending it to an external liability assessment system to obtain a liability assessment result.

[0010] Optionally, the method further includes: after determining the responsible party in the historical logistics link to which the recorded data that deviates from the original data belongs, identifying the target of recovery in that historical logistics link, and including the target of recovery in the successful reporting notification; and the logistics cost recovery task includes: the logistics cost to be recovered, the payment path, and the target of recovery.

[0011] Optionally, the method further includes: updating logistics parameter data and billing data in a preset database when the logistics cost recovery task is successfully executed; sending reward operation information to the logistics operation client and penalty operation information to the terminal of the responsible entity.

[0012] Optionally, the current logistics stage is: sorting, transportation, or delivery; if the current logistics stage is sorting, the historical logistics stage is pickup or transportation; if the current logistics stage is transportation, the historical logistics stage is pickup or sorting; if the current logistics stage is delivery, the historical logistics stage is pickup, sorting, or transportation.

[0013] To achieve the above objectives, according to another aspect of the present invention, a logistics information processing device is provided.

[0014] The logistics information processing device provided in the embodiments of the present invention may include: a receiving unit, a processing unit, and a sending unit.

[0015] The receiving unit can be used to receive logistics parameter reporting information sent by the logistics operation client. This information includes: pre-collected measured data of logistics parameters in the current logistics stage, recorded data of logistics parameters in historical logistics stages, the responsible entity and type of responsibility associated with the recorded data, and discrepancies between the measured and recorded data. The processing unit can determine the corresponding judgment action for the responsibility type in the logistics parameter reporting information based on a pre-configured mapping relationship between responsibility types and judgment actions, and obtain the judgment result using the determined judgment action and the logistics parameter reporting information. The sending unit can respond to the judgment result indicating that the responsible entity is liable, generate a logistics cost recovery task, and send it to the responsible entity's terminal.

[0016] Optionally, the logistics information processing device further includes a pre-processing unit, configured to: receive a logistics reporting request for goods sent by the logistics operation client before receiving the logistics parameter reporting information sent by the logistics operation client; obtain the original data of the logistics parameters of the goods and the logistics type of the goods from an external warehouse management system; obtain the over-limit judgment rule corresponding to the logistics type of the goods based on a pre-configured mapping relationship between logistics type and over-limit judgment rule; obtain the recorded data of logistics parameters of the goods at any historical logistics link; determine the over-limit judgment result using the obtained over-limit judgment rule, the recorded data of the historical logistics link, and the original data; and, in response to the over-limit judgment result indicating a deviation between the recorded data of the historical logistics link and the original data, return a reporting success notification to the logistics operation client; the logistics parameter reporting information is generated and sent by the logistics operation client after receiving the reporting success notification.

[0017] Optionally, the pre-processing unit may be further used to: determine the responsible party and the type of responsibility in the historical logistics process to which the recorded data that deviates from the original data belongs before returning a successful report notification to the logistics operation client, and include the determined responsible party, type of responsibility, recorded data and original data in the successful report notification.

[0018] Optionally, the logistics parameters corresponding to the pre-collected measured data include weight parameters and volume parameters. The pre-processing unit can be further used to: determine the bubble coefficient corresponding to the logistics type of the goods based on the pre-configured mapping relationship between logistics type and bubble coefficient before acquiring the original data; convert the measured data of volume parameters into volumetric weight data using the determined bubble coefficient; determine the volume parameter as the target parameter if the volumetric weight data is greater than the measured data of weight parameters; determine the weight parameter as the target parameter if the volumetric weight data is not greater than the measured data of weight parameters; and use the logistics parameters corresponding to the original data, the logistics parameters corresponding to the recorded data processed by the exceedance judgment rules, and the logistics parameters in the logistics parameter reporting request as target parameters.

[0019] Optionally, the logistics parameter reporting information further includes: an image of the goods in the current logistics process; the liability assessment action includes: direct third-party liability assessment, or a combination of mutual liability assessment and third-party liability assessment; and the processing unit can be further configured to: generate a liability assessment request and send it to an external liability assessment system when the determined action is direct third-party liability assessment, in order to obtain a liability assessment result in response to the liability assessment request; wherein, the liability assessment request includes: logistics parameter reporting information and an image; when the determined action is a combination of mutual liability assessment and third-party liability assessment, interact with the terminal of the responsible party to obtain the mutual liability assessment result; if the mutual liability assessment result indicates that the responsible party confirms that it is liable, then generate a corresponding liability assessment result; if the mutual liability assessment result indicates that the responsible party confirms that it is not liable, then generate a liability assessment request and send it to an external liability assessment system to obtain a liability assessment result.

[0020] Optionally, the pre-processing unit can be further used to: after determining the responsible party in the historical logistics link to which the recorded data that deviates from the original data belongs, determine the target of recovery in the historical logistics link and include the target of recovery in the successful report notification; and the logistics cost recovery task includes: logistics costs to be recovered, payment path and target of recovery.

[0021] Optionally, the sending unit interacts with external systems to: update logistics parameter data and billing data in a preset database when the logistics cost collection task is successfully executed; send reward operation information to the logistics operation client; and send penalty operation information to the terminal of the responsible entity.

[0022] Optionally, the current logistics stage is: sorting, transportation, or delivery; if the current logistics stage is sorting, the historical logistics stage is pickup or transportation; if the current logistics stage is transportation, the historical logistics stage is pickup or sorting; if the current logistics stage is delivery, the historical logistics stage is pickup, sorting, or transportation.

[0023] To achieve the above objectives, according to another aspect of the present invention, an electronic device is provided.

[0024] An electronic device according to the present invention includes: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the logistics information processing method provided by the present invention.

[0025] To achieve the above objectives, according to another aspect of the present invention, a computer-readable storage medium is provided.

[0026] The present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the logistics information processing method provided by the present invention.

[0027] To achieve the above objectives, according to another aspect of the present invention, a computer program product is provided.

[0028] One computer program product of the present invention includes a computer program that, when executed by a processor, implements the logistics information processing method provided by the present invention.

[0029] According to the technical solution of the present invention, the embodiments described above have the following advantages or beneficial effects:

[0030] This paper presents a universal logistics parameter reporting solution that can be reused across various logistics stages. Upon receiving a logistics parameter reporting message from a logistics operation client, the reporting system determines the corresponding action based on a pre-configured mapping between responsibility types and judgment actions. Using this determined action and the reported logistics parameter information, the system obtains a judgment result. If the judgment result indicates that the responsible party is liable, the reporting system generates a logistics cost recovery task and sends it to the responsible party's terminal. This solution achieves an automated and efficient reporting process, reusable in various logistics stages and application scenarios with different responsibility types. Each logistics stage can integrate the reporting system without modification or with minor modifications, thereby improving the development efficiency of the reporting system across multiple scenarios, reducing repetitive work during development, enhancing system maintainability, and ultimately contributing to improved system stability, overall logistics efficiency, and service quality. As an optional solution, the logistics system can also implement reusable logistics parameter over-limit judgment logic or volume and weight conversion logic by pre-configuring the mapping relationship between logistics type and over-limit judgment rules or the mapping relationship between logistics type and bubble coefficient, thereby further improving the reusability and maintainability of the reporting system.

[0031] The further effects of the aforementioned unconventional alternative methods will be explained below in conjunction with specific implementation methods. Attached Figure Description

[0032] The accompanying drawings are provided to better understand the invention and are not intended to unduly limit the scope of the invention. Wherein:

[0033] Figure 1 This is a schematic diagram of the main steps of the logistics information processing method in an embodiment of the present invention;

[0034] Figure 2 This is a schematic diagram illustrating the specific execution steps of the logistics information processing method in this embodiment of the invention;

[0035] Figure 3 This is a schematic diagram of the system architecture of the logistics information processing method in an embodiment of the present invention;

[0036] Figure 4 This is a schematic diagram of the components of the logistics information processing device in an embodiment of the present invention;

[0037] Figure 5 This is an exemplary system architecture diagram that can be applied thereto according to embodiments of the present invention;

[0038] Figure 6 This is a schematic diagram of the electronic device structure used to implement the logistics information processing method in the embodiments of the present invention. Detailed Implementation

[0039] The following description, in conjunction with the accompanying drawings, illustrates exemplary embodiments of the present invention, including various details to aid understanding. These details should be considered merely exemplary. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the invention. Similarly, for clarity and brevity, descriptions of well-known functions and structures are omitted in the following description.

[0040] It should be noted that, unless otherwise specified, the embodiments of the present invention and the technical features thereof can be combined with each other.

[0041] Figure 1 This is a schematic diagram of the main steps of the logistics information processing method in an embodiment of the present invention.

[0042] like Figure 1 As shown, the logistics information processing method of this invention can be executed by a reporting system, and the specific execution steps are as follows:

[0043] Step S101: Receive logistics parameter reporting information sent by the logistics operation client. In practical applications, operators in logistics links such as transportation, sorting, and delivery can send logistics parameter reporting information to the reporting system through the logistics operation client to report inaccurate values ​​of logistics parameters such as volume and weight. The reporting system can receive the above logistics parameter reporting information and perform subsequent processing. In one embodiment, the logistics links can be divided into the pickup link, sorting link, transportation link, and delivery link. The pickup link can include user order placement and goods pickup. The sorting link refers to the distribution of goods in the sorting center to determine the next destination (e.g., delivery station). The transportation link executes the transportation of goods between different locations. The delivery link refers to the delivery of goods to the delivery address through collection and distribution stations and delivery personnel. In specific scenarios, the logistics parameter reporting information can include: pre-collected measured data of logistics parameters of goods in the current logistics link, recorded data of logistics parameters of goods in historical logistics links, the responsible entity and type of responsibility associated with the recorded data; in particular, there is a discrepancy between the above measured data and recorded data.

[0044] Step S102: Based on the pre-configured mapping relationship between responsibility types and judgment actions, determine the judgment action corresponding to the responsibility type in the reported logistics parameter information. Use the determined judgment action and the reported logistics parameter information to obtain the judgment result. In this step, the reporting system determines the judgment action corresponding to the current responsibility type based on the pre-configured relationship between responsibility types and judgment actions. Executing the above judgment action on the reported logistics parameter information yields the judgment result. This step is used to determine whether the responsible party bears responsibility for the inaccurate logistics parameter values ​​to facilitate subsequent processing.

[0045] Step S103: In response to the judgment indicating that the responsible party is liable, a logistics cost recovery task is generated and sent to the responsible party's terminal. This step generates a logistics cost recovery task and sends it to the responsible party when the responsible party is liable, thereby recovering the previously lost logistics costs.

[0046] Through the above steps, an efficient reporting process can be achieved, which automates the receipt of reporting information, determination of responsibility, and recovery of logistics costs. Based on configuration, it can be reused in various logistics links and application scenarios with different types of responsibility. Each logistics link can be connected to the reporting system without modification or with minor modifications to the reporting system, thereby improving the development efficiency of the reporting system in multiple scenarios.

[0047] Figure 2 This is a schematic diagram illustrating the specific execution steps of the logistics information processing method in this embodiment of the invention. Figure 3 This is a schematic diagram of the system architecture of the logistics information processing method in an embodiment of the present invention. See also: Figure 2 , 3 .

[0048] The reporting system can interact with the access layer, receiving and processing reporting-related information sent by the access layer. The processing results can be output to the application layer for subsequent logic execution. The access layer may include logistics operation clients installed on the terminals of logistics operators in the sorting, transportation, and delivery stages. The application layer may include these various logistics operation clients, and may also include processes such as waybill updates, billing updates, big data processing, and reward / penalty processing. The reporting system may include a unified rule service for interacting with the access layer to confirm the initial reporting information. The unified rule service includes a weight and volume verification service for obtaining raw logistics parameter data (such as volume and weight at the time of outbound shipment), an excess judgment service for performing excess judgment, and a responsibility determination service for identifying the responsible party. The reporting system also includes the main processes such as message queue (MQ) input, data storage, action judgment, freight collection, and message queue output. The following is combined with... Figure 2 and Figure 3 Please provide an explanation.

[0049] Step S201: The reporting system receives logistics reporting requests. In this step, if logistics operators in the current logistics process discover significant deviations in historical logistics parameters such as weight and volume, they can report this to the reporting system through the logistics operation client. Logistics operators can perform reporting-related operations through the module on the logistics operation client that connects to the reporting system. For example, logistics parameters may include weight (weight parameter), volume, length, width, and height (volume, length, width, and height belong to volume parameters), and may also include other parameters such as density and packaging status. This article will use weight, volume, length, width, and height as examples for explanation. Preferably, the interaction between the reporting system and the logistics operation client can be implemented through a message queue.

[0050] It is understood that the current logistics stage includes sorting, transportation, and distribution, which are capable of being reported. The historical logistics stages are within the same fulfillment process for the same goods as the current stage, and the historical stage precedes the current stage. If the current logistics stage is sorting, the historical stage was either pickup or transportation; if the current stage is transportation, the historical stage was either pickup or sorting; if the current stage is distribution, the historical stage was pickup, sorting, or transportation. In practical applications, a logistics report request may include the waybill identifier corresponding to the goods (such as the waybill number, which can be entered into the logistics operation client via terminal scanning), the goods identifier, and pre-collected measured data of the goods' logistics parameters in the current logistics stage. Optionally, the logistics report request may also include images of the goods in the current logistics stage.

[0051] Step S202: The reporting system interacts with the warehouse management system to obtain raw data and logistics type. In this step, after receiving a logistics report request, the reporting system can interact with the warehouse management system to obtain the raw data of the logistics parameters involved in the report and the logistics type to facilitate the processing of report-related information. This step can be performed by the weight and volume verification service. It is understood that the reporting system can also read the above raw data and logistics type from a local or external database. The above raw data refers to the original values ​​of the logistics parameters of the goods in the warehouse, such as the logistics parameter values ​​when the goods leave the warehouse. The logistics type refers to the business type to which the goods belong during the logistics process, such as: small express delivery, fresh goods, cold chain delivery goods, pharmaceutical goods, etc.

[0052] As a preferred solution, before acquiring the raw data, the reporting system can determine the bubble-weight coefficient corresponding to the logistics type of the goods based on a pre-configured mapping relationship between logistics type and bubble-weight coefficient. It then uses this determined bubble-weight coefficient to convert the measured volumetric parameters into volumetric weight data. For example, the bubble-weight coefficient for small express deliveries is 12000, and for cold chain delivery goods it is 8000. This mapping relationship can be configured locally within the reporting system or in a pre-defined configuration center. If the volumetric weight data is greater than the measured weight data, the reporting system can determine the target parameter based on the volumetric parameter; if the volumetric weight data is not greater than the measured weight data, the reporting system can determine the target parameter based on the weight parameter. The target parameter is understood to be the parameter used to perform logistics billing. Subsequently, the reporting system can perform subsequent processing on the data related to the target parameter in the logistics parameters, ignoring other parameters besides the target parameter. For example, when using volumetric weight billing, subsequent processing is performed on volumetric parameters such as volume, length, width, and height, ignoring the original weight data; when using original weight billing, subsequent processing is performed on weight parameters, ignoring the volumetric parameters. It should be noted that the reporting system may also skip the above process and directly perform subsequent processing on each logistics parameter.

[0053] Step S203: The reporting system obtains matching exceedance judgment rules based on the configuration. This step can be executed by the exceedance judgment service. Specifically, the reporting system obtains the exceedance judgment rules corresponding to the logistics type of the goods based on the pre-configured mapping relationship between logistics types and exceedance judgment rules, and obtains the recorded data of logistics parameters of the goods at any historical logistics stage. For example, the exceedance judgment rule for weight parameters for small express delivery is: the absolute value of the difference between the recorded data and the original data is greater than 0.5 kg; the exceedance judgment rule for volume of cold chain delivery goods is: the absolute value of the difference between the recorded data and the original data is greater than 2000 cubic centimeters. The above mapping relationship can be configured locally in the reporting system or in a pre-configured configuration center.

[0054] Step S204: The reporting system determines the result of exceeding the standard. In this step, the reporting system uses the obtained rules for judging exceeding the standard, historical logistics record data, and raw data to determine the result of judging exceeding the standard. The result of judging exceeding the standard can indicate whether there is a deviation between the recorded data and the raw data that conforms to the corresponding rules for judging exceeding the standard.

[0055] Step S205: The reporting system obtains the responsible party, type of responsibility, and target for recovery. In this step, the reporting system can determine the responsible party (usually logistics operators) in the historical logistics process corresponding to the discrepancy in the recorded data, the corresponding type of responsibility, and the target for recovery of logistics fees (e.g., express delivery fees) (e.g., the user or logistics operators) through the responsible party service. The above-mentioned type of responsibility refers to various situations where logistics parameters are inaccurate, such as zero weight and zero volume (i.e., the weight and volume recorded in the historical logistics process are both zero), exceeding weight limits, exceeding volume limits, cash on delivery, and the user being a trusted user, etc.

[0056] Step S206: The reporting system returns a successful report notification. If the result of the exceedance judgment indicates a discrepancy between the recorded data and the original data in the historical logistics process, the reporting system can return a successful report notification to the logistics operation client. The successful report notification can include: the identified responsible party, the type of responsibility, the recorded data, and the original data. This data can be used to generate subsequent logistics parameter reporting information. Through steps S201 to S206, the reporting system can perform preliminary processing based on unified services such as verifying weight and volume, exceeding limits judgment, and confirming the responsible party, to facilitate the implementation of the main process of reporting based on logistics parameter information. This helps to determine the data and judgment results required for the main process in advance, filter out reporting information that does not exceed the limits, and improve the efficiency of reporting information processing. After receiving the successful report notification, the logistics operation client can update the reporting status of this report.

[0057] Step S207: The reporting system receives logistics parameter reporting information. In this step, after receiving a successful reporting notification, the logistics operation client generates logistics parameter reporting information and sends it to the reporting system. The logistics parameter reporting information may include: pre-collected measured data of logistics parameters for the goods in the current logistics stage; recorded data of logistics parameters for the goods in historical logistics stages; the responsible party and type of responsibility associated with the recorded data; and discrepancies between the measured data and the recorded data. The logistics parameter reporting information may also include: the original logistics parameter data determined through the aforementioned steps, the target of the investigation, and images of the goods in the current logistics stage. Preferably, after receiving the logistics parameter reporting information, the reporting system can store the data locally or in a database.

[0058] Step S208: The reporting system obtains the matching judgment action based on the configuration. The reporting system can pre-configure the mapping relationship between responsibility types and judgment actions to cover the accountability logic in different application scenarios. For example, the judgment action can be direct third-party judgment, joint liability assessment combined with third-party judgment, or joint liability assessment only. It can also include simply recording relevant data without making a judgment. Direct third-party judgment is executed by the judgment system, acting as a third party, through relevant data. Joint liability assessment combined with third-party judgment first involves the reporting system interacting with the responsible party's terminal to have the responsible party acknowledge whether or not they are liable. If they do not acknowledge liability, the judgment system executes the judgment. Joint liability assessment only refers to the reporting system interacting with the responsible party's terminal to have the responsible party acknowledge whether or not they are liable, without executing the third-party assessment method.

[0059] The mapping relationships above are as follows: for the liability type of zero weight and zero volume, the judgment action is only for both parties to acknowledge responsibility; for the liability type of trusted users, the judgment action is only to record relevant data; and for the liability type of exceeding the weight limit, the judgment action is a combination of acknowledgment by both parties and judgment by a third party. These mapping relationships can be configured locally in the reporting system or in a pre-configured configuration center.

[0060] Step S209: The reporting system obtains the judgment result. In this step, the reporting system can obtain the judgment result using the determined judgment action and logistics parameter reporting information. Specifically, if the determined action is direct third-party judgment, the reporting system generates a judgment request and sends it to an external judgment system to obtain a judgment result in response to the judgment request; the judgment request may include: logistics parameter reporting information and cargo images; if the determined action is a combination of mutual acknowledgment of responsibility and third-party judgment, the reporting system interacts with the terminal of the responsible party to obtain the mutual acknowledgment of responsibility result (i.e., whether the responsible party admits to assuming responsibility); if the mutual acknowledgment of responsibility result indicates that the responsible party confirms that it is responsible, a corresponding judgment result is generated; if the mutual acknowledgment of responsibility result indicates that the responsible party confirms that it is not responsible, a judgment request is generated and sent to an external judgment system to obtain the judgment result. Subsequently, if the judgment result indicates that the responsible party is responsible, steps S210 and S211 are executed; if the judgment result indicates that the responsible party is not responsible, the process ends.

[0061] Step S210: The reporting system generates a logistics cost recovery task and sends it to the terminal of the responsible party. In this step, the reporting system generates a logistics cost recovery task and sends it to the terminal of the responsible party. The logistics cost recovery task may include: the logistics cost to be recovered, the payment path (e.g., the QR code used to make the payment), and the target of the recovery, so that the responsible party can recover the lost logistics cost.

[0062] Step S211: The reporting system sends messages to perform subsequent operations. In one embodiment, the reporting system can send messages through a message queue to perform operations such as data updates and big data analysis. For example, if a logistics fee collection task is successfully completed, the reporting system can send messages to an external system to update logistics parameter data and billing data in a preset database. This may include delivery fees for logistics operators, thereby ensuring that personnel salaries are not affected by deviations in logistics parameters; send reward information to the logistics operation client and penalty information to the terminal of the responsible party; and perform analysis on the global reporting data on the big data platform for overall logistics situation assessment.

[0063] In the technical solution of this invention, an efficient reporting process is implemented through automated execution. This process is reused in various logistics links and application scenarios with different responsibility types based on a configurable approach. Each logistics link can be integrated into the reporting system without modification or with minor modifications, thereby improving the development efficiency of the reporting system in multiple scenarios, reducing repetitive work during development, and enhancing system maintainability. This, in turn, helps improve the stability of the reporting system and the overall logistics efficiency and service quality. As an optional solution, the logistics system can also implement reusable logistics parameter exceeding-limit judgment logic or volume-weight conversion logic through pre-configuration of the mapping relationship between logistics type and exceeding-limit judgment rules or the mapping relationship between logistics type and bubble-counting coefficient. This further improves the reusability and maintainability of the reporting system.

[0064] It should be noted that the technical solutions of this invention, including the collection, updating, analysis, processing, use, transmission, and storage of user personal information, all comply with relevant laws and regulations, are used for legitimate purposes, and do not violate public order and good morals. Necessary measures are taken to prevent unauthorized access to user personal information data and to safeguard user personal information security, network security, and national security.

[0065] For the foregoing method embodiments, they are described as a series of actions for ease of description. However, those skilled in the art should understand that the present invention is not limited to the described order of actions, and some steps may actually be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential for implementing the present invention.

[0066] To facilitate better implementation of the above-described solutions of the embodiments of the present invention, related apparatus for implementing the above-described solutions is also provided below.

[0067] Please see Figure 4As shown, the logistics information processing device 400 provided in this embodiment of the invention may include: a receiving unit 401, a processing unit 402, and a sending unit 403.

[0068] The receiving unit 401 can be used to receive logistics parameter reporting information sent by the logistics operation client. The logistics parameter reporting information includes: pre-collected measured data of logistics parameters of goods in the current logistics process, recorded data of logistics parameters of goods in historical logistics processes, the responsible entity and responsibility type associated with the recorded data, and the discrepancy between the measured data and the recorded data. The processing unit 402 can be used to determine the judgment action corresponding to the responsibility type in the logistics parameter reporting information based on the pre-configured mapping relationship between responsibility type and judgment action, and obtain the judgment result using the determined judgment action and the logistics parameter reporting information. The sending unit 403 can be used to respond to the judgment result indicating that the responsible entity is liable, generate a logistics cost recovery task and send it to the terminal of the responsible entity.

[0069] In this embodiment of the invention, the logistics information processing device further includes a pre-processing unit, configured to: receive a logistics reporting request for goods sent by the logistics operation client before receiving the logistics parameter reporting information sent by the logistics operation client; obtain the original data of the logistics parameters of the goods and the logistics type of the goods from an external warehouse management system; obtain the over-limit judgment rule corresponding to the logistics type of the goods based on a pre-configured mapping relationship between logistics type and over-limit judgment rule; obtain the recorded data of logistics parameters of the goods in any historical logistics link; determine the over-limit judgment result using the obtained over-limit judgment rule, the recorded data of the historical logistics link, and the original data; and return a reporting success notification to the logistics operation client in response to the over-limit judgment result indicating that there is a deviation between the recorded data of the historical logistics link and the original data; the logistics parameter reporting information is generated and sent by the logistics operation client after receiving the reporting success notification.

[0070] As a preferred embodiment, the pre-processing unit can be further used to: determine the responsible party and the type of responsibility in the historical logistics process to which the recorded data that deviates from the original data belongs before returning a successful report notification to the logistics operation client, and include the determined responsible party, type of responsibility, recorded data and original data in the successful report notification.

[0071] Preferably, the logistics parameters corresponding to the pre-collected measured data include weight parameters and volume parameters; the pre-processing unit can be further used to: before acquiring the raw data, determine the bubble coefficient corresponding to the logistics type of the goods based on the pre-configured mapping relationship between logistics type and bubble coefficient, and convert the measured data of volume parameters into volumetric weight data using the determined bubble coefficient; if the volumetric weight data is greater than the measured data of weight parameters, determine the volume parameters as target parameters; if the volumetric weight data is not greater than the measured data of weight parameters, determine the weight parameters as target parameters; and the logistics parameters corresponding to the raw data, the logistics parameters corresponding to the recorded data processed by the exceedance judgment rules, and the logistics parameters in the logistics parameter reporting request are the target parameters.

[0072] In one embodiment, the logistics parameter reporting information further includes: an image of the goods in the current logistics process; the liability assessment action includes: direct third-party liability assessment, or a combination of mutual liability assessment and third-party liability assessment; and the processing unit 402 can be further configured to: generate a liability assessment request and send it to an external liability assessment system when the determined action is direct third-party liability assessment, in order to obtain a liability assessment result in response to the liability assessment request; wherein, the liability assessment request includes: logistics parameter reporting information and an image; when the determined action is a combination of mutual liability assessment and third-party liability assessment, interact with the terminal of the responsible party to obtain the mutual liability assessment result; if the mutual liability assessment result indicates that the responsible party confirms that it is liable, then generate a corresponding liability assessment result; if the mutual liability assessment result indicates that the responsible party confirms that it is not liable, then generate a liability assessment request and send it to an external liability assessment system to obtain a liability assessment result.

[0073] In one optional implementation, the pre-processing unit may be further used to: after determining the responsible party in the historical logistics link to which the recorded data that deviates from the original data belongs, determine the target of the recovery in that historical logistics link, and include the target of the recovery in the successful report notification; and the logistics cost recovery task includes: the logistics cost to be recovered, the payment path, and the target of the recovery.

[0074] In one optional technical solution, the sending unit 403 interacts with an external system to: update the logistics parameter data and billing data in the preset database when the logistics cost collection task is successfully executed; send reward operation information to the logistics operation client; and send penalty operation information to the terminal of the responsible entity.

[0075] Furthermore, in this embodiment of the invention, the current logistics link is: sorting link, transportation link, or delivery link; when the current logistics link is sorting link, the historical logistics link is pickup link or transportation link; when the current logistics link is transportation link, the historical logistics link is pickup link or sorting link; when the current logistics link is delivery link, the historical logistics link is pickup link, sorting link, or transportation link.

[0076] According to the technical solution of this invention, an efficient reporting process is achieved through automated execution. This process can be reused in various logistics links and application scenarios with different responsibility types based on a configurable approach. Each logistics link can be integrated into the reporting system without modification or with minor modifications, thereby improving the development efficiency of the reporting system in multiple scenarios, reducing repetitive work during development, and enhancing system maintainability. This, in turn, helps improve the stability of the reporting system and the overall logistics efficiency and service quality. As an optional solution, the logistics system can also implement reusable logistics parameter exceeding-limit judgment logic or volume-weight conversion logic through pre-configuration of the mapping relationship between logistics type and exceeding-limit judgment rules or the mapping relationship between logistics type and bubble-counting coefficient, thereby further improving the reusability and maintainability of the reporting system.

[0077] Figure 5 An exemplary system architecture 500 is shown for which the logistics information processing method or logistics information processing apparatus of the present invention can be applied.

[0078] like Figure 5 As shown, system architecture 500 may include terminal devices 501, 502, and 503, network 504, and server 505 (this architecture is merely an example; the components included in a specific architecture may be adjusted according to the specific application). Network 504 serves as the medium for providing a communication link between terminal devices 501, 502, and 503 and server 505. Network 504 may include various connection types, such as wired or wireless communication links or fiber optic cables.

[0079] Users can use terminal devices 501, 502, and 503 to interact with server 505 via network 504 to receive or send messages, etc. Various client applications can be installed on terminal devices 501, 502, and 503, such as logistics parameter reporting applications, etc. (for example only).

[0080] Terminal devices 501, 502, and 503 can be various electronic devices with displays that support web browsing, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0081] Server 505 can be a server that provides various services, such as a backend reporting server that supports the logistics parameter reporting application operated by users using terminal devices 501, 502, and 503 (for example only). The backend reporting server can process the received logistics reporting requests and feed back the processing results (such as a report success notification - for example only) to terminal devices 501, 502, and 503.

[0082] It should be noted that the logistics information processing method provided in this embodiment of the invention is generally executed by server 505, and correspondingly, the logistics information processing device is generally set in server 505.

[0083] It should be understood that Figure 5 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0084] The present invention also provides an electronic device. The electronic device of this invention includes: one or more processors; and a storage device for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the logistics information processing method provided by the present invention.

[0085] The following is for reference. Figure 6 It shows a schematic diagram of the structure of a computer system 600 suitable for implementing an electronic device according to embodiments of the present invention. Figure 6 The electronic device shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments of the present invention.

[0086] like Figure 6 As shown, the computer system 600 includes a central processing unit (CPU) 601, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 602 or programs loaded from storage section 608 into random access memory (RAM) 603. The RAM 603 also stores various programs and data required for the operation of the computer system 600. The CPU 601, ROM 602, and RAM 603 are interconnected via a bus 604. An input / output (I / O) interface 605 is also connected to the bus 604.

[0087] The following components are connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 610 as needed so that computer programs read from it can be installed into storage section 608 as needed.

[0088] In particular, according to the embodiments disclosed in this invention, the processes described in the above main step diagrams can be implemented as computer software programs. For example, embodiments of this invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the main step diagrams. In the above embodiments, the computer program can be downloaded and installed from a network via communication section 609, and / or installed from removable medium 611. When the computer program is executed by central processing unit 601, it performs the functions defined in the system of this invention.

[0089] It should be noted that the computer-readable medium shown in this invention can be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. A computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this invention, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0090] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0091] The units described in the embodiments of the present invention can be implemented in software or hardware. The described units can also be housed in a processor; for example, a processor can be described as including a receiving unit, a processing unit, and a transmitting unit. The names of these units do not necessarily limit the specific unit; for example, a receiving unit can also be described as "a unit that provides logistics parameter reporting information to the processing unit."

[0092] In another aspect, the present invention also provides a computer-readable medium, which may be included in the device described in the above embodiments; or it may exist independently and not assembled into the device. The computer-readable medium carries one or more programs, and when the device executes the one or more programs, the steps performed by the device include: receiving logistics parameter reporting information sent by a logistics operation client; wherein the logistics parameter reporting information includes: pre-collected measured data of logistics parameters of goods in the current logistics stage, recorded data of logistics parameters of goods in historical logistics stages, the responsible entity and responsibility type associated with the recorded data; a discrepancy exists between the measured data and the recorded data; determining the judgment action corresponding to the responsibility type in the logistics parameter reporting information based on a pre-configured mapping relationship between responsibility type and judgment action; obtaining a judgment result using the determined judgment action and the logistics parameter reporting information; and generating a logistics fee collection task and sending it to the terminal of the responsible entity in response to the judgment result indicating that the responsible entity is liable.

[0093] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the method provided by the present invention.

[0094] In the technical solution of this invention, an efficient reporting process is implemented through automated execution. This process is reused in various logistics links and application scenarios with different responsibility types based on a configurable approach. Each logistics link can be integrated into the reporting system without modification or with minor modifications, thereby improving the development efficiency of the reporting system in multiple scenarios, reducing repetitive work during development, and enhancing system maintainability. This, in turn, helps improve the stability of the reporting system and the overall logistics efficiency and service quality. As an optional solution, the logistics system can also implement reusable logistics parameter exceeding-limit judgment logic or volume-weight conversion logic through pre-configuration of the mapping relationship between logistics type and exceeding-limit judgment rules or the mapping relationship between logistics type and bubble-counting coefficient. This further improves the reusability and maintainability of the reporting system.

[0095] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can occur depending on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A logistics information processing method, characterized in that, include: The system receives logistics parameter reporting information sent by the logistics operation client; wherein the logistics parameter reporting information includes: pre-collected measured data of logistics parameters of the goods in the current logistics stage, recorded data of logistics parameters of the goods in the historical logistics stages, the responsible entity and type of responsibility associated with the recorded data; and there is a deviation between the measured data and the recorded data. Based on the pre-configured mapping relationship between responsibility types and judgment actions, the judgment action corresponding to the responsibility type in the logistics parameter reporting information is determined, and the judgment result is obtained by using the determined judgment action and the logistics parameter reporting information; In response to the judgment result indicating that the responsible party is liable, a logistics cost recovery task is generated and sent to the terminal of the responsible party; The method further includes: before receiving the logistics parameter reporting information sent by the logistics operation client, receiving a logistics reporting request for the goods sent by the logistics operation client; obtaining the original data of the logistics parameters of the goods and the logistics type of the goods from an external warehouse management system; obtaining the excess judgment rule corresponding to the logistics type of the goods based on a pre-configured mapping relationship between logistics type and excess judgment rule; obtaining the recorded data of the logistics parameters of the goods at any historical logistics stage; determining the excess judgment result using the obtained excess judgment rule, the recorded data of the historical logistics stage, and the original data; and returning a reporting success notification to the logistics operation client in response to the excess judgment result indicating a deviation between the recorded data of the historical logistics stage and the original data. The logistics parameter reporting information is generated and sent by the logistics operation client after receiving the reporting success notification. Before returning a successful report notification to the logistics operation client, the responsible party and the type of responsibility in the historical logistics process to which the recorded data that deviates from the original data belongs are determined, and the determined responsible party, the type of responsibility, the recorded data, and the original data are included in the successful report notification; after determining the responsible party in the historical logistics process to which the recorded data that deviates from the original data belongs, the target for recovery in that historical logistics process is determined, and the target for recovery is included in the successful report notification; and the logistics cost recovery task includes: logistics costs to be recovered, payment path, and the target for recovery.

2. The method according to claim 1, characterized in that, The logistics parameters corresponding to the pre-collected measured data include: weight parameters and volume parameters; the method further includes: Before acquiring the raw data, the bubble coefficient corresponding to the logistics type of the goods is determined based on the pre-configured mapping relationship between logistics type and bubble coefficient, and the measured data of the volume parameter is converted into volume weight data using the determined bubble coefficient. If the volumetric weight data is greater than the measured data of the weight parameter, the volume parameter is determined as a target parameter; if the volumetric weight data is not greater than the measured data of the weight parameter, the weight parameter is determined as a target parameter; and, The target parameters are the logistics parameters corresponding to the original data, the logistics parameters corresponding to the recorded data processed using the exceeding judgment rules, and the logistics parameters in the logistics parameter reporting request.

3. The method according to claim 1, characterized in that, The logistics parameter reporting information further includes: an image of the goods at the current logistics stage; the liability determination action includes: direct third-party liability determination, or a combination of both parties acknowledging liability and third-party liability determination; and, obtaining the liability determination result using the determined liability determination action and the logistics parameter reporting information includes: If the determined action is direct third-party liability assessment, a liability assessment request is generated and sent to an external liability assessment system to obtain a liability assessment result in response to the liability assessment request; wherein, the liability assessment request includes: the logistics parameter reporting information and the image; In cases where the determined action involves both parties acknowledging responsibility and a third party adjudicating responsibility, the system interacts with the terminal of the responsible party to obtain the responsibility acknowledgment result. If the responsibility acknowledgment result indicates that the responsible party confirms its responsibility, a corresponding adjudication result is generated. If the responsibility acknowledgment result indicates that the responsible party confirms its lack of responsibility, an adjudication request is generated and sent to an external adjudication system to obtain the adjudication result.

4. The method according to claim 1, characterized in that, The method further includes: If the logistics fee collection task is successfully completed, update the logistics parameter data and billing data in the preset database; send reward operation information to the logistics operation client and penalty operation information to the terminal of the responsible entity.

5. The method according to any one of claims 1-4, characterized in that, The current logistics process refers to: sorting, transportation, or delivery. If the current logistics stage is the sorting stage, the historical logistics stage is the pickup stage or the transportation stage; If the current logistics stage is the transportation stage, the historical logistics stage is the pickup stage or the sorting stage. If the current logistics stage is the delivery stage, the historical logistics stage is the pickup stage, sorting stage, or transportation stage.

6. A logistics information processing device, characterized in that, include: The receiving unit is used to receive logistics parameter reporting information sent by the logistics operation client; wherein, the logistics parameter reporting information includes: pre-collected measured data of logistics parameters of the goods in the current logistics stage, recorded data of logistics parameters of the goods in historical logistics stages, the responsible entity and responsibility type associated with the recorded data; there is a deviation between the measured data and the recorded data; The processing unit is used to determine the judgment action corresponding to the responsibility type in the logistics parameter report information based on the pre-configured mapping relationship between responsibility type and judgment action, and to obtain the judgment result using the determined judgment action and the logistics parameter report information; The sending unit is used to generate a logistics cost recovery task and send it to the terminal of the responsible party in response to the judgment result indicating that the responsible party is responsible; The pre-processing unit is configured to: receive a logistics reporting request for the goods sent by the logistics operation client before receiving the logistics parameter reporting information sent by the logistics operation client; obtain the original data of the logistics parameters of the goods and the logistics type of the goods from an external warehouse management system; obtain the excess judgment rule corresponding to the logistics type of the goods based on a pre-configured mapping relationship between logistics type and excess judgment rule; obtain the recorded data of the logistics parameters of the goods at any historical logistics stage; determine the excess judgment result using the obtained excess judgment rule, the recorded data of the historical logistics stage, and the original data; and, in response to the excess judgment result indicating a deviation between the recorded data of the historical logistics stage and the original data, return a response to the logistics operation client. The notification of successful reporting is as follows: The logistics parameter reporting information is generated and sent by the logistics operation client after receiving the notification of successful reporting; Before returning the notification of successful reporting to the logistics operation client, the responsible party and the type of responsibility in the historical logistics process to which the recorded data that deviates from the original data belongs are determined, and the determined responsible party, the type of responsibility, the recorded data, and the original data are included in the notification of successful reporting; After determining the responsible party in the historical logistics process to which the recorded data that deviates from the original data belongs, the target for recovery in that historical logistics process is determined, and the target for recovery is included in the notification of successful reporting; and the logistics fee recovery task includes: logistics fees to be recovered, payment path, and the target for recovery.

7. An electronic device, characterized in that, include: One or more processors; Storage device for storing one or more programs. When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the method as described in any one of claims 1-5.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1-5.

Images