CN114302436B

CN114302436B - Physical layer testing method and device, chip and module equipment

Info

Publication number: CN114302436B
Application number: CN202111676117.8A
Authority: CN
Inventors: 王鹏; 索忠伟; 汤坚
Original assignee: Unisoc Chongqing Technology Co Ltd
Current assignee: Unisoc Chongqing Technology Co Ltd
Priority date: 2021-12-31
Filing date: 2021-12-31
Publication date: 2023-07-18
Anticipated expiration: 2041-12-31
Also published as: CN114302436A

Abstract

The application discloses a physical layer testing method, a device, a chip and module equipment, wherein the method comprises the following steps: acquiring a test case parameter script file, wherein the test case parameter script file comprises parameter information of a downlink signal; determining data structure information corresponding to the test case parameter script file, wherein the data structure information is used for indicating the association relation among a plurality of test case parameters; determining a Function Application Platform Interface (FAPI) message based on the data structure information, wherein the FAPI message is used for indicating a physical layer to generate a downlink signal based on the FAPI message; the FAPI message is sent to the physical layer. Based on the method described in the application, the test efficiency of the physical layer subsystem and the reliability of the test parameters can be improved, and the integrity of the physical layer subsystem is ensured.

Description

Physical layer testing method and device, chip and module equipment

Technical Field

The present invention relates to the field of computers, and in particular, to a physical layer testing method, a physical layer testing device, a physical layer testing chip, and a physical layer module device.

Background

The New air interface (NR) base station baseband unit includes a protocol stack and a physical layer subsystem, which are respectively run on different chip systems. The protocol stack and the physical layer subsystem interact control information and data information through a functional application platform interface (Functional application platform interface, FAPI). Before the system test is performed on the protocol stack and the physical layer, the physical layer subsystem (including the physical layer software and the chip accelerator) needs to be subjected to an integrated test.

At present, a pile function is added into physical layer software in an integrated test mode, and FAPI interface parameters are written in through pile codes, so that the operation of the physical layer software is controlled, and each parameter is configured, and the test of the physical layer subsystem is realized. However, this approach does not allow for automated testing and more stub code can affect the integrity of the physical layer software. Therefore, how to improve the testing efficiency of the physical layer subsystem is a problem to be solved.

Disclosure of Invention

The utility model provides a physical layer test method, device, chip and module equipment, which can improve the test efficiency of a physical layer subsystem and the reliability of test parameters, and ensure the integrity of the physical layer subsystem.

In a first aspect, the present application provides a physical layer testing method, including: acquiring a test case parameter script file, wherein the test case parameter script file comprises parameter information of a downlink signal; determining data structure information corresponding to the test case parameter script file, wherein the data structure information is used for indicating the association relation among a plurality of test case parameters; determining a Function Application Platform Interface (FAPI) message based on the data structure information, wherein the FAPI message is used for indicating a physical layer to generate a downlink signal based on the FAPI message; the FAPI message is sent to the physical layer.

Based on the method described in the first aspect, the test efficiency of the physical layer subsystem and the reliability of the test parameters can be improved, and the integrity of the physical layer subsystem is ensured.

In one possible implementation, the FAPI message includes control information and data information of the downlink signal.

In one possible implementation, before sending the FAPI message to the physical layer, the method further includes: and sending a first request to a physical layer, wherein the first request is used for requesting the physical layer to send capability information, and the capability information comprises the bandwidth supported by the physical layer, the subcarrier bandwidth and the maximum sending antenna number.

In one possible implementation, the method further includes: determining a cell configuration parameter according to the data structure information and the capability information of the physical layer; and sending a first message to the physical layer, wherein the first message comprises the cell configuration parameters and is used for indicating the physical layer to analyze the cell configuration parameters.

In one possible implementation, the method further includes: after receiving a second message sent by the physical layer, determining a protocol data unit PDU parameter of a next time slot based on the data structure information, wherein the second message is used for indicating a time slot interval; and sending a third message to the physical layer, wherein the third message comprises the PDU parameter of the next time slot, and the third message is used for indicating a register transmission level RTL hardware accelerator of the physical layer to generate a downlink signal. Based on the possible implementation manner, the execution of each test case can be automated, and the test efficiency of the physical layer is improved.

In one possible implementation, the data structure information includes a synchronization signal block SSB parameter, a downlink control information DCI parameter, a downlink shared channel DLSCH parameter, and a channel state reference signal CSIRS parameter, and determining a PDU parameter of a next slot based on the data structure information includes: determining SSB PDU parameters of the next slot based on SSB parameters included in the data structure information; determining DCI PDU parameters of the next time slot based on the DCI parameters included in the data structure information; determining a DLSCH PDU parameter of the next slot based on the DLSCH parameter included in the data structure information; determining a CSIRS PDU parameter of the next slot based on the CSIRS parameter included in the data structure information; the PDU parameters for the next slot include one or more of the following: the SSB PDU parameter of the next slot, the DCI PDU parameter of the next slot, the DLSCH PDU parameter of the next slot, and the CSIRS PDU parameter of the next slot.

In one possible implementation, the method further includes: extracting target PDU parameters obtained by the physical layer based on the third message analysis and target digital signals output by an RTL hardware accelerator of the physical layer; if the target PDU parameters are the same as the PDU parameters corresponding to the test case parameter script file and the target digital signals are the same as the digital signals corresponding to the test case parameter script file, determining that the physical layer test is successful.

In one possible implementation manner, determining the data structure information corresponding to the test case parameter script file includes: determining one or more target configuration parameters in the test case parameter script file; and determining data structure information corresponding to the test case parameter script file based on one or more target configuration parameters and a preset data structure. Based on this possible implementation, the efficiency of physical layer testing can be improved.

In one possible implementation, the test case parameter script file is derived based on downstream signal generation configuration software. Based on the possible implementation mode, because the source of the test case parameter script file is generated by special software, the generation of the test case is time-saving and labor-saving, and the correctness and the reliability of the test case parameter script file can be improved.

In a second aspect, the present application provides a physical layer testing apparatus, the apparatus comprising: the acquisition unit is used for acquiring a test case parameter script file, wherein the test case parameter script file comprises parameter information of a downlink signal; the determining unit is used for determining data structure information corresponding to the test case parameter script file, wherein the data structure information is used for indicating the association relation among a plurality of test case parameters; the determining unit is further configured to determine a functional application platform interface FAPI message based on the data structure information, where the FAPI message is used to instruct a physical layer to generate a downlink signal based on the FAPI message; and the sending unit is used for sending the FAPI message to the physical layer.

In a third aspect, the present application provides a chip comprising a processor and a communication interface, the processor being configured to cause the chip to perform the method of the first aspect or any one of its possible implementations.

In a fourth aspect, the present application provides a module apparatus, the module apparatus comprising a communication module, a power module, a storage module, and a chip, wherein: the power supply module is used for providing electric energy for the module equipment; the storage module is used for storing data and instructions; the communication module is used for carrying out internal communication of the module equipment or carrying out communication between the module equipment and external equipment; the chip is for performing the method of the first aspect described above or any one of its possible implementations.

