CN114302436A

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

Info

Publication number: CN114302436A
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: 2022-04-08
Anticipated expiration: 2041-12-31
Also published as: CN114302436B

Abstract

The application discloses a physical layer testing method, a physical layer testing 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 downlink signals; determining data structure information corresponding to the test case parameter script file, wherein the data structure information is used for indicating the incidence 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. 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 guaranteed.

Description

Physical layer testing method and device, chip and module equipment

Technical Field

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

Background

In a New Radio (NR) base station baseband unit, a protocol stack and a physical layer subsystem are included, and both of them run on different chip systems. The interaction between the protocol stack and the physical layer subsystem is performed through a Functional Application Platform Interface (FAPI) for interaction of control information and data information. Before the protocol stack and the physical layer are subjected to system test, the physical layer subsystem (comprising physical layer software and a chip accelerator) needs to be subjected to integrated test.

At present, in a manner of performing an integrated test on a physical layer subsystem, stub functions are usually added to physical layer software, and FAPI interface parameters are written through stub codes, so that the physical layer software is controlled to operate and configure each parameter, and the test on the physical layer subsystem is realized. However, such a method cannot realize automatic testing, and more stub codes affect the integrity of physical layer software. Therefore, how to improve the testing efficiency of the physical layer subsystem is an urgent problem to be solved.

Disclosure of Invention

The application provides a physical layer testing method, a physical layer testing device, a chip and module equipment, which can improve the testing efficiency of a physical layer subsystem and the reliability of testing 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 downlink signals; determining data structure information corresponding to the test case parameter script file, wherein the data structure information is used for indicating the incidence 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.

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 guaranteed.

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: 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 a bandwidth supported by the physical layer, a subcarrier bandwidth and a maximum number of sending antennas.

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

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 Transfer Level (RTL) hardware accelerator of the physical layer to generate a downlink signal. Based on the possible implementation mode, the execution of each test case can be automated, and the test efficiency of the physical layer is improved.

In one possible implementation manner, the determining the PDU parameter of the next slot based on the data structure information includes: determining the SSB PDU parameter of the next time slot based on the SSB parameter included in the data structure information; determining the DCI PDU parameter of the next time slot based on the DCI parameter 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: SSB PDU parameter of the next slot, DCI PDU parameter of the next slot, DLSCH PDU parameter of the next slot, and 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; 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.

In a possible implementation manner, determining 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 the possible implementation mode, the efficiency of the physical layer test can be improved.

In a possible implementation manner, the test case parameter script file is obtained based on the downlink 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 test case is generated in a time-saving and labor-saving manner, 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 test apparatus, comprising: an obtaining unit, configured to obtain a test case parameter script file, where the test case parameter script file includes parameter information of a downlink signal; the determining unit is used for determining data structure information corresponding to the test case parameter script file, and the data structure information is used for indicating the incidence relation among a plurality of test case parameters; the determining unit 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, configured to send the FAPI message to a physical layer.

In a third aspect, the present application provides a chip comprising a processor and a communication interface, the processor being configured to implement the method of the above first aspect of the chip or any possible implementation manner thereof.

In a fourth aspect, the present application provides a module device, which includes a communication module, a power module, a storage module, and a chip, wherein: the power 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 is used for carrying out communication between the module equipment and external equipment; the chip is configured to perform the method of the first aspect or any one of its possible implementations.

In a fifth aspect, the present application provides a computer-readable storage medium having stored thereon computer-readable instructions that, when run on a communication device, cause the communication device to perform the method of the first aspect or any possible implementation thereof.

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 in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.

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 diagram of a system architecture provided by an embodiment of the present application;

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

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

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

fig. 8 is a flowchart for determining a third message according to an embodiment of the present application;

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

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

fig. 11 is a schematic flowchart of another physical layer testing method provided in an embodiment of the present application;

fig. 12a is a schematic flowchart of another physical layer testing method provided in the embodiment of the present application;

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

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

FIG. 14 is a schematic structural 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 apparatus according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The terminology used in the following embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used in the specification of the present application 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 otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the listed items.

It should be noted that the terms "first," "second," "third," and the like in the description and claims of the present application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in other sequences than described or illustrated herein. Furthermore, the terms "comprises," "comprising," or any other variation 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, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

