Anti-carrying method, electronic device and medium

Abstract

The application provides a hidden loading method, an electronic device and a medium, and relates to the technical field of aircraft loading. The method comprises the following steps: determining that a cabin to be loaded currently exists, obtaining loadable information at the current time according to a loading sequence; in response to input selection information, obtaining second identification information of a target object, and performing primary verification according to the loadable information and the second identification information; determining that the primary verification is passed, sending state information of the target object to a secondary verification terminal, so that the secondary verification terminal obtains the code of the cabin and third identification information of the target object on the cabin in response to a verification instruction corresponding to the state information, and performs secondary verification according to the third identification information and the code. The application can effectively reduce the dependence on the personal experience of loading personnel, reduce the situation of manual judgment errors, avoid hidden loading problems caused by wrong loading and missing loading, improve the efficiency of loading operation, reduce the operation cost of the airport, and at the same time, ensure the flight safety of the flight.

Description

Technical Field

[0001] This application relates to the field of aircraft loading technology, and more specifically, to a method for preventing concealment, electronic equipment, and medium. Background Technology

[0002] In air cargo loading operations, it is typically necessary to load objects of different weights and sizes (such as cargo and baggage) into designated cargo bays of the corresponding flights according to the loading list. In actual operations, the loading sequence usually relies on the individual loading personnel to load the objects and check for any unauthorized loading. However, manual operation is prone to errors in loading positions and omissions. This not only reduces loading efficiency but also increases airport operating costs and can easily lead to unauthorized loading issues, affecting flight safety. Summary of the Invention

[0003] The purpose of this application is to address the shortcomings of existing technologies by providing a method, electronic device, and medium for preventing hidden loads, which can solve the problems that existing manual loading and inspection methods are prone to hidden loads, reducing operational efficiency, increasing operating costs, and affecting flight safety.

[0004] To achieve the above objectives, this application adopts the following technical solution: In a first aspect, this application provides an anti-hidden mark method for an initial verification terminal, wherein the initial verification terminal is communicatively connected to a secondary verification terminal, and the method includes: Determine the available cargo slots to be loaded, and obtain the available loading information at the current moment based on the loading order. The loading order is determined based on the influence relationship between the loading order data and the cargo slots. The available loading information includes a list of available cargo slots and the first identification information of the corresponding target object. In response to the input selection information, the second identification information of the target object is obtained, and an initial verification is performed based on the loadability information and the second identification information. Once the initial verification is successful, the status information of the target object is sent to the secondary verification terminal so that the secondary verification terminal responds to the verification command corresponding to the status information, obtains the cabin code and the third identification information of the target object on the cabin, and performs secondary verification based on the third identification information and the code.

[0005] In an optional implementation, obtaining the loadable information at the current moment based on the loading order includes: The loading order is determined based on the influence relationship between the loading order data and the cargo space. The current available cargo space is obtained according to the loading order. The affected cargo space corresponding to the available cargo space is the already loaded cargo space. A list of available loading spaces is generated based on the available loading spaces, and the first identification information of the target object corresponding to each available loading space in the list is recorded.

[0006] In an optional implementation, the step of obtaining the second identification information of the target in response to the input selection information includes: Display the list of available aircraft bays and receive selection information input based on the list of available aircraft bays; Based on the selection information, the target object to be loaded is determined, and the scanning device corresponding to the initial verification terminal is invoked to scan the target object to obtain the second identification information.

[0007] In an optional implementation, the initial verification based on the installability information and the second identification information includes: Based on the loadability information, determine the first identification information corresponding to the target object to be loaded; If the first identification information and the second identification information match, then the verification is considered successful.

[0008] In an optional implementation, detecting whether the first identification information and the second identification information match includes: Obtain the type of the target object, including goods and luggage; If the type is goods, then the code and / or weight corresponding to the goods are obtained according to the first identification information, and the code and / or weight are matched with the second identification information; If the type is luggage, then the destination station corresponding to the luggage is obtained according to the first identification information, and the destination station is matched with the second identification information.

[0009] In an optional implementation, determining that the initial verification passed includes: An operation log is generated, the status information corresponding to the target object is updated, and new loadable information is generated. The operation log includes information about the target object as well as the corresponding operator, operation time, and operation type.

[0010] In an optional implementation, the method includes: Once it is confirmed that new installation order data has been detected, version difference information is obtained based on the new installation order data; Perform a rollback operation based on the status of the target object corresponding to the version difference information, and obtain the current loading status of the target object corresponding to the new installation order data after the rollback operation; A new loading sort is generated based on the new installation order data and the current loading status.

[0011] In an optional implementation, performing a rollback operation based on the state of the target object corresponding to the version difference information includes: Based on the state of the target object, a rollback candidate set is constructed, and the cabin class corresponding to the rollback candidate set and the affected cabin class corresponding to the cabin class are determined. A rollback closure is generated based on the impact of the state change of the cabin on the state of the affected cabin. The rollback closure includes the cabin to be rolled back, and the state change of the cabin is generated based on the rollback operation of the target object in the rollback candidate set. A rollback operation is performed based on the rollback closure, and the rollback operation includes unloading the loaded target object.

[0012] Secondly, this application provides an anti-hidden mark method for a secondary verification terminal, wherein the secondary verification terminal is communicatively connected to the primary verification terminal, and the method includes: The system receives the status information of the target object transmitted by the initial verification terminal. The status information is obtained by the initial verification terminal based on the determination that there are currently unloaded cabins, the loading order, the current loading availability information, the second identification information of the target object in response to the input selection information, the initial verification based on the loading availability information and the second identification information, and the system sends the information when the initial verification is successful. The loading order is determined based on the influence relationship between the loading order data and the cabins. The loading availability information includes a list of available cabins and the first identification information of the corresponding target object. In response to the verification command corresponding to the status information, the cabin code and the third identification information of the target object on the cabin are obtained; A second verification is performed based on the third identification information and the encoding.

[0013] In an optional implementation, a secondary verification is performed based on the third identification information and the encoding, including: The third identification information is compared with the installation order data; Obtain the target code of the cabin corresponding to the target object based on the loading order data, and compare the target code with the code of the cabin. If the installation order data contains the target object corresponding to the third identification information and the target code is consistent with the code, then the secondary verification is confirmed to be successful.

[0014] Thirdly, this application provides an electronic device including a processor and a memory, wherein the processor and the memory are communicatively connected, the memory stores program data, and the program data is used to execute any of the methods described above.

[0015] Fourthly, this application provides a computer-readable storage medium storing a computer program that is used to perform any of the methods described above.

[0016] The beneficial effects of the technical solutions provided in this application are: The method for preventing unauthorized loading provided in this application includes: determining the available cargo slots to be loaded; obtaining the available loading information at the current moment based on the loading order, where the loading order is determined based on the influence relationship between the loading order data and the cargo slots; the available loading information includes a list of available cargo slots and the first identification information of the corresponding target object; in response to input selection information, obtaining the second identification information of the target object; performing an initial verification based on the available loading information and the second identification information; and, if the initial verification is successful, sending the status information of the target object to a secondary verification terminal so that the secondary verification terminal responds to the verification command corresponding to the status information, obtains the code of the cargo slot and the third identification information of the target object on the cargo slot, and performing a secondary verification based on the third identification information and the code. This application embodiment can determine the currently available cargo slots based on the loading order to achieve sequential loading of target objects. Through a dual verification mechanism of initial and secondary verification, the target object information and loading position are double-checked, effectively reducing reliance on the personal experience of loading personnel, reducing human judgment errors, avoiding unauthorized loading and omissions, improving loading efficiency, reducing airport operating costs, and ensuring flight safety. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments of this application will be briefly introduced below.

