A PUSCH slot-by-slot differentiated closed loop test system and method

Abstract

The application relates to a PUSCH time slot differentiation closed loop test system and method, and belongs to the technical field of continuous test of an uplink physical layer of a satellite borne base station. The system is aimed at a scenario of substantially different PUSCH test vectors of a continuous target absolute time slot configuration, and establishes a time slot test record of binding control parameters, exclusive IQ, expected test results, result association information and time constraints for each PUSCH object. The exclusive IQ of the record is sent only when the record and exclusive resources are valid, the control satisfies the condition of being available on time, and the IQ sending window is in the IQ sending window. According to the result association information, the asynchronous CRC result and the actual TB result are recovered to the original record matched uniquely, and compared with the expected result. A plurality of records are overlapped and promoted in stages under the condition of resource isolation, and the started records are bounded and ended after the test plan is completed. The risk of false pass and false failure caused by cross time slot mismatch can be reduced, and the stability of asynchronous result attribution and comparison can be improved.

Description

Technical Field

[0001] This application relates to the field of continuous testing technology for uplink physical layer of spaceborne base stations, and in particular to a PUSCH time-slot differentiated closed-loop testing system and method. Background Technology

[0002] During the development and testing of spaceborne base stations, continuous functional verification of the uplink physical layer of PUSCH (Physical Uplink Shared Channel) is required. Conventional test systems transmit control parameters and test IQ through the control path and IQ (in-phase / quadrature) data path respectively, and asynchronously receive CRC (Cyclic Redundancy Check) results and TB (Transmission Block) results.

[0003] In continuous multi-slot PUSCH testing, control parameters and IQ data can be transmitted via different paths, and the transmission latency and data presentation of the two paths may differ. If only the program order of publishing control parameters first and then transmitting IQ data is considered, it is difficult to determine whether the control parameters meet the physical layer access conditions when the IQ data arrives. Furthermore, the reuse of cached resources may overlap with data transmission or result verification in preceding time slots, leading to cross-time slot resource overwriting or mismatch. Periodic wrapping of system frame numbers, multiple PUSCH objects within the same time slot, and out-of-order, duplicate, delayed, or actual TB buffer updates of test results all increase the difficulty of result attribution and data verification. Summary of the Invention

[0004] Therefore, it is necessary to provide a PUSCH time-slot-by-time differentiated closed-loop test system and method to address the aforementioned technical problems.

[0005] A PUSCH time-slot-by-time differential closed-loop test system includes a test host, a front-end processing unit, and a physical layer processing unit. The test host and the physical layer processing unit are connected via a control path, and the test host, the front-end processing unit, and the physical layer processing unit are connected via a data path. The time-slot-by-time differential closed-loop test process executed by the system includes: The test host constructs a test plan containing multiple future target absolute time slots, configures a dedicated test vector for the PUSCH object corresponding to each target absolute time slot, and the test vectors corresponding to at least two target absolute time slots in the test plan have substantial differences in at least one of the control parameters, dedicated IQ, or expected TB. Before the start of each target absolute time slot, an independent time slot test record is built for each corresponding PUSCH object. The time slot test record is fixedly bound to the control parameters, exclusive IQ, expected CRC status, expected TB, result association information, IQ sending window and result deadline of the corresponding PUSCH object, and the same set of test content and resources are referenced after the control parameters are published. The control parameters of the corresponding PUSCH object are fully published through the control path. The dedicated IQ bound to this time slot test record is sent through the data path only when the result receiving position of the time slot test record and the corresponding PUSCH object has been established, the dedicated resource of the time slot test record is valid, the control parameters meet the conditions for timely access, and the current time is within the IQ sending window. The receiving physical layer processing device, based on the control parameters of the corresponding PUSCH object and the CRC result formed by the dedicated IQ, as well as the actual TB result formed when the protocol requests the return of data, queries the currently active time slot test record and the completed historical time slot test record according to the result association information in the result message. Only the uniquely matching currently active time slot test record is identified as the original time slot test record. The CRC result and the actual TB result are written into the original time slot test record, and compared with the expected CRC state, expected TB length, and expected TB content saved in advance in the original time slot test record. Under the condition of resource isolation referenced by each time slot test record, multiple time slot test records are made to advance in stages and overlap. After the test plan ends or a stop instruction is received, the creation of new time slot test records is stopped, and the processing of the time slot test records that have started continues until all are completed or a unified end date is reached.

[0006] In one embodiment, the test host is also configured to calculate the control parameter content digest, the dedicated IQ content digest, and the expected TB content digest that affect PUSCH processing, and to identify substantial content differences based on the content digests; changes in filenames, storage addresses, or resource numbers are not considered substantial content differences.

[0007] In one embodiment, before the control parameters are released, the test host is further configured to: establish a time domain by cell, carrier, and subcarrier interval; convert the system frame number and intra-frame slot number into a target absolute slot that is monotonically increasing within the same time domain and is not affected by system frame number wraparound; assign a unique operating generation for each continuous test; and determine the identity of each slot test record based on the operating generation, time domain, target absolute slot, and PUSCH object sequence number.

[0008] In one embodiment, before the control parameters are released, the test host is also configured to reserve an activity record location, an IQ queue location, and an actual TB storage space for each PUSCH object, and to use the activity record location, IQ queue location, and actual TB storage space as dedicated resources for the test record of this time slot, and to make the test record of the time slot continuously reference the same set of dedicated resources after the control parameters are released.

