Waybill processing method and device, electronic equipment and storage medium

Abstract

The invention discloses a waybill processing method and device, electronic equipment and a storage medium, and relates to the technical field of computers. A specific embodiment of the method comprises the steps of receiving a processing instruction of a waybill, obtaining corresponding waybill information to determine logistics information of each logistics node corresponding to the waybill, and generating a monitoring event set corresponding to each logistics node based on the logistics information; in response to the state change of the waybill, obtaining the current state information of the waybill to match the current state information with the monitoring event set, and determining the delivery exception information of the waybill according to the matching result to generate an exception message; and determining a current logistics node based on the current state information so as to send the abnormal information to a monitoring end associated with the logistics node. According to the embodiment, the problems that when the number of waybills is large, a large number of tasks are issued, it is difficult for business personnel to check and monitor the waybill distribution situation in time, and waybill distribution abnormity cannot be effectively avoided can be solved.

Description

Technical Field

[0001] This invention relates to the field of computer technology, and in particular to a method, apparatus, electronic device, and storage medium for processing waybills. Background Technology

[0002] In the logistics and delivery scenario of waybills, the process from order placement to delivery involves many stages. Any anomaly at any stage can lead to waybill backlogs, resulting in timeouts and other issues. To avoid these delivery anomalies, relevant technologies typically distribute logistics tasks to the corresponding personnel in each stage's system. However, when the number of waybills is large, distributing numerous tasks makes it difficult for personnel to promptly view and monitor delivery status, thus failing to effectively prevent delivery anomalies. Summary of the Invention

[0003] In view of this, embodiments of the present invention provide a method, apparatus, electronic device, and storage medium for processing waybills, which can solve the problem that when a large number of tasks are issued when the number of waybills is large, it is difficult for business personnel to view and monitor the waybill delivery status in a timely manner, and it is impossible to effectively avoid waybill delivery anomalies.

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

[0005] A method for processing waybills according to an embodiment of the present invention includes: receiving a processing instruction for a waybill, obtaining corresponding waybill information, determining the logistics information of each logistics node corresponding to the waybill, and generating a set of monitoring events corresponding to each logistics node based on the logistics information;

[0006] In response to the status change of the waybill, the current status information of the waybill is obtained and matched with the monitoring event set. Based on the matching result, the delivery abnormality information of the waybill is determined and an abnormal message is generated.

[0007] The current logistics node is determined based on the current status information, and the abnormal information is sent to the monitoring terminal associated with the logistics node.

[0008] In one embodiment, obtaining the current status information of the waybill to match it with the set of monitoring events includes:

[0009] Obtain the current status information of the waybill to determine the current logistics node corresponding to the waybill, and query the corresponding monitoring event set;

[0010] For each monitoring event in the monitoring event set, the corresponding condition parameters are queried to determine the parameter value of the condition parameters based on the current status information, so as to match it with the monitoring event and obtain the matching result.

[0011] In yet another embodiment, the monitoring events include site monitoring events;

[0012] Determining the parameter value of the condition parameter based on the current state information to match the monitoring event includes:

[0013] Extract the current station corresponding to the waybill from the current status information, and query the corresponding station attributes;

[0014] Obtain the delivery standard parameters of the site monitoring event corresponding to the waybill, so as to match the site attributes with the delivery standard parameters.

[0015] In yet another embodiment, a set of monitoring events corresponding to each of the logistics nodes is generated based on the logistics information, including:

[0016] For each logistics node, query the corresponding monitoring type, obtain the monitoring event template associated with each monitoring type, and generate a corresponding monitoring event set based on the logistics information.

[0017] In another embodiment, obtaining the corresponding waybill information to determine the logistics information of each logistics node corresponding to the waybill includes:

[0018] Obtain the address information and delivery type of the waybill to determine the logistics route of the waybill, and determine the location information of each logistics node corresponding to the waybill based on the logistics route;

[0019] The item type of the waybill is obtained, and the time information corresponding to each logistics node is determined in combination with the logistics route.

