Measurement and control baseband device management method and related device

Abstract

The application discloses a kind of management methods and related equipment of test and control baseband equipment.It is used for non-ground network communication terminal, comprising: receiving the test and control task instruction issued, parsing test and control task instruction;Based on target test and control mode and task running parameter, mode configuration file and reconstruction scheduling command are generated and issued to reconfigurable scheduling intermediate layer, so that reconfigurable scheduling intermediate layer loads the signal processing function module corresponding to the target test and control mode, to establish the mapping relationship between signal processing function module and the logical resource, computing resource, intermediate frequency transceiver channel resource and synchronous clock resource of the test and control baseband equipment;Parameter configuration is carried out, and the test and control task corresponding to target test and control mode is started.It can solve the problem that although the existing test and control baseband based on software radio technology can realize limited system switching through software loading, the existing scheme still has the problems of incomplete system coverage and insufficient reconfigurable switching capability.

Description

Technical Field

[0001] The embodiments of this application relate to the aerospace field, and more specifically, the present invention relates to a method for managing measurement and control baseband equipment and related equipment. Background Technology

[0002] With the rapid development of the aerospace industry, the number of launches and mission types of various aerospace targets, such as satellites, launch vehicles, and near-space vehicles, have increased significantly. The telemetry, tracking, and command (TT&C) communication systems used for different types of aerospace targets and different mission phases of the same target vary considerably. Furthermore, in actual TT&C missions, only a single TT&C system for the corresponding scenario needs to be operated within the same mission period. However, equipment needs to have the ability to switch between different missions and targets quickly and without interruption. This places higher demands on the multi-system compatibility, flexible configuration, reliable operation, and engineering deployment capabilities of ground-based TT&C equipment. As the core unit of the ground-based TT&C system, the TT&C baseband undertakes core functions such as remote control and telemetry, ranging and velocity measurement, and two-way data transmission. Its architecture and performance directly determine the mission coverage and operational efficiency of the TT&C system.

[0003] Traditional telemetry, tracking, and command (TT&C) basebands often employ a fixed, specialized design. A single device can only adapt to a single TT&C system and a fixed mission scenario. When facing complex TT&C missions involving multiple target types and multiple system switching, multiple dedicated baseband devices with different systems must be stacked. This results in high deployment costs, large data center space requirements, difficulties in multi-device collaborative scheduling, and cumbersome mode switching processes, making it unsuitable for the current development needs of the aerospace TT&C industry. While software-defined radio (SDR)-based TT&C basebands can achieve limited system switching through software loading and have become the mainstream development direction, existing solutions still suffer from core problems such as incomplete system coverage and insufficient reconfigurable switching capabilities. Summary of the Invention

[0004] The summary section introduces a series of simplified concepts, which will be further explained in detail in the detailed description section. The summary section of this invention is not intended to limit the key features and essential technical features of the claimed technical solution, nor is it intended to determine the scope of protection of the claimed technical solution.

[0005] To address the shortcomings of existing software-defined radio (SDR)-based telemetry and control baseband systems, which, while enabling limited system switching via software loading, still suffer from incomplete system coverage and insufficient reconfigurable switching capabilities, this invention proposes a telemetry and control baseband equipment management method. This method includes: Receive measurement and control task instructions from local users or remotely issued by the station control system, and parse the measurement and control task instructions to obtain the target measurement and control mode, task operation parameters and task cycle information; Based on the target measurement and control mode and the task operation parameters, generate a mode configuration file and a reconstructed scheduling command; The mode configuration file and the reconfiguration scheduling command are sent to the reconfigurable scheduling intermediate layer so that the reconfigurable scheduling intermediate layer loads the signal processing function module corresponding to the target measurement and control mode, so as to establish the mapping relationship between the signal processing function module and the logic resources, computing resources, intermediate frequency transceiver channel resources and synchronous clock resources of the measurement and control baseband equipment. Based on the mapping relationship, parameters are configured for at least one of the uplink, intermediate frequency receiving link, remote control loop self-loop link, telemetry processing link, and speed and distance measurement processing link, and the measurement and control task corresponding to the target measurement and control mode is started.

[0006] Secondly, the present invention also proposes a measurement and control baseband device, the device including reconfigurable signal processing firmware; The reconfigurable signal processing firmware includes: a general-purpose low-level driver layer, a reconfigurable scheduling intermediate layer, and a mode-specific function module library; The mode-specific function module library includes signal processing function modules corresponding to at least two measurement and control modes. The reconfigurable scheduling intermediate layer is used to load the signal processing function module corresponding to the target measurement and control mode from the mode-specific function module library according to the mode configuration file and the reconfiguration scheduling command, and establish a resource mapping relationship between the signal processing function module and the hardware resource pool, so that the core signal processing board is reconfigured into a measurement and control baseband processing link corresponding to the target measurement and control mode.

[0007] Thirdly, an electronic device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program stored in the memory to implement the steps of the measurement and control baseband device management method as described in any of the first aspects above.

[0008] Fourthly, the present invention also proposes a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the measurement and control baseband device management method of any of the above claims in the first aspect.

[0009] In summary, the telemetry and control baseband equipment management method proposed in this application can improve the multi-mode adaptability of a single telemetry and control baseband device. Since the signal processing functional modules corresponding to the target telemetry and control mode can be loaded according to the task, and logic resources, computing resources, intermediate frequency transceiver channel resources, and synchronization clock resources can be remapped according to the task, the same device can adapt to different tasks such as standard telemetry and control, spread spectrum telemetry and control, two-way data transmission, and rocket telemetry, without needing to configure independent baseband devices for each task. Furthermore, it can reduce the complexity of manual configuration during task switching. The management software parses task instructions into mode configuration files and reconfiguration scheduling commands, and performs legality verification before issuing them, reducing the workload of manually configuring underlying parameters item by item, and also reducing the probability of link failure due to parameter mismatch. For example, task personnel only need to select the target mode and input key task parameters, and the system can automatically generate the corresponding link configuration without manually determining which functional modules should be loaded onto which resources. Furthermore, this scheme improves the reliability of mode reconfiguration. The reconfigurable scheduling intermediate layer does not simply load functional modules; instead, it establishes mapping relationships between functional modules and logical resources, computing resources, intermediate frequency transceiver channel resources, and synchronization clock resources, giving the reconfiguration process clear resource ownership and link structure. This avoids different functional modules competing for the same hardware resources and prevents task startup failures due to incomplete link structures. Moreover, this scheme is better suited for unattended or remote centralized control scenarios. Since task commands can originate from local users or be remotely issued by the station control system, and the management software can automatically parse, verify, generate configurations, and trigger reconfiguration, the telemetry and control station can complete task preparation and mode switching with minimal human intervention. For example, in scenarios where multiple satellites pass overhead consecutively, the station control system can sequentially issue telemetry and control task commands for different targets according to the task plan. The equipment automatically configures the corresponding modes and parameters based on different targets, thereby reducing the operational burden on the field. Attached Figure Description

[0010] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit this specification. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings: Figure 1 This application provides a schematic flowchart of a measurement and control baseband equipment management method. Figure 2 This is a schematic diagram illustrating an application scenario of a measurement and control baseband device provided in an embodiment of this application. Figure 3 A schematic diagram illustrating the working principle of a reconfigurable signal processing firmware for a measurement and control baseband device provided in this application embodiment; Figure 4 This is a schematic diagram of the structure of a measurement and control baseband device management electronic device provided in an embodiment of this application. Detailed Implementation

[0011] The terms "first," "second," "third," "fourth," 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 described herein can be implemented in a sequence other than that illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus. The technical solutions of the embodiments of this application will now be clearly and completely described in conjunction with the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them.

