Waybill data processing method, computer equipment, readable storage medium and program product

Abstract

The invention relates to a waybill data processing method, computer equipment, a computer readable storage medium and a computer program product. The method comprises the steps of calculating a storage node identifier corresponding to a to-be-prompted waybill according to a waybill identifier of the to-be-prompted waybill; acquiring waybill data corresponding to the waybill to be prompted from a storage node corresponding to the storage node identifier; when the waybill data indicates that the to-be-prompted waybill is a first to-be-prompted waybill meeting the prompt screening condition, caching the first waybill data of the first to-be-prompted waybill; according to the cached first waybill data, obtaining outbound time of a delivery object corresponding to each first to-be-prompted waybill; and when the call-out time of the delivery object is up, initiating a call-out prompt for the delivery object by using the interactive voice response system. By adopting the method, the obtaining efficiency of the waybill data can be improved, and the timeliness of logistics waybill processing can be improved.

Description

Technical Field

[0001] This application relates to the field of logistics technology, and in particular to a waybill data processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product. Background Technology

[0002] In the express delivery and logistics process, the timeliness of waybills is crucial for ensuring the smooth completion of the delivery process. To ensure that waybills are processed in a timely manner during delivery, logistics network staff typically need to manually screen waybills that may have timeliness issues and remind relevant delivery personnel. To reduce the workload of manual operations, related technologies have introduced automated methods to monitor and alert on timeliness risks of waybills. However, traditional waybill data storage and retrieval methods are prone to read / write performance limitations when dealing with massive amounts of waybill data, making it difficult to meet the needs of real-time acquisition and processing of waybill data in automated processing scenarios, thus affecting the timeliness of alerts. Summary of the Invention

[0003] Therefore, it is necessary to provide a waybill data processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product to address the aforementioned technical problems.

[0004] Firstly, this application provides a method for processing waybill data, including:

[0005] Calculate the storage node identifier corresponding to the waybill to be prompted based on the waybill identifier of the waybill to be prompted.

[0006] Retrieve the waybill data corresponding to the waybill to be prompted from the storage node corresponding to the storage node identifier;

[0007] When the waybill data indicates that the waybill to be prompted is a first waybill to be prompted that meets the prompting filter conditions, the first waybill data of the first waybill to be prompted is cached.

[0008] Based on the cached data of each of the first waybills, the outbound call time of the delivery object corresponding to each of the first waybills to be notified is obtained;

[0009] When the outbound call time for the delivery recipient arrives, an outbound call notification is initiated to the delivery recipient using an interactive voice response system.

[0010] In one embodiment, obtaining the outbound call time of the delivery object corresponding to each of the first order to be prompted based on the cached first order data includes: obtaining the delivery object and delivery scenario corresponding to each of the first order to be prompted based on the cached first order data; and obtaining the outbound call time of each delivery object based on the first order data corresponding to each delivery object and the corresponding delivery scenario.

[0011] In one embodiment, obtaining the outbound call time of each delivery object based on the first waybill data corresponding to each delivery object and the corresponding delivery scenario includes: obtaining outbound call prompt rules corresponding to each delivery scenario based on the delivery object; constructing prompt text based on the first waybill data corresponding to each delivery object and the outbound call prompt rules corresponding to each delivery scenario; and generating the outbound call time of the delivery object using a large language model based on the prompt text.

[0012] In one embodiment, before initiating an outbound call prompt to the delivery object using an interactive voice response system when the outbound call time for the delivery object arrives, the process includes: constructing a combined prompt information for the delivery object based on the first waybill data corresponding to the delivery object; the process of initiating an outbound call prompt to the delivery object using an interactive voice response system when the outbound call time for the delivery object arrives includes: initiating an outbound call prompt to the delivery object using an interactive voice response system based on the combined prompt information when the outbound call time for the delivery object arrives.

[0013] In one embodiment, before caching the first waybill data of the first waybill to be prompted when the waybill data indicates that the waybill to be prompted is a first waybill to be prompted that meets the prompt filtering conditions, the method includes: obtaining the timeout duration and delivery object corresponding to the waybill to be prompted based on the waybill data of the waybill to be prompted; and determining that the waybill to be prompted is a first waybill to be prompted that meets the prompt filtering conditions when the timeout duration corresponding to the waybill to be prompted is less than the timeout threshold and the number of first waybills to be prompted corresponding to the delivery object is less than the waybill quantity threshold.

[0014] In one embodiment, the first waybill data is cached in a first cache space; the method further includes: if the timeout duration corresponding to the waybill to be prompted is not less than a timeout threshold, determining that the waybill to be prompted is a second waybill to be prompted that does not meet the prompt filtering conditions; or, if the number of first waybills to be prompted corresponding to the delivery object is not less than a waybill quantity threshold, determining that the waybill to be prompted and the first waybill to be prompted of the delivery object are second waybills to be prompted that do not meet the prompt filtering conditions; caching the second waybill data corresponding to the second waybill to be prompted in a second cache space; obtaining the logistics outlet corresponding to each second waybill to be prompted based on the second waybill data in the second cache space; and initiating a message prompt to the management terminal of each logistics outlet based on the second waybill data corresponding to each logistics outlet.

[0015] In one embodiment, the method further includes: obtaining outbound call notification records and timeout durations corresponding to each of the first pending notification waybills; if the outbound call notification records of the first pending notification waybills indicate that the number of outbound call notifications for the first pending notification waybills is not less than a notification number threshold, or the timeout duration of the first pending notification waybills is not less than a timeout threshold, determining that the first pending notification waybills are second pending notification waybills that do not meet the notification filtering conditions, and migrating the second waybill data corresponding to the second pending notification waybills from the first cache space to the second cache space.