[0020] In yet another embodiment, after obtaining the current status information of the waybill, the method further includes:

[0021] Based on the current status information, determine the current logistics node corresponding to the waybill, query the corresponding timed monitoring event, and trigger the timed monitor;

[0022] In response to the timed monitor determining that the abnormal alarm conditions are met, the delivery abnormality information of the waybill is determined to generate an abnormal message.

[0023] In yet another embodiment, it further includes:

[0024] Receive the query information of the waybill, obtain the current status information of the waybill, and determine the current logistics status of the waybill;

[0025] In response to the current logistics status being in an ended state, the delivery result of the waybill is generated and sent; in response to the current logistics status not being in an ended state, the historical delivery status of the waybill is obtained and sent.

[0026] To achieve the above objectives, according to another aspect of the present invention, an apparatus for processing waybills is provided.

[0027] An apparatus for processing waybills according to an embodiment of the present invention includes: a generation unit, configured to receive processing instructions for waybills, obtain corresponding waybill information, determine logistics information of each logistics node corresponding to the waybill, and generate a set of monitoring events corresponding to each logistics node based on the logistics information;

[0028] A matching unit is used to respond to the status change of the waybill, obtain the current status information of the waybill, match it with the monitoring event set, determine the delivery abnormality information of the waybill based on the matching result, and generate an abnormal message.

[0029] The sending unit is used to determine the current logistics node based on the current status information, so as to send the abnormal information to the monitoring terminal associated with the logistics node.

[0030] In one embodiment, the matching unit is specifically used for:

[0031] Obtain the current status information of the waybill to determine the current logistics node corresponding to the waybill, and query the corresponding monitoring event set;

[0032] For each monitoring event in the monitoring event set, the corresponding condition parameters are queried to determine the parameter value of the condition parameters based on the current status information, so as to match it with the monitoring event and obtain the matching result.

[0033] In yet another embodiment, the monitoring events include site monitoring events;

[0034] The matching unit is specifically used for:

[0035] Extract the current station corresponding to the waybill from the current status information, and query the corresponding station attributes;

[0036] Obtain the delivery standard parameters of the site monitoring event corresponding to the waybill, so as to match the site attributes with the delivery standard parameters.

[0037] In yet another embodiment, the generating unit is specifically used for:

[0038] For each logistics node, query the corresponding monitoring type, obtain the monitoring event template associated with each monitoring type, and generate a corresponding monitoring event set based on the logistics information.

[0039] In yet another embodiment, the generating unit is specifically used for:

[0040] Obtain the address information and delivery type of the waybill to determine the logistics route of the waybill, and determine the location information of each logistics node corresponding to the waybill based on the logistics route;

[0041] The item type of the waybill is obtained, and the time information corresponding to each logistics node is determined in combination with the logistics route.

[0042] In yet another embodiment, the apparatus further includes:

[0043] The triggering unit is used to determine the current logistics node corresponding to the waybill based on the current status information, query the corresponding timed monitoring event, and trigger the timed monitor.

[0044] The generation unit is used to determine the delivery anomaly information of the waybill in response to the timed monitor determining that the abnormal alarm conditions are met, so as to generate an abnormal message.

[0045] In yet another embodiment, the apparatus further includes:

[0046] The receiving unit is used to receive the query information of the waybill and obtain the current status information of the waybill in order to determine the current logistics status of the waybill.

[0047] The sending unit is further configured to generate and send the delivery result of the waybill in response to the current logistics status being an ended state; and to obtain and send the historical delivery status of the waybill in response to the current logistics status not being an ended state.

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

[0049] An electronic device according to an embodiment of 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 waybill processing method provided in the embodiment of the present invention.

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

[0051] An embodiment of the present invention provides a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the waybill processing method provided in the embodiment of the present invention.

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

[0053] A computer program product according to an embodiment of the present invention includes a computer program that, when executed by a processor, implements the waybill processing method provided in an embodiment of the present invention.

