Data processing method and device, equipment, storage medium and program product

Abstract

The embodiment of the invention provides a data processing method which is implemented at a distribution control system. The method comprises the following steps: receiving first waybill information of a to-be-checked object, wherein the first waybill information indicates attribute information and state information of the object; based on a checking strategy, a checking task for the object is generated, the checking strategy is determined at least based on the first waybill information, and the checking task indicates that the first waybill information is checked within first preset time; in response to determining that the first waybill information is not checked, generating a first state mark for the first waybill information, the first state mark indicating that the first waybill information needs to be checked; and sending the inventory task and the first state mark to the distribution station to request the distribution station to execute the inventory task. Through the mode of generating the inventory task based on the inventory strategy and processing the data in the automatic process, manual operation is reduced, the inventory working process is simplified, and the data processing efficiency is improved.

Description

Technical Field

[0001] The exemplary embodiments disclosed herein relate generally to the field of computers, and more specifically to data processing methods, apparatus, devices, computer-readable storage media, and computer program products. Background Technology

[0002] In the field of logistics and warehousing management, it is often necessary to regularly inventory parcels and other items in stock and process related data to ensure the accuracy of inventory information, thereby supporting the efficient operation of the distribution system.

[0003] In related technologies, the methods for object inventory and data processing mainly rely on manual operation. Operations personnel need to manually export the data of the objects to be inventoried, generate an inventory list, and then delivery personnel scan each object, recording and reporting discrepancies. This method typically requires a significant investment of manpower and time, and the repeated manual operations are prone to introducing human error, leading to low accuracy in the inventory results. Furthermore, headquarters or control systems struggle to achieve real-time monitoring of inventory tasks and data at each site, making it difficult to quickly detect and handle anomalies.

[0004] Therefore, a more automated and intelligent data processing solution is needed to improve the efficiency and accuracy of inventory work. Summary of the Invention

[0005] In a first aspect of this disclosure, a data processing method implemented at a delivery control system is provided. The method includes: receiving first waybill information of an object to be inventoried, the first waybill information indicating attribute information and status information of the object; generating an inventory task for the object based on an inventory strategy, the inventory strategy being determined at least based on the first waybill information, the inventory task indicating that the first waybill information should be inventoried within a first predetermined time; in response to determining that the first waybill information has not been inventoried, generating a first status flag for the first waybill information, the first status flag indicating that the first waybill information needs to be inventoried; and sending the inventory task and the first status flag to a delivery station to request the delivery station to perform the inventory task.

[0006] In a second aspect of this disclosure, a data processing method implemented at a delivery terminal device is provided. The method includes: receiving an inventory task for an object to be inventoried and a first status flag, the inventory task indicating that first waybill information of the object needs to be inventoried within a first predetermined time period, the first waybill information indicating attribute information and status information of the object, and the first status flag indicating that the first waybill information needs to be inventoried; and executing the inventory task, wherein the inventory task includes: obtaining second waybill information of the object through the object's information identifier; determining whether the first waybill information and the second waybill information match; in response to the first waybill information and the second waybill information matching, generating a second status flag for the first waybill information and the second waybill information, the second status flag indicating that the first waybill information and the second waybill information match; and in response to the first waybill information and the second waybill information not matching, generating a third status flag for the first waybill information and the second waybill information, the third status flag indicating that the first waybill information and the second waybill information do not match.

[0007] In a third aspect of this disclosure, a data processing apparatus implemented at a delivery control system is provided. The apparatus includes: a receiving module configured to receive first waybill information of an object to be inventoried, the first waybill information indicating attribute information and status information of the object; a task generation module configured to generate an inventory task for the object based on an inventory strategy, the inventory strategy being determined at least based on the first waybill information, the inventory task indicating that the first waybill information should be inventoried within a first predetermined time; a status flag generation module configured to generate a first status flag for the first waybill information in response to determining that the first waybill information has not been inventoried, the first status flag indicating that the first waybill information needs to be inventoried; and a sending module configured to send the inventory task and the first status flag to a delivery station to request the delivery station to perform the inventory task.

[0008] In a fourth aspect of this disclosure, a data processing apparatus implemented at a delivery terminal device is provided. The apparatus includes: a receiving module configured to receive an inventory task for an object to be inventoried and a first status flag, the inventory task indicating that first waybill information of the object needs to be inventoried within a first predetermined time period, the first waybill information indicating attribute information and status information of the object, and the first status flag indicating that the first waybill information needs to be inventoried; and an execution module configured to execute the inventory task, wherein the inventory task includes: obtaining second waybill information of the object through an information identifier of the object; determining whether the first waybill information and the second waybill information match; in response to the first waybill information and the second waybill information matching, generating a second status flag for the first waybill information and the second waybill information, the second status flag indicating that the first waybill information and the second waybill information match; and in response to the first waybill information and the second waybill information not matching, generating a third status flag for the first waybill information and the second waybill information, the third status flag indicating that the first waybill information and the second waybill information do not match.

[0009] In a fifth aspect of this disclosure, an electronic device is provided. The electronic device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method of the first aspect of this disclosure or the method of the second aspect of this disclosure when executed by the at least one processing unit.

[0010] In a sixth aspect of this disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program that can be executed by a processor to perform the method according to the first aspect of this disclosure or the method according to the second aspect of this disclosure.

[0011] In a seventh aspect of this disclosure, a computer program product is provided. The computer program product includes computer-executable instructions that, when executed by a processor, implement the method according to a first aspect of this disclosure or a second aspect of this disclosure.

[0012] It should be understood that the description in the Summary of the Invention section is not intended to limit the key or essential features of the embodiments of this disclosure, nor is it intended to restrict the scope of this disclosure. Other features of this disclosure will become readily apparent from the following description. Attached Figure Description

[0013] The above and other features, advantages, and aspects of various implementations of this disclosure will become more apparent in the following detailed description, taken in conjunction with the accompanying drawings. In the drawings, the same or similar reference numerals denote the same or similar elements, wherein:

[0014] Figure 1 A schematic diagram of an example architecture for data processing according to an embodiment of the present disclosure is shown;

[0015] Figure 2 A flowchart is shown illustrating a data processing procedure implemented at a delivery control system according to some embodiments of the present disclosure;

[0016] Figure 3A A schematic diagram illustrating the process of generating an inventory task according to some embodiments of the present disclosure is shown;

[0017] Figure 3B A schematic diagram illustrating the process of manually generating an inventory task according to some embodiments of the present disclosure is shown;

[0018] Figure 3C A schematic diagram of an interface for manually generating inventory tasks according to some embodiments of the present disclosure is shown;

[0019] Figure 3DA schematic diagram illustrating the process of automatically generating inventory tasks according to some embodiments of the present disclosure is shown;

[0020] Figure 3E A schematic diagram of an interface for automatically generating inventory tasks according to some embodiments of the present disclosure is shown;

[0021] Figure 3F A schematic diagram illustrating the process of determining an inventory strategy according to some embodiments of the present disclosure is shown;

[0022] Figure 3G A schematic diagram of a display interface for an inventory task according to some embodiments of the present disclosure is shown;

[0023] Figure 3H A schematic diagram of an interface for sending reminder messages according to some embodiments of the present disclosure is shown.

[0024] Figure 4 A schematic diagram of the interface of a delivery station according to some embodiments of the present disclosure is shown;

[0025] Figure 5 A flowchart illustrating the process of performing an inventory counting task at a delivery terminal device according to some embodiments of the present disclosure is shown.

[0026] Figure 6A A schematic diagram of the interface of a delivery terminal device according to some embodiments of the present disclosure is shown;

[0027] Figure 6B A schematic diagram of a task inventory interface according to some embodiments of the present disclosure is shown;

[0028] Figure 6C A schematic diagram of a task prompting interface according to some embodiments of the present disclosure is shown;

[0029] Figure 6D A schematic diagram illustrating a process for updating the task difference state according to some embodiments of the present disclosure is shown;

[0030] Figure 6E A schematic diagram of a task status interface according to some embodiments of the present disclosure is shown;

[0031] Figure 7 A block diagram of a data processing apparatus implemented in a delivery control system according to some embodiments of the present disclosure is shown;

[0032] Figure 8 A block diagram of a data processing apparatus implemented at a delivery terminal device according to some embodiments of the present disclosure is shown; and

[0033] Figure 9 A block diagram of an electronic device in which one or more embodiments of the present disclosure may be implemented is shown. Detailed Implementation

[0034] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0035] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may also be included below.

[0036] In this document, unless explicitly stated otherwise, performing a step in response to A does not mean that the step is performed immediately after A, but may include one or more intermediate steps.