[0016] Secondly, this application also provides a waybill data processing apparatus, comprising:

[0017] The identifier calculation module is used to calculate the storage node identifier corresponding to the waybill to be prompted based on the waybill identifier of the waybill to be prompted.

[0018] The data acquisition module is used to acquire the waybill data corresponding to the waybill to be prompted from the storage node corresponding to the storage node identifier;

[0019] The first caching module is used to cache the first waybill data of the first waybill to be prompted when the waybill data indicates that the waybill to be prompted is a first waybill to be prompted that meets the prompting filtering conditions.

[0020] The outbound call decision module is used to obtain the outbound call time of the delivery object corresponding to each of the first order to be prompted based on the cached data of each of the first order.

[0021] The outbound call notification module is used to initiate an outbound call notification to the delivery recipient using an interactive voice response system when the outbound call time for the delivery recipient arrives.

[0022] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0023] Calculate the storage node identifier corresponding to the waybill to be prompted based on the waybill identifier of the waybill to be prompted.

[0024] Retrieve the waybill data corresponding to the waybill to be prompted from the storage node corresponding to the storage node identifier;

[0025] When the waybill data indicates that the waybill to be prompted is a first waybill to be prompted that meets the prompting filter conditions, the first waybill data of the first waybill to be prompted is cached.

[0026] Based on the cached data of each of the first waybills, the outbound call time of the delivery object corresponding to each of the first waybills to be notified is obtained;

[0027] When the outbound call time for the delivery recipient arrives, an outbound call notification is initiated to the delivery recipient using an interactive voice response system.

[0028] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0029] Calculate the storage node identifier corresponding to the waybill to be prompted based on the waybill identifier of the waybill to be prompted.

[0030] Retrieve the waybill data corresponding to the waybill to be prompted from the storage node corresponding to the storage node identifier;

[0031] When the waybill data indicates that the waybill to be prompted is a first waybill to be prompted that meets the prompting filter conditions, the first waybill data of the first waybill to be prompted is cached.

[0032] Based on the cached data of each of the first waybills, the outbound call time of the delivery object corresponding to each of the first waybills to be notified is obtained;

[0033] When the outbound call time for the delivery recipient arrives, an outbound call notification is initiated to the delivery recipient using an interactive voice response system.

[0034] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0035] Calculate the storage node identifier corresponding to the waybill to be prompted based on the waybill identifier of the waybill to be prompted.

[0036] Retrieve the waybill data corresponding to the waybill to be prompted from the storage node corresponding to the storage node identifier;

[0037] When the waybill data indicates that the waybill to be prompted is a first waybill to be prompted that meets the prompting filter conditions, the first waybill data of the first waybill to be prompted is cached.

[0038] Based on the cached data of each of the first waybills, the outbound call time of the delivery object corresponding to each of the first waybills to be notified is obtained;

[0039] When the outbound call time for the delivery recipient arrives, an outbound call notification is initiated to the delivery recipient using an interactive voice response system.

[0040] The aforementioned waybill data processing method, apparatus, computer equipment, computer-readable storage medium, and computer program product calculate the storage node identifier corresponding to the waybill to be prompted based on its waybill identifier, and retrieve the waybill data corresponding to the waybill to be prompted from the storage node corresponding to the storage node identifier. If the waybill data indicates that the waybill to be prompted is the first waybill to be prompted that meets the prompt filtering conditions, the first waybill data of the first waybill to be prompted is cached. Based on the cached first waybill data, the outbound call time for each delivery object corresponding to the first waybill to be prompted is obtained. Then, when the outbound call time for the delivery object arrives, an outbound call prompt is initiated to the delivery object using an interactive voice response system. This scheme, by utilizing the deterministic mapping relationship between waybill identifiers and storage node identifiers, distributes different waybill data into different storage nodes. When retrieving waybill data, it directly calculates the corresponding storage node identifier using the waybill identifier. Based on this deterministic mapping relationship and the sharded database architecture for waybill data storage, it can meet the real-time reading requirements of massive waybill data. Subsequently, by caching the first order data corresponding to the first order to be prompted that meets the prompt filtering conditions, the first order data can be read efficiently in the process of determining the outbound call time and triggering the outbound call prompt for each delivery object. This helps to improve the efficiency of obtaining the outbound call time and initiate the outbound call prompt to the delivery object within the effective time window, ensuring the timeliness of the prompt. Attached Figure Description

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

[0042] Figure 1 This is a flowchart illustrating a waybill data processing method in one embodiment;

[0043] Figure 2 This is a flowchart illustrating the process of obtaining the outbound call time for each delivery recipient in one embodiment;

[0044] Figure 3 This is a flowchart illustrating the process of initiating a message notification to the management terminal of a logistics network point in one embodiment;

[0045] Figure 4 This is a structural block diagram of a waybill data processing device in one embodiment;

[0046] Figure 5 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0047] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0048] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various objects, but these objects are not limited by these terms. These terms are only used to distinguish the first object from the second object. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0049] In one embodiment, such as Figure 1 As shown, a logistics message notification method is provided. This embodiment illustrates the method applied to a server, but it is understood that the method can also be applied to a terminal, or to a system including both a terminal and a server, and implemented through interaction between the terminal and the server. In this embodiment, the method includes the following steps:

[0050] Step S101: Calculate the storage node identifier corresponding to the waybill to be prompted based on the waybill identifier of the waybill to be prompted.

