Intelligent consumable fine access control method based on edge computing

Abstract

The application relates to the technical field of edge computing, in particular to an intelligent consumable fine access control method based on edge computing, which comprises the following steps: receiving consumable categories, batches, stock quantities, storage space states and returned quantities through edge computing nodes on the side of an intelligent consumable cabinet, receiving application for taking and obtaining use frequency and replenishment cycle, reading real-time stock, minimum safe stock, expiration date and permission records in a stock account, determining the number of consumables that can be taken and target storage spaces, generating taking, returning, inventory or replenishment tasks, comparing actual quantities with task quantities after access is completed and updating records. In the application, cabinet-side collection, stock constraints, storage space control, task association and quantity verification are continuously processed, consumable access feedback enters the updating condition of a stock account and consumable circulation record, and replenishment priority is corresponded with real-time stock, minimum safe stock, use frequency, replenishment cycle and expiration date.

Description

Technical Field

[0001] This invention relates to the field of edge computing technology, and in particular to a refined access control method for intelligent consumables based on edge computing. Background Technology

[0002] Edge computing technology involves data acquisition, on-site computation, rule invocation, local storage, and network synchronization close to terminal devices. It typically involves collaboration between terminal sensors, embedded processors, memory, interface programs, and backend servers based on device status, business requests, timestamps, and data table fields. Traditional edge computing-based intelligent consumables refined access control methods refer to the process of accessing consumable cabinets in hospitals, laboratories, and production sites. Electronic tag readers, barcode scanners, weight sensors, or location detectors obtain consumable category, batch, inventory quantity, location status, and return quantity. They receive requisition requests and, based on consumable circulation records or replenishment configurations, obtain usage frequency and replenishment cycles. The local processor reads inventory ledgers, permission records, minimum safety stock, and expiration date fields to generate requisition, return, inventory, or replenishment tasks. Cabinet door locks or location locks are used as execution targets, and after access, the task quantity is compared with the actual quantity and written to the inventory ledger and consumable circulation records.

[0003] Traditional consumable cabinet storage and retrieval processes mainly rely on single cabinet opening records and inventory deductions. Consumable categories, batches, location status, requisition applications, returned quantities, usage frequency, and replenishment cycles are scattered and entered into local ledgers or back-end systems. The edge side lacks sufficient processing of the correlation between minimum safety stock, expiration date, task quantity, and actual quantity. When multiple batches and multiple locations coexist, the selection of target locations and replenishment order depend on the individual inventory status, which can easily lead to a lag between the ledger records and the cabinet-side storage and retrieval feedback. It is also difficult to continuously correspond consumable circulation records with inventory counts and replenishment tasks. Summary of the Invention

[0004] The purpose of this invention is to provide a refined access control method for intelligent consumables based on edge computing. This method is used to locally collect information on consumable categories, batches, inventory quantities, storage location status, and returned quantities at the intelligent consumable cabinet side, receive requisition requests, acquire usage frequency and replenishment cycle, and perform correlation judgment and task control on the above data. This enables the consumable requisition, return, inventory, and replenishment processes to form a continuous processing flow corresponding to the inventory ledger and consumable circulation records at the edge side.

[0005] To achieve the above objectives, the present invention provides a method for refined access control of intelligent consumables based on edge computing, comprising the following steps: On the smart consumable cabinet side, edge computing nodes receive data from consumable identification devices, location detection devices, and quantity detection devices, which collect data on consumable categories, batches, inventory quantities, location status, and returned quantities. The system also receives requisition requests and obtains usage frequency and replenishment cycles. The edge computing node reads the real-time inventory, minimum safety stock, expiration date and permission records from the inventory ledger. When the application for requisition meets the permission records and there is still valid inventory after deducting the minimum safety stock from the real-time inventory, the requisition quantity is determined. When the conditions are not met, a rejection or pending review task is generated. Candidate storage locations are selected based on the batch, the expiration date, the storage location status, and the inventory quantity. The storage locations that meet the available quantity and the expiration date meet the preset conditions are determined as target storage locations. The cabinet door lock or storage location lock corresponding to the target storage location is then controlled to open. Generate requisition tasks, return tasks, inventory tasks, or replenishment tasks, associate tasks with the consumable category, batch, target storage location, task quantity, and execution status, and determine replenishment priority based on the real-time inventory, minimum safety stock, usage frequency, replenishment cycle, and expiration date; After the storage and retrieval are completed, the actual quantity is compared with the task quantity. When the quantity deviation does not exceed the preset deviation threshold, the inventory ledger and consumable circulation record are updated. When the quantity deviation exceeds the preset deviation threshold, an abnormal review task is generated.