In a fifth aspect, the present application provides a computer readable storage medium having stored therein computer readable instructions which, when run on a communication device, cause the communication device to perform the method of the first aspect or any one of its possible implementations.

In a sixth aspect, the present application provides a computer program or computer program product comprising code or instructions which, when run on a computer, cause the computer to perform the method as in the first aspect or any one of its possible implementations.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a network architecture diagram of a 5G system provided in an embodiment of the present application;

fig. 2 is a 5G FAPI architecture diagram provided in an embodiment of the present application;

fig. 3 is a base station baseband unit architecture diagram provided in an embodiment of the present application;

FIG. 4 is a schematic diagram of an L1 software state machine provided by an embodiment of the present application;

FIG. 5 is a schematic diagram of a system architecture provided in an embodiment of the present application;

fig. 6 is a flow chart of a physical layer testing method according to an embodiment of the present application;

FIG. 7a is a preset data structure provided in an embodiment of the present application;

FIG. 7b is a schematic diagram of data structure information of a test case parameter script file according to an embodiment of the present application;

FIG. 8 is a flow chart of determining a third message provided by an embodiment of the present application;

FIG. 9 is a flow chart of a test data parameter provided in an embodiment of the present application;

FIG. 10 is a physical layer integration test framework provided in an embodiment of the present application;

FIG. 11 is a flowchart illustrating another physical layer testing method according to an embodiment of the present disclosure;

FIG. 12a is a flowchart of another physical layer testing method according to an embodiment of the present disclosure;

FIG. 12b is a message interaction diagram between PC software/DummyPS/L1 software provided by an embodiment of the present application;

fig. 13 is a schematic structural diagram of a physical layer testing device according to an embodiment of the present application;

FIG. 14 is a schematic diagram of another physical layer testing apparatus according to an embodiment of the present disclosure;

fig. 15 is a schematic structural diagram of a module device according to an embodiment of the present application.

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made clearly and completely with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

The terminology used in the following embodiments of the application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include the plural forms as well, unless the context clearly indicates to the contrary. It should also be understood that the term "and/or" as used in this application refers to and encompasses any or all possible combinations of one or more of the listed items.

It should be noted that, in the description and claims of the present application and in the above figures, the terms "first," "second," "third," etc. are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments of the present application described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or server that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed or inherent to such process, method, article, or apparatus.

For a better understanding of the embodiments of the present application, the following first describes a communication system related to the embodiments of the present application:

the technical solution of the embodiment of the application can be applied to various communication systems, for example: global system for mobile communications (global system of mobile communication, GSM), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA) systems, general packet radio service (general packet radio service, GPRS), long term evolution (long term evolution, LTE) systems, LTE frequency division duplex (frequency division duplex, FDD) systems, LTE time division duplex (time division duplex, TDD), universal mobile telecommunications system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX) communication systems, fifth generation (5th generation,5G) systems or new radio, NR) future communication systems, and the like.

Referring to fig. 1, fig. 1 is a network architecture diagram of a 5G system according to an embodiment of the present application. As shown in fig. 1, the network architecture of the 5G system mainly comprises two parts, namely a 5G core network (Access and Mobility Management Function/User Plane Function, AMF/UPF) and an access network (5G Node b, gNB), wherein the core network and the access network are connected through an NG interface, and the gNB is connected through an Xn interface. Wherein, gNB includes a centralized Unit (5G Node B-Central Unit, gNB-CU) and a Distributed Unit (5G Node B-Distributed Unit, gNB-DU). With the establishment of the open radio access network (Open Radio Access Network, O-RAN) alliance, the design principle of the proposed radio access network breaks through the traditional access network design concept, and the core technical concept is as follows: the wireless system equipment is split into standard subsystem components for layered independent research and development, and can support the independent decoupling purchase of the limited propulsion hardware accelerator, a general hardware platform and the remote radio unit (Remote Radio Unit, RRU) subsystem. The key principles include: (1) The industry is led towards open, interoperable interfaces, radio access network (Radio Access Network, RAN) virtualization and RAN interfaces supporting big data; (2) hardware generalization: maximally utilizing common commercial hardware and commercial chips, and maximally reducing proprietary application-specific integrated circuit (Application Specific Integrated Circuit, ASIC) hardware; (3) interface openness and software openness sourcing: an application program interface (Application Programming Interface, API) is formulated and its standardization is driven as required, exploring the open source to a suitable extent.

In a Small Cell Forum (SCF) related design, a standardized functional application platform interface (Functional application platform interface, FAPI) is proposed for an interface between L2/L3 and L1 PHY in the gNB, where L2/L3 software represents a protocol stack and L1 PHY represents a physical layer subsystem. Referring to fig. 2, fig. 2 is a 5G FAPI architecture diagram provided in an embodiment of the present application. As shown in fig. 2, the L2/L3 software and the L1 PHY may be located at different physical locations, and control information and data information are interacted between them through a FAPI interface, where the P5 interface is mainly a control information interface between the L2 and L1 PHY, the P7 interface is mainly a data information interface between the L2 and L1 PHY, and the P19 interface is a front end control interface between the L2 and DFE/RF. The L2/L3 software includes radio resource control (Radio Resource Control, RRC), packet data convergence protocol (Packet Data Convergence Protocol, PDCP), radio link layer control protocol (Radio Link Control, RLC), and medium access control protocol (Media Access Control, MAC).

In order to facilitate understanding of the solution provided in the embodiments of the present application, the following description is provided for a base station baseband unit design architecture:

referring to fig. 3, fig. 3 is a base station baseband unit architecture diagram provided in an embodiment of the present application. As shown in fig. 3, the L2/L3 software (protocol stack) performs message interaction with the L1 software (physical layer subsystem) through the FAPI interface, while the L1 software controls the RTL hardware accelerator through the register transfer stage (Register Transformation Level, RTL) interface, and provides parameters of different physical channels for generating digital signals, and finally the digital signals are transmitted to the RF through the Radio Frequency (RF) interface, and generate analog signals for sending.

As described above, the L2/L3 software performs information interaction with the L1 software through the FAPI interface, and the L1 software performs state machine switching through different FAPI messages. As shown in fig. 4, fig. 4 is a schematic diagram of an L1 software state machine provided in an embodiment of the present application. The L1 software is divided into three states, IDLE state (IDLE), CONFIGURED state (CONFIGURED), and RUNNING state (RUNNING). The IDLE state is an initial state after power-up, and after receiving a configure request message, it switches into a CONFIGURED state, after receiving a start message start, request, in the CONFIGURED state, it switches into a RUNNING state, and after receiving a stop message stop. In addition, the L1 software also transmits a slot indication to indicate the slot interval. As shown in table 1, the messages that the L1 software can process in different states are different, and the same messages are also different in different states.

TABLE 1