[0037] It is understood that the data involved in this technical solution (including but not limited to the data itself, the acquisition, use, storage or deletion of the data) shall comply with the requirements of relevant laws, regulations and related provisions.

[0038] As mentioned earlier, in the field of logistics and warehousing management, it is often necessary to regularly inventory and process the relevant data of packages and other items in the inventory to ensure the accuracy of inventory information and support the efficient operation of the delivery system.

[0039] Inventory counting refers to the process of counting and verifying goods, packages, commodities, or assets, and processing the resulting data to ensure that the quantity, type, and condition of the inventoried items match the records or expectations.

[0040] In related technologies, the processes for inventorying objects and processing data all rely on manual operation by relevant personnel.

[0041] As an example, the current inventory process may include: Operations-submitted inventory process: Operations personnel retrieve relevant package data to be inventoried based on conditions (such as site, document status, network type, package origin, etc.). If packages to be inventoried exist in the system, operations personnel will export an inventory list and send the corresponding paper slips to the relevant sites; On-site inventory process: Delivery personnel scan and verify each package on the site according to the inventory list generated by operations personnel. Delivery personnel check whether the information on the list matches the actual package by scanning each package. If discrepancies are found (such as missing, incorrect, or extra packages), these discrepancies and their reasons need to be recorded; Inventory result entry process: Operations personnel review the inventory records submitted by delivery personnel, enter these results into the system, and update the package data at the site.

[0042] This approach has some problems, specifically including the following aspects:

[0043] The inefficiency of manual operations: This relies heavily on manual work by delivery operations staff. Staff need to export data on packages to be inventoried from the system, generate inventory lists, and then download them. These operations are not only tedious but also prone to human error, leading to low work efficiency.

[0044] Delayed and inaccurate data updates: After inventory checks, discrepancies and updates must be done manually. This method easily leads to delayed updates and potential inaccuracies, especially when processing large volumes of package data.

[0045] Lack of unified management and monitoring: Each site lacks a unified system tool for monitoring and managing the items to be inventoried. Headquarters operations cannot monitor the inventory task status of each site in real time, potentially leading to delayed processing of items or inaccurate data at some sites. This increases the risk of damage and impacts overall operational efficiency.

[0046] In view of this, the present disclosure provides a data processing scheme. In this scheme, a delivery control system receives first waybill information of an object to be inventoried, the first waybill information indicating the object's attribute and status information; based on an inventory strategy, an inventory task is generated for the object, the inventory strategy being determined at least based on the first waybill information, and the inventory task instructing the first waybill information to be inventoried within a first predetermined time; in response to determining that the first waybill information has not been inventoried, a first status flag is generated for the first waybill information, the first status flag indicating that the first waybill information needs to be inventoried; and the inventory task and the first status flag are sent to the delivery station to request the delivery station to execute the inventory task. Thus, an automated process can be used to generate inventory tasks based on an inventory strategy, and relevant data can be automatically updated after the inventory task is executed, thereby reducing manual operations, simplifying the inventory workflow, and improving data processing efficiency.

[0047] The following description will focus on exemplary embodiments of the present disclosure with reference to the accompanying drawings.

[0048] Figure 1 A schematic diagram of an example architecture 100 for data processing according to an embodiment of the present disclosure is shown. It is important to note that the present disclosure is not limited to the modules / systems involved in the example architecture 100. Any additions or replacements to the modules / systems shown in the diagram to achieve similar purposes should be considered as included within the scope of this disclosure.

[0049] In some embodiments, such as Figure 1 As shown, the example architecture 100 generally includes a delivery control system 110, a delivery station 120, and a delivery terminal device 130.

[0050] In some embodiments, the delivery control system 110 can receive waybill information for objects to be inventoried and generate an inventory task for those objects. The delivery control system 110 can send the inventory task to the delivery station 120, requesting the delivery station 120 to perform the inventory task. The delivery control system 110 can be any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, or any combination thereof, including accessories and peripherals of these devices or any combination thereof.

[0051] In some embodiments, the delivery station 120 may be communicatively connected to the delivery control system 110. The delivery station 120 may receive inventory tasks from the delivery control system 110 and assign the inventory tasks to the delivery terminal equipment 130 to instruct the delivery terminal equipment 130 to perform the inventory tasks, for example, through manual assignment by the staff of the delivery station 120 or through an assignment program that automatically assigns inventory tasks based on specific rules or algorithms.

[0052] In some embodiments, the delivery terminal device 130 can communicate with the delivery station 120. The delivery terminal device 130 can receive inventory tasks sent by the delivery station 120 and perform inventory and data processing operations on the objects to be inventoried according to the instructions of the inventory tasks.

[0053] exist Figure 1 In this system, the delivery control system 110, delivery station 120, and delivery terminal equipment 130 can include any computing system with computing capabilities, such as various computing devices / systems, terminal equipment, servers, etc. Terminal equipment can involve any type of mobile terminal, fixed terminal, or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, or any combination thereof, including accessories and peripherals of these devices or any combination thereof. Servers include, but are not limited to, mainframes, edge computing nodes, computing devices in cloud environments, etc.

[0054] It should be understood that Figure 1 The various systems, devices, and components shown are merely examples. In practical applications, various different arrangements, with more, fewer, or different systems, devices, and components, may exist. It should also be understood that... Figure 1 Separate systems, devices, and components are shown, but they can also be implemented in the same system, device, and component.

[0055] Figure 2 A flowchart of a data processing procedure 200 implemented at a delivery control system according to some embodiments of the present disclosure is shown. Procedure 200 may be implemented in environment 100, for example, procedure 200 may be implemented at delivery control system 110. It should be understood that data processing procedure 200 may also include additional boxes not shown and / or some (or more) of the boxes shown, and the scope of the present disclosure is not limited in this respect.

[0056] In frame 210, the delivery control system 110 receives the first waybill information for the objects to be inventoried.

[0057] In some embodiments, the first waybill information indicates the attribute information of the object. For example, the first waybill information may indicate the network type of the object to be inventoried, which refers to the category of the distribution network on which the transportation service relies. Different network types may correspond to different logistics operation modes. For example, network types may include self-operated networks (distribution networks operated by the company itself), third-party carrier networks, partner networks, home appliance networks: transportation networks specifically used for transporting and delivering home appliances (such as televisions, refrigerators, washing machines, etc.), heavy cargo networks: transportation networks specifically used for transporting and delivering heavy goods, etc. The network type determines the object's processing flow and responsible party, so when generating an inventory task, the objects to be inventoried can be filtered according to the network type to ensure that the task is adapted to the network's operating mode.

[0058] In some embodiments, the first waybill information may also indicate the status information of the object. For example, the first waybill information may indicate the order acceptance time and / or waybill status of the object. The order acceptance time refers to the specific time when the system receives the order corresponding to the object, and it can usually be used to determine the priority and urgency of object processing. In an inventory task, the delivery control system 110 can filter out the objects to be inventoried that need to be processed within a specific time range based on the order acceptance time. For example, the order acceptance time can be used to determine which objects to be inventoried have expired and which objects to be inventoried need to be prioritized for inventory.

[0059] Waybill status refers to the real-time status of an object to be inventoried in the logistics process. Common waybill statuses include: Station Receipt: The package has been received by the delivery station and is awaiting further processing; Redelivery: The package has been re-delivered due to failure to complete the initial delivery; Rejection Pending Review: The customer has rejected the package and is currently awaiting further processing or approval; Successful Delivery: The package has been successfully delivered to the customer.

[0060] In other embodiments, the first waybill information may also indicate more, less, or different other information.

[0061] In box 220, the delivery control system 110 generates object-specific inventory tasks based on the inventory strategy.

[0062] In some embodiments, after determining the first waybill information of the objects to be inventoried, the delivery control system 110 may next generate an inventory task for these objects in the system based on a predefined inventory strategy.

[0063] Inventory strategy refers to a set of rules and conditions that the delivery control system 110 can use when generating inventory tasks. These strategies determine which objects in the system need to be inventoried, how to conduct the inventory, and the specific time and frequency of the inventory. Different inventory strategies ensure that the generation process of inventory tasks is targeted and flexible, adapting to the needs and operational conditions of different sites. For example, based on the application of inventory strategies, inventory tasks can be customized based on first waybill information (such as network type, waybill status, order acceptance time, etc.), thereby improving inventory efficiency and accuracy.

[0064] In some embodiments, the delivery control system 110 can determine adaptive inventory tasks based on information from different dimensions, such as delivery station dimension, transportation dimension, and timeliness dimension, through inventory strategies.