[0006] Furthermore, the edge computing node receives the consumable category and batch number collected by the consumable identification device, the storage location status collected by the storage location detection device, and the inventory quantity and returned quantity collected by the quantity detection device, and writes the consumable category, batch number, inventory quantity, storage location status and returned quantity corresponding to the same collection time or the same access task into the same cabinet-side data record; When the correspondence between the consumable category and the batch, the correspondence between the batch and the storage location status, or the correspondence between the inventory quantity and the returned quantity and the same storage and retrieval task is not established in the same cabinet-side data record, the edge computing node marks the same cabinet-side data record as a record to be reviewed and suspends the participation of the same cabinet-side data record in the determination of the available quantity and target storage location.

[0007] Furthermore, the process by which the edge computing node obtains the usage frequency and the replenishment cycle includes: Read the completed requisition, return and replenishment tasks in the consumable circulation record according to the consumable category and batch, determine the usage frequency by the number of requisition tasks or the number of requisition tasks within the preset statistical time window, and read the replenishment configuration record or replenishment task completion record corresponding to the same consumable category to determine the replenishment cycle. When both replenishment configuration records and replenishment task completion records exist, the replenishment configuration records are used as the priority source for the replenishment cycle. When the replenishment configuration records do not exist, the replenishment cycle is determined by the interval between the completion times of two adjacent replenishment tasks.

[0008] Furthermore, the process by which the edge computing node determines the available quantity includes: The permission record is read according to the user identity, consumable category and application quantity in the requisition application. When there is a requisition permission in the permission record that matches the user identity and consumable category, the inventory quantity that meets the validity period is used as the inventory quantity that can participate in the requisition judgment. The quantity of inventory eligible for requisition is compared with the minimum safety stock. When the quantity of inventory eligible for requisition is greater than the minimum safety stock, the quantity eligible for requisition is determined according to the smaller value between the application quantity and the portion of the quantity of inventory eligible for requisition that exceeds the minimum safety stock. When the quantity of inventory eligible for requisition is not greater than the minimum safety stock, a rejection or pending review task is generated.

[0009] Furthermore, before determining the available quantity, the edge computing node also performs a validity check on the inventory quantity eligible for requisition. This validity check includes: Compare the expiration dates of each batch under the corresponding consumable category with the current time, and remove the inventory quantity corresponding to the batches whose expiration dates do not meet the preset expiration date conditions; Compare the location status of the remaining batches with the available location status, and remove the inventory quantity whose location status does not meet the requirements for available location status. The inventory quantity after rejection is used as the inventory quantity that can be used for the decision after validity verification, and is used to determine the quantity that can be used.

[0010] Furthermore, the process by which the edge computing node filters the candidate storage locations includes: According to the consumable category corresponding to the requisition application, read the list of storage locations associated with the same consumable category, match the batches corresponding to each storage location with the batch records under the same consumable category, and remove storage locations whose batches do not belong to the batch records under the same consumable category. The validity period is compared with the preset validity period conditions, and the storage locations whose validity periods do not meet the preset validity period conditions are eliminated; The storage location status is compared with the available storage location status, and storage locations whose status does not meet the requirements of the available storage location status are removed. The remaining storage spaces will be used as candidate storage spaces.

[0011] Furthermore, the process of determining the target storage location includes: Based on the fact that all candidate storage locations have met the preset validity period conditions, the inventory quantity corresponding to each candidate storage location is read, and the candidate storage locations with an inventory quantity not less than the available quantity are taken as the first candidate set. When the first candidate set is empty, a rejection or pending review task is generated; When the first candidate set is not empty, the candidate locations are sorted in order of validity period from earliest to latest, and the candidate locations with the highest validity period are selected as the second candidate set. If a single candidate location exists in the second candidate set, that single candidate location will be designated as the target location. When there are multiple candidate locations in the second candidate set, the target location is determined from the multiple candidate locations according to the location status update time.

[0012] Furthermore, the process of determining the target storage location from multiple candidate storage locations based on the storage location status update time includes: Read the location status update time and the most recent access completion time for each of the multiple candidate locations in the second candidate set; When the location status update time of multiple candidate locations in the second candidate set is later than the most recent access completion time, the candidate location whose location status update time is closest to the current time is determined as the target location. When there are candidate storage locations whose status update time is no later than the most recent access completion time, remove the candidate storage location whose status update time is no later than the most recent access completion time from the second candidate set, and re-determine the target storage location from the removed second candidate set; When the second candidate set after elimination is empty, generate a task to be reviewed and stop the opening of the control cabinet door lock or the cargo location lock.