For 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 scheme of the embodiment of the application can be applied to various communication systems, for example: a global system for mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), a long term evolution (long term evolution, LTE) system, a LTE Frequency Division Duplex (FDD) system, a LTE Time Division Duplex (TDD) system, a universal mobile telecommunications system (universal mobile telecommunications system, UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication system, a fifth generation (5G) system or a new radio system (UMTS), and future communication systems.

Referring to fig. 1, fig. 1 is a network architecture diagram of a 5G system according to an embodiment of the present disclosure. 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), where the core network and the Access network are connected through an NG interface, and the gNB is connected through an Xn interface. Wherein, the gNB comprises 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 an Open Radio Access Network (O-RAN) alliance, the design principle of the proposed Radio Access Network breaks through the traditional design concept of the Access Network, and the core technical concept is as follows: the wireless system equipment is divided into standard subsystem components for layered independent research and development, and hardware independent decoupling purchase of a limited propulsion hardware accelerator, a general hardware platform and a Remote Radio Unit (RRU) subsystem can be supported. The key principle comprises the following steps: (1) the industry is led to develop towards an open and interoperative interface, Radio Access Network (RAN) virtualization and a RAN interface supporting big data; (2) hardware generalization: common commercial hardware and commercial chips are utilized to the maximum extent, and Application Specific Integrated Circuit (ASIC) hardware is reduced to the maximum extent; (3) interface development and software development: an Application Programming Interface (API) is formulated and standardized as needed to explore the open source to an appropriate degree.

In a Small Cell Forum (SCF) related design, a standardized Functional Application Platform Interface (FAPI) is proposed for an interface between L2/L3 and L1 PHY in a gNB, wherein L2/L3 software represents a protocol stack and L1 PHY represents a physical layer subsystem. Referring to fig. 2, fig. 2 is a diagram of a 5G FAPI architecture according to an embodiment of the present disclosure. As shown in fig. 2, the L2/L3 software and the L1 PHY may be in different physical locations, and control information and data information are exchanged between them through FAPI interfaces, where the P5 interface is mainly a control information interface between the L2 and the L1 PHY, the P7 interface is mainly a data information interface between the L2 and the L1 PHY, and the P19 interface is a front-end control interface between the L2 and the DFE/RF. The L2/L3 software includes Radio Resource Control (RRC), Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), and Medium Access Control (MAC).

In order to facilitate understanding of the solution provided in the embodiment of the present application, a design architecture of a base station baseband unit is described as follows:

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

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 the embodiment of the present application. The L1 software is divided into three states, IDLE (IDLE), Configuration (CONFIGURED), and RUNNING (RUNNING). The IDLE state is an initial state after being powered on, the IDLE state is switched into a configuration state after receiving a configuration request message, the IDLE state is switched into a RUNNING state after receiving a data transmission start message start request in the configuration state, and the IDLE state returns to a connected state after receiving a data transmission stop message request message. In addition, the L1 software also sends slot indication to indicate the slot interval. As shown in table 1, the L1 software can process different messages in different states, and the same message can be processed differently in different states.

TABLE 1

At present, a method for performing an integrated test on a physical layer subsystem generally adds a stub function into physical layer software, and based on a physical layer software design architecture and a message processing method, two stub functions need to be added to generate a FAPI message for piling. The first stub function is called after L1 software and RTL hardware accelerator initialization is completed; the second stub function is invoked after receiving a slot interrupt in RUNNING status message processing. It can be seen from the flow that the pile function generates the FAPI message according to the parameters of each test case provided by the algorithm, the parameters of different test cases are different, each test case has a set of codes configured to generate the pile driving FAPI message, and when testing different test cases, the FAPI message generation codes of the corresponding test cases need to be opened and the FAPI message generation codes of other test cases need to be shielded to be compiled and run, so that the purpose of testing different test cases is achieved. However, pile functions are added into the physical layer software to drive the flow of the physical layer software to execute, pile driving code amount is very large for different input parameters of different test cases, and when each test case is tested, pile driving codes of the corresponding test case need to be opened, pile driving codes of other test cases need to be closed, and compiling and running are carried out. Therefore, the method cannot realize automatic testing and is not beneficial to management of the test cases, and because the parameters for generating the FAPI message are provided by the algorithm, the parameters of each test case need to be confirmed manually, the workload is huge, and the correctness and the reasonability of the test parameters cannot be guaranteed; in addition, due to the existence of stub codes, the integrity of the physical layer software codes is also damaged.

