Supply chain resource global configuration optimization method and system based on cross-chain cooperation

Abstract

The present application relates to the technical field of transaction verification, in particular to a cross-chain collaborative supply chain resource global configuration optimization method and system, the method comprising the following steps: obtaining resource state records formed by matching business chain confirmation records and on-site terminal state records, comparing on-chain state and on-site state to generate resource time window slot, determining continuous task segments and preoccupiable slot combinations according to order demand, determining pre-occupancy configuration strategy according to resource idle time and empty driving distance, and generating on-chain occupation credentials and execution instructions. In the present application, by means of resource number matching, time window slot conversion, task segment connection determination and on-chain credential confirmation, the account book confirmation state, on-site physical state and operation control instruction are included in the same configuration link, the deviation between cross-chain state synchronization and on-site execution is compressed, repeated occupation, carrying breakpoint, scheduling conflict and confirmation lag are reduced, and the supply chain resource configuration result has a continuous execution boundary.

Description

Technical Field

[0001] This invention relates to the field of transaction verification technology, and in particular to a method and system for optimizing the global allocation of supply chain resources through cross-chain collaboration. Background Technology

[0002] The field of transaction verification technology involves data processing methods for verifying on-chain transaction messages, account addresses, resource status, and transaction signatures in blockchain applications. Among these, the traditional supply chain resource global configuration optimization method involves the supply chain platform encapsulating procurement, inventory, warehousing, and transportation data into on-chain transaction records. After receiving the transaction message, the blockchain node reads the transaction identifier, resource number, account address, and signature fields, and completes the transaction legality verification and ledger writing according to preset verification rules.

[0003] In traditional supply chain resource allocation, the main data sources in actual operation are order data, inventory data, transportation data, and resource status data. The allocation records are written into the blockchain ledger, and the status and credentials are synchronized by cross-chain gateways or relay nodes. However, there is a lack of on-site verification of resource status under the same resource number between warehouse weighing, vehicle load, and processing equipment time. Inventory, vehicles, routes, and processing links each form local records, and it is difficult to unify the on-chain confirmation time with the on-site availability time. This can easily lead to duplicate occupation, transportation breakpoints, scheduling conflicts, and delays in the execution of allocation results. Summary of the Invention

[0004] To address the technical problems existing in the prior art, embodiments of the present invention provide a method for optimizing the global configuration of supply chain resources through cross-chain collaboration, comprising the following steps: To achieve the above objectives, the present invention adopts the following technical solution: a cross-chain collaborative supply chain resource global configuration optimization method, comprising the following steps: Obtain resource status records, which are obtained by matching business chain confirmation records belonging to two different supply chains with field terminal status records collected by warehousing terminals, vehicle terminals, and equipment controllers according to resource numbers; For the inventory batches, vehicle capacity and processing equipment time periods in the resource status records, compare the on-chain quantity with the on-site quantity, the remaining load capacity on the books with the sensor load capacity, and the equipment release time with the delivery deadline to determine the resource time window slot. Based on the order demand record and the resource time window slots, continuous task segments are determined. For adjacent task segments that have time connection, spatial connection, capacity continuity and are not occupied on the chain, the combination of reservable slots is determined. Based on the pre-occupiable slot combinations, the pre-occupancy configuration strategy is determined by sorting the resource idle time, vehicle empty driving distance, processing waiting time, and cross-chain confirmation number. An on-chain occupancy certificate is generated. When the resource number, occupancy time interval, and occupancy capacity returned by the business chains of the two different supply chains are consistent with the on-chain occupancy certificate, warehouse outbound, vehicle transportation, route driving, and processing scheduling instructions are generated.

[0005] As a further aspect of the present invention, the process of obtaining the resource status record is specifically as follows: Obtain the business chain confirmation records returned by the order business chain, inventory business chain, transportation business chain, processing business chain and capital business chain respectively contained in the first supply chain and the second supply chain, and extract the resource number, on-chain generation time, occupation status and resource content fields from each business chain confirmation record; Acquire the status records of the field terminals collected by the warehouse terminal, vehicle terminal and equipment controller respectively, and extract the resource number, field collection time, physical status and available quantity from each field terminal status record; Establish a matching relationship between the business chain confirmation record with the same resource number and the field terminal status record. When the generation time on the chain is not later than the field collection time and the occupancy status is consistent with the physical status, write the matching relationship into the resource status record.

[0006] As a further aspect of the present invention, a timeliness check is performed before the matching relationship is written into the resource status record. The timeliness check specifically includes: The round-trip time of the cross-chain gateway connecting the first supply chain and the second supply chain is obtained for three consecutive confirmation records returned in this round of configuration calculation. The maximum value among the three round-trip times is determined as the record validity period. The time interval between the on-chain generation time and the on-site collection time is calculated. When the time interval exceeds the validity period of the record, the matching relationship is deleted. When the time interval does not exceed the validity period of the record, the matching relationship is retained.

[0007] As a further aspect of the present invention, the process of determining the resource window slot is specifically as follows: For the inventory batch, obtain the on-chain quantity, the occupied quantity, and the on-site quantity. Subtract the occupied quantity from the on-chain quantity to obtain the on-chain configurable quantity. Compare the on-chain configurable quantity with the on-site quantity. Determine the smaller of the on-chain configurable quantity and the on-site quantity as the inventory slot capacity. For the vehicle's carrying capacity, the remaining load capacity on the books and the sensing load capacity are obtained. The remaining load capacity on the books and the sensing load capacity are compared, and the load capacity of the smaller of the remaining load capacity on the books and the sensing load capacity is determined as the vehicle's slot capacity. For the processing equipment time period, the remaining time of the work order collected by the equipment controller and the delivery deadline returned by the processing business chain are obtained. The remaining time of the processing order is accumulated to determine the equipment release time. When the equipment release time is not later than the delivery deadline, the processing slot time is determined, and the resource time window slot is generated.

