Equipment task generation method and device, equipment, medium and product

Abstract

The invention discloses an equipment task generation method and device, equipment, a medium and a product, and the method comprises the steps: obtaining the target information of a storage business document, and enabling the target information to comprise a business type, a task type and a target key data item; matching a target task model for the storage business document based on a preset matching rule of each task model and the target information; the storage business documents are aggregated based on a preset aggregation rule in the target task model to obtain an aggregated business document, the preset aggregation rule is that the storage business documents belonging to a preset dimension are aggregated according to the preset dimension, and the preset dimension comprises a container; and generating an equipment task corresponding to the aggregation business document. In this way, the expandability of task generation can be improved, different service scenes are adapted, and the equipment operation efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of warehousing technology, and in particular to a method, apparatus, equipment, medium and product for generating equipment tasks. Background Technology

[0002] With the development of intelligent manufacturing, traditional warehouse management is gradually evolving towards automation and intelligence. Modern WMS (Warehouse Management System) not only undertakes inventory management functions but also needs the ability to communicate with various automated devices and schedule tasks. Current WMS systems suffer from the following problems when interacting with hardware devices: fixed task generation methods make it difficult to adapt to different business scenarios, resulting in poor scalability; and similar tasks lead to repeated execution by devices, impacting equipment operating efficiency.

[0003] Therefore, improving the scalability of task generation to adapt to different business scenarios and enhance device operating efficiency are the technical problems that need to be solved. Summary of the Invention

[0004] In view of this, the purpose of this application is to provide a method, apparatus, device, medium, and product for generating equipment tasks, which can improve the scalability of task generation, adapt to different business scenarios, and improve equipment operating efficiency. The specific solution is as follows:

[0005] Firstly, this application provides a method for generating device tasks, including:

[0006] Obtain target information from warehousing business documents, wherein the target information includes business type, task type, and target key data items;

[0007] Based on the preset matching rules of each task model and the target information, the warehouse business document is matched with the target task model.

[0008] The warehouse business documents are aggregated based on the preset aggregation rules in the target task model to obtain aggregated business documents. The preset aggregation rules are to aggregate warehouse business documents belonging to the same preset dimension according to a preset dimension, and the preset dimension includes containers.

[0009] Generate the device task corresponding to the aggregated business document.

[0010] Optionally, generating the device task corresponding to the aggregated business document includes:

[0011] The target storage location is determined based on the target storage area information and storage location selection strategy set in the target task model.

[0012] Based on the target storage location, generate the device task corresponding to the aggregated business document.

[0013] Optionally, after generating the device task corresponding to the aggregated business document, the method further includes:

[0014] Based on the task processing rules set in the target task model, task attributes are set for the device task, wherein the task attributes include one or more of the following: whether to lock the target storage location, whether to allow waiting for execution, and whether to automatically generate the next stage task.

[0015] Optional, also includes:

[0016] When the task attribute is set to automatically generate the next stage task, the next stage task details are generated based on the current warehousing business documents.

[0017] The next stage task is generated based on the details of the next stage task.

[0018] Optionally, after generating the device task corresponding to the aggregated business document, the method further includes:

[0019] Determine whether there is a generated but unexecuted target task, wherein the target task is a task with the same characteristics as the device task, and the characteristics include the container to which it belongs;

[0020] If the target task exists, the device task is appended to the target task.

[0021] Optionally, if the target task exists, the device task is appended to the target task, including:

[0022] If the target task exists and the append attribute of the target task indicates that appending is allowed, then the device task is appended to the target task;

[0023] The additional attributes are configured by the target task model corresponding to the target task.

[0024] Secondly, this application provides a device task generation apparatus, comprising:

[0025] The information acquisition module is used to acquire target information from warehousing business documents, wherein the target information includes business type, task type, and target key data items;

[0026] The model matching module is used to match the target task model for the warehousing business document based on the preset matching rules of each task model and the target information.

[0027] The document aggregation module is used to aggregate the warehouse business documents based on the preset aggregation rules in the target task model to obtain aggregated business documents. The preset aggregation rules are to aggregate warehouse business documents belonging to the same preset dimension according to a preset dimension, and the preset dimension includes containers.

