Intelligent management and dispatching method and system for mobile portable terminal management and control cabinet

Abstract

This invention relates to an intelligent management and scheduling method and system for a control cabinet of a mobile portable terminal. The method includes: acquiring basic device status data of the mobile portable terminal; constructing a lifecycle health feature set of the mobile portable terminal at the current moment based on the basic device status data; obtaining device scheduling priority data based on the lifecycle health feature set; parsing task scheduling requests to obtain a candidate scheduling device set; controlling the control cabinet to execute the removal operation of the target device based on the candidate scheduling device set; performing consistency verification and operational status review on the target device before removal; confirming that the target device status verification and review are passed; completing device scheduling and marking the target device's status as task execution status; and updating the target device's lifecycle feature data and scheduling priority evaluation criteria based on the analysis results after the target device completes the task and returns to the cabinet. This invention can improve the reliability of scheduling.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, specifically to a method and system for intelligent management and scheduling of control cabinets for mobile portable terminals. Background Technology

[0002] Currently, various automation solutions exist in the industry for the management and scheduling of warehouse materials and goods. Chinese patent CN107767034A discloses a method and device for scheduling electricity meter warehouses. This method receives scheduling instructions through a distribution module, and a handling control module determines the consistency between the current address and the destination address, driving the handling equipment to physically move the materials, thus achieving automated warehousing and outbound flow for standardized electrical equipment. Chinese patent CN113065828A discloses an intelligent management and scheduling method for commodity inventory based on cloud data storage analysis. This method analyzes the real-time inventory levels of various types of goods in each store; analyzes the scheduling distances between each store and each warehouse; and analyzes the estimated scheduling time between each store and each warehouse, improving the efficiency of commodity inventory management and scheduling.

[0003] However, when mobile portable terminals are imaging devices (such as SLR cameras, drones, and imaging modules), these devices are not standardized static resources. Their scheduling needs depend not only on location but also on the device's "operating status" and "health." Existing technologies mainly focus on the physical location-based handling logic or inventory scheduling based on macroscopic traffic consumption, failing to perceive the battery health of devices within the terminal cabinet, the self-test status of lens modules, firmware version consistency, and the operational wear and tear of image sensors. Consequently, they cannot achieve refined scheduling based on the device's lifecycle. Summary of the Invention

[0004] This invention addresses the technical problems existing in the prior art by providing a mobile portable terminal-based intelligent management and scheduling method and system for control cabinets, which can improve the management and scheduling effect of control cabinets.

[0005] The technical solution of the present invention to solve the above-mentioned technical problems is as follows:

[0006] This invention provides an intelligent management and scheduling method for a control cabinet of a mobile portable terminal, the method comprising:

[0007] The operating status data of the mobile portable terminal stored in the control cabinet is obtained, and the operating status data is associated with the unique device identifier of the mobile portable terminal to obtain the basic device status data of the mobile portable terminal.

[0008] Based on the device status data, feature extraction and unified scale processing are performed on each of the operating status data to construct the life cycle health feature set of the mobile portable terminal at the current moment.

[0009] Based on the lifecycle health feature set, combined with the device's historical usage and expected operating capabilities, a comprehensive evaluation is performed on each of the mobile portable terminals to generate a scheduling priority index that reflects the suitability of the device to participate in task scheduling in the current state, thereby obtaining device scheduling priority data.

[0010] Upon receiving a task scheduling request for image acquisition, the task scheduling request is parsed to generate device adaptation conditions related to task execution. Based on the device scheduling priority data, mobile portable terminals that meet the device adaptation conditions are filtered and sorted to obtain a set of candidate scheduling devices.

[0011] Based on the candidate scheduling device set, the control cabinet is controlled to perform the out-of-cabinet operation of the target device, and before the out-of-cabinet operation, the target device is subjected to consistency verification and operation status review. After confirming that the target device status verification and review are passed, the device scheduling is completed and the status of the target device is marked as task execution status.

[0012] After the target device completes its task and returns to the cabinet, the operating status data of the target device is collected again, and the operating status data after returning to the cabinet is compared and analyzed with the basic data of the device status before leaving the cabinet to obtain the analysis results. Based on the analysis results, the life cycle characteristic data and scheduling priority evaluation criteria of the target device are updated.

[0013] This invention also provides an intelligent management and scheduling system for a control cabinet of a mobile portable terminal, the system comprising:

[0014] The data acquisition module is used to acquire the operating status data of the mobile portable terminal stored in the control cabinet, and associate the operating status data with the unique device identifier of the mobile portable terminal to obtain the basic device status data of the mobile portable terminal.

[0015] The feature construction module is used to extract features and perform unified scale processing on each of the operating status data based on the device status basic data, and construct the life cycle health feature set of the mobile portable terminal at the current moment.

[0016] The scheduling priority module is used to comprehensively evaluate each of the mobile portable terminals based on the set of life cycle health characteristics, combined with the historical usage and expected operating capacity of the devices, and generate a scheduling priority index that reflects the suitability of the device to participate in task scheduling in the current state, thereby obtaining device scheduling priority data.

[0017] The candidate scheduling module is used to parse the task scheduling request when it receives the task scheduling request for image acquisition, generate device adaptation conditions related to task execution, and filter and sort the mobile portable terminals that meet the device adaptation conditions according to the device scheduling priority data to obtain a set of candidate scheduling devices.

[0018] The task execution module is used to control the control cabinet to perform the out-of-cabinet operation of the target device according to the candidate scheduling device set, and to perform consistency verification and operation status review on the target device before out-of-cabinet operation. After confirming that the target device status verification and review are passed, the device scheduling is completed and the status of the target device is marked as task execution status.

[0019] The management and analysis module is used to re-collect the operating status data of the target device after the target device completes its task and returns to the cabinet, compare and analyze the operating status data after returning to the cabinet with the basic data of the device status before leaving the cabinet to obtain the analysis results, and update the life cycle characteristic data and scheduling priority evaluation basis of the target device based on the analysis results.

[0020] Furthermore, to achieve the above objectives, the present invention also proposes an electronic device, comprising: a memory for storing computer software programs; and a processor for reading and executing the computer software programs, thereby realizing the intelligent management and scheduling method for a mobile portable terminal control cabinet as described above.

[0021] Furthermore, to achieve the above objectives, the present invention also proposes a non-transitory computer-readable storage medium storing a computer software program, which, when executed by a processor, implements the intelligent management and scheduling method for a control cabinet of a mobile portable terminal as described above.

[0022] The beneficial effects of this invention are:

[0023] (1) This invention effectively solves the problem that the existing technology cannot perceive the actual operating status of the terminal by uniformly collecting the battery status, functional module self-test status, firmware version status and cumulative usage status of the mobile portable terminal in the control cabinet and constructing a set of health characteristics of the device life cycle.