[0018] Figure 1 A flowchart of the anti-hidden labeling method provided in the embodiments of this application; Figure 2 A flowchart illustrating the anti-hidden labeling method provided in this application embodiment; Figure 3 A schematic diagram illustrating board box number verification provided in an embodiment of this application; Figure 4 A schematic diagram of cabin verification provided for an embodiment of this application; Figure 5 Another flowchart of the anti-hidden labeling method provided in the embodiments of this application; Figure 6 A structural diagram of the electronic device provided in the embodiments of this application; Figure 7 This is a structural diagram of a computer-readable storage medium provided in an embodiment of this application. Detailed Implementation

[0019] The embodiments of this application are described below with reference to the accompanying drawings. It should be understood that the embodiments described below with reference to the accompanying drawings are exemplary descriptions for explaining the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions of the embodiments of this application.

[0020] Those skilled in the art will understand that, unless specifically stated otherwise, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the terms “comprising” and “including” as used in embodiments of this application mean that the corresponding feature can be implemented as the presented feature, information, data, step, operation, element, and / or component, but do not exclude implementation as other features, information, data, step, operation, element, component, and / or combinations thereof supported by the art. It should be understood that when we say that an element is “connected” or “coupled” to another element, the one element can be directly connected or coupled to the other element, or it can mean that the one element and the other element establish a connection relationship through an intermediate element. Furthermore, “connected” or “coupled” as used herein can include wireless connection or wireless coupling. The term “and / or” as used herein indicates at least one of the items defined by the term; for example, “A and / or B” indicates implementation as “A,” or implementation as “A,” or implementation as “A and B.”

[0021] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0022] The technical solutions of this application and their effects are described below through several exemplary embodiments. It should be noted that the following embodiments can be referenced, borrowed from, or combined with each other. Identical terms, similar features, and similar implementation steps in different embodiments will not be repeated.

[0023] The anti-hidden labeling method, electronic device, and medium provided in this application are intended to solve at least one technical problem existing in the prior art.

[0024] Optionally, such as Figures 1-4 As shown, the object implementing the anti-hidden content method of this application can be a mobile phone, computer, server, cloud platform, or other terminal that can verify the data after receiving the installation order data.

[0025] Optionally, the anti-hidden load method of this application is used for an initial verification terminal, which is communicatively connected to a secondary verification terminal. The initial and secondary verification terminals can be operated by different entities to achieve dual verification. The entity using the initial verification terminal can be an onboard loader or apron manager. When loading or unloading a target object into its corresponding compartment, this entity uses the initial verification terminal to perform an initial verification to ensure the target object is moved to the correct compartment and loaded / unloaded in sequence. The entity using the secondary verification terminal can be an onboard loader. This loader uses the secondary verification terminal to perform a secondary verification to check whether the target object matches the loading manifest data and whether the target object's location matches its compartment, thus achieving dual verification and effectively preventing hidden load issues.

[0026] Optionally, when the target of the method in this application is an initial verification terminal, the method includes: S101: Determine the available cargo slots for loading and obtain the current loading availability information based on the loading order.

[0027] Optionally, the loading order is determined based on the relationship between the loading order data and the cargo space. The loadable information includes a list of available cargo spaces and the first identification information of the corresponding target objects. The loading order data may include cargo spaces corresponding to different target objects, and the target objects to be loaded in each cargo space are determined based on this loading order data.

[0028] Optionally, loading list data can be generated based on information such as the type, size, weight of the target object, baggage information corresponding to the flight, and outbound cargo and mail information. The loading list data will be different for different flights.

[0029] Optionally, the target object can be cargo (such as pallets or containers) or baggage. The first identification information can be the cargo number (such as the pallet or container number) of the cargo or the baggage number of the baggage. The cargo number and baggage number can be represented by a QR code, barcode, number, or other form, and the cargo number can be included in the loading manifest data for aircraft loading. Specifically, the loading manifest data records the cargo number of each target object and the corresponding cargo compartment.

[0030] Optionally, the available loading information at the current moment is obtained based on the loading order, including: determining the loading order based on the influence relationship between the loading order data and the cargo space; obtaining the current available cargo space based on the loading order, where the affected cargo space corresponding to the available cargo space is the already loaded cargo space; generating a list of available cargo spaces based on the available cargo spaces and recording the first identification information of the target object corresponding to each available cargo space in the list. Here, the already loaded cargo space is either a cargo space currently loaded with the target object or a cargo space that does not need to load the target object (i.e., the influence of other cargo spaces needs to be considered).

[0031] Optionally, for obtaining the loading order, the set of loaded cabins can be initialized based on the loading list data of the current flight; the unloaded cabins can be traversed, and the loading order of the unloaded cabins can be determined based on the influence relationship model and the set of loaded cabins. The influence relationship model is established based on the influence relationship between cabins.

[0032] Optionally, the loaded cabin set is initialized based on the loading list data of the current flight, including: determining the unloaded cabins of the target object to be loaded based on the loading list data; determining the cabins other than the unloaded cabins in the current flight as loaded cabins; and adding the loaded cabins to the loaded cabin set.

[0033] Optionally, the available cargo space can be determined based on the aircraft type corresponding to the current flight. Based on this cargo space and the loading manifest data, unloaded cargo spaces that need to be loaded with the target object can be determined. Other cargo spaces besides these unloaded cargo spaces are then added to the loaded cargo space set.

[0034] In one embodiment, the target object is cargo. The loading manifest data for the current flight is obtained, and the set `cabinsWithCargo` representing the cargo spaces actually loaded on this flight is determined. All cargo spaces in the aircraft configuration are then grouped into a set `AllCabins`. Cargo spaces in `AllCabins` that are not in `cabinsWithCargo` are retrieved, their tag type is set to "loaded", and they are added to the loaded cargo space set `loadedSet`. That is, `loadedSet = AllCabins - cabinsWithCargo`. Empty cargo spaces without cargo loading requirements are naturally considered loaded, and their constraints on associated cargo spaces can be released without waiting (i.e., their impact on other cargo spaces is not considered).

[0035] Optionally, the influence relationship model is established based on the influence relationships between cabin classes. Establishing the influence relationship model includes: determining the influence relationships between cabin classes based on the cabin class information corresponding to the current flight, including physical obstruction relationships; storing the influence relationships as configuration data; and constructing the influence relationship model based on the configuration data. The cabin class information may include the physical layout of the cabins, which can be determined by the aircraft corresponding to the current flight.

[0036] Optionally, the influence relationship may also include the influence on the transport or retrieval channel, the influence on the fixation of the target object, and other information that affects the loading sequence.

[0037] In one embodiment, the aircraft corresponding to the current flight can be obtained, and the physical obstruction relationship between cabins can be determined based on the physical layout of the cabins in the aircraft. If cabin X is located on the loading channel of cabin Y, that is, loading X will affect the subsequent loading of Y, then Y is recorded as the affected cabin of X. In this way, the physical obstruction relationship between each cabin can be determined.