[0008] As a further aspect of the present invention, when the resource time window slot is generated, the time boundary of the slot is also determined. The process of determining the time boundary of the slot is as follows: Obtain the session generation time, resource availability start time, and resource availability end time of this round of configuration calculation. Determine the first resource availability start time that is later than the session generation time as the slot start time. Then, sequentially add the slot start time to the outbound operation time, vehicle arrival time, or processing execution time to obtain the slot end time. When the slot end time is not later than the resource availability end time, the resource number, slot start time, slot end time, and slot capacity are written into the resource time window slot.

[0009] As a further aspect of the present invention, the process of determining the continuous task segments is specifically as follows: Obtain the material category, order quantity, starting warehouse, processing requirements, delivery location, and delivery deadline from the order demand record; compare the order quantity with the inventory slot capacity in the resource time window slot; and select an inventory slot that can accommodate the order quantity. Based on the warehouse location of the selected inventory slot, the location of the processing equipment corresponding to the processing requirements, and the delivery location, the continuous task segments are generated in the order of business acceptance: inventory occupancy, warehouse outbound, vehicle transportation, route passage, processing execution, and finished product delivery.

[0010] As a further aspect of the present invention, the process for determining the pre-occupied slot combination is specifically as follows: For each task segment in the continuous task segment, a candidate slot with a resource type that matches the resource requirements of the task segment is selected from the resource time window slots, and the slot start time, slot end time, slot position, and slot capacity of the candidate slot are compared with the start time, end time, position, and quantity of the corresponding task segment. When the candidate slots corresponding to adjacent task segments meet the requirements of being sequential in time, reachable in location, having a capacity not less than the number of task segments, and being unoccupied on the chain, the candidate slots are written into the pre-occupied slot combination.

[0011] As a further aspect of the present invention, the process for determining the pre-occupancy configuration strategy is specifically as follows: The idle time of resources, empty driving distance of vehicles, processing waiting time and number of cross-chain confirmations between two supply chains are obtained for each slot combination in the pre-occupied slot combination. The idle time of resources is used as the first sorting item, the empty driving distance of vehicles as the second sorting item, the processing waiting time as the third sorting item, and the number of cross-chain confirmations as the last sorting item. The slot combinations are sorted in ascending order. When the values ​​of any sorting item are different, the slot combination with the higher ranking is retained. When the values ​​of any sorting item are the same, the next sorting item is compared. The slot combination with the highest ranking is selected to generate the pre-occupancy configuration strategy.

[0012] As a further aspect of the present invention, the process for obtaining resource idle time, vehicle idling distance, processing waiting time, and cross-chain confirmation count is as follows: The resource idle time is obtained by calculating the difference between the start time of each resource time window slot in the pre-occupied slot combination and the start time of the corresponding task segment. The vehicle's current location, loading location, and unloading location are connected sequentially to obtain the vehicle's driving path. The vehicle's empty driving distance is obtained by subtracting the driving distance under the condition of carrying cargo from the vehicle's driving path. The processing waiting time is obtained by calculating the difference between the release time of the processing equipment and the arrival time of the vehicle at the production line. The number of business chains that cross the first and second supply chains involved in the same slot combination is counted to obtain the number of cross-chain confirmations.

[0013] A cross-chain collaborative supply chain resource global allocation optimization system, the system comprising: The status verification module acquires resource status records, which are obtained by matching the business chain confirmation records belonging to two different supply chains with the on-site terminal status records collected by the warehousing terminal, vehicle terminal, and equipment controller according to the resource number. The resource orchestration module compares the on-chain quantity with the on-site quantity, the remaining load capacity on the books with the sensor load capacity, and the equipment release time with the delivery deadline in the resource status record for the inventory batches, vehicle capacity and processing equipment time periods to determine the resource time window slots. The task receiving module determines consecutive task segments based on order demand records and the resource time window slots. For adjacent task segments that have time connection, space connection, capacity connection and are not occupied on the chain, the module determines the combination of reservable slots. The voucher scheduling module determines the pre-occupancy configuration strategy based on the pre-occupiable slot combination, sorting by resource idle time, vehicle empty driving distance, processing waiting time, and cross-chain confirmation count. It generates on-chain occupancy vouchers. When the resource number, occupancy time interval, and occupancy capacity returned by the business chains of the two different supply chains are consistent with the on-chain occupancy vouchers, it generates warehouse outbound, vehicle transportation, route driving, and processing scheduling instructions.

[0014] Compared with the prior art, the advantages and positive effects of the present invention are as follows: In this invention, by matching business chain confirmation records and on-site terminal status records according to resource numbers, inventory batches, vehicle capacity, and processing equipment time periods are converted into resource time window slots. Then, continuous task segments are constructed based on order requirements. The time connection, spatial connection, capacity acceptance, and on-chain occupancy status of adjacent task segments are jointly determined to form a combination of pre-occupied slots. The pre-occupancy configuration strategy is determined based on resource idle time, vehicle empty driving distance, processing waiting time, and cross-chain confirmation count. After the on-chain occupancy certificate is consistent with the content returned by the business chain, an execution instruction is generated, so that ledger confirmation, on-site status, and operation control form a closed configuration link, reducing duplicate occupancy, scheduling conflicts, and cross-chain confirmation delays. Attached Figure Description

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

[0016] Figure 1 This is a flowchart illustrating the cross-chain supply chain resource allocation process of this invention. Figure 2 This is a schematic diagram illustrating the cross-chain status verification effect of the present invention; Figure 3 This is a schematic diagram illustrating the effect of generating resource window slots in this invention. Figure 4 This is a schematic diagram illustrating the continuous task segment succession effect of the present invention; Figure 5 This is a schematic diagram illustrating the occupancy certificate and scheduling closed-loop effect of the present invention. Detailed Implementation