[0028] The task generation module is used to generate the device tasks corresponding to the aggregated business documents.

[0029] Thirdly, this application provides an electronic device, including a memory and a processor, wherein:

[0030] The memory is used to store computer programs;

[0031] The processor is used to execute the computer program to implement the aforementioned device task generation method.

[0032] Fourthly, this application provides a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the aforementioned device task generation method.

[0033] Fifthly, this application provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the aforementioned device task generation method.

[0034] As can be seen from the above solutions, this application provides a method for generating equipment tasks, including: obtaining target information of warehousing business documents, wherein the target information includes business type, task type, and target key data items; matching the warehousing business documents with target task models based on preset matching rules of each task model and the target information; aggregating the warehousing business documents based on preset aggregation rules in the target task model to obtain aggregated business documents, wherein the preset aggregation rules are to aggregate warehousing business documents belonging to the same preset dimension according to a preset dimension, the preset dimension including containers; and generating equipment tasks corresponding to the aggregated business documents.

[0035] As can be seen, the beneficial effects of this application are as follows: extracting the target information of warehousing business documents and matching it with the task model according to the preset matching rules, tasks can be generated according to the matched task model. By expanding the business model, it can adapt to different business scenarios. Furthermore, it can aggregate warehousing business documents with the same information according to preset dimensions to generate equipment tasks, avoiding the repeated operation of equipment caused by generating equipment tasks separately for similar warehousing business documents. In this way, the scalability of task generation can be improved, adapting to different business scenarios and improving equipment operating efficiency.

[0036] Correspondingly, the device task apparatus, device and readable storage medium provided in this application also have the above-mentioned technical effects. Attached Figure Description

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

[0038] Figure 1 A flowchart of a device task generation method provided in this application embodiment;

[0039] Figure 2 This application provides a schematic diagram of device task generation as an embodiment of the present application.

[0040] Figure 3 A timing diagram for the execution feedback of a scheduling task for shelving and warehousing equipment is provided in an embodiment of this application;

[0041] Figure 4 A schematic diagram of a data model provided in an embodiment of this application;

[0042] Figure 5 This is a schematic diagram of a device task generation apparatus provided in an embodiment of this application;

[0043] Figure 6 This is a structural diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0044] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0045] With the development of intelligent manufacturing, traditional warehouse management is gradually evolving towards automation and intelligence. Modern WMS systems not only handle inventory management but also need the ability to communicate and schedule tasks with various automated equipment (such as stacker cranes, AGVs, conveyors, sorting machines, and robotic arms). Current WMS systems face the following problems when interacting with hardware: Fixed task assignment methods: Most systems use hard-coded or fixed processes to configure task assignment rules, lacking flexibility and making it difficult to adapt to different business scenarios. Rigid scheduling strategies: Existing systems mostly use preset scheduling rules, making it difficult to dynamically adjust based on real-time warehouse information. Difficult human-machine collaboration: The lack of a unified configuration mechanism for task flow between humans and equipment leads to low collaboration efficiency. Poor scalability: Adding new business or changing processes requires extensive code modification and system refactoring, resulting in high maintenance costs. Poor aggregability: When multiple documents with the same business attributes generate equipment tasks, they cannot be dynamically added or aggregated, leading to duplicate execution and low operating efficiency. To address this, this application provides a device task generation solution that enhances the scalability of task generation, adapts to different business scenarios, and improves device operating efficiency. This solution features flexible, configurable, visualized, highly scalable device task generation that supports human-machine collaborative operations, thereby improving the intelligence and adaptability of the WMS system.

[0046] See Figure 1 As shown in the figure, this application discloses a device task generation method, including:

[0047] Step S11: Obtain the target information of the warehousing business document, wherein the target information includes the business type, task type and target key data items.

[0048] The business types can include outbound, inbound, and transfer; the task types can include put-away, de-putting, and moving. Shelves are used to store materials. Key target data can include data source (source warehouse area, storage location), container type, container code, and material attributes. Material attributes can include inbound time, style number, supplier, etc., or batch information determined based on inbound time, style number, and supplier. Warehouse areas can include pallet areas and bin areas, which can be uniquely identified by warehouse area numbers. Containers are used to place materials. Materials can be any items stored in the warehouse.