[0038] Optionally, the target aircraft type or aircraft data for the current flight can be determined. Based on this target aircraft type or aircraft data, the physical layout of the cabins can be determined. Based on this physical layout, an affected cabin set `BeAffectedCabins` for each cabin can be generated (this set represents the influence relationship between cabins). Here, `BeAffectedCabins` for cabin X represents the set of cabins that will be physically affected (blocked or hindered) by the target object loaded by X when cabin X is loaded. If there are cabins in `BeAffectedCabins` for cabin X that have not yet been loaded, then cabin X is not allowed to be loaded. This affected cabin set is stored as configuration data, using cabin identifiers as keys and a list of affected cabin identifiers as values ​​to generate an influence relationship model.

[0039] Optionally, determining the loading order of unloaded cargo spaces based on the influence relationship model and the set of loaded cargo spaces includes: determining that there are unloaded cargo spaces; obtaining the set of affected cargo spaces corresponding to the unloaded cargo spaces based on the influence relationship model, wherein the set of affected cargo spaces includes cargo spaces affected by the unloaded cargo spaces; determining the marking type of the unloaded cargo spaces based on the matching relationship between the set of affected cargo spaces and the set of loaded cargo spaces, wherein the marking type includes loadable and blocked; sorting at least one unloaded cargo space based on the marking type; and determining the sorted unloaded cargo spaces as loaded cargo spaces and placing them into the set of loaded cargo spaces.

[0040] Optionally, loading sorting can be performed through traversal. This involves iterating through the currently unloaded cargo slots, obtaining the corresponding set of affected cargo slots for each unloaded slot, identifying the sortable unloaded cargo slots based on this set, and then sorting those unloaded cargo slots. After sorting, the remaining unloaded cargo slots are traversed and sorted again.

[0041] Optionally, the tag type of unloaded cabins is determined based on the matching relationship between the affected cabin set and the loaded cabin set, including: if all cabins in the affected cabin set belong to the loaded cabin set, the tag type of the unloaded cabin is determined to be loadable; if some or all of them are not in the loaded cabin set, the tag type of the unloaded cabin is determined to be blocked. In this way, the cabins that can be sorted are filtered.

[0042] In one embodiment, the system iterates through the currently unloaded cabins. For each unloaded cabin X, it queries the set of affected cabins `BeAffectedCabins(X)`. It then determines whether all cabins in this set belong to the set of loaded cabins `loadedSet`. If so, cabin X is marked as "loadable" and added to the list of loadable cabins; otherwise, cabin X is marked as "blocked," and the reason for blocking is that the affected cabins include unloaded cabins.

[0043] Optionally, sorting at least one unloaded cabin space based on the tag type includes: generating a list of loadable cabin spaces based on cabin spaces tagged as loadable; selecting at least one unloaded cabin space from the list of loadable cabin spaces for sorting based on priority rules, and recording the sorting of the unloaded cabin spaces. This can be done by selecting only one unloaded cabin space for sorting at a time, and then regenerating the list of loadable cabin spaces after sorting; alternatively, two or more unloaded cabin spaces can be selected from the list of loadable cabin spaces according to user needs or preset instructions, and then sorted according to priority.

[0044] Optionally, the priority rules can be: prioritize the cabins with fewer affected cabins in the list of available cabins (the fewer affected cabins, the less constraint they will have on subsequent operations after loading); when the number of affected cabins is the same, priority is determined according to the order of the cabins in the aircraft configuration (cabins with later numbers have priority, and cabins that are physically farthest from the cabin door have priority in loading).

[0045] Optionally, priority rules may also include: setting priority based on the distance of the cargo space and the cargo hold exit, with the higher the distance, the lower the priority; or setting priority based on the difficulty of handling and placing the target object corresponding to the cargo space, with the higher the difficulty, the higher the priority.

[0046] In one embodiment, a cargo space is selected from the list of available cargo spaces according to a preset priority rule as the current loading target. The order of the current loading target is determined based on the sequence number of the already sorted cargo spaces. Furthermore, after determining the order of a cargo space, the cargo space can be marked as loaded, added to the loaded cargo space set `loadedSet`, and removed from the list of available cargo spaces.

[0047] Optionally, sorting at least one unloaded cargo hold based on its tag type includes: if the list of loadable cargo holds is determined to be empty and there are unloaded cargo holds with a tag type of "blocked", then modifying the tag type of the unloaded cargo hold to "loadable" according to the set of affected cargo holds corresponding to the unloaded cargo hold and issuing an alarm; sorting is then performed based on the unloaded cargo holds with the tag type of "loadable". This method can prevent the process from being blocked due to the remaining unloaded cargo holds failing to meet the sorting conditions after all normally sortable cargo holds have been loaded, ensuring that the loading operation can continue. At the same time, alarms alert operators to abnormal situations that do not meet constraints, reminding operators to verify and confirm on-site, ensuring the safety and compliance of the loading operation.

[0048] Optionally, alarms can be issued through text prompts, sound alarms, or by controlling specific indicator lights to illuminate. The specific alarm method can be determined according to actual needs.

[0049] In one embodiment, if the list of available cabins is empty after traversing all unloaded cabins, and there are still cabins that have not been loaded (i.e., there are unloaded cabins), then a circular dependency deadlock is determined to exist; the deadlock breaking strategy is executed: select the cabin with the fewest affected cabins from the unloaded cabins, forcibly mark it as available for loading, and issue an alarm; the alarm includes: the cabin identifier that has been forcibly unlocked, its list of affected cabins, and the identifiers of the affected cabins that have not yet been loaded.

[0050] In one embodiment, the current flight corresponds to an A333 aircraft. During loading sorting, an impact model is established for the A333 aircraft's bulk cargo space. This bulk cargo space comprises three bays, numbered 51, 52, and 53, with the following impact relationships: Loading bay 51 is affected by bays 53 and 52, requiring bays 53 and 52 to be loaded first; loading bay 52 is affected by bay 53, requiring bay 53 to be loaded first; loading bay 53 has no affected bays and can be loaded at any time. The physical meaning of this model is: bay 53 is located at the farthest end (near the tail), bay 52 is in the middle, and bay 51 is located at the closest end (near the door). The loading order should be from farthest to closest: load 53 first, then 52, and finally 51. If 51 is loaded first, the target objects of bays 52 and 53 cannot enter the rear bays via bay 51.

[0051] If the loading list data indicates that there are target customers in cabins 51, 52, and 53 of this flight, then `cabinsWithCargo = {51, 52, 53}` and `loadedSet = {}` (no empty cabins).

[0052] Traverse unloaded bays: - 53: BeAffectedCabins=[], all are loaded (empty set satisfies) → mark type as loadable - 52: BeAffectedCabins=

[53] , 53 not installed → marked as blocked - 51: BeAffectedCabins=[53, 52], 53 and 52 are not installed → the flag type is blocked. The generated list of available loading slots includes slot 53. Slot 53 is selected as the current loading target, and loading is sorted (e.g., the sorting number is 1). Slot 53 is marked as loaded, `loadedSet = {53}`. Continuing to iterate through the unloaded slots, we get: 52:BeAffectedCabins=

[53] , 53 is already installed → can be installed; 51:BeAffectedCabins=[53, 52], 52 not installed → blocked.

[0053] Generate a new list of available loading bays:

[52] , select bay number 52, and sort the loading (sorting number is 2). Mark 52 as loaded, `loadedSet = {52}`. Continue to traverse the unloaded bays to get: 51: BeAffectedCabins=[53, 52], 53 and 52 are both loaded → mark the type as loadable. Generate a new list of loadable cabins:

[51] , select cabin 51, and sort the loading (the sorting number is 3). Mark 51 as loaded, `loadedSet = {51}`.

[0054] The final loading sequence is: 53→52→51.

[0055] In one embodiment, the target object is loaded into the front cabin of an A333 aircraft, establishing an affected relationship model for the front cabin. The front cabin contains 33 cabins, among which there are circular dependencies. For example, cabin 26L requires cabins 24P and 26 to be loaded first, cabin 24P requires cabin 26L to be loaded first, and cabin 26 requires cabin 26L to be loaded first—forming a circular dependency. Based on the loading list data, it is determined that only cabins 26L and 24P have the target object for this flight, i.e., `cabinsWithCargo ={26L, 24P}`, while the remaining 31 cabins are empty, `loadedSet={26R,25L,25R,24L,...,12,11}` (a total of 31). Traverse the unloaded cabins: -26L: BeAffectedCabins=[24P,26], 24P not installed → blocked; -24P: BeAffectedCabins=[26L,26R,25L,25R,26,25], 26L not installed → prevented; At this point, the list of available cabins is empty, and two cabins are unloaded, triggering a deadlock detection. The number of affected cabins is checked: 26L=2, 24P=6. Cabin 26L, with the fewest affected cabins, is forcibly unlocked. After sorting the loading of 26L, it is added to the loadedSet. Since 26L is already loaded in the BeAffectedCabins of cabin 24P, and the rest (26R, 25L, 25R, 26, 25) are empty and already in the loadedSet, the tag type of 24P changes to available. The final loading order is: 26L→24P.

[0056] Without a mechanism that treats empty slots as loaded, only 26L of the six affected slots in 24P would have cargo, while the other five empty slots would have to wait, resulting in invalid constraints. By dynamically identifying empty slots, 24P can load cargo only by waiting for 26L, significantly simplifying the constraints.

[0057] Optionally, after obtaining the loading sort, the cargo bays where target objects have been loaded and those where target objects have not yet been loaded can be determined based on the loading list data and the loading sort. From the cargo bays where target objects have not yet been loaded, objects that can currently be loaded and whose affected cargo bays are already loaded are selected based on the loading sort, and these objects are identified as available cargo bays. After obtaining the available cargo bays, they can be added to the available cargo bay list so that operators are aware of the cargo bays currently available for aircraft loading.

[0058] Optionally, the list of available bays is not a fixed table, but a dynamically changing set of available bays. This list serves as the boundary of the geofence, and is updated every time a bay is installed.

[0059] Optionally, the list of available loading bays includes bays that can currently be used to load the target object (i.e., there are no affected bays or the affected bays have already loaded the target object or are marked as loaded). The bays in the list of available loading bays can be arranged according to the calculated loading order, and the operator can be prompted to load the target object in sequence. Alternatively, the operator can disregard the order of the available loading bays and select only the target object corresponding to a specific bay in the list for loading. After each loading, the loading order of the target objects is recalculated, thereby generating a new list of available loading bays.

[0060] Optionally, to avoid incorrect loading of the target object, the first identification information can be written into the list of available loading bays. Specifically, the list of available loading bays may include the number of the target object corresponding to each available loading bay. After obtaining the current list of available loading bays, the initial verification terminal displays the list and the first identification information so that the user can quickly find the target object to be loaded.

[0061] In one embodiment, the operator can be the apron manager, and the initial verification terminal can be a mobile terminal. The terminal outputs a list of available cargo slots and their corresponding cargo / baggage information based on the calculated loading order. Only cargo slots marked as fully loaded will appear in this list; those not listed are outside the fence and cannot be accessed. This list is dynamic—it doesn't arrange all cargo slots in order for you to follow at once. Instead, it is recalculated after each loading operation, and the electronic fence range may expand (potentially adding new available cargo slots) or remain unchanged (if the loaded cargo slots do not release any new constraints).

[0062] Optionally, the boundaries of the electronic fence are not fixed. They are determined by the dynamic intersection of two sets: Set A: the calculated set of "currently allowed loading bays"; Set B: the set of bays to which cargo / baggage that has not yet completed boarding / entry operations belong; Fence = A ∩ B. Each time a boarding or entry operation is completed, Set A and Set B change, and the fence boundaries are recalculated accordingly. At any given time, handlers can only handle cargo / baggage within the fence; anything outside the fence is blocked.

[0063] This is the "electronic fence based on dynamic intersection"—the fence boundary is not drawn by humans, but calculated in real time by the system based on the loading progress. The further the loading progresses, the larger the fence area becomes; if any step goes wrong, the fence will not expand, and the erroneous operation will be directly blocked outside the fence.

[0064] S102: In response to the input selection information, obtain the second identification information of the target object, and perform an initial verification based on the loadability information and the second identification information.

[0065] Optionally, in response to the input selection information, the second identification information of the target is obtained, including: displaying a list of available loading bays, receiving selection information input based on the list of available loading bays; determining the target object to be loaded according to the selection information, and calling the scanning device corresponding to the initial verification terminal to scan the target object using the scanning device to obtain the second identification information.

[0066] Optionally, such as Figure 3 As shown, the terminal can display the list of available cabins, and can also display the flight information corresponding to the target object and the location of the currently loaded target object (such as the front cabin, rear cabin, or bulk cabin).

[0067] Optionally, users can select information through touch screen clicks, buttons, voice input, and other inputs. This selection information may include the selected loadable compartment and the first identification information of the target object corresponding to that compartment.

[0068] Optionally, the scanning device can be a camera of the initial verification terminal, a barcode scanner connected to the initial verification terminal, or other objects capable of acquiring second identification information.

[0069] In one embodiment, each available cargo bay in the list can have a corresponding barcode scanning button. The terminal determines the target object to be loaded based on the button clicked by the user and uses a camera to scan the target object to obtain second identification information. When the target object is cargo, the second identification information can be represented by a barcode or QR code, which is obtained by scanning the barcode or QR code. Alternatively, an RFID tag can be attached to the target object, and the second identification information can be obtained through this tag.

[0070] Optionally, an initial verification is performed based on the loadability information and the second identification information, including: determining the first identification information corresponding to the target object to be loaded based on the loadability information; if the first identification information and the second identification information match, the verification is deemed successful.

[0071] Optionally, if the first identification information does not match the second identification information, the verification is determined to have failed, and the terminal can issue an alarm, which can be done through sound, text, images or other means.

[0072] Optionally, detecting whether the first identification information and the second identification information match includes: obtaining the type of the target object, including goods and luggage; if the type is goods, obtaining the code and / or weight corresponding to the goods based on the first identification information, and matching the code and / or weight with the second identification information; if the type is luggage, obtaining the destination station corresponding to the luggage based on the first identification information, and matching the destination station with the second identification information.