[0017] The technical solution of the present invention will now be described with reference to the accompanying drawings.

[0018] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.

[0019] Please see Figures 1 to 5This embodiment provides a cross-chain collaborative supply chain resource global configuration optimization method. In practical applications, such as in a supply chain collaborative environment where raw material warehousing, warehouse outbound, vehicle transportation, production line processing, and finished product delivery operate continuously, the order business chain, inventory business chain, transportation business chain, processing business chain, and capital business chain continuously generate business chain confirmation records. Warehouse terminals, vehicle terminals, and equipment controllers continuously generate on-site terminal status records. The configuration process forms a closed loop around the same order demand record in terms of on-chain occupancy status, on-site physical status, resource time window slots, and scheduling instructions, including the following steps: S1: Obtain resource status records. These records are status data objects formed by matching business chain confirmation records belonging to two different supply chains with field terminal status records based on resource IDs. The resource ID is an index field used by both the business chain and field terminals for inventory batches, vehicle capacity, or processing equipment time periods. The business chain confirmation record is the evidence data returned after confirmation by the business chain node. The field terminal status record is the physical status data collected and uploaded by warehouse terminals, vehicle terminals, and equipment controllers when resource status changes. Each resource status record carries the resource ID, on-chain generation time, field collection time, occupancy status, physical status, resource content fields, available quantity, and status verification identifier, serving as input for the subsequent resource time window slot determination process.

[0020] Before generating resource status records, the business chain confirmation records and on-site terminal status records undergo field integrity verification. If a record is missing a resource number, time field, or status field, a supplementary entry identifier is generated and written to the exception queue. The exception queue only provides input to the link re-acquisition and terminal re-acquisition processes and does not enter the resource time window slot determination process. If duplicate records exist for the same resource number, the record whose on-chain generation time and on-site acquisition time meet the timeliness verification and whose status fields are completely connected is retained. The duplicate record is written to the status traceability log. The status traceability log saves the record source, interface source, parsing status, and processing result for traceability in the subsequent voucher verification process.

[0021] S101: Retrieve the business chain confirmation records returned by the order business chain, inventory business chain, transportation business chain, processing business chain, and capital business chain respectively contained in the first and second supply chains, and extract the resource number, on-chain generation time, occupancy status, and resource content fields from each business chain confirmation record. The order business chain returns the order demand record and order status; the inventory business chain returns the on-chain quantity and occupied quantity of the inventory batch; the transportation business chain returns the remaining book load capacity of the vehicle and the vehicle occupancy status; the processing business chain returns the processing equipment time period, delivery deadline, and work order status; and the capital business chain returns the capital constraint status corresponding to the resource pre-occupancy. The above fields are entered into the configuration cache through the cross-chain gateway. The configuration cache uses the resource number as an index to merge the confirmation records of the same resource on different business chains into the on-chain status view.

[0022] The on-chain state view is an intermediate data object generated in this step, carrying the resource status fields, link source, and confirmation status returned by each business chain. If the cross-chain gateway returns an interface error, field parsing failure, or incomplete business chain confirmation status, the corresponding resource in the on-chain state view is marked as pending verification on-chain. This mark prevents the corresponding resource from entering the pre-occupied slot combination. Resources pending verification on-chain are retained in the configuration cache and will re-participate in matching after the cross-chain gateway returns a complete confirmation record.

[0023] S102: Acquire the field terminal status records collected by the warehouse terminal, vehicle terminal, and equipment controller respectively, and extract the resource number, field collection time, physical status, and available quantity from each field terminal status record. The warehouse terminal collects the warehouse location of the inventory batch, the on-site inventory quantity, and the outbound availability status. The vehicle terminal collects the vehicle's current location, sensor load capacity, vehicle operating status, and transport availability status. The equipment controller collects the processing equipment time period, work order remaining time, equipment release status, and processing execution status. The field terminal status records are entered into the field status view via the terminal interface. The field status view associates the physical status, location field, capacity field, and collection source field with the resource number.

[0024] The on-site status view performs validity checks on the collected records. If the collection time is missing, the resource number cannot be parsed, the physical status does not match the terminal type, or the available quantity field cannot be identified by business rules, the corresponding record is marked as pending on-site review. When there are conflicts between records with the same resource number generated by warehouse terminals, vehicle terminals, and equipment controllers, the matching source record is retained according to the correspondence between terminal type and resource type. Records from non-matching sources are written to the on-site anomaly log, which is then transmitted to the status tracing process and is not used as the basis for generating slot capacity.

[0025] S103: Establish a matching relationship between the service chain confirmation record with the same resource number and the on-site terminal status record. When the on-chain generation time is not later than the on-site collection time and the occupancy status is consistent with the physical status, write the matching relationship into the resource status record. The matching relationship is the association object between the on-chain status view and the on-site status view, carrying the resource number, link source, terminal source, status consistency identifier, and timeliness verification identifier. The on-chain generation time is used to confirm the sequential boundary of the formation of the service chain record, and the on-site collection time is used to confirm the boundary of the on-site physical status entering the configuration process. The consistency between the occupancy status and the physical status indicates that there is no conflict between the on-chain resource occupancy result and the on-site available status.

