A method and system for multi-layer container association and multi-lock coordination whole rack call execution

Abstract

The application provides a multi-layer container association and multi-lock cooperative whole rack call execution method and system. The method obtains a call request and determines a matched inventory layout association record, thereby determining a leaf container, a top layer container, a source storage location, a production line task and a target storage location; checks the reference integrity and type matching between the inventory layout association record, the leaf container, the top layer container and the source storage location, and between the call request, the production line task and the target storage location, to obtain a checkable positioning chain; thereby determining a joint update object set of the source storage location, the target storage location and the inventory layout association record and sequentially applying for a business lock. When the business lock is successfully occupied, a carrying instruction sheet is created in a critical section and a migration state is linked and migrated by taking the carrying instruction sheet as a voucher; when a business lock occupation failure, a carrying instruction sheet creation exception or a joint state migration exception occurs, the business lock is released in reverse order and the migrated state is restored, thereby improving the consistency of concurrent states and the failure recovery capability.

Description

Technical Field

[0001] This application relates to the field of intelligent warehouse execution control technology, and more specifically, to a method and system for executing whole-rack material calling based on multi-layer container association and multi-lock collaboration. Background Technology

[0002] In a smart warehouse's whole-rack material requisition scenario, after the production line issues a material requisition, it is necessary to determine the leaf container where the material is located, the top-level container to which the leaf container belongs, the source storage location of the top-level container, and the target storage location corresponding to the production line's material drop point. Then, the top-level container, along with the leaf container it carries and the material, is transported from the turnover area to the production line's material drop point as a handling unit. This process involves multi-level object location and the status updates of multiple objects.

[0003] In existing solutions, the process typically involves first querying the leaf container where the material is located, then querying the top-level container attached to the leaf container, the storage location of the top-level container, and the production line drop point. These relationships are scattered across leaf container records, top-level container records, storage location records, and task records, and are reassembled during runtime using temporary association queries. Existing solutions also employ single-lock or coarse-grained locks to handle object updates during concurrent material calls.

[0004] In the existing solutions described above, incomplete data is easily obtained when references are missing, and it is difficult to determine the set of objects that need to be jointly updated at once. Furthermore, a single lock cannot cover joint updates of multiple objects, which may result in multiple competing transport instructions corresponding to the same top-level container. In addition, when the process fails midway, the already occupied business locks and the migrated states lack a unified reverse rollback, which may cause the storage location to be continuously locked and the production line task status to be inconsistent with the actual transport status.

[0005] Therefore, this application provides a method and system for executing whole-frame material calling based on multi-layer container association and multi-lock collaboration, in order to solve one of the above-mentioned technical problems. Summary of the Invention

[0006] The purpose of this application is to provide a method and system for executing whole-frame material calls based on multi-layer container association and multi-lock coordination, which can solve at least one of the aforementioned technical problems. The specific solution is as follows: According to a specific embodiment of this application, in a first aspect, this application provides a method for executing whole-frame material call based on multi-layer container association and multi-lock collaboration, including: Obtain a material requisition request, determine the inventory layout association record matching the material requisition request, and determine the leaf container, top-level container, source storage location, production line task, and target storage location based on the inventory layout association record and the material requisition request; verify the reference integrity and type matching between the inventory layout association record, the leaf container, the top-level container, and the source storage location, as well as between the material requisition request, the production line task, and the target storage location, to obtain a verifiable location chain; based on the verifiable location chain, determine a joint update object set consisting of the source storage location, the target storage location, and the inventory layout association record, and sequentially request the source storage location, the leaf container, the target storage location, and the target storage location based on the joint update object set. The business locks for the target storage location and the associated inventory layout record are defined. In response to successful acquisition of all business locks, a transport instruction order is created within the business lock critical section to move the top-level container from the source storage location to the target storage location. Within the business lock critical section, the transport instruction order serves as the joint state migration credential, and the states of the production line task, the source storage location, the target storage location, and the associated inventory layout record are migrated in tandem. In response to business lock acquisition failure, transport instruction order creation anomaly, or joint state migration anomaly, the business locks occupied by the material call request are released in reverse order, and the migrated states of the production line task, the source storage location, the target storage location, and the associated inventory layout record are restored in reverse order.

[0007] According to a specific embodiment of this application, in a second aspect, this application provides a multi-layer container association and multi-lock coordination whole-frame material calling execution system, comprising: The associated positioning module is used to acquire a material requisition request, determine the inventory layout association record matching the material requisition request, and determine the leaf container, top-level container, source storage location, production line task, and target storage location based on the inventory layout association record and the material requisition request; verify the reference integrity and type matching between the inventory layout association record, the leaf container, the top-level container, and the source storage location, as well as between the material requisition request, the production line task, and the target storage location, to obtain a verifiable positioning chain; and determine a joint update object set composed of the source storage location, the target storage location, and the inventory layout association record based on the verifiable positioning chain. The concurrent execution module is used to sequentially apply for business locks on the source storage location, the target storage location, and the inventory layout association record according to the joint update object set; in response to the successful acquisition of all business locks, a transport instruction order is created within the business lock critical section to move the top-level container from the source storage location to the target storage location; within the business lock critical section, the transport instruction order is used as the joint state migration credential to link and migrate the states of the production line task, the source storage location, the target storage location, and the inventory layout association record; the compensation and recovery module is used to release the business locks occupied by the material call request in reverse order in response to the failure of business lock acquisition, abnormal creation of transport instruction order, or abnormal joint state migration, and to restore the migrated states of the production line task, the source storage location, the target storage location, and the inventory layout association record in reverse order.

