Lattice resource management method and device, equipment and storage medium

Abstract

The invention relates to the field of intelligent cabinet resource management, and discloses a lattice resource management method, device and equipment and a storage medium, and the method comprises the steps: receiving a lattice use request of a business side, and the lattice use request at least comprises a business type and a use time period; based on an allocatable time period of a cell and a service type adapted to the allocatable time period, screening candidate cells meeting the cell use request; determining a target lattice from the candidate lattices; and allocating the use authority of using the target grid in the use time period to the business party. The problem that in the prior art, the lattice resource utilization rate is low is solved.

Description

Technical Field

[0001] This invention relates to the field of intelligent cabinet resource management, and in particular to a method, apparatus, equipment and storage medium for managing cabinet resources. Background Technology

[0002] Smart parcel lockers consist of fixed physical compartments. Current technology employs a static resource allocation strategy, where each compartment logically corresponds to a single purpose (such as parcel storage), and its service function remains unchanged, unable to be dynamically adjusted according to time changes or different business needs. Furthermore, existing systems lack a conflict coordination mechanism for multiple services sharing the same physical resource. Under static allocation, compartment functions cannot be switched over time, resulting in significant fluctuations in utilization rates within 24 hours. Hardware resources cannot be effectively utilized during idle periods, and the lack of conflict coordination capabilities for multiple services sharing physical compartments means that even if reuse is needed, orderly sharing cannot be achieved, leading to persistent resource idleness.

[0003] Therefore, existing technologies suffer from low utilization of grid space resources. Summary of the Invention

[0004] This invention provides a grid resource management method, apparatus, computer equipment, and storage medium to solve the problem of low grid resource utilization in the prior art.

[0005] Firstly, a grid resource management method is provided, including: Receive grid usage requests from service providers. Grid usage requests must include at least the service type and usage period. Based on the allocable time slots of the grid and the service types that the allocable time slots are compatible with, candidate grids that meet the grid usage requests are filtered. Identify the target cell from the candidate cells; Assign usage permissions to the business unit for the target grid during the usage period.

[0006] Optionally, before receiving the grid usage request from the business party, the following steps are also included: Create at least two logical cells for each cell, and each logical cell is uniquely bound to one business type; Configure non-overlapping allocatable time periods for each logical cell in each cell.

[0007] Optionally, based on the allocatable time slots of the grid and the service types that the allocatable time slots are compatible with, candidate grids that meet the grid usage requests can be filtered, including: Analyze the business type, usage period, and inherent attribute requirements of the grid usage request; Based on the correlation between the allocable time slots of the grid and the adapted business types, grids that are adapted to the business types and whose allocable time slots include the usage time slots are selected. Verify whether the selected grid cells meet the inherent attribute requirements of the grid cells, and retain the grid cells that meet the inherent attribute requirements as candidate grid cells.

[0008] Optionally, the target cell can be determined from the candidate cells, including: Collect resource status data for each candidate grid; The resource status data is weighted and calculated based on the load balancing algorithm to generate a priority score; Sort the candidate cells by score from highest to lowest, and select the highest-scoring candidate cell as the target cell.

[0009] Optionally, after allocating usage rights for the target grid to the business party during the usage period, the following may also be included: Monitor the operational status of the target grid and the expiration of its usage period; If the business operation is detected to be completed or the usage period expires, the binding relationship between the target grid and the current business is released.

[0010] Optionally, the grid usage request may also include a reservation mode parameter to filter candidate grids that meet the grid usage request, and may also include: Parse the booking mode parameters to determine the booking type, which includes periodic booking; Extract the periodic rules and time period repetition range, and verify whether the allocable time period of the grid is compatible with the periodic rules; Retain grid cells that fit the cycle rule as candidate grid cells.

[0011] Optional, grid resource management methods also include: Monitor abnormal events during the use of the grid; If an abnormal event is detected, immediately suspend all operations on the grid and send an abnormality alert notification to the business party; Based on the preset exception handling mechanism, abnormal events in the grid are handled. After the abnormal event is resolved, all operations on the grid will be restarted.

[0012] Secondly, a grid resource management device is provided, comprising: The receiving module is used to receive grid usage requests from business parties. The grid usage request must include at least the business type and the usage period. The filtering module is used to filter candidate grids that meet the grid usage requests based on the grid's allocable time period and the service type that the allocable time period is compatible with. The determination module is used to determine the target cell from the candidate cells; The allocation module is used to allocate usage permissions for a target grid to business users during the usage period.

[0013] Thirdly, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described grid resource management method.

[0014] Fourthly, a computer-readable storage medium is provided, which stores a computer program that, when executed by a processor, implements the steps of the above-described grid resource management method.