[0026] Before writing the matching relationship into the resource status record, a timeliness check is performed. The round-trip time of the confirmation records continuously returned by the cross-chain gateway in the current configuration calculation according to the preset sampling rounds is written to the gateway's timeliness cache. The gateway's timeliness cache selects the longest round-trip record that covers the interface fluctuation boundary of the current round as the record's validity period field. The interval between the on-chain generation time and the on-site collection time is identified by the timeliness check process. When the interval exceeds the record's validity period field, the matching relationship is deleted and written to the expired status log. When the interval is within the coverage range of the record's validity period field, the matching relationship is retained and written to the resource status record. The expired status log feeds back the resource number, link source, and terminal source to the cross-chain gateway's re-retrieval process and the terminal's re-collection process, enabling subsequent rounds to re-acquire the on-chain and on-site status of the same resource.

[0027] S2: Based on the inventory batches, vehicle capacity, and processing equipment time periods in the resource status records, compare the on-chain quantity with the on-site quantity, the remaining book load capacity with the sensor load capacity, and the equipment release time with the delivery deadline to determine the resource time window slot. The resource time window slot is a candidate resource that can be invoked by the order demand record, carrying the resource number, resource type, slot start time, slot end time, slot location, slot capacity, on-chain occupancy status, and on-site availability status. The slot location is derived from the warehouse location, current vehicle location, loading location, unloading location, processing equipment location, or delivery location. The slot capacity is derived from the range of resources that can be accommodated after confirmation by the on-chain resource field and the on-site resource field.

[0028] The resource slot determination process takes resource status records as input, writing inventory batches, vehicle capacity, and processing equipment time periods into the inventory slot candidate set, vehicle slot candidate set, and processing slot candidate set, respectively. If a resource status record has an on-chain pending verification, on-site pending review, expired status, or status conflict flag, the corresponding resource will not enter the slot candidate set, and the resource number, anomaly flag, and anomaly source will be written into the slot exclusion log. The slot exclusion log is transmitted to the voucher scheduling process to prevent abnormal resources from generating on-chain occupancy vouchers.

[0029] S201: For each inventory batch, obtain the on-chain quantity, the occupied quantity, and the on-site quantity. Subtract the occupied quantity from the on-chain quantity to obtain the on-chain configurable quantity. Compare the on-chain configurable quantity with the on-site quantity, and determine the smaller of the two as the inventory slot capacity. The on-chain quantity and the occupied quantity are derived from the resource content field returned by the inventory business chain, the on-site quantity is derived from the warehouse terminal status record, and the inventory slot capacity is written into the inventory slot candidate set and bound to the warehouse location of the inventory batch.

[0030] The capacity of inventory slots is determined by the combined constraints of the configurable quantity on the blockchain and the quantity on-site. When the configurable quantity on the blockchain is less than the quantity on-site, the configurable quantity on the blockchain is used as the configurable boundary, indicating that the inventory available for pre-occupancy on the blockchain does not cover all on-site inventory. When the quantity on-site is less than the configurable quantity on the blockchain, the quantity on-site is used as the configurable boundary, indicating that the actual outbound inventory on-site restricts the configurable range on the blockchain. If the occupied status returned by the inventory business chain is inconsistent with the outbound availability status returned by the warehouse terminal, the inventory batch is written to the inventory conflict queue. The inventory conflict queue is fed back to the status verification process for re-matching, and no inventory slots are provided to consecutive task segments.

[0031] S202: For vehicle capacity, obtain the remaining load capacity on the books and the sensor load capacity. Compare the remaining load capacity on the books and the sensor load capacity, and determine the smaller of the two as the vehicle slot capacity. The remaining load capacity on the books comes from the resource content field of the vehicle's transport resources in the transportation business chain, and the sensor load capacity comes from the load sensing field collected by the vehicle terminal. The vehicle slot capacity is bound to the vehicle's current location, loading location, unloading location, and vehicle operating status and then written into the vehicle slot candidate set.

[0032] Determining vehicle slot capacity ensures that the on-chain transport capacity and the on-site vehicle loading status are subject to the same constraints. The remaining load capacity on the books is constrained by the on-chain transport occupancy status, while the sensored load capacity is constrained by the actual on-site vehicle loading status. A comparison of these two factors retains the transport capacity that can be jointly confirmed by the on-chain and on-site systems. If a vehicle terminal returns a missing location, the vehicle's operating status conflicts with the transport business chain's occupancy status, or the vehicle cannot enter a loading location, the vehicle's capacity is written into a vehicle unacceptable queue. This queue records the vehicle number, the source of the anomaly, and the location status, and prevents the corresponding vehicle from entering a pre-occupied slot combination.

[0033] S203: For processing equipment time periods, obtain the remaining time of the work order collected by the equipment controller and the delivery deadline returned by the processing business chain. Accumulate the remaining time of the processing order to determine the equipment release time. When the equipment release time is not later than the delivery deadline, determine the processing slot time and generate the resource time window slot. The remaining time of the work order comes from the equipment controller's collection result of the current work order status. The delivery deadline comes from the delivery constraint field between the processing business chain and the order business chain. The equipment release time is used to represent the time boundary for the processing equipment to enter the state of being able to receive new processing tasks from the current work order status.

[0034] After the processing slot time is generated, it is written into the processing slot candidate set along with the processing equipment location, processing requirements, equipment release status, and on-chain occupancy status. If the equipment release time is later than the delivery deadline, the processing equipment time period is marked as delivery not accepted. The delivery not accepted flag is passed to the continuous task segment determination process, preventing the processing equipment from participating in the processing execution segment of the corresponding order. If the equipment controller returns a missing remaining time for the work order or the processing business chain does not return a delivery deadline, the processing equipment time period enters the processing completion queue. The completion queue feeds back the resource number and missing field name to the equipment controller acquisition process and the processing business chain query process.

[0035] S204: Determine the time boundary of the resource time window slot when it is generated. Obtain the session generation time, resource availability start time, and resource availability end time calculated in this round of configuration. Determine the first resource availability start time that is later than the session generation time as the slot start time. Sequentially add the slot start time to the outbound operation time, vehicle arrival time, or processing execution time to obtain the slot end time. When the slot end time is not later than the resource availability end time, write the resource number, slot start time, slot end time, and slot capacity into the resource time window slot.