[0049] Step S12: Match the target task model to the warehousing business document based on the preset matching rules of each task model and the target information.

[0050] In this embodiment, it may be necessary to pre-set different task models and configure matching rules within each task model, i.e., preset matching rules. These rules include setting the business type, task type, and target key data items that can match the task model. The preset matching rules enable matching the corresponding business documents with the appropriate target task model.

[0051] If any warehousing business document matches multiple task models, the task model with the highest priority is selected according to the priority of the task models.

[0052] Step S13: Aggregate the warehousing business documents based on the preset aggregation rules in the target task model to obtain aggregated business documents. The preset aggregation rules are to aggregate warehousing business documents belonging to the same preset dimension according to a preset dimension, and the preset dimension includes containers.

[0053] This application embodiment can aggregate warehousing business documents based on preset aggregation rules, enabling warehousing business documents with the same specified information to be aggregated and generate a single equipment task. For example, it can aggregate warehousing business documents for the same container. The preset dimensions may also include material attributes, operators, etc. Since multiple business requests may be received at the same time, and each business request carries warehousing business documents, this application embodiment can aggregate multiple warehousing business documents that match the same task model.

[0054] Step S14: Generate the device task corresponding to the aggregated business document.

[0055] In this embodiment, an aggregated business document corresponding to multiple warehousing business documents can generate a single equipment task. The equipment task can be generated based on the aggregated business document and the task rules, task assignment rules, and task appending rules configured in the target task model.

[0056] Furthermore, generating the device task corresponding to the aggregated business document includes: determining the target storage location based on the target storage area information and storage location selection strategy set in the target task model; and generating the device task corresponding to the aggregated business document based on the target storage location.

[0057] In other words, target storage area information can be set in the task model, and the storage location selection strategy can be set in the task model or not, and implemented through external logic. Storage location selection strategies can be random, shortest path, load balancing, spatial quality balancing, or priority strategies, or a combination of these strategies. Specifically, a random strategy randomly selects a target storage location from the target storage area corresponding to the target storage area information. A priority strategy selects a target storage area based on the priority of multiple target storage areas, and then selects a target storage location within that target area. Multiple target storage areas can be set in the task model, each with a corresponding priority. If a priority strategy is combined with a random strategy, the target storage area is selected based on priority, and a storage location is randomly selected from within that target storage area. The shortest path strategy uses the source location in the warehousing business document, i.e., the source location of the material, to filter target storage locations in the target storage area according to the shortest path. The load balancing strategy selects storage areas with different material placement values ​​from multiple target storage areas according to a load balancing strategy. The spatial quality balancing strategy is used to balance the quality of materials in different storage areas. After selecting the target storage location, a device task is generated, and the corresponding path information, i.e. the path from the source location to the target storage location, can be set for the device task based on the target storage location.

[0058] Furthermore, after generating the device task corresponding to the aggregated business document, the method further includes: setting task attributes for the device task based on the task processing rules set in the target task model, wherein the task attributes include one or more of the following: whether to lock the target storage location, whether to allow waiting for execution, and whether to automatically generate the next stage task.

[0059] If the target storage location is locked, no other containers can be placed in that location. If the target storage location is not locked, other containers can be placed in it. If execution is allowed to wait, the system can wait for other tasks in the target storage location to complete before execution. If execution is not allowed to wait, and other tasks exist in the target storage location, a task failure message will be generated, or a new target storage location will be selected.

[0060] Furthermore, it also includes: when the task attribute is to automatically generate the next stage task, then generating the next stage task details based on the current warehousing business documents; and generating the next stage task based on the next stage task details.

[0061] The task details can be copied data from various information items in a warehouse business document. The current warehouse business document can be a single document or an aggregated document. In an aggregated document, only one item of identical information can be retained. For example, if the task types are the same, the corresponding business type is retained in the aggregated document. The quantities of the same material can be accumulated. The next-stage task is generated based on the next-stage task details; that is, the target information of the next-stage task details is obtained, and a target task model is matched based on the preset matching rules of each task model and the target information; the next-stage task is generated based on the target task model. If the preset aggregation rules are met, it can also be aggregated with other task details or warehouse business documents.

