RF TEST REPORT
Eurofins TA Technology (Shanghai) Co., Ltd. tested the above equipment in accordance with the requirements in FCC CFR47 Part 15E (2023). The test results show that the equipment tested is capable of demonstrating compliance with the requirements as documented in this report.
Prepared by: Xu Ying
Approved by: Xu Kai
Testing Laboratory: Eurofins TA Technology (Shanghai) Co., Ltd., Building 3, No.145, Jintang Rd, Pudong Shanghai, P.R.China. TEL: +86-021-50791141/2/3, FAX: +86-021-50791141/2/3-8000
Report Summary
This document presents the results of radio frequency (RF) testing performed on the Nokia G-1425G-E Optical Network Terminal (ONT). The testing was conducted by Eurofins TA Technology (Shanghai) Co., Ltd. in accordance with FCC CFR47 Part 15E regulations. The report details compliance with Dynamic Frequency Selection (DFS) requirements for devices operating in the U-NII bands.
The testing covered several key areas, including DFS Detection Thresholds, U-NII Detection Bandwidth, Channel Availability Check Time, Channel Move Time, Channel Closing Transmission Time, Non-Occupancy Period, and Statistical Performance Check. All tested parameters met the specified requirements, indicating compliance with the relevant FCC standards.
1. General Description of Equipment Under Test
1.1. Applicant and Manufacturer Information
Applicant | Nokia Shanghai Bell Co., Ltd. |
Applicant Address | No.388, Ningqiao Rd, Pilot Free Trade Zone, Shanghai, 201206 P.R. China |
Manufacturer | Nokia of America Corporation |
Manufacturer Address | 2301 Sugar Bush Rd. Raleigh, NC 27612 |
1.2. General Information
Model | G-1425G-E |
SN | ALCLB43F4474 |
Hardware Version | 3TN 00674 AAAA |
Software Version | 3TN00702FJLI48 |
Power Supply | AC adapter |
Antenna Type | External Antenna |
Operating Frequency Range(s) | U-NII-2A: 5250MHz-5350MHz U-NII-2C: 5470MHz-5725MHz |
Modulation Type | 802.11a: OFDM 802.11n(HT20/HT40): OFDM 802.11ac (VHT20/VHT40/VHT80): OFDM |
Operating Mode | Master, Client with radar detection, Client without radar detection |
1.3. EUT Accessory
Adapter 1 | Manufacturer: Ruide, Model: RD1201000-C55-35MGD |
Adapter 2 | Manufacturer: Keli, Model: KL-WA120100-E |
Note: The EUT is sent from the applicant to Eurofins TA and the information of the EUT is declared by the applicant.
1.4. Hardware Code Information
ONT Mnemonic | Kit Code | EMA Code | Part Description |
---|---|---|---|
1 | 3TN 00683 XXXX (Code can be any capital letter from A to Z) | 3TN 00673 XXXX (Code can be any capital letter from A to Z) | GPON ONT,4XGE UNI,1POTS, WIFI 5,2x2 11n + 2x2 11ac |
1.5. Information of Configuration
No. | Name | Model/Code No. | Edition | Serial No. |
---|---|---|---|---|
1 | G-1425G-E | 3TN 00673 AAAA | PEM2 | PEM |
2 | G-1425G-E | 3TN 00673 BAAA | PEM2 | PEM |
3 | Power adapter | RD1201000-C55-35MGD | - | PEM |
4 | Power adapter | RD1201000-C55-35OGD | - | PEM |
5 | Power adapter | RD1201000-C55-35YGD | - | PEM |
6 | Power adapter | KL-WA120100-E | - | PEM |
7 | Power adapter | KL-WE120100-B | - | PEM |
8 | Power adapter | KL-WB120100-B | - | PEM |
1.6. Auxiliary Equipment Details
No. | Name | Brand name | Model | NSB code | Valid Until | |
---|---|---|---|---|---|---|
1 | BigTao | XINERTEL | BigTao220 | DE8708 | No Cal. Required | |
2 | PC | Lenovo | T61 | 7661MC4L3KW965 | No Cal. Required | |
3 | PC | Lenovo | T61 | 7661MC4L3KW959 | No Cal. Required | |
5 | 7362 ISAM DF-16 | NOKIA | 3FE45632AAAA | YP1747F403F | No Cal. Required |
1.7. Information of Ports
No. | Port name | Test Number | Shielded or unshielded | Cable type (optic, twisted pair, etc.) | Max. Cable length |
---|---|---|---|---|---|
1 | AC Power Port | 1 | unshielded | - | - |
2 | GE | 4 | unshielded | - | - |
1 | POTS | 1 | unshielded | - | - |
System Diagram
The system diagram illustrates the connections between the GPON ONT (G-1425G-E) and various components. The ONT features a GPON Port, RJ11 port (for voice), and four RJ45 ports (GE 1x4) for data connectivity. It supports 2.4G WiFi and 5G WiFi via internal antennas. The device connects to an OLT via fiber and receives power from a PSU via a DC jack. Auxiliary equipment includes a BigTao220 device, a PC, and a router for throughput testing. The diagram shows data flow from the OLT through the ONT to the PC and WiFi interfaces.
Wireless Technology and Frequency Range
Wireless Technology | Bandwidth | Channel | Frequency |
---|---|---|---|
U-NII-2A | 20 MHz | 52 | 5260MHz |
56 | 5280MHz | ||
60 | 5300MHz | ||
64 | 5320MHz | ||
40 MHz | 54 | 5270MHz | |
62 | 5310MHz | ||
80 MHz | 58 | 5290MHz | |
Wi-Fi U-NII-2C | 20 MHz | 100 | 5500MHz |
104 | 5520MHz | ||
108 | 5540MHz | ||
112 | 5560MHz | ||
116 | 5580MHz | ||
120 | 5600MHz | ||
124 | 5620MHz | ||
128 | 5640MHz | ||
132 | 5660MHz | ||
136 | 5680MHz | ||
140 | 5700MHz | ||
144 | 5720MHz | ||
40 MHz | 102 | 5510MHz | |
110 | 5550MHz | ||
118 | 5590MHz | ||
126 | 5630MHz | ||
134 | 5670MHz | ||
142 | 5710MHz | ||
80 MHz | 106 | 5530MHz | |
122 | 5610MHz | ||
138 | 5690MHz |
Does this device support TPC Function? Yes
Does this device support TDWR Band? Yes
3. Applied Standards
According to the specifications of the manufacturer, the equipment must comply with the requirements of the following standards:
Test standards: FCC CFR47 Part 15E (2023) Unlicensed National Information Infrastructure Devices
Reference standard: FCC KDB 905462 D02 UNII DFS Compliance Procedures New Rules v02
4. DFS Technical Requirements and Radar Test Waveforms
4.1. DFS Overview
Table 1: Applicability of DFS Requirements Prior to Use of a Channel
Requirement | Operational Mode | ||
---|---|---|---|
Master | Client Without Radar Detection | Client With Radar Detection | |
Non-Occupancy Period | Yes | Not required | Yes |
DFS Detection Threshold | Yes | Not required | Yes |
Channel Availability Check Time | Yes | Not required | Not required |
U-NII Detection Bandwidth | Yes | Not required | Yes |
Table 2: Applicability of DFS Requirements during Normal Operation
Requirement | Operational Mode | |
---|---|---|
Master Device or Client with Radar Detection | Client Without Radar Detection | |
DFS Detection Threshold | Yes | Not required |
Channel Closing Transmission Time | Yes | Yes |
Channel Move Time | Yes | Yes |
U-NII Detection Bandwidth | Yes | Not required |
Additional Requirements for Devices with Multiple Bandwidth Modes | Master Device or Client with Radar Detection | Client Without Radar Detection |
U-NII Detection Bandwidth | All BW modes must be tested | Not required |
Statistical Performance Check | All BW modes must be tested | Not required |
Channel Closing Transmission Time | Test using widest BW mode available | Test using the widest BW mode available for the link |
Channel Move Time | Test using widest BW mode available | Test using the widest BW mode available for the link |
All other tests | Any single BW mode | Not required |
Note: Frequencies selected for statistical performance check should include several frequencies within the radar detection bandwidth and frequencies near the edge of the radar detection bandwidth. For 802.11 devices it is suggested to select frequencies in each of the bonded 20 MHz channels and the channel center frequency.
4.2. DFS Detection Thresholds
Table 3: DFS Detection Thresholds for Master Devices and Client Devices with Radar Detection
Maximum Transmit Power | Value (See Notes 1, 2, and 3) |
---|---|
EIRP ≥ 200 milliwatt | -64 dBm |
EIRP < 200 milliwatt and power spectral density < 10 dBm/MHz | -62 dBm |
EIRP < 200 milliwatt that do not meet the power spectral density requirement | -64 dBm |
Note 1: This is the level at the input of the receiver assuming a 0 dBi receive antenna.
Note 2: Throughout these test procedures an additional 1 dB has been added to the amplitude of the test transmission waveforms to account for variations in measurement equipment. This will ensure that the test signal is at or above the detection threshold level to trigger a DFS response.
Note 3: EIRP is based on the highest antenna gain. For MIMO devices refer to KDB Publication 662911 D01.
Table 4: DFS Response Requirement Values
Parameter | Value |
---|---|
Non-occupancy Period | Minimum 30 minutes |
Channel Availability Check Time | 60 seconds |
Channel Move Time | 10 seconds (See Note 1) |
Channel Closing Transmission Time | 200 milliseconds + an aggregate of 60 milliseconds over remaining 10 second period. (See Notes 1 and 2) |
U-NII Detection Bandwidth | Minimum 100% of the U-NII 99% transmission power bandwidth. (See Note 3) |
Note 1: Channel Move Time and the Channel Closing Transmission Time should be performed with Radar Type 0. The measurement timing begins at the end of the Radar Type 0 burst.
Note 2: The Channel Closing Transmission Time is comprised of 200 milliseconds starting at the beginning of the Channel Move Time plus any additional intermittent control signals required to facilitate a Channel move (an aggregate of 60 milliseconds) during the remainder of the 10 second period. The aggregate duration of control signals will not count quiet periods in between transmissions.
Note 3: During the U-NII Detection Bandwidth detection test, radar type 0 should be used. For each frequency step the minimum percentage of detection is 90 percent. Measurements are performed with no data traffic.
4.3. Radar Test Waveforms
Table 5: Short Pulse Radar Test Waveforms
Radar Type | Pulse Width (µsec) | PRI (µsec) | Number of Pulses | Minimum Percentage of Successful Detection | Minimum Number of Trials |
---|---|---|---|---|---|
0 | 1 | 1428 | 18 | See Note 1 | See Note 1 |
1 | 1 | Roundup | Test A: 15 unique PRI values randomly selected from the list of 23 PRI values in Table 5a | 60% | 30 |
Test B: 15 unique PRI values randomly selected within the range of 518-3066 µsec, with a minimum increment of 1 µsec, excluding PRI values selected in Test A | |||||
2 | 1-5 | 150-230 | 23-29 | ||
3 | 6-10 | 200-500 | 16-18 | ||
4 | 11-20 | 200-500 | 12-16 | 60% | 30 |
Aggregate (Radar Types 1-4) | 80% | 120 |
Note 1: Short Pulse Radar Type 0 should be used for the detection bandwidth test, channel move time, and channel closing time tests.
Table 5a: Pulse Repetition Intervals Values for Test A
Pulse Repetition Frequency Number | Pulse Repetition Frequency (Pulses Per Second) | Pulse Repetition Interval (Microseconds) |
---|---|---|
1 | 1930.5 | 518 |
2 | 1858.7 | 538 |
3 | 1792.1 | 558 |
4 | 1730.1 | 578 |
5 | 1672.2 | 598 |
6 | 1618.1 | 618 |
7 | 1567.4 | 638 |
8 | 1519.8 | 658 |
9 | 1474.9 | 678 |
10 | 1432.7 | 698 |
11 | 1392.8 | 718 |
12 | 1355 | 738 |
13 | 1319.3 | 758 |
14 | 1285.3 | 778 |
15 | 1253.1 | 798 |
16 | 1222.5 | 818 |
17 | 1193.3 | 838 |
18 | 1165.6 | 858 |
19 | 1139 | 878 |
20 | 1113.6 | 898 |
21 | 1089.3 | 918 |
22 | 1066.1 | 938 |
23 | 326.2 | 3066 |
The aggregate is the average of the percentage of successful detections of Short Pulse Radar Types 1-4. For example, the following table indicates how to compute the aggregate of percentage of successful detections.
Radar Type | Number of Trials | Number of Successful Detections | Minimum Percentage of Successful Detection |
---|---|---|---|
1 | 35 | 29 | 82.9% |
2 | 30 | 18 | 60% |
3 | 30 | 27 | 90% |
4 | 50 | 44 | 88% |
Aggregate (82.9% + 60% + 90% + 88%)/4 = 80.2% |
Table 6: Long Pulse Radar Test Waveform
Radar Type | Pulse Width (µsec) | Chirp Width (MHz) | PRI (µsec) | Number of Pulses per Burst | Number of Bursts | Minimum Percentage of Successful Detection | Minimum Number of Trials |
---|---|---|---|---|---|---|---|
5 | 50-100 | 5-20 | 1000-2000 | 1-3 | 8-20 | 80% | 30 |
The parameters for this waveform are randomly chosen. Thirty unique waveforms are required for the Long Pulse Radar Type waveforms. If more than 30 waveforms are used for the Long Pulse Radar Type waveforms, then each additional waveform must also be unique and not repeated from the previous waveforms.
Table 7: Frequency Hopping Radar Test Waveform
Radar Type | Pulse Width (µsec) | PRI (µsec) | Pulses per Hop | Hopping Rate (kHz) | Hopping Sequence Length (msec) | Minimum Percentage of Successful Detection | Minimum Number of Trials |
---|---|---|---|---|---|---|---|
6 | 1 | 333 | 9 | 0.333 | 300 | 70% | 30 |
For the Frequency Hopping Radar Type, the same Burst parameters are used for each waveform. The hopping sequence is different for each waveform and a 100-length segment is selected from the hopping sequence defined by the following algorithm: The first frequency in a hopping sequence is selected randomly from the group of 475 integer frequencies from 5250 5724 MHz. Next, the frequency that was just chosen is removed from the group and a frequency is randomly selected from the remaining 474 frequencies in the group. This process continues until all 475 frequencies are chosen for the set. For selection of a random frequency, the frequencies remaining within the group are always treated as equally likely.
4.4. Test Set-ups
The tests were conducted using N7607C Signal Studio V2.2.0.0. Channel loading was based on IP.
Setup for Master with Injection at the Master
This setup involves injecting radar test waveforms into the Master device. A Radar Test Signal Generator is connected via attenuators and splitters to the UUT (Master) and a Client device. A Spectrum Analyzer monitors the output. The diagram shows signal paths and attenuation levels (e.g., ATT 10 dB, ATT 30 dB).
Setup for Client with Injection at the Master
In this configuration, the radar test waveforms are injected into the Master device, while the UUT operates as a Client. Similar to the Master injection setup, it uses a Radar Test Signal Generator, attenuators, splitters, the UUT (Client), a Master device, and a Spectrum Analyzer.
Setup for Client with Injection at the Client
This setup involves injecting radar test waveforms directly into the Client device (UUT). It includes a Radar Test Signal Generator, attenuators, splitters, a Master device, the UUT (Client), and a Spectrum Analyzer. The signal path is configured to deliver the radar waveform to the client.
5. Test Cases
5.1. DFS Detection Thresholds
Ambient Condition
Temperature | 15C ~ 35C |
Relative humidity | 20% ~ 80% |
Pressure | 86 kPa ~ 106 kPa |
Methods of Measurement
Testing was performed with the device operating as a Client with injection at the Master. For a detection threshold level of -64dBm, the required signal strength at the EUT antenna location was -64dBm. The tested level was lower than the required level, indicating a margin to the limit.
Frequency of Calibration
Bandwidth | Central Frequency |
---|---|
802.11ac 20MHz | 5300MHz |
5500MHz | |
802.11ac 40MHz | 5270MHz |
5550MHz | |
802.11ac 80MHz | 5290MHz |
5610MHz |
Calibration Result
Refer to the section 6.1 of this report for test data.
5.2. U-NII Detection Bandwidth
Ambient Condition
Temperature | 15C ~ 35C |
Relative humidity | 20% ~ 80% |
Pressure | 86 kPa ~ 106 kPa |
Methods of Measurement
The procedure involves adjusting equipment to produce radar bursts (Short Pulse Radar Types 0-4) at the EUT's operating channel center frequency. The EUT is set up as a standalone device without traffic. Radar bursts are generated, and the UUT's response is noted over at least 10 trials. The EUT must detect the radar waveform within the DFS band according to the U-NII Detection Bandwidth criterion. For channels where bandwidth exceeds the DFS band edge, specific channels are selected. If not possible, testing is done to the DFS band edge. The radar frequency is stepped up and down in 5 MHz increments (and 1 MHz for fine-tuning) to find the highest frequency (FH) and lowest frequency (FL) where detection meets the criterion. The U-NII Detection Bandwidth is calculated as FH - FL. This bandwidth must meet the criterion in Table 4, ensuring the EUT can detect radar waveforms across the significant energy spectrum.
Limits: Minimum 100% of the U-NII 99% transmission power bandwidth. Radar type 0 is used for detection. Minimum 90% detection rate per frequency step.
Measurement Uncertainty: Assessed at 95% confidence level, k=2, U=0.44 dB.
Test Results: Refer to section 6.2 of this report for test data.
5.3. Channel Availability Check Time
Ambient Condition
Temperature | 15C ~ 35C |
Relative humidity | 20% ~ 80% |
Pressure | 86 kPa ~ 106 kPa |
Methods of Measurement
Initial Channel Availability Check Time: The U-NII device is powered on and instructed to operate on a U-NII channel with DFS functions. A spectrum analyzer is set to zero span mode to monitor the channel for 2.5 minutes after power-on. The EUT must not transmit any beacon or data transmissions until at least 1 minute after the power-on cycle completion. Transmission on the channel is then confirmed.
Radar Burst at the Beginning/End of the Channel Availability Check Time: This procedure verifies successful radar detection and avoidance of operation on the channel when a radar burst occurs at the beginning or end of the Channel Availability Check Time. The EUT is powered on, and a radar burst (Short Pulse Radar Types 0-4) is injected with a level equal to DFS Detection Threshold + 1 dB. The EUT's response (detection and subsequent non-transmission) is observed for 2.5 minutes after the burst. The Channel Availability Check results are recorded.
Timing Diagram Description: The diagrams illustrate the timing sequence for radar testing. Key events include Power-Up (Tpower_up), Channel Availability Check (Tch_avail_check), Injected Radar Burst, Radar Detection, and Transmissions on initial/new channels. The diagrams show how the radar burst timing relates to the channel availability check period.
Limits: Initial Channel Availability Check Time: 60s
Measurement Uncertainty: Assessed at 95% confidence level, k=1.96.
Test Results: Refer to section 6.3 of this report for test data.
5.4. Channel Move Time, Channel Closing Transmission Time and Non-Occupancy Period
Ambient Condition
Temperature | 15C ~ 35C |
Relative humidity | 20% ~ 80% |
Pressure | 86 kPa ~ 106 kPa |
Methods of Measurement
These tests verify DFS parameters during In-Service Monitoring. A radar burst (Radar Type 0) at DFS Detection Threshold + 1dB is generated on an operating channel. The EUT's response is observed for Channel Move Time, Channel Closing Transmission Time, and Non-Occupancy Period. One frequency is chosen from the U-NII-2A or U-NII-2C bands, ensuring control signals are present. The EUT operates as either a Master or Client device, associating with the appropriate counterpart. For conducted tests, the radar generator connects to the Master device; for radiated tests, it is directed towards the Master. Channel loading is streamed from Master to Client. After the radar burst, transmissions are observed for over 10 seconds (Channel Move Time) and the Channel Move Time and Channel Closing Transmission Time are recorded if radar detection occurs. For Master devices, monitoring continues for over 30 minutes to ensure no resumption of transmissions. If the EUT is a Client, steps 1-6 are performed.
Figure 17 Description: This figure illustrates the timing for Channel Closing Transmission Time and Channel Closing Time. It shows the UUT transmissions relative to the injected radar burst, indicating the time intervals for Channel Move Time (Tchannel_move_time) and Non-Occupancy Period (Tnon-occupancy).
Limits
Parameter | Limit |
---|---|
Channel Move Time | ≤10s |
Channel Closing Transmission Time | ≤200ms + 60ms (over remaining 10s period) |
Non-Occupancy Period | ≥30min |
Note 1: Channel Move Time and Channel Closing Transmission Time performed with Radar Type 0. Timing begins at the end of the Radar Type 0 burst.
Note 2: Channel Closing Transmission Time includes 200ms plus an aggregate of 60ms for control signals during the 10s period.
Measurement Uncertainty: Assessed at 95% confidence level, k=1.96, U=2.69 dB.
Test Results: Refer to section 6.4 of this report for test data.
5.5. Statistical Performance Check
Ambient Condition
Temperature | 15C ~ 35C |
Relative humidity | 20% ~ 80% |
Pressure | 86 kPa ~ 106 kPa |
Methods of Measurement
This test determines the minimum percentage of successful detection for various radar types (Tables 5-7) when a radar burst at DFS Detection Threshold + 1dB is generated on the operating channel. The procedure is similar to that for Channel Move Time, involving EUT association as Master or Client, radar waveform generation, and observation of EUT transmissions. Specific durations are observed for Radar Type 0 (>10 seconds) and Long Pulse Radar Type 5 (>22 seconds) to ensure detection occurs. If the EUT is a Client, steps 1-6 are performed.
Limits
Radar Type | Minimum Percentage of Successful Detection | Minimum Number of Trials |
---|---|---|
1 | 60% | 30 |
2 | 60% | 30 |
3 | 60% | 30 |
4 | 60% | 30 |
Aggregate (Radar Types 1-4) | 80% | 120 |
5 | 80% | 30 |
6 | 70% | 30 |
Measurement Uncertainty: Assessed at 95% confidence level, k=1.96, U=2.69 dB.
Test Results: Refer to section 6.5 of this report for test data.
6. Test Results
6.1. DFS Detection Thresholds
The following spectrum analyzer plots (Pages 28-33) illustrate the DFS Detection Thresholds for Radar Types 0, 1A, 1B, 2, 3, and 4 across various central frequencies (5270 MHz, 5290 MHz, 5300 MHz, 5500 MHz, 5550 MHz, 5610 MHz). Each plot displays the signal trace with a marker indicating the measured detection level. For Radar Type 0, the measured levels are consistently around -63 dBm to -64 dBm, meeting the specified detection threshold of -64 dBm and indicating compliance.
6.2. U-NII Detection Bandwidth
Refer to section 5.2 for the test methodology and limits. Test data is provided in section 6.2.
6.3. Channel Availability Check Time
Refer to section 5.3 for the test methodology and limits. Test data is provided in section 6.3.
6.4. Channel Move Time, Channel Closing Transmission Time and Non-Occupancy Period
Refer to section 5.4 for the test methodology and limits. Test data is provided in section 6.4.
6.5. Statistical Performance Check
Refer to section 5.5 for the test methodology and limits. Test data is provided in section 6.5.