[0024] (2) By comprehensively evaluating the health characteristics of the device life cycle and generating scheduling priority indicators, the present invention only filters and sorts devices that meet the task adaptation conditions and have high scheduling priority during the task scheduling stage, avoiding scheduling devices with insufficient power, abnormal functional modules or inconsistent firmware, thereby significantly reducing the probability of failure of image acquisition tasks due to device status mismatch.

[0025] (3) The present invention incorporates the historical usage of equipment, the operational decay status and the current life cycle health characteristics into a unified evaluation process, avoiding the dominance of single parameters or human experience in scheduling decisions, making the equipment scheduling results more objective, consistent and repeatable, and improving the overall scheduling reliability of the system. Attached Figure Description

[0026] Figure 1 A flowchart of a method for intelligent management and scheduling of a control cabinet for a mobile portable terminal provided by the present invention;

[0027] Figure 2 A schematic diagram of the structure of a mobile portable terminal control cabinet intelligent management and scheduling system provided by the present invention;

[0028] Figure 3 A schematic diagram of the hardware structure of a possible electronic device provided by the present invention;

[0029] Figure 4 This is a schematic diagram of the hardware structure of a possible computer-readable storage medium provided by the present invention. Detailed Implementation

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

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

[0032] In the description of this invention, the term "for example" is used to mean "used as an example, illustration, or description." Any embodiment described as "for example" in this invention is not necessarily to be construed as being more preferred or advantageous than other embodiments. The following description is provided to enable any person skilled in the art to make and use the invention. Details are set forth in the following description for purposes of explanation. It should be understood that those skilled in the art will recognize that the invention can be made without using these specific details. In other instances, well-known structures and processes will not be described in detail to avoid obscuring the description of the invention with unnecessary detail. Therefore, the invention is not intended to be limited to the embodiments shown, but is consistent with the broadest scope of the principles and features disclosed herein.

[0033] Please see Figure 1 The present invention provides a flowchart of an intelligent management and scheduling method for a control cabinet of a mobile portable terminal, comprising the following steps:

[0034] Step 201: Obtain the operating status data of the mobile portable terminal stored in the control cabinet, and associate the operating status data with the unique device identifier of the mobile portable terminal to obtain the basic device status data of the mobile portable terminal.

[0035] The operational status data includes at least battery status information, core functional module self-test status information, firmware version information, and cumulative usage status information. In some embodiments, the control cabinet may be equipped with an interface module for communicating with a mobile portable terminal. When the mobile portable terminal is stored in the control cabinet, the interface module automatically establishes a communication connection with the corresponding mobile portable terminal and collects the operational status data of the mobile portable terminal. The operational status data includes, but is not limited to, current battery status information, core functional module self-test results, firmware version information, and cumulative device usage status information.

[0036] Meanwhile, the control cabinet can read the unique device identifier of the mobile portable terminal and associate the collected operating status data with the corresponding unique device identifier for storage, thereby obtaining the basic device status data of the mobile portable terminal for subsequent status analysis and scheduling decisions.

[0037] In some embodiments, step 201 may further include:

[0038] The control cabinet establishes a communication connection with the mobile portable terminal, collects the battery status information, functional module self-test information and firmware version information of the mobile portable terminal, and obtains the original operating data of the device;

[0039] Based on the original operating data of the equipment, various types of operating status data are classified and time-stamped to obtain structured operating status data;

[0040] Based on the structured operational status data, it is associated with the device's unique identifier and stored to obtain the basic device status data of the mobile portable terminal.

[0041] In some embodiments, operational data acquisition between the control cabinet and the mobile portable terminal can be performed via wired or wireless communication interfaces, including but not limited to USB, UART, CAN, Bluetooth, Wi-Fi, or a dedicated serial bus. When the mobile portable terminal is inserted into or placed in the corresponding bracket within the control cabinet and establishes a physical or wireless connection with the control cabinet, the interface management module of the control cabinet detects the presence of the device and triggers the communication establishment process. The communication establishment process includes: device identifier reading, handshake protocol execution, and necessary authentication steps. Specifically, the control cabinet initiates a connection request to the mobile portable terminal and receives the unique device identifier (e.g., serial number, MAC address, or factory serial number) and device capability description information returned by the mobile portable terminal; the unique identifier is used for subsequent data association and indexing. During the authentication process, a simple handshake based on a device certificate or a pre-set key can be used to confirm the legitimacy of the connection. If necessary, an encrypted channel can be established for the communication link to ensure data transmission integrity. If authentication fails, the system records the abnormal event and performs retry, alarm, or manual intervention according to a preset strategy.

[0042] After communication and authentication are completed, the control cabinet can request operational status information from the mobile portable terminal via predefined device interface commands or data reporting protocols, or the mobile portable terminal can proactively report such information. Operational status information includes at least the following types:

[0043] Battery status information, such as current voltage, estimated remaining capacity (SOC), charge / discharge cycle count, charging status, internal resistance or temperature alarm indicators, etc.

[0044] Self-test information of functional modules, such as image sensor self-test results (including pixel defect statistics and black level drift detection results), lens module self-test results (including autofocus execution results and aperture response), communication module self-test and sensor response time, etc.

[0045] Firmware version information, including firmware version number, firmware release date, firmware checksum (e.g., CRC or hash digest), and compatibility identifier with the control cabinet's supported version list;

[0046] If the equipment supports it, other operational metrics such as cumulative uptime, last maintenance date, and summary of recent abnormal events can be collected simultaneously.

[0047] After receiving the above data, the control cabinet can verify the data integrity (e.g., check field format, check value matching, or communication layer CRC), and execute a retransmission request for records that fail verification or record the event as an abnormal record.

[0048] Furthermore, the collected operational status information, along with the aforementioned unique device identifier, collection timestamp (using a unified time zone format), and collection source identifier, can be encapsulated into a raw operational data record for the device (hereinafter referred to as "raw record"). The raw record retains the original fields and original message format for future auditing or backtracking. The raw record can be written to the local temporary storage of the control cabinet and asynchronously distributed to the central management server or cloud storage. Transaction protection or pre-write backup is employed during the writing process to reduce the risk of loss.

[0049] The raw records can be preprocessed to obtain structured runtime status data. Preprocessing may include:

[0050] a) Classify different fields in the original record according to data type. For example, classify battery-related fields as "power supply", sensor self-test results as "sensor", firmware information as "software / firmware", etc.

[0051] b) Generate standardized timestamps: unify the collected timestamps into a specified format (e.g., ISO-8601) and record the sequence number and timing relationship information of the collected events;

[0052] c) Perform preprocessing strategies for missing fields or outliers: imputate or mark imputable numeric items as "outlier / missing", and add outlier identifiers and error codes to items with incorrect format or exceeding the threshold.

[0053] d) Map and normalize field names, data types, and units according to a predefined data dictionary or pattern to ensure that similar metrics from different devices or firmware versions are structurally consistent.

[0054] After the above processing, the system can convert the original records into structured runtime status data records (hereinafter referred to as "structured records"). The structured records are logically divided into several field groups. Each field group contains a field name, field value, unit, time stamp and verification identifier, which facilitates subsequent feature extraction and statistical analysis.