[0013] Furthermore, the process by which the edge computing node determines the replenishment priority includes: The real-time inventory, minimum safety stock, usage frequency, replenishment cycle, and expiration date are read using the consumable category as the statistical object. When the real-time inventory is lower than the minimum safety stock, an inventory gap indicator is generated; When the real-time inventory is not lower than the minimum safety stock, a normal inventory status is generated; The cycle consumption status is determined based on the usage frequency and the replenishment cycle, and the expiration risk status is determined based on the expiration date. Write the inventory gap identifier or the normal inventory identifier, the cycle consumption status and the expiration risk status into the replenishment task record, and determine the replenishment priority according to the preset priority table.

[0014] Furthermore, the process of comparing the actual quantity with the task quantity after the access is completed includes: After the cabinet door lock or the storage location lock is closed, the edge computing node reads the number of tasks corresponding to the same task and the actual number fed back by the quantity detection device; The absolute value of the difference between the actual quantity and the task quantity is taken as the quantity deviation, and the quantity deviation is compared with the preset deviation threshold. When the quantity deviation does not exceed the preset deviation threshold, the corresponding inventory increase or decrease result is written into the inventory ledger according to the task type, and the task number, consumable category, batch, target storage location, actual quantity and verification result are written into the consumable circulation record; When the quantity deviation exceeds the preset deviation threshold, the inventory change corresponding to this task is kept in the pending confirmation state, and an abnormal review task containing the task number, target location and quantity deviation is generated.

[0015] Compared with the prior art, the advantages and positive effects of the present invention are as follows: In this invention, edge computing nodes combine data collected by consumable identification devices, location detection devices, and quantity detection devices with requisition applications, usage frequency, and replenishment cycles at the counter side. Real-time inventory, minimum safety stock, expiration date, and permission records in the inventory ledger jointly participate in the determination of the requisition quantity, making the requisition result subject to dual constraints of inventory and permissions. Batch, location status, and inventory quantity participate in the candidate location screening. The target location corresponds to the cabinet door lock or location lock control. The comparison result between the task quantity and the actual quantity determines the update of the inventory ledger and consumable circulation records or the generation of anomaly review tasks, so that storage and retrieval feedback enters the ledger update conditions. Attached Figure Description

[0016] 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.

[0017] Figure 1 This is the main flowchart of the intelligent consumables refined access control of the present invention; Figure 2This is a schematic diagram illustrating the data recording and verification process on the cabinet side of the present invention. Figure 3 This is a schematic diagram illustrating the logic for determining the quantity that can be requisitioned according to the present invention; Figure 4 This is a schematic diagram of the target cargo location screening and lock control of the present invention; Figure 5 This is a schematic diagram illustrating the replenishment priority status association of the present invention; Figure 6 This is a schematic diagram illustrating the quantity verification and record update status of the present invention. Detailed Implementation

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

[0019] 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.

[0020] Please see Figure 1 This invention provides a method for refined access control of intelligent consumables based on edge computing, comprising the following steps: The following embodiments illustrate the feasible processing of the technical solutions described in this invention on the smart consumable cabinet side. In these embodiments, edge computing nodes act as the main execution entities for cabinet-side data reception, inventory constraint judgment, location screening, task generation, lock control, quantity verification, and record updating; consumable identification devices provide consumable categories and batches; location detection devices provide location status; quantity detection devices provide inventory quantity, returned quantity, and actual quantity after storage / retrieval; inventory ledgers record real-time inventory, minimum safety stock, expiration date, and access records; and consumable circulation records record completed requisition tasks, return tasks, replenishment tasks, and task verification results. The drawing numbers and S-type step numbers in these embodiments are only used to identify the process and drawing content and do not constitute additional limitations on quantity, parameters, sequence range, or protection boundaries. If there are component names with numerical labels in the drawings, their meaning should be consistent with the corresponding components in the protection scope text, drawing description, and original drawings. Component labels are only used to identify the component itself and are not used as quantity or parameter limitations; this embodiment does not add component labels to technical objects that were not assigned labels in the original disclosure materials.

[0021] Please see Figures 1 to 6This embodiment provides a refined access control method for intelligent consumables based on edge computing, applied to scenarios where the processes of consumable requisition, return, inventory, and replenishment are processed locally and in a closed loop at the intelligent consumable cabinet. This method uses data collected at the cabinet as input, and inventory ledgers and consumable circulation records as constraints and update objects. Edge computing nodes at the cabinet level complete permission checks, inventory verification, location selection, task association, and quantity verification, creating a continuous data processing link between access actions, location control, and ledger updates.