At present, a pile function is added to physical layer software in a mode of carrying out integrated test on a physical layer subsystem, and pile functions are added at two positions to generate a piled FAPI message based on a physical layer software design architecture and a message processing mode. The first stub function is invoked after the initialization of the L1 software and RTL hardware accelerator is completed; the second stub function is invoked after receiving a slot interrupt in the RUNNING status message process. The pile function generates FAPI information according to the parameters of each test case provided by the algorithm, the parameters of different test cases are different, a set of codes for configuring and generating piling FAPI information is arranged for each test case, and when different test cases are tested, FAPI information generating codes of corresponding test cases are required to be opened, other test case FAPI information generating codes are shielded for compiling and running, so that the purpose of testing the different test cases is achieved. However, pile functions are added into the physical layer software to drive the physical layer software to execute, pile code amounts can be very large for different input parameters of different test cases, when each test case is tested, corresponding test case pile codes are required to be opened, and other test case pile codes are required to be closed for compiling and running. Therefore, the method cannot realize automatic test, is unfavorable for the management of test cases, and because parameters for generating FAPI information are provided by an algorithm, each test case parameter needs to be confirmed manually, the workload is huge, and the correctness and rationality of the test parameters cannot be ensured; in addition, the integrity of the physical layer software code is also damaged due to the existence of the stub code.

In order to improve the test efficiency of the physical layer subsystem and the reliability of test parameters and ensure the integrity of the physical layer subsystem, the application provides a physical layer test method, a device, a chip and module equipment. Specifically, the general principle of the physical layer testing method is as follows: firstly, acquiring a test case parameter script file, wherein the test case parameter script file comprises parameter information of downlink signals; then, determining data structure information corresponding to the test case parameter script file, wherein the data structure information is used for indicating the association relation among a plurality of test case parameters; then, determining a FAPI message based on the data structure information; and finally, sending the FAPI message to the physical layer so that the physical layer generates a downlink signal based on the FAPI message.

In a specific implementation, the above-mentioned physical layer testing method may be performed by a testing device, where the testing device may include PC software, protocol stack simulation software, physical layer software, a register transfer level (Register Transformation Level, RTL) hardware accelerator, a Radio Frequency (RF) module, a module that provides computing operation of the testing device, and the like, and is not limited herein. The test device may include a test layer and a physical layer, where the test layer includes PC software and protocol stack simulation software, the PC software may be configured to determine data structure information corresponding to the test case parameter script file, and the protocol stack simulation software may be DummyPS software configured to determine FAPI messages based on the data structure information, i.e. simulate a protocol stack to determine FAPI messages; the physical layer includes physical layer software, an RTL hardware accelerator, and an RF module.

Alternatively, the above-mentioned physical layer test method may be performed by a terminal device and a test apparatus together, the terminal device may be a tablet computer, a notebook computer, a desktop computer, a smart phone, or the like, but is not limited thereto; the test apparatus may include protocol stack simulation software, physical layer software, an RTL hardware accelerator, an RF module, and modules providing computational operations of the test apparatus, etc., and by way of example, the test apparatus may include a test layer including protocol stack simulation software and a physical layer including physical layer software, an RTL hardware accelerator, and an RF module. See, for example, fig. 5: the terminal equipment can acquire the test case parameter script file, then determine the data structure information corresponding to the test case parameter script file, and send the data structure information to the testing device. Correspondingly, after receiving the data structure information corresponding to the test case parameter script file, the testing device determines the FAPI message based on the data structure information by utilizing the testing layer, and sends the FAPI message to the physical layer.

The physical layer testing method, the device, the chip and the module device provided by the embodiment of the application are further described in detail below.

Based on the above description, fig. 6 is a schematic flow chart of a physical layer testing method according to an embodiment of the present application. As shown in fig. 6, the physical layer testing method includes the following steps 601 to 604. The method execution body shown in fig. 6 may be a test device. Alternatively, the method execution body shown in fig. 6 may be a chip in the test apparatus. Fig. 6 illustrates an example of an execution body of a test apparatus including a test layer and a physical layer.

601. The test device acquires a test case parameter script file, wherein the test case parameter script file comprises parameter information of a downlink signal.

In the embodiment of the application, the test case parameter script file may be one or more, and the test case parameter script file includes parameter information of a downlink signal, such as frequency point information, subcarrier bandwidth, synchronization signal block (Synchronization Signal and PBCH block, SSB), downlink control information (Dowlink Control Information, DCI), and the like.

In one possible implementation, the test case parameter script file is derived based on downstream signal generation configuration software. The test layer of the test device can also comprise downlink Signal generation configuration software (such as Keysight N7631C Signal Studio), and a plurality of test case parameter script files are generated according to test requirements by using the downlink Signal generation configuration software in the test layer, so that the reliability and the correctness of the test parameters are ensured by the test case parameter script files, and meanwhile, the time cost of the test is saved.

It should be noted that, the test case parameter script file may be generated by the test device through the own downlink signal generating configuration software; the test case parameter script file may be directly obtained by the test apparatus from another device after the test case parameter script file is generated by the other device, and is not limited herein.

602. The test device determines data structure information corresponding to the test case parameter script file, wherein the data structure information is used for indicating the association relation among a plurality of test case parameters.

In this embodiment of the present application, the test device may read the test case parameter script file by using PC software in the test layer, where the PC software is configured to generate data structure information corresponding to the test case parameter script file. By standardizing the parameter information in the test case parameter script file, the subsequent analysis of the parameters in the data structure information is facilitated, and the improvement of the test efficiency of the physical layer is facilitated.

In one possible implementation manner, the determining, by the testing device, data structure information corresponding to the test case parameter script file includes: determining one or more target configuration parameters in the test case parameter script file; and determining data structure information corresponding to the test case parameter script file based on the one or more target configuration parameters and a preset data structure. It should be understood that first, one or more target configuration parameters in the test case parameter script file are extracted, and then the target configuration parameters are saved to corresponding substructures according to a preset data structure. The target configuration parameters may be frequency point information, waveform data length, carrier parameters, SSB parameters, DCI parameters, downlink shared channel (Downlink Shared Channel, DLSCH) parameters, channel state Reference Signal (CSIRS) parameters, downlink bandwidth part (Downlink Bandwidth Part, DLBWP) parameters, and the like.

The flow of the test device determining the target configuration parameters in the test case parameter script file by the PC software in the test layer is exemplified as follows:

(1) And reading the test case parameter script file.

(2) According to the waveform (waveform) key words, searching the parameters related to waveform in the test case parameter script file, such as information values of frequency point information, waveform data length and the like, and storing the information values in a waveform substructure in a preset data structure.

(3) According to carrier keywords, searching carrier related parameters in the test case parameter script file, such as bandwidth, cell ID, resource grid configuration and other information, and storing the information in a carrier sub-structure in a preset data structure.

(4) And searching parameters related to SSB in the test case parameter script file, such as subcarrier bandwidth, SSB pattern, SSB period, lmax, activated SSB index, MIB and other information, and storing the information in an SSB substructure in a preset data structure according to the SSB key word.

(5) And searching parameters related to the DCI in the test case parameter script file, such as information of a transmission time slot index, a transmission start symbol, RNTITYPE, RNTI, a search space type, a belonged BWP, a CORESET, a DCI type and the like, according to the DCI key word, storing the information in a DCI substructure in a preset data structure, and recording the number of the DCI.

(6) According to the DLSCH key words, searching parameters related to the DLSCH in the test case parameter script file, such as information of a transmission time slot index, a transmission start symbol, an occupied symbol number, a codeword number, a BWP (binary WP) to which the DLSCH belongs, a frequency domain occupied PRB, MCS (modulation scheme) and the like, storing the information into a DLSCH substructure in a preset data structure, and recording the number of the DLSCH.