[0009] In one embodiment, the test host is further configured to first write the complete control parameters, the identity of the test record belonging to the time slot, and the control submission number into the inactive control area, and then publish the control submission status after confirming that the writing has been completed and the memory barrier has been cleared; after obtaining the new control submission number, the physical layer processing device checks the control parameter message boundary, the identity of the time slot test record, and the target absolute time slot, and registers the control parameters that have passed the check. When the physical layer processing device supports control acceptance confirmation, the timely availability condition is that the test host has received the control acceptance confirmation corresponding to the control submission number of this time. When the physical layer processing device does not support control acceptance confirmation, the on-time access condition is composed of the control parameters written into the arrival certificate and the predetermined minimum advance amount. The minimum advance amount at least covers the worst-case delay and protection margin of control visibility, physical layer access, IQ transmission and front-end processing.

[0010] In one embodiment, the time slot test record is also fixedly bound to the planned IQ symbol range, which represents the valid symbol range of the corresponding PUSCH object's planned IQ transmission within the target absolute time slot. When the test host transmits a dedicated IQ, it only reads the record identity, dedicated IQ, planned IQ symbol range, and IQ transmission window from the test record of its own time slot, and does not read the global current IQ that can be updated by other target absolute time slots. The actual transmitted IQ symbol range and time corresponding to complete transmission, partial transmission, transmission failure, or missed IQ transmission window are written back to the test record of its own time slot, and the retransmission of expired IQs is prohibited after the latest time of the IQ transmission window has passed.

[0011] In one embodiment, the result association information includes available fields in the result message such as cell, carrier, timeslot, object identifier, handle, terminal identifier, and retransmission process number; If no time slot test record is matched, the result is recorded as an expired result; if multiple time slot test records are matched, the result is recorded as a mismatch and is not written to other time slot test records; if a historical time slot test record that has ended is matched, the result is recorded as a late result and appended to the historical time slot test record, and the late result is not allowed to participate in the current test; the result is only received when it uniquely matches a currently active time slot test record, and the order in which the result arrives and the time slot currently being sent are not involved in the result attribution determination.

[0012] In one embodiment, for the actual TB result belonging to a unique currently active time slot test record, the result writer publishes a result update number after completing the writing of the actual TB result and result description, necessary cache write-back, and memory barrier; the test host checks whether the address, length, and boundaries of the actual TB result are valid, reads the result update number for the first time, copies the complete actual TB result to form a copy, and reads the result update number again, accepting the copy only if the result update numbers read twice match; if the result update numbers read twice do not match, the copy is discarded, a write conflict is recorded, and the actual TB result is reread before the result deadline of the test record belonging to the time slot.

[0013] In one embodiment, the test host is further configured to: Update the current target absolute timeslot according to the timeslot indication, and if the timeslot indication is lost, out of order, or an out-of-range jump occurs, suspend the creation of new timeslot test records and suspend the IQ transmissions that have not yet been executed until the time base is restored; Control parameters for prohibiting the publication of new time slot test records when the result association information of a new time slot test record conflicts with the currently active time slot test record or a historical time slot test record that is in a late isolation period; It allows the release of control parameters for the next time slot test record or the sending of a dedicated IQ for the next time slot test record while the previous time slot test record is waiting for results; and after the test plan ends or a stop instruction is received, the time slot test records that have released control parameters, are sending IQs, or are waiting for results continue to proceed according to their respective IQ sending windows and result deadlines. When the unified closing deadline is completed before all time slot test records are completed, the time slot test records that are still in the middle stage will be converted to timeouts one by one, and the completed time slot test records and their result association information will be retained until the latest isolation period ends.

[0014] A PUSCH time-slot-by-time differential closed-loop test method is implemented based on the above-mentioned PUSCH time-slot-by-time differential closed-loop test system. The method includes: The test host constructs a test plan containing multiple future target absolute time slots, configures a dedicated test vector for the PUSCH object corresponding to each target absolute time slot, and the test vectors corresponding to at least two target absolute time slots in the test plan have substantial differences in at least one of the control parameters, dedicated IQ, or expected TB. Before the start of each target absolute time slot, an independent time slot test record is built for each corresponding PUSCH object. The time slot test record is fixedly bound to the control parameters, exclusive IQ, expected CRC status, expected TB, result association information, IQ sending window and result deadline of the corresponding PUSCH object, and the same set of test content and resources are referenced after the control parameters are published. The control parameters of the corresponding PUSCH object are fully published through the control path. The dedicated IQ bound to this time slot test record is sent through the data path only when the result receiving position of the time slot test record and the corresponding PUSCH object has been established, the dedicated resource of the time slot test record is valid, the control parameters meet the conditions for timely access, and the current time is within the IQ sending window. The receiving physical layer processing device, based on the control parameters of the corresponding PUSCH object and the CRC result formed by the dedicated IQ, as well as the actual TB result formed when the protocol requests the return of data, queries the currently active time slot test record and the completed historical time slot test record according to the result association information in the result message. Only the uniquely matching currently active time slot test record is identified as the original time slot test record. The CRC result and the actual TB result are written into the original time slot test record, and compared with the expected CRC state, expected TB length, and expected TB content saved in advance in the original time slot test record. Under the condition of resource isolation referenced by each time slot test record, multiple time slot test records are made to advance in stages and overlap. After the test plan ends or a stop instruction is received, the creation of new time slot test records is stopped, and the processing of the time slot test records that have started continues until all are completed or a unified end date is reached.