[0036] The session generation time is derived from the session field written during the configuration process. The resource availability start time and resource availability end time are derived from the on-chain occupancy status, on-site availability status, and business rule table in the resource status record. The outbound operation time, vehicle arrival time, and processing execution time are derived from the configuration fields of the warehousing operation rules, path access rules, and processing technology rules. The configuration fields are stored in the rule base and retrieved according to resource type. If the slot end time is later than the resource availability end time, the resource time window slot is marked as out of time. The time out of time flag is passed to the pre-occupied slot combination filtering process to prevent resources with open time boundaries from participating in task acceptance.

[0037] S3: Based on order demand records and resource time window slots, determine continuous task segments. For adjacent task segments where there are time, space, and capacity connections and no on-chain resource time window slots, determine the combinations of slots that can be pre-occupied. Order demand records are demand data objects returned from the order business chain and confirmed through the status verification process, carrying material category, order quantity, starting warehouse, processing requirements, delivery location, and delivery deadline. Continuous task segments are task structures generated according to the supply chain business acceptance sequence, carrying task segment name, resource demand type, task start time, task end time, task location, task quantity, and on-chain occupancy constraints.

[0038] Before consecutive task segments are determined, the order requirement records undergo field integrity verification. If the material category cannot match the inventory batch, the starting warehouse is missing, the processing requirements lack equipment compatibility fields, or the delivery location cannot be identified by path rules, the order requirement record is written to the order pending verification queue. The pending verification queue reports the missing fields and verification status to the order business chain. Order requirement records with complete fields enter the task segment generation process and establish candidate relationships with resource time window slots based on resource type, location, and capacity.

[0039] S301: Retrieve the material category, order quantity, originating warehouse, processing requirements, delivery location, and delivery deadline from the order demand record. Compare the order quantity with the inventory slot capacity in the resource time window slots and select an inventory slot capable of accepting the order quantity. The material category is used to match the resource content field of the inventory batch, the originating warehouse is used to match the inventory slot location, the processing requirements are used to match the processing equipment capacity field, and the delivery location is used to match the vehicle route and finished product delivery location. The comparison result between the order quantity and the inventory slot capacity forms an inventory acceptance identifier, which is written to the inventory occupancy segment of the continuous task segment.

[0040] After an inventory slot is selected, the inventory occupancy segment outputs the inventory batch, starting warehouse, slot start time, slot end time, and slot capacity to the warehouse outbound segment. If several inventory slots can accommodate the order quantity for the same order request record, the inventory slot that meets the task connection conditions in terms of starting warehouse location, outbound time boundary, and on-chain unoccupied state is retained as a candidate. If no inventory slot can accommodate the order quantity, the order request record is marked as unacceptable inventory, and this unacceptable inventory flag is passed to the document scheduling process, preventing the generation of the corresponding on-chain occupancy document for that order.

[0041] S302: Based on the selected warehouse location of the inventory slot, the location of the processing equipment corresponding to the processing requirements, and the delivery location, generate continuous task segments according to the business acceptance sequence of inventory occupancy, warehouse outbound, vehicle transportation, route passage, processing execution, and finished product delivery. The inventory occupancy segment accepts the inventory slots; the warehouse outbound segment accepts the outbound operation time; the vehicle transportation segment accepts the vehicle slot capacity and the current vehicle location; the route passage segment accepts the loading location, unloading location, and route passage rules; the processing execution segment accepts the processing equipment time period and processing requirements; and the finished product delivery segment accepts the delivery location and delivery deadline.

[0042] When consecutive task segments are generated, the end position, end time, and task quantity of the previous task segment become the input constraints for the next task segment. A spatial connection identifier is formed when the end position of the warehouse outbound segment coincides with the loading position of the vehicle transport segment. A time connection identifier is formed when the end time of the vehicle transport segment is not later than the receiving time of the processing execution segment. A capacity acceptance identifier is formed when the processing execution segment accepts a quantity not less than the task quantity. If any connection identifier is missing, the corresponding consecutive task segment is written to the task breakpoint queue. The task breakpoint queue records the breakpoint position, breakpoint type, and associated resource number for resource time window slot re-selection.

[0043] S303: For each task segment in a continuous task segment, select candidate slots from the resource time window slots whose resource type matches the resource requirements of the task segment. Compare the slot start time, slot end time, slot position, and slot capacity of the candidate slots with the start time, end time, position, and quantity of the corresponding task segment. The resource types of the candidate slots include inventory batches, vehicle capacity, and processing equipment time periods. The resource requirements of the task segment are written in the continuous task segment generation process. The comparison process is executed in the order of time boundary, position connection, capacity acceptance, and on-chain occupancy status. If the previous condition is not met, the next condition is not considered.

[0044] When a candidate slot corresponding to an adjacent task segment meets the following criteria: time continuity, location reachability, capacity not less than the number of task segments, and on-chain occupancy status is unoccupied, the candidate slot is written into the pre-occupiable slot combination. The pre-occupiable slot combination is a combined data object composed of inventory slots, vehicle slots, route access constraints, and processing slots, carrying a combination identifier, resource number set, occupancy time interval, occupancy capacity, task segment connection identifier, and on-chain unoccupied identifier. If a candidate slot meets the capacity requirement but is not location reachable, it is written into the location unreachable queue. If a candidate slot meets the location reachability requirement but has a time boundary break, it is written into the time uncontinuity queue. All of these queues are fed back to the slot selection process as a basis for excluding subsequent combinations.