(7) And searching parameters related to the CSIRS in the test case parameter script file, such as information of a sending time slot index, a BWP (broadband wireless communication protocol), a sending start symbol, a frequency domain occupation PRB (physical resource block), a RowIndex and the like, according to the CSIRS key words, storing the information into a CSIRS substructure in a preset data structure, and recording the number of the CSIRS.

Further, after one or more target configuration parameters in the test case parameter script file are determined, the target configuration parameters are stored in the corresponding substructures according to the preset data structure. As shown in fig. 7a, fig. 7a is a preset data structure provided in an embodiment of the present application, where the preset data structure includes a waveform substructure, a carrier substructure, an SSB substructure, a DCI substructure, a DLSCH substructure, and a CSIRS substructure. The preset data structure indicates the association and the positional relationship among the plurality of test case parameters. As shown in fig. 7b, fig. 7b is a schematic diagram of data structure information of a test case parameter script file provided in the embodiment of the present application, where a wave-form related parameter is stored in a wave-form substructure in a preset data structure, a carrier-related parameter is stored in a wave-form substructure in a preset data structure, an SSB-related parameter is stored in an SSB substructure in a preset data structure, a DCI-related parameter is stored in a DCI substructure in a preset data structure, a DLSCH-related parameter is stored in a DLSCH substructure in a preset data structure, and a CSIRS-related parameter is stored in a CSIRS substructure in a preset data structure.

603. The testing device determines a Function Application Platform Interface (FAPI) message based on the data structure information, wherein the FAPI message is used for indicating a physical layer to generate a downlink signal based on the FAPI message.

In this embodiment of the present application, a test layer of a test device may simulate a protocol stack to determine a FAPI message, and exemplary, the test device may utilize DummyPS software in the test layer to read the data structure information through a serial port, and parse parameters in the data structure information to generate the FAPI message. The DummyPS software may be configured to simulate a protocol stack to send an FAPI message to a physical layer through an FAPI interface, and periodically schedule the physical layer to generate a downlink signal, thereby implementing a test on the physical layer. Here, the FAPI message may be understood as the foregoing initiation message START.request, START.request for indicating that the physical layer is ready to start generating and transmitting the downlink signal. Based on the mode, the physical layer testing efficiency can be improved, and the integrity of the physical layer is ensured.

In one possible implementation, the FAPI message includes control information and data information of the downlink signal. Wherein, the control information of the downlink signal can be cell configuration parameters, protocol data unit (Protocol Data Unit, PDU) parameters, etc.; the data information of the downlink signal may be downlink physical shared channel data or the like.

In one possible implementation, the testing device further includes, before sending the FAPI message to the physical layer: and sending a first request to the physical layer, wherein the first request is used for requesting the physical layer to send capability information, and the capability information comprises the bandwidth supported by the physical layer, the subcarrier bandwidth and the maximum sending antenna number. The capability information of the physical layer refers to a capability included in the physical layer, for example, band Combination (BC) information supported by the physical layer in the current network environment, uplink/downlink parameter information corresponding to each Band, supported multiple-Input multiple-Output (MIMO) information, power Class (Power Class) information, channel state information Reference Signal (Channel State Information-Reference Signal) information, bandwidth Class (bandwidth Class) information, and the like. The first request here can be understood as the aforementioned param. And after the physical layer receives the first request sent by the test layer in the test device, the capability information of the physical layer is sent to the test layer in the test device.

Optionally, the method further comprises: the testing device determines a cell configuration parameter according to the data structure information and the capability information of the physical layer; the test device sends a first message to the physical layer, the first message including the cell configuration parameter, the first message being used to instruct the physical layer to parse the cell configuration parameter. It should be understood that after the test layer of the test device receives the capability information of the physical layer, the test layer combines the data structure information corresponding to the test case parameter script file to determine the cell configuration parameter from the data structure information, and sends the cell configuration parameter to the physical layer through the first message. The first message here can be understood as the config. Request described previously. Correspondingly, after the physical layer receives the first message, the physical layer analyzes the cell configuration parameters.

The capability information of the physical layer includes carrier bandwidth supporting 100MHz, carrier aggregation supporting 4×4MIMO supporting, and the test device extracts the cell configuration parameters from the received data structure information in combination with the capability information of the physical layer.

In one possible implementation, the method further includes: after receiving a second message sent by the physical layer, the testing device determines a protocol data unit PDU parameter of the next time slot based on the data structure information, wherein the second message is used for indicating a time slot interval; the test device sends a third message to the physical layer, where the third message includes the PDU parameters of the next time slot, and the third message is used to instruct the register transfer level RTL hardware accelerator of the physical layer to generate a downlink signal. It should be understood that, after receiving the second message sent by the physical layer, the test layer in the test device needs to determine the PDU parameters needed to be sent in the next time slot, and sends the PDU parameters needed to be sent in the next time slot to the physical layer through the third message. The second message herein may be understood as the aforementioned slot indication for indicating the slot interval; the third message here can be understood as dl_config. Request/tx_data. Request as described earlier. Correspondingly, the physical layer analyzes the received PDU parameters, and generates a downlink signal by using the RTL hardware accelerator of the physical layer.

Optionally, the data structure information includes an SSB parameter, a DCI parameter, a DLSCH parameter, and a CSIRS parameter, and the testing device determines a PDU parameter of a next slot based on the data structure information, including: determining SSB PDU parameters of the next slot based on the SSB parameters included in the data structure information; determining DCI PDU parameters of the next time slot based on the DCI parameters included in the data structure information; determining DLSCH PDU parameters of the next time slot based on the DLSCH parameters included in the data structure information; determining a CSIRS PDU parameter of the next time slot based on the CSIRS parameter included in the data structure information; the PDU parameters for the next slot include one or more of the following: the SSB PDU parameter of the next slot, the DCI PDU parameter of the next slot, the DLSCH PDU parameter of the next slot, and the CSIRS PDU parameter of the next slot.

Referring to fig. 8, fig. 8 is a flowchart of determining a third message according to an embodiment of the present application. As shown in fig. 8, the following steps need to be performed:

(1) And reading SSB substructure parameters in the data structure information (namely a cell configuration parameter structure body), and calculating the number tx_ssb_num and index numbers sent by SSB in the next time slot according to subcarrier bandwidth, SSB pattern, SSB period, lmax and activated SSB index. If tx_ssb_num is greater than 0, assembling an SSB PDU parameter in a third message (dl_config. Request) according to the SSB parameter, and subtracting 1 from the value of tx_ssb_num; if tx_ssb_num is less than or equal to 0, the DCI number dci_num in the data structure information is read, and dci_cnt is made equal to 0.

(2) If dci_num is larger than dci_cnt, reading a parameter of dci_cnt in the data structure information, judging whether the DCI needs to be transmitted in the next time slot according to a transmission time slot index of the DCI, extracting the DCI parameter, the BWP and the CORESET parameters if the DCI needs to be transmitted, assembling the DCI PDU parameter in a third message (DL_CONFIG. request), and adding 1 to the value of the dci_cnt; if dci_num is less than or equal to dci_cnt, the DLSCH number dlsch_num in the data structure information is read, and dlsch_cnt is made equal to 0.