[0022] S1, the edge computing node receives data collected from the cabinet side, application for use, and obtains usage frequency and replenishment cycle.

[0023] In S1, the consumable identification device collects the consumable category and batch, the location detection device collects the location status, and the quantity detection device collects the inventory quantity and the returned quantity. After receiving the above collection results, the edge computing node writes the consumable category, batch, inventory quantity, location status, and returned quantity into the same counter-side data record according to the same collection time or the same access task. The counter-side data record is used to bind consumable objects, batch objects, location objects, and quantity objects from different collection sources as inputs for the same counter-side processing. Subsequent judgments on the available quantity and determination of the target location both use counter-side data records that are not marked as records to be reviewed as the participating objects.

[0024] Edge computing nodes verify the correspondence between data records on the same storage unit. Verification includes the correspondence between consumable categories and batches, batches and storage location status, and inventory and returned quantities and the same storage / retrieval task. If any of these correspondences are invalid, the edge computing node marks the data record as pending verification and suspends its participation in determining the available quantity and target storage location. This process prevents inconsistent or mismatched storage unit data from directly entering the inventory deduction or storage location opening process, avoiding triggering subsequent control actions with uncertain data.

[0025] Edge computing nodes receive requisition requests. These requests serve as input for subsequent permission checks and determination of the available quantity. The fields for these requests include user identity, consumable category, and requested quantity. User identity is used to match permission records, consumable category is used to determine the corresponding inventory object and storage location list, and requested quantity is used to compare with the available portion after inventory constraints. Requisition requests do not directly trigger lock opening; instead, they first proceed to the inventory ledger reading and permission record verification phase.

[0026] When edge computing nodes acquire usage frequency, they read completed requisition, return, and replenishment tasks from the consumable circulation record according to consumable category and batch. Usage frequency is determined by the number of requisition tasks or the quantity of requisition tasks within a preset statistical time window, serving as input representing the consumption status of the same consumable category within that window. This usage frequency does not independently determine lock opening; rather, it is used in conjunction with real-time inventory, minimum safety stock, replenishment cycle, and expiration date when determining subsequent replenishment priorities.

[0027] When an edge computing node obtains a replenishment cycle, it reads either the replenishment configuration record or the replenishment task completion record corresponding to the same consumable category. If both exist, the replenishment configuration record is prioritized as the source of the replenishment cycle; if no replenishment configuration record exists, the interval between two consecutive replenishment task completion times is used to determine the replenishment cycle. Therefore, the source of the replenishment cycle is limited to the replenishment configuration record and the replenishment task completion record, and subsequent replenishment priorities are not generated based on unsourced cycle data.

[0028] S2, the edge computing node reads the inventory ledger and determines the available quantity or generates rejection or pending review tasks.

[0029] In S2, edge computing nodes read the real-time inventory, minimum safety stock, expiration date, and permission records from the inventory ledger according to the user identity, consumable category, and requested quantity in the requisition application. Real-time inventory indicates the current inventory status of the corresponding consumable recorded in the inventory ledger; minimum safety stock limits the minimum inventory that must be retained after requisition; expiration date excludes batches that do not meet the preset expiration date conditions; and permission records determine whether there is a matching requisition permission between the user identity and the consumable category.

[0030] The edge computing node first determines whether the requisition application meets the requisition conditions based on the permission records. When a requisition permission matching the user's identity and consumable category exists in the permission records, the edge computing node uses the inventory quantity that meets the expiration date as the eligible inventory quantity for requisition. When no matching requisition permission exists in the permission records, the edge computing node does not enter the lock opening control and generates a rejection or pending review task. A rejection task indicates that the current requisition application does not meet the current permission constraints, while a pending review task indicates that the current requisition application or its related records require manual or subsequent process confirmation.

[0031] Before determining the available quantity, the edge computing nodes perform validity checks on the inventory quantities eligible for requisition. The edge computing nodes compare the expiration dates of each batch under the corresponding consumable category with the current time, removing the inventory quantities corresponding to batches whose expiration dates do not meet the preset expiration date conditions. Next, they compare the storage location status of the remaining batches with the available storage location status, removing the inventory quantities whose storage location status does not meet the available storage location status requirements. The remaining inventory quantities are then used as the valid inventory quantities eligible for requisition. The output of the validity check continues to the minimum safety stock comparison; inventory quantities that fail the validity check are not included in the formation of the current available quantity.