[0045] S4: Based on the available slot combinations, the pre-occupancy configuration strategy is determined by sorting the resource idle time, vehicle empty driving distance, processing waiting time, and cross-chain confirmation count. An on-chain occupancy certificate is generated. When the resource number, occupancy time interval, and occupancy capacity returned by the business chains of two different supply chains are consistent with the on-chain occupancy certificate, warehouse outbound, vehicle transport, route travel, and processing scheduling instructions are generated. The pre-occupancy configuration strategy is a strategy data object selected from the available slot combinations and prepared for on-chain pre-occupancy. It carries the combination identifier, sorting field, resource number set, occupancy time interval, occupancy capacity, business chain confirmation path, and scheduling instruction template. The on-chain occupancy certificate is a stored evidence object submitted to the business chain for resource occupancy confirmation, carrying the resource number, order identifier, occupancy time interval, occupancy capacity, business chain source identifier, and certificate status.

[0046] Before sorting available slot combinations during the credential scheduling process, it is first confirmed that all resources in the combination have an on-chain unoccupied status, an on-site available status, and a task segment connection status. If any resource experiences an on-chain status update, an on-site status change, or a slot timeout, the combination is marked as pre-occupancy invalid. The pre-occupancy invalidation flag is written to the combination status log and fed back to the resource status record update process. The combination status log is used to record the status changes of a combination entering the sorting process, being excluded, submitting credentials, and receiving confirmation, forming a traceability link in the scheduling process.

[0047] S401: Obtain the resource idle time, vehicle empty driving distance, processing waiting time, and cross-chain confirmation count between the two supply chains for each slot combination in the available slot combinations. Sort the slot combinations in ascending order, using resource idle time as the first sorting item, vehicle empty driving distance as the second sorting item, processing waiting time as the third sorting item, and cross-chain confirmation count as the last sorting item. If the values ​​of any sorting item are different, retain the slot combination with the highest sorting value. If the values ​​of any sorting item are the same, continue to compare the next sorting item and select the slot combination with the highest sorting value to generate the pre-allocation configuration strategy.

[0048] Resource idle time is a waiting field between the start time of the resource time window slot and the start time of the corresponding task segment, derived from the slot time boundary and continuous task segment time boundary in the pre-occupied slot combination. Vehicle empty driving distance is the empty driving distance obtained by sequentially connecting the vehicle's current position, loading position, and unloading position, and then subtracting the driving path while carrying cargo, derived from the vehicle terminal position field and path passage rules. Processing waiting time is a waiting field between the processing equipment release time and the vehicle arrival time at the production line, derived from the processing slot time and the end time of the route passage segment. Cross-chain confirmation count is the confirmation round field corresponding to the number of business chains involved in the same slot combination, derived from the business chain source identifier associated with the resource number in the combination. All the above sorting fields are written to the strategy sorting cache, which is called by the voucher scheduling process and is not written to the field terminal.

[0049] The sorting is performed in a fixed order, with the resource idle time sorting field first used to distinguish the waiting status of combined resources. If the sorting results are the same, the vehicle empty driving distance sorting field is used to distinguish the empty driving status of the transport route. If they are still the same, the processing waiting time sorting field is used to distinguish the production line waiting status. If they are still the same, the cross-chain confirmation count sorting field is used to distinguish the cross-chain confirmation link occupancy status. If a sorting field is missing, the corresponding combination is written to the sorting completion queue. The completion queue requests the missing field from the resource time window slot, continuous task segment, and cross-chain gateway, respectively, and does not participate in the generation of the pre-occupancy configuration strategy in this round.

[0050] S402: Generate an on-chain occupancy certificate according to the pre-occupancy configuration strategy, and submit the on-chain occupancy certificate to the business chain associated with the resource number in the order business chain, inventory business chain, transportation business chain, processing business chain, and funds business chain. After the business chain returns a confirmation record, extract the resource number, occupancy time range, and occupancy capacity, and check them item by item against the corresponding fields in the on-chain occupancy certificate. If the resource number, occupancy time range, and occupancy capacity are consistent, write the certificate status as "occupancy confirmed" and generate warehouse outbound, vehicle transportation, route travel, and processing scheduling instructions. If any of the checked fields are inconsistent, write the certificate status as "occupancy conflict" and write the conflicting resource number, conflicting fields, and return link source to the certificate conflict queue.

[0051] Warehouse outbound instructions, carrying the inventory batch, starting warehouse, outbound time boundary, and outbound capacity, are transmitted to the warehouse terminal for outbound preparation. Vehicle transport instructions, carrying the vehicle number, loading location, unloading location, transport capacity, and transport time boundary, are transmitted to the vehicle terminal for transport confirmation. Route travel instructions, carrying the vehicle's travel path, loading location, unloading location, and traffic status, are transmitted to the vehicle terminal and route scheduling interface. Processing scheduling instructions, carrying the processing equipment number, processing requirements, processing slot time, and processing capacity, are transmitted to the equipment controller for scheduling write. If any instruction is not confirmed by the receiver, the corresponding instruction is written to the instruction pending confirmation queue. The pending confirmation queue resends the instruction status query to the receiver and prevents the same resource number from being invoked by a new pre-allocation configuration strategy before confirmation is completed.

[0052] S403: On-chain occupancy vouchers, business chain return confirmation records, warehouse outbound instructions, vehicle transportation instructions, route driving instructions, and processing scheduling instructions are all written to the scheduling traceability record. The scheduling traceability record is a process evidence object established around the order identifier, carrying resource number, business chain source, terminal source, voucher status, instruction status, exception identifier, and status update time fields. The status update time field originates from internal status changes during business chain return, terminal confirmation, and configuration processes, and access permissions are jointly constrained by the business rules of the order business chain and the funds business chain.