(3) If dlsch_num is greater than dlsch_cnt, reading the DLSCH parameter of the dlsch_cnt in the data structure information, judging whether the DLSCH needs to be transmitted in the next time slot according to the transmission time slot index, extracting the DLSCH parameter and the BWP parameter if the DLSCH parameter needs to be transmitted, assembling the DLSCH PDU parameter in a third message (dl_config. Request), and adding 1 to the value of dlsch_cnt; if the DLSCH needs to be transmitted, the DLSCH transmission data parameters in the third message (TX_DATA. Request) including the transmission data length and the payload are assembled according to the TBSIZE of the DLSCH PDU. If dlsch_num is less than or equal to dlsch_cnt, the number csirs_num of CSIRS in the data structure information is read, and csirs_cnt is made equal to 0.

(4) If csirs_num is greater than csirs_cnt, reading parameters of csirs_cnt in the data structure information, judging whether the CSIRS needs to be transmitted in the next time slot according to the transmission time slot index, extracting the CSIRS parameters and the BWP parameters if the CSIRS needs to be transmitted, assembling the CSIRS PDU parameters in a third message (DL_CONFIG. request), and adding 1 to the value of csirs_cnt. If csirs_num is less than or equal to csirs_cnt, the PDU parameter determination of the next time slot in the third message is completed.

(5) And sending the determined third message (DL_CONFIG/TX_DATA. Request) to the physical layer so that the physical layer can analyze the PDU parameters in the third message, and the configuration of a register transfer level RTL hardware accelerator of the physical layer is realized, thereby generating a downlink signal.

In one possible implementation, the method further includes: the testing device extracts the target PDU parameters obtained by the physical layer based on the third message analysis and the target digital signals output by the RTL hardware accelerator of the physical layer; if the target PDU parameter is the same as the PDU parameter corresponding to the test case parameter script file, and the target digital signal is the same as the digital signal corresponding to the test case parameter script file, the test device determines that the physical layer test is successful.

It should be understood that the test layer of the test apparatus may extract the target PDU parameters obtained by the physical layer based on the analysis of the third message and the target digital signals output by the RTL hardware accelerator of the physical layer, that is, the input and output of the RTL hardware accelerator, by using the call data acquisition function. Comparing the target PDU parameter with the PDU parameter corresponding to the test case parameter script file, and comparing the target digital signal with the digital signal corresponding to the test case parameter script file: if the target PDU parameters are the same as the PDU parameters corresponding to the test case parameter script file and the target digital signals are the same as the digital signals corresponding to the test case parameter script file, determining that the test case parameter script file successfully tests the physical layer; if the target PDU parameter is different from the PDU parameter corresponding to the test case parameter script file or the target digital signal is different from the digital signal corresponding to the test case parameter script file, determining that the test case parameter script file fails to test the physical layer.

Referring to fig. 9, fig. 9 is a flowchart of a test data parameter according to an embodiment of the present application. As shown in fig. 9, after the physical layer detects the slot interruption, a second message (slot indication) is sent to the test device. If a third message (DL_CONFIG/TX_DATA. Request) sent by the testing device is received, analyzing PDU parameters of each next time slot included in the third message, realizing configuration of an RTL hardware accelerator of a physical layer according to the PDU parameters, and starting the RTL hardware accelerator to output a digital signal. In order to verify the correctness of the test result of the test case parameter script file, a data acquisition function is called, PDU parameters input by the RTL hardware accelerator and digital signals output by the RTL hardware accelerator are acquired, and the PDU parameters and the digital signals corresponding to the known test case parameter script file are compared, so that the verification of the physical layer test is realized. If the third message (dl_confirm/tx_data.request) sent by the test device is not received, but the stop.request is received, stopping the test of the physical layer; if the CONFIG request is received, transmitting a cell configuration parameter; if neither stop. Request nor config. Request is received, an error. Indication is sent, indicating receipt of an unprocessed message.

604. The test device sends the FAPI message to the physical layer.

In the embodiment of the application, the test layer of the test device sends the FAPI message to the physical layer, so that the physical layer can generate a downlink signal based on the FAPI message. Specifically, after the physical layer receives the FAPI message, if the time slot interval is detected, a second message is sent to the test layer of the test device, PDU parameters in the third message are analyzed later, and then the RTL hardware accelerator of the physical layer is configured by utilizing the analyzed PDU parameters so that the RTL hardware accelerator generates a digital signal; and finally, the RTL hardware accelerator transmits the digital signal to the radio frequency module through the radio frequency interface so as to convert the digital signal into an analog signal for transmission, wherein the analog signal is a downlink signal.

In general, the physical layer testing method provided in the embodiments of the present application may be summarized as a physical layer integrated testing framework described below, as shown in fig. 10. The PC software and the DummyPS software are communicated through a serial port, the DummyPS software and the L1 software (physical layer software) are communicated through a FAPI interface, the L1 software and the PHY accelerator (RTL hardware accelerator) are communicated through an RTL interface, and the PHY accelerator and the RF radio frequency are communicated through an RF interface. After the test case parameter script file is obtained, the PC software mainly executes step 602, and data structure information corresponding to the determined test case parameter script file is sent to DummyPS software through a serial port; the DummyPS software mainly executes step 603, where the determined FAPI message is sent to the L1 software through the FAPI interface, the analog protocol stack sends the FAPI message to the physical layer software through the FAPI interface, and the L1 software is periodically scheduled to generate a downlink signal through the RTL hardware accelerator, so as to implement testing of the physical layer subsystem. When the PC software detects that the current test case parameter script file is detected, the next test case parameter script file is automatically read, the test process is repeated, and the DummyPS software is informed to stop the test until all the test case parameter script files are completely tested.

Referring to fig. 11, fig. 11 is a flowchart of another physical layer testing method according to an embodiment of the present application. As shown in fig. 11, first, the PC software reads the test case parameter script file, generates data structure information corresponding to the test case parameter script file, and sends the data structure information to the DummyPS software through the serial port; then DummyPS software extracts cell configuration parameters according to data structure information provided by PC software; then assembling the FAPI interface param.request and sending the FAPI interface param.request to L1 software; analyzing the cell configuration parameters, generating a cell configuration FAPI interface config.request and sending the cell configuration FAPI interface config.request to L1 software; sending a start-up downlink transmission FAPI message start.request; the downlink transmission configuration FAPI interface dl_config_request/Tx_data.request is assembled and transmitted to the L1 software before the arrival of the transmission slot according to the transmission period of each channel.

It can be seen that, based on the method described in fig. 6, different test case parameter script files are generated by using downlink signal configuration software according to the test requirements, then data structure information corresponding to the test case parameter script files is determined, the FAPI message is determined by analyzing the data structure information corresponding to the test case parameter script files, the simulation protocol stack sends the FAPI message to the physical layer software through the FAPI interface, and the physical layer is periodically scheduled to generate a downlink signal, so that the test of the physical layer is realized. It should be understood that, because the source of the test case parameter script file is generated by special software, the generation of the test case is time-saving and labor-saving, and the correctness of the test case parameter script file is ensured; the execution of each test case can be automated, and no additional function is inserted into the physical layer for generating the FAPI message, so that the integrity of the physical layer is ensured. Therefore, based on the method described in fig. 6, the test efficiency and the reliability of the test parameters of the physical layer subsystem can be improved, and the integrity of the physical layer subsystem is ensured.