[0062] After generating the device task corresponding to the aggregated business document, the process further includes: determining whether there is an existing but unexecuted target task, wherein the target task is a task with the same characteristics as the device task, including its container; if the target task exists, the device task is appended to the target task. That is, tasks in the same container can be merged for execution. The same container refers to materials to be moved being in the same container. This further improves operational efficiency.

[0063] In an optional implementation, if the target task exists, the device task is appended to the target task, including: if the target task exists and the append attribute of the target task indicates that appending is allowed, then the device task is appended to the target task; wherein the append attribute is configured by the target task model corresponding to the target task. That is, task appending rules can be configured in the task model to configure whether tasks are allowed to be appended.

[0064] In addition, the task model can also include task distribution rules, i.e., configuration to allow or disallow distribution, and can also set some distribution conditions. Considering that some tasks are performed manually, this embodiment of the application can be configured to disallow distribution, i.e., not distribute to the device for execution.

[0065] This application embodiment obtains the task model through a graphical user interface, meaning users can configure various rules through the graphical user interface to obtain the corresponding task model. New task models can be created, or existing task models can be modified.

[0066] In other words, this embodiment allows configuration of a task model, including matching rules (for filtering). These rules can include the source warehouse (starting warehouse), material attributes, etc., specifying where the container originates (the location of the material) and what attributes of the material are contained in the container to generate a task. Processing rules can also be configured, including setting the target warehouse (where the container needs to be moved) and task waiting (yes / no). If the target warehouse has no available storage space, the task is not sent to the equipment, and the background continuously refreshes until an available storage space becomes available. Otherwise, if the target warehouse has no available storage space, the task execution fails. Aggregation rules can also be configured, such as aggregation by container. For example, if there are ten material movement requirements, but these materials belong to only two containers, only two container movements need to be moved, requiring only two equipment movement tasks instead of ten. Multiple target warehouses can be selected, prioritizing available storage spaces from those with higher priority. The storage space selection algorithm can be configured in the background according to the project; a factory can configure one or more selection algorithms.

[0067] In this embodiment, processes for each business type can be pre-designed. For example, the inbound process can involve first receiving containers (putting materials into containers), then placing the containers at the inbound checkpoint for shelving confirmation (corresponding to inbound-shelving, inbound stage one), and then moving the containers from the inbound checkpoint to the storage location via equipment tasks (corresponding to inbound-movement, inbound stage two). In the outbound process, the containers are first moved from the storage location to the picking location via equipment tasks (corresponding to outbound-movement, outbound stage one), and then manual picking is performed (corresponding to outbound-removal, outbound stage two).

[0068] In this embodiment of the application, the model can be configured to automatically generate the next stage task. For example, after the first stage of warehousing is completed, the second stage task is automatically generated based on the shelving position of the first stage as the starting position. After the first stage of outbound is completed, the second stage task is automatically generated based on the target position of the first stage as the starting position. The generated task (may include setting the starting position, target position, recording which materials are included, which container is moved, etc.).

[0069] Furthermore, by adding rules, if a task that has already been generated has not yet been issued because there is no available target storage location, and then there is a material handling requirement, and this material also belongs to the container corresponding to this task, then this material can also be added and recorded, without having to generate the task again.

[0070] This embodiment allows configuration of distribution rules, which can restrict distribution to containers (container codes are not empty). It can be configured to not distribute in the first stage of warehousing, distribute in the second stage of warehousing, distribute in the first stage of outbound, not distribute in the second stage of outbound, distribute for equipment handling, and not distribute for manual operations, etc.

[0071] Furthermore, this application embodiment provides exception handling and task rescheduling: it has an exception detection mechanism, which can manually trigger device task scheduling when a device task fails or its status is abnormal. After obtaining task failure information, the task status is displayed on the task list, and the task can be reissued after manually ruling out hardware device abnormalities; rollback strategies, backup device switching strategies, and manual intervention mechanisms can be configured. After obtaining task failure information, the task status is displayed on the task list, and the manual intervention mechanism can be manually operated to place the container in the target storage location (and then click complete, without waiting for device callback notification). Rollback cancels the task and business documents. Backup device switching is based on the device response. If there is an abnormal device, the abnormal device is removed from the available device list in the background, and the backup device is activated.