[0015] The aforementioned grid resource management method, device, equipment, and storage medium receive usage requests containing "service type" and filter candidate grids based on the grid's "allocable time slots," allowing the same grid to serve different services at different times. Using "usage time slots" as the core allocation criterion, the system matches service needs by filtering grids' "allocable time slots," ensuring grids are accurately matched to services with demand at different times, avoiding long-term idleness during specific periods, and significantly improving overall resource utilization. By receiving requests containing "usage time slots," the system adapts to the timing requirements of new services, expanding grids from single-function to multi-service scenarios, increasing grid usage frequency, and further improving utilization. Therefore, this invention solves the problem of low grid resource utilization in the prior art. Attached Figure Description

[0016] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the 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 a flowchart illustrating a grid resource management method according to an embodiment of the present invention; Figure 2 This is a schematic diagram of a grid resource management device according to an embodiment of the present invention. Detailed Implementation

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

[0019] It should be understood that, when used in this specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0020] It should also be understood that the term “and / or” as used in this specification and the appended claims refers to any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0021] As used in this specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," or "in response to determination." Similarly, the phrase "if determined" or "if matched to [described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once matched to [described condition or event]," or "in response to matched to [described condition or event]."

[0022] Furthermore, in the description of this invention and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0023] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of the invention include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0024] It should be understood that the sequence number of each step in the following embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present invention.

[0025] To illustrate the technical solution of the present invention, specific embodiments are described below.

[0026] Please see Figure 1 As shown, Figure 1 A flowchart illustrating the grid resource management method provided in this embodiment of the invention includes the following steps: S11: Receive grid usage requests from service providers. Grid usage requests must include at least the service type and usage period.

[0027] The business type clearly defines the functional attributes of the business, such as express delivery storage, community retail, and item rental, which are the core dimensions for selecting suitable storage compartments (such as size and hardware support capabilities).

[0028] Using time periods to clearly define the time attributes of a business, including start and end times, is the core basis for avoiding conflicts between multiple businesses and realizing time-sharing reuse of grid slots, and it adapts to the refined management logic of grid slot time resources.

[0029] In one example, in a community retail scenario, a merchant initiates a request to use storage compartments, with the business type being "community retail" and the usage period being "8:00-18:00 daily". The request implicitly includes the requirement that the compartment size be suitable for storing snacks, daily necessities, and other goods, and the system can use this to filter for compartments that meet the size requirements.

[0030] In one example, in a courier scenario, the courier initiates a request to use a storage compartment, with the service type being "courier storage" and the usage period being "19:00 on the same day to 10:00 the next day". The system can allocate storage compartments used for retail during the daytime to courier services through time-time matching, achieving resource reuse.

[0031] In one example, in a rental scenario, the rental platform initiates a request to use a rental space, with the business type being "item rental" and the usage period being "every Saturday from 9:00 to 17:00" (a periodic booking requirement). The system can then filter for non-conflicting rental spaces based on this time period to meet specific time-sensitive business needs.

[0032] S12: Based on the allocatable time period of the grid and the service type that the allocatable time period is compatible with, filter candidate grids that meet the grid usage request.

[0033] This step is a key screening process for realizing dynamic reuse of grid slots. Its core value is to accurately match "business needs" with "grid slot resource capabilities". It locks in available grid slots through dual-dimensional verification of allocable time periods and business type adaptation, which avoids time conflicts between multiple businesses and ensures that grid slot functions are adapted to business types.

[0034] Allocable time slot verification uses the time slots that are currently not occupied and have no future booking conflicts as the filtering criteria. The core is to determine whether the usage time slot of the business request is completely matched with the idle time slot of the grid, so as to avoid the same grid being repeatedly allocated at the same time. Business type adaptation verification ensures that the business type adapted by the grid in its allocable time slot is consistent with the business type in the grid usage request.

[0035] In one example, in a community retail business scenario, a merchant requests the "community retail" service, with the usage period being "8:00-18:00 daily". When filtering, the system first checks the allocable time periods of all grids, and locks the grids with no occupancy conflicts between 8:00 and 18:00; then it further filters the grids that can execute the "community retail" service, and finally obtains the candidate grids.

[0036] In one example, in a parcel storage service scenario, a courier requests the "parcel storage" service during the period of "19:00 on the same day to 10:00 the next day". The system first filters out the storage compartments that are idle between 19:00 and 10:00 the next day; then it verifies whether these compartments support the "parcel storage" service and selects the candidate compartments that meet the requirements.

[0037] In one example, in a rental business scenario, the rental platform requests an "item rental" service, with the usage period being "every Saturday from 9:00 to 17:00". The system first searches for all rental spaces with no booking conflicts during Saturday's 9:00-17:00 period; then it filters among those spaces that support the "item rental" service, ultimately obtaining candidate rental spaces.