[0065] For example, refer to Figure 3A , Figure 3A A schematic diagram of a process 300A for generating an inventory task according to some embodiments of the present disclosure is shown. Process 300A can be implemented at a delivery control system 110.

[0066] In frame 311, the delivery control system 110 determines the station information based on the first waybill information.

[0067] In some embodiments, the inventory task includes site information for delivery station 120. The site information indicates the site type and location information of the delivery station.

[0068] Site type refers to the classification or nature of a delivery site, which can be distinguished based on different operating models and business needs. For example, site types can include: self-operated delivery stations: delivery stations directly managed and operated by the company; third-party carriers: stations managed by third-party logistics companies that have a cooperative relationship with the company; and cooperative delivery stations: delivery stations that cooperate with multiple companies and are responsible for shared logistics tasks.

[0069] In some embodiments, the location information of a delivery station may include information indicating the center, warehouse, or region corresponding to the delivery station.

[0070] A center refers to a central organization that manages multiple sites, and is usually divided according to geographical area or function.

[0071] A warehouse is a specific location used to store goods, and it can be further subdivided into different types of warehouses at the site level. For example, an operations warehouse is used to store a company's own goods or long-term inventory; a sorting warehouse is used to temporarily store packages awaiting sorting, with a fast turnover rate; and a cloud warehouse is a virtual warehouse managed using cloud technology, which may not store actual items but is used to record and manage inventory data.

[0072] A region refers to the geographical location or service area of ​​a site, usually based on administrative divisions or internal company divisions. For example, the country may be divided into several major regions, each of which may contain multiple provinces and distribution centers.

[0073] Regional information can also specify a particular city or a specific area within a city, indicating the service area that a particular station is responsible for.

[0074] In some embodiments, the delivery station serves as the basic dimension for inventory tasks, which are then transmitted to specific delivery stations 120. The delivery control system 110 can be configured with multiple levels and stations based on different station types, warehouse types, and provinces and their subordinate distribution centers within major regions. By specifying station information, the delivery control system 110 can accurately match inventory tasks according to the actual conditions of different delivery stations.

[0075] In this embodiment of the disclosure, determining the information at the station level enables the inventory tasks generated by the delivery control system 110 to be more accurate, efficient, and adaptable to the operational needs of different stations, thereby improving the operational efficiency and accuracy of the entire logistics chain.

[0076] Continue to refer to Figure 3A In box 312, the delivery control system 110 generates transportation information based on the inventory strategy.

[0077] In some embodiments, the inventory task also includes transportation information for the objects, which indicates the transportation type and transportation status of the objects.

[0078] In some embodiments, the generated object-specific inventory task can also be configured based on the transportation information of the objects to be inventoried. The objects to be inventoried are transported based on corresponding waybills; for example, the transportation type can indicate the objects to be inventoried.

[0079] Waybill Source: This refers to the channel or platform from which the waybill was generated. For example: Self-operated: Waybills processed by the platform itself, usually executed by the platform's own logistics system; Open: Waybills opened to third parties through the platform, which may involve multiple different logistics providers; Specific types of supply chain waybills; Pure delivery: Waybills that are only responsible for delivery.

[0080] Network type: refers to the type of logistics network in which the waybill is located.

[0081] Multi-level: This refers to whether the waybill involves multiple logistics links or levels. For example, the waybill may flow between different logistics nodes, involving multiple transfers and processing procedures.

[0082] Document timeliness: refers to the time frame within which a waybill needs to be processed. For example: Express Delivery: orders requiring fast delivery; Standard Delivery: orders to be delivered within the standard time; Evening Delivery: orders specifically scheduled for delivery at night.

[0083] In some embodiments, the transport status can indicate the objects to be inventoried:

[0084] Waybill Status: The current status of a waybill is an important factor in determining the inventory task.

[0085] Waybill type: refers to the type of waybill, such as: forward delivery: normal delivery from the warehouse to the customer; reverse pickup: retrieving goods from the customer, such as returns; forward collection: retrieving goods from the supplier or merchant, ready to be delivered to the customer.

[0086] In some embodiments, transportation information can also indicate additional value-added services (referring to extra services attached to the waybill) for the objects to be inventoried, such as: integrated delivery and installation: not only delivery but also installation services; unpacking and inspection: services that allow customers to unpack and inspect goods in front of the customer; packaging: involving special packaging services; and delivery to the customer's floor, not just the door. This transportation-related information can help the delivery control system 110 to more precisely customize inventory tasks, ensuring that objects of different types of waybills are correctly inventoried under different conditions, thereby improving the accuracy and efficiency of logistics management.

[0087] In this embodiment of the disclosure, by generating transportation-dimensional information, such as waybill origin, network type, and timeliness requirements, the delivery control system 110 can generate more accurate inventory tasks. This customized task ensures that the objects to be inventoried for various waybill types can be processed appropriately, thereby improving the accuracy and efficiency of inventory counting.

[0088] Continue to refer to Figure 3A In box 313, the delivery control system 110 determines the timeliness information based on the inventory strategy.

[0089] In some embodiments, the inventory task further includes timeliness information for the object. The timeliness information indicates the order acceptance time of the waybill corresponding to the object and the deadline for inventorying the first waybill information.

[0090] Order acceptance time refers to the time when the order corresponding to the object is received by the system, or it can be the time when the order corresponding to the object is generated and enters the logistics system. Order acceptance time helps the system prioritize the processing of objects awaiting inventory that were accepted earlier but have not yet been completed, thus avoiding delays.

[0091] In some embodiments, the delivery control system 110 can also set the priority of inventory based on the order acceptance time to ensure the processing of time-sensitive orders.

[0092] In some embodiments, the deadline for inventorying the first waybill information affects which objects to be inventoried will be included in the inventory scope. For example, the inventory task determines the objects to be inventoried based on a set deadline. The delivery control system 110 can filter eligible objects to be inventoried based on the set deadline and generate corresponding inventory tasks.

[0093] In this embodiment of the disclosure, time-related information is crucial during the generation of inventory tasks. Timeliness information helps the delivery control system 110 configure and execute inventory tasks according to different time conditions. Generating inventory tasks based on timeliness information can improve the timeliness and accuracy of inventory checks, optimize resource allocation and workload, and simultaneously enhance customer satisfaction.

[0094] Continue to refer to Figure 3A In box 314, the delivery control system 110 generates a specific inventory task based on information from each dimension of the determined inventory task.

[0095] In some embodiments, the execution process of the delivery control system 110 generating inventory tasks may include two methods: manual inventory configuration and automatic inventory configuration.

[0096] In some embodiments, the manual inventory configuration method supports the delivery control system 110 in generating corresponding inventory tasks based on the interaction results with staff. For example, the delivery control system 110 receives the operators' selection of configuration information such as site information, waybill cut-off time range, inventory deadline, network type, and waybill status, and generates inventory tasks in batches at the site level.

[0097] In some embodiments, manual inventory configuration can be applied to scenarios requiring flexible handling and customization, allowing adaptation to non-standard situations. For example, if items awaiting delivery at a distribution station are delayed due to network issues, backlogs, or other reasons, the delivery control system 110 can generate accurate inventory tasks based on configuration information manually selected by staff, ensuring that these packages are processed in a timely manner.

[0098] In some embodiments, the automatic inventory configuration method instructs the delivery control system 110 to generate target inventory tasks at predetermined intervals based on an inventory strategy. For example, the delivery control system 110 determines information such as delivery stations, order start and end times, inventory deadlines, network types, and waybill status based on the inventory strategy, and automatically and periodically generates inventory tasks based on the task generation time (in weekly units).

[0099] In some embodiments, the automated inventory configuration method allows the delivery control system 110 to periodically generate inventory tasks for several delivery stations based on an inventory strategy. This method is suitable for scenarios requiring regular inventory checks, automates the task generation process, and reduces omissions or errors that may result from manual operation.

[0100] In this embodiment of the disclosure, the delivery control system 110 can generate inventory tasks based on the actual situation of specific stations through manual inventory configuration, thereby flexibly responding to special circumstances. By automatically generating inventory tasks, it ensures that all delivery stations are inventoried according to the prescribed cycle, avoiding data inaccuracies caused by human error in omitting certain stations.

[0101] In some embodiments, the delivery control system 110 may also perform verification based on the actual situation of each delivery station and object during the generation of inventory tasks.

[0102] For example, refer to Figure 3B , Figure 3B A schematic diagram of a process 300B for manually generating inventory tasks according to some embodiments of the present disclosure is shown. Process 300B can be implemented at the distribution control system 110.

