A baggage release control method, device, storage medium and program product

Abstract

The application provides a checked baggage grading release control method, device, storage medium and program product, which are used for solving the problem of checked baggage release efficiency reduction caused by insufficient downstream processing capacity during airport check-in peak period. The method establishes the association between the checked baggage session and the flight cut-off time limit, obtains the counter and downstream processing link state data in real time, calculates the key parameters such as the maximum waiting time of the baggage and the downstream acceptable recovery time, and generates a dynamic release scheme including five grading strategies such as immediate release, timed waiting release and the like. Through the continuous monitoring and dynamic adjustment mechanism, the system accurately controls the release time when the downstream processing capacity fluctuates, avoids improper waiting on the adjacent cut-off baggage, and relieves the downstream congestion. The method improves the operation reliability and processing efficiency of the airport checked baggage system, and reduces the risk of baggage missing the flight and the need for manual intervention.

Description

Technical Field

[0001] This application relates to the field of smart airport and baggage automation technology, and in particular to a baggage release control method, device, storage medium and program product. Background Technology

[0002] With the continuous growth of air passenger traffic, airports have generally deployed self-service or manual baggage check-in equipment in check-in areas to improve the efficiency of front-end baggage reception and processing. In some related technologies, front-end baggage check-in equipment mainly focuses on the identification, size and weight detection, and tag reading of individual pieces of baggage. After completing the above detection and verification, the standard control logic of the system is to immediately drive the counter conveyor belt to release the received baggage instantly, allowing it to flow directly into the downstream security screening equipment and the main baggage handling conveyor chain in a single cycle.

[0003] However, during peak check-in periods when flights are concentrated, downstream security screening equipment or transitional conveyor lines often experience short-term fluctuations in processing capacity and localized congestion due to excessive instantaneous reception volume.

[0004] To alleviate this downstream congestion, the common technical intervention is to directly suspend all baggage check-in counters' receiving or release sessions at the front end. However, this blanket suspension can easily lead to excessive delays for baggage nearing its flight's loading deadline, causing it to miss the final loading deadline. This increases the probability of missed flights, requiring subsequent manual emergency intervention and special retrieval, thus lowering the overall reliability of the airport's baggage check-in system and the passenger experience. Summary of the Invention

[0005] This application provides a baggage release control method, device, storage medium, and program product for improving the efficiency of airport baggage check-in systems.

[0006] Firstly, this application provides a method for tiered release control of checked baggage, comprising: establishing a current check-in session and associating the current check-in session with the cut-off time of the flight to which the current checked baggage belongs; acquiring counter status data and target processing link status data corresponding to the current check-in session; determining the downstream acceptable recovery time and / or acceptable capacity of the target processing link within a preset time domain based on the target processing link status data; determining the waiting limit of the current check-in session based on the current time, the cut-off time, and the estimated duration for the current check-in session to complete downstream processing; and generating a release control for the current check-in session based on the downstream acceptable recovery time and / or acceptable capacity, the waiting limit, and the counter status data. The release control strategy includes at least one of the following: immediate release, timed waiting release, priority release, candidate channel reassignment, and manual takeover, and generates a corresponding release window or release conditions; the release control strategy is converted into counter human-machine interface control signals and / or transmission control signals to control the moment when the current checked baggage enters the target processing link; the counter status data and target processing link status data are continuously updated during the waiting period, and the release control strategy is adjusted when the update results meet the preset upgrade conditions. The waiting period is the time from the issuance of the waiting control instruction to the arrival of the release window or the release control strategy being adjusted to priority release, candidate channel reassignment, or manual takeover when the release control strategy is timed waiting release.

[0007] In the above embodiment, the system calculates the maximum waiting time for the current baggage check-in session based on the difference between the cut-off time and the current time, after deducting the estimated downstream processing time and safety margin. Baggage is classified as urgent when this maximum is less than or equal to zero. This transforms the time constraint for each baggage check-in session from a static flight cut-off time to a dynamic waiting window, allowing the system to consider both downstream processing time and remaining time margin when making release decisions. This provides a quantified time boundary for the tiered release strategy and avoids imposing inappropriate waiting control on baggage nearing its cut-off time.

[0008] In conjunction with some embodiments of the first aspect, in some embodiments, the estimated duration of downstream processing is determined based on the current time, the cut-off time limit, and the current shipping session, and the upper limit of the waiting time for the current shipping session is determined. Specifically, this includes: obtaining the estimated downstream processing time from the time the current baggage is received from the current check-in counter to the completion of the security check and sorting processes in the target processing link; subtracting the estimated downstream processing time and a preset safety time margin from the time difference between the cut-off time limit and the current time to obtain the upper limit of the waiting time for the current shipping session, where the safety time margin is used to compensate for transportation fluctuations and abnormal processing time; when the upper limit of the waiting time is less than or equal to zero, it is determined that the current baggage is in an emergency state nearing the cut-off time.

[0009] In the above embodiments, the system calculates the time difference between the cut-off time and the current time, subtracts the estimated downstream processing time and a preset safety margin, to obtain the maximum tolerable dwell time of the current baggage check-in session at the counter. By introducing a session-level time constraint of a waiting limit, the judgment dimension of the release decision is expanded from a single dimension of downstream link status to a three-dimensional space of "downstream status - flight time limit - processing time". This enables the system to identify the differentiated fault tolerance capabilities of different baggage in the time dimension, establishes a quantitative basis for differentiated release strategies, and reduces the risk of baggage nearing the cut-off time missing its flight due to blind waiting.

[0010] In conjunction with some embodiments of the first aspect, in some embodiments, a release control strategy for the current baggage check-in session is generated based on the downstream acceptable recovery time and / or acceptable capacity, the waiting limit, and counter status data. Specifically, this includes: calculating the recommended release start point for the current baggage, where the recommended release start point is the maximum value between the current time, the downstream acceptable recovery time, and the channel switching compensation time; if the recommended release start point is not later than the sum of the current time and the waiting limit, and the counter status data indicates that the current counter has the acceptance conditions, a timed waiting release strategy is generated, and the recommended release start point is used as the start time of the release window; if the recommended release start point is later than the sum of the current time and the waiting limit, or the counter status data indicates that the current counter does not have the acceptance conditions, a priority release, candidate channel reassignment, or manual takeover strategy is generated; if the acceptable capacity of the target processing link is within a preset safety range at the current time, and the current counter has the acceptance conditions, an immediate release strategy is generated.

