5g nr hdl cell search and mib recovery reference application video -凯发k8网页登录

the nr hdl cell search and mib recovery reference applications in wireless hdl toolbox are hardware-optimized implementations that you can use to detect and decode 5g new radio signal information as part of your wireless application.

the subsystems from which you will generate hdl are modeled in simulink because simulink has a built-in sense of time and helps visualize parallel architectures and fixed-point data type propagation.

since these started as matlab algorithms using 5g toolbox, we re-used that code to verify our implementations, and that workflow is demonstrated here.

the first step is to partition the functionality that will be deployed to the application, from the testbench. we do that right in matlab, while we add some functionality that will be required for deployment, so we can verify the numerics. for instance because this needs to work for real-world over-the-air signals, it includes a digital down converter for mixing to baseband and changing sample rate.

the input waveform is generated from this matlab function, also included in this reference application.

on the output side, the matlab code will initially display and plot the results, and then print some comparisons versus the reference.

in this diagram, the blue boxes represent test bench elements and the orange represents design. it’s important to do this partitioning early to make it easier to swap in and compare versions with more implementation detail.

there are two major subsystems that are targeted for hardware. the first will perform cell search and detect the primary and secondary synchronization signals, and sometimes that’s all an application needs to use. the second subsystem uses that information to decode the master information block, or mib.

focusing on the synchronization signal block detection, it runs in two phases, controlled by a software layer.

the first phase – search mode - takes in the waveform along with a coarse estimate for frequency offset and the desired subcarrier spacing, and performs pss detection, returning the correlation results for the three possible pss values.  search mode allows the software to coordinate a search for pss (or cells) at different coarse frequency offsets and subcarrier spacings. the software determines the strongest pss correlation, corresponding to the strongest cell, then calls the same hardware subsystem again in demodulation mode, this time passing this pss info for the hardware to perform ofdm demodulation and sss detection, returning those results.

there’s also a matlab structure of diagnostic signals that gets routed to the top level. this structures the design nicely to later bring these signals up to the top-level of the fpga for debug.

finally, the ssb decode subsystem decodes the mib info from the demodulated resource grid.

we still need to adapt these algorithms to work on a continuous stream of signal data, as they would in hardware. simulink is the best environment for that because it models timing.

the matlab testbench drives the simulink model’s inputs, and they get converted to a stream of samples, then back to frames on the output for comparison versus that matlab hardware reference algorithm, which in this stage is the reference the testbench will use to verify.

here we created separate simulink models for each of the hardware-targeted subsystems. this shows the benefits of partitioning – we can use the matlab simulation version of one while we focus on the simulink details of the other. first the cell search subsystem.

the matlab data is passed via the from workspace blocks here, and the outputs collected for matlab in these to workspace blocks. while we drive the test bench using matlab, being able to visualize the architecture and data type propagation makes simulink more conducive to adding the streaming hardware behavior to the design. just as with the matlab reference, the incoming waveform moves through the ddc to pss detection in the first mode, the results are returned to the matlab testbench acting as the software, and then driven back into the hardware in demodulation mode, where it’s sent into the ofdm demodulator, which is a hardware-ready block you can just plug in and configure. the demodulated grid is output, and also sent into sss detection, with the results all registered at the system output and returned to matlab. you can also see the collecting of diagnostic info for output to the top level.

we can kick off the simulation from matlab, and as it starts it generates a plot for the generated test waveform, that shows the combined resource grid of all eight ssbs in the transmitted waveform. the simulation takes a few minutes since it runs both the matlab and simulink, in each mode…so skipping ahead to the results. first the cell search mode results showing pss0 as the strongest cell, then a nice clean peak from the sss correlator, and finally the spectrogram showing the demodulated symbols that follow pss, with sss in the center 127 resource elements of the second symbol. all of these results and the diagnostics are returned to the matlab workspace for analysis.

and then if you want to decode mib, the mib recovery reference application adds a block decode module. this module is triggered when the detection block signals it has detected the cell id. it passes in the cell id and streams in the grid data. again this is well-partitioned where it processes the physical broadcast channel, then the broadcast channel using the polar decoder ip block, and collects the output using this state machine.

now, you can use hdl coder to generate hdl for each of these subsystems. typically you would use one or both in your application and generate hdl from the whole application. but if you want to try just this reference application deployed to a software-defined radio kit, we also have a version of this design combined together and set up to target a xilinx zynq-based sdr. everything in the hdl workflow advisor is pre-populated, including the mapping of the axi interfaces to communicate between the hardware and software, and it will generate the hdl, axi mappings, embedded software, and drivers, and program the board so you can run using live over-the-air signals.

but typically you would use this as-is or make your own modifications to return ssb and mib info to your 5g-based application.

the reference application overview provides more detail, and the design itself is available in wireless hdl toolbox