[0032] Edge computing nodes compare the inventory quantity eligible for requisition after validity verification with the minimum safety stock. When the eligible inventory quantity exceeds the minimum safety stock, the edge computing node compares the requested quantity with the portion of the eligible inventory quantity exceeding the minimum safety stock, and determines the smaller of the two as the eligible quantity. Therefore, the eligible quantity is simultaneously limited by the requested quantity, the valid inventory quantity, and the minimum safety stock, preventing requisition actions from causing real-time inventory to fall below the minimum safety stock. When the eligible inventory quantity is not greater than the minimum safety stock, the edge computing node generates a rejection or pending review task and does not proceed with opening the target storage location.

[0033] S3, the edge computing node filters candidate storage locations, determines the target storage location, and controls the lock to open.

[0034] In S3, edge computing nodes read the list of storage locations associated with the same consumable category according to the requisition application. Each storage location in the list is first matched with the batch records under the same consumable category; storage locations whose batches do not belong to the same consumable category are removed. This process ensures that storage location filtering does not solely depend on whether a storage location has inventory, but rather establishes the correspondence between consumable categories, batches, and storage locations first.

[0035] Edge computing nodes compare the expiration date of the corresponding batch for each storage location with preset expiration date conditions, eliminating locations whose expiration dates do not meet the preset conditions. They then compare the storage location status with the available storage location status, eliminating locations whose status does not meet the available storage location status requirements. The remaining storage locations serve as candidate storage locations. The formation of candidate storage locations involves sequentially matching consumable categories and batches, determining expiration dates, and determining storage location status, ensuring that subsequent target storage locations are determined only from those that match the criteria, have valid expiration dates, and are available.

[0036] Once all candidate storage locations have met the preset validity period conditions, the edge computing node reads the inventory quantity corresponding to each candidate storage location and selects those with an inventory quantity not less than the available quantity as the first candidate set. When the first candidate set is empty, it means that no single candidate storage location can meet the available quantity for this use. The edge computing node generates a rejection or pending review task and does not control the opening of the cabinet door locks or storage location locks.

[0037] When the first candidate set is not empty, the edge computing node sorts the candidate locations in the first candidate set according to their validity period from earliest to latest, and selects the candidate locations with the highest validity period as the second candidate set. When there is a single candidate location in the second candidate set, the edge computing node identifies that single candidate location as the target location. When there are multiple candidate locations in the second candidate set, the edge computing node proceeds to determine the location status update time to identify the target location.

[0038] The edge computing node reads the location status update time and the most recent access completion time for each of the multiple candidate locations in the second candidate set. When the location status update times of multiple candidate locations in the second candidate set are all later than the most recent access completion time, the edge computing node determines the candidate location with the location status update time closest to the current time as the target location. When there is a candidate location with a location status update time no later than the most recent access completion time, the edge computing node removes the candidate location with a location status update time no later than the most recent access completion time from the second candidate set and re-determines the target location from the removed second candidate set. When the removed second candidate set is empty, the edge computing node generates a task to be reviewed and stops controlling the opening of cabinet door locks or location locks.

[0039] Once the target storage location is determined, the edge computing node controls the opening of the corresponding cabinet door lock or storage location lock. Lock opening is controlled by the target storage location, with the correspondence between the available quantity and the target storage location as a prerequisite. If no target storage location is identified, the target storage location is removed, or verification is required, the edge computing node does not perform unlocking control. Thus, a traceable control chain is formed between the unlocking action and the consumable category, batch, expiration date, storage location status, inventory quantity, and available quantity.

[0040] S4, edge computing nodes generate storage and retrieval tasks and determine replenishment priorities.

[0041] In S4, edge computing nodes generate requisition, return, inventory, or replenishment tasks based on current business triggers and counter-side processing results. Task records are associated with consumable category, batch, target storage location, task quantity, and execution status. The consumable category and batch specify the task object, the target storage location specifies the counter-side execution location, the task quantity is used to verify the actual quantity after storage / retrieval, and the execution status indicates the task's status change from generation to completion or pending review. After task generation, this task becomes a common index for subsequent quantity comparisons, inventory ledger updates, and consumable flow record writing.