[0073] In one embodiment, the operator can be a cargo handler. The terminal displays a list of available cargo slots. The handler selects a slot from the list and clicks the "Scan" button. The terminal then displays a scanning window to instruct the handler to scan the target object. When the target object is a pallet or container, the handler scans the barcode / QR code on the pallet or container to obtain the pallet / container number (cargo_serial_no). The terminal compares the scan result with the corresponding pallet / container number in the current list of available cargo slots. If the pallet / container number matches and the slot to which the pallet / container belongs is within the current available cargo slot range, the verification passes. If the pallet / container number does not match or the slot to which the pallet / container belongs is outside the current available cargo slot range (i.e., outside the fence), the verification fails, and the terminal issues an audible and visual alarm, displaying the reason for the rejection. When the target object is baggage, the handler scans the baggage barcode to obtain the baggage number. The terminal compares the destination station corresponding to the scanned baggage number with the destination station corresponding to the current cargo slot. If the destination stations match, the verification passes; if the destination stations do not match, the verification fails, and an alarm is triggered. In addition, when the target is goods, the pre-loaded weight of the goods can be compared with the actual weight. If they are inconsistent, a red reminder will be displayed (the operation can be interrupted, only the reminder will be displayed).

[0074] Optionally, outbound cargo and mail data, loading manifest data, and information obtained through barcode scanning can be compared to obtain verification results. The loading manifest data can include both graphical and textual versions.

[0075] Optionally, to further avoid errors, a cargo hold layout diagram can be printed, and the apron manager can manually verify the loading order of the target objects based on the diagram.

[0076] S103: After confirming that the initial verification has passed, the status information of the target object is sent to the secondary verification terminal so that the secondary verification terminal responds to the verification command corresponding to the status information, obtains the cabin code and the third identification information of the target object on the cabin, and performs secondary verification based on the third identification information and the code.

[0077] Optionally, confirming that the initial verification has passed includes: generating an operation log, updating the status information corresponding to the target object, and generating new installable information. The operation log includes information about the target object as well as the corresponding operator, operation time, and operation type.

[0078] In one embodiment, after the initial verification passes, the terminal can perform operations such as inserting logs, updating cabin status, and refreshing the list of available cabins. Specifically: Insert Log: Record the cargo / baggage information, operator, operation time, and operation type "on the machine" for this operation; Update cargo / baggage status: Mark the status of the record corresponding to this cargo / baggage as "boarded", and the terminal will display the line as dark green; Refresh the list of available loading bays: Recalculate the available loading bays based on the latest set of loaded bays, update the electronic fence range based on the calculation results, and perform the loading operation on the target object again.

[0079] At this time, the secondary verification terminal of the personnel on board (the onboard loading and unloading personnel) listens in real time via WebSocket and synchronously receives the status change of the cargo being loaded onto the aircraft. The corresponding record automatically turns dark green and a "Verify" button appears to verify the target object that has been loaded into the hold.

[0080] Optionally, after the target object is moved to the cabin, the code of the target object and the identification code of the cabin can be obtained. The code and the identification code are compared to determine whether they are consistent with the data on the loading list. If they are consistent, the verification is confirmed to be successful; if they are inconsistent, the verification is confirmed to be unsuccessful.

[0081] Optionally, a secondary verification is performed based on the third identification information and the code, including: comparing the third identification information with the loading order data; obtaining the target code of the cabin corresponding to the target object based on the loading order data, and comparing the target code with the code of the cabin; if the loading order data contains a target object corresponding to the third identification information and the target code is consistent with the code, then the secondary verification is determined to be successful.

[0082] In one embodiment, the target object can be cargo or baggage. After the cargo / baggage is physically moved into the cabin, the cabin crew clicks the "Verify" button on the terminal to enter the verification interface. This verification requires scanning two codes to obtain third-party identification information, specifically: The first code – Cargo / Baggage Identification Code: Goods: Scan the barcode / QR code on the goods to obtain the goods number, and compare it with the goods number in the loading order data; Baggage: Scan the baggage barcode, obtain the baggage number, and compare it with the baggage number in the packing slip data; The second code – cabin location code: Scan the cabin QR code affixed inside the cabin to obtain your current cabin identifier; Cross-validate the two scan results. The cargo / baggage identification code matches the loading manifest record, and the cabin class QR code corresponds to the cabin class specified on the loading manifest. Verification passed. If any discrepancy is found, the verification fails, an alert is issued, and the specific mismatch is displayed.

[0083] Optionally, after successful verification, a log can be inserted: recording the cargo / baggage information verified this time, the two barcodes scanned, the operator, the operation time, and the operation type "verification (placement)", updating the cabin status: changing the record from "boarded" (dark green) to "placed" (blue), hiding the "verification" button, and updating the fence: if all cargo / baggage in the cabin has been placed, the cabin as a whole is marked as "completed", and its constraint on other cabins as an affected cabin is officially released.

[0084] The above operations achieve a dual-shift cycle. The initial check after boarding the aircraft verifies whether the target can board the plane—whether the identity and order are correct. The secondary check after boarding the aircraft verifies whether the target is placed in the correct position—whether the identity and cabin class are correct. The two shifts verify independently, without interdependence but inextricably linked: the onboard verification cannot be triggered until the initial check confirms "boarding," and the electronic fence is only truly released after the onboard verification confirms "in place." If either shift fails to complete its task, the electronic fence will not allow subsequent cabin classes to proceed, thus forming a complete anti-hidden load closed loop.

[0085] In one embodiment, the complete verification process for preventing hidden content can be as follows: Phase 1: On-board and off-board verification (operated by off-board loading and unloading personnel using the initial verification terminal) The loading and unloading personnel on board the aircraft select the cargo space to be loaded from the list of available cargo spaces and scan the cargo / baggage barcode using the initial verification terminal; Terminal verification: whether the scanned cargo number matches the record in the loading order data, and whether the cargo space is within the current loading range (belonging to the list of loading cargo spaces). If the verification passes, the cargo status changes to "Loaded" (dark green), and the log is written (operation type="Loaded"). The list of available loading bays is refreshed, and the fenced area is updated. The onboard secondary verification terminal synchronizes in real time via WebSocket, the cargo record automatically turns green, and the secondary verification terminal displays a "Verify" button.

[0086] Phase Two: Onboard Position Verification (operated by onboard loading and unloading personnel using a secondary verification terminal) After the cargo is physically pushed into the hold, the onboard stevedore clicks the "verify" button for the record on the terminal. The terminal then enters a double-blind scanning interface, which only displays two input areas: "Please scan cargo code" and "Please scan hold code," without displaying the expected values ​​(the expected numbers for the cargo code and hold code). The onboard stevedore first scans the barcode / QR code on the cargo to obtain the cargo number; this is the physical collection of identification information.

[0087] Scan the cabin QR code on the bulkhead to obtain the cabin identifier; this is physical data collection at the location level.

[0088] The terminal performs cross-comparison: Identity dimension: Compare the scanned item number with the item number in the loading order data; Location dimension: Compare the scanned cabin identifier with the specified cabin in the loading order data; If both dimensions match, the verification passes. If either dimension is inconsistent, the verification fails, an alarm is issued, and the specific mismatch is displayed (e.g., "Cargo number mismatch: Scan AKE12345, expected AKE67890" or "Vehicle space mismatch: Scan 24P, expected 26L").

[0089] If the verification passes, the record status changes to "In Place" (blue), the "Verify" button is hidden, and the log is written (operation type="verify", recording the two scanned values ​​and the comparison result). If all cargo / baggage in this cargo space has completed the placement verification, the entire cargo space is marked as "Completed", and its constraint on other cargo spaces as an affected cargo space is officially released.