[0103] As an example, such as Figure 2 The box 220 shown may include, for example, Figure 3B The execution steps shown in boxes 320A to 326 are as follows. In box 320A, the delivery control system 110 creates a manual inventory task for an object, and in box 320B, the delivery control system 110 determines that the inventory task type is a manual inventory task.

[0104] In box 321, the delivery control system 110 receives selections of information such as the site for the inventory task, the cut-off time range for the waybill, the inventory deadline, the network type, and the waybill status.

[0105] In box 322, the delivery control system 110 determines whether there are any items (waybill packages) to be inventoried at the delivery station. If there are no waybill packages to be inventoried, then box 323 is executed. If there are waybill packages to be inventoried, then box 324 is executed.

[0106] In box 323, the delivery control system 110 displays a prompt on the front-end page, indicating that there are no packages to be inventoried at this site under the current conditions, and records that there are no objects to be inventoried at this delivery site.

[0107] In some embodiments, each object in the delivery station determined by the delivery control system 110 may have already completed the corresponding inventory operation. By checking whether there are any objects to be inventoried, it can be ensured that the newly generated inventory tasks are based on the current actual needs, and unnecessary inventory tasks can be avoided.

[0108] In box 324, the delivery control system 110 generates an inventory task for the packages to be inventoried. In box 325, the delivery control system 110 marks these packages as "pending inventory". In box 326, the delivery control system 110 transmits the inventory task to the corresponding delivery station.

[0109] Figure 3C A schematic diagram of an interface 320 for manually generating inventory tasks according to some embodiments of the present disclosure is shown.

[0110] like Figure 3C As shown, the delivery control system 110 generates corresponding inventory tasks based on information received from the operators, such as the region, distribution center, station, waybill acceptance time, inventory deadline, network type, and waybill status of the inventory task manually selected by the operators.

[0111] For example, refer to Figure 3D , Figure 3D A schematic diagram of a process 300C for automatically generating inventory tasks according to some embodiments of the present disclosure is shown. Process 300C can be implemented at a distribution control system 110.

[0112] As an example, such as Figure 2 The box 220 shown may include, for example, Figure 3D The execution steps shown in boxes 330A to 339 are as follows. In box 330A, the delivery control system 110 creates an inventory task, and in box 330B, the delivery control system 110 determines the type of inventory task for the target object as an automatic inventory task based on the inventory strategy.

[0113] In box 331, the delivery control system 110 determines the station corresponding to the object to be inventoried, the order start and end time, the inventory end time, the network type, the waybill status, and the task generation time.

[0114] In box 332, the delivery control system 110 determines whether the current system time is the task generation time. If the current system time is determined to be the task generation time, then box 333 is executed.

[0115] In box 333, the delivery control system 110 determines whether there are any unfinished inventory tasks at the delivery station. If there are unfinished tasks, box 334 is executed. If there are no unfinished tasks, box 335 is executed.

[0116] In box 334, the delivery control system 110 records unfinished tasks.

[0117] In some embodiments, after determining the configuration information for various dimensions of the inventory task, the delivery control system 110 can also determine whether there are any inventory tasks that have been generated but not yet completed at the corresponding delivery station. If there are incomplete inventory tasks at a station, the delivery control system 110 can record this in the log and not generate new tasks for that station, thereby preventing duplicate or conflicting inventory tasks.

[0118] In box 335, the delivery control system 110 determines whether there are any items (waybill packages) to be inventoried at the delivery station. If there are no waybill packages to be inventoried, then box 336 is executed. If there are waybill packages to be inventoried, then box 337 is executed.

[0119] In box 336, the delivery control system 110 records packages awaiting inventory via logs.

[0120] In box 337, the delivery control system 110 generates an inventory task for the packages to be inventoried. In box 338, the delivery control system 110 marks these packages as "pending inventory". In box 339, the delivery control system 110 transmits the inventory task to the corresponding delivery station.

[0121] As an example, Figure 3E A schematic diagram of an interface 330 for automatically generating inventory tasks according to some embodiments of the present disclosure is shown.

[0122] like Figure 3E As shown, the delivery control system 110 automatically generates corresponding inventory tasks at a predetermined cycle based on information such as the set task generation time, inventory task area, distribution center, station, order start time, inventory end time, network type, and waybill status.

[0123] In this embodiment of the disclosure, periodic checks and verifications can avoid generating repetitive judgment tasks, update data in real time, optimize resource allocation, and improve overall management efficiency. Furthermore, by verifying the objects to be inventoried at the site in real time, it ensures that tasks are generated only when actually needed, improving the accuracy and efficiency of task generation.

[0124] In some embodiments, the delivery control system 110 may, before generating an inventory task, use an inventory strategy corresponding to the strategy template pool to execute the process of generating an inventory task based on the inventory strategy.

[0125] Figure 3F A schematic diagram of a process 300D for determining an inventory strategy according to some embodiments of the present disclosure is shown. Process 300D can be implemented at a distribution control system 110.

[0126] In box 341, the delivery control system 110 determines from the strategy template pool whether a first inventory strategy matching the first waybill information exists. If a first inventory strategy matching the first waybill information exists, box 342 is executed. If no first inventory strategy matching the first waybill information exists, box 343 is executed.

[0127] In box 342, the delivery control system 110 responds to the existence of a first inventory strategy and generates an inventory task based on the first inventory strategy.

[0128] The strategy template pool can be a database or collection containing predefined inventory strategy templates. These inventory strategies can be pre-defined based on historical experience and standard requirements, and are used to guide the generation and management of inventory tasks.

[0129] In some embodiments, the delivery control system 110 generates inventory tasks based on the execution flow of the inventory strategy. First, the delivery control system 110 checks in the strategy template pool whether there are existing inventory strategy templates that meet the current requirements. If there are applicable strategy templates in the template pool, the system will directly use these templates to generate the corresponding inventory tasks.

[0130] In box 343, in response to the absence of a first inventory strategy, the delivery control system 110 creates a second inventory strategy based on the first waybill information.

[0131] In some embodiments, if the delivery control system 110 determines that there is no judgment strategy template applicable to the target object in the strategy template pool, it can create an inventory strategy based on the first waybill information corresponding to the object.

[0132] In box 344, the delivery control system 110 generates an inventory task based on the created second inventory strategy.

[0133] In some embodiments, the delivery control system 110 generates corresponding inventory tasks based on a newly created inventory strategy.

[0134] In some embodiments, when creating a second inventory strategy, the delivery control system 110 may determine the task configuration type indicated by the inventory strategy, such as manual inventory configuration and automatic inventory configuration.

[0135] In box 345, the delivery control system 110 determines whether to save the second inventory strategy. If it determines to save the second inventory strategy, then proceed to box 347. If it determines not to save the second inventory strategy, then proceed to box 346. In box 346, the delivery control system 110 ends the inventory strategy creation process without saving the newly created inventory strategy as a template in the strategy template.

[0136] In box 347, in response to determining that a second inventory strategy needs to be saved, the delivery control system 110 saves the second inventory strategy to the strategy template pool.

[0137] In some embodiments, the delivery control system 110 can save the created decision-making strategies as templates. These templates include pre-defined strategy parameters, such as site type, inventory scope, document attributes, and timeframe. When similar inventory tasks need to be created in the future, the delivery control system 110 can directly and quickly apply the preset strategies to generate the corresponding inventory task based on the saved templates.

[0138] In this embodiment of the disclosure, the time and manual operation for creating inventory tasks are reduced by using existing inventory strategy templates, thereby improving the overall efficiency of task generation. Furthermore, by saving the newly created inventory strategy as a new template after generating the task, a ready-made reference can be provided for future similar tasks, reducing the workload of repeatedly creating strategies and improving management efficiency and consistency.

[0139] Return to reference Figure 2 In box 230, in response to determining that the first waybill information has not been inventoried, the delivery control system 110 generates a first status flag for the first waybill information. The first status flag indicates that the first waybill information needs to be inventoried.

[0140] In some embodiments, after an inventory task is generated, the delivery control system 110 typically needs to generate a status flag to mark the object corresponding to the inventory task as "pending inventory".

[0141] As an example, after generating an inventory task, the delivery control system 110 can create a task record, including the specific requirements and related settings for the inventory. Based on the task configuration and conditions, the system will determine the objects that need to be inventoried corresponding to the first waybill information and mark these objects as "pending inventory" in the task record.

[0142] In box 240, the delivery control system 110 sends an inventory task and a first status flag to the delivery station to request the delivery station 120 to perform the inventory task.