[0008] Compared with the prior art, the above-described solutions of this application have at least the following beneficial effects: This application provides a method for executing whole-rack material requisition with multi-layer container association and multi-lock collaboration. It locates leaf containers, top-level containers, source storage locations, production line tasks, and target storage locations through inventory layout association records and material requisition requests, and verifies the integrity and type matching of the two sets of references to obtain a verifiable location chain, thereby identifying the joint update object. Furthermore, by applying for business locks in the order of source storage location, target storage location, and inventory layout association records, the risk of circular waiting and contention for coverage in concurrent material requisitions can be reduced. In addition, after all business locks are successfully acquired, a transport instruction order is created in the business lock critical section to move the top-level container from the source storage location to the target storage location. Using the transport instruction order as evidence, the state of the production line task and the joint update object is migrated in conjunction. In case of failure or anomaly, the business locks are released in reverse order and the migrated state is restored, thereby improving concurrent state consistency and failure recovery capabilities. Attached Figure Description

[0009] Figure 1 A flowchart of the whole-frame material call execution method provided in the embodiments of this application; Figure 2 A schematic diagram of a multi-layer container association and verifiable location chain relationship provided in an embodiment of this application; Figure 3 A flowchart illustrating the sequential application and failed release of three service locks provided in this application embodiment; Figure 4 A flowchart of failure compensation and recovery and failure recording provided for embodiments of this application; Figure 5 This application provides a timing diagram of the entire execution chain for concurrent whole-frame material calling in its embodiments. Figure 6A block diagram of a multi-layer container association and multi-lock coordination whole-frame material calling execution system provided in this application embodiment; Figure 7 A flowchart of state machine button gating provided for an embodiment of this application. Detailed Implementation

[0010] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail 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 in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0011] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. The singular forms “a,” “said,” and “the” used in the embodiments of this application and the appended claims are also intended to include the plural forms, and “multiple” generally includes at least two unless the context clearly indicates otherwise.

[0012] It should be understood that the term "and / or" used in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this article generally indicates that the preceding and following related objects have an "or" relationship.

[0013] It should be understood that although the terms first, second, third, etc., may be used in the embodiments of this application, these descriptions should not be limited to these terms. These terms are only used to distinguish the descriptions. For example, first may also be referred to as second without departing from the scope of the embodiments of this application, and similarly, second may also be referred to as first.

[0014] Depending on the context, the words “if” or “suppose” as used here can be interpreted as “when” or “in response to determination” or “in response to detection.” Similarly, depending on the context, the phrases “if determination” or “if detection (of the stated condition or event)” can be interpreted as “when determination” or “in response to determination” or “when detection (of the stated condition or event)” or “in response to detection (of the stated condition or event).”

[0015] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a product or system comprising a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a product or system. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the product or system that includes said element.

[0016] It should be noted that any symbols and / or numbers present in the specification that are not marked in the accompanying drawings are not reference numerals.

[0017] The optional embodiments of this application are described in detail below with reference to the accompanying drawings.

[0018] The embodiments provided in this application are embodiments of a whole-frame material call execution method with multi-layer container association and multi-lock collaboration.

[0019] In this embodiment of the application, "whole rack material call" means that the top container, together with the leaf container and materials carried by the top container, is used as a handling unit and transported from the source warehouse to the target warehouse corresponding to the production line task.

[0020] The following is combined Figure 1 The embodiments of this application will be described in detail.

[0021] Figure 1 This is a flowchart illustrating a method for executing a whole-frame material call based on multi-layer container association and multi-lock collaboration, as provided in an embodiment of this application.

[0022] Reference Figure 1 This includes the following steps: S101. Obtain the material requisition request, determine the inventory layout association record that matches the material requisition request, and determine the leaf container, top-level container, source storage location, production line task, and target storage location based on the inventory layout association record and the material requisition request.

[0023] S102. Verify the integrity and type matching of references between inventory layout association records, leaf containers, top-level containers and source storage locations, as well as between material call requests, production line tasks and target storage locations, to obtain a verifiable location chain.

[0024] S103. Based on the verifiable location chain, determine the set of joint update objects consisting of source storage location, target storage location, and inventory layout association records.

[0025] S104. Based on the set of joint update objects, apply for business locks for the source storage location, target storage location, and inventory layout association records in sequence.

[0026] S105. In response to the successful acquisition of all business locks, a transport instruction form is created within the critical section of the business lock to move the top-level container from the source storage location to the target storage location.

[0027] S106. Within the critical zone of the business lock, the status of the production line task, source warehouse location, target warehouse location, and inventory layout associated records are linked and migrated using the handling instruction sheet as the joint status migration voucher.

[0028] S107. In response to failure of business lock acquisition, abnormal creation of material handling instruction sheet or abnormal joint state migration, release the business lock occupied by the material call request in reverse order, and restore the state of the production line task, source warehouse location, target warehouse location and inventory layout association record that has been migrated in reverse order.

[0029] In this embodiment of the application, the material call request is used to trigger a whole-aircraft material call execution.

[0030] For example, a material call request can include a request identifier, a target production line identifier, a target material identifier, a button source, and a trigger time.

[0031] In some embodiments, after obtaining a material requisition request, the material and production line information carried in the requisition request is used to determine the matching inventory layout association record. The inventory layout association record, as a materialized carrier of multi-level relationships, may include leaf container references, top-level container references, storage location references, production line references, material identifiers, quantities, lock flags, and creation times.

[0032] In this embodiment of the application, the inventory layout association record is used to determine the leaf container, the top-level container and the source storage location, and the material call request is used to determine the production line task and the target storage location.