[0054] One embodiment of the above invention has the following advantages or beneficial effects: In this embodiment, after receiving the processing instruction of the waybill, the logistics information of each corresponding logistics node can be determined based on the waybill information, and then a monitoring event set for each logistics node can be generated. The monitoring events can be used to monitor abnormalities during the waybill delivery process. Therefore, when the state of the waybill changes, the current state information of the waybill can be obtained and matched with the monitoring event set. Based on the matching result, it can be determined whether the state of the waybill meets the monitoring event, thus identifying the abnormalities and delivery anomalies of the waybill, generating an anomaly message, and sending the anomaly message to the corresponding monitoring terminal. In this embodiment, monitoring events for anomaly monitoring are generated for each logistics node of the waybill, so that the matching result with the monitoring event can be determined in a timely manner based on the state information of the waybill. This allows for timely detection of anomalies during the waybill delivery process, and timely sending of anomaly messages, thereby achieving full-process anomaly monitoring of waybill delivery, timely and effective detection of waybill delivery anomalies, avoiding abnormal situations such as waybill delays and backlogs, and improving the delivery efficiency of waybills.

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

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

[0057] Figure 1 This is a schematic diagram of a main flow of a waybill processing method according to an embodiment of the present invention;

[0058] Figure 2 This is a schematic diagram of another main process of a waybill processing method according to an embodiment of the present invention;

[0059] Figure 3 This is a schematic diagram of the main units of a waybill processing apparatus according to an embodiment of the present invention;

[0060] Figure 4 This is an exemplary system architecture diagram in which embodiments of the present invention can be applied;

[0061] Figure 5 This is a schematic diagram of the structure of a computer system suitable for implementing embodiments of the present invention. Detailed Implementation

[0062] 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.

[0063] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other. The acquisition, storage, use, and processing of data in the technical solutions of this application all comply with the relevant provisions of national laws and regulations.

[0064] This invention provides a waybill processing system that can be used to process waybill deliveries, specifically for monitoring the waybill delivery process, and especially for monitoring anomalies during waybill delivery.

[0065] This invention provides a method for processing waybills, which can be executed by a waybill processing system, such as... Figure 1 As shown, the method includes:

[0066] S101: Receive the processing instructions for the waybill, obtain the corresponding waybill information, determine the logistics information of each logistics node corresponding to the waybill, and generate a set of monitoring events corresponding to each logistics node based on the logistics information.

[0067] The processing instructions for waybills can be automatically triggered or sent by other devices. These instructions can represent commands to monitor the waybill and may include waybill information (i.e., waybill information can be obtained from the processing instructions themselves), or they may include a waybill identifier. After receiving the waybill processing instruction, the system can retrieve the waybill information corresponding to the waybill identifier. The waybill information can include various details, such as item type, delivery type, delivery address, and delivery packaging parameters.

[0068] In this embodiment of the invention, waybill delivery can be divided into nodes to divide the entire delivery process into one or more delivery stages, with each node serving as a logistics node. For example, the delivery process of a waybill can be divided into three stages: pickup, transportation, and delivery. Each stage can serve as a logistics node. In more granular monitoring scenarios, delivery stages can also be divided based on the delivery stations where the waybill stops. For instance, during the transportation process, the waybill may stop at multiple delivery stations, so the transportation node can be further divided into delivery stages based on the delivery stations where the waybill stops.

[0069] For waybills, after obtaining the waybill information, the delivery process of the waybill can be predetermined, so the logistics information corresponding to each logistics node can also be determined. Logistics information represents the waybill delivery information for the corresponding logistics node, and can be specifically set based on monitoring needs. This can include the initial state, intermediate state, and end state of the waybill corresponding to the logistics node, the initial location, intermediate location, and end location of the waybill, delivery station information, the required delivery time, and whether time monitoring is required, etc. For example, for a delivery logistics node, the initial state of the waybill may include "pending unsealing of the vehicle," the intermediate state may include "pending inspection," "pending delivery," and "delivery," the end state may include "delivery completed," the initial location may include the delivery station, the end location may include the destination address of the waybill, delivery station information may include the delivery station identifier, location, and delivery type, the required delivery time can be estimated or determined based on the waybill delivery requirements, and whether time monitoring is required can be set based on needs.