[0042] For requisition tasks, the task quantity comes from the confirmed available quantity or the current execution quantity corresponding to the requisition application, and the target storage location comes from the target storage location determined in S3. For return tasks, the return quantity is fed back by the quantity detection equipment and entered into the same cabinet-side data record, and the task is associated with the consumable category, batch, and target storage location. For inventory tasks, the edge computing node associates the task with the consumable category, batch, target storage location, and task quantity to be verified, so that the inventory results can be compared with the corresponding records in the inventory ledger. For replenishment tasks, the edge computing node associates the replenishment object with the consumable category, batch, and replenishment priority, so that the replenishment execution can correspond to the inventory gap, cycle consumption status, and expiration risk status.

[0043] When determining replenishment priorities, edge computing nodes retrieve real-time inventory, minimum safety stock, usage frequency, replenishment cycle, and expiration date based on consumable category. When real-time inventory falls below the minimum safety stock, the edge computing node generates an inventory gap flag; when real-time inventory is not lower than the minimum safety stock, the edge computing node generates a normal inventory flag. The inventory gap flag and the normal inventory flag are used to distinguish whether the current inventory of the same consumable category has reached the minimum safety stock constraint.

[0044] Edge computing nodes determine the periodic consumption status based on usage frequency and replenishment cycle. Usage frequency is derived from the number or quantity of requisition tasks within a preset statistical time window, while the replenishment cycle is derived from replenishment configuration records or the interval between the completion times of two adjacent replenishment tasks. The periodic consumption status characterizes the consumption pressure of the same consumable category under replenishment cycle constraints. Edge computing nodes determine the expiration date risk status based on the expiration date, ensuring that batches approaching or failing to meet preset expiration date conditions can have corresponding status expressions in the replenishment task record. Edge computing nodes write inventory shortage or normal inventory indicators, periodic consumption status, and expiration date risk status into the replenishment task record and determine the replenishment priority according to a preset priority table. The replenishment priority is not generated solely by real-time inventory, but is determined by real-time inventory, minimum safety stock, usage frequency, replenishment cycle, and expiration date all entering the same replenishment task record and then using a preset priority table.

[0045] S5. After the storage and retrieval are completed, the edge computing node compares the actual quantity with the number of tasks and updates the record or generates an anomaly review task.

[0046] In S5, once the cabinet door lock or storage location lock is closed, the edge computing node reads the task quantity corresponding to the same task and receives the actual quantity from the quantity detection device. The task quantity originates from the quantity field associated with the requisition task, return task, inventory task, or replenishment task in S4, while the actual quantity comes from the feedback from the quantity detection device after the storage / retrieval is completed. The edge computing node compares the actual quantity and the task quantity under the same task number to avoid quantity verification across tasks, storage locations, or batches.

[0047] Edge computing nodes use the absolute value of the difference between the actual quantity and the task quantity as the quantity deviation, and compare this deviation with a preset deviation threshold. When the quantity deviation does not exceed the preset threshold, the edge computing nodes write the corresponding inventory increase / decrease results into the inventory ledger according to the task type. For requisition tasks, the inventory of the corresponding consumable category, batch, and target location in the inventory ledger is reduced based on the actual quantity; for return or replenishment tasks, the corresponding record in the inventory ledger is increased based on the actual quantity; for inventory count tasks, the inventory ledger enters the corresponding record update process based on the verification results. After the inventory increase / decrease results are written into the inventory ledger, the edge computing nodes write the task number, consumable category, batch, target location, actual quantity, and verification result into the consumable circulation record. The consumable circulation record thus contains the execution object, execution location, actual quantity, and verification status of this task, for subsequent use in frequency statistics, replenishment cycle determination, and task traceability.

[0048] When the quantity deviation exceeds a preset deviation threshold, the edge computing node keeps the inventory change corresponding to this task in a pending confirmation state and generates an anomaly review task. The anomaly review task includes a task number, target storage location, and quantity deviation, allowing the review object to point back to the current storage / retrieval task, the execution location on the counter, and the inconsistent quantity status. Under this branch, the inventory ledger does not directly complete the final inventory change based on the unconfirmed actual quantity; instead, the consumables circulation record retains the task association required for anomaly review. Therefore, the actual quantity reported by the quantity detection device is not only used to update inventory but also serves as a trigger condition to prevent abnormal inventory changes.

[0049] In this embodiment, edge computing nodes continuously process the relationships between counter-side data records, inventory ledgers, consumable circulation records, and task records. Counter-side data records provide consumable categories, batches, inventory quantities, storage location status, and returned quantities; inventory ledgers provide real-time inventory, minimum safety stock, expiration dates, and access records; consumable circulation records provide completed tasks to determine usage frequency and replenishment cycles; task records carry the execution status of requisition, return, inventory, or replenishment. These records are linked by consumable category, batch, target storage location, and task number, ensuring that every access action can be traced back to input data, judgment conditions, lock control, and quantity verification results.