[0015] The aforementioned PUSCH time-slot-by-time differential closed-loop testing system and method have the following advantages compared to existing technologies: 1. Based on the architecture of control and data paths, and based on the target absolute time slots that are monotonically increasing in the time domain, time slot-by-time differentiated closed-loop testing is carried out. The test host establishes independent time slot test records for each PUSCH object, and after the control parameters are released, it keeps referencing the same set of control parameters, dedicated IQ, expected test results, result association information and time constraints, thereby avoiding cross-time slot mismatch caused by the content of the later time slot covering the data of the previous time slot, reducing the risk of false pass and false failure of the test, and supporting multiple differentiated records to be advanced in stages under resource isolation conditions.

[0016] 2. The testing process adopts a timing logic that first publishes control parameters and then sends dedicated IQs under the constraint of test records in the same time slot. This matches the system's dual-path transmission architecture. Through standardized transmission timing and IQ transmission gating constraints, it is ensured that the control parameters and dedicated IQs can accurately correspond to the PUSCH objects in the same target absolute time slot. This avoids the problem of parameter and IQ matching disorder caused by differences in dual-path transmission and improper transmission order, ensuring the correspondence of data received by the physical layer processing device and providing a reliable premise for generating accurate actual test results in the future.

[0017] 3. Based on the result association information, uniquely restore the CRC result and the actual TB result to the original time slot test record, and then compare it with the expected CRC state, expected TB length and expected TB content pre-stored in the original record; reduce the risk of result mismatch through record matching and bounded termination mechanism, and isolate the interference of past test data on the current test. Attached Figure Description

[0018] Figure 1 This is a schematic diagram of the structure of a PUSCH time-slot-by-time differential closed-loop test system in one embodiment; Figure 2 This is a schematic diagram illustrating the unique attribution of asynchronous results to the actual TB verification process in one embodiment; Figure 3 This is a schematic diagram illustrating the staged overlapping execution process of two differentiated time-slot test records in one embodiment. Detailed Implementation

[0019] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0020] In one embodiment, this application provides a PUSCH time-slot-by-time differential closed-loop test system. The system includes a test host, a front-end processing unit, and a physical layer processing unit. The test host and the physical layer processing unit are communicatively connected via a control path, and the test host, the front-end processing unit, and the physical layer processing unit are sequentially communicatively connected via a data path. The time-slot-by-time differential closed-loop test process executed by the system includes: First, a test plan containing multiple future target absolute time slots is constructed by the test host. A dedicated test vector is configured for the PUSCH object corresponding to each target absolute time slot, and the test vectors for at least two target absolute time slots in the test plan must exhibit substantial content differences in at least one of the following: control parameters, dedicated IQ, or expected TB. As a method for identifying substantial content differences, the test host can calculate the content digests of the control parameters, dedicated IQ, and expected TB that affect PUSCH processing; changes in metadata such as filenames, storage addresses, or resource numbers are not considered substantial content differences. The target absolute time slots exhibit a monotonically increasing characteristic within the same time domain.

[0021] Secondly, before the start of each target absolute time slot, an independent time slot test record is established for each corresponding PUSCH object. This time slot test record is fixedly bound to the control parameters, dedicated IQ, expected test results (including expected CRC status and expected TB), result association information, IQ sending window, and result deadline of the corresponding PUSCH object, and continues to reference the same set of test content and resources after the control parameters are published. For ease of understanding, each time slot test record can be regarded as an independent "test data package"; subsequent target absolute time slots use a new data package, and the previous data package is retained until the results are compared.

[0022] The control parameters of the corresponding PUSCH object are fully published through the control path. The dedicated IQ bound to this time slot test record is sent through the data path only when the result receiving position of the time slot test record and the corresponding PUSCH object has been established, the dedicated resource of the time slot test record is valid, the control parameters meet the conditions for timely access, and the current time is within the IQ sending window.

[0023] Then, the receiving physical layer processing device, based on the control parameters of the corresponding PUSCH object and the CRC result formed by the dedicated IQ, as well as the actual TB result formed when the protocol requests the return of data, queries the currently active time slot test record and the completed historical time slot test record according to the result association information in the result message. Only the uniquely matching currently active time slot test record is identified as the original time slot test record. The CRC result and the actual TB result are written into the original time slot test record, and compared with the expected CRC state, expected TB length, and expected TB content saved in advance in the original time slot test record. Under the condition of resource isolation referenced by each time slot test record, multiple time slot test records are made to advance in stages and overlap. After the test plan ends or a stop instruction is received, the creation of new time slot test records is stopped, and the processing of the time slot test records that have started continues until all are completed or a unified end date is reached.

[0024] It should be understood that the system proposed in this application relies on a control path and a data path architecture to implement PUSCH time-slot-by-time differentiated closed-loop testing with a target absolute time slot that monotonically increases in the time domain. Each PUSCH object's independent record continuously references the same set of test content and resources after control is released, which can reduce the risk of false passes and false failures caused by cross-time slot content coverage. By relying on records, resources, control, and time conditions to jointly gate dedicated IQ, the execution timing of the two input paths can be coordinated. Based on the result-related record, a unique match is made with the original time slot test record, and then the expected test result is compared with the original time slot test record. Combined with bounded termination and delayed isolation, the risk of asynchronous result mismatch and historical data interfering with the current test can be reduced.

[0025] Figure 1 An example of the system proposed in this application is shown. Figure 1In this diagram, CPU (TESTMAC main controller), FPGA (PHY), and DSP (PHY) represent the test host, front-end processing unit, and physical layer processing unit, respectively. The test host is a CPU, the physical layer processing unit is a DSP (Digital Signal Processor), and the front-end processing unit is an FPGA (Field-Programmable Gate Array). Control parameters for the PUSCH object are sent via the FAPI (Functional Application Platform Interface) / PCIE (High-Speed ​​Peripheral Component Interconnect Bus) control path between the CPU and DSP. IQ data is sent from the CPU to the FPGA via ECPRI (Enhanced General Purpose Radio Interface) for front-end processing, and then delivered to the DSP via SRIO (Serial RapidIO). The arrival times and visibility methods of the two paths to the DSP differ, but they are both constrained by the same time slot test record.