[0070] Therefore, the steps to determine the logistics information of each logistics node may include: obtaining the address information and delivery type of the waybill to determine the logistics route of the waybill, and determining the location information of each logistics node corresponding to the waybill based on the logistics route; obtaining the item type of the waybill to determine the time information corresponding to each logistics node in combination with the logistics route.

[0071] Since the delivery operations performed on each waybill are different, the need for anomaly monitoring is also different for each logistics node. Therefore, each logistics node can set corresponding monitoring requirements, and then generate a corresponding set of monitoring events based on the logistics information of the logistics node.

[0072] It should be noted that monitoring events are used to monitor delivery anomalies. Delivery events can be configured with corresponding event conditions. When a delivery order meets the event conditions, the monitoring event can be triggered, which can identify an anomaly in the delivery of the delivery order. This allows for timely identification of the anomaly information and the issuance of an anomaly alert, so that the delivery anomaly can be resolved in a timely manner and the delivery of the delivery order can be completed as soon as possible.

[0073] In this embodiment of the invention, possible anomalies during waybill delivery can be categorized, and corresponding monitoring types can be set. For example, a waybill may exhibit packaging errors, such as ordinary packaging for fresh produce or damaged packaging, so a packaging monitoring type can be set. Similarly, a waybill may exhibit delivery station anomalies, such as the delivery station's supported delivery type not matching the waybill's requirements, or the delivery station's location not matching the waybill's delivery route, so a station monitoring type can be set. For each monitoring type, corresponding monitoring event templates can be set for generating monitoring events.

[0074] Specifically, for the monitoring needs of each logistics node, a correspondence can be established between it and each monitoring type. Then, when generating a set of monitoring events, the monitoring types corresponding to each logistics node can be queried first, and the monitoring event templates associated with each monitoring type can be obtained, so as to generate the corresponding set of monitoring events based on the logistics information.

[0075] It should be noted that the monitoring event template can include event condition templates to establish the triggering conditions for monitoring events. Since event triggering conditions often involve operations such as comparison and matching, logical operations may be involved. Therefore, a condition management module can be set up to support logical operations such as AND, OR, and NOT, enabling the configuration of time conditions for monitoring events.

[0076] In scenarios where the triggering conditions for monitoring events require matching real-time data acquired during the waybill delivery process with parameters determined through the waybill information, these parameters, known as delivery standard parameters, need to be pre-determined when generating the monitoring event. These parameters are then used to generate triggering conditions through a condition template, thereby generating the monitoring event. For example, for a site monitoring event, to monitor whether the site where the waybill arrives meets the delivery type requirements, the monitoring delivery standard parameter in the event conditions can be set to the delivery type determined from the waybill information. Then, during the waybill delivery process, the delivery types supported by the site where the waybill arrives can be acquired in real time, and matched with the monitoring delivery standard parameter to determine whether the event conditions for the monitoring event are met, thus identifying any anomalies.

[0077] In some scenarios, delivery orders require time limits at certain delivery nodes due to delivery needs. For example, when the item on a delivery order is fresh produce, timely delivery is necessary, so a delivery time limit needs to be set. In such scenarios, time monitoring of delivery nodes is required. This can be achieved by setting up a timed monitor and setting trigger conditions for the timed monitor during the time monitoring phase. When the delivery order meets the trigger conditions, the corresponding timed monitor is triggered. If the delivery order fails to enter the next stage of delivery within the monitoring time of the timed monitor, then the delivery order is considered to be abnormal.

[0078] S102: In response to a change in the status of a waybill, obtain the current status information of the waybill, match it with the set of monitoring events, determine the delivery anomaly information of the waybill based on the matching result, and generate an anomaly message.