[0072] As can be seen, the embodiments of this application extract the target information of the warehousing business documents and match it with the task model according to the preset matching rules. The task can be generated according to the matched task model. By expanding the business model, it can adapt to different business scenarios. Furthermore, warehousing business documents with the same information can be aggregated according to preset dimensions to generate equipment tasks, avoiding the repeated operation of equipment caused by generating equipment tasks separately for similar warehousing business documents. In this way, the scalability of task generation can be improved, adapting to different business scenarios and improving equipment operating efficiency.

[0073] Further, see Figure 2 As shown, Figure 2This is a schematic diagram illustrating equipment task generation provided in an embodiment of this application. Equipment tasks are generated from warehouse business documents based on task models. Task models can be matched to warehouse business documents. The matching process can be based on information such as the business attributes (outbound, inbound, transfer), task type (put on shelf, unput on shelf, move), and rule conditions in the task model (i.e., the aforementioned preset matching rules). If multiple task models are matched, they are sorted according to their priority, and the task model with the highest priority can be selected as the target task model. Thus, an outbound document with a task type of "movement" can be equipped with an outbound movement model, an inbound document with a task type of "movement" can be matched with an inbound movement model, and a transfer document with a task type of "movement" can be matched with a transfer movement model. Rule conditions can be set in the task model to filter warehouse business documents. These conditions can include single or multiple selections of document status, warehouse area, material attributes, operator role, etc. When multiple selections are made, a submission set or union set can be used to filter out business documents used to generate equipment tasks. If a task model is matched, it means that there are warehouse business documents that meet the preset matching rules and are matched with the corresponding task model. Business documents can be further aggregated according to aggregation rules, and target storage locations can be selected to generate equipment tasks. Aggregation rules set in the task model, such as conditions like identical containers, identical material attributes, or identical operators, can be used to select single or multiple aggregated documents. The target storage area set in the task model limits the selection range of target storage locations, and the target storage location is selected based on the set storage location selection algorithm (such as random, shortest path, load balancing, space quality equalization, priority, etc.), generating the equipment task. Furthermore, equipment task attributes can be set according to task processing rules, including whether to lock the target storage location, whether the task can wait, and whether to automatically generate the next stage task document. The system can further determine if a target task exists—that is, a generated but unexecuted task with the same characteristics, such as a task with the same container. If it does not exist, a new equipment task is stored, which is the generated equipment task. The current document's generated task details are associated with this equipment task. If the distribution rules are met, the task distribution ends. If no target task exists, determine whether the task appending rules are met. If so, generate task details for the current document and associate them with the target task. If the task appending rules are not met, store the new device task (i.e., the generated device task) and associate the task details for the current document with the device task. If the task does not meet the distribution rules, wait for the task to be assigned.

[0074] The WMS system can define a standardized task model structure, which includes information such as business type, task type, matching rules, aggregation rules, processing rules, execution path (target storage area), task appending rules, and task distribution rules. The task model supports a graphical configuration interface, allowing users to dynamically configure it. Dynamic task generation: When the WMS system receives a business document request, it generates a specific equipment scheduling task based on the task model. The scheduling engine supports various scheduling algorithms (such as random, shortest path, load balancing, space quality equalization, priority, etc.) and can be configured to select the corresponding target storage location. Equipment task distribution and execution feedback: The generated equipment scheduling tasks are distributed to the equipment control system through interfaces such as REST API (Representational State Transfer Application Programming Interface), MQTT (Message Queuing Telemetry Transport), and OPC UA (OPC Unified Architecture). After executing a task, the equipment control system feeds back the execution status (such as success, failure, or interruption) to the WMS system, completing business document processing and forming a closed-loop control. Anomaly handling and task rescheduling: The system has an anomaly detection mechanism. When a device task fails or its status is abnormal, device task rescheduling can be manually triggered. Rollback strategies, backup device switching strategies, and manual intervention mechanisms can be configured.