[0012] In some technologies, multi-mode measurement and control baseband equipment based on software-defined radio (SDR) architecture falls into two categories in terms of core technical solutions. The first category is dedicated multi-mode measurement and control basebands, employing FPGA combined with a customized DSP hardware platform. They develop fixed signal processing links and software programs for 2-3 mainstream measurement and control modes, enabling only limited mode switching and basic operating parameter configuration. Furthermore, mode switching requires interrupting the current task and reloading the firmware, failing to achieve uninterrupted online seamless switching. The accompanying software only supports basic local parameter configuration and status monitoring, lacking comprehensive remote operation and maintenance, automated testing, and full-process task scheduling functions. The second category is general-purpose SDR measurement and control platforms, employing a modular hardware architecture and a general-purpose SDR processing environment. These platforms can be adapted to different measurement and control modes through secondary development. While some solutions utilize a CPCI bus architecture, they lack a standardized 2U rack-mount design, making them unsuitable for the engineering deployment requirements of standard racks in measurement and control equipment rooms. Simultaneously, the platform lacks built-in mature functional IP cores for all-scenario measurement and control modes, requiring users to perform extensive secondary development to achieve engineering applications of different measurement and control modes. The mode switching process is complex, and one-click online reconfiguration under specific task scenarios is not possible. Therefore, these solutions cannot achieve coverage of standard TT&C telemetry and control, non-coherent spread spectrum telemetry and control, two-way data transmission, rocket telemetry, and integrated high-altitude and low-altitude full-scenario telemetry and control systems through time-sharing multiplexing of a single device. A single device cannot adapt to the system switching requirements of different aerospace targets and different mission stages. In multi-mission scenarios, multiple dedicated devices must be stacked, which significantly increases the deployment cost, space occupation, and coordination scheduling difficulty of the telemetry and control system. The reconfigurability and mode switching capabilities of these solutions have inherent limitations. They can only achieve limited adjustments to basic operating parameters and cannot complete the software-defined reconfiguration of the entire baseband signal processing link. Switching between different telemetry and control systems requires recompiling and loading firmware, interrupting the current telemetry and control task, or even restarting the device. It is impossible to achieve seamless online switching between different tasks and cannot guarantee the continuity of telemetry and control tasks. At the same time, these solutions do not optimize hardware resources for single-mode time-sharing operation scenarios, cannot achieve pooled reuse of hardware resources in all modes, have low hardware utilization, long development cycles for adapting to new telemetry and control systems, and most of them do not adopt a standardized CPCI modular bus architecture, resulting in insufficient board-level functional expansion and equipment maintenance capabilities. It also cannot simultaneously meet the high-performance measurement and control requirements of different scenarios, such as multi-mode time-sharing and full-scenario performance. In limited system switching, it generally suffers from problems such as narrow Doppler dynamic adaptation range, long signal acquisition time under low signal-to-noise ratio, insufficient ranging and velocity measurement accuracy, and large degradation of demodulation threshold. It cannot simultaneously meet the high-performance measurement and control requirements of different scenarios such as conventional satellite measurement and control, rocket high-dynamic telemetry, and high-speed data transmission of high-orbit spacecraft. At the same time, it lacks complete automated functions such as system self-testing, self-closed-loop testing, and bit error rate statistics. The efficiency of on-site debugging, performance calibration and fault diagnosis of the equipment is extremely low, and the operation and maintenance costs are high.Furthermore, existing solutions suffer from weak remote control and security capabilities, supporting only basic local parameter configuration and simple network communication. They lack robust remote mode switching, automated task scheduling, and online equipment upgrade capabilities, failing to meet the centralized control requirements of unattended telemetry and control stations. Simultaneously, they lack effective mechanisms to protect core sensitive data such as spread spectrum pseudocodes and telemetry and control keys from unauthorized access, resulting in insufficient security for data storage and retrieval, thus failing to meet the security and confidentiality requirements of high-level aerospace telemetry and control missions. Therefore, to address the issues of incomplete system coverage and insufficient reconfigurable switching capabilities in existing software-defined radio-based telemetry and control basebands, please refer to [reference needed]. Figure 1 , Figure 1 The flowchart of a measurement and control baseband equipment management method provided in this application embodiment can specifically include steps S110 to S140.

[0013] S110 receives measurement and control task instructions input by local users or remotely issued by the station control system, and parses the measurement and control task instructions to obtain the target measurement and control mode, task operation parameters and task cycle information.

[0014] S120, Based on the target measurement and control mode and the task operation parameters, generate a mode configuration file and a reconstructed scheduling command.

[0015] S130, the mode configuration file and the reconfiguration scheduling command are sent to the reconfigurable scheduling intermediate layer so that the reconfigurable scheduling intermediate layer loads the signal processing function module corresponding to the target measurement and control mode, so as to establish the mapping relationship between the signal processing function module and the logic resources, computing resources, intermediate frequency transceiver channel resources and synchronous clock resources of the measurement and control baseband equipment.

[0016] S140, based on the mapping relationship, configure the parameters of at least one of the uplink, intermediate frequency receiving link, remote control loop self-loop link, telemetry processing link and speed and distance measurement processing link, and start the measurement and control task corresponding to the target measurement and control mode.

[0017] Understandably, the structure of traditional telemetry and control baseband equipment, where fixed hardware links correspond to fixed telemetry and control systems, can be transformed into a structure where a unified hardware resource pool supports different telemetry and control modes. Multi-mode baseband management software parses task requirements, and a reconfigurable scheduling intermediate layer loads signal processing modules and maps hardware resources, enabling the same telemetry and control baseband equipment to automatically form different telemetry and control baseband processing links based on different tasks. Traditional telemetry and control baseband equipment typically embeds functions such as modulation, demodulation, ranging, velocity measurement, remote control encoding, and telemetry decoding into specific links. When a task switches from standard telemetry and control to spread spectrum telemetry and control, or from satellite telemetry to rocket telemetry, it often requires replacing equipment, reloading firmware, manually adjusting numerous parameters, or even restarting the equipment. The equipment does not abstract hardware capabilities into schedulable resources, nor does it encapsulate signal processing capabilities under different telemetry and control modes into loadable functional modules.

[0018] For example, after the measurement and control baseband equipment is powered on, the industrial-grade industrial control computer platform starts the multi-mode baseband management software. The management software first loads the device driver, communication service, configuration management service, and monitoring interface. Subsequently, the core signal processing board loads the general-purpose low-level driver layer and the reconfigurable scheduling intermediate layer, and performs status checks on the intermediate frequency input channel, intermediate frequency output channel, remote control loop input channel, clock chip, interface chip, memory, bus communication link, etc. The checks may include: confirming whether the clock source is locked, confirming whether the sampling clock is stable, confirming whether the intermediate frequency input and output channels are responsive, confirming whether the storage unit can read the mode configuration file and function module file, confirming whether the management software can communicate normally with the signal processing board through the high-speed parallel bus or other internal communication links, and confirming whether the reconfigurable scheduling intermediate layer is in a command-receiving state. If the checks pass, the device enters the task-waiting scheduling state; if the checks fail, the management software can display specific abnormalities on the monitoring interface, such as "synchronization clock not locked", "intermediate frequency receiving channel initialization failed", or "mode function module library unreadable", etc.

[0019] For example, telemetry and control (TT&C) mission instructions can come from two types of entry points: one is through local users selecting a mission template, filling in parameters, and submitting via a monitoring interface; the other is through the station control system remotely issuing mission plans via a network interface. After receiving the mission instruction, the management software parses the instruction fields, extracting information such as the target TT&C mode, target number, mission start time, mission end time, uplink parameters, downlink parameters, remote control parameters, telemetry parameters, and ranging and velocity measurement parameters. The target TT&C mode can be standard TT&C, non-coherent spread spectrum TT&C, two-way data transmission, rocket telemetry, or integrated TT&C. Mission operation parameters can include code rate, modulation method, subcarrier frequency, spreading code rate, receiving center frequency, intermediate frequency bandwidth, loop bandwidth, ranging system, ranging audio frequency, pseudocode parameters, encoding method, decoding method, output power, and receiving gain. Mission cycle information can include mission preparation time, link establishment time, formal TT&C time, mission end time, and mode release time.