In order to improve the testing efficiency of a physical layer subsystem and the reliability of testing parameters and ensure the integrity of the physical layer subsystem, the application provides a physical layer testing method, a physical layer testing device, a chip and module equipment. Specifically, the physical layer test method is roughly based on the following principle: firstly, obtaining 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 incidence relation among a plurality of test case parameters; then, determining a FAPI message based on the data structure information; and finally, sending a 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 apparatus, and the testing apparatus may include PC software, protocol stack simulation software, physical layer software, a Register Transfer Level (RTL) hardware accelerator, a Radio Frequency (RF) module, and a module for providing a computing operation of the testing apparatus, and the like, which is not limited herein. For example, the testing apparatus may include a testing layer and a physical layer, where the testing 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, and is configured to determine a FAPI message based on the data structure information, that is, simulate a protocol stack to determine the FAPI message; the physical layer includes physical layer software, an RTL hardware accelerator, and an RF module.

Alternatively, the above-mentioned physical layer testing method may be executed by a terminal device and a testing apparatus, where the terminal device may be, but is not limited to, a tablet computer, a notebook computer, a desktop computer, a smart phone, and the like; the testing device may include protocol stack simulation software, physical layer software, an RTL hardware accelerator, an RF module, a module for providing calculation operation of the testing device, and the like, and exemplarily, the testing device may include a testing layer including the protocol stack simulation software and a physical layer including the physical layer software, the RTL hardware accelerator, and the RF module. For example, see FIG. 5 for an illustration: the terminal device may first obtain 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 test apparatus. Correspondingly, after receiving the data structure information corresponding to the test case parameter script file, the test device determines the FAPI information by using the test layer based on the data structure information, and sends the FAPI information to the physical layer.

The following further describes the physical layer testing method, apparatus, chip and module device provided in the embodiments of the present application in detail.

Based on the above explanation, fig. 6 is a schematic flowchart of a physical layer testing method provided in the 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 apparatus. 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 subject of a method by using a test apparatus including a test layer and a physical layer.

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

In this embodiment, the testcase parameter script file may include one or more parameter Information of the downlink Signal, such as frequency point Information, subcarrier bandwidth, Synchronization Signal block and PBCH block (SSB), Downlink Control Information (DCI), and the like.

In a possible implementation manner, the test case parameter script file is obtained based on the downlink 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 the downlink Signal generation configuration software in the test layer is used for generating a plurality of test case parameter script files according to test requirements, so that the reliability and the correctness of test parameters are ensured by the test case parameter script files, and 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 apparatus through the own downlink signal generation configuration software; the test case parameter script file may be obtained directly from other devices by the test apparatus after the test case parameter script file is generated by the other devices, which 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 incidence relation among a plurality of test case parameters.

In this embodiment, the test device may read the test case parameter script file by using PC software in the test layer, where the PC software is used 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 parameters in the data structure information can be conveniently analyzed subsequently, and the test efficiency of a physical layer can be improved.

In a possible implementation manner, the determining, by the testing apparatus, 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 the one or more target configuration parameters in the test case parameter script file are extracted first, and then the target configuration parameters are saved in the corresponding sub-structures according to the preset data structure. The target configuration parameter may be frequency point Information, a waveform data length, a carrier parameter, an SSB parameter, a DCI parameter, a Downlink Shared Channel (DLSCH) parameter, a Channel State Reference Signal (CSIRS) parameter, a Downlink Bandwidth Part (DLBWP) parameter, and the like.

For example, the process of the testing device determining the target configuration parameters in the test case parameter script file through the PC software in the test layer is as follows:

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

(2) According to a waveform (waveform) keyword, finding parameters related to waveform in a test case parameter script file, such as frequency point information, waveform data length and other information values, and storing the parameters in a waveform substructure in a preset data structure.

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

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

(5) According to the DCI keywords, searching parameters related to the DCI in the test case parameter script file, such as information of a sending time slot index, a sending start symbol, RNTITYPE, RNTI, a search space type, a BWP and CORESET which the test case parameter script file belongs to, and the DCI type, storing the parameters into a DCI substructure in a preset data structure, and recording the number of the DCI.