[0033] In this embodiment of the application, the leaf container represents a single container carried by the top-level container, the top-level container represents the object to be transported in this whole rack call, the source storage location represents the storage location where the top-level container is currently located, and the target storage location represents the target unloading point corresponding to the production line task.

[0034] In this embodiment of the application, after the object is determined, two sets of reference relationships are processed respectively. The first set of reference relationships is located between the inventory layout association record, leaf container, top-level container and source storage location, and the second set of reference relationships is located between the material call request, production line task and target storage location.

[0035] Specifically, reference integrity verification determines whether each reference exists, while type matching verification determines whether the record type pointed to by the reference matches the object type corresponding to the referenced field. Based on this, after both sets of reference relationships pass the verification, a verifiable locating chain is obtained.

[0036] In this embodiment, the verifiable location chain is used to determine the objects that need to be jointly protected and updated in this material requisition execution. The joint update object set consists of source storage location, target storage location, and inventory layout association records. This joint update object set determines the scope of the business lock application and provides source storage location, target storage location, and inventory layout association records to subsequent business lock applications.

[0037] In this embodiment, business locks are applied for sequentially according to the order of source location, target location, and inventory layout association records. Successful acquisition of all business locks indicates that all three jointly updated objects have entered the protection scope of this material requisition request, and then the process enters the business lock critical section. Within the business lock critical section, a material handling instruction is created with the top-level container as the material handling object and the source and target locations as the start and end points of the material handling.

[0038] In this embodiment, the transport instruction sheet serves as a joint state migration credential. Based on this, after the transport instruction sheet is created, the state of the production line task, source warehouse location, target warehouse location, and inventory layout associated records are migrated in a coordinated manner within the business lock critical section.

[0039] Specifically, the storage location status obtained from the linkage migration includes the source storage location in a locked state and the target storage location in an occupied state with the top-level container identifier written in. The task status and layout status obtained from the linkage migration correspond to the transfer instruction sheet.

[0040] In this embodiment, when a service lock application, material handling instruction creation, or joint state transition fails or an anomaly occurs, the service locks already occupied by the current material call request are released in the reverse order of the service lock application order, and the transitioned states are restored in the reverse order of the state transition relationship. The failure compensation is limited to the actual occupied service locks and the actual transitioned states.

[0041] In this embodiment of the application, a verifiable location chain can be obtained and a set of joint update objects can be determined by using inventory layout association records, material call requests, and two sets of reference verifications.

[0042] In this embodiment, applying for business locks on source storage locations, target storage locations, and inventory layout association records in the same order can reduce the possibility of concurrent material calls resulting in circular waiting and contention for overwriting. Furthermore, creating a handling instruction sheet within the critical section of the business lock and migrating related states in conjunction with it can reduce the possibility of other material call requests inserting modifications during their processing. Moreover, releasing the business lock in reverse order and restoring the migrated state in case of failure or exception is beneficial for restoring the consistency of the business lock and related object states.

[0043] In one feasible embodiment, determining the inventory layout associated record that matches the material requisition request includes obtaining a filter identifier, filtering candidate records, and selecting a target record.

[0044] Specifically, the target material identifier and target production line identifier are obtained from the material requisition request. The target material identifier is used to match the material identifier in the inventory layout association record, and the target production line identifier is used to match the production line reference in the inventory layout association record. Further, candidate inventory layout association records are filtered from the set of inventory layout association records. Candidate inventory layout association records must simultaneously satisfy the following conditions: the material identifier matches the target material identifier, the production line reference matches the target production line identifier, the quantity is greater than zero, and the lock flag is in an available state. A quantity greater than zero indicates that the corresponding inventory layout association record has materials available for this material requisition, and the lock flag being in an available state indicates that the corresponding record can enter subsequent business lock applications. Based on this, the candidate inventory layout association records are sorted in ascending order of creation time, and the first candidate inventory layout association record after sorting is selected to obtain the inventory layout association record matching the material requisition request.

[0045] In this embodiment, the use of material, production line, quantity, and lock flag for screening helps to exclude records with mismatched materials or production lines, zero quantities, or records that are already occupied. Furthermore, this application selects the first candidate record in ascending order of creation time, ensuring consistency in the selection criteria for matching records.

[0046] In another feasible embodiment, the inventory layout association record and the material call request are used as inputs to two object query chains, which can be executed separately without limiting the order of execution.

[0047] Specifically, in the first object query chain, the leaf container record is retrieved based on the leaf container reference recorded in the inventory layout association record to obtain the leaf container; the top-level container record is retrieved based on the top-level container reference recorded in the inventory layout association record to obtain the top-level container; and the source storage location is retrieved based on the storage location reference in the top-level container record.

[0048] Among them, leaf container determination and top-level container determination share the same inventory layout association record input, and source storage location determination uses the storage location reference of the top-level container.

[0049] In the second object query chain, the production line task record is queried based on the task identifier in the material call request to obtain the production line task; the storage location record is queried based on the target material unloading point reference in the production line task record to obtain the target storage location.

[0050] Among them, the production line task and the target storage location are received in sequence, and the target storage location represents the unloading point corresponding to the production line task.

[0051] Figure 2 The embodiments of this application provide a schematic diagram of the relationship between multi-layer container association and verifiable location chain.

[0052] Reference Figure 2 Inventory layout association records point to the leaf container and top-level container respectively through leaf container references and top-level container references. The top-level container points to the source storage location through its current storage location reference. Material call requests correspond to production line tasks through task identifiers, and production line tasks correspond to target storage locations through target unloading points. The first and second object query chains provide two sets of reference verification objects, and the results of the two sets of reference verifications are used together to obtain a verifiable location chain.

