7. 2.2 nFAPI Procedures
• The nFAPI P5 interface configures the PNF device at the PNF device level and at the static PHY level.
• The nFAPI P7 interface operates the PHY for the subframe procedures.
2.2.1 nFAPI PNF configuration procedure
2.2.2 nFAPI P5 PHY configuration procedure
2.2.3. nFAPI p7 subframe procedure
8. 2.2.1 nFAPI PNF Configuration Procedures
1. Inizialitation
2. Reset
3. Restart
4. Reconfigure
• See next slide for detail of
PNF Inizialitation
Procedure & PNF PARAM
message exchange.
*) See the full spec
documents for other
procedure and message
exchange
17. • 2.2.2 nFAPI P7 Subframe Procedures
The nFAPI P7 interface configures the PNF PHYs every subframe.
Procedures Purpose
1. PHY Synchronization estimation and compensation of timing differences between the VNF
and the PHY instance
2. API message order The L1 API has constraints on when certain subframe messages can be
sent, or will be
received, by the L2/L3 software.
3. API message timing nFAPI P7 messages sent from the VNF to PNF must arrive at the PNF a
minimum time before the subframe they configure starts transmission
on the air interface
4. Semi-static information create periodic transmission patterns on the uplink
5. Uplink HARQ signalling ACK or NACK downlink
data transmissions sent to a UE.
6. Downlink BCH, PCH, DLSCH, MCH, PRS, CSI
7. Uplink RACH, ULSCH, SRS, CQI, SR
8. RNTI Measurement SNR, Timing advance, Doppler estimation
18. • 2.3 nFAPI messages
• 2.3.1 nFAPI Transport Layer
23. nFAPI Implementation – P5
• Source Code:
https://gitlab.com/changshengliusamuel/openairinterface5g/blob/dev
elop-nb-iot/openair2/LAYER2/MAC/config_NB_IoT.c
• For the explanation of the flowchart please refer to:
http://bit.ly/nfapi-implementation-p5