[0011] In the above embodiments, the system generates one of the following strategies based on the time relationship between the recommended release start point and the waiting limit, combined with the current counter's acceptance conditions: immediate release, timed waiting release, priority release, candidate channel reassignment, or manual takeover. By using downstream acceptance recovery time, session waiting limit, and counter status data as decision inputs, a multi-dimensional strategy generation logic is constructed: when the recommended release start point falls within the waiting range and the counter has acceptance conditions, the system generates a timed waiting strategy to stagger downstream load; when the recommended release start point exceeds the waiting limit or the counter does not have acceptance conditions, the system generates a priority release, channel reassignment, or manual takeover strategy to ensure the processing of time-sensitive baggage. This hierarchical decision-making transforms release control from a global pause to refined management, alleviating downstream congestion while reducing the probability of missed flights for baggage nearing catch-up.

[0012] In conjunction with some embodiments of the first aspect, in some embodiments, the release control strategy is converted into counter human-machine interface control signals and / or transmission control signals, specifically including: when the release control strategy is timed waiting for release, issuing a waiting instruction to the programmable logic controller and / or human-machine interface of the current check-in counter; controlling the human-machine interface to display a prompt message including the reason for waiting and the remaining countdown; temporarily locking the physical release button function of the current check-in counter through the programmable logic controller, and / or delaying the start action of the baggage conveyor belt after successful barcode scanning; synchronously controlling the status indicator light of the current check-in counter to switch to a preset waiting color indicator; when the start time of the release window is reached, automatically unlocking the physical release button function or starting the baggage conveyor belt, and closing the prompt message.

[0013] In the above embodiment, after generating a timed waiting release strategy, the system issues a waiting instruction to the programmable logic controller of the current check-in counter. This involves temporarily locking the physical release button or delaying the start of the baggage conveyor belt. Simultaneously, the system controls the human-machine interface to display a message including the reason for the wait and the remaining countdown. Upon reaching the start time of the release window, the system automatically unlocks or starts the conveyor belt. The physical button locking or conveyor belt delay mechanism prevents inappropriate release operations at the hardware level. The countdown message provides transparent feedback to operators regarding the reason for the wait and the remaining time. The automatic unlocking or starting mechanism further eliminates the uncertainty of manual judgment regarding the timing of resumption, raising the timing control precision of strategy execution to the level of system automation and reducing release timing deviations.

[0014] In conjunction with some embodiments of the first aspect, in some embodiments, the downstream acceptable recovery time and / or acceptable capacity of the target processing link within a preset time domain is determined based on the target processing link status data. Specifically, this includes: collecting the trigger frequency of the conveyor photocells, the occupancy status of the security checkpoint entrance, and the number of baggage staying in the transition conveyor area of ​​the target processing link according to a preset time window, and generating a historical processing capacity time series; inputting the historical processing capacity time series and the current flight centralized check-in information into a pre-trained traffic prediction model; outputting the expected processing rate of the target processing link within a preset short-term window in the future through the traffic prediction model, and identifying the time point when the expected processing rate falls below a preset safe load threshold, and determining this time point as the downstream acceptable recovery time.

[0015] In the above embodiment, the system inputs the generated historical processing capacity time series and the current flight check-in information into a pre-trained traffic prediction model, outputting the expected processing rate of the target processing link within a preset short-term window in the future, thereby determining the downstream acceptance recovery time. This embodiment, by introducing a traffic prediction model, transforms the downstream status assessment from a static "whether there is current congestion" to a dynamic "when can acceptance be restored," enabling the system to obtain a temporal expectation of downstream processing capacity when generating a release control strategy. This provides a quantitative basis for waiting time for the timed waiting release strategy, improving the accuracy of release timing selection.

[0016] In conjunction with some embodiments of the first aspect, in some embodiments, the counter status data and target processing link status data are continuously updated during the waiting period, and the release control strategy is adjusted when the update result meets the preset upgrade conditions. Specifically, this includes: during the timed waiting period for release, if the target processing link status data is detected to deteriorate, causing the downstream acceptable recovery time to be delayed, and the recommended release start point after the delay is later than the sum of the current time and the waiting limit, then the preset upgrade conditions are met, and the release control strategy is upgraded from timed waiting release to priority release or candidate channel reassignment; during the timed waiting period for release, if the number of people queuing in front of the current shipping counter or the queue length in the counter status data exceeds the preset congestion threshold, or the receiving conveyor belt is approaching full load, then the preset upgrade conditions are met, the current waiting state is revoked, and priority release or manual takeover is triggered.

[0017] In the above embodiments, the system establishes a continuous status monitoring and strategy reassessment mechanism during the waiting period, transforming the release control from a static "fixed upon issuance" mode to an adaptive "continuous tracking-dynamic adjustment" mode: when the downstream status deteriorates to the point that the original waiting time no longer meets the time constraint, the system promptly terminates the waiting and triggers priority release or channel reassignment; when the backlog at the counter reaches a threshold, the system cancels the waiting to prevent further congestion. This dynamic adjustment provides the system with a second decision-making opportunity during the waiting period, reducing inappropriate waiting caused by prediction bias in the initial decision basis or sudden environmental changes, and improving the robustness of release control in complex dynamic environments.

[0018] In conjunction with some embodiments of the first aspect, in some embodiments, when the release control strategy includes candidate channel reassignment, the method further includes: acquiring real-time status data and downstream prediction data of multiple candidate channels adjacent to the current check-in counter or located on the same check-in island; calculating the downstream acceptable recovery time and the corresponding estimated queuing waiting time for each candidate channel; selecting candidate channels whose sum of estimated queuing waiting time and downstream acceptable recovery time meets the waiting limit of the current check-in session; and issuing a reassignment instruction to the human-computer interaction interface to guide passengers to the selected optimal candidate channel for check-in.

[0019] In the above embodiments, the system improves the channel reassignment decision-making based on "queueing time - downstream expectations - time constraints" through a multi-dimensional evaluation mechanism for candidate channels. It not only examines the current queuing status of candidate channels, but also combines the future acceptability of its downstream links and the waiting limit of the current session to select the optimal channel that can avoid excessively long queues at the front end and meet the timely processing needs of downstream channels. This expands load diversion from single-point adjustment at the counter level to collaborative optimization at the check-in island level, ensuring the timely processing of time-sensitive baggage while improving the utilization rate of the entire check-in area's processing capacity.

[0020] In a second aspect, embodiments of this application provide a baggage classification and release control device, which includes: one or more processors and a memory; the memory is coupled to the one or more processors, and the memory is used to store computer program code, which includes computer instructions, and the one or more processors call the computer instructions to cause the baggage classification and release control device to perform the method described in the first aspect and any possible implementation thereof.