[0020] For example, the management software calls the corresponding parameter templates and constraint rules according to the target measurement and control mode, and organizes the task parameters input by the user or issued by the station control system into a mode configuration file. This configuration file may include mode identifiers, functional module identifiers, uplink parameters, downlink parameters, ranging and velocity measurement parameters, intermediate frequency channel parameters, clock configuration parameters, resource requirement information, and status reporting requirements. Simultaneously, the management software generates a reconfiguration scheduling command, specifying which signal processing functional modules need to be loaded, which old resources need to be released, which processing links need to be established, and which channels and clocks need to be initialized. Legality verification can be divided into parameter range verification, mode matching verification, link consistency verification, and resource availability verification. Parameter range verification is used to determine whether the code rate, bandwidth, gain, sampling rate, output power, etc., exceed the equipment's supported range. Mode matching verification is used to determine whether a certain parameter is suitable for the current target measurement and control mode. For example, the spread spectrum code rate parameter is usually suitable for spread spectrum measurement and control mode; if it is incorrectly entered and forcibly enabled in a non-spread spectrum mode, a parameter mismatch should be indicated. Link consistency check is used to determine whether the uplink modulation parameters, remote control coding parameters, and small loop check parameters are consistent, and whether the downlink receiving parameters, telemetry decoding parameters, and frame format parameters are consistent. Resource availability check is used to determine whether the logic resources, computing resources, intermediate frequency channel resources, and clock resources of the current core signal processing board can meet the requirements of the target mode.

[0021] For example, after receiving the mode configuration file and reconfiguration scheduling command, the reconfigurable scheduling middle layer first parses the set of functional modules required by the target telemetry and control mode. For instance, the standard telemetry and control mode may require a remote control encoding module, an uplink modulation module, a downlink demodulation module, a telemetry decoding module, a ranging processing module, and a velocity processing module; the spread spectrum telemetry and control mode may also require functional modules such as spread spectrum code generation, pseudo-code acquisition, and pseudo-code tracking; the rocket telemetry mode may require a fast acquisition module and a high-speed telemetry processing module suitable for high-dynamic scenarios. Subsequently, the reconfigurable scheduling middle layer retrieves the corresponding modules from the mode-specific functional module library and allocates logical and computational resources according to the resource requirements of each module. For parts that require real-time high-speed processing, they can be mapped to logical resources first; for parts that require flexible calculation or complex control, they can be mapped to computational resources. At the same time, the intermediate frequency input channel is bound to the downlink receiving and processing link, the intermediate frequency output channel is bound to the uplink modulation link, the remote control loop input channel is bound to the loop comparison link, and the synchronization clock resource is configured as a timing reference that meets the current sampling rate, symbol rate, and ranging and velocity accuracy requirements.

[0022] For example, based on the resource mapping results reported by the reconfigurable scheduling intermediate layer, the management software confirms that each type of functional module has been loaded onto the corresponding resource, and then writes parameters to each link. For the uplink, the management software can write the remote control frame format, encoding method, scrambling rules, and command verification rules to the remote control processing module, and the modulation method, output sampling rate, output power, subcarrier parameters, or baseband shaping filter parameters to the signal modulation module. For the intermediate frequency receiving link, the management software can write the center frequency, sampling rate, receiving gain, filter bandwidth, automatic gain control parameters, carrier acquisition range, and code synchronization parameters to the receiving module. For the remote control small loop self-loop link, the management software can configure the sampling parameters, comparison window, comparison field, and anomaly criteria of the small loop input channel, enabling the device to confirm whether the command was correctly formed through small loop feedback after the remote control command is output. For the telemetry processing link, the management software can configure descrambling rules, decoding method, frame synchronization word, data output format, bit error rate statistics period, frame error statistics rules, and frame loss judgment rules. For the speed and distance measurement processing link, the management software can configure sidetone ranging or pseudocode ranging parameters, time stamping method, Doppler estimation window, speed calculation cycle, and measurement result validity criteria.

[0023] In some examples, it also includes: During the execution of the measurement and control mission, the operating status data, link status data, signal processing results, and measurement and control service data of the measurement and control baseband equipment are collected. The operating status data, link status data, signal processing results, and measurement and control service data are centrally displayed and managed through a monitoring interface. After the measurement and control task is completed, the remote control data, telemetry data, speed and distance measurement data, operation logs and task reports generated by the measurement and control task are classified and stored, so that the measurement and control baseband equipment enters the waiting state to receive the next measurement and control task instruction.

[0024] For example, after the measurement and control task is started, the multi-mode baseband management software can uniformly register the status data of modules such as the equipment monitoring module, intermediate frequency receiving module, remote control processing module, telemetry processing module, speed and distance measurement processing module, and acquisition processing module to the corresponding data channel of the monitoring interface. The equipment monitoring module periodically reads the status of the core signal processing board, clock unit, interface communication unit, and storage unit, such as whether the temperature exceeds the threshold, whether the voltage is stable, whether the clock is locked, and whether the interface experiences packet loss or communication timeout. The intermediate frequency receiving module continuously reports the received signal level, carrier synchronization status, bit synchronization status, frame synchronization status, and demodulation status. The remote control processing module reports the remote control command encoding, framing, scrambling, small-loop comparison results, and command execution status. The telemetry processing module reports the descrambling, decoding, and deframing results, as well as the bit error rate, number of mis-frames, and number of lost frames. The speed and distance measurement processing module reports the distance measurement results, speed measurement results, measurement validity criteria, and data generation status. After receiving the above data, the monitoring interface can centrally display it according to the task operation logic. For example, the same task page can display device health status, uplink status, downlink status, remote control loop verification results, telemetry data processing status, speed and distance measurement results, and current alarm information. For critical data, colors, text prompts, status labels, or curves can be set for display. For instance, carrier lock status can be displayed as "locked" or "unlocked," bit error rate can be displayed as a real-time value and trend curve, and distance measurement results can be displayed as the current distance value and validity status. For status management, the monitoring interface not only displays data but can also trigger prompts based on preset rules. For example, when the bit error rate consistently exceeds a threshold, it can indicate a decline in link quality; when the temperature approaches its upper limit, it can indicate abnormal heat dissipation; and when the loop comparison fails, it can indicate that the remote control command needs to be reviewed. After the measurement and control task is completed, the multi-mode baseband management software establishes a data directory or database record based on the task identifier, target identifier, task time, measurement and control mode, and data type. Remote control data can be saved according to command number, transmission time, command content, small-scale comparison results, and execution status; telemetry data can be saved according to reception time, frame number, original code content, decoding result, error statistics, and forwarding status; speed and distance measurement data can be saved according to measurement time, distance value, speed value, validity flag, and calculation parameters; operation logs can save user operations, system status changes, module status switching, anomaly prompts, and handling processes; task reports can summarize basic task information, link operation status, remote control execution status, telemetry reception quality, speed and distance measurement results, and anomalies. After storage, the system marks the current task's working status as completed, releases the management context occupied by the task, and puts the device into a waiting-for-scheduling state.

[0025] In some examples, the process further includes, before sending the pattern configuration file and the reconfigurable scheduling command to the reconfigurable scheduling middleware layer: For the target measurement and control mode, at least one of the modulation scheme, code rate, loop bandwidth, ranging mode, receiving gain, sampling rate, filter bandwidth and acquisition and tracking parameters is checked for range, mode matching and resource usage. If the task operation parameters do not meet the parameter constraints of the target measurement and control mode, or if the resource requirements corresponding to the task operation parameters exceed the available resource margin of the measurement and control baseband equipment, a parameter anomaly prompt will be generated and the reconfiguration scheduling command will be prevented from being issued. If the task operation parameters meet the parameter constraints of the target measurement and control mode, and the resource requirements corresponding to the task operation parameters do not exceed the available resource margin of the measurement and control baseband equipment, the mode configuration file and the reconfiguration scheduling command are generated.