[0143] In some embodiments, the delivery control system 110 may download the generated inventory task and its related status flags to the corresponding delivery station 120 (e.g., station workbench and mobile application) to request the delivery station 120 to execute the corresponding inventory task based on the inventory task and the first status flag.

[0144] Figure 3G A schematic diagram of a display interface 340 for an inventory task according to some embodiments of the present disclosure is shown.

[0145] like Figure 3G As shown, the delivery control system 110 allows users with relevant permissions (such as the person who created the inventory task or relevant operations personnel) to view detailed information about the generated inventory tasks. This detailed information may include basic parameters of the task (such as site, package attributes, inventory deadline, etc.), task status (such as pending inventory, inventory completed, whether there are discrepancies, etc.), and related historical records or remarks.

[0146] In some embodiments, for inventory tasks that have been generated but not yet started, users with relevant permissions in the delivery control system 110 (such as the task creator or relevant operations personnel) can cancel them. Reasons for cancellation may include, for example, the task being no longer applicable, changes in site conditions, or incorrect task settings.

[0147] In this embodiment of the disclosure, by supporting the viewing of the task status of inventory tasks, the current status and progress of each inventory task can be clearly understood, which helps to identify problems in a timely manner and make adjustments or interventions. Moreover, by invalidating invalid tasks, the waste of resources (such as manpower, time and equipment) can be avoided, and work efficiency can be improved.

[0148] Figure 3H A schematic diagram of an interface 350 for sending reminder messages according to some embodiments of the present disclosure is shown.

[0149] like Figure 3H As shown, the delivery control system 110 can send the generated inventory tasks and corresponding status flags to the corresponding delivery station 120 (e.g., the delivery station workbench or the mobile device of other station managers (such as the station manager)). The delivery control system 110 can also send a mandatory reminder message to the delivery station 120, notifying the station that a new inventory task is pending. The reminder message can include basic task information, such as task content, requirements, and deadline. A mandatory reminder is a notification sent by the system that cannot be ignored, ensuring that station staff see and process the inventory task in a timely manner.

[0150] Figure 4 A schematic diagram of an interface 400 of a delivery station 120 according to some embodiments of the present disclosure is shown.

[0151] like Figure 4 As shown, delivery station 120 can view detailed information about generated inventory tasks. This detailed information can include basic task parameters (such as station, package attributes, inventory deadline, etc.), task status (such as pending inventory, inventory completed, whether there are discrepancies, etc.), and related historical records or remarks.

[0152] In some embodiments, after receiving these mandatory reminder messages, the delivery station 120 can select appropriate personnel to perform the inventory task according to the task requirements and resource availability, and assign the inventory task to the delivery terminal device 130.

[0153] Figure 5 A flowchart is shown of a process 500 for performing an inventory task at a delivery terminal device according to some embodiments of the present disclosure. Process 500 can be implemented in environment 100, for example, process 500 can be implemented at a configuration terminal device 130.

[0154] In box 510, configure terminal device 130 to receive inventory tasks.

[0155] In some embodiments, the delivery terminal device 130 receives an inventory task for objects to be inventoried and a first status flag. The inventory task indicates that the first waybill information of the objects needs to be inventoried within a first predetermined time. The first waybill information indicates the attribute information and status information of the objects. The first status flag indicates that the first waybill information requires inventory.

[0156] In some embodiments, the delivery terminal device 130 performs an inventory count task.

[0157] In some embodiments, the staff performing the inventory task view detailed task information, such as task requirements and status markers (e.g., "pending inventory"), through their delivery terminal device 130, and then perform the inventory task. For example, the staff performs the inventory task in a designated area or location according to the task requirements. The delivery terminal device 130 receives the task execution results from the staff and performs corresponding data processing.

[0158] Figure 6A A schematic diagram of the interface 610 of a delivery terminal device 130 according to some embodiments of the present disclosure is shown.

[0159] like Figure 6A As shown, in response to receiving the inventory task and the first status flag, the delivery terminal device 130 displays a task prompt identifier 611. The task prompt identifier 611 indicates that an inventory task to be executed has been received.

[0160] In some embodiments, in response to the triggering of task prompt identifier 611, task inventory interface 620 is displayed.

[0161] Continue to refer to Figure 5 In frame 520, the delivery terminal device 130 receives the scanning results obtained by the staff from scanning the information tags of the packages to be inventoried according to the inventory task.

[0162] In some embodiments, performing an inventory task first includes the delivery terminal device 130 performing the following: obtaining the second waybill information of the object through the object's information identifier and determining whether the first waybill information and the second waybill information match.

[0163] As an example, staff use mobile devices (such as mobile phones or barcode scanners) to scan information tags on packages. These tags are typically in the form of QR codes, barcodes, etc., and contain detailed information about the waybill. The delivery terminal device 130 reads the second waybill information based on the information tags, compares it with the information, and verifies the package's status, quantity, waybill type, and other information.

[0164] In some embodiments, in response to a match between the first waybill information and the second waybill information, the delivery terminal device 130 generates a second status flag for the first waybill information and the second waybill information. The second status flag indicates that the first waybill information and the second waybill information match.

[0165] In some embodiments, in response to a mismatch between the first waybill information and the second waybill information, the delivery terminal device 130 generates a third status flag for the first waybill information and the second waybill information, the third status flag indicating that the first waybill information and the second waybill information do not match.

[0166] In some embodiments, the delivery terminal device 130 compares the scanned second waybill information with the first waybill information of the object to check whether the actual situation of the package matches the system record. If the information matches, the delivery terminal device 130 generates a second status mark, and the package is marked as "no difference". If there is a difference (such as the corresponding package not being scanned, information inconsistency, etc.), the delivery terminal device 130 generates a third status mark, and the package is marked as "there is a difference", which needs to be recorded and further processed.

[0167] In this embodiment of the disclosure, waybill information can be quickly obtained through information identification, and the obtained waybill information can be compared with the expected waybill information in the database to verify the status, quantity, waybill type, and other information of the objects in real time. This real-time comparison method can immediately identify and mark objects with mismatched information, ensuring that problems can be handled in a timely manner.

[0168] Return to reference Figure 5 In box 530, in response to the completion of the inventory operation on a package to be inventoried, the delivery terminal device 130 determines that the inventory operation on the package is complete.

[0169] In box 540, the delivery terminal device 130 determines whether the scanning progress has exceeded a predetermined percentage. If it is determined that the scanning progress has not exceeded the predetermined percentage, then proceed to box 520. If it is determined that the scanning progress has exceeded the predetermined percentage, then proceed to box 550.

[0170] In some embodiments, by setting a scan progress threshold (e.g., 20%), operators are required to scan at least a certain percentage of packages before marking the task as "complete". This mandatory requirement ensures that inventory tasks are performed effectively, avoids incomplete inventory data due to insufficient package scanning, and thus improves overall inventory quality.

[0171] Figure 6B A schematic diagram of a task inventory interface 620 according to some embodiments of the present disclosure is shown. The task inventory interface 620 is used to perform inventory tasks.

[0172] In some embodiments, the task inventory interface includes an inventory confirmation control 622. The inventory confirmation control 622 is used to determine whether the inventory task has been completed.

[0173] In some embodiments, in response to the progress of the inventory task reaching a predetermined threshold, the inventory determination control 622 is enabled.

[0174] In this embodiment, the threshold setting effectively prevents operators from directly triggering the inventory confirmation control before completing sufficient scanning tasks. By restricting operational permissions, staff are encouraged to complete the inventory according to the prescribed procedures, ensuring the standardization of the inventory operation.

[0175] Continue to refer to Figure 5 In box 550, delivery terminal equipment 130 can update the status of inventory packages based on the scan results.

[0176] As an example, the delivery terminal device 130 can update the status of the packages corresponding to the inventory task instruction based on the scanning results of each package. Packages that have been scanned and have no issues will be marked as "no discrepancies," while unscanned or discrepancies will be marked as "discrepancies not processed."

[0177] In box 560, delivery terminal device 130 can update task difference status based on the inventory package status.

[0178] In some embodiments, in response to the triggering of the inventory confirmation control 622, the delivery terminal device 130 displays a task prompt interface 630.

[0179] Figure 6C A schematic diagram of a task prompting interface 630 according to some embodiments of the present disclosure is shown.

[0180] In some embodiments, the task prompt interface 630 indicates the number of objects for which the inventory task has not been completed and provides processing prompts. The processing prompts instruct that objects whose first waybill information and second waybill information do not match be processed within a second predetermined time.