[0053] In some implementations, the four-layer relationship between leaf containers, top-level containers, storage locations, and production line tasks can be formally expressed using the following set: ; Where M represents the set of four-level association mappings, Represents the set of leaf containers. Let B represent the top-level container set, B represent the storage location set, and T represent the production line task set. This represents a four-element association consisting of a leaf container, a top-level container, a storage location, and a production line task. Indicates a leaf container, 'b' represents a top-level container, 'b' represents a storage location, and 't' represents a production line task. The four-level association mapping is used to represent the object relationships carried by the inventory layout association records. The target storage location is determined based on the target unloading point reference of the production line task, and together with the source storage location and the inventory layout association records, it forms a joint update object set.

[0054] Specifically, the reference integrity and type matching checks include verifying whether the leaf container references and top-level container references in the inventory layout association records can point to their respective records, whether the storage location reference of the top-level container can point to the source storage location, and whether the task identifier and the target unloading point reference of the production line task in the material requisition request can respectively determine the production line task and the target storage location. Furthermore, the parent container reference in the leaf container record is also used to check the reverse constraint between the leaf container and the top-level container; when the parent container reference points to the corresponding top-level container, the corresponding association satisfies the reverse constraint.

[0055] For example, the top-level container can be the steel frame R, and the leaf containers can be boxes B1, B2, B3, and B4. The storage location reference of the steel frame R points to the source storage location P, and the parent container references of the four leaf containers point to the steel frame R respectively.

[0056] For example, the material call request of production line A is identified by the task identifier, and the target unloading point reference of production line A task points to the unloading point of production line A.

[0057] For example, the inventory layout association record serves as the association carrier, enabling the location of box B1, box B2, box B3, box B4, steel frame R, source warehouse location P, and production line A task to be located along the reference relationship; source warehouse location P, production line A unloading point, and inventory layout association record constitute the joint update object set for this material call.

[0058] Based on this, the two object query chains respectively determine the container and source repository objects and the task and target repository objects, so that the reference verification and joint update objects have clear processing objects.

[0059] In another feasible embodiment, the service lock is implemented by updating the lock flag bit of the database record.

[0060] Specifically, when the identifier or associated field of the target record matches and the lock flag is in an available state, the conditional update will update the lock flag to a locked state. The number of affected rows in the database record update is used to represent the occupancy result of the corresponding business lock.

[0061] Figure 3 The flowchart illustrates the sequential application and failure release of three service locks provided in this application embodiment.

[0062] Reference Figure 3 This includes the following steps: S301. Perform a database record update on the source storage location based on the condition that the source storage location identifier matches and the lock flag is in an available state, so as to update the lock flag of the source storage location to a locked state and obtain the number of rows affected by the source storage location update.

[0063] S302. Determine the number of rows affected by the source location update; terminate the business lock application when the number of rows affected by the source location update is zero, and proceed with the target location business lock application when the number of rows affected by the source location update reaches one row.

[0064] S303. Perform a database record update on the target storage location based on the condition that the target storage location identifier matches and the lock flag is in an available state. Update the lock flag of the target storage location to a locked state and obtain the number of rows affected by the target storage location update.

[0065] S304. Determine the number of rows affected by the update of the target storage location; when the number of rows affected by the update of the target storage location is zero, release the business lock of the source storage location and terminate the business lock application; when the number of rows affected by the update of the target storage location reaches one row, enter the inventory layout association record business lock application.

[0066] S305. Perform a database record update on the inventory layout associated record, with the storage location field pointing to the source storage location and the lock flag being in an available state. Update the lock flag of the inventory layout associated record to a locked state and obtain the number of rows affected by the layout record update.

[0067] S306. Determine the number of rows affected by the layout record update; when the number of rows affected by the layout record update is zero, release the business locks of the target storage location and the source storage location in sequence and terminate the business lock application; when the number of rows affected by the layout record update reaches one row, the business locks are successfully occupied.

[0068] S307. Successfully secured business locks for source location, target location, and inventory layout association records.

[0069] In some embodiments, the source storage location business lock is the first business lock in a fixed application order. When the source storage location condition update does not affect database records, the number of rows affected by the source storage location update is zero, and the current material requisition request does not acquire the source storage location business lock, and the business lock application terminates at this point; when the number of rows affected by the source storage location update reaches one row, the source storage location lock flag has been updated to the locked state, and the application for the target storage location business lock continues.

[0070] Based on this, the target storage location business lock is the second business lock in the fixed application order. When the number of rows affected by the target storage location update is zero, the target storage location business lock acquisition fails, at which point the already acquired source storage location business lock is released and the application is terminated; when the number of rows affected by the target storage location update reaches one, the application for the inventory layout associated record business lock continues.

[0071] Furthermore, the inventory layout association record business lock is the third business lock in the fixed application order. The storage location field in the condition update points to the source storage location, used to limit the source storage location corresponding to this material requisition for the locked inventory layout association record. When the number of rows affected by the layout record update is zero, the target storage location business lock and the source storage location business lock are released in the reverse order of the application order. When the number of rows affected by the layout record update reaches one, it is determined that all three business locks have been successfully acquired and the process enters the business lock critical section.

[0072] In this embodiment, the source location, target location, and inventory layout association records are processed in the same order. This ensures that material request requests for overlapping objects apply for business locks in the same sequence, reducing the likelihood of different material request requests holding different business locks and waiting for each other. Furthermore, releasing the already held preceding business lock when any subsequent business lock fails to be acquired reduces the likelihood of some business locks being continuously held.