[0050] The specific processes, field states, judgment order, task association methods, lock control conditions, inventory update conditions, and abnormal review triggering methods described in this embodiment are used to illustrate the feasible implementation methods of the present invention. Without departing from the technical solutions described in this invention and the scope supported by the original disclosure, any equivalent substitutions, equivalent modifications, equivalent combinations, order adjustments, equivalent transformations of field names, equivalent acceptance of the executing entity, or equivalent changes in the carrier form that can be conceived by those skilled in the art should fall within the scope of protection of this patent; however, they shall not be extended to unclaimed topics, nor shall they alter the substantive correspondence of technical objects through changes in labeling. Equivalent changes shall not replace, delete, or weaken the method features, control relationships, data relationships, timing relationships, parameter relationships, and access feedback relationships necessary to achieve the technical effect.

Claims

1. A method for refined access control of intelligent consumables based on edge computing, characterized in that, Includes the following steps: On the smart consumable cabinet side, edge computing nodes receive data from consumable identification devices, location detection devices, and quantity detection devices, which collect data on consumable categories, batches, inventory quantities, location status, and returned quantities. The system also receives requisition requests and obtains usage frequency and replenishment cycles. The edge computing node reads the real-time inventory, minimum safety stock, expiration date and permission records from the inventory ledger. When the application for requisition meets the permission records and there is still valid inventory after deducting the minimum safety stock from the real-time inventory, the requisition quantity is determined. When the conditions are not met, a rejection or pending review task is generated. Candidate storage locations are selected based on the batch, the expiration date, the storage location status, and the inventory quantity. The storage locations that meet the available quantity and the expiration date meet the preset conditions are determined as target storage locations. The cabinet door lock or storage location lock corresponding to the target storage location is then controlled to open. Generate requisition tasks, return tasks, inventory tasks, or replenishment tasks, associate tasks with the consumable category, batch, target storage location, task quantity, and execution status, and determine replenishment priority based on the real-time inventory, minimum safety stock, usage frequency, replenishment cycle, and expiration date; After the storage and retrieval are completed, the actual quantity is compared with the task quantity. When the quantity deviation does not exceed the preset deviation threshold, the inventory ledger and consumable circulation record are updated. When the quantity deviation exceeds the preset deviation threshold, an abnormal review task is generated.

2. The method for refined access control of intelligent consumables based on edge computing according to claim 1, characterized in that, The edge computing node receives the consumable category and batch number collected by the consumable identification device, the storage location status collected by the storage location detection device, and the inventory quantity and returned quantity collected by the quantity detection device. It also writes the consumable category, batch number, inventory quantity, storage location status, and returned quantity corresponding to the same collection time or the same access task into the same cabinet-side data record. When the correspondence between the consumable category and the batch, the correspondence between the batch and the storage location status, or the correspondence between the inventory quantity and the returned quantity and the same storage and retrieval task is not established in the same cabinet-side data record, the edge computing node marks the same cabinet-side data record as a record to be reviewed and suspends the participation of the same cabinet-side data record in the determination of the available quantity and target storage location.

3. The method for refined access control of intelligent consumables based on edge computing according to claim 1, characterized in that, The process by which the edge computing node obtains the usage frequency and the replenishment cycle includes: Read the completed requisition, return and replenishment tasks in the consumable circulation record according to the consumable category and batch, determine the usage frequency by the number of requisition tasks or the number of requisition tasks within the preset statistical time window, and read the replenishment configuration record or replenishment task completion record corresponding to the same consumable category to determine the replenishment cycle. When both replenishment configuration records and replenishment task completion records exist, the replenishment configuration records are used as the priority source for the replenishment cycle. When the replenishment configuration records do not exist, the replenishment cycle is determined by the interval between the completion times of two adjacent replenishment tasks.

4. The method for refined access control of intelligent consumables based on edge computing according to claim 1, characterized in that, The process by which the edge computing node determines the available quantity includes: The permission record is read according to the user identity, consumable category and application quantity in the requisition application. When there is a requisition permission in the permission record that matches the user identity and consumable category, the inventory quantity that meets the validity period is used as the inventory quantity that can participate in the requisition judgment. The quantity of inventory eligible for requisition is compared with the minimum safety stock. When the quantity of inventory eligible for requisition is greater than the minimum safety stock, the quantity eligible for requisition is determined according to the smaller value between the application quantity and the portion of the quantity of inventory eligible for requisition that exceeds the minimum safety stock. When the quantity of inventory eligible for requisition is not greater than the minimum safety stock, a rejection or pending review task is generated.