[0053] The scheduling traceability record receives status feedback from the voucher conflict queue, instruction pending confirmation queue, task breakpoint queue, and slot exclusion log, and writes the feedback results to the configuration status of the order requirement record. Configuration statuses include pending verification, unacceptable, pre-occupancy invalid, occupancy conflict, instruction pending confirmation, and scheduling confirmed. The scheduling confirmed status is triggered jointly by the business chain confirmation record and the terminal instruction confirmation. After entering this status, the corresponding resource number in the resource status record is updated to "occupied on the chain" and "scheduled on-site." The updated resource status record serves as input for subsequent configuration processes, ensuring that the same resource does not repeatedly enter the resource time window slot before being released.

[0054] The cross-chain collaborative supply chain resource global configuration optimization system, in conjunction with the aforementioned methods, includes a status verification module, a resource orchestration module, a task acceptance module, and a voucher scheduling module. The status verification module handles the acquisition of business chain confirmation records, on-site terminal status records, resource number matching, and timeliness verification (S1) mentioned above. Its input interfaces connect to the cross-chain gateway, warehouse terminal, vehicle terminal, and equipment controller, and it outputs resource status records, anomaly queues, status traceability logs, and expired status logs. The resource orchestration module handles the determination of inventory slot capacity, vehicle slot capacity, processing slot time, and slot time boundary (S2) mentioned above. It inputs resource status records and rule base fields, and outputs resource time window slots, slot exclusion logs, and candidate set statuses.

[0055] The task acceptance module handles the order demand record verification, inventory slot selection, continuous task segment generation, and pre-occupied slot combination filtering functions described in S3 above. It inputs order demand records, resource time window slots, and path access rules, and outputs continuous task segments, pre-occupied slot combinations, task breakpoint queues, unreachable location queues, and unacceptable time queues. The voucher scheduling module handles the sorting field acquisition, pre-occupied configuration strategy determination, on-chain occupancy voucher generation, business chain return verification, and scheduling instruction output functions described in S4 above. It inputs pre-occupied slot combinations, cross-chain gateway return records, and terminal confirmation status, and outputs on-chain occupancy vouchers, warehouse outbound instructions, vehicle transport instructions, route travel instructions, processing scheduling instructions, and scheduling traceability records.

[0056] The status verification module does not directly generate scheduling instructions, the resource orchestration module does not directly rewrite the business chain occupancy status, the task acceptance module does not directly submit on-chain occupancy vouchers, and the voucher scheduling module does not directly collect the status of on-site terminals. The modules communicate using resource status records, resource time window slots, continuous task segments, pre-occupied slot combinations, pre-occupied configuration strategies, and on-chain occupancy vouchers as the transmission objects. Each object, after field verification, becomes the input for the next. When the cross-chain gateway interface is abnormal, the terminal interface is abnormal, rule base fields are missing, or scheduling instructions are not confirmed, the system writes the abnormal status to the corresponding log or queue. The module corresponding to the source of the abnormality then retrieves, verifies, or blocks subsequent calls until the resource status, task connection, on-chain vouchers, and terminal instructions form a consistent record under the same order identifier.

[0057] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of protection of the described technical solutions.

Claims

1. A cross-chain collaborative supply chain resource global allocation optimization method, characterized in that, Includes the following steps: Obtain resource status records, which are obtained by matching business chain confirmation records belonging to two different supply chains with field terminal status records collected by warehousing terminals, vehicle terminals, and equipment controllers according to resource numbers; For the inventory batches, vehicle capacity and processing equipment time periods in the resource status records, compare the on-chain quantity with the on-site quantity, the remaining load capacity on the books with the sensor load capacity, and the equipment release time with the delivery deadline to determine the resource time window slot. Based on the order demand record and the resource time window slots, continuous task segments are determined. For adjacent task segments that have time connection, spatial connection, capacity continuity and are not occupied on the chain, the combination of reservable slots is determined. Based on the pre-occupiable slot combinations, the pre-occupancy configuration strategy is determined by sorting the resource idle time, vehicle empty driving distance, processing waiting time, and cross-chain confirmation number. An on-chain occupancy certificate is generated. When the resource number, occupancy time interval, and occupancy capacity returned by the business chains of the two different supply chains are consistent with the on-chain occupancy certificate, warehouse outbound, vehicle transportation, route driving, and processing scheduling instructions are generated.

2. The cross-chain collaborative supply chain resource global allocation optimization method according to claim 1, characterized in that, The process of obtaining the resource status record is as follows: Obtain the business chain confirmation records returned by the order business chain, inventory business chain, transportation business chain, processing business chain and capital business chain respectively contained in the first supply chain and the second supply chain, and extract the resource number, on-chain generation time, occupation status and resource content fields from each business chain confirmation record; Acquire the status records of the field terminals collected by the warehouse terminal, vehicle terminal and equipment controller respectively, and extract the resource number, field collection time, physical status and available quantity from each field terminal status record; Establish a matching relationship between the business chain confirmation record with the same resource number and the field terminal status record. When the generation time on the chain is not later than the field collection time and the occupancy status is consistent with the physical status, write the matching relationship into the resource status record.

3. The cross-chain collaborative supply chain resource global allocation optimization method according to claim 2, characterized in that, Before the matching relationship is written into the resource status record, a timeliness check is performed. The timeliness check specifically involves: The round-trip time of the cross-chain gateway connecting the first supply chain and the second supply chain is obtained for three consecutive confirmation records returned in this round of configuration calculation. The maximum value among the three round-trip times is determined as the record validity period. The time interval between the on-chain generation time and the on-site collection time is calculated. When the time interval exceeds the validity period of the record, the matching relationship is deleted. When the time interval does not exceed the validity period of the record, the matching relationship is retained.