[0026] In one embodiment, before the control parameters are released, the test host is further configured to: establish a time domain by cell, carrier, and subcarrier intervals; convert the system frame number and intra-frame time slot number into a target absolute time slot that is monotonically increasing within the same time domain and unaffected by system frame number wraparound; assign a unique operating generation for each continuous test; and determine the identity of each time slot test record based on the operating generation, time domain, target absolute time slot, and PUSCH object sequence number. The operating generation is defined as a unique number assigned for a single continuous test by the system, and a completely new operating generation is assigned when the system initiates a new round of testing.

[0027] It should be understood that dividing the time domain according to the cell, carrier, and subcarrier intervals, and constructing a target absolute time slot that is unaffected by system frame number wrap-around and monotonically increasing, can reduce timing confusion caused by frame number cycling; and by relying on the generation of operation to distinguish each round of testing, data from different test batches can be isolated, avoiding mutual interference between new and old test records, and improving the reliability of data matching for cross-time slot and multi-round testing.

[0028] In one embodiment, before the control parameters are released, the test host is also configured to reserve an activity record location, an IQ queue location, and an actual TB storage space for each PUSCH object, and to use the activity record location, IQ queue location, and actual TB storage space as dedicated resources for the test record of this time slot, and to make the test record of the time slot continuously reference the same set of dedicated resources after the control parameters are released.

[0029] It should be understood that by pre-reserving activity record locations, IQ queue locations, and actual TB storage space for each PUSCH object and forming a dedicated resource group, the time-slot test records are continuously bound to the corresponding resources after the control parameters are released. This can reduce the risk of resource contention, address confusion, and data overwriting between different PUSCH objects caused by dynamic allocation and release of resources during the test process, improve the stability of control parameters, IQ data, and TB information storage, and enhance the independence and integrity of cross-time-slot test data storage.

[0030] In one embodiment, the test host is further configured to first write the complete control parameters, the identity of the test record belonging to the timeslot, and the control submission number to the inactive control area. After confirming that the write has arrived and the memory barrier has been completed, it publishes a control submission status. After obtaining the new control submission number, the physical layer processing device checks the control parameter message boundary, the timeslot test record identity, and the target absolute timeslot, and registers the control parameters that have passed the check. When the physical layer processing device supports control acceptance confirmation, the timely availability condition is that the test host has received the control acceptance confirmation corresponding to the current control submission number. When the physical layer processing device does not support control acceptance confirmation, the timely availability condition is composed of the control parameter write arrival proof and a predetermined minimum advance, wherein the minimum advance covers at least the worst-case latency and protection margin for control visibility, physical layer access, IQ transmission, and front-end processing.

[0031] It is important to note that each system run selects only one of the two gating mechanisms—one that the physical layer processing device supports and one that does not—for control acceptance confirmation, and this selection remains unchanged. Both gating logics must adhere to the constraints of the same time-slot test record and jointly verify the record, resources, and timing conditions. They only differ in that they use the same control submission number for control acceptance confirmation, or write the arrival proof and preset minimum lead time into the control parameters. This gating mechanism reduces the risk of control parameter and IQ mismatch caused by dual-path asynchronous operation.

[0032] In one embodiment, the time slot test record is also fixedly bound to the planned IQ symbol range, which represents the valid symbol range of the corresponding PUSCH object's planned IQ transmission within the target absolute time slot. When the test host transmits a dedicated IQ, it only reads the record identity, dedicated IQ, planned IQ symbol range, and IQ transmission window from the test record of its own time slot, and does not read the global current IQ that can be updated by other target absolute time slots. The actual transmitted IQ symbol range and time corresponding to complete transmission, partial transmission, transmission failure, or missed IQ transmission window are written back to the test record of its own time slot, and the retransmission of expired IQs is prohibited after the latest time of the IQ transmission window has passed.

[0033] It should be understood that when sending a dedicated IQ, only the internal information of the test record of the corresponding PUSCH object's time slot is read, discarding the global current IQ that can be overwritten and updated by the absolute time slot of other targets, thus avoiding mutual interference between IQ data of different time slots; at the same time, the actual range and time of IQ symbols sent corresponding to various IQ sending states are written back to the test record of the corresponding time slot, which can completely retain the sending process information, and stipulates that expired IQs are prohibited from being resent after the latest time of the IQ sending window, which can prevent cross-time slot data tampering and out-of-order delivery of expired data, ensuring that the IQ data of each PUSCH object is bound to the time slot test record one by one, improving the traceability and timing compliance of the testing process.

[0034] In one embodiment, such as Figure 2 As shown, when the actual test results are sent back to the test host, the test host also uses the result association information, including available fields such as cell, carrier, time slot, object identifier, handle, terminal identifier and retransmission process number in the result message, to query and match the currently active time slot test records and the completed historical time slot test records.

[0035] If no time slot test record is matched, the result is recorded as an expired result and not written to other time slot test records; if multiple time slot test records are matched, the result is recorded as a mismatch and not written to other time slot test records; if a historical time slot test record that has ended is matched, the result is recorded as a late result and appended to the historical time slot test record, and the late result is not allowed to participate in the current test; the result is only received when it uniquely matches a currently active time slot test record, and the order in which the result arrives and the time slot currently being sent are not involved in the result attribution determination.