[0038] It's important to note that in some scenarios, the inherent attributes of the storage compartments also need to be considered. These attributes form the underlying foundation for business type adaptation and, together with "allocated time slots" and "time slot-compatible business types," constitute a three-dimensional filtering process. The fixed nature of these inherent attributes determines the business adaptation boundaries of the compartments. For example, even if a small-sized compartment is available during a specific time slot and is marked as compatible with "item rental," it cannot meet the storage needs of large rental equipment. Similarly, a compartment without load-bearing reinforcement, even with retail business permissions enabled, cannot be used to store heavy retail goods. Therefore, when filtering candidate compartments, we first use "allocated time slots" to narrow down the range of compartments with no time conflicts. Then, we narrow down the candidate pool for business type matching using "time slot-compatible business types." Finally, we perform precise verification based on the inherent attributes of the compartments to ensure that the selected candidate compartments are not only "available in time and functionally compatible" but also "hardware compliant," fundamentally avoiding business execution failures caused by mismatched inherent attributes (such as items being unable to be placed, inconvenient storage and retrieval operations, and security risks). The above steps for screening candidate grids are not unique. Alternatively, grids that meet the hardware requirements can be identified based on their inherent attributes. Then, grids with non-conflicting time slots can be narrowed down using "allocated time slots." Finally, candidate grids can be determined based on "time slot matching service type." In some embodiments, grids whose "service type" matches the "service type" in the grid usage request can be screened first. Then, grids whose "allocated time slots" do not conflict with the "usage time slots" in the grid usage request can be screened from among them. Finally, grids that meet the hardware requirements can be identified based on their inherent attributes as candidate grids.

[0039] S13: Determine the target cell from the candidate cells.

[0040] The core value of this step is to select the optimal target grid from the candidate grids that meet the criteria.

[0041] In one embodiment, determining the target cell from the candidate cells includes: collecting resource status data of each candidate cell; performing weighted calculation on the resource status data based on a load balancing algorithm to generate a priority score; sorting the scores from high to low, and selecting the candidate cell with the highest score as the target cell.

[0042] The core value of this embodiment is to quantitatively assess the target grid, ensuring that the target grid meets business needs and achieving global grid resource load balancing, avoiding local resource overload or idleness, and further improving the overall grid resource utilization rate.

[0043] Resource status data forms the basis of quantitative assessment, covering core indicators reflecting the "load level" and "service capacity" of the grid. The data is updated in real time to ensure assessment accuracy. Core collected indicators typically include: historical utilization rate (e.g., the percentage of time occupied in the last 7 / 30 days), current load (e.g., the number of booked but unfulfilled business orders), hardware health (e.g., the failure rate and sensor normal response rate in the last 3 months), and network status (e.g., real-time communication latency and command response speed).

[0044] The core of the load balancing algorithm is "weight allocation on demand." It sets the weight percentage of each indicator based on business scenarios and operational goals, and generates a priority score through weighted summation (the higher the score, the more suitable the grid is as the target grid). The weight setting logic prioritizes balancing resource utilization, followed by ensuring business stability. For example, in general scenarios, the weight allocation is: historical utilization 30%, current load 25%, hardware health 30%, and network status 15%. In emergency business scenarios (such as instant delivery), the network status weight can be adjusted to 30% to prioritize response speed.

[0045] All candidate grids are ranked in descending order of their scores, and the top-ranked grid is selected as the target grid to ensure objectivity and efficiency in decision-making. In case of a tie, auxiliary indicators such as "grid location priority" and "historical business matching degree" can be added to break the tie.

[0046] In one example, there are 3 candidate cells. The specific data and calculation process are as follows: Candidate port A has a historical utilization rate of 60%, corresponding to a score of 18; current load is 2 single units, corresponding to a score of 20; hardware health is 98%, corresponding to a score of 29.4; network latency is 50ms, corresponding to a score of 14. The overall priority score is 18+20+29.4+14=81.4.

[0047] Candidate port B has a historical utilization rate of 85%, corresponding to a score of 25.5; a current load of 5 units, corresponding to a score of 10; a hardware health rate of 95%, corresponding to a score of 28.5; and a network latency of 60ms, corresponding to a score of 12. The overall priority score is 25.5+10+28.5+12=76.

[0048] Candidate port C has a historical utilization rate of 70%, corresponding to a score of 21; current load is 3 units, corresponding to a score of 15; hardware health is 92%, corresponding to a score of 27.6; network latency is 45ms, corresponding to a score of 14.5. The overall priority score is 21+15+27.6+14.5=78.1.

[0049] The sorting result is grid A (81.4) > grid C (78.1) > grid B (76), and the system finally determines grid A as the target grid.

[0050] S14: Assign usage permissions to the business party for the target grid during the usage period.

[0051] This step is the final stage of grid cell resource allocation. Its core value is to clarify the permission binding relationship between the business party and the target grid cell. This ensures that the business party can legally use the grid cell within a specified time period, and also prevents the resources from being illegally occupied or used beyond their authority through permission control, thus providing security for the dynamic reuse of grid cells.

[0052] This step strongly links access permissions with the business party, the target lock, and the usage period. Only the specified business party is authorized to operate the target lock during the designated time period; other business parties or those operating outside of authorized periods cannot obtain access. The permission's effective time is exactly the same as the usage period requested by the business party, preventing long-term permission validity that could lead to resource hoarding. A unique business credential (such as a QR code, verification code, or electronic key) is generated simultaneously when allocating permissions, serving as the identity verification basis for subsequent unlocking and ensuring that permissions are not misused. Furthermore, after permission allocation, the status of the target lock (e.g., "authorized" or "occupied") can be updated in real time and synchronized globally to prevent duplicate lock allocation.