Fig. 12a is a flowchart of another physical layer testing method according to an embodiment of the present application. As shown in fig. 12a, the physical layer testing method includes the following steps 1201 to 1212. The method execution body shown in fig. 12a may be a terminal device and a test apparatus. Alternatively, the method execution body shown in fig. 12a may be a chip in the terminal device and a chip in the test apparatus. Fig. 12a illustrates an example of a method execution body of a terminal device, a test layer, and a physical layer, wherein the test device includes the physical layer and the test layer.

1201. The terminal equipment acquires a test case parameter script file, wherein the test case parameter script file comprises parameter information of a downlink signal.

1202. The terminal equipment determines data structure information corresponding to the test case parameter script file, and sends the data structure information to the testing device, wherein the data structure information is used for indicating the association relation among a plurality of test case parameters.

1203. The test layer sends a first request to the physical layer requesting the physical layer to send capability information.

1204. The physical layer transmits capability information to the test layer, the capability information including a bandwidth supported by the physical layer, a subcarrier bandwidth, and a maximum number of transmit antennas.

1205. And the test layer determines the cell configuration parameters according to the data structure information and the capability information of the physical layer.

1206. The test layer sends a first message to the physical layer, the first message including the cell configuration parameter.

1207. The physical layer analyzes the cell configuration parameters included in the first message and sends an analysis response to the test layer.

The parsing response is used for indicating that the physical layer has completed parsing the cell configuration parameters.

1208. The test layer determines a FAPI message based on the data structure information, the FAPI message being used to instruct the physical layer to generate a downlink signal based on the FAPI message.

1209. The test layer sends the FAPI message to the physical layer.

1210. And if the physical layer detects the time slot interruption, sending a second message to the test layer, wherein the second message is used for indicating the time slot interval.

1211. The test layer determines the PDU parameters of the next slot based on the data structure information.

1212. The test layer transmits a third message to the physical layer, the third message including the PDU parameters of the next slot.

The specific implementation manner of steps 1201 to 1212 may refer to the specific implementation manner and the description of possible implementation manners of steps 601 to 604, which are not described herein. It should be noted that, for the current test case parameter script file, after the physical layer sends the second message to the test layer, the process from step 1210 to step 1212 is repeated until the test of the entire test case parameter script file is completed.

Referring to fig. 12b, fig. 12b is a message interaction diagram between PC software/DummyPS/L1 software according to an embodiment of the present application. Before the physical layer test is started, the PC software needs to send an NR_PC_DummyPS_PowerOn_req message to the DummyPS software, carry parameters to inform the DummyPS software that the DummyPS software is ready to start the test, after the DummyPS software completes corresponding initialization, the NR_DummyPS_PC_PowerOn_Cnf message is replied to the PC software, the PC software starts to read a first test case parameter script file, determines data structure information corresponding to the test case parameter script file, and sends the data structure information to the DummyPS software through the NR_PC_DummyPS_CellConfig_req message, and the DummyPS software stores the data structure information and starts to start the flow of the first test case. Simulating the L2/L3 software to assemble related FAPI information, firstly assembling a PARAM.request message (corresponding to the first request) to the L1 software, after the L1 software replies a PARAM.response (including capability information of a physical layer), the DummyPS software replies an NR_DummyPS_PC_CellConfig_Cnf message to the PC software to indicate that the configuration of the test case configuration cell configuration information is completed, then assembling a CONFIG.request (corresponding to the first message) to the L1 software according to the cell configuration parameters in the data structure information, after the L1 software analyzes the cell configuration parameters, sending a START.request message (corresponding to the FAPI message) after replying CONFIG.response, dummyPS, and starting a data sending process. The L1 software detects the time slot interval and sends a slot indication (corresponding to the second message) to the DummyPS, the DummyPS needs to judge the PDU parameters needed to be sent in the next time slot, and a DL_CONFIG. request/TX_DATA. Request message (corresponding to the third message) is assembled; after finishing the test of the current test case, the PC software reads the parameter script file of the next test case, sends an NR_PC_DummyPS_CellConfig_Req message to DummyPS, carries parameters to inform the DummyPS software of switching the test case, saves the relevant configuration information of the cell after receiving the message, sends a STOP.request message to the L1 software, informs to stop the data sending process of the current test case, and starts the test process of the new test case, namely sends a series of message interaction processes such as PARAM.request and the like. After the PC software completes the test of all test case parameter script files, the DummyPS software is informed to stop the test by sending an NR_PC_DummyPS_PowerOn_req message carrying parameters, the DummyPS software sends a STOP.request message to the L1 software, the L1 software is informed to stop the test, and finally the DummyPS software replies with an NR_PC_DummyPS_PowerOn_Cnf message of the PC software to indicate that all the tests are finished.

It can be seen that, based on the method described in fig. 12a, different test case parameter script files are generated by using downlink signal configuration software according to the test requirements, then data structure information corresponding to the test case parameter script files is determined, FAPI messages are determined by analyzing the data structure information corresponding to the test case parameter script files, and the simulation protocol stack sends the FAPI messages to the physical layer software through the FAPI interface, and periodically schedules the physical layer to generate downlink signals, thereby realizing the test of the physical layer. It should be understood that, because the source of the test case parameter script file is generated by special software, the generation of the test case is time-saving and labor-saving, and the correctness of the test case parameter script file is ensured; the execution of each test case can be automated, and no additional function is inserted into the physical layer for generating the FAPI message, so that the integrity of the physical layer is ensured. Therefore, based on the method described in fig. 12a, the test efficiency and the reliability of the test parameters of the physical layer subsystem can be improved, and the integrity of the physical layer subsystem is ensured.

Referring to fig. 13, fig. 13 is a schematic structural diagram of a physical layer testing apparatus according to an embodiment of the present invention, where the physical layer testing apparatus may be a terminal device or a device (e.g. a chip) with a function of the terminal device. Specifically, as shown in fig. 13, the physical layer testing apparatus 1300 may include:

An obtaining unit 1301, configured to obtain a test case parameter script file, where the test case parameter script file includes parameter information of a downlink signal;

a determining unit 1302, configured to determine data structure information corresponding to the test case parameter script file, where the data structure information is used to indicate an association relationship between a plurality of test case parameters;

the determining unit 1302 is further configured to determine, based on the data structure information, a FAPI message of a functional application platform interface, where the FAPI message is used to instruct a physical layer to generate a downlink signal based on the FAPI message;

a sending unit 1303, configured to send the FAPI message to a physical layer.

In one possible implementation, the sending unit 1303 is further configured to, before sending the FAPI message to the physical layer: and sending a first request to a physical layer, wherein the first request is used for requesting the physical layer to send capability information, and the capability information comprises the bandwidth supported by the physical layer, the subcarrier bandwidth and the maximum sending antenna number.