[0051] Among them, the waybill to be notified can be a waybill with time-sensitive risks in the logistics and distribution process. For example, it can be a waybill that has not been processed after the waybill processing deadline. The waybill identifier of the waybill to be notified can be the waybill number of the waybill.

[0052] The waybill data of logistics organizations can be stored based on a sharded database architecture. When storing waybill data, a routing key value can be generated by hashing the waybill identifier, and the shard instance (i.e., storage node) where the data is written can be determined based on this routing key value. Therefore, in this step, the storage node identifier corresponding to the waybill to be notified can be obtained by hashing the waybill identifier and using the calculated routing key value. This storage node identifier indicates the storage node where the waybill data to be notified is stored.

[0053] Step S102: Obtain the waybill data corresponding to the waybill to be prompted from the storage node corresponding to the storage node identifier.

[0054] Specifically, based on the storage node identifier, the pre-stored waybill data corresponding to the waybill to be prompted can be retrieved from the corresponding storage node. For example, the waybill data for each waybill may include information such as the waybill identifier, delivery object identifier, delivery scenario identifier, and waybill processing deadline.

[0055] Step S103: If the waybill data indicates that the waybill to be prompted is the first waybill to be prompted that meets the prompt filtering conditions, cache the first waybill data of the first waybill to be prompted.

[0056] The prompt filtering criteria can be used to distinguish different types of pending prompts for waybills. Based on the waybill data, it can determine whether a waybill requires an outbound call notification to the recipient. For example, the prompt filtering criteria may include a judgment condition based on a preset timeout threshold. The server can obtain the timeout duration corresponding to the pending prompts for the waybill based on the time interval between the waybill processing deadline and the current time contained in the waybill data. If the timeout duration is less than the preset timeout threshold, the server determines that the pending prompts for the waybill is the first pending prompts for the waybill that meets the prompt filtering criteria.

[0057] In the case where it is determined that the waybill to be prompted is the first waybill to be prompted, its corresponding first waybill data can be cached in a preset cache space. This cache space can be used as a data pool to cache multiple first waybill data.

[0058] Step S104: Based on the cached first waybill data, obtain the outbound call time of the delivery object corresponding to each first waybill to be prompted.

[0059] Specifically, based on the delivery object identifier contained in each cached first waybill data, the delivery object corresponding to each first pending notification waybill can be determined. Then, the first waybill data can be aggregated at the delivery object level to obtain the first waybill data corresponding to one or more first pending notification waybills for each delivery object. Furthermore, based on the first waybill data corresponding to each delivery object, the outbound call time corresponding to each delivery object can be determined; this outbound call time can be the time when an outbound call notification is initiated to the delivery object. For example, the first waybill data in the cache space can be processed periodically according to a preset notification cycle (e.g., 10 minutes), and the outbound call time for the corresponding delivery object can be determined based on all the first waybill data cached at the end of each notification cycle.

[0060] For example, the prompt priority of each delivery object can be determined based on the first waybill data corresponding to each delivery object, and the outbound call time of each delivery object can be determined sequentially within a preset prompt time period according to the prompt priority in descending order. For example, the prompt priority of each delivery object can be obtained according to the number of first waybills to be prompted corresponding to each delivery object in descending order.

[0061] For example, a large language model can be used to infer the outbound call time for each delivery object based on the first waybill data corresponding to each delivery object. Specifically, structured prompt words can be used to organize the outbound call prompt rules and the first waybill data corresponding to the delivery object into prompt text for the large language model. This prompt text is then input into the large language model, guiding it to infer the outbound call time for the delivery object based on the first waybill data, under the constraints of the outbound call prompt rules. The outbound call prompt rules can be rules for configuring the outbound call time, such as including prompt priorities corresponding to different data characteristics of the first waybill data.

[0062] Step S105: When the outbound call time for the delivery recipient arrives, initiate an outbound call notification to the delivery recipient using the interactive voice response system.

[0063] Specifically, when the outbound call time for each delivery recipient arrives, the Interactive Voice Response (IVR) system can be triggered to initiate a call to the communication terminal associated with the delivery recipient, and output voice prompt information to the communication terminal after the call is connected. This voice prompt information can be used to provide batch notifications for the first batch of pending delivery orders for that delivery recipient, such as indicating the total number of the first batch of pending delivery orders.

[0064] In the aforementioned waybill data processing method, by utilizing the deterministic mapping relationship between waybill identifiers and storage node identifiers, different waybill data are distributed and written to different storage nodes. When retrieving waybill data, the corresponding storage node identifier is directly calculated using the waybill identifier. Based on this deterministic mapping relationship and the sharded database architecture for waybill data storage, the real-time reading requirements for massive amounts of waybill data can be met. Furthermore, by caching the first waybill data corresponding to the first waybill to be prompted that meets the prompt filtering conditions, the first waybill data can be efficiently read during the subsequent determination of the outbound call time for each delivery object and the triggering of the outbound call prompt. This improves the efficiency of obtaining the outbound call time and ensures that the outbound call prompt to the delivery object is initiated within the effective time window, guaranteeing the timeliness of the prompt.

[0065] In an exemplary embodiment, obtaining the outbound call time of the delivery object corresponding to each first pending notification waybill based on the cached first waybill data may include: obtaining the delivery object and delivery scenario corresponding to each first pending notification waybill based on the cached first waybill data; and obtaining the outbound call time of each delivery object based on the first waybill data corresponding to each delivery object and the corresponding delivery scenario.

[0066] Specifically, the first waybill data may include information such as the waybill identifier, delivery object identifier, delivery scenario identifier, and waybill processing deadline corresponding to the first waybill to be notified. Among them, the delivery object identifier can be used to determine the delivery object corresponding to the first waybill to be notified; and the delivery scenario identifier can be used to determine the delivery scenario corresponding to the first waybill to be notified.