[0036] In one embodiment, for the actual TB result belonging to a unique currently active time slot test record, the result writer publishes a result update number after completing the writing of the actual TB result and result description, necessary cache write-back, and memory barrier. The test host checks whether the address, length, and boundaries of the actual TB result are valid. If invalid, it stops reading and registers boundary failure, forming an object-level failure conclusion. If valid, it reads the result update number for the first time, copies the complete actual TB result to form a copy, and reads the result update number again. The copy is accepted only if the result update numbers read twice match. If the result update numbers read twice do not match, the copy is discarded, a write conflict is recorded, and the actual TB result is reread before the result deadline of the test record belonging to the time slot. If the stable copy acquisition times out, an object-level timeout conclusion is formed. Subsequently, only the stable copy is compared with the expected test results in the original record. After CRC status backfilling or obtaining a stable actual TB copy, it is determined whether the expected messages in the original record are complete. If not complete and not timed out, it continues to wait. If not complete and timed out, it lists the missing items and records them as result timeout. The expected test results in the original record are used to complete the comparison, and finally, the object-level closed-loop conclusion is saved.

[0037] It should be noted that the runtime generation, control commit number, and result update number mentioned in this application are numbering for different purposes. The runtime generation is used to identify a continuous test; the control commit number is used to identify a control parameter release transaction, and multiple incrementing control commit numbers can be contained within the same runtime generation; the result update number is released by the result writer after completing an actual TB and result description write, and is used to determine whether the result has been updated during the replication of the actual TB.

[0038] In one embodiment, the test host is further configured to: update the current target absolute timeslot according to the timeslot indication; and suspend the creation of new timeslot test records and the transmission of IQs that have not yet been executed until the time base is restored when the timeslot indication is lost, out of order, or jumps out of range; prohibit the publication of control parameters for new timeslot test records when the result association information of a new timeslot test record conflicts with the currently active timeslot test record or a historical timeslot test record in the late isolation period; allow the publication of control parameters for a subsequent timeslot test record or the transmission of a dedicated IQ for a subsequent timeslot test record while the previous timeslot test record is waiting for the result; and after the test plan ends or a stop instruction is received, allow timeslot test records that have published control parameters, are transmitting IQs, or are waiting for results to continue according to their respective IQ transmission windows and result deadlines; when the unified closing deadline is completed before all timeslot test records are completed, convert timeslot test records that are still in the intermediate stage to timeout one by one, and retain the completed timeslot test records and their result association information until the late isolation period ends.

[0039] It should be understood that, in response to abnormal scenarios such as lost time slot indicators, out-of-order delivery, and out-of-range transitions, suspending the addition of new time slot test records and the transmission of pending IQ signals, and prioritizing the repair of the time base, can prevent invalid tests and erroneous signal transmissions caused by timing errors. Simultaneously, through a result association information deduplication mechanism, the transmission of control parameters for new time slot test records is blocked when duplicates occur, preventing parameter conflicts and instruction overlap caused by duplicate records. This effectively reduces the risk of system disorder caused by timing anomalies and duplicate data, and improves the stability of the time slot test process and the reliability of signal transmission.

[0040] Figure 3 The demonstration showcases the phased, overlapping execution process of two differentiated time-slot test records. Specifically, each differentiated time-slot test record independently progresses through preparation, control submission, dedicated IQ transmission, result waiting, verification, and termination. For example, while time-slot test record A is waiting for or receiving results, time-slot test record B can be established, dedicated resources reserved for record B, and its control parameters published. After the joint gating conditions for record B are met, the dedicated IQ bound to record B is sent. Records A and B obtain their respective resources through their record identities and independently complete result attribution, verification, and conclusion formation. When the upper limit of active records, IQ queue, or actual TB storage space is reached, the system prioritizes protecting time-slot test records that have already published control parameters or sent dedicated IQs; time-slot test records that have not yet published control parameters and cannot catch up with the IQ transmission window terminate due to insufficient resources. Figure 3 In the middle, alt indicates that an operation must be selected to be executed, and par indicates parallel processing in the UML sequence diagram.

[0041] After the test plan is completed or a stop command is received, the system will terminate in the following order: Stop creating new time slot test records. Save the reason for stopping test records that have not yet been published and end the process.

[0042] Time slot test records that have already published control parameters, are sending IQ data, or are awaiting actual test results will continue to progress according to their respective IQ sending windows and result deadlines; a conclusion will be reached immediately upon completion of a time slot test record, without waiting for other time slot test records.

[0043] All time slot test records for all activities are closed normally upon completion; when the unified closure deadline arrives first, time slot test records that are still in the middle stage are converted to timeout records one by one, and the final completed stage and missing actions are saved.

[0044] The end-slot test record and associated results information are retained until the late isolation period ends. The results buffer is released when writing stops or DMA (Direct Memory Access) is completed; if confirmation is temporarily unavailable, isolation continues and the results are not passed to subsequent slot test records.

[0045] Furthermore, control parameters are not published when test vectors are missing, generation relationships are unclear, or result association information conflicts; dedicated IQs are not sent when control parameters do not meet the conditions for timely access; partial transmissions, window timeouts, missing results, and address anomalies are all saved in the original time slot test record; reversed or identical duplicate results do not change the conclusion, and different content for the same identity ends with a result conflict. The next run uses a new running generation. When the CRC result or actual TB result asynchronously returned to the test host by the physical layer processing device does not carry the running generation, the new running generation must wait for the old result association information to end delayed isolation, or select new result association information that is still unique during the active and isolation periods; the result buffer that the old running generation has not yet safely released continues to remain isolated.