[0055] In some embodiments, a mapping relationship can be established between structured records and corresponding unique device identifiers, and the mapped structured records can be written into the device status basic data warehouse. The storage of device status basic data can take the form of relational database tables or time-series databases, which should at least include the following index fields: unique device identifier, acquisition time, data category, and record version number. During storage, the data source (control cabinet number), transmission status, and data integrity check code can be recorded simultaneously. To meet reliability requirements, the storage mechanism can support write redundancy, logging, and version control, so that a complete historical trajectory can be obtained during backtracking or model training. After storage is completed, the system can trigger one or more of the following optional actions: queue the new record for use by the offline batch processing model; trigger the real-time health assessment module to perform a preliminary check; or send an alarm to the management platform or maintenance personnel when a critical anomaly is detected.

[0056] In the above process, if communication is interrupted, data is corrupted, or device identifier conflicts occur, the system will handle the situation according to a preset fault tolerance strategy, including: re-establishing the connection and retransmitting the request, writing the error record to the exception log table for manual review, or marking the device in an abnormal state and blocking its participation in the scheduling process until the problem is resolved. These fault tolerance and exception handling steps can ensure the authenticity and availability of the basic device status data.

[0057] Through the process described in this embodiment, the control cabinet can reliably establish a communication connection with the mobile portable terminal and complete initial authentication. It robustly collects and verifies the device's battery, functional module self-test, and firmware information. The raw data is categorized, time-stamped, and standardized into structured records. These structured records are then associated with the device's unique identifier and stored as basic device status data. This basic device status data provides an accurate and traceable data foundation for subsequent lifecycle feature construction, scheduling priority evaluation, and closed-loop updates.

[0058] Step 202: Based on the basic data of device status, perform feature extraction and unified scale processing on each operating status data to construct a set of life cycle health features of the mobile portable terminal at the current moment.

[0059] The lifecycle health feature set is used to characterize the availability and operational stability of mobile portable terminals, resulting in device lifecycle feature data. In some embodiments, the system can perform feature extraction processing on different types of operational status data, such as converting raw battery status data into battery health features and converting functional module self-test results into functional stability features.

[0060] Subsequently, a unified scale processing can be performed on the various extracted features, so that features from different sources and with different dimensions can be comprehensively analyzed under the same evaluation scale, thereby constructing a set of life cycle health features corresponding to the mobile portable terminal at the current moment, which is used to characterize the overall operational health status of the device.

[0061] In some embodiments, step 202 may further include:

[0062] Based on the basic equipment status data, the corresponding status features are extracted for different types of operating status data to obtain multiple status feature sub-items;

[0063] Based on the state feature sub-items, a uniform scaling process is performed on each state feature sub-item to obtain standardized state feature sub-items;

[0064] Based on the standardized state feature sub-items, a subset of lifecycle health features for mobile portable terminals is formed, and a set of lifecycle health features is constructed based on the subset of lifecycle health features.

[0065] In some embodiments, the system can first read the structured operating status data record corresponding to the mobile portable terminal from the device status basic data, and perform feature extraction processing on different types of operating status data according to the predefined status type classification rules.

[0066] Specifically, the state types include at least the following categories:

[0067] a) Power status data: including battery level, voltage, charge / discharge cycles, temperature, and related alarm indicators;

[0068] b) Functional module status data: including image sensor self-test results, lens module execution status, and focus or exposure response;

[0069] c) Software and firmware status data: including firmware version number, checksum, consistency identifier, and upgrade history;

[0070] d) Use and aging status data: including cumulative runtime, number of task executions, abnormal interruption records, etc.

[0071] For the different categories of data mentioned above, the system can convert the original fields into status feature sub-items that reflect the device's operating status according to preset feature mapping rules. For example, battery-related fields can be converted into battery health feature sub-items, functional module self-test results into functional stability feature sub-items, and firmware-related fields into system consistency feature sub-items.

[0072] After the above processing, the system can generate multiple state feature sub-items for each mobile portable terminal. The state feature sub-items are logically independent of each other and are used to characterize the state performance of the device under different operating dimensions.

[0073] In this embodiment, since different state feature items come from different types of operating state data, their numerical ranges, expression methods and evaluation directions are different. The system further performs uniform scale processing on each state feature item.

[0074] Standardized scaling includes, but is not limited to:

[0075] a) Map numerical features to a predefined uniform numerical range;

[0076] b) Convert Boolean or enumerated features into comparable state identifiers;

[0077] c) Add anomaly weight or confidence mark to feature items that have anomalies or missing values;

[0078] d) Perform structural consistency processing on similar features from different device models or firmware versions.

[0079] By using the above-mentioned unified scaling process, the various state feature sub-items are logically comparable and combinable, resulting in standardized state feature sub-items, which provide a foundation for subsequent comprehensive analysis.

[0080] In this embodiment, the system can group and integrate standardized state feature items according to predefined lifecycle dimension division rules, based on standardized state feature items, to form a subset of lifecycle health features for mobile portable terminals.

[0081] The lifecycle health feature subsets can correspond to different aspects of the device's lifecycle, such as power health subset, functional stability subset, system consistency subset, and usage degradation subset. Each lifecycle health feature subset consists of a set of interrelated standardized state feature sub-items, used to reflect the overall state of the device in that lifecycle dimension.

[0082] Furthermore, the system can aggregate and correlate the various lifecycle health feature subsets to construct a lifecycle health feature set for the mobile portable terminal at the current moment. This lifecycle health feature set is used to characterize the overall operational health and sustainable usage capability of the device, and serves as the basic input data for subsequent scheduling priority evaluation.

[0083] Through the processing flow of this embodiment, the system can convert multi-source, heterogeneous operational status data into well-structured and uniformly scaled lifecycle health features while maintaining the integrity and traceability of basic device status data. The resulting lifecycle health feature set can objectively reflect the health status of mobile portable terminals under different operational dimensions, providing a stable and repeatable input basis for device scheduling priority assessment.

[0084] In some embodiments, step 202 may further include:

[0085] Based on a subset of lifecycle health characteristics, historical usage records and abnormal records of mobile portable terminals are obtained to acquire historical status data.

[0086] Based on historical status data, a weighted and integrated subset of life cycle health characteristics is processed to obtain comprehensive health characteristic data.

[0087] Based on comprehensive health feature data, a set of lifecycle health features is generated to characterize the overall operating status of the equipment.

[0088] In some embodiments, the system may further access the historical data storage unit corresponding to the mobile portable terminal based on a subset of lifecycle health characteristics to obtain usage records and anomaly records generated by the mobile portable terminal during its historical operation.

[0089] Historical usage records may include, but are not limited to: cumulative device runtime, number of task executions, distribution of high-load runtime periods, and information on long-term idle or frequently used time periods; abnormal records may include, but are not limited to: functional module self-test failure records, task interruption records, battery abnormal alarm records, communication abnormal records, and maintenance or repair records.