[0021] Thirdly, embodiments of this application provide a computer program product containing instructions that, when the computer program product is run on a baggage classification and release control device, cause the baggage classification and release control device to perform the method described in the first aspect and any possible implementation thereof.

[0022] Fourthly, embodiments of this application provide a computer-readable storage medium including instructions that, when executed on a baggage classification and release control device, cause the baggage classification and release control device to perform the method described in the first aspect and any possible implementation thereof.

[0023] Understandably, the baggage classification and release control device provided in the second aspect, the computer program product provided in the third aspect, and the computer storage medium provided in the fourth aspect are all used to execute the methods provided in the embodiments of this application. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.

[0024] One or more technical solutions provided in the embodiments of this application have at least the following technical effects or advantages:

[0025] 1. This application establishes a session-level waiting limit calculation mechanism, which incorporates the cut-off time limit, the expected downstream processing time, and the safety margin into the release decision. This avoids imposing inappropriate waiting control on baggage near the cut-off time limit, thereby reducing the risk of missed loading time due to blind global suspension of baggage and improving the operational reliability of the airport baggage check-in system.

[0026] 2. This application introduces a downstream acceptable recovery time prediction and tiered release strategy generation mechanism to transform release control into time-constrained differentiated management, enabling the system to alleviate congestion in downstream security checks and transport links while ensuring priority processing of time-sensitive baggage, thus reducing the need for manual emergency intervention.

[0027] 3. This application establishes an adaptive closed-loop control mechanism by continuously monitoring the status of the counter and downstream during the waiting period and dynamically adjusting the release strategy. When the downstream status deteriorates or the front-end backlog exceeds the limit, the waiting is terminated in a timely manner and priority release or channel reassignment is triggered, which improves the robustness of release control and passenger experience during peak check-in periods. Attached Figure Description

[0028] Figure 1 This is a flowchart illustrating a graded release control method for checked baggage in an embodiment of this application;

[0029] Figure 2 This is a schematic diagram of the physical device structure of a baggage classification and release control device in the embodiments of this application. Detailed Implementation

[0030] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification of this application, the singular expressions “a,” “an,” “the,” “the,” and “this” are intended to include the plural expressions as well, unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in this application refers to any or all possible combinations including one or more of the listed items.

[0031] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0032] The following describes the process of the method provided in this implementation. Please refer to [link / reference]. Figure 1 This is a flowchart illustrating a graded release control method for checked baggage in an embodiment of this application.

[0033] S101. Establish the current baggage check-in session and associate the current baggage check-in session with the cut-off time of the flight to which the current baggage belongs.

[0034] A baggage check-in session refers to the complete business process from when a passenger initiates a baggage check-in request until the baggage is released at the counter or the session expires. It includes a logical set of operations such as passenger identity verification, baggage weighing and inspection, tag printing and binding, and release control. The cut-off time is the last moment, as determined by the airline or airport's operational support rules, when a flight stops accepting checked baggage. This is typically 30 to 45 minutes before the scheduled flight departure time, ensuring sufficient time for subsequent security checks, sorting, and loading operations. Session association involves binding and storing the unique identifier of the current baggage check-in session with information such as baggage tag, counter number, flight number, and cut-off time, so that subsequent stages can trace the time constraints of that baggage.

[0035] Specifically, after receiving a trigger signal through the counter's human-machine interface or programmable logic controller, the system generates a unique session identifier (such as a UUID format) in a local or cloud database. It then queries the Airport Operations Database (AODB) in real time to determine the scheduled departure time of the flight to which the baggage belongs. Combining this with the airport's local check-in rules table or the airline's cut-off rule library, the system calculates the flight's cut-off time stamp. For example, if a flight is scheduled to depart at 11:00, and the rule library specifies a cut-off time of 40 minutes before departure, the system automatically calculates and stores the cut-off time as 10:20. Simultaneously, the session identifier is bound to a triplet of the counter ID, baggage tag number, and passenger ID number hash value, written to the session status table, and a session timeout duration is set (typically 300 seconds). If the baggage is not released before the timeout, the session resources are automatically released and an exception log is recorded.

[0036] S102. Obtain the counter status data and target processing link status data corresponding to the current shipping session.

[0037] The counter status data refers to a multi-dimensional set of real-time information reflecting the current operational status and front-end acceptance capacity of the baggage check-in counter. This includes fields such as the number of people queuing or the queue length, the occupancy status of the receiving conveyor belt, the status of the physical release button, counter malfunction or emergency stop status, manual or self-service mode identification, and the current status of the human-machine interface. The target processing link status data refers to the real-time operating parameters of the downstream conveyor channels, security equipment, and sorting systems that the checked baggage is expected to enter. This includes information such as the trigger frequency of the conveyor's photocells, the occupancy status of the security scanner entrance, the number of baggage items remaining in the transition conveyor area, and congestion signs at the sorting port. This data is used to assess the instantaneous processing capacity and congestion level of the downstream link.

[0038] This step is triggered immediately after the session is successfully established, ensuring that subsequent decisions are based on the latest status. Specifically, the system collects status information through the following multi-source data interfaces: the number of people queuing at the counter is counted in real time by a depth camera installed above the counter, and the queue length is measured by a ground pressure sensor array or a laser rangefinder; the occupancy status of the receiving conveyor belt is determined by photoelectric sensors deployed at both ends of the conveyor belt, and when the photoelectric sensor is continuously blocked for more than a threshold, it is marked as fully loaded; the status of the physical release button and the counter emergency stop status are directly read from the digital input register of the programmable logic controller (PLC); the manual or self-service mode identifier and the HMI page status are obtained by communicating with the human-machine interface via OPC UA or Modbus TCP protocol to obtain status bits.

[0039] For target processing link status data, the system first queries the default downstream channel number based on the current counter configuration table, and then subscribes to the status messages of each key node device within that channel through the Baggage Handling System (BHS) SCADA interface, with a typical sampling period of 1 second. For example, if counter A is connected to conveyor channel 3 by default, the system collects parameters in real time such as the photocell frequency at the entrance of channel 3, the occupancy flag of the X-ray scanning chamber of the downstream security inspection machine, and the photocell count difference between the transition section from channel 3 to channel 4 (used to estimate the number of items remaining). When conflicts occur between multi-source data (e.g., the camera counts 3 people but the ground sensor shows 2), the system uses a confidence-weighted fusion algorithm to prioritize the data source with higher historical accuracy. The core of this multi-dimensional status perception is to transform the abstract concepts of "whether the counter is accepting" and "whether the downstream is congested" into a quantifiable and real-time updatable multi-field status vector, providing accurate decision input for the subsequent generation of tiered release strategies and avoiding decision-making errors caused by lagging or incomplete status information.