(6) And searching parameters related to the DLSCH in the test case parameter script file according to the DLSCH keyword, such as information of a transmission time slot index, a transmission starting symbol, the number of occupied symbols, the number of code words, a belonged BWP, a frequency domain occupied PRB, an MCS, a modulation mode and the like, storing the information into a DLSCH substructure in a preset data structure, and recording the number of the DLSCH.

(7) According to the CSIRS keywords, parameters related to CSIRS in the test case parameter script file, such as information of sending time slot index, belonged BWP, sending start symbol, frequency domain occupied PRB, RowIndex and the like, are searched, and are stored in a CSIRS substructure in a preset data structure, and the number of CSIRS is recorded.

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 sub-structures according to a 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 sub-structure, a carrier sub-structure, an SSB sub-structure, a DCI sub-structure, a DLSCH sub-structure, and a CSIRS sub-structure. The preset data structure indicates the association relationship and the position relationship among a 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 according to an embodiment of the present application, where a related parameter of waveform is stored in a waveform substructure in a preset data structure, a related parameter of carrier is stored in a waveform substructure in the preset data structure, a related parameter of SSB is stored in an SSB substructure in the preset data structure, a related parameter of DCI is stored in a DCI substructure in the preset data structure, a related parameter of DLSCH is stored in a DLSCH substructure in the preset data structure, and a related parameter of CSIRS is stored in a CSIRS substructure in the 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 the embodiment of the present application, a test layer of the test apparatus may simulate a protocol stack to determine the FAPI message, and for example, the test apparatus may read the data structure information through a serial port by using DummyPS software in the test layer, and analyze parameters in the data structure information to generate the FAPI message. The DummyPS software can be used for simulating a protocol stack to send FAPI information to a physical layer through a FAPI interface, and periodically scheduling the physical layer to generate a downlink signal, so that the physical layer is tested. Here, the FAPI message may be understood as the aforementioned start message start. Based on the mode, the test efficiency of the physical layer 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. The control information of the downlink signal may be a cell configuration parameter, a Protocol Data Unit (PDU) parameter, and the like; the data information of the downstream signal may be downstream physical shared channel data or the like.

In a possible implementation manner, before the testing device sends the FAPI message to the physical layer, the method further includes: 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 number of sending antennas. The capability Information of the physical layer refers to capabilities included in the physical layer, for example, Band Combination (BC) Information supported by the physical layer in a current network environment, uplink/downlink parameter Information corresponding to each frequency 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. Request may be understood herein as the aforementioned param. 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 includes: the testing device determines the cell configuration parameters according to the data structure information and the capability information of the physical layer; the testing device sends a first message to a physical layer, wherein the first message comprises the cell configuration parameters, and the first message is used for instructing the physical layer to analyze the cell configuration parameters. It should be understood that, after receiving the capability information of the physical layer, the test layer of the test apparatus determines the cell configuration parameter from the data structure information in combination with the data structure information corresponding to the test case parameter script file, and sends the cell configuration parameter to the physical layer through the first message. The first message here may be understood as the aforementioned config. Accordingly, after receiving the first message, the physical layer parses the cell configuration parameter.

Illustratively, the capability information of the physical layer includes carrier bandwidth supporting 100MHz, carrier aggregation supporting, and 4 × 4MIMO supporting, and the testing apparatus 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 a next time slot based on the data structure information, wherein the second message is used for indicating a time slot interval; and the testing device sends 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 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 apparatus needs to determine the PDU parameter that needs to be sent in the next time slot, and sends the PDU parameter that needs to be sent in the next time slot to the physical layer through the third message. The second message here can be understood as the aforementioned slot indication, which indicates the slot interval; the third message here can be understood as the aforementioned DL _ config. Correspondingly, the physical layer analyzes the received PDU parameters, and generates a downlink signal by using an 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 apparatus determines a PDU parameter of a next slot based on the data structure information, including: determining an SSB PDU parameter of a next time slot based on the SSB parameter 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 a next slot based on the DLSCH parameter included in the data structure information; determining a CSIRS PDU parameter of a 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: SSB PDU parameter of next slot, DCI PDU parameter of next slot, DLSCH PDU parameter of next slot and CSIRS PDU parameter of next slot.

Referring to fig. 8, fig. 8 is a flowchart for 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), and calculating the number tx _ SSB _ num and the index number sent by the SSB in the next time slot according to the subcarrier bandwidth, the SSB pattern, the SSB period, the Lmax and the activated SSB index. If tx _ SSB _ num is greater than 0, assembling SSB PDU parameters in a third message (DL _ config.request) according to the SSB parameters, and subtracting 1 from the value of tx _ SSB _ num; if tx _ ssb _ num is less than or equal to 0, reading the DCI number DCI _ num in the data structure information, and making DCI _ cnt equal to 0.