[0073] In one feasible embodiment, after all business locks are successfully acquired, the container identifier of the top-level container is read, a handling instruction sheet is assembled based on the source storage location, the target storage location, and the container identifier, and a handling instruction sheet is created within the critical section of the business lock.

[0074] For example, a transport instruction record can include document status, transport type, source storage location, target storage location, top-level container reference, robot task definition identifier, and remarks. Among them, the source storage location, target storage location, and top-level container reference represent the transport start point, transport end point, and transport object, respectively.

[0075] In this embodiment, the source storage location, the target storage location, and the container identifier are used together to create a transport instruction sheet, so that the transport instruction sheet has a clear correspondence with the top-level container and the start and end locations of the transport; after the transport instruction sheet is successfully created, the transport instruction sheet serves as a joint state transition certificate.

[0076] In this embodiment, the joint state migration involves task state, storage location state, and layout state. The task state may include task state fields, remarks or exception descriptions, and execution target; the storage location state may include source storage location lock flag, target storage location loading status, target storage location occupancy flag, and top-level container identifier written to the target storage location; the layout state may include material identifier, production line reference, quantity, lock flag, top-level container reference, leaf container reference, and storage location reference.

[0077] Based on this, within the critical section of the business lock, the remarks information of the production line task is cleared; the loading status and occupancy flag of the target storage location are updated to the occupied status, and the container identifier of the top-level container is written to the target storage location; the locking flag of the inventory layout association record is updated to the locked status. The locking flag of the source storage location has already been updated to the locked status during the business lock application process; therefore, the storage location status obtained from the joint state migration includes both the source storage location in the locked state and the target storage location in the occupied state.

[0078] In this embodiment, the status processing of production line tasks, target storage locations, and inventory layout related records is implemented around the same material handling instruction. Furthermore, by processing the task status, storage location status, and layout status in a coordinated manner within the business lock critical section, it is beneficial to reduce the possibility of inconsistencies arising from the modification of related statuses by concurrent material requisition requests.

[0079] In another feasible embodiment, failure handling is triggered by failure of business lock acquisition, abnormal creation of transport instruction sheet, or abnormal joint state transition. Failure handling includes compensation and recovery of business lock and state, as well as failure context recording and persistent retry processing.

[0080] Figure 4 A flowchart illustrating the failure compensation and recovery and failure recording process provided in this application embodiment.

[0081] Reference Figure 4 This includes the following steps: S401, Detection of business lock occupancy failure, abnormal creation of transport instruction sheet, or abnormal joint state migration.

[0082] S402a, Reverse the order of releasing the service lock that has been occupied by the call request.

[0083] S403a, Reverse the state that has been migrated.

[0084] S402b: Record the failure stage and competing object of this material request, and obtain the failure context.

[0085] S403b: Write the failure context to the failure log and add the production line task to the persistent retry queue.

[0086] Specifically, the scope of business lock compensation is determined based on the location of the failure: when the source warehouse location business lock fails to be used, the business lock application is terminated if the current material call request does not use the business locks of the source warehouse location, target warehouse location, and inventory layout association record; when the target warehouse location business lock fails to be used, the source warehouse location business lock that has already been used is released; when the inventory layout association record business lock fails to be used, the target warehouse location business lock and the source warehouse location business lock are released in sequence.

[0087] Furthermore, if an error occurs in the creation of a material handling order or a joint state migration after all three business locks have been successfully acquired, the business locks acquired for this material call request will be released in the order of inventory layout association record, target storage location, and source storage location. If the joint state migration has already changed some of the states, the states of the production line task, source storage location, target storage location, and inventory layout association record that have been migrated will be restored in the reverse order of the state migration relationship.

[0088] For example, a failure context can include a request identifier, failure category, failure stage, contested object identifier, source storage location identifier, target storage location identifier, top-level container identifier, timestamp, and error description. The failure stage indicates that the failure occurred at the corresponding stage in the business lock application, transport instruction creation, or joint state migration. The contested object identifier indicates the source storage location, target storage location, or inventory layout association record corresponding to the business lock occupancy failure.

[0089] Based on this, after obtaining the failure context, the failure context is written to the failure log, and the production line task is added to the persistent retry queue. The writing of the failure log and the enqueueing of the production line task are both based on the failure context. There is no restriction on the order of the two processing actions. The failure log is used to retain the failure stage and the contention object, and the persistent retry queue is used to carry the production line tasks waiting to be re-executed.

[0090] In this embodiment, reversing the release of the service lock and reversing the state helps to restore the already executed local processing along the reverse relationship; the failure context can retain the failure phase and the contention object, and the persistent retry queue provides support for the subsequent re-execution of failed tasks.

[0091] Figure 5The timing diagram for the entire chain of concurrent whole-frame material calling provided in the embodiments of this application.

[0092] Reference Figure 5 Production lines A and B each initiate a material requisition request, with both requests corresponding to the top-level container steel frame R and the source storage location P. The steel frame R carries boxes B1, B2, B3, and B4, and production lines A and B each have corresponding target storage locations.

[0093] For example, the material requisition request from production line A first determines the matching inventory layout association record, and then determines the leaf container, steel frame R, source storage location P, production line A task, and production line A target storage location along the inventory layout association record and production line A's material requisition request. After the reference verification passes, a verifiable location chain is obtained, and a joint update object set consisting of source storage location P, production line A target storage location, and inventory layout association record is determined.

[0094] For example, production line A's material requisition request requests business locks in the order of source location P, production line A's target location, and inventory layout association record. After all three business locks are successfully acquired, production line A's material requisition request enters the business lock critical section, creating a transport instruction order to move the steel frame R from source location P to production line A's target location, and using the transport instruction order as evidence to link and migrate the status of production line A's task, source location P, production line A's target location, and inventory layout association record.