[0090] After acquiring the aforementioned historical usage and anomaly records, the system can sort and correlate the relevant data by time, and match it with the corresponding unique device identifier to form historical status data characterizing the device's historical operating conditions. This historical status data logically corresponds to a subset of the lifecycle health characteristics at the current moment, and is used for subsequent comprehensive analysis.

[0091] In some embodiments, the system can perform weighted integration processing on the aforementioned subset of lifecycle health features based on historical state data. This weighted integration processing is not a simple summation, but rather assigns different integration weights to various features within the lifecycle health feature subset based on the differences in the degree of impact of different types of historical state data on the device's operating status.

[0092] Specifically, for historical usage records related to long-term stability (such as cumulative runtime or high load ratio), the system increases the proportion of their impact on lifecycle characteristics during the integration process; for short-term or occasional abnormal records, the system reduces the proportion of their impact on overall characteristics during the integration process, or only significantly affects the corresponding characteristics when abnormalities occur frequently.

[0093] Through the weighted integration process described above, the system can maintain sensitivity to the current operating status while incorporating the influence of historical operating trends, thereby generating comprehensive health characteristic data that reflects the overall operating status of the equipment.

[0094] In this embodiment, the system summarizes and organizes the health status under each life cycle dimension based on comprehensive health feature data, and generates a life cycle health feature set to characterize the overall operating status of the equipment.

[0095] The lifecycle health feature set logically comprises comprehensive feature results from multiple lifecycle dimensions, used to fully reflect the availability, operational stability, and continuous usability of mobile portable terminals at the current moment. This lifecycle health feature set serves as an important basis for subsequent scheduling priority evaluation and device selection, and is stored and continuously updated to adapt to changes in device operating status.

[0096] Through the historical state introduction and feature integration process in this embodiment, the system can comprehensively consider the current operating status characteristics of the mobile portable terminal with historical usage trends and abnormal situations, avoiding scheduling decisions based solely on instantaneous states. This improves the ability of the lifecycle health feature set to represent the true operating status of the device, providing a more stable and reliable foundation for subsequent scheduling decisions.

[0097] Step 203: Based on the lifecycle health feature set, combined with the device's historical usage and expected operating capabilities, conduct a comprehensive evaluation of each mobile portable terminal, generate a scheduling priority index that reflects the suitability of the device to participate in task scheduling in the current state, and obtain device scheduling priority data.

[0098] In some embodiments, the system can comprehensively assess the suitability of the device for current task scheduling based on a set of lifecycle health characteristics, combined with the historical usage and expected operational capabilities of the mobile portable terminal.

[0099] Through comprehensive evaluation, a corresponding scheduling priority index can be generated for each mobile portable terminal, and device scheduling priority data can be formed to reflect the priority order of different devices participating in image acquisition task scheduling in the current state.

[0100] In some embodiments, step 203 may further include:

[0101] Based on the set of lifecycle health characteristics, multiple state assessment elements are determined for scheduling evaluation;

[0102] Based on the status assessment elements, the current operating status of each mobile portable terminal is comprehensively analyzed to obtain the initial scheduling assessment results;

[0103] Based on the initial scheduling evaluation results, a corresponding first scheduling priority index is generated;

[0104] Based on the first scheduling priority index, the device scheduling priority data is obtained.

[0105] In this embodiment, the system can extract key state dimensions directly related to device scheduling from the lifecycle health feature set as state assessment elements required for scheduling evaluation. These state assessment elements reflect the core capabilities and risk levels of the mobile portable terminal when performing image acquisition tasks.

[0106] Specifically, the condition assessment elements include at least one or more of the following: power stability elements reflecting the continuous operating capability of the equipment, functional module stability elements reflecting the reliability of image acquisition, firmware and software compatibility elements reflecting the consistency of the system environment, and usage degradation elements reflecting the long-term effects of equipment use.

[0107] The system can extract corresponding feature values ​​from the life cycle health feature set according to the preset scheduling evaluation rules, and use them as the set of status evaluation elements for scheduling evaluation, providing an input basis for subsequent scheduling analysis.

[0108] In this embodiment, the system can perform a comprehensive analysis of the current operating status of each mobile portable terminal based on a set of status assessment elements. The comprehensive analysis processes the impact of different status assessment elements in a unified manner according to a pre-set scheduling assessment logic, in order to form a judgment result on the overall suitability of the device scheduling.

[0109] During this process, the system can identify the interrelationships between state assessment elements. For example, when the equipment has a significant deficiency in a certain key state assessment element, its overall assessment result will decrease accordingly; when all state assessment elements are in a stable state, its overall assessment result will increase accordingly.

[0110] Based on the above comprehensive analysis, the system generates a corresponding initial scheduling evaluation result for each mobile portable terminal, which is used to characterize the basic suitability of the device to participate in task scheduling in the current state.

[0111] In this embodiment, the system can quantify the scheduling order of mobile portable terminals based on the initial scheduling evaluation results and generate a corresponding first scheduling priority index.

[0112] The first scheduling priority index is used to reflect the relative priority relationship of different mobile portable terminals in the same scheduling scenario. Its generation process maintains consistency with the life cycle health feature set and scheduling evaluation elements to ensure that the basis for the formation of scheduling priority is traceable and interpretable.

[0113] In this embodiment, the system can organize and encapsulate the generated first scheduling priority index and associate it with the corresponding unique device identifier to form device scheduling priority data.

[0114] Equipment scheduling priority data can be stored according to fields such as equipment identifier, evaluation time, scheduling priority index, and status summary, which are used for filtering, sorting, and scheduling control of equipment in subsequent task scheduling requests. Through the above processing, the system completes the transformation from a set of lifecycle health characteristics to a data format that can be directly used for scheduling decisions.

[0115] Through the scheduling evaluation element determination and scheduling priority generation process in this embodiment, the system can perform a structured evaluation of the scheduling suitability of mobile portable terminals based on unified life cycle health characteristics, and form clear scheduling priority data, thereby providing a stable and reliable decision-making basis for subsequent task matching and equipment selection.

[0116] In some embodiments, step 203 may also be labeled as follows:

[0117] Based on the historical task execution data of the mobile portable terminal, obtain the device usage intensity information and obtain the usage attenuation parameter;

[0118] Based on the attenuation parameter, the first scheduling priority index is dynamically corrected to obtain the corrected second scheduling priority index.

[0119] Based on the second scheduling priority index, multiple mobile portable terminal devices are scheduled and sorted to obtain device scheduling priority data.

[0120] In this embodiment, the system performs statistical analysis on the actual usage intensity of the device based on the historical task execution data of the mobile portable terminal, so as to reflect the load level of the device within a certain time period.

[0121] Specifically, historical task execution data includes at least one or more of the following: the number of times the device executes a task within a preset period, the duration of a single task and the cumulative runtime, and records of abnormal interruptions or performance degradation during task execution.

[0122] Based on the historical task execution data, the system can comprehensively assess the equipment's usage frequency, continuous operation, and cumulative load to obtain usage attenuation parameters that characterize the degree of equipment performance degradation. These parameters reflect the potential performance degradation trend that may occur due to long-term or high-frequency use.