[0079] During the delivery process, delivery dynamics can be collected or reported in real time, allowing for the determination of changes in the delivery status. After each status change, anomaly detection can be performed to promptly identify any issues. Therefore, in response to a status change, the current status information of the waybill can be obtained and matched against a set of monitoring events. Since these events are for anomaly monitoring, a successful match indicates an anomaly. Based on the successfully matched monitoring events, the delivery anomaly information, such as the anomaly type and stage, can be determined, leading to the generation of an anomaly message. The current status information of the waybill can include its current status, the current delivery station, and the current logistics node.

[0080] Specifically, since different logistics nodes correspond to different sets of monitoring events, this step first obtains the current status information of the waybill to determine the current logistics node corresponding to the waybill, and then queries the corresponding set of monitoring events. Then, for each monitoring event in the set, the corresponding condition parameters are queried to determine the parameter values ​​based on the current status information, and these parameters are matched with the monitoring events to obtain the matching results. The condition parameters represent the conditions required for the event conditions to perform the matching operation, and their values ​​can be determined based on the current status information.

[0081] For example, taking a site monitoring event as an example, the matching steps for the monitoring event can be performed as follows: extract the current site corresponding to the waybill from the current status information, query the corresponding site attributes; obtain the delivery standard parameters of the site monitoring event corresponding to the waybill, so as to match the site attributes and the delivery standard parameters. Here, the conditional parameters of the site monitoring event can be the delivery types supported by the site, so the site attributes can include the delivery types supported by the site, which are the parameter values ​​of the conditional parameters. The delivery standard parameters can be the delivery type required by the waybill determined in step S101, and thus the delivery type required by the waybill can be matched with the delivery types supported by the site to obtain the matching result.

[0082] In some scenarios, due to the need for time monitoring, after obtaining the current status information, the current logistics node corresponding to the waybill can be determined based on the current status information to query the corresponding timed monitoring event. If a timed monitoring event is found, it means that time monitoring is required, and the corresponding timed monitor can be triggered. In response to the timed monitor determining that the abnormal alarm conditions are met, the delivery abnormal information of the waybill is determined to generate an abnormal message.

[0083] Timed monitors are typically set with abnormal alarm conditions, such as the waybill status not changing within a predetermined time or the waybill status not changing to a specified status within a predetermined time. When the timed monitor determines that the abnormal alarm conditions are met, it can determine that the waybill has an abnormality. Then, based on the abnormal alarm conditions, it can determine the delivery abnormality information and generate an abnormal message.

[0084] It should be noted that, in this embodiment of the invention, information such as the status of the waybill can be sent via MQ trigger, so that the information of the waybill can be obtained in a timely manner.

[0085] S103: Determine the current logistics node based on the current status information, and send the abnormal information to the monitoring terminal associated with the logistics node.

[0086] Each logistics node can be assigned a corresponding monitoring terminal, which can be the terminal device of the responsible personnel or the monitoring device in the waybill system. In this way, after an abnormal message is generated, it can be sent to the monitoring terminal associated with the logistics node, so that the abnormality of the waybill can be handled in a timely manner.

[0087] In this embodiment of the invention, the status changes of the waybill can also be recorded to facilitate the query of the waybill's delivery status. Specifically, the process can be as follows: receiving the query information of the waybill, obtaining the current status information of the waybill to determine the current logistics status of the waybill; in response to the current logistics status being an end status, generating and sending the delivery result of the waybill; in response to the current logistics status not being an end status, obtaining and sending the historical delivery status of the waybill.

[0088] When the current logistics status is "closed," meaning the waybill delivery is complete, a delivery result can be directly generated and sent to the inquiring party. When the current logistics status is not "closed," meaning the waybill delivery is incomplete, the historical delivery status of the waybill can be retrieved—that is, the historical delivery status from the initial status to the current logistics status—so that the inquiring party can understand the waybill delivery process. Specifically, the historical delivery status can refer to the recorded status information of the waybill.