[0026] For example, multi-mode baseband management software can preset parameter constraint tables and resource requirement models for each target telemetry and control mode. The parameter constraint table records the allowed modulation scheme, code rate range, loop bandwidth range, ranging mode type, receiver gain range, sampling rate range, filter bandwidth range, and acquisition and tracking parameter range for that mode. The resource requirement model records the logic resources, computing resources, intermediate frequency transceiver channel resources, and synchronization clock resources required by that mode under different parameter conditions. For example, high code rate telemetry processing usually requires more logic and computing resources; wide acquisition range and complex tracking algorithms may increase computing resource consumption; bidirectional data transmission may simultaneously occupy uplink and downlink high-speed processing resources. When the user or station control system submits the task operation parameters, the management software first performs range verification. For example, it determines whether the code rate is within the range supported by the target mode, whether the loop bandwidth is consistent with the signal dynamic characteristics and the range supported by the receiver algorithm, whether the receiver gain is within the hardware-configurable range, and whether the sampling rate matches the intermediate frequency input / output channel capabilities. Subsequently, mode matching verification is performed. For example, if the target telemetry and control mode is rocket telemetry, the focus is on verifying whether the high-speed telemetry processing, acquisition and tracking parameters, and receiving bandwidth match; if the target telemetry and control mode is spread spectrum telemetry and control, the focus is on verifying whether the spreading code rate, pseudo-code parameters, and despreading processing parameters are complete and meet the mode requirements. Next, a resource occupancy check is performed, which calculates the expected resource requirements based on the target mode and parameters and compares them with the current available resource reserves. Available resource reserves can be provided by the reconfigurable scheduling middleware layer or the equipment monitoring module, including the current proportion of idle logical resources, available computing resources, the number of idle intermediate frequency channels, available clock configuration capabilities, and storage space. When any check fails, the management software generates a parameter anomaly message and prevents the reconfiguration scheduling command from being issued. The anomaly message should point to a specific reason, such as the code rate exceeding the current mode's supported limit, the ranging mode not matching the target telemetry and control mode, the receiving bandwidth exceeding the configurable range of the intermediate frequency receiving channel, or the expected logical resource occupancy exceeding the current available resource reserves. When all checks pass, the management software saves the task parameters to the mode configuration file and generates a reconfiguration scheduling command. The mode configuration file can contain mode identifiers, parameter sets, functional module identifiers, link configuration items, and resource requirement descriptions; the refactoring scheduling command can contain instructions such as loading target modules, releasing old modules, establishing resource mappings, and initializing links.

[0027] In some examples, it also includes: The execution status of the current measurement and control task is confirmed through the reconfigurable scheduling intermediate layer; When the current measurement and control task has been completed, unload the old signal processing function module corresponding to the current measurement and control mode, and release the logic resources, computing resources, intermediate frequency transceiver channel resources and synchronization clock resources occupied by the old signal processing function module; Load a new signal processing function module corresponding to the target measurement and control mode from the preset measurement and control mode function module library, and perform load integrity verification, timing synchronization verification and link status verification on the new signal processing function module; If the load integrity check, the timing synchronization check, and the link status check all pass, the telemetry and control baseband device is confirmed to have entered the task-ready state corresponding to the target telemetry and control mode.

[0028] For example, after receiving a command related to the target mode, the reconfigurable scheduling middle layer first reads the current task status flag. This status flag can be maintained by the multi-mode baseband management software, device control module, or task scheduling module, and includes at least the following states: standby, task preparation, task execution, task completion, and task finished. Only when the current state is task finished or standby is the old module unloading process allowed; if the current state is still task execution, the reconfigurable scheduling middle layer refuses to unload and returns a status message indicating that the current task is not finished. During the old module unloading phase, the reconfigurable scheduling middle layer stops the functional modules according to the dependencies of the old mode links. For example, it first stops data output and task processing, then stops modulation and demodulation processing, and finally releases the underlying channels and clock configurations. Then, it releases the logical resources, computing resources, intermediate frequency transceiver channel resources, and synchronization clock resources occupied by the old signal processing functional modules, and clears the old mode link mapping table. The release process can record the resource release results, such as whether a certain logical partition was successfully released, whether a certain intermediate frequency channel returned to an idle state, and whether a certain clock configuration was unbound. During the new module loading phase, the reconfigurable scheduling intermediate layer reads the new signal processing function module corresponding to the target mode from the pre-set telemetry and control mode function module library. If the target mode is standard telemetry and control, then standard remote control, telemetry, and ranging / velocity measurement related modules are loaded; if the target mode is spread spectrum telemetry and control, then spread spectrum acquisition, despreading, tracking, and related telemetry processing modules are loaded; if the target mode is two-way data transmission, then high-speed modulation, high-speed demodulation, and data frame processing modules are loaded. After loading is complete, a loading integrity check is performed, such as checking the module version, module checksum, loading status register, and module interface status. Subsequently, a timing synchronization check is performed, such as confirming whether the relationship between the sampling clock, processing clock, synchronization clock, and the time base required for ranging and velocity measurement meets the requirements of the target mode. Finally, a link status check is performed, such as confirming that the intermediate frequency input / output channels are available, the data interfaces between modules are connected, parameter initialization is complete, and status feedback is normal. When the integrity check, timing synchronization check, and link status check all pass, the reconfigurable scheduling intermediate layer returns a "target mode ready" status to the multi-mode baseband management software. The management software displays the task execution ready status of the device entering the target measurement and control mode on the monitoring interface. If any check fails, the system can remain in standby or fall back to a safe state and indicate the reason for the failure, such as incomplete loading of functional modules, failure to establish clock synchronization, or abnormal downlink receive link status.

[0029] In some examples, it also includes: During the execution of the measurement and control task, based on the preset test cycle or the test instructions issued by the user, the automated test module is invoked to perform device self-test, link test, signal processing result comparison and test report generation; When a link anomaly, signal loss, hardware status anomaly, or data processing anomaly is detected, the fault diagnosis and management module is invoked to locate the fault, classify the fault, and generate alarms for the abnormal data, and output the corresponding handling prompts. In the event of a link anomaly or signal loss corresponding to a failure to acquire downlink telemetry and control signals, the acquisition processing module is invoked to perform signal reacquisition, synchronization header identification, carrier synchronization acquisition, and code ring synchronization acquisition in order to restore the telemetry and control link status.

[0030] For example, multi-mode baseband management software can set preset test cycles for automated testing modules, such as performing link quality checks at regular intervals, or allow users to issue test commands through a monitoring interface. Automated testing can include device self-testing, link testing, signal processing result comparison, and test report generation. Device self-testing can read temperature, voltage, clock lockout, interface communication, and resource usage status. Link testing can check the status of the uplink modulation link, intermediate frequency receiving link, remote control loop self-loop link, and telemetry processing link. Signal processing result comparison can compare the remote control loop feedback data with the original remote control command, compare the telemetry frame de-framing results with the expected frame structure, and compare the ranging and velocity measurement results with reasonable variation ranges. Test reports can record test time, test items, criteria, results, and anomalies. When the system detects link anomalies, signal loss, hardware status anomalies, or data processing anomalies, the fault diagnosis management module reads the abnormal data and its context information. For example, link anomalies can include excessively low received signal level, continuously increasing bit error rate, and frequent frame synchronization loss; signal loss of lock can include carrier lock loss, code ring lock loss, and bit synchronization failure; hardware status anomalies can include excessively high temperature, abnormal voltage, clock unlocking, and interface communication timeout; data processing anomalies can include abnormal decoding failure rate, frame format errors, and sudden changes in ranging results. The fault diagnosis and management module can classify faults according to the source of the anomaly, duration, scope of impact on the link, and criticality of the task, and generate alarm information and handling prompts. For example, for a short-term increase in bit error rate, it can prompt attention to link quality; for continuous carrier lock loss, it can prompt the execution of signal reacquisition; for clock unit anomalies, it can prompt the suspension of the task and checking the clock source. When a link anomaly or signal lock loss is determined to be a failure to acquire downlink telemetry and control signals, the acquisition processing module initiates the reacquisition process. First, it reads the acquisition parameters according to the current target telemetry and control mode, such as carrier search range, code phase search range, synchronization header format, and acquisition threshold. Then, it re-searches the downlink baseband data, identifies the synchronization header, re-establishes carrier synchronization, and performs code ring synchronization acquisition for modes requiring code synchronization. If reacquisition is successful, the system updates the link status and resumes downlink measurement and control signal processing; if reacquisition fails, the fault diagnosis and management module continues to maintain the alarm and outputs further handling suggestions, such as checking the RF front end, adjusting the receive gain, or reviewing the task parameters.