[0181] As an example, if the delivery terminal device 130 determines, based on the package status, that all packages in the inventory task have been successfully scanned, it can update the task's discrepancy status to "No discrepancies," indicating that no missing or abnormal packages were found. If any packages were not scanned, the delivery terminal device 130 can update the task's discrepancy status to "Differences Unprocessed." Simultaneously, the delivery terminal device 130 can display a prompt on the screen to alert the operator to process these discrepancies within a second, predetermined timeframe.

[0182] In this embodiment, the delivery terminal device can automatically update the task discrepancy status based on the scanning results, eliminating the need for manual judgment. This reduces human error and improves the accuracy of inventory tasks. When an object is not scanned, the system promptly updates the task discrepancy status to "Difference Unprocessed" and displays a notification to the operator. This immediate notification ensures that operators pay attention to and address discrepancy issues as early as possible, avoiding delays that could affect subsequent work.

[0183] Figure 6D A schematic diagram of a process 600A for updating the task difference state according to some embodiments of the present disclosure is shown. Process 600A can be implemented at the configuration terminal device 130.

[0184] In box 611, the configuration terminal device 130 determines whether all packages in the inventory task have been inventoried. If it is determined that the inventory is complete, that is, all packages have been successfully scanned, the configuration terminal device 130 can execute box 612 to update the difference status of the inventory task to "no difference".

[0185] If it is determined that the inventory is not completed, that is, the package has not been scanned or the scan result information differs from the expected result, the configuration terminal device 130 can execute box 613, in which the configuration terminal device 130 prompts to complete the processing of the package with discrepancies within a predetermined time.

[0186] In box 614, the terminal device 130 is configured to receive the processing results for the tagged difference package.

[0187] In box 615, the configuration terminal device 130 determines whether the difference package has been processed. If it is determined that the difference package has been processed, box 612 is executed. In box 612, the configuration terminal device 130 updates the difference status of the corresponding inventory task based on the processing result of the marked difference package.

[0188] As an example, the processing of discrepancies in packages may include selecting the reason for the discrepancy and uploading relevant images. For instance, if the configuration terminal device 130 receives the processing result within a specified time (e.g., three hours) and determines that the delivery personnel have processed all discrepancies in packages and uploaded relevant photos, the configuration terminal device 130 can update the discrepancy status of the task to "Difference Processed".

[0189] If no message or indication indicating that the difference package processing is complete is received, the configuration terminal device 130 executes box 616. In box 616, the configuration terminal device 130 determines whether the current system time has reached the deadline for processing. If the deadline for processing has not been reached, the configuration terminal device 130 continues to execute box 614.

[0190] If the deadline for processing has been reached, configure terminal device 130 to execute box 612. In box 612, configure terminal device 130 to update the difference status of the corresponding inventory task based on the processing result indicating that the difference processing has not been completed even though the deadline for processing has been reached.

[0191] As an example, if the configuration terminal device 130 determines that the delivery personnel failed to complete the discrepancy processing operation within a specified time (e.g., three hours), the configuration terminal device 130 can update the status of the inventory task to "overdue and unprocessed".

[0192] In some embodiments, the configuration terminal device 130 can display a task prompt interface 630 to prompt the operator to complete the processing within a predetermined time.

[0193] like Figure 6C As shown, the task prompt interface 630 includes an inventory upload control 631. The inventory upload control 631 is used to control the termination of the inventory task and upload images of objects whose information does not match the first waybill information and the second waybill information.

[0194] In some embodiments, in response to triggering the inventory upload control 631, the configuration terminal device 130 terminates the inventory task. In response to the termination of the inventory task, the configuration terminal device 130 generates a fourth status identifier for objects that have not completed the inventory task, the fourth status identifier indicating that the corresponding inventory task for the object has not been completed.

[0195] In some embodiments, when the inventory upload control 631 is triggered, the configuration terminal device 130 terminates the execution of the current inventory task and ends the inventory process of the task. Based on the completion status of the current inventory task, the configuration terminal device 130 can generate a status flag indicating that the inventory task for these packages has not yet been completed, that is, it is in a state where there are discrepancies but they have not yet been processed.

[0196] In some embodiments, when the inventory upload control 631 is triggered, the configuration terminal device 130 can display an image upload page after terminating the execution of the current inventory task. On the image upload page, the configuration terminal device 130 receives images of objects whose first waybill information and second waybill information do not match.

[0197] In some embodiments, in response to the completion of image uploading for objects whose first and second waybill information do not match, the configuration terminal device 130 generates a fifth status identifier for the inventory task. The fifth status identifier indicates that the inventory task for objects whose first and second waybill information do not match has been completed.

[0198] In some embodiments, staff can handle discrepancies found during the inventory process (e.g., damaged or missing packages) after the inventory operation is terminated, for example, by taking photos via the inventory upload control 631 and uploading them to the configuration terminal device 130. The configuration terminal device 130 receives these images and updates the status of the inventory task to "discrepancies handled".

[0199] In some embodiments, the configuration terminal device 130 can associate uploaded images with inventory records for subsequent inspection and processing.

[0200] In some embodiments, in response to the completion of image uploading for objects where the first waybill information and the second waybill information do not match, the configuration terminal device 130 determines the time taken for image uploading. In response to the time taken exceeding a second predetermined time, the configuration terminal device 130 generates a sixth status flag for the inventory task. The sixth status flag indicates that the inventory task is not completed.

[0201] As an example, in response to the completion of image uploads for mismatched objects, the configuration terminal device 130 determines the time taken for the difference processing. If the time taken is determined to be greater than a second predetermined time (e.g., 3 hours), the configuration terminal device 130 can generate a sixth status flag, thereby updating the status of the inventory task to "overdue and unprocessed" and recording it in the relevant operation log.

[0202] As another example, if the configuration terminal device 130 determines that the current system time triggers the inventory upload control 631 to exceed the second predetermined time, the configuration terminal device 130 can also generate a sixth status flag, thereby updating the status of the inventory task to "overdue and unprocessed" and recording it in the relevant operation log.

[0203] In this embodiment of the disclosure, by updating the status of inventory tasks for which difference processing has not been completed or for which difference images have been uploaded late to "overdue and unprocessed", timely overdue alerts can be provided, resource allocation can be optimized, task processing efficiency can be improved, and important data can be provided for performance evaluation and task supervision.

[0204] In some embodiments, the task prompt interface 630 further includes an inventory completion control 632. The inventory completion control 632 is used to control the termination of the inventory task.

[0205] In some embodiments, in response to the triggering of the inventory completion control 632, the configuration terminal device 130 terminates the inventory task. In response to the termination of the inventory task, a fourth status flag is generated for objects that have not completed the inventory task, indicating that the corresponding inventory task for the object has not been completed.

[0206] In some embodiments, when the inventory upload control 632 is triggered, the configuration terminal device 130 terminates the execution of the current inventory task and ends the inventory process of the task. Based on the completion status of the current inventory task, the configuration terminal device 130 can generate a status flag indicating that the inventory task of these packages has not yet been completed, that is, it is in a state where there are discrepancies but they have not yet been processed.

[0207] In some embodiments, in response to the failure to complete the inventory task within a first predetermined time after receiving the inventory task, the configuration terminal device 130 generates a seventh status identifier for the inventory task, the seventh status identifier indicating that the inventory task has not been completed.

[0208] In some embodiments, the first predetermined time may refer to a threshold time during which the inventory task needs to be completed. If the configuration terminal device 130 determines that the inventory task has not started or has not been completed before this threshold time, a status flag can be generated to mark the inventory task as "overdue and incomplete," which means that the task has not started or completed within the predetermined time range.

[0209] In this embodiment of the disclosure, by generating status identifiers, the configuration terminal device 130 can accurately record which inventory tasks have been completed, which are in a discrepancy state but still being processed, and which are overdue and incomplete. Through the generation and updating of status identifiers, the completion status and position of inventory tasks can be accurately recorded. This not only improves the accuracy and efficiency of inventory, but also optimizes resource allocation, enhances the transparency of task management, and provides real-time data support.

[0210] Figure 6E A schematic diagram of a task status interface 640 according to some embodiments of the present disclosure is shown. For example... Figure 6E As shown, the delivery control system 110 and / or delivery station 120 can control and present a display interface to show the current status of each package in each inventory task (such as "pending processing", "inventory completed", "difference processing", "overdue and unprocessed", etc.), the reasons for the discrepancies, and other information. Through the task status interface, operators can track the detailed status of each inventory task, such as whether the task was completed within the specified time and whether there are any overdue situations.

[0211] Figure 7A block diagram of a data processing apparatus 700 implemented at a delivery control system according to some embodiments of the present disclosure is shown. The apparatus 700 may be implemented as or include the delivery control system 110.