[0089] It should be noted that before obtaining the current status information of the waybill, the waybill information can also be verified. For example, if the query information can include a waybill identifier, the existence of the waybill information can be verified. If it exists, the current status information of the waybill can be obtained; if it does not exist, an empty string can be returned.

[0090] In this embodiment of the invention, monitoring events for anomaly monitoring are generated for each logistics node of the waybill. This allows for timely determination of the matching results between the waybill's status information and the monitoring events, thereby enabling timely detection of anomalies in the waybill's delivery process and timely sending of anomaly messages. This achieves full-process anomaly monitoring of waybill delivery, timely and effective detection of waybill delivery anomalies, avoidance of anomalies such as waybill delays and backlogs, and improvement of waybill delivery efficiency.

[0091] The following is combined Figure 2 The illustrated embodiments provide a detailed explanation of the waybill processing method in this invention. Figure 2 As shown, the method includes:

[0092] S201: Receive the processing instruction for the waybill, obtain the corresponding waybill information, and determine the logistics information of each logistics node corresponding to the waybill.

[0093] S202: For each logistics node, query the corresponding monitoring types, obtain the monitoring event templates associated with each monitoring type, and generate the corresponding monitoring event set based on the logistics information.

[0094] S203: In response to a change in the status of the waybill, obtain the current status information of the waybill.

[0095] S204: Obtain the current status information of the waybill to determine the current logistics node corresponding to the waybill and query the corresponding monitoring event set.

[0096] S205: For each monitoring event in the monitoring event set, query the corresponding condition parameters to determine the parameter values ​​of the condition parameters based on the current status information, so as to match them with the monitoring events and obtain the matching results.

[0097] S06: Determine the delivery exception information of the waybill based on the matching results, and generate an exception message.

[0098] S07: Determine the current logistics node based on the current status information, and send the abnormal information to the monitoring terminal associated with the logistics node.

[0099] It should be noted that the data processing principle in the embodiments of the present invention is the same as... Figure 1 The data processing principles in the illustrated embodiments are the same and will not be repeated here.

[0100] To address the problems existing in the prior art, embodiments of the present invention provide a waybill processing device 300, such as... Figure 3 As shown, the device 300 includes:

[0101] The generation unit 301 is used to receive the processing instruction of the waybill, obtain the corresponding waybill information, determine the logistics information of each logistics node corresponding to the waybill, and generate a set of monitoring events corresponding to each logistics node based on the logistics information.

[0102] The matching unit 302 is used to respond to the status change of the waybill, obtain the current status information of the waybill, match it with the monitoring event set, determine the delivery abnormality information of the waybill based on the matching result, and generate an abnormal message.

[0103] The sending unit 303 is used to determine the current logistics node based on the current status information, so as to send the abnormal information to the monitoring terminal associated with the logistics node.

[0104] It should be understood that the manner in which embodiments of the present invention are implemented is different from the implementation method. Figure 1 The embodiments shown are the same and will not be described again here.

[0105] In one embodiment, the matching unit 302 is specifically used for:

[0106] Obtain the current status information of the waybill to determine the current logistics node corresponding to the waybill, and query the corresponding monitoring event set;

[0107] For each monitoring event in the monitoring event set, the corresponding condition parameters are queried to determine the parameter value of the condition parameters based on the current status information, so as to match it with the monitoring event and obtain the matching result.

[0108] In yet another embodiment, the monitoring events include site monitoring events;

[0109] The matching unit 302 is specifically used for:

[0110] Extract the current station corresponding to the waybill from the current status information, and query the corresponding station attributes;

[0111] Obtain the delivery standard parameters of the site monitoring event corresponding to the waybill, so as to match the site attributes with the delivery standard parameters.

[0112] In yet another embodiment, the generation unit 301 is specifically used for:

[0113] For each logistics node, query the corresponding monitoring type, obtain the monitoring event template associated with each monitoring type, and generate a corresponding monitoring event set based on the logistics information.

[0114] In yet another embodiment, the generation unit 301 is specifically used for:

[0115] Obtain the address information and delivery type of the waybill to determine the logistics route of the waybill, and determine the location information of each logistics node corresponding to the waybill based on the logistics route;

[0116] The item type of the waybill is obtained, and the time information corresponding to each logistics node is determined in combination with the logistics route.

[0117] In yet another embodiment, the device 300 further includes:

[0118] The triggering unit is used to determine the current logistics node corresponding to the waybill based on the current status information, query the corresponding timed monitoring event, and trigger the timed monitor.

[0119] The generation unit 301 is used to determine the delivery abnormality information of the waybill in response to the timed monitor determining that the abnormal alarm conditions are met, so as to generate an abnormal message.

[0120] In yet another embodiment, the device 300 further includes:

[0121] The receiving unit is used to receive the query information of the waybill and obtain the current status information of the waybill in order to determine the current logistics status of the waybill.

[0122] The sending unit 303 is further configured to generate and send the delivery result of the waybill in response to the current logistics status being an end status; and to obtain and send the historical delivery status of the waybill in response to the current logistics status not being an end status.

[0123] It should be understood that the manner in which embodiments of the present invention are implemented is different from the implementation method. Figure 1 , 2 The embodiments shown are the same and will not be described again here.

[0124] In this embodiment of the invention, monitoring events for anomaly monitoring are generated for each logistics node of the waybill. The matching result of the monitoring event can be determined in a timely manner based on the status information of the waybill, thereby enabling timely detection of anomalies in the waybill during the delivery process and timely sending of anomaly messages. This achieves anomaly monitoring of the entire waybill delivery process, timely and effectively detects anomalies in waybill delivery, avoids anomalies such as waybill delays and backlogs, and improves the delivery efficiency of waybills.

[0125] According to embodiments of the present invention, an electronic device and a readable storage medium are also provided.

[0126] An electronic device according to an embodiment of the present invention includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to cause the at least one processor to perform the waybill processing method provided in the embodiment of the present invention.

[0127] Figure 4 An exemplary system architecture 400 is shown, in which the method or apparatus for waybill processing according to embodiments of the present invention can be applied.

[0128] like Figure 4 As shown, system architecture 400 may include terminal devices 401, 402, and 403, a network 404, and a server 405. Network 404 serves as the medium for providing communication links between terminal devices 401, 402, and 403 and server 405. Network 404 may include various connection types, such as wired or wireless communication links, or fiber optic cables, etc.

[0129] Users can use terminal devices 401, 402, and 403 to interact with server 405 via network 404 to receive or send messages, etc. Various client applications can be installed on terminal devices 401, 402, and 403.

[0130] Terminal devices 401, 402, and 403 can be, but are not limited to, smartphones, tablets, laptops, and desktop computers, etc.

[0131] Server 405 can be a server that provides various services. The server can analyze and process data such as received product information query requests, and feed back the processing results (such as product information - just an example) to the terminal device.

[0132] It should be noted that the waybill processing method provided in this embodiment of the invention is generally executed by server 405, and correspondingly, the waybill processing device is generally located in server 405.

[0133] It should be understood that Figure 4 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.

[0134] The following is for reference. Figure 5 It shows a schematic diagram of the structure of a computer system 500 suitable for implementing embodiments of the present invention. Figure 5 The computer system 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.

[0135] like Figure 5As shown, the computer system 500 includes a central processing unit (CPU) 501, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 502 or programs loaded from storage section 508 into random access memory (RAM) 503. The RAM 503 also stores various programs and data required for the operation of the system 500. The CPU 501, ROM 502, and RAM 503 are interconnected via a bus 504. An input / output (I / O) interface 505 is also connected to the bus 504.

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