(2) If DCI _ num is greater than DCI _ cnt, reading parameters of DCI _ cnt-th DCI in the data structure information, judging whether the DCI needs to be sent in the next time slot or not according to the sending time slot index of the DCI, if so, extracting the DCI parameters and the BWP and CORESET parameters which belong to the DCI parameters, assembling the DCI parameters and the BWP and CORESET parameters into a DCI PDU parameter in a third message (DL _ CONFIG.request), and adding 1 to the numerical value of DCI _ cnt; and if the dci _ num is less than or equal to the dci _ cnt, reading the DLSCH number DLSCH _ num in the data structure information, and enabling the DLSCH _ cnt to be equal to 0.

(3) If DLSCH _ num is larger than DLSCH _ cnt, reading parameters of DLSCH of the second DLSCH _ cnt in the data structure information, judging whether the DLSCH needs to be sent in the next time slot or not according to the sending time slot index of the DLSCH, if so, extracting the DLSCH parameters and the BWP parameters to assemble the DLSCH parameters into a DLSCH PDU parameter in a third message (DL _ CONFIG. request), and adding 1 to the numerical value of the DLSCH _ cnt; if the DLSCH needs to be transmitted, assembling the DLSCH transmission data parameters including the transmission data length and payload in the third message (TX _ DATA.request) according to the TBSIZE of the DLSCH PDU. If dlsch _ num is less than or equal to dlsch _ cnt, reading the number CSIRS _ num in the data structure information, and making CSIRS _ cnt equal to 0.

(4) If CSIRS _ num is larger than CSIRS _ cnt, reading parameters of CSIRS of CSIRS _ cnt in the data structure information, judging whether the CSIRS needs to be sent in the next time slot or not according to the sending time slot index of the CSIRS, if so, extracting the CSIRS parameters and the BWP parameters to assemble the CSIRS parameters into 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 for the next slot in the third message is completed.

(5) And sending the determined third message (DL _ CONFIG. request/TX _ DATA. request) to the physical layer, so that the physical layer can analyze PDU parameters in the third message, the configuration of a register transmission level RTL hardware accelerator of the physical layer is realized, and a downlink signal is generated.

In one possible implementation, the method further includes: the test device extracts 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 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 parsed by the physical layer based on the third message and the target digital signals output by the RTL hardware accelerator of the physical layer, i.e. the input and output of the RTL hardware accelerator, by using the call data collection function. Comparing the target PDU parameters with the PDU parameters corresponding to the test case parameter script file, and comparing the target digital signals with the digital signals corresponding to the test case parameter script file: 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, determining that the test case parameter script file successfully tests the physical layer; and if the target PDU parameters are different from the PDU parameters corresponding to the test case parameter script file or the target digital signals are different from the digital signals 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 disclosure. As shown in fig. 9, after detecting the timeslot break, the physical layer sends a second message (slot indication) to the test apparatus. If a third message (DL _ CONFIG. request/TX _ DATA. request) sent by the testing device is received, the PDU parameter of each next time slot included in the third message is analyzed, the configuration of the RTL hardware accelerator of the physical layer is realized according to the PDU parameter, and the RTL hardware accelerator is started 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 a third message (DL _ config.request/TX _ data.request) transmitted by the test apparatus is not received but a stop.request is received, stopping the test of the physical layer; if the CONFIG. request is received, sending the cell configuration parameters; if neither the stop.request nor the config.request is received, an error.indication is sent, indicating that a message that cannot be processed is received.

604. The testing device sends the FAPI message to a physical layer.

In the embodiment of the application, a test layer of a test device sends a FAPI message to a physical layer, so that the physical layer can generate a downlink signal based on the FAPI message. Specifically, after receiving the FAPI message, if a time slot interval is detected, the physical layer sends a second message to the test layer of the test apparatus, and then analyzes the PDU parameter in the third message, and then configures the RTL hardware accelerator of the physical layer using the analyzed PDU parameter, 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 sending, wherein the analog signal is a downlink signal.