[0075] In this embodiment, for materials in the same container (or other materials with the same attributes) that are repeatedly requisitioned, they can be aggregated into a single handling task instead of generating multiple tasks. In the first and second stages of outbound processing, manual and equipment tasks can be linked through business documents. If the first stage is not completed, the second stage cannot be operated (the materials have not been moved out and cannot be taken; a message indicating that the task is in progress can be displayed to avoid manual execution). In the first and second stages of inbound processing, manual and equipment tasks can be linked through business documents. In the first stage, the container is placed at the inbound checkpoint, and the completion is confirmed by a person (or by a camera scanning the container barcode and notifying the system), which triggers the second stage of handling, moving the container to the storage location. Furthermore, multiple target storage areas can be configured, sorted by priority from high to low, to obtain available target storage locations (based on the filtering algorithm configured for each factory). Additionally, tasks can be configured to be issued or not issued based on the task type.

[0076] See Figure 3 As shown, Figure 3This application provides a timing diagram for the execution feedback of a warehouse placement and storage equipment scheduling task. The WMS task scheduling module generates a first-stage WMS conveyor belt task based on the placement order and sends it to the WCS (Equipment Control System). The WCS receives hardware identification information indicating that the container has arrived at the conveyor belt gate and reports the container code and gate location to the WMS task scheduling module. The WMS task scheduling module finds the corresponding first-stage WMS task based on the container code, transmits the actual gate location, confirms the placement, updates the placement order (actual storage location), receiving order, and storage order status, updates the storage location inventory (with container), and generates a second-stage task detail from the first-stage WMS task details (the target storage location of the first-stage task is the starting storage location of the second-stage task). The first-stage WMS task serves as the data source, and the second-stage task (issuance strategy) is generated according to the task model. If there are incomplete tasks under the same task model and aggregation rule, the task details are updated according to the model configuration, and the associated task ID (identifier) ​​is updated. If no additional tasks can be added, a new task is generated. The process involves updating task details, associating task IDs and statuses, generating a second-stage task to be executed through the WMS task status processing module, locking the target storage location for the second-stage WMS task, issuing second-stage transport equipment task information, generating a transport equipment task in the WCS (equipment control center), returning task information to the WMS task scheduling module, updating the second-stage WMS task (issuance strategy), associating the transport equipment task ID, starting the transport, processing the second-stage task status (in execution / left the starting storage location) in the WMS task status processing module, triggering a second-stage transport task start callback, updating the task status in the WMS task scheduling module, completing the second-stage task (excluding manually operated tasks), updating the WMS task (issuance strategy), task details status completion, information, releasing the starting storage location, and updating the storage location inventory (with containers) according to the task details by calling the transfer logic, and binding the container storage location.

[0077] Further, see Figure 4 As shown, Figure 4This application provides a data model diagram, which may include a database model design for equipment tasks, task models, and task details. The task-detail association table includes task ID, detail ID, and some basic fields. The details are the task details, or task data source details, and may include detail ID, source document type (e.g., receiving slip, putaway slip, picking slip), source order number, source detail item, business type (inbound, outbound, etc.), task type (putaway, descent, move, adjust, etc.), container code, source warehouse area, target warehouse area, target warehouse location, material number, material name, color code, style number, production order number, PO (purchase order code), supplier, quantity, detail status (pending generation, generated, returned), etc. The model table can... This includes model ID, business type (inbound, outbound, etc.), task type (put on hold, drop, move, adjust, etc.), task source (details, task), strategy description, strategy type (issue, generate), priority, source storage location, recommended storage location strategy, whether the task is waiting, aggregation rules, target storage area, whether the source storage location is locked, whether the target storage location is locked, and whether the task has appended detailed rules (yes, no). The task table can include task status, container code, business type (inbound, outbound, etc.), task type (put on hold, drop, move, adjust, etc.), starting storage location, starting storage area, target storage location, target storage area, recommended storage location, human-processed mark, task operator, device task ID, preceding task identifier, model ID, operator, etc. It can also provide a model filtering rule association table, including rule ID, model ID, filtering data source field, comparison type, comparison value, rule association symbol '(-)', rule association logic 'AND-OR', rule type 1, task append rule 2, filtering rule conditions, etc.