[0031] In some examples, it also includes: Receive remote maintenance instructions and determine the operation permissions corresponding to the remote maintenance instructions based on the user authentication results; When the operation permissions meet the preset upgrade permissions, the main control program, reconfigurable scheduling firmware, or newly added measurement and control mode function modules can be remotely loaded and upgraded online. After the upgrade is completed, the upgraded main control program, reconfigurable scheduling firmware or newly added measurement and control mode function modules are subject to version verification, integrity verification and running status verification. User identity information, operation content, upgrade objects, verification results, and abnormal information during remote maintenance are written into the operation log and stored through the file management module to achieve access control and traceability management of the measurement and control baseband equipment management process.

[0032] For example, after receiving a remote maintenance command, the multi-mode baseband management software first calls the user management module for identity authentication. Identity authentication may include account password verification, certificate verification, token verification, or station control system authorization verification. After successful authentication, the user management module determines the operation permissions corresponding to the remote maintenance command based on the user role and permission table. For example, if the remote maintenance command is to upgrade a new measurement and control mode function module, the system checks whether the user has the permission to upgrade the mode function module; if the remote maintenance command is to upgrade the reconfigurable scheduling firmware, the system checks whether the user has the permission to upgrade the firmware. When the operation permissions meet the preset upgrade permissions, the system enters the remote online loading and upgrade process. For main control program upgrades, the system can first receive the upgrade package and save it to a designated storage area, then perform version identification and integrity verification, and then replace the original main control program at a safe time. For reconfigurable scheduling firmware upgrades, the system can write the firmware file to the firmware storage area and load the new firmware when the device is in a waiting-for-schedule or maintenance state. For upgrades of new measurement and control mode function modules, the system can write the new module to the measurement and control mode function module library and register the module identifier, version number, applicable mode, resource requirements, and interface specifications. After the upgrade is complete, the system performs version verification, integrity verification, and operational status verification. Version verification reads the version number of the upgrade object and compares it with the target version in the remote maintenance command. Integrity verification confirms that the file is not corrupted by comparing the checksum, signature, or file length. Operational status verification varies depending on the upgrade object: after the main control program is upgraded, it checks whether the management software can start normally and recognize the device; after the reconfigurable scheduling firmware is upgraded, it checks whether it can receive mode configuration files and reconfigurable scheduling commands; after the newly added measurement and control mode function module is upgraded, it checks whether the module can be recognized by the function module library, whether it can pass the loading test, and whether it can match the interface of the general underlying driver layer and the reconfigurable scheduling middleware layer. Regardless of whether the upgrade is successful or not, the system writes the remote maintenance process to the operation log. The log content includes user identity information, login source, operation time, maintenance command type, upgrade object, version before upgrade, version after upgrade, verification result, exception information, and processing result. The file management module categorizes and stores the logs and supports subsequent retrieval and export.

[0033] In some cases, considering that after the telemetry and control baseband equipment completes the switch from one telemetry and control mode to another, the conventional practice is usually only to check whether the new mode's functional module has been successfully loaded, whether the link is locked, and whether the parameters have been written. However, in actual equipment, state variables such as clock division relationships, initial states of loop filters, cumulative phase values ​​of numerically controlled oscillators, and offsets of ranging time markers from the old mode may not completely disappear as the functional modules are unloaded. These residual states do not directly cause link loss of lock, nor do they manifest as obvious equipment failures, and are therefore very insidious. After a new task is started, telemetry may deframe normally, and the carrier may lock normally, but velocity and ranging results may show a fixed offset or slow drift. For example, if the previous task was in high-speed data transmission mode and the next task switches to standard telemetry and ranging mode, the residual phase accumulation state of the numerically controlled oscillator formed under the wider loop bandwidth of the old mode may cause a slight deviation in the ranging time markers in the new mode. For ordinary monitoring interfaces, this deviation is easily misjudged as a change in the motion state of the space target, rather than a system error caused by residual equipment reconfiguration. Based on this, in some examples, after the new signal processing function module is loaded and before confirming that the telemetry and control baseband device has entered the task ready state corresponding to the target telemetry and control mode, the method further includes: Extract a residual state summary from at least one of the following: link status register, clock configuration record, loop filter status cache, numerically controlled oscillator phase accumulation record, and ranging time stamp cache of the old signal processing function module corresponding to the current measurement and control mode. Based on the clock constraints, loop initial conditions, and ranging and velocity measurement accuracy requirements corresponding to the target measurement and control mode, the impact score of the residual state summary on the residual state of the target measurement and control mode is determined. If the residual state impact score exceeds the preset impact threshold, at least one of the execution states of the clock divider chain, loop filter, numerically controlled oscillator and ranging time marker unit corresponding to the target measurement and control mode is blanked. If the residual state impact score does not exceed the preset impact threshold, or if the state blanking process is completed, the measurement and control baseband device is confirmed to enter the task running ready state corresponding to the target measurement and control mode.

[0034] For example, after the reconfigurable scheduling intermediate layer completes the loading of the new signal processing function module, it does not immediately return the task-ready state to the multi-mode baseband management software, but instead enters the residual state detection process. The system first extracts a residual state summary from the old signal processing function module corresponding to the current measurement and control mode or its operation record. The residual state summary may not save complete operation data, but rather extract key summary information that can characterize the impact of the historical state of the old mode. For example, the link state register may include the carrier lock state, code ring lock state, frame synchronization state, abnormal state flag, and resource occupancy state under the old mode; the clock configuration record may include the sampling clock frequency used in the old mode, the division coefficient, the synchronization clock source, the clock switching record, and the phase-locked state; the loop filter state cache may include the loop filter's integral term, historical error term, bandwidth configuration, and convergence state; the numerically controlled oscillator phase accumulation record may include the phase accumulation value, frequency control word, phase reset flag, and accumulation time; the ranging time stamp cache may include the ranging start time stamp, delay compensation value, the ranging offset record of the previous task, and the time stamp validity state. Subsequently, the system scores the residual state summary based on the requirements of the target measurement and control mode. This scoring does not simply determine the existence of residual values, but rather considers the sensitivity of the new mode to residual states. For example, if the target telemetry and control mode does not enable ranging and velocity measurement processing, the residual impact weight of the ranging time stamp cache can be lower; if the target telemetry and control mode is a high-precision ranging mode, the weights of the ranging time stamp cache and clock configuration record should be increased; if the target telemetry and control mode is sensitive to carrier phase continuity, the weights of the numerically controlled oscillator phase accumulation record and loop filter state cache should be increased. A normalized residual quantity is set for each type of residual state, and weights are set according to the target telemetry and control mode to calculate the residual state impact score. For example, the system can convert the difference between the old mode clock division coefficient and the target mode clock division coefficient, the degree to which the loop filter integral term deviates from the target initial value, whether the numerically controlled oscillator phase accumulation value is not zero, and whether the ranging time stamp cache contains old task compensation, etc., into scoring items respectively. If the comprehensive score exceeds the preset impact threshold, it indicates that the residual state of the old mode may affect the operation of the new mode, and state blanking processing needs to be performed. State blanking processing can be performed according to the source of the residual state. For the clock divider chain, the clock division coefficients corresponding to the target mode can be reconfigured, and the clock lock-in can be stabilized. For the loop filter, the integral term, historical error term, and convergence state can be cleared, or the initial filter state of the target mode can be loaded. For the numerically controlled oscillator, the phase accumulation value can be cleared, and the frequency control word and initial phase value corresponding to the target mode can be rewritten. For the ranging time stamp unit, the old task time stamp cache and delay compensation cache can be cleared, and the time base of the target task can be regenerated. After the state blanking is completed, the system reads the relevant states again, confirms that the impact score has dropped below the threshold, and then returns the task running ready state to the management software.