[0040] S103. Based on the target processing link status data, determine the downstream acceptable recovery time and / or acceptable capability of the target processing link within the preset time domain.

[0041] The downstream acceptable recovery time refers to the future point in time when the target processing link, due to current congestion or high load, is expected to see its processing rate drop below a preset safe load threshold and be able to stably accept new baggage again, expressed as a timestamp. Acceptable capacity refers to the level of ability of the target processing link to accept new baggage at the present or a future time, expressed as a percentage (e.g., current acceptable capacity 60%), discrete levels (e.g., high / medium / low), or remaining capacity in the number of pieces. The preset time domain refers to the length of the future time window for the system to predict the downstream status, typically 5 to 15 minutes, used to balance prediction accuracy and computational response speed.

[0042] This step is executed immediately after acquiring the target processing link status data, providing a time-series expectation basis for subsequent release timing decisions. Specifically, the system collects historical operational data of each key node in the target processing link according to a preset time window (e.g., the past 10 minutes): the trigger frequency of the conveyor photocells reflects the number of items passing through per unit time; the duration of occupancy at the security checkpoint entrance reflects the degree of security processing bottlenecks; and the number of baggage staying in the transition conveyor area is calculated by the difference between the photocell counts at the entrance and exit. The above multi-dimensional time series data is organized into a historical processing capacity time series matrix at a fixed sampling interval (e.g., 10 seconds). At the same time, information such as the centralized check-in opening time and the expected number of check-in passengers for each flight in the current period is obtained from the airport's AODB system as input for external influencing factors.