In a possible implementation, the determining unit 1302 is further configured to: determining a cell configuration parameter according to the data structure information and the capability information of the physical layer; the transmitting unit 1303 is further configured to: and sending a first message to the physical layer, wherein the first message comprises the cell configuration parameters and is used for indicating the physical layer to analyze the cell configuration parameters.

In a possible implementation, the determining unit 1302 is further configured to: after receiving a second message sent by the physical layer, determining a protocol data unit PDU parameter of a next time slot based on the data structure information, wherein the second message is used for indicating a time slot interval; the transmitting unit 1303 is further configured to: and sending a third message to the physical layer, wherein the third message comprises the PDU parameter of the next time slot, and the third message is used for indicating a register transmission level RTL hardware accelerator of the physical layer to generate a downlink signal.

In a possible implementation manner, the data structure information includes a synchronization signal block SSB parameter, a downlink control information DCI parameter, a downlink shared channel DLSCH parameter, and a channel state reference signal CSIRS parameter, and the determining unit 1302 is specifically configured to, when determining the PDU parameter of the next slot based on the data structure information: determining SSB PDU parameters of the next slot based on SSB parameters included in the data structure information; determining DCI PDU parameters of the next time slot based on the DCI parameters included in the data structure information; determining a DLSCH PDU parameter of the next slot based on the DLSCH parameter included in the data structure information; determining a CSIRS PDU parameter of the next slot based on the CSIRS parameter included in the data structure information; the PDU parameters for the next slot include one or more of the following: the SSB PDU parameter of the next slot, the DCI PDU parameter of the next slot, the DLSCH PDU parameter of the next slot, and the CSIRS PDU parameter of the next slot.

In a possible implementation manner, the apparatus further includes a test unit, where the test unit is configured to: extracting target PDU parameters obtained by the physical layer based on the third message analysis and target digital signals output by an RTL hardware accelerator of the physical layer; if the target PDU parameters are the same as the PDU parameters corresponding to the test case parameter script file and the target digital signals are the same as the digital signals corresponding to the test case parameter script file, determining that the physical layer test is successful.

In one possible implementation manner, the determining unit 1302 is specifically configured to, when determining the data structure information corresponding to the test case parameter script file: determining one or more target configuration parameters in the test case parameter script file; and determining data structure information corresponding to the test case parameter script file based on one or more target configuration parameters and a preset data structure.

In one possible implementation, the test case parameter script file is derived based on downstream signal generation configuration software.

The embodiment of the application also provides a chip which can execute the relevant steps of the electronic equipment in the embodiment of the method. The chip includes a processor and a communication interface, the processor configured to cause the chip to:

Acquiring a test case parameter script file, wherein the test case parameter script file comprises parameter information of a downlink signal; determining data structure information corresponding to the test case parameter script file, wherein the data structure information is used for indicating the association relation among a plurality of test case parameters; determining a Function Application Platform Interface (FAPI) message based on the data structure information, wherein the FAPI message is used for indicating a physical layer to generate a downlink signal based on the FAPI message; the FAPI message is sent to the physical layer.

In one possible implementation, before sending the FAPI message to the physical layer, the processor is configured to cause the chip to: and sending a first request to a physical layer, wherein the first request is used for requesting the physical layer to send capability information, and the capability information comprises the bandwidth supported by the physical layer, the subcarrier bandwidth and the maximum sending antenna number.

In one possible implementation, the processor is configured to further cause the chip to: determining a cell configuration parameter according to the data structure information and the capability information of the physical layer; and sending a first message to the physical layer, wherein the first message comprises the cell configuration parameters and is used for indicating the physical layer to analyze the cell configuration parameters.

In one possible implementation, the processor is configured to further cause the chip to: after receiving a second message sent by the physical layer, determining a protocol data unit PDU parameter of a next time slot based on the data structure information, wherein the second message is used for indicating a time slot interval; and sending a third message to the physical layer, wherein the third message comprises the PDU parameter of the next time slot, and the third message is used for indicating a register transmission level RTL hardware accelerator of the physical layer to generate a downlink signal.

In a possible implementation, the data structure information includes a synchronization signal block SSB parameter, a downlink control information DCI parameter, a downlink shared channel DLSCH parameter, and a channel state reference signal CSIRS parameter, and the processor is configured to cause the chip to perform the following operations when determining the PDU parameter of the next slot based on the data structure information: determining SSB PDU parameters of the next slot based on SSB parameters included in the data structure information; determining DCI PDU parameters of the next time slot based on the DCI parameters included in the data structure information; determining a DLSCH PDU parameter of the next slot based on the DLSCH parameter included in the data structure information; determining a CSIRS PDU parameter of the next slot based on the CSIRS parameter included in the data structure information; the PDU parameters for the next slot include one or more of the following: the SSB PDU parameter of the next slot, the DCI PDU parameter of the next slot, the DLSCH PDU parameter of the next slot, and the CSIRS PDU parameter of the next slot.

In one possible implementation, the processor is configured to further cause the chip to: extracting target PDU parameters obtained by the physical layer based on the third message analysis and target digital signals output by an RTL hardware accelerator of the physical layer; if the target PDU parameters are the same as the PDU parameters corresponding to the test case parameter script file and the target digital signals are the same as the digital signals corresponding to the test case parameter script file, determining that the physical layer test is successful.

In one possible implementation, in determining the data structure information corresponding to the test case parameter script file, the processor is configured to cause the chip to perform the following operations: determining one or more target configuration parameters in the test case parameter script file; and determining data structure information corresponding to the test case parameter script file based on one or more target configuration parameters and a preset data structure.

In one possible implementation, the chip includes at least one processor, at least one first memory, and at least one second memory; wherein the at least one first memory and the at least one processor are interconnected by a circuit, and instructions are stored in the first memory; the at least one second memory and the at least one processor are interconnected by a line, where the second memory stores data to be stored in the embodiment of the method.

For each device and product applied to or integrated in the chip, each module contained in the device and product can be realized in a hardware mode such as a circuit, or at least part of the modules can be realized in a software program, the software program runs on a processor integrated in the chip, and the rest (if any) of the modules can be realized in a hardware mode such as a circuit.

Referring to fig. 14, fig. 14 is a schematic structural diagram of another physical layer testing apparatus according to an embodiment of the invention. The physical layer testing apparatus 1400 may include a memory 1401, a processor 1402. Optionally, a communication interface 1403 is also included. The memory 1401, processor 1402, and communication interface 1403 are connected by one or more communication buses. Wherein the communication interface 1403 is controlled by the processor 1402 to transmit and receive information.

Memory 1401 may include read only memory and random access memory and provide instructions and data to processor 1402. A portion of memory 1401 may also include nonvolatile random access memory.

The communication interface 1403 is used to receive or transmit data.

The processor 1402 may be a central processing unit (Central Processing Unit, CPU), the processor 1402 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor, but in the alternative, the processor 1402 may be any conventional processor or the like. Wherein:

Memory 1401 is used to store program instructions.

A processor 1402 for calling program instructions stored in memory 1401.

The processor 1402 invokes the program instructions stored in the memory 1401 to cause the physical layer testing apparatus 1400 to perform the method performed by the terminal device in the method embodiment described above.