[0212] The apparatus 700 includes a receiving module 710 configured to receive first waybill information of an object to be inventoried, the first waybill information indicating the object's attribute information and status information; a task generation module 720 configured to generate an inventory task for the object based on an inventory strategy, the inventory strategy being determined at least based on the first waybill information, the inventory task indicating that the first waybill information should be inventoried within a first predetermined time; a status flag generation module 730 configured to generate a first status flag for the first waybill information in response to determining that the first waybill information has not been inventoried, the first status flag indicating that the first waybill information needs to be inventoried; and a sending module 740 configured to send the inventory task and the first status flag to a delivery station to request the delivery station to perform the inventory task.

[0213] In some embodiments, the inventory task includes site information for the delivery station, indicating the site type and location information of the delivery station. The task generation module 720 is further configured to determine the site information based on the first waybill information.

[0214] In some embodiments, the inventory task further includes transportation information for the objects, indicating the transportation type and status of the objects. The task generation module 720 is further configured to generate transportation information based on the inventory strategy.

[0215] In some embodiments, the inventory task further includes timeliness information for the object, indicating the order acceptance time of the waybill corresponding to the object and the deadline for inventorying the first waybill information. The task generation module 720 is further configured to determine the timeliness information based on the inventory strategy.

[0216] In some embodiments, the task generation module 720 is further configured to generate object-specific inventory tasks at predetermined intervals based on an inventory strategy.

[0217] In some embodiments, the apparatus 700 further includes a strategy determination module 750, configured to determine from a strategy template pool whether there exists a first inventory strategy that matches the first waybill information; and in response to the existence of the first inventory strategy, to generate an inventory task based on the first inventory strategy.

[0218] In some embodiments, the strategy determination module 750 is further configured to, in response to the absence of a first inventory strategy, create a second inventory strategy based on the first waybill information; generate an inventory task based on the created second inventory strategy; determine whether to save the second inventory strategy based on the inventory task; and, in response to determining that the second inventory strategy should be saved, save the second inventory strategy to the strategy template pool.

[0219] The modules included in device 700 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units can be implemented using software and / or firmware, such as machine-executable instructions stored on a storage medium. In addition to or as an alternative to machine-executable instructions, some or all of the units in device 700 can be implemented at least partially by one or more hardware logic components. By way of example and not limitation, exemplary types of hardware logic components that can be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-chips (SoCs), complex programmable logic devices (CPLDs), and so on.

[0220] Figure 8 A block diagram of a data processing apparatus 800 implemented at a delivery terminal device according to some embodiments of the present disclosure is shown. The apparatus 800 may be implemented as or include the delivery terminal device 130.

[0221] The apparatus 800 includes a receiving module 810 configured to receive an inventory task for an object to be inventoried and a first status flag. The inventory task indicates that first waybill information of the object needs to be inventoried within a first predetermined time. The first waybill information indicates the object's attribute information and status information. The first status flag indicates that the first waybill information needs to be inventoried. The apparatus also includes an execution module 820 configured to execute the inventory task, wherein the inventory task includes: obtaining second waybill information of the object through the object's information identifier; determining whether the first waybill information and the second waybill information match; generating a second status flag for the first waybill information and the second waybill information in response to a match, the second status flag indicating that the first waybill information and the second waybill information match; and generating a third status flag for the first waybill information and the second waybill information in response to a mismatch, the third status flag indicating that the first waybill information and the second waybill information do not match.

[0222] In some embodiments, the execution module 820 is further configured to display a task prompt identifier in response to receiving an inventory task and a first status flag, the task prompt identifier indicating that an inventory task to be executed has been received; and to display a task inventory interface in response to triggering the task prompt identifier, the task inventory interface being used to execute the inventory task.

[0223] In some embodiments, the task inventory interface includes an inventory confirmation control, which is used to determine whether the inventory task is completed. The execution module 820 is further configured to enable the inventory confirmation control in response to the execution progress of the inventory task reaching a predetermined threshold; and to display a task prompt interface in response to the triggering of the inventory confirmation control. The task prompt interface indicates the number of objects for which the inventory task has not been completed and processing prompt information. The processing prompt information indicates that objects whose first waybill information and second waybill information do not match will be processed within a second predetermined time.

[0224] In some embodiments, the task prompt interface includes an inventory upload control, which is used to control the termination of the inventory task and upload images of objects whose first waybill information and second waybill information do not match. The execution module 820 is further configured to terminate the inventory task in response to triggering the inventory upload control; generate a fourth status identifier for objects whose inventory tasks have not been completed in response to the termination of the inventory task, the fourth status identifier indicating that the corresponding inventory task of the object has not been completed; and upload images of objects whose first waybill information and second waybill information do not match.

[0225] In some embodiments, the task prompt interface includes an inventory completion control, which controls the termination of the inventory task, and the execution module 820 is further configured to terminate the inventory task in response to the triggering of the inventory upload control; in response to the termination of the inventory task, a fourth status identifier is generated for objects that have not completed the inventory task, the fourth status identifier indicating that the corresponding inventory task of the object has not been completed.

[0226] In some embodiments, the execution module 820 is further configured to generate a fifth status flag for the inventory task in response to the completion of image upload for objects whose first waybill information and second waybill information do not match. The fifth status flag indicates that the inventory task for objects whose first waybill information and second waybill information do not match has been completed.

[0227] In some embodiments, the execution module 820 is further configured to determine the time taken for image uploading in response to the completion of image uploading of an object for which the first waybill information and the second waybill information do not match; and to generate a sixth status flag for the inventory task in response to the time taken being greater than a second predetermined time, the sixth status flag indicating that the inventory task has not been completed.

[0228] In some embodiments, the execution module 820 is further configured to generate a seventh status identifier for the inventory task in response to the inventory task not being completed within a first predetermined time after receiving the inventory task, the seventh status identifier indicating that the inventory task has not been completed.

[0229] The modules included in device 800 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units can be implemented using software and / or firmware, such as machine-executable instructions stored on a storage medium. In addition to or as an alternative to machine-executable instructions, some or all of the units in device 800 can be implemented at least partially by one or more hardware logic components. By way of example, and not limitation, exemplary types of hardware logic components that can be used include field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-chips (SoCs), complex programmable logic devices (CPLDs), and so on.

[0230] Figure 9 A block diagram of an electronic device 900 in which one or more embodiments of the present disclosure may be implemented is shown. It should be understood that... Figure 9 The electronic device 900 shown is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein.

[0231] like Figure 9 As shown, electronic device 900 is in the form of a general-purpose electronic device. Components of electronic device 900 may include, but are not limited to, one or more processors or processing units 910, memory 920, storage device 930, one or more communication units 940, one or more input devices 950, and one or more output devices 960. Processing unit 910 may be a physical or virtual processor and is capable of performing various processes according to programs stored in memory 920. In a multiprocessor system, multiple processing units execute computer-executable instructions in parallel to improve the parallel processing capability of electronic device 900.

[0232] Electronic device 900 typically includes multiple computer storage media. Such media can be any available media accessible to electronic device 900, including but not limited to volatile and non-volatile media, removable and non-removable media. Memory 920 can be volatile memory (e.g., registers, cache, random access memory (RAM)), non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. Storage device 930 can be removable or non-removable media and can include machine-readable media, such as flash drives, disks, or any other media capable of storing information and / or data and accessible within electronic device 900.

[0233] Electronic device 900 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not explicitly stated... Figure 9As shown, disk drives for reading from or writing to removable, non-volatile disks (e.g., "floppy disks") and optical disk drives for reading from or writing to removable, non-volatile optical disks can be provided. In these cases, each drive can be connected to a bus (not shown) via one or more data media interfaces. Memory 920 may include computer program product 925 having one or more program modules configured to perform various methods or actions of various embodiments of this disclosure.

[0234] The communication unit 940 enables communication with other electronic devices via a communication medium. Additionally, the functionality of the components of the electronic device 900 can be implemented using a single computing cluster or multiple computing machines capable of communicating via communication connections. Therefore, the electronic device 900 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or another network node.

[0235] Input device 950 can be one or more input devices, such as a mouse, keyboard, trackball, etc. Output device 960 can be one or more output devices, such as a monitor, speaker, printer, etc. Electronic device 900 can also communicate with one or more external devices (not shown) via communication unit 940 as needed. These external devices include storage devices, display devices, etc., and can communicate with one or more devices that enable user interaction with electronic device 900, or with any device that enables electronic device 900 to communicate with one or more other electronic devices (e.g., network card, modem, etc.). Such communication can be performed via input / output (I / O) interface (not shown).