5. The method for refined access control of intelligent consumables based on edge computing according to claim 4, characterized in that, Before determining the available quantity, the edge computing node performs a validity check on the inventory quantity eligible for requisition. The validity check includes: Compare the expiration dates of each batch under the corresponding consumable category with the current time, and remove the inventory quantity corresponding to the batches whose expiration dates do not meet the preset expiration date conditions; Compare the location status of the remaining batches with the available location status, and remove the inventory quantity whose location status does not meet the requirements for available location status. The inventory quantity after rejection is used as the inventory quantity that can be used for the decision after validity verification, and is used to determine the quantity that can be used.

6. The method for refined access control of intelligent consumables based on edge computing according to claim 1, characterized in that, The process by which the edge computing node filters the candidate storage locations includes: According to the consumable category corresponding to the requisition application, read the list of storage locations associated with the same consumable category, match the batches corresponding to each storage location with the batch records under the same consumable category, and remove storage locations whose batches do not belong to the batch records under the same consumable category. The validity period is compared with the preset validity period conditions, and the storage locations whose validity periods do not meet the preset validity period conditions are eliminated; The storage location status is compared with the available storage location status, and storage locations whose status does not meet the requirements of the available storage location status are removed. The remaining storage spaces will be used as candidate storage spaces.

7. The method for refined access control of intelligent consumables based on edge computing according to claim 6, characterized in that, The process of determining the target storage location includes: Based on the fact that all candidate storage locations have met the preset validity period conditions, the inventory quantity corresponding to each candidate storage location is read, and the candidate storage locations with an inventory quantity not less than the available quantity are taken as the first candidate set. When the first candidate set is empty, a rejection or pending review task is generated; When the first candidate set is not empty, the candidate locations are sorted in order of validity period from earliest to latest, and the candidate locations with the highest validity period are selected as the second candidate set. When there is a single candidate location in the second candidate set, the single candidate location is determined as the target location. When there are multiple candidate locations in the second candidate set, the target location is determined from the multiple candidate locations according to the location status update time.

8. The method for refined access control of intelligent consumables based on edge computing according to claim 7, characterized in that, The process of determining the target storage location from multiple candidate storage locations based on the storage location status update time includes: Read the location status update time and the most recent access completion time for each of the multiple candidate locations in the second candidate set; When the location status update time of multiple candidate locations in the second candidate set is later than the most recent access completion time, the candidate location whose location status update time is closest to the current time is determined as the target location. When there are candidate storage locations whose status update time is no later than the most recent access completion time, remove the candidate storage location whose status update time is no later than the most recent access completion time from the second candidate set, and re-determine the target storage location from the removed second candidate set; When the second candidate set after elimination is empty, generate a task to be reviewed and stop the opening of the control cabinet door lock or the cargo location lock.

9. The method for refined access control of intelligent consumables based on edge computing according to claim 1, characterized in that, The process by which the edge computing node determines the replenishment priority includes: The real-time inventory, minimum safety stock, usage frequency, replenishment cycle, and expiration date are read using the consumable category as the statistical object. When the real-time inventory is lower than the minimum safety stock, an inventory gap flag is generated; when the real-time inventory is not lower than the minimum safety stock, an inventory normal flag is generated. The cycle consumption status is determined based on the usage frequency and the replenishment cycle, and the expiration risk status is determined based on the expiration date. Write the inventory gap identifier or the normal inventory identifier, the cycle consumption status and the expiration date risk status into the replenishment task record, and determine the replenishment priority according to the preset priority table.

10. The method for refined access control of intelligent consumables based on edge computing according to claim 1, characterized in that, The process of comparing the actual quantity with the task quantity after the data is stored includes: After the cabinet door lock or the storage location lock is closed, the edge computing node reads the number of tasks corresponding to the same task and the actual number fed back by the quantity detection device; The absolute value of the difference between the actual quantity and the task quantity is taken as the quantity deviation, and the quantity deviation is compared with the preset deviation threshold. When the quantity deviation does not exceed the preset deviation threshold, the corresponding inventory increase or decrease result is written into the inventory ledger according to the task type, and the task number, consumable category, batch, target storage location, actual quantity and verification result are written into the consumable circulation record; When the quantity deviation exceeds the preset deviation threshold, the inventory change corresponding to this task is kept in the pending confirmation state, and an abnormal review task containing the task number, target location and quantity deviation is generated.

Images