[0067] Subsequently, the outbound call time for each delivery object can be obtained based on the first waybill data corresponding to each delivery object and the delivery scenario involved. For example, different delivery scenarios can correspond to different scenario importance levels. Therefore, based on the distribution of the number of first-to-be-notified waybills (i.e., the number of first waybill data) corresponding to different delivery scenarios for each delivery object, the notification priority for each delivery object can be obtained. Then, based on the notification priority from high to low, the outbound call time for each delivery object can be determined sequentially within a preset notification period. For example, different delivery scenarios can also correspond to different outbound call notification rules. Therefore, by combining the outbound call notification rules corresponding to the delivery scenarios involved in the first waybill data of each delivery object, a general notification rule for setting the outbound call time for that delivery object can be obtained. Then, by combining the general notification rule corresponding to each delivery object, the outbound call time for each delivery object can be determined within a preset notification period.

[0068] In this embodiment, by reasoning about the outbound call time of the delivery object based on the data of each first waybill corresponding to the delivery object and the delivery scenario involved, the timeliness characteristics of the delivery scenario of each first waybill to be reminded corresponding to the delivery object can be fully considered, and a more accurate outbound call time can be obtained.

[0069] In one exemplary embodiment, such as Figure 2 As shown, based on the first waybill data corresponding to each delivery recipient and the corresponding delivery scenario, the outbound call time for each delivery recipient can be obtained, which may include:

[0070] Step S201: Based on the delivery scenarios corresponding to the delivery objects, obtain the outbound call prompt rules corresponding to each delivery scenario.

[0071] Each delivery scenario of a logistics waybill can correspond to a preset outbound call notification rule. In this step, the outbound call notification rules corresponding to each delivery scenario involved in each first unnotified waybill corresponding to the delivery object can be obtained. These outbound call notification rules can be rules used to configure outbound call times, such as the correspondence between the delivery scenario and the notification priority of the delivery object, and specific time configuration strategies corresponding to different quantity levels or different timeout duration levels of the first unnotified waybills corresponding to the delivery scenario.

[0072] Step S202: Construct a prompt text based on the first waybill data corresponding to each delivery object and the outbound call prompt rules corresponding to each delivery scenario.

[0073] Specifically, based on the first waybill data corresponding to each delivery object and the outbound call prompting rules corresponding to the delivery scenarios of each first waybill to be prompted for that delivery object, prompt text for input into the large language model can be constructed. This prompt text can be structured prompt information containing the first waybill data and the outbound call prompting rules.

[0074] Step S203: Based on the prompt text, use a large language model to generate the outbound call time for the delivery object.

[0075] Specifically, the prompt text corresponding to the delivery recipient can be input into the large language model. This prompt text guides the large language model, under the constraints of one or more outbound call prompt rules, to infer the outbound call time of the delivery recipient based on the first waybill data corresponding to that recipient. Alternatively, the prompt texts of multiple delivery recipients can be integrated into batch data and input into the large language model, allowing the large language model to perform batch inference of the outbound call time for each delivery recipient.

[0076] In this embodiment, by constructing prompt text based on the first waybill data corresponding to the delivery object and the outbound prompt rules corresponding to each delivery scenario, and then using a large language model to infer the outbound call time of the delivery object based on the prompt text, the accuracy and efficiency of outbound call time inference can be improved.

[0077] In an exemplary embodiment, before initiating an outbound call prompt to the delivery object using the interactive voice response system when the outbound call time for the delivery object arrives, the process includes: constructing a combined prompt information for the delivery object based on the first waybill data corresponding to the delivery object; and initiating an outbound call prompt to the delivery object using the interactive voice response system when the outbound call time for the delivery object arrives, the process includes: initiating an outbound call prompt to the delivery object based on the combined prompt information using the interactive voice response system when the outbound call time for the delivery object arrives.

[0078] The merge prompt information can be used to describe the overall situation of all the first pending prompt orders corresponding to the delivery object. For example, it can include the statistical results of the data of each of the first pending prompt orders corresponding to the delivery object. For example, the statistical results of the first pending prompt orders can include, but are not limited to, the total number of orders, the number of orders for each delivery scenario, and the overall timeout situation. For example, the statistical results of each of the first orders corresponding to the delivery object can be obtained by first statistically analyzing the data, and then the statistical results can be filled into a preset merge prompt template to construct the merge prompt information for the delivery object. For example, the data of each of the first orders corresponding to the delivery object can also be input into a large language model, and prompt words can be used to guide the large language model to summarize the data of each of the first orders and generate the merge prompt information for the delivery object.

[0079] Specifically, when the outbound call time for the delivery recipient arrives, the interactive voice response system can be triggered to initiate a call to the communication terminal associated with the delivery recipient, and after the call is connected, a voice prompt message corresponding to the combined prompt message will be output to the communication terminal.

[0080] In this embodiment, by constructing a combined prompt information for the delivery object and initiating an outbound call prompt to the delivery object based on this information, the amount of data that the interactive voice response system needs to transmit and process can be reduced, which is beneficial to improving the efficiency of outbound call prompts.

[0081] In an exemplary embodiment, before caching the first waybill data of the first waybill to be prompted, if the waybill data indicates that the waybill to be prompted is the first waybill to be prompted that meets the prompt filtering conditions, the following steps may be included: obtaining the timeout duration and delivery object corresponding to the waybill to be prompted based on the waybill data of the waybill to be prompted; and determining that the waybill to be prompted is the first waybill to be prompted that meets the prompt filtering conditions if the timeout duration corresponding to the waybill to be prompted is less than the timeout threshold and the number of first waybills to be prompted corresponding to the delivery object is less than the waybill quantity threshold.