[0078] This provides a task-model-based device scheduling task generation solution, achieving deep integration of task scheduling and device control within the WMS system. This improves the automation level and scheduling efficiency of the warehouse system, demonstrating promising application prospects and widespread application value. It can generate downstream hardware device scheduling tasks based on task model configuration, achieving seamless integration between the task model and hardware device control within the WMS system, and enhancing the flexibility, intelligence, and scalability of task scheduling. Key features include: High flexibility: Through visual process modeling, users can freely define task flows to adapt to various business scenarios. Enhanced device compatibility: Support for multi-vendor and multi-type device access through a protocol adapter mechanism. Intelligent scheduling: Introducing a dynamic optimization mechanism to achieve optimal task execution. Convenient operation and maintenance: Providing task execution monitoring, log tracking, and anomaly handling functions to improve system maintainability. Strong scalability: Supporting task flow version management and modular expansion, facilitating system upgrades and feature iterations.

[0079] See Figure 5 As shown, this application provides a device task generation apparatus, including:

[0080] The information acquisition module 11 is used to acquire target information of warehousing business documents, wherein the target information includes business type 12, task type and target key data items;

[0081] The model matching module 13 is used to match the target task model for the warehousing business document based on the preset matching rules of each task model and the target information.

[0082] The document aggregation module 14 is used to aggregate the warehouse business documents based on the preset aggregation rules in the target task model to obtain aggregated business documents. The preset aggregation rules are to aggregate warehouse business documents belonging to the same preset dimension according to a preset dimension, and the preset dimension includes containers.

[0083] The task generation module 15 is used to generate the device tasks corresponding to the aggregated business documents.

[0084] As can be seen, the embodiments of this application extract the target information of the warehousing business documents and match it with the task model according to the preset matching rules. The task can be generated according to the matched task model. By expanding the business model, it can adapt to different business scenarios. Furthermore, warehousing business documents with the same information can be aggregated according to preset dimensions to generate equipment tasks, avoiding the repeated operation of equipment caused by generating equipment tasks separately for similar warehousing business documents. In this way, the scalability of task generation can be improved, adapting to different business scenarios and improving equipment operating efficiency.

[0085] Specifically, the task generation module 15 can be used to: determine the target storage location based on the target storage area information and storage location selection strategy set in the target task model; and generate the equipment task corresponding to the aggregated business document based on the target storage location.

[0086] Furthermore, the device may also include an attribute setting module for setting task attributes for the device task based on the task processing rules set in the target task model, wherein the task attributes include one or more of the following: whether to lock the target storage location, whether to allow waiting for execution, and whether to automatically generate the next stage task.

[0087] Furthermore, the device also includes an automatic task generation module, used to: when the task attribute is to automatically generate the next stage task, generate the next stage task details based on the current warehousing business documents; and generate the next stage task based on the next stage task details.

[0088] Furthermore, the device may also include:

[0089] The task judgment module is used to determine whether there is a generated but unexecuted target task after the device task corresponding to the aggregated business document is generated. The target task is a task with the same characteristics as the device task, and the characteristics include the container to which it belongs.

[0090] The task appending module is used to append the device task to the target task if the target task exists.

[0091] The task appending module can be used to append the device task to the target task if the target task exists and the appending attribute of the target task indicates that appending is allowed; wherein the appending attribute is configured by the target task model corresponding to the target task.

[0092] See Figure 6 As shown in the figure, this application discloses an electronic device 20, including a processor 21 and a memory 22; wherein, the memory 22 is used to store a computer program; the processor 21 is used to execute the computer program, the device task generation method disclosed in the foregoing embodiment.

[0093] For details regarding the specific process of the above-mentioned device task generation method, please refer to the relevant content disclosed in the foregoing embodiments, which will not be repeated here.

[0094] Furthermore, the memory 22, as a carrier for resource storage, can be a read-only memory, random access memory, disk, or optical disk, and the storage method can be temporary storage or permanent storage.

[0095] In addition, the electronic device 20 also includes a power supply 23, a communication interface 24, an input / output interface 25, and a communication bus 26; wherein, the power supply 23 is used to provide operating voltage for the various hardware devices on the electronic device 20; the communication interface 24 can create a data transmission channel between the electronic device 20 and external devices, and the communication protocol it follows can be any communication protocol applicable to the technical solution of this application, and is not specifically limited here; the input / output interface 25 is used to acquire external input data or output data to the outside world, and its specific interface type can be selected according to specific application needs, and is not specifically limited here.