[0095] For example, production line B requests a new lock on the same source location P after production line A has already acquired it. Since the lock flag for source location P is already locked, the number of rows affected by the source location update for production line B is zero, and production line B's lock request terminates at source location P. Production line B records the failure phase and the contention object corresponding to source location P, obtains the failure context, writes the failure context to the failure log, and adds production line B's task to the persistent retry queue.

[0096] For example, when an anomaly occurs during the creation of a material handling order or a joint state migration in production line A, a compensation and recovery process is initiated. Compensation and recovery releases the already occupied business locks in the order of inventory layout association records, production line A's target storage location, and source storage location P, and restores the migrated states in the reverse order of the state migration relationship. Thus, in the normal execution path, the material handling order and related states are processed around the same material requisition request, while in paths where contention fails or an anomaly occurs, the already occupied business locks and migrated states undergo corresponding compensation processing.

[0097] Figure 6 This is a block diagram of a multi-layer container association and multi-lock collaboration whole-frame material calling execution system provided in an embodiment of this application.

[0098] Reference Figure 6This application provides a whole-frame material calling execution system with multi-layer container association and multi-lock collaboration.

[0099] In this embodiment of the application, the whole-frame material call execution system includes an associated positioning module 601, a concurrent execution module 602, and a compensation and recovery module 603.

[0100] In some implementations, the association positioning module 601 receives a material requisition request, determines the inventory layout association record matching the material requisition request from the inventory layout association record set, and determines the leaf container, top-level container, source storage location, production line task, and target storage location based on the inventory layout association record and the material requisition request. The association positioning module 601 verifies the reference integrity and type matching between the inventory layout association record, leaf container, top-level container, and source storage location, as well as between the material requisition request, production line task, and target storage location, to obtain a verifiable positioning chain; it determines a joint update object set consisting of the source storage location, target storage location, and inventory layout association record based on the verifiable positioning chain, and provides the joint update object set, along with the objects required for order creation and state transition, to the concurrent execution module 602.

[0101] The concurrent execution module 602 receives the set of joint update objects and sequentially applies for business locks on the source storage location, target storage location, and inventory layout association records according to the set of joint update objects. After all business locks are successfully acquired, a transfer instruction order is created within the critical section of the business lock to move the top-level container from the source storage location to the target storage location. The transfer instruction order is used as the joint state migration certificate to link the state of the production line task, source storage location, target storage location, and inventory layout association records, and obtain the business lock acquisition result, the transfer instruction order, and the joint state migration result.

[0102] The compensation and recovery module 603 responds to business lock occupancy failure, abnormal creation of transport instruction sheet, or abnormal joint state migration. Based on the business locks already occupied and the migrated states of this material call request, it releases the business locks in reverse order and restores the migrated states of production line tasks, source warehouse locations, target warehouse locations, and inventory layout association records in reverse order.

[0103] In this embodiment, the verifiable positioning chain and the set of joint update objects output by the associated positioning module 601 provide a clear processing object for the concurrent execution module 602. The concurrent execution module 602 completes the application for business lock, order creation and state transition around the set of joint update objects. Failure or abnormal conditions trigger the compensation and recovery module 603 to perform recovery processing. The three modules form data and triggering relationships through the set of joint update objects, business lock occupancy results, handling instruction sheets and failure or abnormal conditions, so that associated positioning, concurrent execution and compensation and recovery are coordinated and executed around the same whole rack material call.

[0104] In one feasible embodiment, the concurrent execution module 602 sequentially performs database record updates on the source storage location, target storage location, and inventory layout association records in the joint update object set, and determines the business lock occupancy result based on the number of rows affected by the corresponding database record updates.

[0105] Specifically, the concurrent execution module 602 first performs a database record update on the source storage location based on the condition that the source storage location identifier matches and the lock flag is in an available state. This updates the lock flag of the source storage location to a locked state and obtains the number of rows affected by the source storage location update. When the number of rows affected by the source storage location update reaches one row, it continues to request a business lock for the target storage location; otherwise, it terminates the business lock request. The concurrent execution module 602 then performs a database record update on the target storage location based on the condition that the target storage location identifier matches and the lock flag is in an available state. This updates the lock flag of the target storage location to a locked state and obtains the number of rows affected by the target storage location update. When the number of rows affected by the target storage location update reaches one row, it continues to request a business lock for the inventory layout associated record; otherwise, it releases the source storage location business lock and terminates the business lock request. The concurrent execution module 602 performs database record updates on the inventory layout association records, based on the condition that the storage location field points to the source storage location and the lock flag is in an available state. It updates the lock flag of the inventory layout association records to a locked state and obtains the number of rows affected by the layout record update. When the number of rows affected by the layout record update reaches one, it is determined that the business locks for the source storage location, target storage location, and inventory layout association records have all been successfully acquired; otherwise, the business locks for the target storage location and the source storage location are released sequentially, and the business lock application is terminated. Based on this, the concurrent execution module 602 uses the number of rows affected by each database record update to determine the business lock acquisition results item by item, ensuring that the business lock application results correspond to the conditional update results of the source storage location, target storage location, and inventory layout association records.

[0106] In another feasible embodiment, the compensation and recovery module 603 also records the failure stage and contention object of this material call request, obtains the failure context, writes the failure context into the failure log, and adds the production line task to the persistent retry queue. The failure log writing and production line task enqueueing are both triggered by the failure of business lock acquisition, the abnormal creation of the transport instruction sheet, or the abnormal joint state transition.