[0082] Specifically, the data for a pending delivery order may include information such as the order identifier, the recipient identifier, the delivery scenario identifier, and the order processing deadline. The time interval between the order processing deadline and the current time determines the timeout duration for the pending delivery order, and the recipient identifier identifies the corresponding recipient.

[0083] For example, the prompt filtering conditions may include a first filtering condition based on the timeout duration and a second filtering condition based on the number of first pending prompt orders for the same delivery object. Specifically, the timeout duration corresponding to the pending prompt order can be compared with a preset timeout threshold. If the timeout duration is less than the timeout threshold, the pending prompt order is determined to meet the first filtering condition. Simultaneously, based on the delivery object identifier corresponding to the pending prompt order, the number of first pending prompt orders for that delivery object in the cache space can be queried. If this number is less than a preset order quantity threshold (e.g., 20), the pending prompt order is determined to meet the second filtering condition.

[0084] If a waybill to be prompted meets both the first and second screening conditions, it can be determined that the waybill to be prompted is the first waybill to be prompted that meets the prompt screening conditions.

[0085] In this embodiment, by filtering the order to be reminded based on the timeout duration and the number of the first order to be reminded for the same delivery object, the number of the first order to be reminded and the timeout level for each delivery object can be controlled, which helps to improve the effectiveness of outbound call reminders to delivery objects.

[0086] In one exemplary embodiment, the first waybill data is cached in the first cache space; such as Figure 3 As shown, the method may further include:

[0087] Step S301: If the timeout duration corresponding to the waybill to be prompted is not less than the timeout threshold, determine the waybill to be prompted as the second waybill to be prompted that does not meet the prompting filtering conditions; or, if the number of the first waybill to be prompted for the delivery object corresponding to the waybill to be prompted is not less than the waybill quantity threshold, determine the waybill to be prompted and the first waybill to be prompted for the delivery object as the second waybill to be prompted that does not meet the prompting filtering conditions.

[0088] The second waybill to be notified can be a waybill that requires notification from the warehouse staff of the corresponding logistics point. The corresponding logistics point can be the logistics point to which the delivery recipient belongs.

[0089] For example, the prompt filtering conditions may include a first filtering condition based on the timeout duration and a second filtering condition based on the number of first pending prompt orders for the same delivery object. Specifically, the timeout duration corresponding to the pending prompt order can be compared with a preset timeout threshold. If the timeout duration is not less than the timeout threshold, the pending prompt order can be determined to not meet the first filtering condition. Simultaneously, based on the delivery object identifier corresponding to the pending prompt order, the number of first pending prompt orders for that delivery object in the cache space can be queried. If this number is not less than a preset order quantity threshold (e.g., 20), the pending prompt order can be determined to not meet the second filtering condition. If the pending prompt order does not meet at least one of the first and second filtering conditions, the pending prompt order can be determined to be a second pending prompt order that does not meet the prompt filtering conditions.

[0090] Specifically, when the pending prompt order does not meet the second screening condition, that is, when the number of the first pending prompt orders for the delivery object corresponding to the order is not less than the preset order quantity threshold, it can be determined that the first pending prompt order corresponding to the delivery object is also a second pending prompt order that does not meet the prompt screening condition.

[0091] Step S302: Cache the second waybill data corresponding to the second waybill to be prompted in the second cache space.

[0092] The first waybill data corresponding to the first waybill to be prompted can be cached in the first cache space, and the second waybill data corresponding to the second waybill to be prompted can be cached in the second cache space. The first cache space and the second cache space can be two independent cache spaces, which can respectively constitute a first data pool for temporarily storing the first waybill data and a second data pool for temporarily storing the second waybill data.

[0093] Specifically, for the second pending waybill identified in the aforementioned steps, the second waybill data corresponding to that waybill can be cached in the second cache space. Furthermore, for waybills identified as second pending waybills because they do not meet the second filtering criteria, the second waybill data (i.e., the original first waybill data) of that waybill can be transferred from the first cache space to the second cache space.

[0094] Step S303: Based on the second waybill data in the second cache space, obtain the logistics outlet corresponding to each second waybill to be prompted.

[0095] Specifically, based on the delivery object identifier contained in each second waybill data in the second cache space, the delivery object corresponding to each second waybill to be prompted can be determined, and the logistics network point to which the delivery object belongs can be used as the logistics network point corresponding to the second waybill to be prompted.

[0096] Step S304: Based on the second waybill data corresponding to each logistics outlet, send a message notification to the management terminal of each logistics outlet.

[0097] Specifically, the system can aggregate second-pending waybills at the logistics network point level to obtain second-pending waybill data for each logistics network point. Then, a message notification can be sent to the management terminal of each logistics network point. This could be done by sending a notification message to the management terminal, or by using an interactive voice response system to make a call to the management terminal and outputting a voice notification message after the call is connected. This notification message can be used to remind users of each second-pending waybill at the logistics network point. The management terminal can be a terminal device associated with the warehouse management personnel of the logistics network point.

[0098] In this embodiment, by setting up independent first and second cache spaces, the second waybill data corresponding to the second waybill that does not meet the prompt filtering conditions is stored in the second cache space. This avoids mixed caching of first and second waybill data, which is beneficial to improving the data reading efficiency of different prompting tasks. Furthermore, by sending a message prompt to the management terminal of each logistics network based on the second waybill data corresponding to that network, the warehouse staff of the logistics network can promptly grasp the relevant information of the second waybill to be prompted, which is conducive to the timely processing of these waybills.