[0123] In this embodiment, after obtaining the usage attenuation parameter, the system can incorporate it into the evaluation process of the first scheduling priority index to dynamically correct the scheduling priority of the device.

[0124] Specifically, when the attenuation parameter represents a device under high usage intensity, the system lowers the corresponding first scheduling priority indicator; when the attenuation parameter represents a device under relatively low usage intensity, the system maintains or appropriately raises the corresponding first scheduling priority indicator. Through the above correction process, the scheduling priority can simultaneously reflect the current health status of the device and its historical usage load.

[0125] After dynamic correction, the system generates a corresponding second scheduling priority index for each mobile portable terminal. The second scheduling priority index is used to more realistically characterize the overall suitability of the device in the current scheduling scenario.

[0126] In this embodiment, the system performs unified scheduling and sorting of multiple mobile portable terminals based on a second scheduling priority index.

[0127] Specifically, the system sorts the mobile and portable terminals that meet the task adaptation conditions according to the size of the second scheduling priority index, forming a scheduling queue with a clear order, and associates the sorting result with the corresponding unique device identifier to obtain device scheduling priority data.

[0128] The device scheduling priority data is used in subsequent task scheduling requests to prioritize or sequentially call candidate devices, thereby ensuring the reliability of task execution while achieving a balanced allocation of device usage.

[0129] By introducing attenuation parameters and a dynamic correction mechanism for scheduling priorities in this embodiment, the system can further consider the potential impact of long-term equipment use on the basis of the original scheduling evaluation results. This makes the generated equipment scheduling priority data more consistent with the actual operating status of the equipment, effectively avoiding excessive consumption of a single device due to long-term high-frequency scheduling, thereby improving the overall system stability and the rationality of equipment management.

[0130] In some embodiments, the device scheduling priority data may include a comprehensive scheduling priority index, which can be expressed as:

[0131] ;

[0132] in, It is a comprehensive scheduling priority index. It is a characteristic value of the device's battery health. These are health characteristics of the image sensor and lens module. These are firmware consistency and compatibility characteristics. It is the cumulative high-intensity use attenuation factor of the equipment. The expected runtime of the current task is... α is the predicted remaining stable operating time of the equipment, β and γ are the first weight, second weight and third weight respectively; δ is the attenuation adjustment coefficient, which is used to adjust the influence of the cumulative high-intensity use attenuation factor of the equipment on the comprehensive scheduling priority index; the specific values ​​corresponding to α, β, γ and δ can be preset, and are not specifically limited here.

[0133] It is understood that device scheduling priority data includes a comprehensive scheduling priority index used to quantify the suitability of mobile portable terminals for task scheduling. This comprehensive scheduling priority index is used to make horizontal comparisons among multiple candidate devices to assist the system in completing scheduling ranking and target device selection.

[0134] This represents the battery health characteristic value of the device, used to reflect the degree of battery capacity degradation, voltage stability, and discharge performance; when A higher value indicates that the equipment has a strong ability to operate continuously.

[0135] These represent health characteristics of the image sensor and lens module, reflecting the self-test status of the imaging unit, response stability, and the operational status of the optical module; when A higher value indicates that the device is more suitable for performing tasks that require high image quality.

[0136] This represents firmware consistency and compatibility characteristics, used to reflect the degree of matching between the device firmware version and the current task execution environment; when A higher value indicates that the device has a high degree of task adaptability at the software level.

[0137] The above three factors are comprehensively adjusted through corresponding weight parameters α, β, and γ in order to highlight the importance of different operating state characteristics in different application scenarios.

[0138] This represents the cumulative high-intensity use degradation factor of the equipment, used to reflect the performance degradation trend of the equipment due to long-term or frequent execution of high-load tasks. In the construction of the comprehensive scheduling priority index, the system introduces... The relevant suppression terms constrain the overall scheduling priority index of a device when its usage degradation is high, thereby reducing its priority in scheduling. This method prevents the device from being continuously scheduled at high frequencies due to overuse.

[0139] The system can further introduce a task runtime matching factor to evaluate the matching relationship between the current remaining stable operating capacity of the equipment and the task requirements.

[0140] in, Indicates the expected runtime of the current task. This represents the predicted remaining stable runtime of the equipment. The system uses the ratio between these two values ​​to reflect the likelihood that the equipment will complete its current task without experiencing performance anomalies.

[0141] By introducing a runtime matching factor, the comprehensive scheduling priority index increases when the remaining stable operating capacity of the equipment is significantly greater than the expected runtime of the task; conversely, the comprehensive scheduling priority index decreases when the equipment's operating capacity is close to or lower than the task requirements.

[0142] The system can compare and sort multiple mobile portable terminals based on a comprehensive scheduling priority index, and use the sorting results as an important component of the device scheduling priority data.

[0143] By using this comprehensive scheduling priority index, the system can prioritize the use of equipment that is in good operating condition, has a reasonable load, and has sufficient stable operating capability to perform tasks, provided that the task adaptability conditions are met. This improves the success rate of image acquisition tasks and extends the service life of the overall equipment group.

[0144] By introducing a comprehensive scheduling priority index, this solution enables a multi-dimensional, dynamic, and adjustable evaluation of the scheduling priority of mobile portable terminals. This allows equipment scheduling to no longer rely solely on physical location or static inventory information, but to comprehensively reflect the health status of the equipment, historical usage degradation, and task adaptability, thereby significantly improving the rationality and reliability of scheduling decisions.

[0145] Step 204: Upon receiving a task scheduling request for image acquisition, the task scheduling request is parsed to generate device adaptation conditions related to task execution. Based on the device scheduling priority data, mobile portable terminals that meet the device adaptation conditions are filtered and sorted to obtain a set of candidate scheduling devices.

[0146] In some embodiments, when the system receives a task scheduling request for image acquisition, it can first parse the task scheduling request to obtain task requirement information such as the time required for task execution, functional requirements, and operating environment requirements.

[0147] Based on the task requirements information, device compatibility conditions related to task execution are generated. Based on device scheduling priority data, mobile portable terminals that meet the device compatibility conditions are filtered and sorted to obtain a set of candidate scheduling devices for task execution.

[0148] In some embodiments, step 204 may further include:

[0149] Obtain the task scheduling request, parse the execution duration, functional requirements and runtime environment requirements of the task scheduling request, and obtain the task requirement information;

[0150] Based on the task requirements, generate the corresponding device compatibility conditions;

[0151] Based on device compatibility conditions and device scheduling priority data, mobile portable terminals are filtered and sorted to obtain a set of candidate scheduling devices.

[0152] In this embodiment, the system can receive task scheduling requests initiated by upper-layer business systems or manual scheduling terminals through a task scheduling interface. The task scheduling request includes at least basic parameter information related to the execution of the image acquisition task. The system parses the task scheduling request, extracting the task's execution duration, functional requirements, and operating environment requirements to form structured task requirement information. Specifically: the execution duration characterizes the continuous running time required for the task under normal execution conditions; the functional requirements characterize the task's requirements for enabling device functional modules, including but not limited to image acquisition, positioning, communication, or storage functions; and the operating environment requirements characterize the external conditions under which the task is executed, including ambient temperature, lighting conditions, space constraints, or communication environment requirements.