As shown in fig. 15, fig. 15 is a schematic structural diagram of a module apparatus according to an embodiment of the present application. The module apparatus 1500 may perform the steps related to the terminal apparatus or the network apparatus in the foregoing method embodiment, where the module apparatus 1500 includes: communication module 1501, power module 1502, memory module 1503 and chip 1504.

Wherein the power module 1502 is configured to provide power to the module device; the storage module 1503 is used for storing data and instructions; the communication module 1501 is used for performing communication inside the module device or for communicating between the module device and an external device; the chip 1504 is used to perform the method performed by the terminal device in the method embodiment described above.

It should be noted that, details not mentioned in the embodiments corresponding to fig. 14 and fig. 15 and specific implementation manners of each step may refer to the embodiment shown in fig. 6 and the foregoing details, which are not repeated herein.

The present application also provides a computer readable storage medium having instructions stored therein, which when run on a processor, implement the method flows of the method embodiments described above.

The present application also provides a computer program product, which when run on a processor, implements the method flows of the above method embodiments.

With respect to each of the apparatuses and each of the modules/units included in the products described in the above embodiments, it may be a software module/unit, a hardware module/unit, or a software module/unit, and a hardware module/unit. For example, each module/unit included in each device or product applied to or integrated in the chip may be implemented in hardware such as a circuit, or at least part of the modules/units may be implemented in software program, where the software program runs on an integrated processor inside the chip, and the rest (if any) of the modules/units may be implemented in hardware such as a circuit; for each device and product applied to or integrated in the chip module, each module/unit contained in the device and product can be realized in a hardware manner such as a circuit, different modules/units can be located in the same piece (such as a chip, a circuit module and the like) or different components of the chip module, or at least part of the modules/units can be realized in a software program, the software program runs on a processor integrated in the chip module, and the rest (if any) of the modules/units can be realized in a hardware manner such as a circuit; for each device, product, or application to or integrated with the terminal, the included modules/units may all be implemented in hardware such as a circuit, and different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components in the terminal, or at least some modules/units may be implemented in a software program, where the software program runs on a processor integrated inside the terminal, and the remaining (if any) some modules/units may be implemented in hardware such as a circuit.

It should be noted that, for simplicity of description, the foregoing method embodiments are all described as a series of acts, but it should be understood by those skilled in the art that the present application is not limited by the order of acts described, as some acts may, in accordance with the present application, occur in other orders and concurrently. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily required in the present application.

The descriptions of the embodiments provided in the present application may be referred to each other, and the descriptions of the embodiments are focused on, and for the part that is not described in detail in a certain embodiment, reference may be made to the related descriptions of other embodiments. For convenience and brevity of description, for example, reference may be made to the related descriptions of the method embodiments of the present application for the functions and operations performed by the devices and apparatuses provided by the embodiments of the present application, and reference may also be made to each other, combined or cited between the method embodiments, and between the device embodiments.

Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A physical layer testing method, the method comprising:

acquiring a test case parameter script file, wherein the test case parameter script file comprises parameter information of a downlink signal;

determining one or more target configuration parameters in the test case parameter script file;

determining data structure information corresponding to the test case parameter script file based on the one or more target configuration parameters and a preset data structure, wherein the data structure information is used for indicating the association relation among a plurality of test case parameters;

determining a Function Application Platform Interface (FAPI) message based on the data structure information, wherein the FAPI message is used for indicating a physical layer to generate a downlink signal based on the FAPI message;

and sending the FAPI message to the physical layer.

2. The method of claim 1, wherein the FAPI message includes control information and data information of the downlink signal.

3. The method of claim 1, wherein prior to said sending the FAPI message to the physical layer, the method further comprises:

and sending a first request to the physical layer, wherein the first request is used for requesting the physical layer to send capability information, and the capability information comprises the bandwidth supported by the physical layer, the subcarrier bandwidth and the maximum sending antenna number.

4. A method according to claim 3, characterized in that the method further comprises:

determining a cell configuration parameter according to the data structure information and the capability information of the physical layer;

and sending a first message to the physical layer, wherein the first message comprises the cell configuration parameters, and the first message is used for indicating the physical layer to analyze the cell configuration parameters.

5. The method according to claim 4, wherein the method further comprises:

after receiving a second message sent by the physical layer, determining a protocol data unit PDU parameter of a next time slot based on the data structure information, wherein the second message is used for indicating a time slot interval;

and sending a third message to the physical layer, wherein the third message comprises PDU parameters of the next time slot, and the third message is used for indicating a register transmission level RTL hardware accelerator of the physical layer to generate a downlink signal.

6. The method of claim 5, wherein the data structure information includes a synchronization signal block SSB parameter, a downlink control information DCI parameter, a downlink shared channel DLSCH parameter, and a channel state reference signal CSIRS parameter, and wherein determining the PDU parameter for the next slot based on the data structure information comprises:

Determining SSB PDU parameters of the next slot based on SSB parameters included in the data structure information;

determining DCI PDU parameters of the next time slot based on the DCI parameters included in the data structure information;

determining a DLSCH PDU parameter of the next time slot based on the DLSCH parameter included in the data structure information;

determining a CSIRS PDU parameter of the next time slot based on the CSIRS parameter included in the data structure information;

the PDU parameters of the next slot include one or more of the following: the SSB PDU parameter of the next time slot, the DCI PDU parameter of the next time slot, the DLSCH PDU parameter of the next time slot and the CSIRS PDU parameter of the next time slot.

7. The method of claim 6, wherein the method further comprises:

extracting target PDU parameters obtained by the physical layer based on the third message analysis and target digital signals output by an RTL hardware accelerator of the physical layer;

and if the target PDU parameters are the same as the PDU parameters corresponding to the test case parameter script file and the target digital signals are the same as the digital signals corresponding to the test case parameter script file, determining that the physical layer test is successful.

8. The method of claim 1, wherein the test case parameter script file is derived based on downstream signal generation configuration software.

9. A physical layer testing apparatus, the apparatus comprising:

the acquisition unit is used for acquiring a test case parameter script file, wherein the test case parameter script file comprises parameter information of downlink signals;

a determining unit, configured to determine one or more target configuration parameters in the test case parameter script file;

the determining unit is further configured to determine data structure information corresponding to the test case parameter script file based on the one or more target configuration parameters and a preset data structure, where the data structure information is used to indicate an association relationship between multiple test case parameters;

the determining unit is further configured to determine a functional application platform interface FAPI message based on the data structure information, where the FAPI message is used to instruct a physical layer to generate a downlink signal based on the FAPI message;

and the sending unit is used for sending the FAPI message to the physical layer.

10. A chip comprising a processor and a communication interface, the processor being configured to cause the chip to perform the method of any one of claims 1-8.

11. The utility model provides a module equipment, its characterized in that, module equipment includes communication module, power module, storage module and chip, wherein:

the power supply module is used for providing electric energy for the module equipment;

the storage module is used for storing data and instructions;

the communication module is used for carrying out internal communication of module equipment or carrying out communication between the module equipment and external equipment;

the chip being adapted to perform the method of any one of claims 1 to 8.

12. A computer readable storage medium having stored therein computer readable instructions which, when run on a communication device, cause the communication device to perform the method of any of claims 1-8.