[0090] Optionally, RFID tags or Bluetooth beacons can be affixed to the target object and cargo compartment, attached to the bulkhead and the target cargo. When the target object enters the cargo hold, the sensor antenna and card reader at the door automatically acquire dual codes and perform cross-verification to avoid the need for terminal scanning. Alternatively, text that can be used for OCR recognition can be set on the target object and cargo compartment. When the target object enters the cargo hold, OCR recognition equipment at the door or other locations can automatically acquire and verify the image of the text (such as verifying whether the cargo belongs to the flight and whether the compartment is correct), thus avoiding the need for terminal scanning.

[0091] Optionally, when the target object is baggage, if the baggage has a pallet number, the same verification method as for cargo can be used. If the baggage does not have a pallet number, the cabin class identifier and baggage number (third identification information) can be displayed on the verification page of the secondary verification terminal. The baggage number is obtained by scanning the baggage barcode, and the system compares whether the destination station corresponding to the baggage number is consistent with the cabin class destination station, and whether the baggage ID is consistent with the loading manifest record. Since loose baggage does not have an independent physical container, the verification accuracy of the cabin class dimension is different from that of the target object, but the double-blind principle remains unchanged.

[0092] Optionally, in actual loading operations, the loading manifest data (loading instructions) is not static. Before flight departure, version changes may occur due to reasons such as: addition or removal of target objects, cabin adjustments, weight balance corrections, etc. When changes occur, the cabin allocation of some loaded or being loaded target objects may change, resulting in inconsistencies between completed loading operations and the new version of the loading manifest. To resolve this issue, a rollback operation is required. This can be achieved through... Rollback after a version change is not a simple "full restart", but a minimal adaptive rollback based on the affected relationships - only the load states that are truly affected are rolled back, the completed operations that are not affected are preserved, and the dependencies are automatically rebuilt to ensure that the load jobs after the rollback still meet the order constraints.

[0093] "Adaptiveness" is reflected in three aspects: Adaptive change identification: Instead of "starting over completely when the version changes", it compares the two versions of the loading list one by one to accurately identify which cargo / baggage has changed its cabin allocation. Only the records that have changed are included in the rollback candidate set. Rollback scope is adaptive: After a shipment is rolled back, subsequent shipments that depend on it for loading also need to be rolled back - but only those on the affected links are rolled back, while completed operations not on the affected links are retained; Adaptive Sequence Reconstruction: After the rollback is completed, the set of loaded bays changes, and the loading sequence needs to be recalculated. The system automatically calls the dynamic loading sequence sorting algorithm to regenerate the fences and sequence without manual intervention.

[0094] Optionally, the method of this application includes: determining that new loading order data has been detected, obtaining version difference information based on the new loading order data; performing a rollback operation based on the status of the target object corresponding to the version difference information, obtaining the current loading status of the target object corresponding to the new loading order data after the rollback operation; and generating a new loading order based on the new loading order data and the current loading status for aircraft loading.

[0095] Optionally, the new loading order data is the loading order data newly received during the aircraft loading process or after the loading order has been calculated. After obtaining the new loading order data, it can be compared with the previous loading order data for the current flight item by item. The comparison dimensions can include dimensions that affect loading, such as cargo number / baggage number, target cabin class, destination, and weight, and the differences in different dimensions are recorded in the version difference information.

[0096] In one embodiment, version difference information may include three categories, specifically: Unchanged records: Cargo number, cargo space, destination, and weight are all consistent; mark the corresponding target object as "reserved". Change log: If the cabin class, destination, or weight changes, the corresponding target object will be marked as "requires rollback"; New record: For goods / luggage added in the new version, the corresponding target object will be marked as "to be loaded"; Delete Records: Goods / baggage that no longer exist in the new version will be marked as "requires rollback". The status of a target object can be determined as "retained", "requires rollback", or "pending loading".

[0097] Optionally, a rollback operation is performed based on the state of the target object corresponding to the version difference information, including: constructing a rollback candidate set based on the state of the target object, determining the cabin class corresponding to the rollback candidate set and the affected cabin class corresponding to the cabin class; generating a rollback closure based on the impact of the cabin class state change on the state of the affected cabin class, the rollback closure including the cabin class to be rolled back, the cabin class state change being generated based on the rollback operation of the target object in the first rollback candidate set; and pulling down the target object of the cabin class corresponding to the rollback closure.

[0098] Optionally, target objects marked as "required to be rolled back" can be added to the rollback candidate set. The information recorded in the rollback candidate set may include: cargo / baggage number, corresponding cargo hold, and current loading status (already on board / already in place / not yet on board).

[0099] Optionally, the current loading status of each target object in the rollback candidate set can be obtained, and the rollback operation to be taken can be determined based on the current status. Specifically, if the current loading status is "in place" (on-board verification completed): a "pull-down" operation needs to be performed, that is, physically removing the cargo / baggage from the hold and restoring it to the unloaded state; "on board" (off-board verification completed but on-board verification not completed): a "pull-down" operation needs to be performed to remove the cargo / baggage from the hold; "not on board" (only appears in the deletion record): no physical operation is required, and it is directly removed from the list of available loading slots.

[0100] Optionally, after determining the rollback action to be collected, the state of the corresponding cabin of the target object can also be obtained, and the impact on the affected cabin can be determined based on the change in the state. Based on the impact, the cabins that need to be rolled back are determined and added to the rollback candidate set, thereby generating a rollback closure.

[0101] In one embodiment, after a target object in the rollback candidate set is rolled back, the status of its cargo compartment changes, which may affect the compliance of other loaded cargo compartments. The specific analysis logic is as follows: For the cabin class (hereinafter referred to as cabin class 22P) recorded in the rollback candidate set, if the status of cabin class 22P changes from "loaded" to "unloaded" after the rollback, then query all cabin classes containing cabin class 22P in BeAffectedCabins. These cabin classes are the affected cabin classes of cabin class 22P. For each affected cabin class, if it is currently loaded and not in the rollback candidate set (i.e., it should have been retained), determine whether all other affected cabin classes in its BeAffectedCabins other than cabin class 22P are still loaded. If so, the affected cabin class can remain loaded and does not need to be rolled back; if not, that is, the rollback causes unloaded cabin classes to appear among the affected cabin classes of this cabin class, then the affected cabin class also needs to be rolled back and added to the rollback candidate set.

[0102] The above process is executed recursively until no new cabin slots are added to the rollback candidate set, forming the final rollback closure. Rollback propagation is not a "one-to-one" process, but rather it is determined layer by layer along the affected dependency chain. Rollback is only propagated when the rollback actually causes the affected constraints of a certain cabin slot to no longer be satisfied, thus avoiding excessive rollback.

[0103] Optionally, when performing a rollback operation based on the rollback closure, the rollback operation can be performed sequentially, starting from the end of the affected link (the first affected cargo hold). For each record requiring rollback, the secondary verification terminal pushes a "pull down" command to the onboard stevedore, displaying the identification information of the target object to be pulled down and its cargo hold location. The onboard stevedore physically removes the target object (cargo / baggage) and confirms the pull down operation at the terminal. The record status of the target object is restored to "unloaded," and the corresponding cargo hold is removed from the set of loaded cargo holds (i.e., all records for that cargo hold are rolled back). After completing the rollback operation, a log can also be written (operation type="pull down," recording the reason for the version change, the pulled cargo number, the original cargo hold location, the operator, and the operation time).