[0053] In one example, in a community retail business scenario, a merchant's business request is "community retail," the usage period is "daily 8:00-18:00," and the target grid is grid A. When the system assigns permissions to this merchant, it binds the association "Merchant ID - Grid A - daily 8:00-18:00," generating a unique merchant code. After 8:00 each day, the merchant can unlock grid A to restock using this merchant code, and users can pick up their orders within the specified time using the pickup code generated after shopping. After 18:00, the permissions automatically expire, and neither the merchant nor the user can operate grid A anymore; the grid status is updated to "pending delivery service allocation."

[0054] In one example, in a parcel storage service scenario, the courier's service request is "parcel storage," with a usage period of "19:00 on the same day to 10:00 the next day," and the target parcel locker is locker A. When assigning permissions, the system binds "courier ID - locker A - 19:00 on the same day to 10:00 the next day," generating a temporary delivery voucher. After 19:00, the courier can unlock locker A with the voucher to drop off the parcel, and the system simultaneously sends a pickup code to the recipient. After 10:00 the next day, both the delivery voucher and the pickup code become invalid, and uncollected parcels will trigger a system reminder, with the locker status updated to "idle and awaiting authorization."

[0055] In one example, in a rental business scenario, the rental platform's business request is "item rental," the usage period is "every Saturday 9:00-17:00," and the target grid is grid F. When assigning permissions, the system binds "Rental Platform ID - Grid F - every Saturday 9:00-17:00" and generates a periodic electronic key. Every Saturday after 9:00, the rental user can unlock grid F to pick up and return the device using the electronic key issued by the platform; after 17:00, the key expires, the grid is automatically locked, and the status is updated to "idle," awaiting authorization to take effect the following week.

[0056] The aforementioned grid resource management method receives usage requests containing "business type" and filters candidate grids based on their "allocated time slots," allowing the same grid to serve different businesses at different times. Using "usage time slot" as the core allocation criterion, it matches business needs by filtering grids' "allocated time slots," ensuring grids are accurately matched to businesses with demand at different times, avoiding long-term idleness during specific periods, and significantly improving overall resource utilization. By receiving requests containing "usage time slots," it adapts to the timing requirements of new businesses, expanding grids from single-function to multi-service scenarios, increasing grid usage frequency, and further improving utilization. Therefore, this invention solves the problem of low grid resource utilization in existing technologies.

[0057] In one embodiment, before receiving a grid usage request from a service provider, the method further includes: creating at least two logical grids for each grid, with each logical grid uniquely bound to a service type; and configuring non-overlapping allocable time periods for each logical grid of each grid.

[0058] This embodiment is a preliminary basic configuration step for dynamic grid reuse. Its core value is to break the functional and time limitations of a single physical grid from the underlying architecture through "physical grid virtualization + time period isolation", which provides feasibility for subsequent multi-service time-sharing reuse and directly solves the problems of single grid function and idle waste in the existing technology.

[0059] This step builds the multi-service reuse capability of physical grids through a combination of "logical grid creation + allocable time period configuration". The core logic includes: Logical grids are bound one-to-one with business types. Each physical grid is split into at least two independent logical grids, and each logical grid corresponds to only one business type (such as express delivery, retail, leasing). The logical grid is a "functional mirror" of the physical grid, realizing the functional split of the same physical grid and enabling a single physical grid to handle multiple businesses. Allocable time slots do not overlap. Different logical grids under the same physical grid are configured with completely non-overlapping allocable time slots. Through time-dimensional isolation, usage conflicts between different business types are avoided, ensuring that the same physical grid serves different businesses in an orderly manner at different times, maximizing the utilization of time resources. There is a many-to-one mapping between physical and logical grids. Multiple logical grids share the hardware resources of a single physical grid. The status of a logical grid (idle, authorized, occupied) is synchronously associated with the physical grid, ensuring unified scheduling and management of hardware resources without increasing additional hardware investment.

[0060] In one example, there is a physical grid X, and the configuration process for this grid is as follows: The first step is to create logical grids and bind them to business types. Create three logical grids for the physical grid X: Logical Grid X1 (bound to the "Community Retail" business), Logical Grid X2 (bound to the "Courier Storage" business), and Logical Grid X3 (bound to the "Item Rental" business). Each logical grid only responds to requests for its corresponding business type and does not interfere with each other.

[0061] The second step is to configure non-overlapping allocable time slots, assigning dedicated allocable time slots to the three logical grids: Logical Grid X1 (8:00-18:00 daily), Logical Grid X2 (19:00-7:00 the next day daily), and Logical Grid X3 (10:00-16:00 every Saturday). These three time slots do not overlap, ensuring that the usage needs of different services will not conflict.