[0099] In an exemplary embodiment, the method may further include: obtaining outbound call notification records and timeout durations corresponding to each of the first pending notification waybills; and obtaining the timeout durations corresponding to each of the first pending notification waybills; and, if the outbound call notification records of the first pending notification waybills indicate that the number of outbound call notifications for the first pending notification waybills is not less than a notification frequency threshold, or if the timeout duration of the first pending notification waybills is not less than a timeout threshold, determining that the first pending notification waybills are second pending notification waybills that do not meet the notification filtering conditions, and migrating the second waybill data corresponding to the second pending notification waybills from the first cache space to the second cache space.

[0100] Specifically, for each first pending waybill, its corresponding outbound call notification record and timeout duration can be obtained. The outbound call notification record can include information about outbound call notifications already initiated for the first pending waybill; based on this record, the number of outbound call notifications initiated for the first pending waybill can be determined. Furthermore, based on the time interval between the waybill processing deadline and the current time contained in the first waybill data corresponding to the first pending waybill, the timeout duration for the first pending waybill can be obtained.

[0101] The filtering criteria can include a first filtering criterion based on timeout duration and a third filtering criterion based on the number of outbound call notifications. Specifically, the timeout duration corresponding to the first pending order can be compared with a preset timeout threshold. If the timeout duration is less than the threshold, the first pending order is determined to meet the first filtering criterion; otherwise, it is determined that the first pending order does not meet the first filtering criterion. Simultaneously, the number of outbound call notifications corresponding to the first pending order can be compared with a preset notification number threshold. If the number of outbound call notifications is less than the notification number threshold, the first pending order is determined to meet the third filtering criterion; otherwise, it is determined that the first pending order does not meet the third filtering criterion.

[0102] Specifically, when a first pending waybill meets both the first and third filtering conditions, it can be determined that the first pending waybill meets the filtering conditions, and the first waybill data corresponding to the first pending waybill can continue to be temporarily stored in the first cache space. Conversely, when a first pending waybill does not meet at least one of the first and third filtering conditions, it can be determined that the first pending waybill is a second pending waybill that does not meet the filtering conditions, and the second waybill data (the original first waybill data) corresponding to the second pending waybill can be migrated from the first cache space to the second cache space.

[0103] In this embodiment, by checking the timeout duration and number of outbound call prompts of the first waybill data in the first cache space, and migrating the first waybill data that does not meet the conditions to the second cache space, it is possible to avoid the data of the first waybill to be prompted remaining in the first cache space if the timeout is too long or if it has not been processed after multiple reminders. This helps to release the available capacity of the first cache space and ensures that the corresponding waybill to be prompted can be processed by prompting the warehouse staff.

[0104] In one exemplary embodiment, a waybill data processing method is provided.

[0105] Specifically, the waybill data processing method in this embodiment can include three parts: data acquisition, data transmission, and task triggering. The data acquisition part is triggered before the data transmission and task triggering parts to ensure that the waybill data in the cache is up-to-date. The waybill data of the logistics organization can be stored based on a sharded database architecture. When storing waybill data, a routing key value can be generated by hashing the waybill identifier, and the sharded database instance (i.e., storage node) to which the data is written can be determined based on this routing key value.

[0106] In the data acquisition section, the storage node identifier corresponding to the abnormal waybill can be calculated based on the waybill identifier, and the waybill data corresponding to the abnormal waybill can be obtained from the storage node corresponding to the storage node identifier. Subsequently, based on the waybill data corresponding to the abnormal waybill, the abnormal waybill can be filtered using filtering logic corresponding to different delivery scenarios to obtain the waybills to be prompted that need to be prompted to the delivery recipient or warehouse personnel at the logistics network. Specifically, based on the prompt filtering conditions, the waybills to be prompted can be divided into two categories: first, the first waybill to be prompted that needs to be prompted to the delivery recipient (timeout duration less than the timeout threshold and the number of first waybills to be prompted corresponding to the delivery recipient is less than the waybill volume threshold); and second, the second waybill to be prompted that needs to be prompted to warehouse personnel (timeout duration not less than the timeout threshold, or the number of first waybills to be prompted corresponding to the delivery recipient is not less than the waybill volume threshold). The first waybill data corresponding to the first waybill to be prompted and the second waybill data corresponding to the second waybill to be prompted can be cached in a first data pool and a second data pool, respectively, with the two data pools corresponding to independent cache spaces.

[0107] In the data transmission section, old data (i.e., first-order data that has already received outbound call notifications) can be retrieved from the first data pool. It is then determined whether the number of outbound call notifications for each first-order order to be notified corresponding to the old data is less than the notification frequency threshold, and whether the timeout duration for each first-order order to be notified is less than the timeout threshold. If the number of outbound call notifications for the first-order order to be notified corresponding to the old data is not less than the notification frequency threshold, or the timeout duration is not less than the timeout threshold, the first-order order to be notified can be used as the second-order order to be notified, and its corresponding order data can be used as the second-order order data, migrating it from the first data pool to the second data pool. New data (newly cached first-order order data in the first data pool) can also be compared with the old data, using the order identifier and delivery scenario identifier as data identifiers. If new data with matching data identifiers exists, the new data is deleted; otherwise, the old data is deleted. After filtering the data in the first data pool, a large language model can be provided for inference of outbound call times, with each batch consisting of 30 delivery objects. Specifically, prompt text can be constructed based on the first waybill data corresponding to each delivery object and the prompt logic (i.e., outbound call prompt rules) corresponding to each delivery scenario. Then, a large language model is used to infer the outbound call time for each delivery object based on this prompt text. The order of outbound call times for different delivery objects can be determined based on the importance level of the delivery scenario involved in the first waybill to be prompted for each delivery object.