[0107] In this embodiment, the failure context enables the compensation and recovery module 603 to retain the location of the failure and the business lock contention object, and the persistent retry queue is used to save production line tasks waiting to be re-executed, providing corresponding data for anomaly tracing and task recovery from the perspective of system function coordination.

[0108] Figure 7 A flowchart of state machine button gating provided for an embodiment of this application.

[0109] Reference Figure 7 This includes the following steps: S701: Perform button task distribution polling to determine whether to enter the material requisition process or the return to inventory process based on the parity of the button address.

[0110] S702. Determine whether the following conditions are met simultaneously: the pager signal is flashing, the production line task is issued, the target material unloading point is empty, and there is an inventory layout association record with a lock flag that is available and the quantity is greater than zero.

[0111] S703a: In response to the simultaneous fulfillment of the four conditions, the corresponding material call request is released and enters the associated location processing.

[0112] S703b: In response to any condition not being met, turn off the light feedback and block the corresponding execution.

[0113] For example, the button task distribution polling determines the corresponding button task to enter the material requisition process or the return to the warehouse process based on the parity of the button address.

[0114] For example, the button task to enter the material requisition process accepts pre-processing and resource gating judgments.

[0115] In this embodiment, the pre-processor and resource gating sequentially determine whether the caller signal is flashing, whether the production line task is in a published state, whether the target material unloading point is empty, and whether there is an inventory layout association record where the lock flag is in an available state and the quantity is greater than zero. When all four conditions are met simultaneously, the state machine button gating allows the corresponding material call request to enter the associated positioning process; when any condition is not met, the state machine button gating turns off the light feedback and blocks the corresponding execution.

[0116] This application reduces the number of material call requests that do not meet the execution conditions from entering multiple service lock applications by checking the call status, task status, target material unloading point status, and inventory layout resource status before associating location and applying for service locks.

[0117] Regarding the system in the above embodiments, the specific ways in which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated here.

[0118] Although the operations are described in a specific order in the accompanying drawings, this should not be construed as requiring these operations to be performed in the specific order or serial order shown, or requiring all of the operations shown to obtain the desired result. In certain environments, multitasking and parallel processing may be advantageous.

[0119] The methods and systems of this application can be implemented using standard programming techniques, utilizing rule-based logic or other logic to implement various method steps. It should also be noted that the terms "system" and "module" as used herein and in the claims are intended to include implementations using one or more lines of software code and / or hardware implementations and / or devices for receiving input.

[0120] Any step, operation, or procedure described herein may be performed or implemented using one or more hardware or software modules, either alone or in combination with other devices. In one embodiment, the software module is implemented using a computer program product comprising a computer-readable medium containing computer program code, which is executable by a computer processor to perform any or all of the described steps, operations, or procedures.

[0121] The foregoing description of implementations of this application has been provided for illustrative and descriptive purposes. The foregoing description is not exhaustive and is not intended to limit this application to the exact forms disclosed. Various modifications and variations may exist in accordance with the foregoing teachings, or may arise from practice of this application. These embodiments were chosen and described to illustrate the principles of this application and its practical application, enabling those skilled in the art to utilize this application in various implementations and modifications to suit the specific purpose of the concept.

[0122] Regarding the system in the above embodiments, the specific ways in which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated here.

[0123] It can be further understood that, unless otherwise specified, "connection" includes both direct connections where no other components exist between the two parties and indirect connections where other components exist between them.

[0124] It is further understood that although the operations are described in a specific order in the accompanying drawings in the embodiments of this application, this should not be construed as requiring these operations to be performed in the specific order or serial order shown, or requiring all the operations shown to be performed to obtain the desired result. In certain environments, multitasking and parallel processing may be advantageous.

[0125] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the field of this application that are not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0126] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

[0127] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for executing whole-frame material calling based on multi-layer container association and multi-lock coordination, characterized in that, include: Obtain a material requisition request, determine the inventory layout association record that matches the material requisition request, and determine the leaf container, top-level container, source storage location, production line task, and target storage location based on the inventory layout association record and the material requisition request; Verify the integrity and type matching of references between the inventory layout association record, the leaf container, the top-level container and the source storage location, as well as between the material call request, the production line task and the target storage location, to obtain a verifiable location chain; Based on the verifiable location chain, a set of joint update objects consisting of the source storage location, the target storage location, and the inventory layout association record is determined, and based on the set of joint update objects, business locks for the source storage location, the target storage location, and the inventory layout association record are applied for in sequence. In response to the successful acquisition of all the business locks, a transfer instruction form is created within the critical section of the business lock to move the top-level container from the source storage location to the target storage location; Within the critical zone of the business lock, the transport instruction sheet serves as the joint state migration credential, linking and migrating the states of the production line task, the source storage location, the target storage location, and the associated records of the inventory layout; In response to failure to acquire a business lock, an abnormality in the creation of a material handling instruction, or an abnormality in the joint state migration, the business lock held by the material call request is released in reverse order, and the migrated states of the production line task, the source storage location, the target storage location, and the inventory layout association record are restored in reverse order.

2. The method according to claim 1, characterized in that, The process of determining the inventory layout association record that matches the material requisition request includes: Obtain the target material identifier and target production line identifier from the material request; From the set of inventory layout association records, filter candidate inventory layout association records that match the target material identifier, match the target production line identifier, have a quantity greater than zero, and have a lock flag in an available state. The first candidate inventory layout association record is selected in ascending order of creation time and used as the inventory layout association record that matches the material requisition request.