In summary, the physical layer testing method provided by the embodiment of the present application can be summarized as the physical layer integrated testing framework described below, as shown in fig. 10. The PC software and the DummyPS software communicate through a serial port, the DummyPS software and the L1 software (physical layer software) communicate through a FAPI interface, the L1 software and the PHY accelerator (RTL hardware accelerator) communicate through an RTL interface, and the PHY accelerator and the RF adopt an RF interface to communicate. After the test case parameter script file is obtained, the PC software mainly executes step 602, and sends the data structure information corresponding to the determined test case parameter script file to the DummyPS software through the serial port; the DummyPS software mainly executes the step 603 of sending the determined FAPI message to the L1 software through the FAPI interface, the simulation 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 that the test of the physical layer subsystem is realized. When the PC software detects that the current test case parameter script file is detected to be finished, the next test case parameter script file is automatically read, the test process is repeated, and the DummyPS software is not informed to stop testing until all the test case parameter script files are tested.

Referring to fig. 11, fig. 11 is a schematic flowchart of another physical layer testing method according to an embodiment of the present disclosure. As shown in fig. 11, firstly, 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, extracting cell configuration parameters by DummyPS software according to data structure information provided by PC software; then assembling a FAPI interface param.request and sending the FAPI interface param.request to L1 software; analyzing the cell configuration parameters, generating cell configuration FAPI interface config.request and sending the cell configuration FAPI interface config.request to L1 software; sending and starting a downlink sending FAPI message start.request; according to the transmission period of each channel, before the transmission time slot comes, assembling a downlink transmission configuration FAPI interface dl _ config _ request/Tx _ data _ request and transmitting the downlink transmission configuration FAPI interface dl _ config _ request/Tx _ data _ request to L1 software.

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 test requirements, then data structure information corresponding to the test case parameter script files is determined, FAPI information is determined by analyzing the data structure information corresponding to the test case parameter script files, an analog protocol stack sends the FAPI information to physical layer software through a FAPI interface, and a physical layer is periodically scheduled to generate downlink signals, thereby implementing a test on 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 guaranteed; the execution of each test case can be automated, and the generation of the FAPI information does not insert additional functions into the physical layer, thereby ensuring the integrity of the physical layer. Therefore, based on the method described in fig. 6, 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 can be guaranteed.

Fig. 12a is a schematic 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 subject 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 testing apparatus. Fig. 12a illustrates an example of a terminal device, a test layer, and a physical layer as an execution subject of the method, where the test apparatus 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 the downlink signals.

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

1203. The test layer sends a first request to the physical layer, wherein the first request is used for requesting the physical layer to send the 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, wherein the first message comprises the cell configuration parameters.

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

Wherein the analysis response is used for indicating that the physical layer completes the analysis of the cell configuration parameters.

1208. The test layer determines a FAPI message based on the data structure information, and the FAPI message is used for indicating 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 interruption of the time slot, 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 parameter for the next slot based on the data structure information.

1212. The test layer sends a third message to the physical layer, the third message including the PDU parameter for the next slot.