[0108] The triggering task section can include tasks to call the delivery recipient and tasks to call the warehouse manager. Specifically, based on the first waybill data corresponding to each delivery recipient, a combined notification message for the delivery recipient can be constructed. When the outbound call time for that delivery recipient arrives, an interactive voice response system can be used to initiate an outbound call notification to that delivery recipient based on this combined notification message. Furthermore, the interactive voice response system can also be used to send message notifications to the management terminal of the logistics network point based on the second waybill data corresponding to each logistics network point.

[0109] In this embodiment, by utilizing a sharded database architecture to store waybill data and employing waybill identifier hash routing to distribute the data across multiple database instances, the performance limitations of a single database can be overcome, improving the read / write throughput of waybill data and meeting the high real-time read requirements of real-time intelligent outbound call tasks. Simultaneously, by caching the first and second waybill data separately, the data read / write efficiency during the process of alerting abnormal logistics data can be further improved. This allows subsequent processing flows to efficiently obtain the necessary waybill data corresponding to the waybill to be alerted and initiate alerts within the effective time window, ensuring timely alerts. Furthermore, this embodiment categorizes waybills to be alerted into first-level waybills requiring outbound call alerts to the delivery recipient and second-level waybills requiring alerts to warehouse personnel based on factors such as timeout duration, number of outbound call alerts, and the number of first-level waybills to be alerted corresponding to the same delivery object. This allows for targeted alerts for waybills with different time-sensitive risks, facilitating timely processing of each waybill to be alerted. By making decisions on the outbound call time for the first pending waybill and constructing merged reminder information, the success rate of outbound call reminder tasks can be improved, ensuring that the delivery recipient can pay attention to the corresponding waybill and process it in a timely manner, which is conducive to improving the timeliness of waybill processing.

[0110] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0111] Based on the same inventive concept, this application also provides a waybill data processing apparatus for implementing the waybill data processing method described above. The solution provided by this apparatus is similar to the implementation described in the above method; therefore, the specific limitations in one or more waybill data processing apparatus embodiments provided below can be found in the limitations of the waybill data processing method described above, and will not be repeated here.

[0112] In one exemplary embodiment, such as Figure 4As shown, a waybill data processing device is provided, comprising:

[0113] The identifier calculation module 401 is used to calculate the storage node identifier corresponding to the waybill to be prompted based on the waybill identifier of the waybill to be prompted.

[0114] Data acquisition module 402 is used to acquire the waybill data corresponding to the waybill to be prompted from the storage node corresponding to the storage node identifier;

[0115] The first caching module 403 is used to cache the first waybill data of the first waybill to be prompted when the waybill data indicates that the waybill to be prompted is a first waybill to be prompted that meets the prompting filtering conditions.

[0116] The outbound call decision module 404 is used to obtain the outbound call time of the delivery object corresponding to each of the first order to be prompted based on the cached data of each of the first order.

[0117] The outbound call prompt module 405 is used to initiate an outbound call prompt to the delivery recipient using an interactive voice response system when the outbound call time for the delivery recipient arrives.

[0118] In an exemplary embodiment, the outbound call decision module 404 is configured to: obtain the delivery object and delivery scenario corresponding to each of the first order to be prompted based on the cached first order data; and obtain the outbound call time for each delivery object based on the first order data corresponding to each delivery object and the corresponding delivery scenario.

[0119] In an exemplary embodiment, the outbound call decision module 404 is configured to: obtain outbound call prompt rules corresponding to each of the delivery scenarios corresponding to the delivery object; construct prompt text based on each of the first waybill data corresponding to each delivery object and the outbound call prompt rules corresponding to each delivery scenario; and generate the outbound call time of the delivery object using a large language model based on the prompt text.

[0120] In an exemplary embodiment, the apparatus further includes: an information construction module, configured to construct a combined prompt information for the delivery object based on the first waybill data corresponding to the delivery object; and an outbound call prompt module 405, configured to: initiate an outbound call prompt to the delivery object based on the combined prompt information using an interactive voice response system when the outbound call time for the delivery object arrives.

[0121] In an exemplary embodiment, the device further includes: a first acquisition module, configured to obtain the timeout duration and delivery object corresponding to the waybill to be prompted based on the waybill data; and a first filtering module, configured to determine the waybill to be prompted as a first waybill to be prompted that meets the prompt filtering conditions when the timeout duration corresponding to the waybill to be prompted is less than a timeout threshold and the number of first waybills to be prompted corresponding to the delivery object is less than a waybill quantity threshold.

[0122] In an exemplary embodiment, the first waybill data is cached in a first cache space; the device further includes: a second filtering module, configured to determine that the waybill to be prompted is a second waybill to be prompted that does not meet the prompt filtering conditions if the timeout duration corresponding to the waybill to be prompted is not less than a timeout threshold; or, to determine that the waybill to be prompted and the first waybill to be prompted of the delivery object corresponding to the waybill to be prompted are second waybill to be prompted that does not meet the prompt filtering conditions if the number of first waybill to be prompted of the delivery object corresponding to the waybill to be prompted is not less than a waybill quantity threshold; a second caching module, configured to cache the second waybill data corresponding to the second waybill to be prompted in a second cache space; a network point acquisition module, configured to obtain the logistics network point corresponding to each second waybill to be prompted based on the second waybill data in the second cache space; and a message prompting module, configured to initiate a message prompt to the management terminal of each logistics network point based on the second waybill data corresponding to each logistics network point.