[0153] Through the above parsing process, the task scheduling request is transformed from the original instruction form into task requirement information that can be used for device compatibility determination.

[0154] In this embodiment, the system generates device adaptation conditions that match the task execution based on task requirement information. Specifically, the system can map the execution duration in the task requirement information to the remaining stable operating capacity of the device to form adaptation conditions in terms of device operating capacity; map functional requirements to the available status of device functional modules to form adaptation conditions in terms of device functional integrity; and map operating environment requirements to the device's environmental adaptability or operating parameter range to form adaptation conditions in terms of device environmental adaptability.

[0155] Through the above processing, the system forms a set of device compatibility conditions for device screening. These conditions are used to limit the basic range of mobile portable terminals that can participate in this task scheduling.

[0156] In this embodiment, the system can perform preliminary screening of multiple mobile portable terminals in the control cabinet based on device compatibility conditions, eliminate devices that do not meet the basic requirements for task execution, and obtain a subset of candidate devices that meet the device compatibility conditions.

[0157] Based on this, the system can further combine equipment scheduling priority data to sort the subset of candidate devices. The sorting process is based on the equipment scheduling priority data, ensuring that devices with higher scheduling priorities are given priority in the sorting results.

[0158] Finally, based on the filtering and sorting results, the system can generate a set of candidate scheduling devices for subsequent scheduling execution, and provide this set of candidate scheduling devices to the control cabinet execution module for the selection of target devices and cabinet exit control.

[0159] Through the task scheduling request parsing, device adaptation condition generation, and scheduling priority linkage filtering mechanism in this embodiment, the system can further refine the sorting based on the comprehensive operating status of the devices, while ensuring that the devices meet the basic requirements of the tasks. This effectively improves the accuracy and success rate of task scheduling and avoids task execution failures caused by insufficient device capabilities or mismatched status.

[0160] Step 205: Based on the candidate scheduling device set, control cabinet executes the out-of-cabinet operation of the target device, and performs consistency verification and operation status review on the target device before out-of-cabinet operation. After confirming that the target device status verification and review are passed, the device scheduling is completed and the status of the target device is marked as task execution status.

[0161] In some embodiments, the control cabinet control mechanism can drive the corresponding target device to perform an out-of-cabinet operation. Before the out-of-cabinet operation, a consistency check and operational status verification are performed on the target device to confirm the consistency between the device identifier, device status, and scheduling instructions.

[0162] Once the target device status verification and operation status review are confirmed to be passed, the device scheduling operation is completed, and the target device status is marked as task execution status to avoid the device being repeatedly scheduled during task execution.

[0163] Step 206: After the target device completes its task and returns to the cabinet, re-collect the target device's operating status data, compare and analyze the operating status data after returning to the cabinet with the basic device status data before leaving the cabinet, and update the target device's life cycle characteristic data and scheduling priority evaluation criteria based on the analysis results.

[0164] In some embodiments, after the target device completes the image acquisition task and is put back into the control cabinet, the system can re-acquire the operating status data of the target device, and compare and analyze the operating status data after returning to the cabinet with the basic data of the device status before leaving the cabinet to obtain the analysis results of the device status change.

[0165] Based on the analysis results, the lifecycle health characteristic data of the target equipment and the corresponding scheduling priority evaluation criteria are updated, so that the subsequent scheduling process can reflect the actual usage of the equipment and form a continuously optimized equipment management and scheduling mechanism.

[0166] In some embodiments, step 206 may further include:

[0167] Based on the operating status data re-collected after the target device is returned to the cabinet, generate the operating status data after the device is returned to the cabinet;

[0168] The analysis results are obtained by comparing and analyzing the equipment status data after returning to the cabinet with the basic equipment status data before leaving the cabinet.

[0169] Based on the changes in equipment status, the lifecycle health characteristic data and scheduling priority assessment criteria of the target equipment are updated.

[0170] In some embodiments, after the target device completes the image acquisition task and returns to the control cabinet, the control cabinet re-establishes a communication connection with the target device and triggers the acquisition process of device operating status data.

[0171] Specifically, the system can collect data on the target device's battery status, functional module operating status, and firmware operation status according to the same collection strategy as before it was taken out of the cabinet. The collected data is then processed in a unified format and time-stamped to generate post-return operating status data that characterizes the device's status after it is returned to the cabinet.

[0172] Through the above processing, the operational status data after returning to the cabinet is kept consistent with the basic equipment status data before leaving the cabinet in terms of data structure and collection dimensions, thus providing a reliable data foundation for subsequent comparative analysis.

[0173] In this embodiment, the system can perform item-by-item comparative analysis of the operating status data after the device is returned to the cabinet and the basic device status data before the target device is removed from the cabinet. Specifically, the system can analyze multiple dimensions such as changes in battery health, changes in functional module status, and changes in firmware operating status to identify performance consumption, status anomalies, or functional changes that occur during task execution.

[0174] Through the above comparative analysis, the system generates equipment state change results to characterize the changes in equipment state before and after the execution of this task. The equipment state change results serve as the analysis results for subsequent lifecycle health assessment and scheduling strategy adjustment.

[0175] In this embodiment, the system can update the lifecycle health characteristic data and scheduling priority evaluation criteria of the target device based on the device status change results.

[0176] Specifically, when the change in equipment status indicates that the equipment performance has been significantly depleted or shows an abnormal trend, the system adjusts the lifecycle health characteristic data of the target equipment accordingly to reflect its latest operating status; when the change in equipment status indicates that the equipment status is stable or the depletion is low, the system maintains or appropriately modifies the corresponding lifecycle health characteristic data.

[0177] Meanwhile, the system can synchronize the updated lifecycle health feature data for subsequent equipment scheduling priority evaluation, so that the basis for equipment scheduling priority evaluation can continuously reflect the actual operating status of the equipment, thereby realizing dynamic adaptive updating of scheduling strategies.

[0178] Through the cabinet status comparison and dynamic update mechanism in this embodiment, the system can promptly correct the life cycle health characteristics and scheduling evaluation basis of the equipment after the equipment completes the task, avoiding long-term reliance on historical static data for scheduling decisions, thereby improving the precision of equipment management and ensuring the reliability and stability of subsequent task scheduling.

[0179] Please see Figure 2 , Figure 2 This is a schematic diagram of the structure of an intelligent management and scheduling system for a mobile portable terminal control cabinet provided by the present invention.

[0180] like Figure 2 As shown in the embodiment of the present invention, an intelligent management and scheduling system for a mobile portable terminal control cabinet includes:

[0181] The data acquisition module 301 is used to acquire the operating status data of the mobile portable terminal stored in the control cabinet, and associate the operating status data with the unique device identifier of the mobile portable terminal to obtain the basic device status data of the mobile portable terminal.