[0096] Furthermore, embodiments of this application also disclose a computer-readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the device task generation method disclosed in the foregoing embodiments.

[0097] For details regarding the specific process of the above-mentioned device task generation method, please refer to the relevant content disclosed in the foregoing embodiments, which will not be repeated here.

[0098] Furthermore, embodiments of this application provide a computer program product, including a computer program / instructions, which, when executed by a processor, implement the device task generation method disclosed in the foregoing embodiments.

[0099] For details regarding the specific process of the above-mentioned device task generation method, please refer to the relevant content disclosed in the foregoing embodiments, which will not be repeated here.

[0100] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on its differences from other embodiments. Similar or identical parts between embodiments can be referred to interchangeably. For the apparatus disclosed in the embodiments, since it corresponds to the method disclosed in the embodiments, the description is relatively simple; relevant parts can be referred to in the method section.

[0101] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be implemented directly by hardware, a software module executed by a processor, or a combination of both. The software module can be located in random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art.

[0102] The above provides a detailed description of a device task generation method, apparatus, device, medium, and product provided by this application. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for generating equipment tasks, characterized in that, include: Obtain target information from warehousing business documents, wherein the target information includes business type, task type, and target key data items; Based on the preset matching rules of each task model and the target information, the warehouse business document is matched with the target task model. The warehouse business documents are aggregated based on the preset aggregation rules in the target task model to obtain aggregated business documents. The preset aggregation rules are to aggregate warehouse business documents belonging to the same preset dimension according to a preset dimension, and the preset dimension includes containers. Generate the device task corresponding to the aggregated business document.

2. The task generation method according to claim 1, characterized in that, The device task that generates the aggregated business document includes: The target storage location is determined based on the target storage area information and storage location selection strategy set in the target task model. Based on the target storage location, generate the device task corresponding to the aggregated business document.

3. The task generation method according to claim 1, characterized in that, After generating the device task corresponding to the aggregated business document, the process also includes: Based on the task processing rules set in the target task model, task attributes are set for the device task, wherein the task attributes include one or more of the following: whether to lock the target storage location, whether to allow waiting for execution, and whether to automatically generate the next stage task.

4. The task generation method according to claim 3, characterized in that, Also includes: When the task attribute is set to automatically generate the next stage task, the next stage task details are generated based on the current warehousing business documents. The next stage task is generated based on the details of the next stage task.

5. The task generation method according to claim 1, characterized in that, After generating the device task corresponding to the aggregated business document, the process also includes: Determine whether there is a generated but unexecuted target task, wherein the target task is a task with the same characteristics as the device task, and the characteristics include the container to which it belongs; If the target task exists, the device task is appended to the target task.

6. The task generation method according to claim 5, characterized in that, If the target task exists, the device task is appended to the target task, including: If the target task exists and the append attribute of the target task indicates that appending is allowed, then the device task is appended to the target task; The additional attributes are configured by the target task model corresponding to the target task.

7. A device for generating equipment tasks, characterized in that, include: The information acquisition module is used to acquire target information from warehousing business documents, wherein the target information includes business type, task type, and target key data items; The model matching module is used to match the target task model for the warehousing business document based on the preset matching rules of each task model and the target information. The document aggregation module is used to aggregate the warehouse business documents based on the preset aggregation rules in the target task model to obtain aggregated business documents. The preset aggregation rules are to aggregate warehouse business documents belonging to the same preset dimension according to a preset dimension, and the preset dimension includes containers. The task generation module is used to generate the device tasks corresponding to the aggregated business documents.

8. An electronic device, characterized in that, Includes memory and processor, wherein: The memory is used to store computer programs; The processor is configured to execute the computer program to implement the device task generation method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, Used to store a computer program, wherein the computer program, when executed by a processor, implements the device task generation method as described in any one of claims 1 to 6.

10. A computer program product, characterized in that, Includes a computer program / instruction that, when executed by a processor, implements the device task generation method as described in any one of claims 1 to 6.

Images