[0137] In particular, according to the embodiments disclosed in this invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in 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 flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 509, and / or installed from removable medium 511. When the computer program is executed by central processing unit (CPU) 501, it performs the functions defined above in the system of this invention.

[0138] 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. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, 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 can be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0139] 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 unit, 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.

[0140] 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 generation unit, a matching unit, and a sending unit. The names of these units do not necessarily limit the specific unit; for example, a generation unit can also be described as "a unit that performs the functions of a generation unit."

[0141] 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 that, when executed by the device, cause the device to perform the waybill processing method provided by the present invention.

[0142] In another aspect, the present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the waybill processing method provided in the embodiments of the present invention.

[0143] 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 method for processing waybills, characterized in that, include: Receive the processing instruction of the waybill, obtain the corresponding waybill information, determine the logistics information of each logistics node corresponding to the waybill, and generate a set of monitoring events corresponding to each logistics node based on the logistics information; In response to the status change of the waybill, the current status information of the waybill is obtained and matched with the monitoring event set. Based on the matching result, the delivery abnormality information of the waybill is determined and an abnormal message is generated. The current logistics node is determined based on the current status information, and the abnormal information is sent to the monitoring terminal associated with the logistics node.

2. The method according to claim 1, characterized in that, Obtain the current status information of the waybill to match it with the set of monitoring events, including: Obtain the current status information of the waybill to determine the current logistics node corresponding to the waybill, and query the corresponding monitoring event set; For each monitoring event in the monitoring event set, the corresponding condition parameters are queried to determine the parameter value of the condition parameters based on the current status information, so as to match it with the monitoring event and obtain the matching result.

3. The method according to claim 2, characterized in that, The monitoring events include site monitoring events; Determining the parameter value of the condition parameter based on the current state information to match the monitoring event includes: Extract the current station corresponding to the waybill from the current status information, and query the corresponding station attributes; Obtain the delivery standard parameters of the site monitoring event corresponding to the waybill, so as to match the site attributes with the delivery standard parameters.

4. The method according to claim 1, characterized in that, Based on the logistics information, a set of monitoring events corresponding to each logistics node is generated, including: For each logistics node, query the corresponding monitoring type, obtain the monitoring event template associated with each monitoring type, and generate a corresponding monitoring event set based on the logistics information.

5. The method according to claim 1, characterized in that, Obtain the corresponding waybill information to determine the logistics information of each logistics node corresponding to the waybill, including: Obtain the address information and delivery type of the waybill to determine the logistics route of the waybill, and determine the location information of each logistics node corresponding to the waybill based on the logistics route; The item type of the waybill is obtained, and the time information corresponding to each logistics node is determined in combination with the logistics route.

6. The method according to claim 1, characterized in that, After obtaining the current status information of the waybill, the process also includes: Based on the current status information, determine the current logistics node corresponding to the waybill, query the corresponding timed monitoring event, and trigger the timed monitor; In response to the timed monitor determining that the abnormal alarm conditions are met, the delivery abnormality information of the waybill is determined to generate an abnormal message.

7. The method according to claim 1, characterized in that, Also includes: Receive the query information of the waybill, obtain the current status information of the waybill, and determine the current logistics status of the waybill; In response to the current logistics status being in an ended state, the delivery result of the waybill is generated and sent; in response to the current logistics status not being in an ended state, the historical delivery status of the waybill is obtained and sent.

8. A device for processing waybills, characterized in that, include: The generation unit is used to receive the processing instructions of the waybill, obtain the corresponding waybill information, determine the logistics information of each logistics node corresponding to the waybill, and generate a set of monitoring events corresponding to each logistics node based on the logistics information. A matching unit is used to respond to the status change of the waybill, obtain the current status information of the waybill, match it with the monitoring event set, determine the delivery abnormality information of the waybill based on the matching result, and generate an abnormal message. The sending unit is used to determine the current logistics node based on the current status information, so as to send the abnormal information to the monitoring terminal associated with the logistics node.

9. 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-7.

10. A computer-readable 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-7.

Images