 the two (in this example, the L2/L1 FAPI interface). The system test setups deployed should emulate the typical 5G Standalone (SA) and Non-Standalone (NSA) deployments as shown in Fig. 10-2. The complexity of the test environment means a high potential associated cost with establishing the test environment itself including cost of (emulated) core network, CU, DU, RU, and User Equipment (UE) components. Multiple well-established vendors sell dedicated test equipment, but for cost reduction reasons, test equipment can be replaced with off-the- shelf units, for example, RU, UE, and MeNB at the cost of reduced visibility into the internal workings of the equipment. Tradeoffs between cost and performance need to be made by the SVT. Test equipment also includes the following: SA Test Configuration NSA Test Configuration FIGURE 10-2 Stand Alone (SA, top) and Non-Stand Alone (NSA, bottom) system test environments. Chapter 10 Interoperability and test 333 Traffic generators. Traffic sources/sinks that can generate or process deterministic traffic patterns (throughput, packet size, protocol, etc.) as well as deliver test reports to capture key performance indicators (KPIs), including received throughput, latency, packet loss, Protocol analyzers are typically connected through a spoofing port that makes their existence invisible to the equipment communicating over the network. Protocol analyzers can analyze control plane and user plane traffic. RF and spectrum analyzer. Feature testing Most software stack and/or equipment vendors maintain a "compliance matrix" where each feature of the 3GPP standard that is under development is individually accounted for (Supported, Not Supported, Under Development). This is a requirements traceability matrix typically built by taking the 3GPP standard (note to track which version of the standard!) and copying a chapter/subchapter and/or paragraph in this standard into a table that is check- marked for compliance. Keeping to the 3GPP standards definition of feature name and sequence in whi