[0236] According to an exemplary implementation of this disclosure, a computer-readable storage medium is provided that stores one or more computer instructions, wherein the one or more computer instructions are executed by a processor to implement the methods described above. According to an exemplary implementation of this disclosure, a computer program product is also provided, which is tangibly stored on a non-transient computer-readable medium and includes computer-executable instructions that are executed by a processor to implement the methods described above.

[0237] Various aspects of this disclosure are described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products implemented according to this disclosure. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-readable program instructions.

[0238] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that, when executed by the processing unit of the computer or other programmable data processing apparatus, they create means for implementing the functions / actions specified in one or more blocks of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium that causes a computer, programmable data processing apparatus, and / or other device to operate in a particular manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing aspects of the functions / actions specified in one or more blocks of the flowchart and / or block diagram.

[0239] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions that execute on the computer, other programmable data processing apparatus, or other device to perform the functions / actions specified in one or more boxes of a flowchart and / or block diagram.

[0240] 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 this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of an instruction, which contains one or more executable instructions for implementing the specified logical function. 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 consecutive 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 the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, may be implemented using a dedicated hardware-based system that performs the specified function or action, or using a combination of dedicated hardware and computer instructions.

[0241] Various implementations of this disclosure have been described above. The foregoing description is exemplary and not exhaustive, nor is it limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is chosen to best explain the principles, practical applications, or improvements to technology in the market, or to enable others skilled in the art to understand the implementations disclosed herein.

Claims

1. A data processing method implemented at a distribution control system, comprising: receiving first shipping information of an object to be inventoried, the first shipping information indicating attribute information and status information of the object; generating an inventory task for the object based on an inventory policy, the inventory policy determined based on at least the first shipping information, the inventory task indicating to inventory the first shipping information within a first predetermined time; in response to determining that the first shipping information is not inventoried, generating a first status flag for the first shipping information, the first status flag indicating that the first shipping information needs to be inventoried; and transmitting the inventory task and the first status flag to a distribution site to request the distribution site to perform the inventory task. 2.The method of claim 1, wherein the inventory task comprises site information of the distribution site, the site information indicating a site type and location information of the distribution site, and wherein the generating the inventory task for the object based on an inventory policy comprises: determining the site information based on the first shipping information. 3.The method of claim 1, wherein the inventory task further comprises shipping information for the object, the shipping information indicating a shipping type and a shipping status of the object, and wherein the generating the inventory task for the object based on an inventory policy comprises: generating the shipping information based on the inventory policy. 4.The method of claim 1, wherein the inventory task further comprises time-sensitive information for the object, the time-sensitive information indicating an order time of a shipping order corresponding to the object and a deadline to inventory the first shipping information, and wherein the generating the inventory task for the object based on an inventory policy comprises: determining the time-sensitive information based on the inventory policy. 5.The method of claim 1, wherein the generating the inventory task for the object based on an inventory policy further comprises: generating the inventory task for the object based on the inventory policy at a predetermined period. 6.The method of claim 1, wherein the generating the inventory task for the object based on an inventory policy further comprises: determining whether a first inventory policy matching the first shipping information exists from a policy template pool; and in response to the first inventory policy existing, generating the inventory task based on the first inventory policy. 7.The method of claim 6, wherein the generating the inventory task for the object based on an inventory policy further comprises: in response to the first inventory policy not existing, creating a second inventory policy based on the first shipping information; and generating the inventory task based on the created second inventory policy; wherein the method further comprises: determining whether to save the second inventory policy based on the inventory task; and in response to determining to save the second inventory policy, saving the second inventory policy to the policy template pool. 8.A data processing method implemented at a distribution terminal device, comprising: ​ ​ ​ ​ receiving a check task and a first status mark of an object to be checked, the check task indicating checking first waybill information of the object within a first predetermined time, the first waybill information indicating attribute information and state information of the object, and the first status mark indicating that the first waybill information needs to be checked; and executing the check task, wherein the check task comprises: obtaining second waybill information of the object through information identification of the object; determining whether the first waybill information and the second waybill information match; in response to the first waybill information and the second waybill information matching, generating a second status mark for the first waybill information and the second waybill information, the second status mark indicating that the first waybill information and the second waybill information match; and in response to the first waybill information and the second waybill information not matching, generating a third status mark for the first waybill information and the second waybill information, the third status mark indicating that the first waybill information and the second waybill information do not match.

9. The method of claim 8, further comprising: in response to receiving the check task and the first status mark, displaying a task prompt mark, the task prompt mark indicating that the check task to be executed is received; and in response to triggering the task prompt mark, displaying a task check interface, the task check interface being used for executing the check task.

10. The method of claim 9, wherein the task check interface comprises a check determination control, the check determination control being used for determining whether the check task is completed, and the method further comprises: in response to an execution progress of the check task reaching a predetermined threshold, enabling the check determination control; and in response to triggering the check determination control, displaying a task prompt interface, the task prompt interface indicating a number of objects that do not complete the check task and processing prompt information, the processing prompt information indicating processing the objects whose first waybill information and second waybill information do not match within a second predetermined time.

11. The method of claim 10, wherein the task prompt interface comprises a check upload control, the check upload control being used for controlling termination of the check task and uploading images of the objects whose first waybill information and second waybill information do not match, and in response to triggering the check upload control, terminating the check task; in response to termination of the check task, generating a fourth status mark for the objects that do not complete the check task, the fourth status mark indicating that the objects corresponding to the check task are not completed; and uploading the images of the objects whose first waybill information and second waybill information do not match.

12. The method of claim 10, wherein the task prompt interface comprises a check completion control, the check completion control being used for controlling termination of the check task, and in response to triggering the check upload control, terminating the check task; In response to termination of the inventory task, generating a fourth status identifier for the object for which the inventory task is not completed, the fourth status identifier indicating that the corresponding inventory task of the object is not completed. 13.The method of claim 11, further comprising: In response to completion of the image uploading of the object for which the first shipping information and the second shipping information do not match, generating a fifth status identifier for the inventory task, the fifth status identifier indicating that the inventory task of the object for which the first shipping information and the second shipping information do not match is completed. 14.The method of claim 11, further comprising: In response to completion of the image uploading of the object for which the first shipping information and the second shipping information do not match, determining a time consumption of the image uploading; In response to the time consumption being greater than the second predetermined time, generating a sixth status identifier for the inventory task, the sixth status identifier indicating that the inventory task is not completed. 15.The method of claim 8, further comprising: In response to the inventory task not being completed within the first predetermined time after receiving the inventory task, generating a seventh status identifier for the inventory task, the seventh status identifier indicating that the inventory task is not completed. 16.A data processing apparatus implemented at a distribution control system, comprising: a receiving module configured to receive first shipping information of an object to be inventoried, the first shipping information indicating attribute information and status information of the object; a task generating module configured to generate an inventory task for the object based on an inventory policy, the inventory policy being determined based on at least the first shipping information, the inventory task indicating that the first shipping information is to be inventoried within a first predetermined time; a status marker generating module configured to generate a first status marker for the first shipping information in response to determining that the first shipping information is not inventoried, the first status marker indicating that the first shipping information needs to be inventoried; and a sending module configured to send the inventory task and the first status marker to a distribution site to request the distribution site to perform the inventory task. 17.A data processing apparatus implemented at a distribution terminal device, comprising: a receiving module configured to receive an inventory task and a first status marker for an object to be inventoried, the inventory task indicating that first shipping information of the object is to be inventoried within a first predetermined time, the first shipping information indicating attribute information and status information of the object, the first status marker indicating that the first shipping information needs to be inventoried; and an executing module configured to perform the inventory task, wherein the inventory task comprises: obtaining second shipping information of the object through information identification of the object; determining whether the first shipping information and the second shipping information match; in response to the first shipping information and the second shipping information matching, generating a second status marker for the first shipping information and the second shipping information, the second status marker indicating that the first shipping information and the second shipping information match; and ​ ​ ​ In response to the first shipment information and the second shipment information not matching, generating a third status flag for the first shipment information and the second shipment information, the third status flag indicating that the first shipment information and the second shipment information do not match.

18. An electronic device, comprising: at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions, when executed by the at least one processing unit, cause the electronic device to perform the method of any of claims 1-7 or 8-15.

19. A computer-readable storage medium having stored thereon a computer program, the computer program being executable by a processor to implement the method of any of claims 1-7 or 8-15.

20. A computer program product tangibly stored in a computer storage medium and comprising computer-executable instructions that, when executed by a device, cause the device to perform the method of any of claims 1-7 or 8-15.

Images