[0046] It should be noted that, in addition to the technical content described in the above embodiments, the system proposed in this application also has the following alternative implementations, including: Time-slot test records can be stored in structures, object tables, or circular queues; files or databases can be used to persist test plans and end records. The real-time transmission phase uses active records that meet the target time-slot deadlines. Record identity can be explicitly passed or recovered from a combination of result association information that remains unique during the active period and the late isolation period.

[0047] Platforms with acknowledgment-based access control (IQ) can use acknowledgment-gated access control (IQ). Platforms without acknowledgment interfaces can establish access conditions through inactive control zones, incremental submission control numbers, control parameter arrival credentials, and preset minimum lead times. IQs can be sent by symbol, data fragment, or complete time slot, with each task carrying the original record's identity, validity range, and deadline conditions.

[0048] The actual TB can be replicated to a private buffer on the test host, or it can be kept stable by updating the buffer number, reference count, ownership token, or lease. The expected TB can store the complete content, or it can store a read-only resource that can uniquely recover the complete content; the digest is used for quick identity verification, and the final content determination is based on the complete TB.

[0049] This application adopts a time-slot-wise differentiated closed loop under the single IQ normal processing mode, and it is expected that TB will be retained on the test host side for each object to complete the result comparison; this application focuses on the fixed binding, joint gating, unique result attribution and bounded termination of multiple differentiated test vectors in continuous time slots.

[0050] In one specific embodiment, an implementation method and verification method of the system proposed in this application are provided. In this embodiment, the TESTMAC master controller runs on the test host, the C6678 acts as the physical layer processing device, and the FPGA is responsible for IQ front-end processing. The test host publishes PUSCH control parameters and receives actual test results through FAPI messages carried by PCIE, sends IQ to the FPGA through ECPRI, and the FPGA then delivers the PUSCH intermediate data to the C6678 via SRIO. This embodiment uses a 30 kHz subcarrier spacing, so one frame contains 20 time slots, with 19 time slots being valid within the frame. The test plan arranges one PUSCH object in each of the two future target absolute time slots, and the main differences are shown in Table 1. The complete configuration also stores actual processing parameters such as frequency domain range, time domain symbol range, modulation and coding scheme, number of transmission layers, reference signal, uplink control information, rate matching, and IQ generation conditions. The expected TB length is calculated by the complete configuration and fixed in the test vector; Table 1 only shows the main differences for easy understanding.

[0051] Table 1. Two Differentiated PUSCH Test Vectors

[0052] At the start of the test, TESTMAC generates a unique number for this continuous test, which is the generation to run, and establishes the time domain according to the "cell, carrier, 30 kHz subcarrier spacing configuration". PUSCH object A and PUSCH object B obtain independent target absolute timeslots, PUSCH object sequence numbers, protocol field combinations (protocol association keys) used to retrieve the original record of the returned message, IQ transmission windows, and result positions, respectively. The summaries of the two sets of control, IQ, and expected TB are also saved with their respective records.

[0053] After reserving resources for PUSCH object A, TESTMAC publishes complete control A. When C6678 provides a record-by-record acknowledgment interface, TESTMAC waits for it to complete cache invalidation, boundary and identity checks, and return an acceptance acknowledgment; when using the unacknowledgment interface, the written arrival credential and the preset minimum lead time together indicate that control A meets the on-time availability conditions. After entering the IQ sending window, the sending task retrieves IQ A from the record of PUSCH object A.

[0054] After PUSCH object A enters the physical layer processing or result waiting stage, TESTMAC begins to create and publish PUSCH object B. At this time, the two records are in different stages and each holds its own control, IQ, expected TB, and result position. After PUSCH object B enters the sending window, the sending task retrieves the IQ B from the PUSCH object B record.

[0055] The results of the two objects can arrive in reverse order. For example, the received data result of PUSCH object B can arrive earlier than the CRC result of PUSCH object A. TESTMAC first finds the unique record through the protocol association key and the return window, and then immediately saves the corresponding actual TB. PUSCH object A is compared with the expected result A, and PUSCH object B is compared with the expected result B. When the two expected TBs are manually exchanged, the two records still maintain their original association relationship and each leads to a conclusion of inconsistency.

[0056] After the test plan concludes, TESTMAC stops creating new records and continues to receive results from objects that have already been issued control or sent IQs. If all records are completed ahead of schedule, the system terminates the current run directly; if the deadline is reached, records still in the middle stage are marked as timed out, and their late results are added to the end record of the original run number.

[0057] During the test, the IQ transmission status, CRC result and actual TB result corresponding to PUSCH object A and PUSCH object B are recorded respectively. The return results are restored to the corresponding time slot test record according to the protocol association key and return window. The actual result is then compared with the expected CRC status, expected TB length and expected TB content of the record to verify the fixed binding, asynchronous result attribution and result comparison process of the two sets of differentiated test vectors.

[0058] Abnormal scenarios can further validate the processing rules. For example, delay the CRC of PUSCH object A while PUSCH object B completes first, and observe the progress of each record; allow PUSCH object B to send only some symbols and observe the partial transmission results; allow two active records to use the same protocol association key and observe the identity conflict check before publication; allow the old execution result to arrive after the new execution starts and observe the generational isolation of execution. During the test, record the state transitions, actual transmitted symbol range, control parameter publication status, and result attribution information of the test records in each time slot, and use this information to determine whether the multi-record progression, transmission window, identity uniqueness, and handling of late results conform to the preset rules.

