Article scheduling method, processor and program product
By dynamically adjusting the scheduling permissions of warehouse administrators and using distributed log storage, the problems of rigid permissions and audit risks in the parts warehousing system were solved, improving data processing efficiency and system security.
Patent Information
- Application Number
- CN202511552488.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-10-28
- Publication Date
- 2026-02-10
AI Technical Summary
The existing parts warehousing system's access control and auditing mechanisms are rigid, lack operational flexibility, resulting in low data processing efficiency, inability to adapt to dynamic production needs, and audit risks and security vulnerabilities.
By parsing production work orders, the scheduling permissions of warehouse administrators are dynamically adjusted, and permissions are automatically updated according to work order requirements. Combined with 3D maps and material codes, refined permission control is achieved, and a distributed log storage and encryption mechanism is adopted to realize real-time adjustment of permissions and security auditing.
It improved data processing efficiency, reduced manual intervention, enhanced system flexibility and security, reduced the risk of production line downtime, and achieved real-time risk interception and multi-dimensional risk control capabilities.
Smart Images

Figure CN121504338A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of logistics and transportation, and more specifically, to a method for scheduling goods, a processor, and a program product. Background Technology
[0002] Currently, access control and auditing mechanisms for parts warehousing systems typically employ static Role-Based Access Control (RBAC). This method assigns fixed permissions to predefined roles (such as warehouse managers and purchasing staff), with each role bound to its operational scope (e.g., warehouse managers have default access to modify all inventory). For example, this method can use a centralized database to set permission rules; role changes require manual adjustments to configuration files or contacting the administrator. Alternatively, a centralized audit log system can be used. This method stores all operation logs centrally on a single server or database. During auditing, data is retrieved from the central node, and abnormal records are manually filtered. For instance, a Structured Query Language (SQL) database can be used to record operation data, including time, operator, and action type (e.g., inbound, outbound, modification). This method relies on regular backups to prevent data loss.
[0003] However, the above methods suffer from rigid permissions and insufficient operational flexibility: static roles cannot adapt to dynamic production needs. For example, when an urgent order requires the temporary allocation of parts from multiple warehouses, the warehouse manager must apply for permissions at each level, which is too time-consuming. Therefore, the above methods suffer from the technical problem of low data processing efficiency.
[0004] There is currently no effective solution to the above problems. Summary of the Invention
[0005] This application provides a method for scheduling items, a processor, and a program product to at least solve the technical problem of low data processing efficiency.
[0006] According to one aspect of the embodiments of this application, a method for scheduling items is provided. The method may include: in response to obtaining a production work order, parsing the production work order to obtain work order demand data, wherein the production work order is used to request the scheduling of items stored in a storage area, and the work order demand data is used to represent the items to be scheduled in the storage area, and the scheduling information of the items to be scheduled; determining the scheduling permission information of a warehouse management object in the storage area according to the work order demand data, wherein the scheduling permission information is used to represent the permission of the warehouse management object to schedule the items to be scheduled; and in response to a scheduling instruction from the warehouse management object, satisfying the scheduling permission information, scheduling the items to be scheduled according to the scheduling instruction.
[0007] Optionally, in response to obtaining a production work order, the production work order is parsed to obtain work order demand data, including: in response to obtaining a production work order, determining the priority level of the production work order, wherein the priority level is used to characterize the urgency of the production work order; in response to the priority level being greater than a level threshold, parsing the production work order to obtain work order demand data.
[0008] Optionally, the scheduling permission information includes: outbound information and the scheduling areas allowed for scheduling in the storage area. Based on the work order demand data, the scheduling permission information of the warehouse management object in the storage area is determined, including: determining the scheduling information and the sub-storage area storing the items to be scheduled based on the work order demand data; determining the outbound information based on the scheduling information and obtaining the location information of the storage sub-storage area; and determining the scheduling area based on the location information.
[0009] Optionally, the method may further include: obtaining a three-dimensional map of the storage area; and determining the initial scheduling permission information of the warehouse management object according to the three-dimensional map.
[0010] Optionally, the method may further include: determining the material code of the items stored in the storage area, wherein the material code is used to determine the category of the items; and adjusting the initial scheduling permission information according to the material code.
[0011] Optionally, the method may further include: in response to the completion of scheduling of the items to be scheduled, adjusting the scheduling permission information to the initial scheduling permission information and generating a scheduling log, wherein the scheduling log is used to record the retrieval status of the items to be scheduled.
[0012] Optionally, the method may further include: splitting the scheduling log to obtain at least one sub-scheduling log; encrypting the at least one sub-scheduling log to obtain at least one encrypted log; and transmitting the encrypted log to multiple edge nodes for storage.
[0013] Optionally, the method may further include: in response to receiving a deletion command to delete encrypted logs, determining the triggering object that triggered the deletion command; determining whether the triggering object has deletion permission to delete encrypted logs; and in response to the triggering object not having deletion permission, outputting a prompt message.
[0014] According to another aspect of the embodiments of this application, a scheduling device for items is also provided. The device may include: a parsing unit, configured to parse a production work order in response to receiving such a work order to obtain work order demand data, wherein the production work order requests the scheduling of items stored in a storage area, and the work order demand data represents the items to be scheduled in the storage area, as well as scheduling information for the items to be scheduled; a determining unit, configured to determine scheduling permission information of a warehouse management object in the storage area according to the work order demand data, wherein the scheduling permission information represents the permission allowed for the warehouse management object to schedule the items to be scheduled; and a scheduling unit, configured to, in response to a scheduling instruction from the warehouse management object, satisfy the scheduling permission information and schedule the items to be scheduled according to the scheduling instruction.
[0015] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein, when the program is running, it controls the device where the computer-readable storage medium is located to execute the article scheduling method of the embodiments of this application.
[0016] According to another aspect of the embodiments of this application, a processor is also provided for running a program, wherein the program is executed by the processor to perform the item scheduling method of the embodiments of this application.
[0017] According to another aspect of the embodiments of this application, a program product is also provided, the program product including computer instructions, wherein the computer instructions, when executed by a processor, implement the item scheduling method of the embodiments of this application.
[0018] According to another aspect of the embodiments of this application, a vehicle is also provided, which can be used to perform the item scheduling method of the embodiments of this application.
[0019] In this embodiment, in response to obtaining a production work order, the production work order is parsed to obtain work order demand data. The production work order requests the scheduling of items stored in the storage area, and the work order demand data represents the items to be scheduled in the storage area, along with their scheduling information. Based on the work order demand data, the scheduling permission information of the warehouse management object in the storage area is determined. This scheduling permission information represents the permission allowed for the warehouse management object to schedule the items to be scheduled. In response to a scheduling instruction from the warehouse management object, the scheduling permission information is satisfied, and the items to be scheduled are scheduled according to the scheduling instruction. In other words, in this embodiment, after obtaining a production work order, the production work order is parsed to obtain work order demand data. Based on the work order demand data, the warehouse administrator's scheduling permission information is updated. When a scheduling instruction is obtained, the corresponding items to be scheduled can be scheduled according to the instruction. This method automatically adjusts the administrator's scheduling permission information without requiring manual adjustment of the warehouse management object's permissions, thereby improving data processing efficiency and solving the problem of low data processing efficiency. Attached Figure Description
[0020] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:
[0021] Figure 1 This is a flowchart of an item scheduling method according to an embodiment of this application;
[0022] Figure 2 This is a schematic diagram of a distributed storage system according to an embodiment of this application;
[0023] Figure 3 This is a flowchart of another item scheduling process timeline according to an embodiment of this application;
[0024] Figure 4 This is a schematic diagram of an item dispatching device according to an embodiment of this application;
[0025] Figure 5 This is a structural block diagram of a computer terminal according to an embodiment of this application;
[0026] Figure 6 This is a block diagram of an electronic device for a method of scheduling items according to an embodiment of this application. Detailed Implementation
[0027] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.
[0028] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.
[0029] Currently, access control and auditing mechanisms for parts warehousing systems typically employ static role-based access control. This method assigns fixed permissions, binding roles to specific operational scopes (e.g., warehouse managers have default modification permissions for all inventory). For example, this method can use a centralized database to set permission rules; role changes require manual adjustments to configuration files or contacting the administrator. Alternatively, a centralized audit log system can be used. This method stores all operation logs centrally on a single server or database. During auditing, data is retrieved from the central node, and abnormal records are manually filtered. For instance, a structured query language database can be used to record operation data, including time, operator, and action type (e.g., inbound, outbound, modification). This method relies on regular backups to prevent data loss.
[0030] However, the above methods suffer from rigid permissions and insufficient operational flexibility: static roles cannot adapt to dynamic production needs. For example, when an urgent order requires the temporary allocation of parts from multiple warehouses, warehouse managers must apply for permissions at each level, which is time-consuming (usually exceeding one hour) and risks production line shutdowns. Furthermore, the above methods have coarse-grained permissions, with role permissions divided by the overall warehouse (e.g., "Warehouse A Administrator"), failing to refine permissions to the location or batch level (e.g., only allowing operation of the metal parts area in Warehouse A).
[0031] Meanwhile, the above methods have audit risks, such as the risk of data tampering. Centralized logs are stored on a single server, and attackers can directly delete or tamper with records by intruding into the server (e.g., to cover up abnormal outbound behavior). Traceability is inefficient; cross-warehouse and cross-system operations require manual integration of logs from multiple sources, which is time-consuming (averaging 3-5 hours) and prone to missing key information (e.g., unlinked supplier delivery records). Furthermore, the methods have certain security vulnerabilities. For example, static permissions cannot intercept operations in non-business scenarios (e.g., large-scale outbound shipments at 2 AM), requiring manual post-event verification and failing to prevent risks in real time, potentially leading to uncontrolled non-routine operations. In addition, the method relies only on basic rules (e.g., inventory threshold alarms) and lacks multi-dimensional correlation analysis (e.g., frequent account modifications of inventory thresholds + operations outside of working hours), resulting in a single dimension for anomaly detection.
[0032] Alternatively, the root cause of the aforementioned shortcomings can be attributed to limitations in the technical architecture and design logic. In the methods described above, the permission model lacks dynamism and adaptability, with static role binding and a disconnect between permission allocation and production tasks, making it impossible to dynamically adjust based on the urgency of work orders and resource scheduling needs. Furthermore, these methods rely excessively on manual intervention, requiring manual approval in urgent scenarios, which contradicts the trend towards automation and real-time processing in the manufacturing industry.
[0033] Meanwhile, the centralized audit log system suffers from outdated technical architecture and a single point of failure: centralized storage makes it an easy target for attacks and poses a risk of single-point failure (such as server downtime causing audit paralysis). Log analysis technology is lagging, relying on manual retrieval and simple keyword matching, without the introduction of automated rule engines or multi-dimensional correlation analysis. Security mechanisms are poorly designed, employing a passive defense model: primarily relying on post-event tracing, lacking real-time interception and proactive risk control capabilities. The rule base is isolated and fragmented: risk control dimensions such as time, quantity, and behavior have not formed a composite detection model, resulting in a high false negative rate (e.g., only detecting single-day outbound volume, ignoring abnormal operation times).
[0034] To address the aforementioned issues, this application provides a method for scheduling items. After obtaining a production work order, the method parses the work order to obtain work order demand data. Based on this demand data, it updates the warehouse administrator's scheduling permission information. Upon receiving a scheduling instruction, the corresponding items to be scheduled can be scheduled accordingly. This method automatically adjusts the administrator's scheduling permission information, eliminating the need for manual adjustments to the permissions of warehouse management objects. This achieves the technical effect of improving data processing efficiency and solves the technical problem of low data processing efficiency.
[0035] According to an embodiment of this application, an embodiment of a method for scheduling items is provided. The steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Although a logical order is shown in the flowchart, in some cases, the steps shown or described may be performed in a different order than that shown here.
[0036] Figure 1 This is a flowchart of a method for scheduling items according to an embodiment of this application. Figure 1 As shown, the method may include the following steps:
[0037] Step S102: In response to obtaining a production work order, the production work order is parsed to obtain work order demand data. The production work order is used to request the scheduling of items stored in the storage area, and the work order demand data is used to represent the items to be scheduled in the storage area and the scheduling information of the items to be scheduled.
[0038] In the technical solution provided in step S102 of this application, the production work order can be a work task order generated by a production plan or sales order, can be generated by a production management system (such as an ERP or MES system) based on a production plan or sales order, or can be an instruction sheet used to guide warehouse managers or other operators to perform logistics operations. It can include, but is not limited to, details such as production requirements, operation instructions, product information, quantity, time and location.
[0039] For example, suppose a company receives a sales order that requires 1,000 engine parts to be shipped out within 24 hours. The production management system can generate a production work order that specifies the need to dispatch 1,000 engine parts from "Warehouse A - Engine Area" and mark it as "high priority".
[0040] Optionally, the aforementioned work order demand data can be demand data parsed from production work orders, or key information extracted from production work orders, used to guide the system on how to adjust permissions and how to execute scheduling. This can include, but is not limited to, the type, quantity, location, priority, and operation time window of the items to be scheduled. It is used to guide the warehouse management system on how to adjust permissions and implement scheduling operations.
[0041] For example, the following key data can be extracted from the production work order: the item to be scheduled is "engine parts", the quantity is 1000 units, the storage area is "Warehouse A - Engine Area", the scheduling time is the next 24 hours, and the priority is marked as "high".
[0042] Optionally, the above scheduling information can be used to determine the details of the items to be scheduled, including but not limited to: the scheduling quantity of the items to be scheduled, the scheduling process, the time window, the location, the operation method, etc. It should be noted that this is only an example and there are no specific restrictions on the content of the work order requirement data.
[0043] Optionally, after obtaining the production work order, the items to be scheduled, as well as the scheduling quantity and location of the items to be scheduled, can be determined based on the production work order. Therefore, the production work order can be parsed to obtain the work order demand data.
[0044] Optionally, the aforementioned storage area can be a warehouse or other area for storing goods. These goods can include materials, electronic components, etc. It should be noted that there are no specific restrictions on the category of goods here.
[0045] Step S104: Based on the work order requirement data, determine the scheduling permission information of the warehouse management object in the storage area. The scheduling permission information is used to indicate the permission of the warehouse management object to schedule the items to be scheduled.
[0046] In the technical solution provided in step S104 of this application, the aforementioned scheduling permission information can be a description of the permissions granted to the warehouse management object when performing scheduling operations. It can refer to the permission information possessed by the warehouse management object when performing a specific scheduling operation. It can be dynamically generated based on work order demand data and may include, but is not limited to, the type of items operated by the warehouse management object, the area of operation, the allowed operation time, and other special permissions. Under the dynamic permission adjustment mechanism in this application, the scheduling permission information can be automatically adjusted according to the current work order demand. The aforementioned warehouse management object can be a predefined role, such as a warehouse manager (i.e., a warehouse administrator), a purchasing agent, or other object managing the warehouse. It should be noted that this is only an example and does not impose specific restrictions on the identity of the warehouse management object.
[0047] For example, the warehouse manager can only operate "Warehouse B - General Parts Area". However, based on the work order demand data of the emergency production work order, the warehouse manager's scheduling permission information was dynamically adjusted, allowing him to operate "Warehouse A - Engine Area" for the next 8 hours, with the outbound limit temporarily set at 1,000 engine parts.
[0048] Optionally, the traditional static role-based access control method assigns fixed operating permissions according to predefined roles (such as warehouse managers and purchasing agents). In this embodiment, a dynamic permission adjustment mechanism is proposed. This mechanism can automatically grant or adjust the permissions of warehouse management objects according to the urgency of the production work order, the nature of the operation, and the needs. At the same time, it can automatically revoke these permissions after the work order is completed, so as to improve the flexibility and security of the operation and reduce the risk of production line shutdown due to permission issues.
[0049] Optionally, the dynamic permission allocation in this embodiment may include: granting temporary permissions, such as temporarily granting the warehouse manager the following scheduling permissions: increasing the outbound quantity limit to 1000 pieces (the regular limit is 500 pieces), allowing operation of Warehouse A - Engine Zone (original permission was limited to Warehouse B), and binding the permission validity period to the work order deadline. In addition, dynamic permission allocation may also include permission changes, which take effect in real time through Event-Driven Architecture (EDA).
[0050] In this embodiment, a dynamic permission allocation process based on the production task status is proposed. This process constructs a dynamic role-task binding model, which links permissions with the production work order status in real time, and flexibly controls different permissions of roles.
[0051] Step S106: In response to the scheduling instruction from the warehouse management object, and after satisfying the scheduling permission information, schedule the items to be scheduled according to the scheduling instruction.
[0052] In the technical solution provided in step S106 of this application, when a scheduling instruction is received from a warehouse management object, it can be determined whether the scheduling instruction meets the scheduling permission information. If the scheduling instruction meets the scheduling permission information, the items to be scheduled can be scheduled according to the scheduling instruction. The aforementioned scheduling instruction is a specific operation command issued by the warehouse administrator, which follows the restrictions of the scheduling permission information and instructs the system or operators to perform specific scheduling operations. For example, the scheduling instruction may indicate which items should be taken out of the warehouse, taken into the warehouse, or moved within the warehouse.
[0053] Optionally, the warehouse management system will verify whether the scheduling instructions comply with the scheduling permission information, and then execute the corresponding scheduling operation.
[0054] For example, when warehouse manager A issues a dispatch instruction: "Immediately transfer 1,000 engine parts from warehouse A - engine area to the shipping area", the system verifies whether this instruction matches the warehouse manager's current dispatch permission information. Once the permissions are confirmed to be in compliance, the dispatch instruction is executed, and the required engine parts are transferred from the designated area.
[0055] Through steps S102 to S106 of this application, in response to obtaining a production work order, the production work order is parsed to obtain work order demand data. The production work order requests the scheduling of items stored in the storage area, and the work order demand data represents the items to be scheduled in the storage area, along with their scheduling information. Based on the work order demand data, the scheduling permission information of the warehouse management object in the storage area is determined. This scheduling permission information represents the permission allowed for the warehouse management object to schedule the items to be scheduled. In response to a scheduling instruction from the warehouse management object, the scheduling permission information is satisfied, and the items to be scheduled are scheduled according to the scheduling instruction. In other words, in this embodiment, after obtaining a production work order, the production work order is parsed to obtain work order demand data. Based on the work order demand data, the warehouse administrator's scheduling permission information is updated. When a scheduling instruction is obtained, the corresponding items to be scheduled can be scheduled according to the instruction. This method automatically adjusts the administrator's scheduling permission information without requiring manual adjustment of the warehouse management object's permissions, thereby improving data processing efficiency and solving the problem of low data processing efficiency.
[0056] The method described in this embodiment will be further described below.
[0057] As an optional implementation, step S102, in response to obtaining a production work order, parses the production work order to obtain work order demand data, including: in response to obtaining a production work order, determining the priority level of the production work order, wherein the priority level is used to characterize the urgency of the production work order; in response to the priority level being greater than the level threshold, parses the production work order to obtain work order demand data.
[0058] In this embodiment, if a production work order is obtained, its priority level can be determined. This priority level can be used to characterize the urgency of the production work order. For example, a higher priority level indicates a higher urgency, and a lower priority level indicates a lower urgency. To improve data processing efficiency, the production work order can be parsed only when its priority level is greater than a priority threshold to obtain the work order demand data. The aforementioned priority threshold can be a pre-set value, such as a high priority threshold. It should be noted that this is only an illustrative example, and no specific restrictions are placed on the type of priority threshold.
[0059] Optionally, this embodiment proposes a dynamic role authorization mechanism that dynamically binds roles and tasks. When a production work order (such as an emergency order) is marked as high priority, the operation permissions of the role (i.e., the warehouse manager) can be automatically expanded.
[0060] Optionally, it integrates with the Manufacturing Execution System (MES) system interface to monitor work order status change events in real time (e.g., using a RabbitMQ message queue). If a work order status change event occurs, it can be determined that a new production work order exists, and its priority level can be determined. If the priority level is greater than a threshold, the production work order can be parsed to obtain the work order requirement data. The dynamic permission model can be extended using a permission management framework such as Spring Security or Apache Shiro.
[0061] For example, regarding the dynamic adjustment of permissions for urgent orders, if an automotive parts warehouse receives an urgent order for 500 engine parts, requiring overnight inventory allocation, and the regular outbound process cannot meet the timeliness requirements, then the work order status triggers permission expansion. The management system listens for work order events and triggers a dynamic permission allocation process. The work order generated by the MES system is marked as "urgent" (priority: Critical). This production work order can include the following key information: material name, time, quantity, and other key information that describes the need for reassignment of permissions.
[0062] As an optional implementation, step S104, the scheduling permission information includes: outbound information, and the scheduling areas allowed for scheduling in the storage area. According to the work order demand data, the scheduling permission information of the warehouse management object in the storage area is determined, including: according to the work order demand data, determining the scheduling information, and the sub-storage area storing the items to be scheduled; based on the scheduling information, determining the outbound information, and obtaining the location information of the storage sub-storage area; based on the location information, determining the scheduling area.
[0063] In this embodiment, the aforementioned outbound information may include, but is not limited to, the outbound quantity, the name and category of the items to be dispatched, etc. The aforementioned sub-storage area may be a portion of the warehouse, such as a shelf or a specific location. The aforementioned location information can be used to determine the location of the sub-storage area, including its three-dimensional spatial location. It should be noted that this is merely an illustrative example, and no specific limitations are placed on the type of outbound information or the content of the location information.
[0064] Optionally, based on the work order demand data, scheduling information and the location information of the sub-storage area storing the items to be scheduled can be determined. Based on the scheduling information, the outbound information of the warehouse management object can be determined, that is, information such as the maximum number of items allowed to be scheduled by the warehouse management object can be used to determine. Furthermore, based on the location information, the area allowed to be scheduled by the warehouse management object can be determined. Therefore, based on the outbound information and location information, the updated scheduling permission information of the warehouse management object can be obtained.
[0065] Optionally, this embodiment also proposes location-level access control, which more finely divides and controls permissions based on location information within the warehouse (e.g., storage location) and outbound information (e.g., the type of stored parts), avoiding the potential for misoperation or unauthorized operation caused by overly broad permission scopes in traditional methods. All of these measures aim to improve the efficiency and security of the warehouse management system in actual operation.
[0066] As an optional implementation, the method may further include: acquiring a three-dimensional map of the storage area; and determining the initial scheduling permission information of the warehouse management object according to the three-dimensional map.
[0067] In this embodiment, to achieve granular control over storage locations, a 3D map of the storage area can be obtained. Based on this 3D map, the initial scheduling permission information of the warehouse manager can be determined. This initial scheduling permission information can be used to limit the initial management authority of the warehouse manager. The higher-level 3D map refers to a 3D visualization of the warehouse's internal layout and the location of stored items. It may include, but is not limited to, all shelves, aisles, areas, and specific storage information of items within the warehouse. This 3D map not only displays the warehouse's floor plan but also records detailed vertical dimension information such as the height of each shelf and the stacking height of each batch of goods. It should be noted that this is merely an example, and no specific limitations are placed on the content included in the 3D map.
[0068] Optionally, physical storage location permissions can be assigned based on the warehouse's three-dimensional coordinates or warehouse manager (Radio Frequency Identification, or RFID) tags.
[0069] Optionally, a 3D map can be used to precisely define the scope of warehouse administrator permissions. Administrator permissions are no longer limited to the entire warehouse, but are refined to specific shelves or even storage locations. This permission setting greatly improves the precision and security of warehouse management, preventing unauthorized access and operations.
[0070] For example, suppose a 3D map of a warehouse includes: warehouse structure division, the warehouse is divided into three areas: electronic components, mechanical parts, and chemical products. Each area is further subdivided into multiple shelves, such as shelves numbered E101 to E200 in the electronic components area, M001 to M100 in the mechanical parts area, and C001 to C050 in the chemical products area; shelf hierarchy information, each shelf is divided into three levels, representing high, middle, and low levels, used for storing different types of items. For example, shelf E101 in the electronic components area may have precision electronic chips on the high level, cables and connectors on the middle level, and packaging materials on the low level; item location and identification, each item has its exact location in 3D space. For example, a microprocessor with a specific serial number (such as SN: E12345) is placed in the 5th row and 3rd column of the middle level of shelf E123 in the electronic components area.
[0071] Furthermore, based on the aforementioned 3D map, the initial scheduling permissions of warehouse managers can be set as follows: Manager 1 is only authorized to operate shelves E101 to E150 in the electronic components area, and is limited to items on the middle and lower levels; Manager 2 is authorized to operate the upper levels of all shelves in the mechanical parts area for handling the inbound and outbound of large mechanical equipment.
[0072] Optionally, the initial scheduling permission information of the warehouse management object can be determined in advance based on the three-dimensional map of the storage area. When a relatively urgent production work order is obtained, the scheduling permission information of the warehouse management object can be re-determined, and the management permission of the warehouse management object can be adjusted according to the scheduling permission information.
[0073] As an optional implementation, the method may further include: determining the material code of an item stored in the storage area, wherein the material code is used to determine the category of the item; and adjusting the initial scheduling permission information according to the material code.
[0074] In this embodiment, after determining the initial scheduling permission information, the initial scheduling permission information can be adjusted based on the material code of the items stored in the storage area to improve the accuracy of the initial scheduling permission information. The initial scheduling permission information may include, but is not limited to, data such as the schedulable area, schedulable items, and schedulable quantity of the warehouse management object.
[0075] To avoid the emergence of "shared accounts" or "universal accounts," more detailed permission management is required. In this embodiment, based on a 3D warehouse map, permission zones are defined (e.g., a warehouse manager can only operate the shelves between shelf A and shelf B) to achieve location-level control. Based on Enterprise Resource Planning (ERP) material classifications (e.g., motor parts with material codes starting with "MOT-"), the scope of operating employees is restricted to prevent unauthorized operations or misoperations by employees outside the designated area, thus completing the binding of component categories.
[0076] Optionally, the MES and ERP systems can interact in real time via interfaces such as Application Programming Interfaces (APIs). Alternatively, message queue middleware (such as Kafka or RabbitMQ) can be used to implement publish-subscribe for work order status change events.
[0077] As an optional implementation, the method may further include: in response to the completion of the scheduling of the items to be scheduled, adjusting the scheduling permission information to the initial scheduling permission information and generating a scheduling log, wherein the scheduling log is used to record the retrieval status of the items to be scheduled.
[0078] In this embodiment, if the dispatched items are dispatched and the permissions are automatically invalidated, the dispatch permission information can be adjusted to the initial dispatch permission information, and a dispatch log can be generated. This dispatch log can be an audit log, which can be used to record the retrieval status of the items to be dispatched. It can include the dispatched items, the warehouse management object that dispatched the items to be dispatched, the dispatch quantity of the items to be dispatched, the location information of the items to be dispatched, etc.
[0079] Optionally, when an employee generates an urgent work order (such as an order with a priority of "High"), the work order requirements (such as component type, quantity, and delivery time) can be automatically parsed, and a log can be generated. Warehouse staff can be temporarily granted excessive outbound permissions (e.g., the normal single outbound limit is 50 pieces, increased to 500 pieces in emergency mode), and the scope of the permission can be restricted (e.g., only allowing operation on designated shelves in the "SPS area"). Simultaneously, an automatic retrieval mechanism is built; after a production work order is completed, the permission automatically expires and an audit log is generated.
[0080] As an optional implementation, the method may further include: splitting the scheduling log to obtain at least one sub-scheduling log; encrypting the at least one sub-scheduling log to obtain at least one encrypted log; and transmitting the encrypted log to multiple edge nodes for storage.
[0081] In this embodiment, a distributed log sharding storage is proposed. After obtaining the scheduling log, the scheduling log can be split to obtain at least one sub-scheduling log. The at least one sub-scheduling log can be encrypted to obtain at least one encrypted log. The at least one encrypted log can be transmitted to multiple edge nodes for storage.
[0082] Optionally, after the operation log (such as outbound records) is generated, it can be fragmented by time window (such as 10 minutes) to obtain at least one sub-scheduling log. A hash value can be generated using an encryption algorithm (such as SHA-3), and after fragmentation and encryption measures, at least one encrypted log can be obtained. This encrypted log can be stored on three different edge nodes (such as local servers, the cloud, and audit centers). Alternatively, all encrypted logs corresponding to the scheduling log can be stored on multiple edge nodes, or at least one encrypted log can be stored on at least one edge node, or different numbers of encrypted logs can be stored on different edge nodes.
[0083] This embodiment proposes a blockchain sharded storage and edge node consensus verification mechanism. This mechanism stores operation records in shards, and after the outbound operation is completed, the system stores the log shards encrypted. The edge node consensus mechanism requires multi-node verification for critical operations to prevent single points of failure. A multi-rule composite detection engine provides multi-dimensional risk control based on time, quantity, and behavior.
[0084] Alternatively, a node selection strategy can be used to determine the storage area corresponding to the encrypted logs. There are no specific restrictions on the method for determining the storage area of the encrypted logs.
[0085] Figure 2 This is a schematic diagram of a distributed storage system according to an embodiment of this application, such as... Figure 2 As shown, in the client 204 operation, the sharding engine 205 shards the log to obtain sharded logs. Using a node selection strategy and a consistent hashing algorithm, the sharded logs are encrypted to generate encrypted sharded data, which is then stored in edge nodes 201, 202, and 203. Edge node 201 can be a local edge node, edge node 202 can be an edge node in the cloud, and edge node 203 can be an edge node in the audit center.
[0086] Optionally, after the operation log (such as outbound records) is generated, it is sharded according to a time window (such as 10 minutes). Hash values are generated using the SHA-3 algorithm, sharded, and encrypted before being stored on three different edge nodes (such as local servers, cloud storage, audit centers, etc.).
[0087] As an optional implementation, the method may further include: in response to receiving a deletion command to delete encrypted logs, determining the triggering object that triggered the deletion command; determining whether the triggering object has deletion permission to delete encrypted logs; and in response to the triggering object not having deletion permission, outputting a prompt message.
[0088] In this embodiment, tampering operation interception and tracing are also provided. When a deletion command to delete encrypted logs is collected, the triggering object that triggered the deletion command can be identified. It can be determined whether the triggering object has the deletion permission to delete encrypted logs. If the triggering object does not have the deletion permission, it means that the deletion operation here is illegal, and a prompt message can be output.
[0089] For example, in a real-time anomaly interception system with a pre-built multi-dimensional rule base, an employee (non-auditor role) attempts to delete outbound records of expired parts to cover up a management error. At this point, the illegal operation triggers the rule engine, detecting that User 1 (role: ordinary warehouse manager) initiated the deletion operation. The rule engine detects the following violations: role violation (non-auditors are prohibited from deleting logs); abnormal behavior (abnormal frequency of deletion operations). In this situation, real-time interception and alerts can be issued, the system locks the operation interface, and pushes an alert to the auditor.
[0090] In this embodiment, centralized auditing plus two-factor authentication can improve security, but cannot solve the single point of tampering problem. At the same time, it improves dynamic permission management capabilities and real-time risk control capabilities, thereby improving the system's flexibility, efficiency, and security.
[0091] Figure 3 This is a flowchart of another item scheduling process timeline according to an embodiment of this application, such as... Figure 3 As shown, the method may include the following steps:
[0092] Step S302: Trigger work order creation.
[0093] In this embodiment, producer / role 32 triggers work order creation to obtain a production work order.
[0094] Step S304: Work order status changes; adjust operation queue.
[0095] In this embodiment, the work order change information is combined into a queue message queue and pushed to the authorization engine through the MES system 34 (the latency is expected to be less than 100ms to ensure system smoothness) in order to adjust the operation queue.
[0096] Step S306: Work order parsing, permission allocation rule base.
[0097] In this embodiment, the dynamic authorization module 36 parses the work order and establishes a permission division rule base to generate temporary permissions. These dynamic permissions can then be bound to user roles (with an effective timestamp attached).
[0098] Step S308: Obtain the operation request.
[0099] In this embodiment, step S310 can be executed in response to receiving an operation request from producer / role 32.
[0100] Step S310: Determine if permissions are satisfied.
[0101] In this embodiment, in response to a scheduling instruction (i.e., an operation request) from a warehouse management object, it is determined whether the scheduling instruction meets the scheduling permission information. If it does, step S312 is executed; otherwise, step S308 is re-executed.
[0102] Step S312: Dispatch the items to be dispatched according to the dispatch instructions.
[0103] In this embodiment, the items to be scheduled are scheduled according to the scheduling instructions and displayed in the operation interface, and the above process content is used to generate an audit log (including the validity period of permissions).
[0104] For example, suppose a car manufacturer's parts warehouse receives an urgent order requiring the allocation of a large quantity of car engine parts within a very short time. Normally, employee (warehouse clerk) 1's permissions are limited to the general parts area of warehouse B. However, since this urgent order involves engine parts from warehouse A and requires the rapid release of a large quantity of goods, this exceeds employee 1's normal permissions. The production department creates an urgent order (i.e., a production work order) in the ERP system, marks it as "high priority," and enters the required engine part models, quantities, and estimated delivery times. The ERP system automatically transmits this urgent order information to the Manufacturing Execution System (MES) for further coordination of production resources and logistics. The MES system recognizes the high priority attribute of this work order and requests the dynamic access control system to extend employee 1's permissions to meet the needs of the urgent order.
[0105] Furthermore, upon receiving the request from the MES system, the authorization engine begins parsing the specific requirements of the urgent order (such as the type of engine parts, the required quantity, and the warehouse location). Based on the parsing results, a set of temporary permissions is generated for employee one, which may include: privileged access to the engine parts area in warehouse A, a temporary increase in the outbound quantity limit to 1000 pieces (the normal limit is 500 pieces), and the validity period of the permissions being tied to the estimated delivery time of the urgent order.
[0106] Optionally, Employee One's permission information is immediately updated in the system. Simultaneously, an event-driven architecture (such as RabbitMQ message queue) ensures that permission adjustment information is rapidly propagated to all relevant systems. Next, Employee One logs into the warehouse management system. The system checks Employee One's permissions to confirm if they meet the requirements for executing the urgent order. Once confirmed, Employee One can quickly complete the outbound shipment of a large volume of engine parts within the specified time. After completion, the system records all outbound details, including operation time, operator, and operation type. These logs are then sharded and stored across multiple edge nodes (local server, cloud, audit center, etc.) according to time windows. The logs are also encrypted and hashed to ensure data security and integrity. When the delivery time for the urgent order has passed, or the work order status changes to "processed," the system automatically revokes Employee One's temporary permissions and adds a permission revocation record to the operation log, forming a complete audit trail.
[0107] In this embodiment, after obtaining the production work order, the production work order is parsed to obtain the work order demand data. According to the work order demand data, the warehouse administrator's scheduling permission information is updated. When the scheduling instruction is obtained, the corresponding items to be scheduled can be scheduled according to the scheduling instruction. This method can automatically adjust the administrator's scheduling permission information without the need for manual adjustment of the permissions of the warehouse management objects, thereby achieving the technical effect of improving data processing efficiency and solving the technical problem of low data processing efficiency.
[0108] According to an embodiment of this application, a scheduling device for items is also provided. It should be noted that the item scheduling device of this embodiment can be used to execute the item scheduling method of the above embodiments of this application.
[0109] Figure 4 This is a schematic diagram of an item scheduling device according to an embodiment of this application. Figure 4 As shown, the scheduling device 40 for the item may include: a parsing unit 402, a determining unit 404, and a scheduling unit 406.
[0110] The parsing unit 402 is used to parse the production work order in response to obtaining the production work order to obtain the work order demand data. The production work order is used to request the scheduling of items stored in the storage area, and the work order demand data is used to represent the items to be scheduled in the storage area and the scheduling information of the items to be scheduled.
[0111] The determining unit 404 is used to determine the scheduling permission information of the warehouse management object in the storage area according to the work order requirement data. The scheduling permission information is used to indicate the permission of the warehouse management object to schedule the items to be scheduled.
[0112] The scheduling unit 406 is used to respond to scheduling instructions from the warehouse management object, satisfy the scheduling permission information, and schedule the items to be scheduled according to the scheduling instructions.
[0113] The item scheduling device of this embodiment, through a parsing unit, responds to the acquisition of a production work order by parsing the production work order to obtain work order demand data. The production work order requests the scheduling of items stored in the storage area, and the work order demand data represents the items to be scheduled in the storage area, along with their scheduling information. Through a determining unit, the scheduling permission information of the warehouse management object in the storage area is determined according to the work order demand data. The scheduling permission information represents the permission allowed for the warehouse management object to schedule the items to be scheduled. Through a scheduling unit, responding to a scheduling instruction from the warehouse management object, the scheduling permission information is satisfied, and the items to be scheduled are scheduled according to the scheduling instruction. This solves the technical problem of low data processing efficiency and achieves the technical effect of improving data processing efficiency.
[0114] Embodiments of this application may provide a computer terminal, which may be any computer terminal device in a group of computer terminals. Optionally, in this embodiment, the aforementioned computer terminal may also be replaced by a mobile terminal or other terminal device.
[0115] Optionally, in this embodiment, the computer terminal may be located in at least one of a plurality of network devices in a computer network.
[0116] In this embodiment, the computer terminal described above can execute the program code for the following steps in the item scheduling method: In response to obtaining a production work order, the production work order is parsed to obtain work order demand data, wherein the production work order is used to request the scheduling of items stored in the storage area, and the work order demand data is used to represent the items to be scheduled in the storage area, as well as the scheduling information of the items to be scheduled; according to the work order demand data, the scheduling permission information of the warehouse management object in the storage area is determined, wherein the scheduling permission information is used to represent the permission of the warehouse management object to schedule the items to be scheduled; in response to the scheduling instruction from the warehouse management object, the scheduling permission information is satisfied, and the items to be scheduled are scheduled according to the scheduling instruction.
[0117] Optionally, Figure 5 This is a structural block diagram of a computer terminal according to an embodiment of this application, such as... Figure 5 As shown, the computer terminal 508 may include one or more (only one is shown in the figure) processors 502, memory 504, and transmission devices 506.
[0118] The memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the item scheduling method and apparatus in this application embodiment. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, thereby realizing the aforementioned item scheduling method. The memory may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to computer terminal 508 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
[0119] The processor can invoke information and application programs stored in the memory via a transmission device to perform the following steps: In response to obtaining a production work order, the processor parses the production work order to obtain work order demand data, wherein the production work order is used to request the scheduling of items stored in the storage area, and the work order demand data is used to indicate the items to be scheduled in the storage area, as well as the scheduling information of the items to be scheduled; according to the work order demand data, the processor determines the scheduling permission information of the warehouse management object in the storage area, wherein the scheduling permission information is used to indicate the permission of the warehouse management object to schedule the items to be scheduled; in response to the scheduling instruction from the warehouse management object, the processor satisfies the scheduling permission information and schedules the items to be scheduled according to the scheduling instruction.
[0120] Those skilled in the art will understand that Figure 5 The structure shown is for illustrative purposes only. The computer terminal 508 can also be a smartphone (such as an Android phone, an iOS phone, etc.), a tablet computer, a handheld computer, a mobile internet device (MID), a PAD, or other terminal device. Figure 5 This does not limit the structure of the computer terminal 508 described above. For example, the computer terminal 508 may also include components that are more advanced than those described above. Figure 5 The more or fewer components shown (such as network interfaces, display devices, etc.), or having the same Figure 5 The different configurations shown.
[0121] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.
[0122] According to an embodiment of this application, a computer-readable storage medium is also provided, the computer-readable storage medium including a stored program, wherein the program executes the item scheduling method in the above embodiments.
[0123] Optionally, in this embodiment, the computer-readable storage medium may be located in any computer terminal in a group of computer terminals in a computer network, or in any mobile terminal in a group of mobile terminals.
[0124] Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for performing the following steps: in response to obtaining a production work order, parsing the production work order to obtain work order demand data, wherein the production work order is used to request the scheduling of items stored in the storage area, and the work order demand data is used to represent the items to be scheduled in the storage area, and the scheduling information of the items to be scheduled; according to the work order demand data, determining the scheduling permission information of the warehouse management object in the storage area, wherein the scheduling permission information is used to represent the permission of the warehouse management object to schedule the items to be scheduled; in response to the scheduling instruction from the warehouse management object, satisfying the scheduling permission information, scheduling the items to be scheduled according to the scheduling instruction.
[0125] Optionally, the aforementioned computer-readable storage medium may also execute program code that performs the following steps: in response to obtaining a production work order, determining the priority level of the production work order, wherein the priority level is used to characterize the urgency of the production work order; in response to the priority level being greater than a level threshold, parsing the production work order to obtain work order demand data.
[0126] Optionally, the aforementioned computer-readable storage medium may also execute program code that performs the following steps: determining scheduling information and a sub-storage area for storing items to be scheduled based on work order demand data; determining outbound information based on the scheduling information and obtaining location information of the storage sub-storage area; and determining the scheduling area based on the location information.
[0127] Optionally, the aforementioned computer-readable storage medium may also execute program code that performs the following steps: obtaining a three-dimensional map of the storage area; and determining the initial scheduling permission information of the warehouse management object according to the three-dimensional map.
[0128] Optionally, the aforementioned computer-readable storage medium may also execute program code that performs the following steps: determining the material code of an item stored in the storage area, wherein the material code is used to determine the category of the item; and adjusting the initial scheduling permission information according to the material code.
[0129] Optionally, the computer-readable storage medium may also execute program code that performs the following steps: in response to the completion of the scheduling of the items to be scheduled, the scheduling permission information is adjusted to the initial scheduling permission information, and a scheduling log is generated, wherein the scheduling log is used to record the retrieval status of the items to be scheduled.
[0130] Optionally, the aforementioned computer-readable storage medium may also execute program code that performs the following steps: splitting the scheduling log to obtain at least one sub-scheduling log; encrypting the at least one sub-scheduling log to obtain at least one encrypted log; and transmitting the encrypted log to multiple edge nodes for storage.
[0131] Optionally, the aforementioned computer-readable storage medium may also execute program code that performs the following steps: in response to receiving a deletion instruction to delete encrypted logs, determining the triggering object that triggered the deletion instruction; determining whether the triggering object has deletion permission to delete encrypted logs; and in response to the triggering object not having deletion permission, outputting a prompt message.
[0132] In this embodiment, after obtaining the production work order, the production work order is parsed to obtain the work order demand data. According to the work order demand data, the warehouse administrator's scheduling permission information is updated. When the scheduling instruction is obtained, the corresponding items to be scheduled can be scheduled according to the scheduling instruction. This method can automatically adjust the administrator's scheduling permission information without the need for manual adjustment of the permissions of the warehouse management objects, thereby achieving the technical effect of improving data processing efficiency and solving the technical problem of low data processing efficiency.
[0133] According to an embodiment of this application, a processor is also provided for running a program, wherein the item scheduling method in the above embodiments is executed when the program is run by the processor.
[0134] Optionally, in this embodiment, the computer terminal may be located in at least one of a plurality of network devices in a computer network.
[0135] In this embodiment, the computer terminal described above can execute the program code for the following steps in the item scheduling method: In response to obtaining a production work order, the production work order is parsed to obtain work order demand data, wherein the production work order is used to request the scheduling of items stored in the storage area, and the work order demand data is used to represent the items to be scheduled in the storage area, as well as the scheduling information of the items to be scheduled; according to the work order demand data, the scheduling permission information of the warehouse management object in the storage area is determined, wherein the scheduling permission information is used to represent the permission of the warehouse management object to schedule the items to be scheduled; in response to the scheduling instruction from the warehouse management object, the scheduling permission information is satisfied, and the items to be scheduled are scheduled according to the scheduling instruction.
[0136] The memory can be used to store software programs and modules, such as the program instructions / modules corresponding to the item scheduling method and apparatus in this application embodiment. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory, thereby realizing the aforementioned item scheduling method. The memory may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory may further include memory remotely located relative to the processor, and these remote memories can be connected to a computer terminal via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.
[0137] The processor can invoke information and application programs stored in the memory via a transmission device to perform the following steps: In response to obtaining a production work order, the processor parses the production work order to obtain work order demand data, wherein the production work order is used to request the scheduling of items stored in the storage area, and the work order demand data is used to indicate the items to be scheduled in the storage area, as well as the scheduling information of the items to be scheduled; according to the work order demand data, the processor determines the scheduling permission information of the warehouse management object in the storage area, wherein the scheduling permission information is used to indicate the permission of the warehouse management object to schedule the items to be scheduled; in response to the scheduling instruction from the warehouse management object, the processor satisfies the scheduling permission information and schedules the items to be scheduled according to the scheduling instruction.
[0138] Optionally, the processor may also execute program code that performs the following steps: in response to obtaining a production work order, determining the priority level of the production work order, wherein the priority level is used to characterize the urgency of the production work order; in response to the priority level being greater than a level threshold, parsing the production work order to obtain work order demand data.
[0139] Optionally, the processor may also execute program code that performs the following steps: in response to obtaining a production work order, determining the priority level of the production work order, wherein the priority level is used to characterize the urgency of the production work order; in response to the priority level being greater than a level threshold, parsing the production work order to obtain work order demand data.
[0140] Optionally, the processor may also execute program code that performs the following steps: determining scheduling information and a sub-storage area for storing items to be scheduled based on work order demand data; determining outbound information based on scheduling information and obtaining location information of the sub-storage area; and determining the scheduling area based on location information.
[0141] Optionally, the processor may also execute program code that performs the following steps: obtains a three-dimensional map of the storage area; and determines the initial scheduling permission information of the warehouse management object according to the three-dimensional map.
[0142] Optionally, the processor may also execute program code that performs the following steps: determining the material code of the items stored in the storage area, wherein the material code is used to determine the category of the items; and adjusting the initial scheduling permission information according to the material code.
[0143] Optionally, the processor may also execute program code that performs the following steps: in response to the completion of the scheduling of the items to be scheduled, adjust the scheduling permission information to the initial scheduling permission information and generate a scheduling log, wherein the scheduling log is used to record the retrieval status of the items to be scheduled.
[0144] In this embodiment of the application, after obtaining a production work order, the production work order is parsed to obtain work order demand data. According to the work order demand data, the scheduling permission information of the warehouse administrator is updated. When a scheduling instruction is obtained, the corresponding items to be scheduled can be scheduled according to the scheduling instruction. This method can automatically adjust the administrator's scheduling permission information without the need for manual adjustment of the permissions of the warehouse management objects, thereby achieving the technical effect of improving data processing efficiency and solving the technical problem of low data processing efficiency.
[0145] According to an embodiment of this application, a computer program product is also provided, which includes computer instructions, wherein when the computer instructions are executed by a processor, they implement the item scheduling method in the above embodiments.
[0146] Embodiments of this application may provide an electronic device that may include a memory and a processor.
[0147] Figure 6 This is a block diagram of an electronic device for a method of scheduling articles according to an embodiment of this application. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the present application described and / or claimed herein.
[0148] like Figure 6As shown, device 600 includes a computing unit 601, which can perform various appropriate actions and processes based on a computer program stored in read-only memory (ROM) 602 or a computer program loaded from storage unit 608 into random access memory (RAM) 603. RAM 603 can also store various programs and data required for the operation of device 600. The computing unit 601, ROM 602, and RAM 603 are interconnected via bus 604. Input / output (I / O) interface 605 is also connected to bus 604.
[0149] Multiple components in device 600 are connected to I / O interface 605, including: input unit 606, such as keyboard, mouse, etc.; output unit 604, such as various types of displays, speakers, etc.; storage unit 608, such as disk, optical disk, etc.; and communication unit 609, such as network card, modem, wireless transceiver, etc. Communication unit 609 allows device 600 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.
[0150] The computing unit 601 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of the computing unit 601 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 601 performs the various methods and processes described above, such as data verification methods. For example, in some embodiments, the data verification method may be implemented as a computer software program tangibly contained in a machine-readable medium, such as storage unit 608. In some embodiments, part or all of the computer program may be loaded and / or installed on device 600 via ROM 602 and / or communication unit 609. When the computer program is loaded into RAM 603 and executed by the computing unit 601, one or more steps of the data verification method described above may be performed. Alternatively, in other embodiments, the computing unit 601 may be configured to perform a data verification method by any other suitable means (e.g., by means of firmware).
[0151] According to an embodiment of this application, a method for scheduling items is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.
[0152] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems on a chip (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.
[0153] The program code used to implement the methods of this application may be written in any combination of one or more programming languages. This program code may be provided to a processor or controller of a general-purpose computer, special-purpose computer, or other programmable data processing device, such that when executed by the processor or controller, the functions / operations specified in the flowcharts and / or block diagrams are implemented. The program code may be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.
[0154] In the context of this application, a machine-readable medium can be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. Machine-readable media can be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.
[0155] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display, monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or pathball) through which the user provides input to the computer. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).
[0156] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with a graphical user interface or web browser through which a user can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication (e.g., communication networks) of any form or medium. Examples of communication networks include local area networks (LANs), wide area networks (WANs), and the Internet.
[0157] Computer systems can include clients and servers. Clients and servers are generally located far apart and typically interact via communication networks. Client-server relationships are created by computer programs running on the respective computers and having a client-server relationship with each other. Servers can be cloud servers, servers in distributed systems, or servers incorporating blockchain technology.
[0158] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.
[0159] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0160] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.
[0161] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0162] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0163] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.
[0164] The above are merely preferred embodiments of this application. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of this application, and these improvements and modifications should also be considered within the scope of protection of this application.
Claims
1. A method for scheduling items, characterized in that, include: In response to obtaining a production work order, the production work order is parsed to obtain work order demand data. The production work order is used to request the scheduling of items stored in the storage area, and the work order demand data is used to represent the items to be scheduled in the storage area, as well as the scheduling information of the items to be scheduled. Based on the work order demand data, determine the scheduling permission information of the warehouse management object in the storage area, wherein the scheduling permission information is used to indicate the permission of the warehouse management object to schedule the items to be scheduled; In response to the scheduling instruction from the warehouse management object and satisfying the scheduling permission information, the items to be scheduled are scheduled according to the scheduling instruction.
2. The method according to claim 1, characterized in that, In response to receiving a production work order, the production work order is parsed to obtain work order demand data, including: In response to obtaining the production work order, the priority level of the production work order is determined, wherein the priority level is used to characterize the urgency of the production work order; In response to the priority level being greater than the priority threshold, the production work order is parsed to obtain the work order demand data.
3. The method according to claim 1, characterized in that, The scheduling permission information includes: outbound information, and the scheduling areas allowed for scheduling within the storage area. Determining the scheduling permission information of the warehouse management object in the storage area based on the work order demand data includes: Based on the work order demand data, determine the scheduling information and the sub-storage area for storing the items to be scheduled; Based on the scheduling information, the outbound information is determined, and the location information of the sub-storage area is obtained; Based on the location information, the scheduling area is determined.
4. The method according to claim 1, characterized in that, The method further includes: Obtain a 3D map of the storage area; Based on the aforementioned 3D map, determine the initial scheduling permission information for the warehouse management object.
5. The method according to claim 4, characterized in that, The method further includes: Determine the material code of the item stored in the storage area, wherein the material code is used to determine the category of the item; Adjust the initial scheduling permission information according to the material code.
6. The method according to claim 4, characterized in that, The method further includes: In response to the completion of the scheduling of the item to be scheduled, the scheduling permission information is adjusted to the initial scheduling permission information, and a scheduling log is generated, wherein the scheduling log is used to record the retrieval status of the item to be scheduled.
7. The method according to claim 6, characterized in that, The method further includes: The scheduling log is split to obtain at least one sub-scheduling log; Encrypt at least one of the sub-scheduling logs to obtain at least one encrypted log; The encrypted logs are transmitted to multiple edge nodes for storage.
8. The method according to claim 7, characterized in that, The method further includes: In response to the receipt of a deletion command to delete the encrypted log, the triggering object that triggered the deletion command is determined; Determine whether the triggering object has the permission to delete the encrypted log; If the triggering object does not have the deletion permission, a prompt message is output.
9. A processor, characterized in that, The processor is used to run a program, wherein the program is executed by the processor to perform the method according to any one of claims 1 to 8.
10. A computer program product, characterized in that, Includes computer instructions that, when executed by a processor, implement the method described in any one of claims 1 to 8.