[0043] The system inputs historical processing capacity time series and flight check-in information into a pre-trained traffic prediction model. This model can employ an LSTM (Long Short-Term Memory) network, a Temporal Convolutional Network (TCN), or an XGBoost-based ensemble learning model, and has already completed training and hyperparameter tuning using historical data in the offline phase. The model outputs the projected processing rate curve for each moment within a preset short-term window (e.g., the next 10 minutes). The system identifies the point on the curve where the processing rate first drops below a preset safe load threshold (e.g., 70% of the link's designed processing capacity) and marks this point as the downstream acceptable recovery point.

[0044] For example, if the current time is 10:05, and the model predicts that the processing rate will drop from the current 95% to 65% at 10:12, then the recovery time is determined to be 10:12. If the model cannot consistently output the recovery time (e.g., high load throughout the prediction window), the system degenerates to only outputting the current acceptable capacity level, and the policy generation module directly determines whether to allow immediate passage or wait based on the capacity level. This recovery time calculation based on the prediction model enables the system to provide a quantitative basis for the waiting time for the timed waiting release policy.

[0045] In some preferred embodiments, the above steps specifically include:

[0046] Collect data on the trigger frequency of photoelectric sensors on conveyors, the occupancy status of security check machine entrances, and the number of luggage items staying in the transition conveyor area in the target processing link according to a preset time window, and generate a historical processing capacity time series.

[0047] Input the historical processing capacity time series and the current flight centralized check-in information into the pre-trained traffic prediction model;

[0048] The traffic prediction model outputs the expected processing rate of the target processing link within a preset short window in the future, and identifies the time point when the expected processing rate drops below a preset safe load threshold, and determines this time point as the downstream acceptable recovery time.

[0049] Specifically, the system collects historical operational data for each key node in the target processing link according to a preset time window (e.g., the past 10 minutes): the trigger frequency of the conveyor photocells reflects the number of items passing through per unit time; the duration of occupancy at the security checkpoint entrance reflects the degree of bottleneck in security processing; and the number of baggage staying in the transition conveyor area is calculated by the difference between the photocell counts at the entrance and exit. This multi-dimensional time-series data is then organized into a historical processing capacity time-series matrix at fixed sampling intervals (e.g., 10 seconds). Simultaneously, information such as the centralized check-in opening time and estimated check-in volume for each flight within the current time period is obtained from the airport's AODB system as input for external influencing factors.

[0050] The system inputs historical processing capacity time series and flight check-in information into a pre-trained traffic prediction model. This model can employ an LSTM (Long Short-Term Memory) network or a Temporal Convolutional Network (TCN), and has already been trained offline using historical data. The model outputs the projected processing rate curve for each moment within a preset short-term window (e.g., the next 10 minutes). The system identifies the point on the curve where the processing rate first drops below a preset safe load threshold (e.g., 70% of the link's designed processing capacity) and marks this point as the downstream acceptable recovery point.

[0051] For example, if the current time is 10:05 and the model predicts that the processing rate will drop from the current 95% to 65% at 10:12, then the recovery time is determined to be 10:12. If the model cannot stably output the recovery time (e.g., high load throughout the prediction window), the system degenerates to only output the current acceptable capacity level, and the policy generation module directly determines whether to allow immediate passage or wait based on the capacity level.

[0052] S104. Determine the maximum waiting time for the current shipping session based on the current time, the cut-off time limit, and the estimated time for the current shipping session to complete downstream processing.

[0053] The maximum acceptable waiting time refers to the maximum duration that checked baggage can be tolerated to remain or wait at the counter. It is calculated using the cut-off time, the current time, the estimated downstream processing time, and a safety margin, defining the baggage's tolerance boundary in the time dimension. The estimated downstream processing time refers to the total expected time from baggage receipt at the current check-in counter until it completes security checks and sorting in the target processing chain and enters the loading-ready state. This includes the sum of the times for each stage, such as transport time, security scanning time, and sorting action time. This step is executed immediately after obtaining the cut-off time and the current time, establishing a personalized time constraint awareness for each check-in session.

[0054] In some preferred embodiments, the above steps specifically include: obtaining the estimated downstream processing time from the time the current checked baggage is received from the current check-in counter to the completion of the security check and sorting process in the target processing link;

[0055] The waiting limit for the current shipment session is obtained by subtracting the estimated downstream processing time and the preset safety time margin from the time difference between the cut-off deadline and the current time. The safety time margin is used to compensate for transportation fluctuations and the time consumed in handling abnormalities.

[0056] When the maximum waiting time is less than or equal to zero, the current checked baggage is determined to be in an emergency state nearing its loading deadline.

[0057] Among them, the safety time margin refers to the redundant time reserved when calculating the upper limit of waiting time, which is used to absorb the extra time caused by abnormal factors such as fluctuations in conveying speed, temporary equipment failures, and manual secondary inspections. The typical value is 5 to 10 minutes before the cut-off time.

[0058] Specifically, the system first queries the historical statistics database or real-time simulation model of the baggage handling system to obtain the estimated downstream processing time for the current checked baggage to complete security check and sorting from the current counter to the target processing link. If this time cannot be obtained from the real-time interface, the system falls back to using the moving average of the actual processing times of the most recent N sessions (e.g., the most recent 20) of the same channel, or uses the historical average processing time of the same channel during the same time period as a substitute. The calculation formula is: Waiting limit = (Cut-off time limit - Current time) - Estimated downstream processing time - Safety time margin.

[0059] For example, if the cut-off time for a certain piece of baggage is 10:20, the current time is 10:00, the estimated downstream processing time is 12 minutes, and the safety time margin is set to 5 minutes, then the maximum waiting time = (10:20 - 10:00) - 12 minutes - 5 minutes = 3 minutes. This means the baggage can wait at the counter for a maximum of 3 minutes. When the calculated result is less than or equal to zero, the system determines that the baggage is in an emergency state nearing the cut-off time. In the subsequent strategy generation module, it will prohibit the baggage from entering the timed waiting release strategy and directly trigger priority release or manual intervention to ensure that the baggage immediately enters the downstream processing flow. This calculation mechanism transforms the flight cut-off time into a dynamic, remaining available time after deducting necessary processing time. This allows the system to identify the differentiated fault tolerance capabilities of different baggage in the time dimension, establishing a quantified time boundary for the tiered release strategy.

[0060] S105. Based on the downstream acceptable recovery time and / or acceptable capacity, waiting limit and counter status data, generate the release control policy for the current shipping session. The release control policy includes at least one of the following: immediate release, timed waiting release, priority release, candidate channel reassignment and manual takeover, and generate a corresponding release window or release conditions.

[0061] The recommended release start point refers to the optimal baggage release time suggested by the system after comprehensively considering the downstream recovery time and channel switching compensation time. It guides the setting of the time window for the timed waiting release strategy. The channel switching compensation time refers to the additional time required for operations such as conveyor path change and equipment handshake synchronization when baggage needs to be switched from the current default channel to an alternative channel. The typical value is 10 to 30 seconds. The counter acceptance condition refers to the comprehensive status judgment result of the current counter being able to continue to receive or wait for baggage. It includes the logical and calculation results of multiple sub-conditions such as the counter not being in a fault or emergency stop state, the receiving conveyor belt not being fully loaded, the queue length not exceeding the limit, and the HMI interface being in a normal interactive page.

[0062] This step is triggered after obtaining data on the downstream acceptable recovery time, the maximum waiting time, and the counter status. It is the core decision-making step in the entire tiered release control logic.

[0063] In some preferred embodiments, the above steps specifically include:

[0064] Calculate the recommended release point for the current checked baggage. The recommended release point is the maximum value of the current time, the downstream acceptable recovery time, and the channel switching compensation time.

[0065] If the recommended release start point is not later than the sum of the current time and the waiting limit, and the counter status data indicates that the current counter has the conditions for acceptance, then a timed waiting release strategy is generated, and the recommended release start point is used as the start time of the release window.

[0066] If the recommended release start point is later than the sum of the current time and the waiting limit, or if the counter status data indicates that the current counter does not meet the acceptance conditions, a priority release, candidate channel reassignment, or manual takeover strategy will be generated.

[0067] If the current processing capacity of the target processing link is within the preset safety range and the current counter meets the acceptance conditions, an immediate release policy is generated.

[0068] Specifically, the system calculates the recommended release start point, taking the larger value between the current time and (downstream acceptable recovery time + channel switching compensation time) to ensure that the release time is neither earlier than the current time nor earlier than the earliest feasible time when downstream acceptance resumes. Subsequently, the strategy is determined according to the following priority sequence:

[0069] First priority: If the current acceptance capacity of the target processing link is within the preset safety range (e.g., acceptance capacity ≥ 70%) and the counter status data indicates that the current counter has the acceptance conditions, then an immediate release policy is generated, and the system directly issues the release instruction without waiting.

[0070] The second priority is to generate a timed waiting release strategy if the recommended release start point is not later than (current time + waiting limit) and the counter has the acceptance conditions. The recommended release start point is used as the start time of the release window, and the waiting time is calculated as the basis for the countdown display.

[0071] The third priority is if the recommended release start point is later than (current time + waiting limit), indicating that even waiting until downstream recovery will exceed the time tolerance range for the baggage, or if the counter status data indicates that the current counter does not have the conditions to accept it (e.g., the receiving conveyor is full, the counter is in emergency). In this case, the system will select one of the following three strategies: priority release, candidate channel reassignment, or manual takeover: When the target processing link is congested but can be restored in a short time and there are no available candidate channels, the priority release strategy will be generated first, and the baggage will be given a higher downstream processing priority to bypass part of the queue; when there are available candidate channels and the passenger is willing to be reassigned, the candidate channel reassignment strategy will be generated; when none of the above conditions are met or the baggage is in an emergency, the manual takeover strategy will be generated, and the check-in supervisor will intervene to handle the situation.

[0072] Each strategy corresponds to a different release window or release condition: immediate release corresponds to the current time, timed release corresponds to a specific future time and countdown, priority release corresponds to the downstream priority identifier, candidate channel reassignment corresponds to the target channel number, and manual takeover corresponds to the check-in supervisor's employee number and takeover reason code. This hierarchical decision-making logic based on multi-dimensional input extends release control to five levels of refined management: the system immediately releases passengers when downstream is idle to improve efficiency, waits for a period of time when there is short-term congestion downstream but there is still time for luggage to avoid peak load, prioritizes release or reassignment when time is tight to ensure time limits, and manually takes over in extreme cases to mitigate risks.

[0073] S106. Convert the release control strategy into counter human-machine interface control signals and / or transmission control signals to control the timing of the current checked baggage entering the target processing link.

[0074] Among them, the counter human-machine interface control signals refer to the digital instructions sent by the system to the human-machine interface (HMI) of the baggage check-in counter to control the content displayed on the interface, the interactive logic, and the status prompts. These include control fields such as displaying text content, countdown values, button enable status, and triggering prompt sounds. The conveyor control signals refer to the discrete or analog signals sent by the system to the programmable logic controller (PLC) or distributed I / O module of the baggage check-in counter to control hardware actions such as starting and stopping the baggage conveyor belt, locking physical buttons, and changing the color of status indicator lights. These signals are usually implemented through Modbus TCP, OPC UA, or hardwired digital outputs.

[0075] This step is executed immediately after the release control strategy is generated, and it is responsible for translating the abstract strategy decision into physical actions that can be performed by field equipment.

[0076] In some preferred embodiments, the above steps specifically include:

[0077] When the release control strategy is timed waiting release, a waiting instruction is sent to the programmable logic controller and / or human-machine interface of the current check-in counter;

[0078] The human-computer interaction interface displays a prompt message including the reason for the wait and the remaining countdown.

[0079] The physical release button function of the current check-in counter is temporarily locked by the programmable logic controller, and / or the start action of the baggage conveyor belt is delayed after the successful scanning of the code;

[0080] Synchronously control the status indicator light of the current check-in counter to switch to the preset waiting color indicator;

[0081] When the start time of the clearance window is reached, the physical clearance button will be automatically unlocked or the baggage conveyor belt will be started, and the notification message will be turned off.

[0082] Specifically, when the release control strategy is timed waiting release, the system sends a waiting instruction to the PLC of the current check-in counter. This instruction includes parameters such as the waiting duration, the timestamp of the release window start time, and the strategy identifier, which are implemented by writing them into the PLC's holding register. After receiving the instruction, the PLC temporarily locks the physical release button function through internal logic. This is achieved by disabling the interrupt response of the button signal or inserting an interlock condition in the ladder logic. For self-service counters, the PLC can also delay the start action of the baggage conveyor belt after successful barcode scanning. That is, after detecting successful barcode scanning of the baggage tag, the conveyor belt motor is not started immediately, but waits until the start time of the release window before starting.

[0083] Meanwhile, the system sends interface update commands through the communication interface with the HMI (such as TCP Socket or serial port), controlling the HMI to display a prompt message in the main display area that includes the reason for waiting (such as "Downstream security inspection equipment is busy, please wait") and the remaining countdown (such as "Remaining waiting time: 02:35"). The countdown value is updated locally by the HMI every second, or the remaining seconds are periodically pushed by the background system. At the same time, the system controls the status indicator lights of the counter (usually three-color LED light pillars) to switch to the preset waiting color indicator (such as yellow solid or flashing), and drives the indicator light circuit through the digital output port of the PLC or the relay module.

[0084] When the system's internal clock or PLC timer detects that the start time of the release window has been reached, the PLC automatically releases the interlock condition of the physical release button or directly starts the baggage conveyor motor. The HMI synchronously shuts down the waiting prompt message and returns to the normal operation interface, and the status indicator light switches back to green to indicate the ready state.

[0085] For the candidate channel reassignment strategy, the system sends a graphic instruction to the HMI containing the target channel number, reassignment guidance route diagram, and estimated walking time. For the manual takeover strategy, the system triggers a pop-up alarm on the duty supervisor's workstation and pushes session details and suggested handling measures. This design, which converts strategies into multi-level control signals, improves the execution accuracy of release timing control to the level of system automation through both hardware (PLC button locking, conveyor belt delayed start) and software (HMI interface prompts, countdown display) methods.

[0086] S107. During the waiting period, continuously update the counter status data and target processing link status data, and adjust the release control strategy when the update results meet the preset upgrade conditions. The waiting period is the time from the issuance of the waiting control instruction to the arrival of the release window or the release control strategy being adjusted to priority release, candidate channel reassignment, or manual takeover when the release control strategy is timed waiting release.

[0087] The waiting period refers to the time from the moment the system issues the waiting control instruction to the counter after the release control strategy is set to timed waiting release, until the start time of the release window arrives, or the strategy is adjusted in advance to priority release / candidate channel reassignment / manual takeover. During this period, the baggage remains in the counter waiting-to-release state, the conveyor belt is not started, or the release button is locked. The preset upgrade conditions refer to the set of state change thresholds that trigger the system to re-evaluate and adjust the current release control strategy. These include quantitative judgment criteria for various scenarios such as the downstream acceptable recovery time being delayed beyond the tolerance range, the queue length at the counter exceeding the limit, the receiving conveyor belt being fully loaded, and the downstream link recovering ahead of schedule.

[0088] This step continues to run after entering the timed waiting state for release, providing the system with a second decision opportunity to respond to dynamic changes in the environment.

[0089] In some preferred embodiments, the above steps specifically include:

[0090] If, during the timed waiting period for release, the target processing link status data is detected to deteriorate, causing the downstream acceptable recovery time to be delayed and the recommended release start point after the delay is later than the sum of the current time and the waiting limit, then the preset upgrade conditions are met, and the release control strategy is upgraded from timed waiting release to priority release or candidate channel reassignment.

[0091] During the timed waiting period, if the number of people queuing in front of the current check-in counter or the queue length in the counter status data exceeds the preset congestion threshold, or if the receiving conveyor belt is approaching full capacity, the preset upgrade conditions are met, the current waiting status is canceled, and priority release or manual takeover is triggered.

[0092] Specifically, during the waiting period, the system continuously collects and updates counter status data and target processing link status data according to a preset monitoring cycle (typically 2 to 5 seconds). After each update, the system immediately triggers the strategy reassessment logic. When the target processing link status data is detected to deteriorate, such as a further increase in the trigger frequency of the conveyor photocell, a continuous increase in the occupancy rate of the security check machine entrance, or the number of luggage staying in the transition conveyor area exceeding the warning threshold, causing the downstream acceptable recovery time re-output by the flow prediction model to be delayed compared to the original prediction value (e.g., the original prediction was recovery at 10:12, and the updated prediction is recovery at 10:18), the system recalculates the recommended release starting point. If the delayed recommended release starting point is later than (current time + waiting limit), the preset upgrade conditions are met. The system immediately terminates the current waiting state, upgrades the release control strategy from timed waiting release to priority release or candidate channel reassignment, sends a strategy change notification to the HMI and updates the countdown display to "Waiting has been canceled, preparing for priority release" or guide reassignment information, and simultaneously releases the PLC button lock or conveyor belt delay control.

[0093] On the other hand, when the number of people queuing or the queue length in the counter status data exceeds the preset congestion threshold (e.g., the number of people queuing is ≥8 or the queue length is ≥5 meters), or the photoelectric sensor of the receiving belt detects that the belt is approaching full load (e.g., the continuous obstruction time exceeds the threshold), the system determines that continuing to wait will lead to increased front-end congestion and affect the service experience of subsequent passengers. At this time, if the preset upgrade conditions are met, the system cancels the current waiting status, triggers priority release to quickly release the counter's acceptance capacity, or triggers manual takeover by the check-in supervisor to coordinate load diversion.

[0094] To avoid frequent policy switching due to instantaneous data fluctuations, the system employs a debouncing rule, meaning that policy adjustments are only implemented when two or three consecutive reassessments meet the upgrade conditions. Furthermore, the system monitors for early recovery scenarios: when downstream processing rates drop below the safe load threshold early, and the recommended release start point for reassessment is earlier than the original release window but still within the acceptable waiting limit, the system can prematurely lift the waiting status and immediately release the baggage, fully utilizing the idle window of downstream processing capacity. This closed-loop control mechanism of continuous monitoring and dynamic adjustment enables the system to respond in real-time to various environmental changes during the waiting period, such as downstream deterioration, increased front-end backlog, or early recovery. By promptly terminating inappropriate waiting or releasing baggage early, the system ensures timely processing of time-sensitive baggage while preventing the spread of front-end congestion.

[0095] In other preferred embodiments, when the release control strategy includes candidate channel reassignment, the method further includes:

[0096] Obtain real-time status data and downstream prediction data for multiple candidate channels adjacent to or on the same check-in island as the current baggage check-in counter;

[0097] Calculate the downstream acceptable recovery time and the corresponding estimated queuing time for each candidate channel;

[0098] Candidate channels are selected based on the sum of the estimated queuing time and the downstream available recovery time, which meet the waiting limit of the current shipping session.

[0099] Send a reassignment instruction to the human-computer interaction interface to guide passengers to the selected optimal candidate channel for baggage check-in.

[0100] A candidate lane refers to another check-in counter that is physically adjacent to the current check-in counter or located on the same check-in island (usually a group of counters sharing a common transport hub) and capable of handling baggage of the same flight type, thus having the ability to take over the check-in task from the current counter. Estimated queuing time refers to the total expected time for a passenger to walk from the current counter to the candidate lane, complete queuing there, and begin processing, including walking time and the waiting time calculated based on the current number of people queuing in the candidate lane.

[0101] This implementation method is triggered when the release control strategy generation module determines that candidate channel reassignment is necessary, providing passengers with an optimized channel selection scheme. Specifically, the system queries the counter topology configuration table for a list of multiple candidate channels adjacent to the current check-in counter or located on the same check-in island, and obtains real-time status data (including queue length, counter malfunction status, service mode, etc.) and corresponding downstream link prediction data (including downstream acceptance recovery time, acceptance capacity, etc.) for each candidate channel through a real-time data interface.

[0102] The system calculates the downstream acceptable recovery time for each candidate channel (using the same calculation method as S103), and estimates the passenger's expected queuing time for that channel based on the current number of people queuing and the historical average service time. For example, if there are 3 people queuing in candidate channel B and the historical average service time per person is 90 seconds, the queuing time is approximately 270 seconds. Adding the walking time from the current counter to channel B (e.g., 30 seconds), the total expected queuing time is 300 seconds. Then, candidate channels that meet the following condition are selected: the sum of the expected queuing time and the downstream acceptable recovery time for that candidate channel is not later than the waiting limit for the current baggage check-in session, i.e., (expected queuing time + downstream acceptable recovery time - current time) ≤ waiting limit, ensuring that the overall processing time after reassignment remains within the cut-off time constraint.

[0103] Among the candidate channels that meet the time constraints, the system further sorts them by the minimum sum of the estimated queuing time and the downstream recovery time, selecting the channel with the shortest total time as the optimal candidate channel. For example, if counter A currently does not meet the acceptance conditions, candidate counter B has an estimated queuing time of 300 seconds and a downstream recovery time of 180 seconds after the current time, totaling 480 seconds; candidate counter C has an estimated queuing time of 180 seconds and a downstream recovery time of 240 seconds after the current time, totaling 420 seconds. If the current session's waiting limit is 450 seconds, then both B and C meet the conditions, but C has a shorter total time, so the system selects C as the optimal reassignment target.

[0104] The system issues a reassignment instruction to the HMI at the current counter. The interface displays the recommended lane number (e.g., "Recommend going to counter C07"), walking guide arrows, and estimated waiting time. After passenger confirmation, the system can reserve a session at the target lane or send a session migration request. If no candidate lane meets the waiting limit after screening, the system switches directly to manual takeover, with the check-in supervisor coordinating special handling. This candidate lane reassignment mechanism, based on multi-dimensional evaluation, not only examines the current queuing status of the candidate lane but also considers the future capacity of its downstream links and the time constraint of the current session. Through a quantified total time optimization model, the best reassignment target is selected, achieving dynamic and balanced utilization of check-in area processing capacity while ensuring timely processing of time-sensitive baggage.

[0105] The baggage classification and release control device in the embodiments of this invention is described below from the perspective of hardware processing. Please refer to [link / reference]. Figure 2 This is a schematic diagram of the physical device structure of a baggage classification and release control device in the embodiments of this application.

[0106] It should be noted that, Figure 2 The structure of the baggage classification and release control device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of the present invention.

[0107] like Figure 2As shown, the baggage classification and release control device includes a Central Processing Unit (CPU) 201, which can perform various appropriate actions and processes based on programs stored in Read-Only Memory (ROM) 202 or programs loaded from storage section 208 into Random Access Memory (RAM) 203, such as performing the methods described in the above embodiments. The RAM 203 also stores various programs and data required for system operation. The CPU 201, ROM 202, and RAM 203 are interconnected via bus 204. An input / output (I / O) interface 205 is also connected to bus 204.

[0108] The following components are connected to I / O interface 205: input section 206 including audio input devices, push-button switches, etc.; output section 207 including a liquid crystal display (LCD) and audio output devices, indicator lights, etc.; storage section 208 including a hard disk, etc.; and communication section 209 including a network interface card such as a LAN (Local Area Network) card, modem, etc. Communication section 209 performs communication processing via a network such as the Internet. Drive 210 is also connected to I / O interface 205 as needed. Removable media 211, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 210 as needed so that computer programs read from them can be installed into storage section 208 as needed.

[0109] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing computer programs for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 209, and / or installed from removable medium 211. When the computer program is executed by central processing unit (CPU) 201, it performs the various functions defined in the present invention.

[0110] It should be noted that specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this invention, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0111] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. Each block in a flowchart or block diagram may represent a module, program segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those shown in the drawings.

[0112] Specifically, the baggage classification and release control device in this embodiment includes a processor and a memory. The memory stores a computer program, and when the computer program is executed by the processor, it implements the baggage classification and release control method provided in the above embodiment.

[0113] In another aspect, the present invention also provides a computer-readable storage medium, which may be included in the baggage classification and release control device described in the above embodiments; or it may exist independently and not assembled into the baggage classification and release control device. The storage medium carries one or more computer programs, which, when executed by a processor of the baggage classification and release control device, cause the baggage classification and release control device to implement the baggage classification and release control method provided in the above embodiments.

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

[0115] As used in the above embodiments, depending on the context, the term "when..." can be interpreted as meaning "if...", "after...", "in response to determining...", or "in response to detecting...". Similarly, depending on the context, the phrase "when determining..." or "if (the stated condition or event) is interpreted as meaning "if determining...", "in response to determining...", "when (the stated condition or event) is detected", or "in response to detecting (the stated condition or event)".

[0116] 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. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A method for controlling the classification and release of checked baggage, applied to the coordinated control of the airport check-in counter and the downstream baggage handling link, characterized in that, The method includes: Establish a current baggage check-in session and associate the current baggage check-in session with the cut-off time of the flight to which the current baggage belongs; Obtain the counter status data and target processing link status data corresponding to the current baggage check-in session; Based on the target processing link status data, determine the downstream acceptable recovery time and / or acceptable capability of the target processing link within a preset time domain; Based on the current time, the loading deadline, and the estimated time for the current shipping session to complete downstream processing, determine the maximum waiting time for the current shipping session; Based on the downstream acceptable recovery time and / or acceptable capacity, the waiting limit and the counter status data, a release control strategy for the current shipping session is generated. The release control strategy includes at least one of immediate release, timed waiting release, priority release, candidate channel reassignment and manual takeover, and a corresponding release window or release condition is generated. The release control strategy is converted into counter human-machine interface control signals and / or transmission control signals to control the timing when the current checked baggage enters the target processing link; During the waiting period, the counter status data and the target processing link status data are continuously updated, and the release control strategy is adjusted when the update result meets the preset upgrade conditions. The waiting period is the time period from the issuance of the waiting control instruction to the arrival of the release window or when the release control strategy is adjusted to priority release, candidate channel reassignment, or manual takeover, when the release control strategy is timed waiting release.

2. The method of claim 1, wherein, The step of determining the estimated duration of downstream processing based on the current time, the loading deadline, and the current shipping session, and determining the upper limit of the waiting time for the current shipping session, specifically includes: Obtain the estimated downstream processing time from the time the current checked baggage is received at the current check-in counter to the completion of the security check and sorting processes in the target processing link; The estimated downstream processing time and the preset safety time margin are subtracted from the time difference between the cut-off time limit and the current time to obtain the waiting limit of the current shipping session. The safety time margin is used to compensate for transportation fluctuations and abnormal processing time. When the waiting limit is less than or equal to zero, the current checked baggage is determined to be in an emergency state nearing its loading deadline.

3. The method of claim 2, wherein, The release control policy for the current baggage check-in session, generated based on the downstream acceptable recovery time and / or acceptable capacity, the waiting limit, and the counter status data, specifically includes: Calculate the recommended release start point for the current checked baggage, where the recommended release start point is the maximum value of the current time, the downstream acceptable recovery time, and the channel switching compensation time. If the recommended release start point is not later than the sum of the current time and the waiting limit, and the counter status data indicates that the current counter has the acceptance conditions, then a timed waiting release strategy is generated, and the recommended release start point is used as the start time of the release window; If the recommended release start point is later than the sum of the current time and the waiting limit, or if the counter status data indicates that the current counter does not meet the acceptance conditions, then a priority release, candidate channel reassignment, or manual takeover strategy is generated. If the acceptance capacity of the target processing link is within a preset safety range at the current moment, and the current counter meets the acceptance conditions, then an immediate release policy is generated.

4. The method according to any one of claims 1-3, characterized in that, The step of converting the release control strategy into counter human-machine interface control signals and / or transmitting control signals specifically includes: When the release control strategy is timed waiting release, a waiting instruction is sent to the programmable logic controller and / or human-machine interface of the current check-in counter; The human-computer interaction interface is controlled to display a prompt message including the reason for the wait and the remaining countdown; The programmable logic controller temporarily locks the physical release button function of the current check-in counter and / or delays the start action of the baggage conveyor belt after successful scanning; The status indicator light of the current check-in counter is synchronously switched to a preset waiting color. When the start time of the release window is reached, the physical release button function is automatically unlocked or the baggage conveyor belt is started, and the prompt message is turned off.

5. The method according to any one of claims 1-3, characterized in that, The step of determining the downstream acceptable recovery time and / or acceptable capability of the target processing link within a preset time domain based on the target processing link status data specifically includes: Collect the trigger frequency of the photoelectric sensor on the conveyor in the target processing link, the occupancy status of the security check machine entrance, and the number of luggage staying in the transition conveyor area according to the preset time window, and generate a historical processing capacity time series. The historical processing capacity time series and the current flight centralized check-in information are input into the pre-trained traffic prediction model; The traffic prediction model outputs the expected processing rate of the target processing link within a preset short-term window in the future, and identifies the time point when the expected processing rate falls below a preset safe load threshold, and determines this time point as the downstream acceptable recovery time.

6. The method of claim 3, wherein, The step of continuously updating the counter status data and the target processing link status data during the waiting period, and adjusting the release control strategy when the update results meet preset upgrade conditions, specifically includes: During the timed waiting period for release, if the target processing link status data is detected to deteriorate, causing the downstream acceptable recovery time to be delayed and the recommended release start point after the delay is later than the sum of the current time and the waiting limit, then the preset upgrade condition is met, and the release control strategy is upgraded from timed waiting release to priority release or candidate channel reassignment. During the timed waiting period, if the number of people queuing in front of the current check-in counter or the queue length in the counter status data exceeds the preset congestion threshold, or the receiving conveyor belt is approaching full capacity, then the preset upgrade condition is met, the current waiting status is revoked, and priority release or manual takeover is triggered.

7. The method according to claim 1 or 6, characterized in that, When the release control strategy includes candidate channel reassignment, the method further includes: Acquire real-time status data and downstream prediction data of multiple candidate channels adjacent to or on the same check-in island as the current baggage check-in counter; Calculate the downstream acceptable recovery time and the corresponding estimated queuing waiting time for each candidate channel; Candidate channels are selected whose sum of expected queuing time and downstream acceptable recovery time meets the waiting limit of the current shipping session; A reassignment instruction is sent to the human-computer interaction interface to guide passengers to the selected optimal candidate channel for baggage check-in.

8. A baggage sorting and releasing control apparatus characterized by comprising: The baggage classification and release control device includes: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code including computer instructions, and the one or more processors call the computer instructions to cause the baggage classification and release control device to perform the method as described in any one of claims 1-7.

9. A computer-readable storage medium comprising instructions, characterized in that, When the instruction is executed on the baggage classification and release control device, the baggage classification and release control device performs the method as described in any one of claims 1-7.

10. A computer program product, characterised in that, When the computer program product is run on the baggage classification and release control device, it causes the baggage classification and release control device to perform the method as described in any one of claims 1-7.

Images