[0182] The feature construction module 302 is used to extract features and perform unified scale processing on each operating status data based on the basic data of device status, and construct a set of life cycle health features of the mobile portable terminal at the current moment.

[0183] The scheduling priority module 303 is used to comprehensively evaluate each mobile portable terminal based on the set of life cycle health characteristics, combined with the historical usage and expected operating capacity of the device, and generate a scheduling priority index that reflects the suitability of the device to participate in task scheduling in the current state, thereby obtaining device scheduling priority data.

[0184] The candidate scheduling module 304 is used to parse the task scheduling request when it receives the task scheduling request for image acquisition, generate device adaptation conditions related to task execution, and filter and sort the mobile portable terminals that meet the device adaptation conditions according to the device scheduling priority data to obtain a set of candidate scheduling devices.

[0185] The task execution module 305 is used to control the control cabinet to perform the out-of-cabinet operation of the target device according to the candidate scheduling device set, and to perform consistency verification and operation status review on the target device before out-of-cabinet operation. After confirming that the target device status verification and review are passed, the device scheduling is completed and the status of the target device is marked as the task execution status.

[0186] The management and analysis module 306 is used to re-collect the operating status data of the target device after the target device completes its task and returns to the cabinet, compare and analyze the operating status data after returning to the cabinet with the basic data of the device status before leaving the cabinet to obtain the analysis results, and update the life cycle characteristic data and scheduling priority evaluation basis of the target device based on the analysis results.

[0187] Please see Figure 3 , Figure 3 This is a schematic diagram illustrating an embodiment of the electronic device provided in this invention. For example... Figure 3 As shown, an embodiment of the present invention provides an electronic device 400, including a memory 410, a processor 420, and a computer program 411 stored in the memory 410 and executable on the processor 420. When the processor 420 executes the computer program 411, it performs the following steps:

[0188] Obtain the operating status data of the mobile portable terminal stored in the control cabinet, and associate the operating status data with the unique device identifier of the mobile portable terminal to obtain the basic device status data of the mobile portable terminal.

[0189] Based on the basic data of device status, feature extraction and unified scale processing are performed on each operating status data to construct a set of life cycle health features of the mobile portable terminal at the current moment.

[0190] Based on the lifecycle health feature set, combined with the device's historical usage and expected operating capabilities, a comprehensive evaluation of each mobile portable terminal is conducted to generate a scheduling priority index that reflects the suitability of the device to participate in task scheduling in the current state, thus obtaining device scheduling priority data.

[0191] Upon receiving a task scheduling request for image acquisition, the task scheduling request is parsed to generate device adaptation conditions related to task execution. Based on device scheduling priority data, mobile portable terminals that meet the device adaptation conditions are filtered and sorted to obtain a set of candidate scheduling devices.

[0192] Based on the candidate scheduling device set, the control cabinet executes the out-of-cabinet operation of the target device, and performs consistency verification and operation status review on the target device before out-of-cabinet operation. After confirming that the target device status verification and review are passed, the device scheduling is completed and the status of the target device is marked as task execution status.

[0193] After the target device completes its task and returns to the cabinet, the operating status data of the target device is collected again. The operating status data after returning to the cabinet is compared and analyzed with the basic data of the device status before leaving the cabinet to obtain the analysis results. Based on the analysis results, the life cycle characteristic data and scheduling priority evaluation basis of the target device are updated.

[0194] Please see Figure 4 , Figure 4 This is a schematic diagram illustrating an embodiment of a computer-readable storage medium provided by an embodiment of the present invention. For example... Figure 4 As shown, this embodiment provides a computer-readable storage medium 500 on which a computer program 411 is stored. When the computer program 411 is executed by a processor, it performs the following steps:

[0195] Obtain the operating status data of the mobile portable terminal stored in the control cabinet, and associate the operating status data with the unique device identifier of the mobile portable terminal to obtain the basic device status data of the mobile portable terminal.

[0196] Based on the basic data of device status, feature extraction and unified scale processing are performed on each operating status data to construct a set of life cycle health features of the mobile portable terminal at the current moment.

[0197] Based on the lifecycle health feature set, combined with the device's historical usage and expected operating capabilities, a comprehensive evaluation of each mobile portable terminal is conducted to generate a scheduling priority index that reflects the suitability of the device to participate in task scheduling in the current state, thus obtaining device scheduling priority data.

[0198] Upon receiving a task scheduling request for image acquisition, the task scheduling request is parsed to generate device adaptation conditions related to task execution. Based on device scheduling priority data, mobile portable terminals that meet the device adaptation conditions are filtered and sorted to obtain a set of candidate scheduling devices.

[0199] Based on the candidate scheduling device set, the control cabinet executes the out-of-cabinet operation of the target device, and performs consistency verification and operation status review on the target device before out-of-cabinet operation. After confirming that the target device status verification and review are passed, the device scheduling is completed and the status of the target device is marked as task execution status.

[0200] After the target device completes its task and returns to the cabinet, the operating status data of the target device is collected again. The operating status data after returning to the cabinet is compared and analyzed with the basic data of the device status before leaving the cabinet to obtain the analysis results. Based on the analysis results, the life cycle characteristic data and scheduling priority evaluation basis of the target device are updated.

[0201] It should be noted that the descriptions of each embodiment in the above embodiments have different focuses. For parts that are not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0202] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0203] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A system that specifies functions in one or more boxes.

[0204] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including an instruction set implemented in a process. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0205] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0206] Although preferred embodiments of the invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including both the preferred embodiments and all changes and modifications falling within the scope of the invention.

[0207] Obviously, those skilled in the art can make various modifications and variations to this invention without departing from its spirit and scope. Therefore, if these modifications and variations fall within the scope of the claims of this invention and their equivalents, this invention also intends to include these modifications and variations.

Claims