The specific implementation manners of steps 1201 to 1212 may refer to the description of the specific implementation manners and possible implementation manners of steps 601 to 604, which are not described herein again. 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 of steps 1210 to 1212 is continuously repeated until the test of the whole test case parameter script file is finished.

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 starting a physical layer test, the PC software needs to send an NR _ PC _ DummyPS _ Power on _ Req message to DummyPS software, the DummyPS software is informed of carrying parameters to prepare for starting the test, after the DummyPS software completes corresponding initialization, the PC software replies an NR _ DummyPS _ PC _ Power on _ Cnf message 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, 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 process of the first test case. Simulating L2/L3 software to assemble related FAPI information, firstly assembling PARAM.request information (corresponding to the first request) and sending the information to L1 software, after L1 software replies PARAM.response (including the capability information of a physical layer), DummyPS software firstly replies NR _ DummyPS _ PC _ CellConfig _ Cnf information to PC software to indicate that the configuration of the configuration information of the test case configuration cell is completed, then assembling CONFIG.request (corresponding to the first message) according to the configuration parameters of the cell in the data structure information and sending the CONFIG.request (corresponding to the first message) to L1 software, after L1 software analyzes the configuration parameters of the cell, replying CONFIG.response, after DummyPS, sending START.request information (corresponding to the FAPI information) and starting a data sending process. L1 software detects the time slot interval, and sends slot indication (corresponding to the second message) to DummyPS, which needs to judge the PDU parameter that needs to be sent in the next time slot, and assembles DL _ config.request/TX _ data.request message (corresponding to the third message); after the PC software finishes the test of the current test case, reading the parameter script file of the next test case, sending an NR _ PC _ DummyPS _ CellConfig _ Req message to DummyPS, carrying parameters to inform the DummyPS of the test case switching, storing the relevant configuration information of the cell after the DummyPS software receives the message, sending a STOP.request message to L1 software, informing the stop of the data sending process of the current test case, and starting the test process of a new test case, namely sending a series of message interaction processes such as PARAM.request. 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 a parameter carried by a NR _ PC _ DummyPS _ PowerOn _ Req message, the DummyPS software sends a STOP.request message to the L1 software to inform the L1 software to stop the test, and finally the DummyPS software replies a PC software NR _ PC _ DummyPS _ PowerOn _ Cnf message to indicate that all 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 test requirements, then data structure information corresponding to the test case parameter script files is determined, FAPI information is determined by analyzing the data structure information corresponding to the test case parameter script files, an analog protocol stack sends the FAPI information to physical layer software through a FAPI interface, and a physical layer is periodically scheduled to generate downlink signals, thereby implementing a test on 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 guaranteed; the execution of each test case can be automated, and the generation of the FAPI information does not insert additional functions into the physical layer, thereby ensuring the integrity of the physical layer. Therefore, based on the method described in fig. 12a, the testing efficiency of the physical layer subsystem and the reliability of the testing parameters can be improved, and the integrity of the physical layer subsystem can be guaranteed.

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 an apparatus (e.g., a chip) having 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 multiple 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 a possible implementation manner, the sending unit 1303, before sending the FAPI message to the physical layer, is further configured to: 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 a bandwidth supported by the physical layer, a subcarrier bandwidth and a maximum number of sending antennas.

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

In one 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 sending 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 Transfer 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, when determining a PDU parameter of a next slot based on the data structure information, is specifically configured to: determining the SSB PDU parameter of the next time slot based on the SSB parameter included in the data structure information; determining the DCI PDU parameter of the next time slot based on the DCI parameter 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: SSB PDU parameter of the next slot, DCI PDU parameter of the next slot, DLSCH PDU parameter of the next slot, and CSIRS PDU parameter of the next slot.

In one possible implementation, the apparatus further includes a test unit, the test unit being 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; 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.

In a possible implementation manner, when determining the data structure information corresponding to the test case parameter script file, the determining unit 1302 is specifically configured to: 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 a possible implementation manner, the test case parameter script file is obtained based on the downlink signal generation configuration software.

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

acquiring a test case parameter script file, wherein the test case parameter script file comprises parameter information of downlink signals; determining data structure information corresponding to the test case parameter script file, wherein the data structure information is used for indicating the incidence 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.

In one possible implementation, before sending the FAPI message to the physical layer, the processor is configured to cause the chip to: 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 a bandwidth supported by the physical layer, a subcarrier bandwidth and a maximum number of sending antennas.

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

In one possible implementation, the processor is configured to cause the chip to perform the following operations: 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 Transfer Level (RTL) hardware accelerator of the physical layer to generate a downlink signal.

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 when determining the PDU parameter of the next slot based on the data structure information, the processor is configured to cause the chip to perform the following operations: determining the SSB PDU parameter of the next time slot based on the SSB parameter included in the data structure information; determining the DCI PDU parameter of the next time slot based on the DCI parameter 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: SSB PDU parameter of the next slot, DCI PDU parameter of the next slot, DLSCH PDU parameter of the next slot, and CSIRS PDU parameter of the next slot.

In one possible implementation, the processor is configured to cause the chip to perform the following operations: 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.

In one possible implementation, when 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 a possible implementation, the chip includes at least one processor, at least one first memory, and at least one second memory; the at least one first memory and the at least one processor are interconnected through a line, and instructions are stored in the first memory; the at least one second memory and the at least one processor are interconnected through a line, and the second memory stores the data required to be stored in the method embodiment.

For each device or product applied to or integrated in the chip, each module included in the device or product may be implemented by hardware such as a circuit, or at least a part of the modules may be implemented by a software program running on a processor integrated in the chip, and the rest (if any) part of the modules may be implemented by hardware 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 present 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 for transceiving information.