[0123] In an exemplary embodiment, the apparatus further includes: a second acquisition module, configured to acquire outbound call notification records and timeout durations corresponding to each of the first pending notification waybills; and a data migration module, configured to determine that the first pending notification waybill is a second pending notification waybill that does not meet the notification filtering conditions, and to migrate the second waybill data corresponding to the second pending notification waybill from the first cache space to the second cache space, when the outbound call notification records of the first pending notification waybill indicate that the number of outbound call notifications for the first pending notification waybill is not less than a notification number threshold, or the timeout duration of the first pending notification waybill is not less than a timeout threshold.

[0124] Each module in the aforementioned waybill data processing device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the operations corresponding to each module.

[0125] In one exemplary embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 5As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operating system and computer programs stored in the non-volatile storage media. The database stores data such as the waybill identifier for pending waybills. The I / O interfaces are used for information exchange between the processor and external devices. The communication interface is used for communication with external terminals via a network connection. When the computer program is executed by the processor, it implements a waybill data processing method.

[0126] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0127] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above method embodiments.

[0128] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0129] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0130] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0131] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0132] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0133] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A waybill data processing method characterized by, The method includes: Calculate the storage node identifier corresponding to the waybill to be prompted based on the waybill identifier of the waybill to be prompted. Retrieve the waybill data corresponding to the waybill to be prompted from the storage node corresponding to the storage node identifier; When the waybill data indicates that the waybill to be prompted is a first waybill to be prompted that meets the prompting filter conditions, the first waybill data of the first waybill to be prompted is cached. Based on the cached data of each of the first waybills, the outbound call time of the delivery object corresponding to each of the first waybills to be notified is obtained; When the outbound call time for the delivery recipient arrives, an outbound call notification is initiated to the delivery recipient using an interactive voice response system.

2. The method of claim 1, wherein, The step of obtaining the outbound call time for each of the first order to be notified, based on the cached data of each of the first order, includes: Based on the cached data of each of the first waybills, the delivery object and delivery scenario corresponding to each of the first waybills to be notified are obtained; Based on the first waybill data corresponding to each of the delivery objects and the corresponding delivery scenario, the outbound call time of each of the delivery objects is obtained.

3. The method of claim 2, wherein, The step of obtaining the outbound call time for each delivery object based on the first waybill data corresponding to each delivery object and the corresponding delivery scenario includes: Based on the delivery scenarios corresponding to the delivery objects, obtain the outbound call prompt rules corresponding to each delivery scenario; Based on the first waybill data corresponding to each of the delivery objects and the outbound call prompt rules corresponding to each of the delivery scenarios, construct the prompt text; Based on the prompt text, the outbound call time for the delivery recipient is generated using a large language model.

4. The method of claim 1, wherein, Before initiating an outbound call notification to the delivery recipient using an interactive voice response system when the outbound call time for the delivery recipient arrives, the process includes: Based on the data of each of the first waybills corresponding to the delivery object, construct the merged prompt information for the delivery object; When the outbound call time for the delivery recipient arrives, the method of initiating an outbound call notification to the delivery recipient using an interactive voice response system includes: When the outbound call time for the delivery recipient arrives, an outbound call prompt is initiated to the delivery recipient using an interactive voice response system based on the merged prompt information.

5. The method according to any one of claims 1 to 4, characterized in that, Before caching the first waybill data of the first waybill to be prompted when the waybill data indicates that the waybill to be prompted is a first waybill to be prompted that meets the prompt filtering conditions, the following steps are included: Based on the waybill data of the waybill to be notified, the timeout duration and delivery object corresponding to the waybill to be notified are obtained; If the timeout duration corresponding to the waybill to be prompted is less than the timeout threshold, and the number of first waybills to be prompted corresponding to the delivery object is less than the waybill quantity threshold, then the waybill to be prompted is determined to be the first waybill to be prompted that meets the prompt filtering conditions.

6. The method of claim 5, wherein, The first waybill data is cached in the first cache space; The method further includes: If the timeout duration corresponding to the waybill to be prompted is not less than the timeout threshold, the waybill to be prompted is determined to be the second waybill to be prompted that does not meet the prompting screening conditions; Alternatively, if the number of first pending prompting waybills corresponding to the delivery object of the pending prompting waybill is not less than the waybill volume threshold, the pending prompting waybill and the first pending prompting waybill of the delivery object are determined to be second pending prompting waybills that do not meet the prompting filtering conditions. The second waybill data corresponding to the second waybill to be prompted is cached in the second cache space; Based on the second waybill data in the second cache space, the logistics outlets corresponding to each second waybill to be prompted are obtained; Based on the second waybill data corresponding to each of the logistics outlets, a message notification is sent to the management terminal of each of the logistics outlets.

7. The method of claim 6, wherein, The method further includes: Obtain the outbound call notification records and timeout durations corresponding to each of the first pending waybills; If the outbound call notification record of the first pending notification waybill indicates that the number of outbound call notifications for the first pending notification waybill is not less than the notification number threshold, or if the timeout duration of the first pending notification waybill is not less than the timeout threshold, then the first pending notification waybill is determined to be a second pending notification waybill that does not meet the notification filtering conditions, and the second waybill data corresponding to the second pending notification waybill is migrated from the first cache space to the second cache space. 8.A computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer device is configured to perform the method according to any one of claims 1-7. When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

9. A computer-readable storage medium having stored thereon a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer program product comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images