[0035] In some cases, considering that in unattended telemetry and control stations, the station control system may continuously issue multiple telemetry and control task instructions for different targets. Each task instruction is legal on its own, for example, the target mode is legal, the code rate is legal, the sampling rate is legal, and the resource usage is not exceeded. However, when multiple tasks are consecutively scheduled, it is possible that the task completion processing of the previous task has not been completed, while the parameter preloading of the next task has already begun, resulting in cross-contamination of task time windows, data directories, state contexts, or resource release records. This is because it is not a single task instruction error, but a problem of unclear boundaries between the contexts of preceding and following tasks during multi-task scheduling. For example, the telemetry file of the previous task is still being written, while the next task has already created a directory with the same or similar name; the link anomaly alarm of the previous task has not been archived, while the monitoring interface of the next task inherits the alarm status; the intermediate frequency channel of the previous task has been released, but the velocity and ranging data are still being written asynchronously, while the next task directly reads the measurement status left over from the old task. Based on this, in some examples, when receiving multiple telemetry and control task instructions consecutively, the following also applies: For each measurement and control task, a corresponding task context isolation identifier is generated. The task context isolation identifier is bound to the target measurement and control mode, task cycle information, resource mapping table, data storage directory, alarm status set and measurement status cache of the corresponding measurement and control task. Before the next measurement and control task enters the mode configuration file generation stage, check whether the task context isolation flag corresponding to the previous measurement and control task has completed resource release confirmation, data writing confirmation, alarm archiving confirmation, and measurement cache clearing confirmation. If any of the following is not completed: resource release confirmation, data write confirmation, alarm archiving confirmation, and measurement cache clearing confirmation, the subsequent measurement and control task will be placed in a pre-scheduled waiting state, and the subsequent measurement and control task will be prohibited from reusing the resource mapping table, data storage directory, alarm status set, and measurement status cache of the previous measurement and control task. Once the resource release confirmation, data write confirmation, alarm archiving confirmation, and measurement cache clearing confirmation are all completed, a new task context isolation identifier is generated for the next measurement and control task, and the execution mode reconstruction and link startup are performed based on the newly generated task context isolation identifier.

[0036] For example, when the multi-mode baseband management software receives a telemetry and control (TT&C) task instruction, it can generate a task context isolation identifier based on the task number, target identifier, task start time, task end time, and target TT&C mode. This identifier serves as a data and status index for the entire task execution process. The system binds this isolation identifier to the target TT&C mode, task cycle information, resource mapping table, data storage directory, alarm status set, and measurement status cache. Specifically, the target TT&C mode identifies the corresponding standard TT&C, spread spectrum TT&C, two-way data transmission, rocket telemetry, or integrated TT&C mode; the task cycle information defines the task's preparation time, execution time, and end time; the resource mapping table records the logical resources, computing resources, intermediate frequency transceiver channel resources, and synchronization clock resources occupied by the task; the data storage directory stores the remote control data, telemetry data, velocity and distance measurement data, operation logs, and task reports generated by the task; the alarm status set records link anomalies, equipment anomalies, parameter anomalies, and processing anomalies generated during the task; and the measurement status cache stores intermediate distance and velocity measurement states, measurement validity states, and historical measurement points during the task. When the system receives multiple measurement and control task commands consecutively, the next task cannot immediately enter the mode configuration file generation stage. Instead, it first checks whether the context isolation flag of the previous task has completed four types of confirmations. Resource release confirmation confirms that the logical resources, computing resources, intermediate frequency channels, and clock resources occupied by the previous task have been released or transferred to a reallocatable state. Data write confirmation confirms that the data generated by the previous task has been written to the corresponding directory, and there are no files still being written asynchronously. Alarm archiving confirmation confirms that the alarm status of the previous task has been written to the log or task report and is no longer displayed as a current real-time alarm. Measurement cache clearing confirmation confirms that the intermediate states of ranging and velocity measurement and the measurement cache of the previous task have been cleared or archived and will not be read by the next task. If any confirmation is not completed, the system places the next task in a pre-scheduled waiting state. The pre-scheduled waiting state means that the system has received and registered the next task, but has not yet generated the mode configuration file for that task, nor allows the task to reuse the resource mapping table, data storage directory, alarm status set, and measurement status cache of the previous task. Once all four types of confirmations for the current task are completed, the system regenerates a new task context isolation identifier for the next task, and performs refactoring and link startup based on the new isolation identifier.

[0037] In some cases, considering that remote control loop self-loop links are typically used to verify the correctness of remote control commands before and after encoding, framing, and modulation within the baseband, the conventional understanding is that successful loop verification indicates the reliability of the remote control link. However, in reconfigurable multi-mode devices, the remote control loop may only cover the internal baseband return path, not the intermediate frequency output path, channel selection state, or output gain state before actual transmission. This can lead to a situation where the loop verification succeeds, but the actual output channel still retains the old mode configuration. For example, the previous task used the uplink output channel of the integrated telemetry and control mode, and the subsequent task switches to the standard telemetry and control mode. The remote control loop comparison shows that the command content is correct, but the modulation bandwidth, output power, or channel selection of the intermediate frequency output channel is still a residual state of the old mode, causing the actual transmitted signal to not meet the requirements of the new task. Since the loop comparison only verifies the data content and does not verify whether the actual output link has switched to the target mode, based on this, in some examples, after the remote control command passes the loop comparison verification based on the remote control loop return data, the following is also included: Obtain the remote control loop comparison result corresponding to the remote control command, the uplink intermediate frequency output channel configuration, the modulation parameters, output power parameters, channel selection parameters, and digital-to-analog converter sampling parameters corresponding to the target measurement and control mode; A pre-launch link fingerprint is generated based on the target telemetry and control mode. The pre-launch link fingerprint includes at least one of the following: output spectrum characteristics, symbol rate characteristics, modulation phase characteristics, output power characteristics, and channel bonding characteristics. The actual output link fingerprint is obtained by performing short-time sampling or internal detection on the actual uplink intermediate frequency output path. If the actual output link fingerprint is inconsistent with the pre-launch link fingerprint, the remote control command is prohibited from entering the formal launch state, and uplink reconfiguration is triggered.

[0038] For example, after the remote control processing module completes the loop comparison verification based on the remote control loop feedback data and obtains a passing result, the system does not immediately allow the remote control command to enter the formal launch state, but instead enters the pre-launch link consistency verification process. The system first obtains the loop comparison result corresponding to the remote control command to confirm the correctness of the command content; then it reads the uplink intermediate frequency output channel configuration, the modulation parameters, output power parameters, channel selection parameters, and digital-to-analog converter sampling parameters corresponding to the target telemetry and control mode. Subsequently, the system generates a pre-launch link fingerprint based on the target telemetry and control mode. This fingerprint can be understood as a set of verifiable features that the uplink output link should present under the target mode. Output spectrum features may include center frequency, bandwidth, sidelobe distribution, or spectral energy distribution; symbol rate features may reflect the symbol change rhythm of the current remote control signal; modulation phase features may reflect the phase state rules under modulation methods such as phase modulation, two-phase phase shift keying, and four-phase phase shift keying; output power features may reflect whether the pre-launch intermediate frequency output power meets the mission configuration; and channel binding features may reflect whether the current remote control command is bound to the uplink intermediate frequency output path required by the target mission. To obtain the actual output link fingerprint, the system can perform short-time sampling on the actual uplink intermediate frequency (IF) output path or acquire output signal characteristics through internal detection. Short-time sampling allows for internal acquisition of the IF output signal without entering the formal RF transmission state, analyzing its spectrum, symbol rate, and modulation phase. Internal detection can be used to acquire characteristics such as output power, channel presence / absence, and correct channel binding. The system compares the actual output link fingerprint with the target pre-transmission link fingerprint. If the comparison matches, it indicates that the remote control command is not only correct in content but also that the uplink output link meets the current target mode requirements, allowing entry into the formal transmission state. If the comparison does not match, formal transmission is prohibited, and uplink reconfiguration is triggered, such as rewriting modulation parameters, rebinding output channels, resetting the digital-to-analog converter sampling rate, or reconfiguring output power.