[0104] For unchanged records that are not in the rollback closure and are already loaded / positioned, a "confirm" command is pushed to the onboard loader's terminal. The loader confirms that the cargo / baggage does not require operation and retains its loading status. Write to the log (operation type="confirm", recording the reason for the version change, the cargo number confirmed to be retained, the cargo space, the operator, and the operation time).

[0105] Optionally, after the rollback is completed, the system can be re-initialized and recalculated based on the current installation order data and the actual loading status of the target object. The calculation process can be as follows: Reconstruct the loaded bay set: all bays containing loaded / placed records that have not been rolled back, as well as empty bays without target objects, to form a new loadedSet; Rebuild the collection to be loaded: The records restored after the rollback to "unloaded" + the records added by the new version installation order data are combined to form a new cabinsWithCargo; Recalculate the list of available cargo slots and the loading order using the new loadedSet and cabinsWithCargo as input; Recalculate the electronic fence: Update the fence range using the dynamic intersection of the new set of available bays and the set of bays to be operated; Refresh terminal interface: The terminals of the apron manager and loaders are updated synchronously, displaying the new list of loadable items and fence range, and the loading operation continues in the new order.

[0106] Alternatively, if there are data source restrictions on baggage, the processing logic for baggage during version changes can differ from that for cargo: Baggage with cargo numbers (AKE, etc.): Same as the target object, participate in version difference comparison, if the cabin class changes, enter the rollback process, and execute the above methods in full.

[0107] Loose baggage without a cargo number: Since loose baggage cannot be compared one by one between the old and new versions using cargo numbers, the following strategy can be adopted: Once the new version of the packing list data arrives, the bulk baggage area will display a complete list of all baggage without a cargo number (regardless of whether it has been loaded onto the plane). The original loading / insertion logic remains unchanged, and the completed operation status is retained; A new "Seat Confirmation" button has been added (displayed only when version number is greater than 1) to allow apron managers to confirm whether baggage that has been seated is still in the new version's cabin allocation. If the baggage's cabin class remains unchanged in the new version, the apron manager can click "Confirm Seating" and the baggage's status will remain unchanged. If the baggage's cabin class changes or no longer exists in the new version, and the apron manager does not confirm, the baggage must be re-boarded and repositioned. This strategy involves manual verification of the version adaptation for bulk luggage, but the system provides a complete list and operation entry points to ensure nothing is missed.

[0108] The above rollback method has the following advantages: Minimize job waste: By comparing each item and analyzing the propagation of the impact, the rollback scope is precisely controlled on the change records and their dependent links, while the unaffected installed content is left unchanged, avoiding the huge waste of a full reinstall.

[0109] Dependency consistency guarantee: Rollback propagation recursively judges along the affected dependency chain to ensure that the loading status after rollback still meets the constraints of the affected compartment, and there will be no inconsistent state such as "A was rolled back but B's loading dependency A has been loaded".

[0110] Fully automated reconstruction: After the rollback is completed, the loaded collection, the collection to be loaded, the loading sequence, and the electronic fence are all automatically reconstructed without manual intervention. Loaders and unloaders can continue their work by following the terminal prompts.

[0111] Complete chain of evidence: Each version change records the reason for the change, rollback records, and confirmation of retention records, forming a complete chain of evidence that "what changed, what was rolled back, what was retained, and why", meeting audit and traceability requirements.

[0112] Human-machine collaborative baggage matching: For loose baggage that cannot be automatically compared, a system-assisted confirmation entry is provided, rather than relying entirely on manual labor or completely blocking it, thus achieving a balance between accuracy and feasibility.

[0113] The concealment method of this application has the following advantages: Significantly improve the level of aircraft safety operation and eliminate "hidden loads" from the source: the prevention of hidden loads has been moved from "post-event manifest comparison and correction" to "in-event real-time locking and blocking". Through dual code binding and strong verification, the rate of human error such as incorrect loading and omission has been reduced to close to 0%, effectively mitigating the flight accident hazards caused by the imbalance of the aircraft's center of gravity (i.e., the "gray rhino" event in civil aviation safety).

[0114] Significantly improves on-site operational efficiency: The adoption of electronic loading instructions instead of traditional paper manifests eliminates information asymmetry among loading supervisors, stowage coordinators, and loading / unloading personnel, and greatly reduces the frequency of walkie-talkie communication per flight. Actual pilot data shows that the average time for loading verification and reconciliation per flight can be shortened by 5–8 minutes, which is beneficial for improving the on-time performance of hub airports.

[0115] Significantly reduces the workload and mental stress of frontline loading and unloading personnel: Through automatic comparison by system algorithms, the responsibilities of loading and unloading personnel have been successfully transformed from the traditional "100% manual verification executor" to "anomaly handler who only deals with system alarms," ​​greatly reducing mental fatigue under high-intensity operations.

[0116] Transparent and digitally traceable data throughout the entire process: Every scan, location, verification, and version rollback generates an electronic log with the operator's employee number, name, and precise timestamp. This log is tamper-proof and provides scientific data support for subsequent security management, data traceability, and process optimization.

[0117] Based on the same inventive concept, this application also proposes a method for preventing concealment, such as... Figure 5 As shown, this method is used for a secondary verification terminal, which is communicatively connected to the primary verification terminal. The method includes: S201: Receive the status information of the target object transmitted by the initial verification terminal. The status information is obtained by the initial verification terminal when it determines that there is a cabin to be loaded, obtains the loading information at the current time according to the loading order, obtains the second identification information of the target object in response to the input selection information, performs the initial verification according to the loading information and the second identification information, and sends it when it determines that the initial verification is successful.

[0118] Optionally, the loading order is determined based on the relationship between the loading order data and the cabin space. The loadable information includes a list of loadable cabin spaces and the first identification information of the corresponding target object. S202: In response to the verification command corresponding to the status information, obtain the cabin code and the third identification information of the target object on the cabin.

[0119] S203: Perform a second verification based on the third identification information and the encoding.

[0120] Optionally, a secondary verification is performed based on the third identification information and the code, including: comparing the third identification information with the loading order data; obtaining the target code of the cabin corresponding to the target object based on the loading order data, and comparing the target code with the cabin code; if the loading order data contains a target object corresponding to the third identification information and the target code matches the code, then the secondary verification is determined to be successful.

[0121] Based on the same inventive concept, this application also proposes an electronic device, please refer to [link to relevant documentation]. Figure 6 , Figure 6 This is a structural diagram of an electronic device provided in an embodiment of this application. (In conjunction with...) Figure 6 The electronic device described in this application is described in detail.

[0122] In this embodiment, the smart terminal includes a processor and a memory. The processor and the memory are communicatively connected. The memory stores program data, which is used to execute the method described in the above embodiment.

[0123] In this embodiment, the processor is the control center of the smart terminal. It connects various parts of the smart terminal via various interfaces and lines, and performs various functions and processes data by running or executing software programs and / or modules stored in the memory, and by calling data stored in the memory, thereby providing overall monitoring of the smart terminal. Optionally, the processor may include one or more processing units; preferably, the processor may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may also not be integrated into the processor.