1. A method for intelligent management and scheduling of a control cabinet of a mobile portable terminal, characterized in that, The method includes: Obtain the operating status data of the mobile portable terminal stored in the control cabinet, and associate the operating status data with the unique device identifier of the mobile portable terminal to obtain the basic device status data of the mobile portable terminal. Based on the device status data, feature extraction and unified scale processing are performed on each of the operating status data to construct a set of lifecycle health features of the mobile portable terminal at the current moment. Based on the lifecycle health feature set, combined with the device's historical usage and expected operating capabilities, a comprehensive evaluation is performed on each of the mobile portable terminals to generate a scheduling priority index that reflects the suitability of the device to participate in task scheduling in the current state, thereby obtaining device scheduling priority data. Upon receiving a task scheduling request for image acquisition, the task scheduling request is parsed to generate device adaptation conditions related to task execution. Based on the device scheduling priority data, mobile portable terminals that meet the device adaptation conditions are filtered and sorted to obtain a set of candidate scheduling devices. Based on the candidate scheduling device set, the control cabinet is controlled to perform the out-of-cabinet operation of the target device, and before the out-of-cabinet operation, the target device is subjected to consistency verification and operation status review. After confirming that the target device status verification and review are passed, the device scheduling is completed and the status of the target device is marked as task execution status. After the target device completes its task and returns to the cabinet, the operating status data of the target device is collected again, and the operating status data after returning to the cabinet is compared and analyzed with the basic data of the device status before leaving the cabinet to obtain the analysis results. The life cycle characteristic data and scheduling priority evaluation basis of the target device are updated according to the analysis results. This includes generating a scheduling priority index that reflects the suitability of a device for participating in task scheduling in its current state, resulting in device scheduling priority data, including: Based on the lifecycle health feature set, multiple status assessment elements for scheduling evaluation are determined. These status assessment elements include power stability elements reflecting the continuous operation capability of the equipment, functional module stability elements reflecting the reliability of image acquisition, firmware and software compatibility elements reflecting the consistency of the system environment, and usage attenuation elements reflecting the long-term effects of equipment use. Based on the aforementioned status assessment elements, a comprehensive analysis is performed on the current operating status of each mobile portable terminal to obtain the initial scheduling assessment result. Based on the initial scheduling evaluation results, a corresponding first scheduling priority index is generated; Based on the historical task execution data of the mobile portable terminal, device usage intensity information is obtained, and usage attenuation parameters are derived. Based on the attenuation parameter, the first scheduling priority index is dynamically corrected to obtain the corrected second scheduling priority index. Based on the second scheduling priority index, the multiple mobile portable terminals are scheduled and sorted to obtain the device scheduling priority data.

2. The method of claim 1, wherein the method further comprises: Obtain basic device status data for the mobile portable terminal, including: The control cabinet establishes a communication connection with the mobile portable terminal, collects the battery status information, functional module self-test information and firmware version information of the mobile portable terminal, and obtains the original operating data of the device; Based on the original operating data of the equipment, the various types of operating status data are classified and time-stamped to obtain structured operating status data; Based on the structured operational status data, it is associated with the unique identifier of the device and stored to obtain the basic device status data of the mobile portable terminal.

3. The method of claim 2, wherein the method further comprises: Construct a set of lifecycle health characteristics for the mobile portable terminal at the current moment, including: Based on the basic equipment status data, corresponding status features are extracted for different types of operating status data to obtain multiple status feature sub-items; Based on the state feature sub-items, a uniform scaling process is performed on each of the state feature sub-items to obtain standardized state feature sub-items; Based on the standardized state feature sub-items, a lifecycle health feature subset of the mobile portable terminal is formed, and a lifecycle health feature set is constructed based on the lifecycle health feature subset.

4. The method of claim 3, wherein the method further comprises: The lifecycle health feature set is constructed based on a subset of lifecycle health features, including: Based on the subset of lifecycle health features, obtain the historical usage records and abnormal records of the mobile portable terminal to obtain historical status data; Based on the historical state data, the subset of life cycle health features is weighted and integrated to obtain comprehensive health feature data; Based on the comprehensive health feature data, a set of lifecycle health features is generated to characterize the overall operating status of the equipment.

5. The method of claim 1, wherein the method further comprises: The obtained candidate scheduling device set includes: Obtain the task scheduling request, parse the execution duration, functional requirements and operating environment requirements of the task scheduling request, and obtain task requirement information; Based on the task requirements information, generate the corresponding device compatibility conditions; Based on the device compatibility conditions and the device scheduling priority data, the mobile portable terminals are filtered and sorted to obtain the candidate scheduling device set.

6. The method of claim 5, wherein the method further comprises: Update the lifecycle characteristic data and scheduling priority evaluation criteria of the target device based on the analysis results, including: Based on the operating status data re-collected after the target device is returned to the cabinet, the operating status data after the device is returned to the cabinet is generated. The analysis results are obtained by comparing and analyzing the equipment status data after returning to the cabinet with the basic equipment status data before leaving the cabinet. Based on the changes in the device status, the lifecycle health characteristic data and scheduling priority evaluation criteria of the target device are updated.

7. The method of claim 6, wherein the method further comprises: The operational status data includes at least battery status information, core functional module self-test status information, firmware version information, and cumulative usage status information. The lifecycle health feature set is used to characterize the availability and operational stability of the mobile portable terminal, thereby obtaining device lifecycle feature data.

8. A mobile portable terminal management and control cabinet intelligent management and scheduling system, characterized in that, The system includes: The data acquisition module is used to acquire the operating status data of the mobile portable terminal stored in the control cabinet, and associate the operating status data with the unique device identifier of the mobile portable terminal to obtain the basic device status data of the mobile portable terminal. The feature construction module is used to extract features and perform unified scale processing on each of the operating status data based on the device status basic data, and construct the life cycle health feature set of the mobile portable terminal at the current moment. The scheduling priority module is used to comprehensively evaluate each of the mobile portable terminals based on the set of life cycle health characteristics, combined with the historical usage and expected operating capacity of the devices, and generate a scheduling priority index that reflects the suitability of the device to participate in task scheduling in the current state, thereby obtaining device scheduling priority data. The candidate scheduling module is used to parse the task scheduling request when it receives the task scheduling request for image acquisition, generate device adaptation conditions related to task execution, and filter and sort the mobile portable terminals that meet the device adaptation conditions according to the device scheduling priority data to obtain a set of candidate scheduling devices. The task execution module is used to control the control cabinet to perform the out-of-cabinet operation of the target device according to the candidate scheduling device set, and to perform consistency verification and operation status review on the target device before out-of-cabinet operation. After confirming that the target device status verification and review are passed, the device scheduling is completed and the status of the target device is marked as task execution status. The management and analysis module is used to re-collect the operating status data of the target device after the target device completes its task and returns to the cabinet, compare and analyze the operating status data after returning to the cabinet with the basic data of the device status before leaving the cabinet to obtain the analysis results, and update the life cycle characteristic data and scheduling priority evaluation basis of the target device based on the analysis results. This involves generating a scheduling priority index that reflects the suitability of a device for task scheduling in its current state, resulting in device scheduling priority data, including: Based on the lifecycle health feature set, multiple status assessment elements for scheduling evaluation are determined. These status assessment elements include power stability elements reflecting the continuous operation capability of the equipment, functional module stability elements reflecting the reliability of image acquisition, firmware and software compatibility elements reflecting the consistency of the system environment, and usage attenuation elements reflecting the long-term effects of equipment use. Based on the aforementioned status assessment elements, a comprehensive analysis is performed on the current operating status of each mobile portable terminal to obtain the initial scheduling assessment result. Based on the initial scheduling evaluation results, a corresponding first scheduling priority index is generated; Based on the historical task execution data of the mobile portable terminal, device usage intensity information is obtained, and usage attenuation parameters are derived. Based on the attenuation parameter, the first scheduling priority index is dynamically corrected to obtain the corrected second scheduling priority index. Based on the second scheduling priority index, the multiple mobile portable terminals are scheduled and sorted to obtain the device scheduling priority data.

Images