[0039] In some cases, considering that the monitoring interface centrally displays the operating status, link status, and signal processing results during the execution of telemetry and control tasks, conventional solutions assume that the status displayed on the monitoring interface is consistent with the underlying actual status. However, in high-data-volume tasks, telemetry data, link status, measurement results, and alarm information are reported simultaneously, and the monitoring interface or management software message queue may experience refresh delays. In this case, the "unlocked" status displayed on the monitoring interface may be from hundreds of milliseconds ago, while the underlying link has actually regained its lock. If operators or automated diagnostic modules trigger recapture based on the delayed status, it may interfere with normal links. Therefore, in some examples, before calling the fault diagnosis management module to locate faults in abnormal data, the following steps are also included: During the process of the operation status data, the link status data, or the signal processing result being reported to the monitoring interface by the corresponding functional module, the underlying acquisition timestamp, the status generation timestamp, and the interface reception timestamp are written respectively. Based on the underlying acquisition timestamp, the status generation timestamp, and the interface reception timestamp, the status freshness of the corresponding status data is determined. When the freshness of the status is lower than a preset freshness threshold, a delay mark is added to the corresponding status data through the monitoring interface, and the fault diagnosis management module is prohibited from triggering signal recapture based solely on the status data with the added delay mark. If state data that meets the preset freshness threshold and indicates link abnormality or signal loss is continuously acquired, the existence of link abnormality or signal loss is confirmed, and the capture processing module is invoked to perform signal recapture, synchronization header identification, carrier synchronization capture, and code ring synchronization capture.

[0040] For example, each functional module, when collecting operational status data, link status data, or signal processing results, first writes a bottom-level acquisition timestamp. The bottom-level acquisition timestamp represents the actual bottom-level acquisition time corresponding to that status, such as the time when carrier lock status is read, frame synchronization status is acquired, or the end time of the bit error rate statistics window. Subsequently, when a functional module generates a status data packet or status message, it writes a status generation timestamp. The status generation timestamp represents the time when the status is encapsulated into reportable data. Finally, when the monitoring interface or the interface layer of the management software receives the status data, it writes an interface reception timestamp. The system calculates the status freshness based on these three timestamps. The status freshness can be determined based on the difference between the bottom-level acquisition time and the interface reception time, or it can be determined by combining the difference between the status generation time and the interface reception time to judge the delay of the status within the module and during message transmission. For example, if the time between the underlying data acquisition of a certain state and the time received by the interface is too long, it indicates that the state has expired; if the difference between the state generation time and the interface reception time is large, it indicates congestion in the message queue or interface refresh; if the difference between the underlying data acquisition time and the state generation time is large, it indicates a delay in the internal processing of the functional module. When the state freshness is lower than a preset freshness threshold, the monitoring interface adds a delay mark to the state. For example, it displays "State Delay," "Data Expired," or similar labels on the monitoring interface. Meanwhile, the fault diagnosis management module must not trigger signal recapture solely based on this delayed state. The phrase "solely based" is crucial; it means that if only one expired state indicates a link loss, and there is no new underlying state to support it, recapture cannot be performed immediately. The system can continue to wait for new state data or request the corresponding functional module to immediately report a real-time state. Only when the system continuously acquires state data that meets the freshness threshold and all indicate link anomalies or signal loss will it confirm the existence of a link anomaly or signal loss. For example, the system can require that if two or three consecutive fresh states display carrier unlock, code ring unlock, or frame synchronization failure, then the capture processing module can be invoked to perform signal re-acquisition, synchronization header identification, carrier synchronization acquisition, and code ring synchronization acquisition. This can filter out expired states and transient state fluctuations.

[0041] In some examples, the aforementioned telemetry and control baseband equipment includes reconfigurable signal processing firmware, such as... Figure 2 As shown, the reconfigurable signal processing firmware can be represented by a signal processing board or a digital signal processing board; The reconfigurable signal processing firmware includes: a general-purpose low-level driver layer, a reconfigurable scheduling intermediate layer, and a mode-specific function module library; The mode-specific function module library includes signal processing function modules corresponding to at least two measurement and control modes. The reconfigurable scheduling intermediate layer is used to load the signal processing function module corresponding to the target measurement and control mode from the mode-specific function module library according to the mode configuration file and the reconfiguration scheduling command, and establish a resource mapping relationship between the signal processing function module and the hardware resource pool, so that the core signal processing board is reconfigured into a measurement and control baseband processing link corresponding to the target measurement and control mode.

[0042] Understandably, the above solution achieves resource reuse across all measurement and control modes through hardware resource pooling design. No hardware circuit modifications are required; seamless switching between different measurement and control modes can be achieved solely through online firmware loading. A single device can cover standard TT&C measurement and control, non-coherent spread spectrum measurement and control, bidirectional data transmission, rocket telemetry, and integrated high-altitude and low-altitude full-scenario measurement and control systems. The device hardware adopts a generalized and modular design, reserving ample computing power, storage, and interface resources, and possessing the expansion capability to add new measurement and control modes. In terms of hardware interfaces, the baseband can output one uplink modulation signal, while simultaneously supporting the reception and processing of one downlink telemetry input signal and one intermediate frequency remote control loop self-loop input signal. The hardware can adopt a generalized and modular industrial-grade architecture, with the core consisting of an industrial-grade industrial control computer platform and a core signal processing board. These two components achieve high-speed command interaction, data transmission, and unified power supply through a standard high-speed parallel bus. All hardware resources adopt a pooled design, supporting flexible reuse across all measurement and control modes without requiring hardware circuit modifications for different modes. The industrial-grade industrial PC platform can utilize CPCI industrial PC motherboards, providing a standardized industrial-grade operating platform, system computing power, and upper-level management support. It adopts a standard rack-mount industrial chassis, equipped with industrial-grade redundant power supplies and a forced air cooling system to ensure long-term, continuous, and stable operation of the equipment. The industrial PC motherboard can use an Intel Core i7 multi-core processor, onboard 8GB of memory, a 1TB high-speed solid-state drive, pre-installed with a Windows operating system, and integrates two gigabit Ethernet interfaces, supporting TCP / IP and UDP protocols. It provides the operating environment for the unified management software across all modes, and simultaneously undertakes remote communication, data storage, task scheduling, and system management functions between the equipment and the station control management subsystem. The signal processing board is the core hardware carrier for realizing multi-mode measurement and control signal processing. It interconnects with an industrial-grade control computer platform via a standard high-speed parallel bus. Employing a heterogeneous processing architecture combining FPGA and DSP, it integrates multi-channel configurable intermediate frequency transceiver units, a global synchronization clock unit, and interface adapter units, building a universal hardware resource pool. All resources support flexible reuse across all measurement and control modes. The signal processing firmware runs within the FPGA and DSP chips of the core signal processing board, serving as the core carrier for multi-mode reconfigurability. Through flexible scheduling of hardware resources and online loading of IP cores, seamless switching and full-link reconfiguration of different measurement and control modes can be achieved without modifying the hardware circuitry. The universal underlying driver layer is a basic firmware module applicable to all measurement and control modes, including hardware drivers for ADC / DAC, clock chips, interface chips, and storage units. It abstracts and unifies the scheduling of hardware resources, providing standardized hardware access interfaces for upper-layer applications. This eliminates the need to modify the underlying drivers for different measurement and control modes, ensuring stable operation of the hardware platform during mode switching and enabling flexible reuse of hardware resources across all modes.The reconfigurable scheduling middleware layer is the core hub for online mode loading and seamless switching. Running within the FPGA, it receives mode switching commands and parameter configuration files from the host computer management software via a standard high-speed parallel bus. It completes the online loading of the dedicated IP core for the corresponding measurement and control mode, hardware resource allocation, link mapping, timing synchronization, and parameter initialization. Without interrupting the current measurement and control task or restarting the device, it can complete the entire process of unloading the old mode link and reconstructing the new mode link, achieving seamless switching between different modes without interruption. On the other hand, it is responsible for intelligent scheduling and status monitoring of hardware resources, ensuring reasonable resource allocation during mode operation, avoiding resource conflicts during multi-mode switching, and completing status verification and exception handling during the reconstruction process to ensure the reliability of mode switching. Mode-Specific IP Core Layer: This layer contains a built-in reconfigurable IP core library, including dedicated full-link signal processing IP cores for five major categories of telemetry and control modes: standard TT&C telemetry and control, non-coherent spread spectrum telemetry and control, two-way data transmission, rocket telemetry, and integrated high-altitude and low-altitude telemetry and control. Each IP core has a built-in complete signal processing algorithm for the corresponding telemetry and control mode, which can be independently loaded and run according to scheduling instructions. After loading, it can complete the full-function telemetry and control signal processing for the corresponding mode. All IP cores adopt a standardized interface design, which can be seamlessly adapted to the general underlying driver layer and scheduling middleware layer. At the same time, IP core expansion interfaces are reserved. Relying on the resource margin reserved by the hardware platform, other telemetry and control modes can be quickly added through firmware upgrades without modifying the hardware platform.