[0062] When reusing physical locker X, for example, from 8:00 to 18:00 daily, logical locker X1 is active, and physical locker X acts as a retail locker to receive merchant restocking requests and user self-pickup requests; from 19:00 to 7:00 the next day, logical locker X2 is active, and physical locker X switches to a parcel locker to receive parcel delivery and pickup; every Saturday from 10:00 to 16:00, logical locker X3 is active, and physical locker X acts as a rental locker for users to pick up and return the equipment. Through the time-sharing activation of logical lockers, the idle time of physical locker X is fully utilized, achieving efficient reuse of multiple services.

[0063] In one embodiment, candidate grids that meet the grid usage request are filtered based on the grid's allocable time period and the service type that the allocable time period is adapted to. This includes: parsing the service type, usage time period, and grid inherent attribute requirements in the grid usage request; filtering grids that adapt to the service type and whose allocable time period includes the usage time period based on the association between the grid's allocable time period and the adapted service type; verifying whether the filtered grids meet the grid inherent attribute requirements, and retaining grids that meet the grid inherent attribute requirements as candidate grids.

[0064] This embodiment is a refined implementation process for candidate grid selection. Its core value lies in accurately identifying grids that meet the criteria of "business compatibility, time availability, and hardware compliance" through a three-tiered progressive logic of "analyzing requirements → preliminary screening → attribute verification". This ensures the accuracy of the screening results and provides high-quality candidate grids for subsequent target grid selection.

[0065] It's important to note that the inherent attributes of the storage compartments form the underlying foundation for business type adaptation, and together with "allocated time slots" and "time slot-compatible business types," they constitute a three-dimensional filtering process. The fixed nature of these inherent attributes determines the business adaptation boundaries of the compartments. For example, even if a small-sized compartment is available during a specific time slot and is marked as compatible with "item rental," it cannot meet the storage needs of large rental equipment; similarly, a compartment without load-bearing reinforcement, even with retail business permissions, cannot be used to store heavy retail goods. Therefore, when filtering candidate compartments, the process first uses "allocated time slots" to narrow down the range of compartments without time conflicts, then narrows down the candidate pool for business type matching using "time slot-compatible business types," and finally performs precise verification based on the compartment's inherent attributes. This ensures that the selected candidate compartments are not only "available in time and functionally compatible," but also "hardware compliant," fundamentally avoiding business execution failures caused by inherent attribute mismatches (such as items being unable to be placed, inconvenient storage and retrieval operations, and security risks). The above steps for screening candidate grids are not unique. Alternatively, grids that meet the hardware requirements can be identified based on their inherent attributes. Then, grids with non-conflicting time slots can be narrowed down using "allocated time slots." Finally, candidate grids can be determined based on "time slot matching service type." In some embodiments, grids whose "service type" matches the "service type" in the grid usage request can be screened first. Then, grids whose "allocated time slots" do not conflict with the "usage time slots" in the grid usage request can be screened from among them. Finally, grids that meet the hardware requirements can be identified based on their inherent attributes as candidate grids.

[0066] In one example, in a community retail business scenario, a merchant initiates a request to use a locker. After parsing, the core requirements are: "Business type: community retail; Usage time: 8:00-18:00 daily; Locker attribute requirements: medium size (30cm×40cm×50cm), bottom position, QR code lock". The system first filters out locker A, locker B, and locker C based on "suitable for retail business + allocable time period includes 8:00-18:00". Then it verifies the attributes - locker A (medium size, bottom position, QR code lock) meets the requirements, locker B (small size, bottom position, QR code lock) does not meet the size requirements, and locker C (medium size, top position, combination lock) does not meet the location and locking requirements. In the end, only locker A is retained as a candidate locker.

[0067] In one example, in a parcel storage service scenario, a courier initiates a request. The parsed requirements are: "Service type: parcel storage; Usage period: 19:00 on the same day to 10:00 the next day; Compartment attribute requirements: multi-size combination, load capacity ≥10kg, front opening." The system first filters out compartments A, D, and E that are "suitable for parcel services and available during the time period." Then, it verifies the attributes—compartment A (multi-size, load capacity 12kg, front opening) meets the requirements, compartment D (single small size, load capacity 8kg, front opening) does not meet the size and load capacity standards, and compartment E (multi-size, load capacity 10kg, side opening) does not meet the opening method standards. Finally, compartment A is retained as a candidate compartment.

[0068] In one example, in a rental business scenario, the rental platform initiates a request, which, after parsing, specifies the requirements as follows: "Business type: item rental; Usage time: every Saturday 9:00-17:00; Compartment attribute requirements: large size (60cm×50cm×80cm), load capacity ≥15kg, electronic combination lock." The system first filters out compartments F and G that are "suitable for rental business + periodically available time"; then it verifies the attributes—compartment F (large size, load capacity 18kg, electronic combination lock) meets the requirements, while compartment G (large size, load capacity 12kg, barcode lock) does not meet the load capacity and locking requirements. Ultimately, only compartment F is retained as a candidate compartment.