[0059] In one embodiment, a PUSCH time-slot-by-time differential closed-loop test method is implemented based on the above-mentioned PUSCH time-slot-by-time differential closed-loop test system, the method comprising: The test host constructs a test plan containing multiple future target absolute time slots, configures a dedicated test vector for the PUSCH object corresponding to each target absolute time slot, and the test vectors corresponding to at least two target absolute time slots in the test plan have substantial differences in at least one of the control parameters, dedicated IQ, or expected TB. Before the start of each target absolute time slot, an independent time slot test record is built for each corresponding PUSCH object. The time slot test record is fixedly bound to the control parameters, exclusive IQ, expected CRC status, expected TB, result association information, IQ sending window and result deadline of the corresponding PUSCH object, and the same set of test content and resources are referenced after the control parameters are published. The control parameters of the corresponding PUSCH object are fully published through the control path. The dedicated IQ bound to this time slot test record is sent through the data path only when the result receiving position of the time slot test record and the corresponding PUSCH object has been established, the dedicated resource of the time slot test record is valid, the control parameters meet the conditions for timely access, and the current time is within the IQ sending window. The receiving physical layer processing device, based on the control parameters of the corresponding PUSCH object and the CRC result formed by the dedicated IQ, as well as the actual TB result formed when the protocol requests the return of data, queries the currently active time slot test record and the completed historical time slot test record according to the result association information in the result message. Only the uniquely matching currently active time slot test record is identified as the original time slot test record. The CRC result and the actual TB result are written into the original time slot test record, and compared with the expected CRC state, expected TB length, and expected TB content saved in advance in the original time slot test record. Under the condition of resource isolation referenced by each time slot test record, multiple time slot test records are made to advance in stages and overlap. After the test plan ends or a stop instruction is received, the creation of new time slot test records is stopped, and the processing of the time slot test records that have started continues until all are completed or a unified end date is reached.

[0060] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0061] The above embodiments are merely illustrative of several implementation methods of this application, and their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make several modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application.

Claims

1. A PUSCH time-slot-by-time differential closed-loop test system, characterized in that, The system includes a test host, a front-end processing device, and a physical layer processing device. The test host and the physical layer processing device are connected via a control path, and the test host, the front-end processing device, and the physical layer processing device are connected via a data path in sequence. The system's time-slot-by-time differentiated closed-loop test process includes: The test host constructs a test plan containing multiple future target absolute time slots, configures a dedicated test vector for the PUSCH object corresponding to each target absolute time slot, and the test vectors corresponding to at least two target absolute time slots in the test plan have substantial differences in at least one of the control parameters, dedicated IQ, or expected TB. Before the start of each target absolute time slot, an independent time slot test record is constructed for each corresponding PUSCH object. The time slot test record is fixedly bound to the control parameters, dedicated IQ, expected CRC status, expected TB, result association information, IQ sending window and result deadline of the corresponding PUSCH object, and the same set of test content and resources are referenced after the control parameters are published. The control parameters of the corresponding PUSCH object are fully published through the control path. The dedicated IQ bound to this time slot test record is sent through the data path only when the result receiving position of the time slot test record and the corresponding PUSCH object has been established, the dedicated resource of the time slot test record is valid, the control parameters meet the conditions for timely access, and the current time is within the IQ sending window. The system receives the CRC result generated by the physical layer processing device based on the control parameters and dedicated IQ of the corresponding PUSCH object, as well as the actual TB result generated when the protocol requests the return of data. It queries the currently active time slot test record and the completed historical time slot test record based on the result association information in the result message. Only the uniquely matching currently active time slot test record is identified as the original time slot test record. The CRC result and the actual TB result are written into the original time slot test record, and compared with the expected CRC state, expected TB length, and expected TB content previously saved in the original time slot test record. Furthermore, under the condition of resource isolation referenced by each time slot test record, multiple time slot test records are allowed to overlap and advance in stages. Upon the end of the test plan or the receipt of a stop instruction, the creation of new time slot test records is stopped, and the processing of the started time slot test records continues until all are completed or a unified closing deadline is reached.

2. The PUSCH time-slot-by-time differential closed-loop test system according to claim 1, characterized in that, The test host is also configured to calculate the content digest of control parameters affecting PUSCH processing, the dedicated IQ content digest, and the expected TB content digest, and to identify substantive content differences based on the content digests; changes in filenames, storage addresses, or resource numbers are not considered substantive content differences.

3. The PUSCH time-slot-by-time differential closed-loop test system according to claim 1, characterized in that, Before the control parameters are released, the test host is also configured to: establish a time domain by cell, carrier, and subcarrier interval; convert the system frame number and intra-frame time slot number into a target absolute time slot that is monotonically increasing within the same time domain and is not affected by system frame number wraparound; assign a unique operating generation for each continuous test; and determine the identity of each time slot test record based on the operating generation, time domain, target absolute time slot, and PUSCH object sequence number.

4. The PUSCH time-slot-by-time differential closed-loop test system according to claim 1, characterized in that, Before the control parameters are released, the test host is also configured to reserve an activity record location, an IQ queue location, and an actual TB storage space for each PUSCH object, and to use the activity record location, IQ queue location, and actual TB storage space as dedicated resources for this time slot test record, and to ensure that the time slot test record continues to reference the same set of dedicated resources after the control parameters are released.