[0043] Please see Figure 3 The multi-mode baseband management software serves as the core control and data processing platform for reconfigurable multi-mode telemetry and control baseband equipment. Deployed on the device's digital signal processing board, it enables parameter configuration, status monitoring, command control, baseband signal processing, telemetry and control data parsing, and system operation and maintenance management across the entire telemetry and control baseband chain. It covers the entire business process of uplink remote control, downlink telemetry, speed and distance measurement, and system testing and maintenance. Simultaneously, it supports reconfigurable configuration of functional modules, adapting to the needs of telemetry and control tasks across multiple systems and scenarios. The software adopts a modular, layered architecture design, with each module interacting based on standardized data interfaces, achieving functional decoupling and independent reconfiguration, ensuring the software's scalability and multi-scenario adaptability. like Figure 4 As shown, this application embodiment also provides an electronic device 300, including a memory 310, a processor 320, and a computer program 311 stored in the memory 310 and executable on the processor. When the processor 320 executes the computer program 311, it implements the steps of any of the above-mentioned methods for managing the measurement and control baseband device.

[0044] Since the electronic device described in this embodiment is the device used to implement a measurement and control baseband device in the embodiments of this application, those skilled in the art can understand the specific implementation method and various variations of the electronic device in this embodiment based on the method described in the embodiments of this application. Therefore, how the electronic device implements the method in the embodiments of this application will not be described in detail here. Any device used by those skilled in the art to implement the method in the embodiments of this application falls within the scope of protection of this application.

[0045] In practical implementation, when the computer program 311 is executed by the processor, it can achieve the following: Figure 1 Any of the corresponding implementation methods in the embodiments.

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

Claims

1. A method for managing measurement and control baseband equipment, characterized in that, include: Receive measurement and control task instructions from local users or remotely issued by the station control system, and parse the measurement and control task instructions to obtain the target measurement and control mode, task operation parameters and task cycle information; Based on the target measurement and control mode and the task operation parameters, generate a mode configuration file and a reconstructed scheduling command; The mode configuration file and the reconfiguration scheduling command are sent to the reconfigurable scheduling intermediate layer so that the reconfigurable scheduling intermediate layer loads the signal processing function module corresponding to the target measurement and control mode, so as to establish the mapping relationship between the signal processing function module and the logical resources, computing resources, intermediate frequency transceiver channel resources and synchronous clock resources of the measurement and control baseband equipment. Based on the mapping relationship, parameters are configured for at least one of the uplink, intermediate frequency receiving link, remote control loop self-loop link, telemetry processing link, and speed and distance measurement processing link, and the measurement and control task corresponding to the target measurement and control mode is started.

2. The method as described in claim 1, characterized in that, Also includes: During the execution of the measurement and control mission, the operating status data, link status data, signal processing results, and measurement and control service data of the measurement and control baseband equipment are collected. The operating status data, link status data, signal processing results, and measurement and control service data are centrally displayed and managed through a monitoring interface. After the measurement and control task is completed, the remote control data, telemetry data, speed and distance measurement data, operation logs and task reports generated by the measurement and control task are classified and stored, so that the measurement and control baseband equipment enters the waiting state to receive the next measurement and control task instruction.

3. The method as described in claim 1, characterized in that, Before sending the pattern configuration file and the reconfiguration scheduling command to the reconfigurable scheduling intermediate layer, the method further includes: For the target measurement and control mode, at least one of the modulation scheme, code rate, loop bandwidth, ranging mode, receiving gain, sampling rate, filter bandwidth and acquisition and tracking parameters is checked for range, mode matching and resource usage. If the task operation parameters do not meet the parameter constraints of the target measurement and control mode, or if the resource requirements corresponding to the task operation parameters exceed the available resource margin of the measurement and control baseband equipment, a parameter anomaly prompt will be generated and the reconfiguration scheduling command will be prevented from being issued. If the task operation parameters meet the parameter constraints of the target measurement and control mode, and the resource requirements corresponding to the task operation parameters do not exceed the available resource margin of the measurement and control baseband equipment, the mode configuration file and the reconfiguration scheduling command are generated.

4. The method as described in claim 1, characterized in that, Also includes: The execution status of the current measurement and control task is confirmed through the reconfigurable scheduling intermediate layer; When the current measurement and control task has been completed, unload the old signal processing function module corresponding to the current measurement and control mode, and release the logic resources, computing resources, intermediate frequency transceiver channel resources and synchronization clock resources occupied by the old signal processing function module; Load a new signal processing function module corresponding to the target measurement and control mode from the preset measurement and control mode function module library, and perform load integrity verification, timing synchronization verification and link status verification on the new signal processing function module; If the load integrity check, the timing synchronization check, and the link status check all pass, the telemetry and control baseband device is confirmed to have entered the task-ready state corresponding to the target telemetry and control mode.

5. The method as described in claim 1, characterized in that, Also includes: During the execution of the measurement and control task, based on the preset test cycle or the test instructions issued by the user, the automated test module is invoked to perform device self-test, link test, signal processing result comparison and test report generation; When a link anomaly, signal loss, hardware status anomaly, or data processing anomaly is detected, the fault diagnosis and management module is invoked to locate the fault, classify the fault, and generate alarms for the abnormal data, and output the corresponding handling prompts. In the event of a link anomaly or signal loss corresponding to a failure to acquire downlink telemetry and control signals, the acquisition processing module is invoked to perform signal reacquisition, synchronization header identification, carrier synchronization acquisition, and code ring synchronization acquisition in order to restore the telemetry and control link status.

6. The method as described in claim 1, characterized in that, Also includes: Receive remote maintenance instructions and determine the operation permissions corresponding to the remote maintenance instructions based on the user authentication results; When the operation permissions meet the preset upgrade permissions, the main control program, reconfigurable scheduling firmware, or newly added measurement and control mode function modules can be remotely loaded and upgraded online. After the upgrade is completed, the upgraded main control program, reconfigurable scheduling firmware or newly added measurement and control mode function modules are subject to version verification, integrity verification and running status verification. User identity information, operation content, upgrade objects, verification results, and abnormal information during remote maintenance are written into the operation log and stored through the file management module to achieve access control and traceability management of the measurement and control baseband equipment management process.

7. The method as described in claim 4, characterized in that, Also includes: Extract a residual state summary from at least one of the following: link status register, clock configuration record, loop filter status cache, numerically controlled oscillator phase accumulation record, and ranging time stamp cache of the old signal processing function module corresponding to the current measurement and control mode. Based on the clock constraints, loop initial conditions, and ranging and velocity measurement accuracy requirements corresponding to the target measurement and control mode, the impact score of the residual state summary on the residual state of the target measurement and control mode is determined. If the residual state impact score exceeds the preset impact threshold, at least one of the execution states of the clock divider chain, loop filter, numerically controlled oscillator and ranging time marker unit corresponding to the target measurement and control mode is blanked. If the residual state impact score does not exceed the preset impact threshold, or if the state blanking process is completed, the measurement and control baseband device is confirmed to enter the task running ready state corresponding to the target measurement and control mode.

8. A measurement and control baseband device, characterized in that, The device, employing the method as described in any one of claims 1 to 7, includes reconfigurable signal processing firmware; The reconfigurable signal processing firmware includes: a general-purpose low-level driver layer, a reconfigurable scheduling intermediate layer, and a mode-specific function module library; The mode-specific function module library includes signal processing function modules corresponding to at least two measurement and control modes. The reconfigurable scheduling intermediate layer is used to load the signal processing function module corresponding to the target measurement and control mode from the mode-specific function module library according to the mode configuration file and the reconfiguration scheduling command, and establish a resource mapping relationship between the signal processing function module and the hardware resource pool, so that the core signal processing board is reconfigured into a measurement and control baseband processing link corresponding to the target measurement and control mode.

9. An electronic device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that the processor executes the computer program stored in the memory to implement the steps of the measurement and control baseband device management method as described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by the processor, it implements the measurement and control baseband equipment management method as described in any one of claims 1-7.

Images