4. The cross-chain collaborative supply chain resource global allocation optimization method according to claim 1, characterized in that, The process of determining the resource time window slot is as follows: For the inventory batch, obtain the on-chain quantity, the occupied quantity, and the on-site quantity. Subtract the occupied quantity from the on-chain quantity to obtain the on-chain configurable quantity. Compare the on-chain configurable quantity with the on-site quantity. Determine the smaller of the on-chain configurable quantity and the on-site quantity as the inventory slot capacity. For the vehicle's carrying capacity, the remaining load capacity on the books and the sensing load capacity are obtained. The remaining load capacity on the books and the sensing load capacity are compared, and the load capacity of the smaller of the remaining load capacity on the books and the sensing load capacity is determined as the vehicle's slot capacity. For the processing equipment time period, the remaining time of the work order collected by the equipment controller and the delivery deadline returned by the processing business chain are obtained. The remaining time of the processing order is accumulated to determine the equipment release time. When the equipment release time is not later than the delivery deadline, the processing slot time is determined, and the resource time window slot is generated.

5. The cross-chain collaborative supply chain resource global allocation optimization method according to claim 4, characterized in that, When generating the resource time window slot, the time boundary of the slot is also determined. The specific process for determining the time boundary of the slot is as follows: Obtain the session generation time, resource availability start time, and resource availability end time of this round of configuration calculation. Determine the first resource availability start time that is later than the session generation time as the slot start time. Then, sequentially add the slot start time to the outbound operation time, vehicle arrival time, or processing execution time to obtain the slot end time. When the slot end time is not later than the resource availability end time, the resource number, slot start time, slot end time, and slot capacity are written into the resource time window slot.

6. The cross-chain collaborative supply chain resource global allocation optimization method according to claim 1, characterized in that, The process of determining the continuous task segments is as follows: Obtain the material category, order quantity, starting warehouse, processing requirements, delivery location, and delivery deadline from the order demand record; compare the order quantity with the inventory slot capacity in the resource time window slot; and select an inventory slot that can accommodate the order quantity. Based on the warehouse location of the selected inventory slot, the location of the processing equipment corresponding to the processing requirements, and the delivery location, the continuous task segments are generated in the order of business acceptance: inventory occupancy, warehouse outbound, vehicle transportation, route passage, processing execution, and finished product delivery.

7. The cross-chain collaborative supply chain resource global allocation optimization method according to claim 1, characterized in that, The process for determining the pre-occupied slot combination is as follows: For each task segment in the continuous task segment, a candidate slot with a resource type that matches the resource requirements of the task segment is selected from the resource time window slots, and the slot start time, slot end time, slot position, and slot capacity of the candidate slot are compared with the start time, end time, position, and quantity of the corresponding task segment. When the candidate slots corresponding to adjacent task segments meet the requirements of being sequential in time, reachable in location, having a capacity not less than the number of task segments, and being unoccupied on the chain, the candidate slots are written into the pre-occupied slot combination.

8. The cross-chain collaborative supply chain resource global allocation optimization method according to claim 1, characterized in that, The process of determining the pre-occupancy configuration strategy is as follows: The idle time of resources, empty driving distance of vehicles, processing waiting time and number of cross-chain confirmations between two supply chains are obtained for each slot combination in the pre-occupied slot combination. The idle time of resources is used as the first sorting item, the empty driving distance of vehicles as the second sorting item, the processing waiting time as the third sorting item, and the number of cross-chain confirmations as the last sorting item. The slot combinations are sorted in ascending order. When the values ​​of any sorting item are different, the slot combination with the higher ranking is retained. When the values ​​of any sorting item are the same, the next sorting item is compared. The slot combination with the highest ranking is selected to generate the pre-occupancy configuration strategy.

9. The cross-chain collaborative supply chain resource global allocation optimization method according to claim 8, characterized in that, The process of obtaining resource idle time, vehicle idling distance, processing waiting time, and cross-chain confirmation count is as follows: The resource idle time is obtained by calculating the difference between the start time of each resource time window slot in the pre-occupied slot combination and the start time of the corresponding task segment. The vehicle's current location, loading location, and unloading location are connected sequentially to obtain the vehicle's driving path. The vehicle's empty driving distance is obtained by subtracting the driving distance under the condition of carrying cargo from the vehicle's driving path. The processing waiting time is obtained by calculating the difference between the release time of the processing equipment and the arrival time of the vehicle at the production line. The number of business chains that cross the first and second supply chains involved in the same slot combination is counted to obtain the number of cross-chain confirmations.

10. A cross-chain collaborative supply chain resource global allocation optimization system, characterized in that, The system is used to implement the cross-chain collaborative supply chain resource global allocation optimization method according to any one of claims 1-9, and the system includes: The status verification module acquires resource status records, which are obtained by matching the business chain confirmation records belonging to two different supply chains with the on-site terminal status records collected by the warehousing terminal, vehicle terminal, and equipment controller according to the resource number. The resource orchestration module compares the on-chain quantity with the on-site quantity, the remaining load capacity on the books with the sensor load capacity, and the equipment release time with the delivery deadline in the resource status record for the inventory batches, vehicle capacity and processing equipment time periods to determine the resource time window slots. The task receiving module determines consecutive task segments based on order demand records and the resource time window slots. For adjacent task segments that have time connection, space connection, capacity connection and are not occupied on the chain, the module determines the combination of reservable slots. The voucher scheduling module determines the pre-occupancy configuration strategy based on the pre-occupiable slot combination, sorting by resource idle time, vehicle empty driving distance, processing waiting time, and cross-chain confirmation count. It generates on-chain occupancy vouchers. When the resource number, occupancy time interval, and occupancy capacity returned by the business chains of the two different supply chains are consistent with the on-chain occupancy vouchers, it generates warehouse outbound, vehicle transportation, route driving, and processing scheduling instructions.

Images