Remove hardcoding of numerology in VNF
Similar to the parent commit, make the numerology in the VNF configurable. Unlike for the PNF change, the VNF frame/slot info is in a per-PNF connection structure to which the "oai_integration" code has no access. So we need to hack the nfapi_vnf_p7_add_pnf() function signature to take the numerology, to be able to save this on a per-PNF basis. The fact that we store this on a per-PNF basis is not strictly required, as the VNF cannot handle multiple numerologies as of now, either. However, we might want to extend this in the future, so it seems prudent to store this on a per-PNF basis, so that we could start handling multiple numerologies at the L2 without the need to change the L1 or nFAPI code itself. Also, the numerology is not needed except for some code that deals with timing over nFAPI. As of now, we don't use this code (nFAPI gets a trigger every slot, as per the VNF request, see an earlier commit in this series), but also here, let's not make the future more complicated by storing the numerology for each PNF now (this could always be reverted). For 4G, put numerology 0 (15kHZ SCS), which is the SCS that LTE uses.
Showing
Please register or sign in to comment