3. The method according to claim 1, characterized in that, The step of determining the leaf container, top-level container, source storage location, production line task, and target storage location based on the inventory layout association records and the material requisition request includes: Based on the leaf container reference and top-level container reference recorded in the inventory layout association record, the leaf container and the top-level container are determined respectively, and the source storage location is determined based on the storage location reference of the top-level container. The production line task is determined based on the task identifier in the material requisition request, and the target storage location is determined based on the target unloading point reference of the production line task.

4. The method according to claim 1, characterized in that, The step of sequentially requesting business locks for the source storage location, the target storage location, and the inventory layout association record based on the joint update object set includes: Perform a database record update on the source storage location based on the condition that the source storage location identifier matches and the lock flag is in an available state, so as to update the lock flag of the source storage location to a locked state and obtain the number of rows affected by the source storage location update. In response to the fact that the number of rows affected by the source database location update is zero, the business lock application is terminated; In response to the number of rows affected by the source storage location update reaching one row, a database record update is performed on the target storage location based on the condition that the target storage location identifier matches and the lock flag is in an available state, and the lock flag of the target storage location is updated to a locked state, thus obtaining the number of rows affected by the target storage location update; In response to the target storage location update affecting zero rows, the business lock of the source storage location is released and the business lock application is terminated; In response to the target storage location update affecting a row, a database record update is performed on the inventory layout associated record, with the storage location field pointing to the source storage location and the lock flag being in an available state. The lock flag of the inventory layout associated record is updated to a locked state, and the number of rows affected by the layout record update is obtained. In response to the fact that the number of rows affected by the layout record update is zero, the business locks of the target storage location and the source storage location are released sequentially, and the business lock application is terminated. When the number of rows affected by the layout record update reaches one row, it is determined that the business locks for the source storage location, the target storage location, and the inventory layout association record have all been successfully acquired.

5. The method according to claim 1, characterized in that, In response to the successful acquisition of all business locks, a transfer instruction form is created within the critical section of the business locks to move the top-level container from the source storage location to the target storage location, including: Read the container identifier of the top-level container; Based on the source storage location, the target storage location, and the container identifier, the handling instruction sheet is created.

6. The method according to claim 1, characterized in that, The process of using the handling instruction as a joint state migration credential within the business lock critical zone to link and migrate the states of the production line task, the source storage location, the target storage location, and the associated inventory layout records includes: Clear the remarks information for the aforementioned production line task; Update the loading status and occupancy flag of the target storage location to the occupancy status, and write the container identifier of the top-level container to the target storage location; Update the lock flag of the inventory layout associated record to the locked state.

7. The method according to claim 1, characterized in that, The method further includes: In response to failure of business lock acquisition, abnormal creation of transport instruction sheet, or abnormal joint state transition, record the failure stage and contention object of this material call request, and obtain the failure context; Write the failure context to the failure log and add the production line task to the persistent retry queue.

8. A multi-layer container association and multi-lock coordination whole-frame material calling execution system, characterized in that, include: The associated positioning module is used to acquire a material requisition request, determine the inventory layout association record matching the material requisition request, and determine the leaf container, top-level container, source storage location, production line task, and target storage location based on the inventory layout association record and the material requisition request; verify the reference integrity and type matching between the inventory layout association record, the leaf container, the top-level container, and the source storage location, as well as between the material requisition request, the production line task, and the target storage location, to obtain a verifiable positioning chain; and determine a joint update object set composed of the source storage location, the target storage location, and the inventory layout association record based on the verifiable positioning chain. The concurrent execution module is used to sequentially apply for business locks on the source storage location, the target storage location, and the inventory layout association record according to the joint update object set; in response to the successful acquisition of all business locks, a transfer instruction order is created within the business lock critical section to move the top-level container from the source storage location to the target storage location; within the business lock critical section, the transfer instruction order is used as the joint state migration credential to link and migrate the states of the production line task, the source storage location, the target storage location, and the inventory layout association record; The compensation and recovery module is used to release the business lock occupied by the material call request in reverse order in response to failure of business lock acquisition, abnormal creation of material handling instruction order or abnormal joint state migration, and to restore the migrated state of the production line task, the source storage location, the target storage location and the inventory layout association record in reverse order.

9. The system according to claim 8, characterized in that, The concurrent execution module requests the business lock in the following manner: Perform a database record update on the source storage location based on the condition that the source storage location identifier matches and the lock flag is in an available state, so as to update the lock flag of the source storage location to a locked state and obtain the number of rows affected by the source storage location update. In response to the fact that the number of rows affected by the source database location update is zero, the business lock application is terminated; In response to the number of rows affected by the source storage location update reaching one row, a database record update is performed on the target storage location based on the condition that the target storage location identifier matches and the lock flag is in an available state, and the lock flag of the target storage location is updated to a locked state, thus obtaining the number of rows affected by the target storage location update; In response to the target storage location update affecting zero rows, the business lock of the source storage location is released and the business lock application is terminated; In response to the target storage location update affecting a row, a database record update is performed on the inventory layout associated record, with the storage location field pointing to the source storage location and the lock flag being in an available state. The lock flag of the inventory layout associated record is updated to a locked state, and the number of rows affected by the layout record update is obtained. In response to the fact that the number of rows affected by the layout record update is zero, the business locks of the target storage location and the source storage location are released sequentially, and the business lock application is terminated. When the number of rows affected by the layout record update reaches one row, it is determined that the business locks for the source storage location, the target storage location, and the inventory layout association record have all been successfully acquired.

10. The system according to claim 8, characterized in that, The compensation and recovery module is also used for: In response to failure of business lock acquisition, abnormal creation of transport instruction sheet, or abnormal joint state transition, record the failure stage and contention object of this material call request, and obtain the failure context; Write the failure context to the failure log and add the production line task to the persistent retry queue.

Images