[0069] In one embodiment, after allocating usage rights for the target grid to the service provider within a usage period, the method further includes: monitoring the service execution status of the target grid and the expiration of the usage period; if the service execution is completed or the usage period expires, the binding relationship between the target grid and the current service is released.

[0070] This embodiment is a key final step in the recycling and reuse of grid resources. Its core value is to realize the dynamic release and status reset of grid resources, ensuring that the target grid quickly returns to an allocable state after the business ends or the time period expires, avoiding long-term resource occupation, further improving the overall grid utilization rate, and ensuring the orderly reuse of multiple services in a time-sharing manner.

[0071] This embodiment simultaneously tracks "business execution status" and "usage period expiration status" to ensure no resource release is missed. Business execution status is monitored by grid sensors (door magnets, infrared) (e.g., items removed, cabinet doors closed), while usage period is verified in real time by the system clock. Meeting either condition triggers subsequent operations. Furthermore, unbinding and status reset are synchronized, removing the binding relationship between "business party - target grid - usage period" and revoking usage rights (e.g., business credentials expire). Simultaneously, the target grid's status is updated to "idle" or "pending allocation," synchronized to the grid resource pool, ensuring that subsequent new grid usage requests can be correctly filtered for that grid.

[0072] In one example, in a community retail business scenario, the merchant's usage period is "8:00-18:00 daily," and the target parcel locker is locker A. Monitoring is conducted on two fronts: firstly, a door magnetic sensor determines whether the merchant has finished restocking and whether users have picked up their packages; secondly, it verifies whether 18:00 has arrived. If the merchant completes restocking by 17:30 and all users have picked up their packages for the day, the sensor reports "business completed," and the system immediately unbinds the merchant from locker A, updating the locker status to "idle." If there are still unpicked items at 18:00, the system will also trigger unbinding, permissions will be invalidated, the locker status will be updated to "pending delivery," and the unpicked items will be included in subsequent reminder processes.

[0073] In one example, in a parcel storage service scenario, the courier's usage period is "19:00 on the same day to 10:00 the next day," and the target locker is locker A. If the system detects that the recipient retrieves the package at 9:30 the next day using the pickup code, and the locker door closes, the sensor reports "service completed." The system then unbinds the courier, recipient, and locker A, and the locker status is updated to "idle." If the recipient still hasn't retrieved the package by 10:00 the next day, the system triggers the time-limited unbinding, the permission expires, and a timeout reminder is sent to the recipient. The locker status is updated to "pending processing of delayed packages," and the package can then be assigned to other services.

[0074] In one example, in a rental business scenario, the rental platform is available every Saturday from 9:00 AM to 5:00 PM, with the target compartment being compartment F. If a user returns the rented equipment and closes the locker door at 4:40 PM, the sensor reports "Business completed," and the system unlinks the rental platform from compartment F, updating the compartment status to "Idle." If the user fails to return the equipment by 5:00 PM, the system triggers unlinking upon expiration of the time slot, invalidating the access permission. Simultaneously, a timeout reminder is sent to the rental platform, and the compartment status is updated to "Rental business pending follow-up," without affecting subsequent business allocation for other time slots.

[0075] In one embodiment, the grid usage request further includes a reservation mode parameter. Filtering candidate grids that meet the grid usage request also includes: parsing the reservation mode parameter to determine the reservation type, where the reservation type includes periodic reservation; extracting the periodic rules and time period repetition range; verifying whether the grid's allocable time period matches the periodic rules; and retaining grids that match the periodic rules as candidate grids.

[0076] This embodiment is an extension and optimization of the candidate grid selection logic. Its core value is to adapt to the time-series requirements of periodic businesses. By parsing the reservation mode parameters and verifying the adaptability of the period rules, grid resource management can support long-term repeated business requests, further expand grid reuse scenarios, and improve the continuity and flexibility of resource utilization.

[0077] This embodiment extracts reservation mode parameters from grid usage requests to determine whether the reservation type is a periodic reservation (such as daily repetition, weekly repetition on specific days, or monthly repetition at fixed times), distinguishing it from one-time reservations, and initiates targeted period adaptation verification; it parses the periodic rules (such as repetition every Saturday, daily repetition at fixed times) and the period repetition range (such as a repetition cycle of 12 weeks or 3 months) from the reservation mode parameters, clarifying the time pattern and validity period of the business repetition; it queries the allocable time periods of candidate grids, verifying whether they can meet the periodic rules throughout the entire period repetition range (such as the allocable time periods of every Saturday including the usage period of the business request), and without any time conflicts; finally, it only selects grids that fully adapt to the periodic rules within the period repetition range, ensuring that periodic businesses can be used continuously and without conflicts, forming the final candidate grids.