5. The PUSCH time-slot-by-time differential closed-loop test system according to claim 1, characterized in that, The test host is also configured to first write the complete control parameters, the identity of the test record in the corresponding time slot, and the control submission number into the inactive control area, and then publish the control submission status after confirming that the writing has been completed and the memory barrier has been cleared. After obtaining the new control submission number, the physical layer processing device checks the control parameter message boundary, the identity of the time slot test record, and the target absolute time slot, and registers the control parameters that have passed the check. When the physical layer processing device supports control acceptance confirmation, the on-time availability condition is that the test host has received control acceptance confirmation corresponding to the control submission number of this time; When the physical layer processing device does not support control acceptance confirmation, the on-time availability condition is composed of control parameters written into the arrival certificate and a predetermined minimum advance amount, which at least covers the worst-case latency and protection margin of control visibility, physical layer access, IQ transmission and front-end processing.

6. The PUSCH time-slot-by-time differential closed-loop test system according to claim 1, characterized in that, The time slot test record is also fixedly bound to the planned IQ symbol range, which represents the effective symbol range of the corresponding PUSCH object's planned IQ transmission within the target absolute time slot; when the test host transmits a dedicated IQ, it only reads the record identity, dedicated IQ, planned IQ symbol range, and IQ transmission window from the test record of its own time slot, and does not read the global current IQ that can be updated by other target absolute time slots; Write back the actual range and time of IQ symbols sent (completely sent, partially sent, sent but failed, or missed the IQ sending window) to the test record of the corresponding time slot, and prohibit resending expired IQ symbols after the latest time of the IQ sending window has passed.

7. The PUSCH time-slot-by-time differential closed-loop test system according to claim 1, characterized in that, The associated information of the results includes available fields in the cell, carrier, time slot, object identifier, handle, terminal identifier, and retransmission process number in the result message; If no time slot test record is matched, the result is recorded as an expired result; if multiple time slot test records are matched, the result is recorded as a mismatch and is not written to other time slot test records; if a historical time slot test record that has ended is matched, the result is recorded as a late result and appended to the historical time slot test record, and the late result is not allowed to participate in the current test; the result is only received when there is a unique match with a currently active time slot test record, and the order in which the result arrives and the time slot currently being sent are not involved in the result attribution determination.

8. The PUSCH time-slot-by-time differential closed-loop test system according to claim 1, characterized in that, For the actual TB result belonging to the unique current activity time slot test record, the result writer publishes the result update number after completing the writing of the actual TB result and result description, the necessary cache write-back, and memory barrier; The test host checks whether the address, length, and boundaries of the actual TB result are valid, reads the result update number for the first time, copies the complete actual TB result to form a copy, and reads the result update number again. The copy is accepted only if the result update numbers read twice are consistent. If the update numbers of the results from two reads are inconsistent, discard the copy, record the write conflict, and reread the actual TB result before the deadline of the test record in the corresponding time slot.

9. The PUSCH time-slot-by-time differential closed-loop test system according to claim 1, characterized in that, The test host is also configured to: Update the current target absolute timeslot according to the timeslot indication, and if the timeslot indication is lost, out of order, or an out-of-range jump occurs, suspend the creation of new timeslot test records and suspend the IQ transmissions that have not yet been executed until the time base is restored; When the result association information of a new time slot test record conflicts with the currently active time slot test record or a historical time slot test record that is in a late isolation period, the control parameters of the new time slot test record shall be prohibited from being published. Allows the release of control parameters for the next time slot test record or the sending of a dedicated IQ for the next time slot test record while waiting for the results of the previous time slot test record; And after the test plan ends or a stop instruction is received, the time slot test records that have published control parameters, are sending IQ, or are waiting for results continue to advance according to their respective IQ sending windows and result deadlines. When the unified closing deadline is completed before all time slot test records are completed, the time slot test records that are still in the middle stage are converted to timeout one by one, and the completed time slot test records and their result association information are retained until the latest isolation period ends.

10. A PUSCH time-slot-by-time differential closed-loop test method implemented based on the PUSCH time-slot-by-time differential closed-loop test system according to any one of claims 1-9, characterized in that, The method includes: The test host constructs a test plan containing multiple future target absolute time slots, configures a dedicated test vector for the PUSCH object corresponding to each target absolute time slot, and the test vectors corresponding to at least two target absolute time slots in the test plan have substantial differences in at least one of the control parameters, dedicated IQ, or expected TB. Before the start of each target absolute time slot, an independent time slot test record is constructed for each corresponding PUSCH object. The time slot test record is fixedly bound to the control parameters, dedicated IQ, expected CRC status, expected TB, result association information, IQ sending window and result deadline of the corresponding PUSCH object, and the same set of test content and resources are referenced after the control parameters are published. The control parameters of the corresponding PUSCH object are fully published through the control path. The dedicated IQ bound to this time slot test record is sent through the data path only when the result receiving position of the time slot test record and the corresponding PUSCH object has been established, the dedicated resource of the time slot test record is valid, the control parameters meet the conditions for timely access, and the current time is within the IQ sending window. The system receives the CRC result generated by the physical layer processing device based on the control parameters and dedicated IQ of the corresponding PUSCH object, as well as the actual TB result generated when the protocol requests the return of data. It queries the currently active time slot test record and the completed historical time slot test record based on the result association information in the result message. Only the uniquely matching currently active time slot test record is identified as the original time slot test record. The CRC result and the actual TB result are written into the original time slot test record, and compared with the expected CRC state, expected TB length, and expected TB content previously saved in the original time slot test record. Furthermore, under the condition of resource isolation referenced by each time slot test record, multiple time slot test records are allowed to overlap and advance in stages. Upon the end of the test plan or the receipt of a stop instruction, the creation of new time slot test records is stopped, and the processing of the started time slot test records continues until all are completed or a unified closing deadline is reached.

Images