[0124] The smart terminal also includes a power supply (such as a battery) to power various components. Preferably, the power supply can be connected to the processor logic through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system.

[0125] The memory can be used to store software programs and modules. The processor executes various functional applications and data processing of the smart terminal by running the software programs and modules stored in the memory. The memory can mainly include a program storage area and a data storage area. The program storage area can store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area can store data created according to the use of the smart terminal (such as audio data, phone book, etc.). In addition, the memory can include high-speed random access memory, and can also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0126] Based on the same inventive concept, this application also proposes a computer-readable storage medium, please refer to [link to relevant documentation]. Figure 7 , Figure 7 This is a structural diagram of an embodiment of the computer-readable storage medium of this application, in conjunction with... Figure 7 The computer-readable storage medium of this application is described.

[0127] In this embodiment, a computer-readable storage medium stores a computer program that is used to perform the methods described in the above embodiments.

[0128] The computer-readable storage medium may include, but is not limited to, floppy disks, optical disks, CD-ROMs (compact disc-read-only memory), magneto-optical disks, ROMs (read-only memory), RAMs (random access memory), EPROMs (erasable programmable read-only memory), EEPROMs (electrically erasable programmable read-only memory), magnetic cards or optical cards, flash memory, or other types of media / machine-readable media suitable for storing machine-executable instructions. The computer-readable storage medium may be a product not connected to a computer device or a component used in a computer device.

[0129] The terms "first," "second," "third," "fourth," "1," "2," etc. (if present) in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in a sequence other than that shown in the illustrations or text descriptions.

[0130] It should be understood that although arrows indicate various operation steps in the flowcharts of this application's embodiments, the order in which these steps are implemented is not limited to the order indicated by the arrows. Unless explicitly stated herein, in some implementation scenarios of this application's embodiments, the implementation steps in each flowchart can be executed in other orders as required. Furthermore, some or all steps in each flowchart, based on the actual implementation scenario, may include multiple sub-steps or multiple stages. Some or all of these sub-steps or stages can be executed at the same time, and each sub-step or stage can also be executed at different times. In scenarios where execution times differ, the execution order of these sub-steps or stages can be flexibly configured according to requirements, and this application's embodiments do not limit this.

[0131] The above description is only an optional implementation method for some implementation scenarios of this application. It should be noted that for those skilled in the art, other similar implementation methods based on the technical concept of this application without departing from the technical concept of this application also fall within the protection scope of the embodiments of this application.

Claims

1. A method for preventing hidden loads, characterized in that, For use in an initial verification terminal, wherein the initial verification terminal is communicatively connected to a secondary verification terminal, the method includes: Determine the available cargo slots to be loaded, and obtain the available loading information at the current moment based on the loading order. The loading order is determined based on the influence relationship between the loading order data and the cargo slots. The available loading information includes a list of available cargo slots and the first identification information of the corresponding target object. In response to the input selection information, the second identification information of the target object is obtained, and an initial verification is performed based on the loadability information and the second identification information. Once the initial verification is successful, the status information of the target object is sent to the secondary verification terminal so that the secondary verification terminal responds to the verification command corresponding to the status information, obtains the cabin code and the third identification information of the target object on the cabin, and performs secondary verification based on the third identification information and the code.

2. The method for preventing concealed loading according to claim 1, characterized in that, The step of obtaining the loadable information at the current moment based on the loading order includes: The loading order is determined based on the influence relationship between the loading order data and the cargo space. The current available cargo space is obtained according to the loading order. The affected cargo space corresponding to the available cargo space is the already loaded cargo space. A list of available loading spaces is generated based on the available loading spaces, and the first identification information of the target object corresponding to each available loading space in the list is recorded.

3. The method for preventing concealed loading according to claim 1, characterized in that, The process of obtaining the second identification information of the target in response to the input selection information includes: Display the list of available aircraft bays and receive selection information input based on the list of available aircraft bays; The target object to be loaded is determined based on the selection information, and the scanning device corresponding to the initial verification terminal is invoked to scan the target object to obtain the second identification information.

4. The method for preventing concealed loading according to claim 3, characterized in that, The initial verification is performed based on the installability information and the second identification information, including: Based on the loadability information, determine the first identification information corresponding to the target object to be loaded; If the first identification information and the second identification information match, then the verification is successful.

5. The method for preventing concealed loading according to claim 1, characterized in that, Detecting whether the first identification information and the second identification information match includes: Obtain the type of the target object, including goods and luggage; If the type is goods, then the code and / or weight corresponding to the goods are obtained according to the first identification information, and the code and / or weight are matched with the second identification information; If the type is luggage, then the destination station corresponding to the luggage is obtained according to the first identification information, and the destination station is matched with the second identification information.

6. The method for preventing concealed loading according to claim 1, characterized in that, The determination that the initial verification passed includes: An operation log is generated, the status information corresponding to the target object is updated, and new loadable information is generated. The operation log includes information about the target object as well as the corresponding operator, operation time, and operation type.

7. The method for preventing concealed loading according to claim 1, characterized in that, The method includes: Once it is confirmed that new installation order data has been detected, version difference information is obtained based on the new installation order data; Perform a rollback operation based on the status of the target object corresponding to the version difference information, and obtain the current loading status of the target object corresponding to the new installation order data after the rollback operation; A new loading sort is generated based on the new installation order data and the current loading status.

8. The anti-hidden content method according to claim 7, wherein a rollback operation is performed based on the state of the target object corresponding to the version difference information, comprising: Based on the state of the target object, a rollback candidate set is constructed, and the cabin class corresponding to the rollback candidate set and the affected cabin class corresponding to the cabin class are determined. A rollback closure is generated based on the impact of the state change of the cabin on the state of the affected cabin. The rollback closure includes the cabin to be rolled back, and the state change of the cabin is generated based on the rollback operation of the target object in the rollback candidate set. A rollback operation is performed based on the rollback closure, and the rollback operation includes unloading the loaded target object.

9. A method for preventing concealed loading, characterized in that, For a secondary verification terminal, the secondary verification terminal is communicatively connected to the primary verification terminal, the method includes: The system receives the status information of the target object transmitted by the initial verification terminal. The status information is obtained by the initial verification terminal based on the determination that there are currently unloaded cabins, the loading order, the current loading availability information, the second identification information of the target object in response to the input selection information, the initial verification based on the loading availability information and the second identification information, and the system sends the information when the initial verification is successful. The loading order is determined based on the influence relationship between the loading order data and the cabins. The loading availability information includes a list of available cabins and the first identification information of the corresponding target object. In response to the verification command corresponding to the status information, the cabin code and the third identification information of the target object on the cabin are obtained; A second verification is performed based on the third identification information and the encoding.

10. The method for preventing concealed loading according to claim 9, characterized in that, A secondary verification is performed based on the third identification information and the encoding, including: The third identification information is compared with the installation order data; Obtain the target code of the cabin corresponding to the target object based on the loading order data, and compare the target code with the code of the cabin. If the installation order data contains the target object corresponding to the third identification information and the target code is consistent with the code, then the secondary verification is confirmed to be successful.

11. An electronic device, characterized in that, The method includes a processor and a memory, the processor being communicatively connected to the memory, the memory storing program data, and the program data being used to execute the method as described in any one of claims 1-10.

12. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that is used to perform the method as described in any one of claims 1-10.

Images