[0078] In one example, in a long-term replenishment scenario for community retail, a merchant initiates a request to use a storage space. The business type is "community retail," the usage period is "8:00-18:00 daily," and the reservation mode parameter is "periodic reservation - daily repetition - time period repetition range of 30 days." After system parsing, it determines that the reservation type is daily periodic reservation, the periodic rule is "daily repetition," and the repetition range is 30 days. When verifying candidate storage spaces, it is necessary to confirm that the available time periods for the storage space are not conflicting and are suitable for retail business within the next 30 days, from 8:00 to 18:00 daily. If the available time periods for storage space A are "8:00-18:00 daily (long-term valid)," it passes the verification and is retained as a candidate storage space. If the available time periods for storage space B are only available daily for the next 20 days, and are already occupied for the last 10 days, it is excluded because it does not meet the requirement of full compatibility.

[0079] In one example, in a weekend rental scenario, the rental platform initiates a request with the business type being "item rental," the usage period being "every Saturday from 9:00 AM to 5:00 PM," and the booking mode parameters being "periodic booking - repeating every Saturday - time period repetition range of 8 weeks." After system parsing, the periodic rule "repeating every Saturday" with a repetition range of 8 weeks is extracted. During verification, it is necessary to confirm that the candidate rental space is available for allocation every Saturday from 9:00 AM to 5:00 PM for the next 8 weeks and is suitable for the rental business. Rental space F's available time period includes "Saturdays from 9:00 AM to 5:00 PM for the next 10 weeks," meeting the 8-week repetition requirement, and is retained as a candidate rental space; Rental space G's available time period is only available on Saturdays for the first 4 weeks, with bookings already made for the last 4 weeks, therefore it does not meet the requirements and is filtered out.

[0080] In one example, during a monthly concentrated delivery scenario, a company courier initiates a request for "express delivery storage," specifying the usage period as "14:00-18:00 on the 5th, 15th, and 25th of each month," with the booking mode parameters being "periodic booking - repeating on specific days each month - time period repetition range of 6 months." After system parsing, the periodic rule is determined to be "repeated on the 5th / 15th / 25th of each month," with a repetition range of 6 months. When verifying candidate storage spaces, it is necessary to confirm that for the next 6 months, the 14:00-18:00 time period on these three dates is allocable and suitable for express delivery services. Storage space D's allocable time period covers this periodic period without conflict and is retained as a candidate storage space; if storage space E is already occupied on the 5th of the 4th month during this time period, it is excluded due to a conflict.

[0081] In one embodiment, the grid resource management method further includes: monitoring abnormal events during grid usage; if an abnormal event is detected, immediately suspending all operations on the grid and sending an abnormality alert notification to the business party; processing the abnormal event of the grid based on a preset abnormality handling mechanism; and restarting all operations on the grid after the abnormal event is resolved.

[0082] This embodiment is a security guarantee link in grid resource management. Its core value is to establish a closed-loop mechanism of "anomaly monitoring - emergency control - efficient processing - recovery of use". Without affecting the overall operation, it can quickly respond to sudden problems in the use of grids, avoid business interruption, security risks to goods or waste of resources caused by the escalation of anomalies, and ensure the stability and security of dynamic reuse of grids.

[0083] This embodiment uses hardware sensors (door magnets, infrared sensors, load-bearing sensors), system communication modules, and business execution logs to monitor various abnormal events in real time, covering scenarios such as equipment failure, operational anomalies, and environmental risks. Upon detecting an anomaly, it immediately triggers "pause all operations," freezing the locker's unlocking permissions, status updates, and other functions to prevent misoperations under abnormal conditions (such as unauthorized unlocking or duplicate allocation). Simultaneously, it pushes reminders to the business party to ensure timely awareness. It has a built-in preset anomaly handling mechanism that matches corresponding solutions according to the anomaly type, enabling rapid handling without manual intervention and improving processing efficiency. Complex anomalies can trigger manual intervention processes to ensure compliant handling. After the anomaly is resolved, it automatically verifies the locker status (such as normal hardware and no safety hazards), and restarts all operations on the locker upon successful verification.

[0084] In one example, the target compartment's electronic lock malfunctions (unable to unlock / lock), the door magnetic sensor fails (unable to monitor cabinet door status), and the communication module disconnects (unable to receive / feedback commands). Upon detecting the lock malfunction, the system immediately suspends all unlocking requests for that compartment; sends a notification to service providers (such as retailers or delivery personnel) stating "Compartment equipment malfunction, temporarily unavailable"; based on a preset mechanism, it automatically marks the compartment as "faulty and awaiting repair" and reassigns unfinished business to other available compartments; after repair personnel restore the lock, the system verifies that the lock and sensor are functioning correctly and restarts all operations on the compartment.

[0085] In one example, the user failed to close the locker door promptly after unlocking (30 minutes overdue), the package was overweight after delivery triggering a locker weight alarm, and the rental equipment was not properly placed upon return (the infrared sensor did not detect the item). Upon detecting that the locker door was not closed within the time limit, the system immediately suspends further authorization for that locker; sends a reminder to the service provider (e.g., recipient, merchant) stating "Locker door not closed, please handle promptly"; triggers a local buzzer alarm via a preset mechanism; and simultaneously notifies maintenance personnel for on-site verification; once the recipient closes the locker door or maintenance personnel have completed the task, the system verifies the status is normal and restarts all operations on the locker.