Memory 1401 may include both read-only memory and random access memory, and provides instructions and data to processor 1402. A portion of the memory 1401 may also include non-volatile random access memory.

The communication interface 1403 is used for receiving or transmitting data.

The Processor 1402 may be a Central Processing Unit (CPU), and the Processor 1402 may be other general-purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. A general purpose processor may be a microprocessor, and optionally, the processor 1402 may be any conventional processor or the like. Wherein:

memory 1401 for storing program instructions.

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

The processor 1402 calls the program instructions stored in the memory 1401 to make the physical layer testing apparatus 1400 execute the method executed by the terminal device in the above-mentioned method embodiment.

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

The power module 1502 is used for providing power for the module device; the storage module 1503 is used for storing data and instructions; the communication module 1501 is used for performing module device internal communication or for communicating the module device with an external device; the chip 1504 is used for executing the method executed by the terminal device in the above method embodiments.

It should be noted that, for details that are not mentioned in the embodiment corresponding to fig. 14 and fig. 15 and the specific implementation manner of each step, reference may be made to the embodiment shown in fig. 6 and the foregoing description, and details are not repeated here.

Embodiments of the present application further provide a computer-readable storage medium, in which instructions are stored, and when the computer-readable storage medium is executed on a processor, the method flow of the above method embodiments is implemented.

Embodiments of the present application further provide a computer program product, where when the computer program product runs on a processor, the method flow of the above method embodiments is implemented.

Each module/unit included in each apparatus and product described in the above embodiments may be a software module/unit, or may also be a hardware module/unit, or may also be a part of a software module/unit and a part of a hardware module/unit. For example, each module/unit included in each apparatus or product applied to or integrated in a chip may be implemented by hardware such as a circuit, or at least a part of the modules/units may be implemented by a software program running on an integrated processor in the chip, and the rest (if any) part of the modules/units may be implemented by hardware such as a circuit; for each device or product applied to or integrated with the chip module, each module/unit included in the device or product may be implemented by using hardware such as a circuit, and different modules/units may be located in the same piece (e.g., a chip, a circuit module, etc.) or different components of the chip module, or at least some of the modules/units may be implemented by using a software program running on a processor integrated inside the chip module, and the rest (if any) of the modules/units may be implemented by using hardware such as a circuit; for each device or product applied to or integrated in the terminal, the modules/units included in the device or product may all be implemented by 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 of the modules/units may be implemented by software programs running on a processor integrated in the terminal, and the rest (if any) of the modules/units may be implemented by hardware such as a circuit.

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

The descriptions of the embodiments provided in the present application may be referred to each other, and the descriptions of the embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments. For convenience and brevity of description, for example, the functions and operations performed by the devices and apparatuses provided in the embodiments of the present application may refer to the related descriptions of the method embodiments of the present application, and may also be referred to, combined with or cited among the method embodiments and the device embodiments.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions 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 solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart 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 downlink signals;

determining data structure information corresponding to the test case parameter script file, wherein the data structure information is used for indicating an incidence 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 comprises control information and data information for the downlink signal.

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

sending a first request to the physical layer, where the first request is used to request the physical layer to send capability information, where the capability information includes a bandwidth supported by the physical layer, a subcarrier bandwidth, and a maximum number of transmit antennas.

4. The method of claim 3, further comprising:

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

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

5. The method of claim 4, further comprising:

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 Transfer Level (RTL) hardware accelerator of the physical layer to generate a downlink signal.

6. The method of claim 5, wherein the data structure information comprises 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 the determining the PDU parameter for the next slot based on the data structure information comprises:

determining an SSB PDU parameter of the next slot based on the SSB parameter included in the data structure information;

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

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

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

the PDU parameters of the next time slot include one or more of: 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, further comprising:

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 determining data structure information corresponding to the test case parameter script file comprises:

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.

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

10. A physical layer test apparatus, the apparatus comprising:

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

the determining unit is used for determining data structure information corresponding to the test case parameter script file, and the data structure information is used for indicating the incidence relation among a plurality of test case parameters;

the determining unit 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, configured to send the FAPI message to the physical layer.

11. A chip comprising a processor and a communication interface, the processor being configured to cause the chip to perform the method of any of claims 1 to 9.

12. 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 is used for carrying out communication between the module equipment and external equipment;

the chip is used for executing the method of any one of claims 1-9.

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