[0086] In one example, a system concurrency vulnerability led to a conflict of permissions caused by the same grid being repeatedly assigned to two different business units and overlapping booking periods. Upon detecting the conflict, the system immediately suspended the operational permissions of both business units; sent a notification to both parties stating "Grid resource conflict, temporarily unavailable"; initiated a conflict arbitration mechanism, prioritizing the business unit that initiated the request first and reassigning the later-assigned business unit to other candidate grid units; after the conflict was resolved, permissions were restored for the priority business unit, and the other business unit was reassigned a target grid unit to ensure the normal operation of both business units.

[0087] In one embodiment, a grid resource management device is provided. For example... Figure 2As shown, it includes a receiving module 21, a filtering module 22, a determining module 23, and an allocation module 24. Detailed descriptions of each functional module are as follows: Receiver module 21 is used to receive grid usage requests from business parties. The grid usage request includes at least the business type and usage period. The filtering module 22 is used to filter candidate grids that meet the grid usage request based on the grid's allocable time period and the service type that the allocable time period is compatible with. The determination module 23 is used to determine the target cell from the candidate cells; The allocation module 24 is used to allocate usage rights of the target grid to the business party during the usage period.

[0088] This invention also provides an electronic device, including a memory, a processor, and a program stored in the memory and executable on the processor. When the processor executes the program, it implements the aforementioned grid resource management method; to avoid repetition, this will not be described again here. Alternatively, the electronic device can implement the functions of each module in this embodiment of the grid resource management device; this will also not be described again here.

[0089] This invention also provides a readable storage medium storing a program. When the program is executed by a processor, it implements the aforementioned grid resource management method. To avoid repetition, this will not be described again here. Alternatively, when the program is executed by a processor, it implements the functions of each module in this embodiment of the grid resource management device, which will also not be described again here.

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

[0091] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0092] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is used as an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

Claims

1. A method for managing grid resources, characterized in that, include: Receive a grid usage request from a service provider, the grid usage request including at least the service type and usage period; Based on the allocable time period of the grid and the service type that the allocable time period is adapted to, candidate grids that meet the grid usage request are filtered. The target cell is determined from the candidate cells; Assign the business party the right to use the target grid during the usage period.

2. The grid resource management method according to claim 1, characterized in that, Before receiving the grid usage request from the service provider, the method further includes: Create at least two logical cells for each cell, and each logical cell is uniquely bound to one business type; Configure non-overlapping allocatable time periods for each logical cell in each cell.

3. The grid resource management method according to claim 1, characterized in that, The process of filtering candidate grids that meet the grid usage request based on the allocable time slots and the service types adapted to the allocable time slots includes: Analyze the business type, usage period, and inherent attribute requirements of the grid usage request; Based on the correlation between the allocable time slots of the grid and the adapted business type, grids that are adapted to the business type and whose allocable time slots include the usage time slots are selected. Verify whether the selected grid cells meet the inherent attribute requirements of the grid cells, and retain the grid cells that meet the inherent attribute requirements as candidate grid cells.

4. The grid resource management method according to claim 1, characterized in that, Determining the target cell from the candidate cells includes: Collect resource status data for each candidate grid; The resource status data is weighted and calculated based on the load balancing algorithm to generate a priority score; Sort the candidate cells by score from highest to lowest, and select the highest-scoring candidate cell as the target cell.

5. The grid resource management method according to claim 1, characterized in that, After allocating usage rights for the target grid to the service provider during the usage period, the method further includes: Monitor the business execution status of the target grid and the expiration of the usage period; If the business operation is detected to be completed or the usage period expires, the binding relationship between the target grid and the current business is released.

6. The grid resource management method according to claim 1, characterized in that, The grid usage request also includes a reservation mode parameter, and the filtering of candidate grids that match the grid usage request further includes: The booking mode parameters are analyzed to determine the booking type, which includes periodic booking; Extract the periodic rules and time period repetition range, and verify whether the allocable time period of the grid is compatible with the periodic rules; Retain the grid cells that fit the cycle rule as candidate grid cells.

7. The grid resource management method according to claim 1, characterized in that, Also includes: Monitor abnormal events during the use of the grid; If an abnormal event is detected, all operations on the grid should be immediately suspended, and an abnormality alert notification should be sent to the business party. Based on a preset exception handling mechanism, the abnormal events of the grid are handled. After the abnormal event is resolved, all operations on the grid are restarted.

8. A grid resource management device, characterized in that, include: The receiving module is used to receive grid usage requests from service providers, and the grid usage requests include at least the service type and usage period. The filtering module is used to filter candidate grids that meet the grid usage request based on the grid's allocable time period and the service type adapted to the allocable time period. A determining module is used to determine the target cell from the candidate cells; The allocation module is used to allocate usage rights of the target grid to the business party during the usage period.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the grid resource management method as described in any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the grid resource management method as described in any one of claims 1 to 7.

Images