hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
2.2M
|
|---|---|---|---|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.2.2.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 6.4.4 and test tolerance in Table C.1.2-1 of the present document. Table 6.1.2.2.4-1: Carrier leakage requirement Parameters Relative limit (dBc) Test Tolerance 0 dBm β€ Output power -25 Table C.1.2-1 -30 dBm β€ Output power < 0 dBm -20 -40 dBm β€ Output power < -30 dBm -10 6.1.2.3 Error vector magnitude 6.1.2.3.1 Test purpose To verify the EUT transmitter modulation quality in terms of error vector magnitude. The Error Vector Magnitude (EVM) is a measure of the difference between the ideal reference waveform and the measured waveform. The EVM result is defined after the receiver FFT as the square root of the ratio of the mean error vector power to the mean reference power expressed as a percentage as specified in ETSI TS 103 636-2 [1], clause 6.4.2. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 22
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.2.3.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.2.3.3 Test description
|
6.1.2.3.3.1 Initial conditions Table 6.1.2.3.3.1-1: Initial conditions for EVM tests Environment as specified in clause 4.1 Normal Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Lowest, Highest Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length and maximum packet length supported by the EUT, Table G.2.2-6 Transmit powers All transmit powers defined in ETSI TS 103 636-4 [3], Table 6.2.1-3a or 6.2.1-3b according to the EUT power class, Table G.2.1-3 Modulation and coding schemes All MCS supported, Table G.2.2-2 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-5. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) The SS sets the EUT to clause F.5.3 Transmit loop mode operation. The SS may set the EUT to transmit without cover sequence according to clause 5.2. 6.1.2.3.3.2 Test procedure 1) The EUT periodically transmits packets to the SS. 2) TS measures the EVM of the EUT transmission according to ETSI TS 103 636-2 [1], clause 6.4.2 against the limit in Table 6.1.2.3.4-1. 3) When specified transmission duration expires EUT sends loop report.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.2.3.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 6.4.2 and test tolerance in Table C.1.2-1 of the present document. Minimum requirement is defined for RMS average of basic EVM measurements of 20 consecutive 2 subslot packet transmissions with at least two subslot guard interval in between them. Table 6.1.2.3.4-1: Error Vector Magnitude (%) requirement Modulation Test limit Test Tolerance QPSK or BPSK 17,5 % Table C.1.2-1 16-QAM 12,5 % 64-QAM 8 % 6.1.2.4 Transmitter spectrum flatness 6.1.2.4.1 Test purpose Test purpose is to verify the EUT transmitter modulation quality in terms of transmit passband spectral flatness. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 23 The zero-forcing equalizer correction applied in the EVM measurement process measures transmitter spectrum flatness, and it is defined in terms of the maximum peak-to-peak (p-p) ripple of the equalizer coefficients (dB) across the transmission bandwidth . The transmitter spectrum flatness requirement does not limit the correction applied to the signal in the EVM measurement process but for the EVM result to be valid, the equalizer correction that was applied shall meet the EVM equalizer spectrum flatness minimum requirements.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.2.4.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.2.4.3 Test description
|
6.1.2.4.3.1 Initial conditions Table 6.1.2.4.3.1-1: Initial conditions for transmitter spectral flatness Environment as specified in clause 4.1 Normal Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Lowest, Highest Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length and maximum packet length supported by the EUT, Table G.2.2-6 Transmit powers All transmit powers defined in ETSI TS 103 636-4 [3], Table 6.2.1-3a or 6.2.1-3b according to the EUT power class, Table G.2.1-3 Modulation and coding schemes All MCS supported, Table G.2.2-2 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-5. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) The SS sets the EUT to clause F.5.3 Transmit loop mode operation. The SS may set the EUT to transmit without cover sequence according to clause 5.2. 6.1.2.4.3.2 Test procedure 1) The EUT periodically transmits packets to the SS. 2) TS measures the transmitter spectrum flatness against the requirement in Table 6.1.2.4.4-1. 3) When specified transmission duration expires EUT sends loop report.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.2.4.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 6.4.3 and the test tolerance is defined in Table C.1.2-1 of the present document. Table 6.1.2.4.4-1: Transmitter spectrum flatness requirement Test limit Test Tolerance 4 dB (peak-to-peak) Table C.1.2-1 ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 24 6.1.3 Spectrum emissions 6.1.3.1 Occupied bandwidth 6.1.3.1.1 Test purpose To verify the EUT transmitter occupied channel bandwidth relative to nominal bandwidth for all bandwidth configurations is within specific limits.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.3.1.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.3.1.3 Test description
|
6.1.3.1.3.1 Initial conditions Table 6.1.3.1.3.1-1: Initial conditions for occupied bandwidth tests Environment as specified in clause 4.1 Normal, TL/VL, TL/VH, TH/VL, TH/VH Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Lowest, Highest Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length and maximum packet length supported by the EUT, Table G.2.2-6 Transmit powers Maximum transmission power supported by the EUT, Table G.2.1-3 Modulation and coding schemes All MCS supported, Table G.2.2-2 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-5. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) The SS sets the EUT to clause F.5.3 Transmit loop mode operation. 6.1.3.1.3.2 Test procedure 1) The EUT periodically transmits packets to the SS. 2) TS measures the occupied bandwidth in steps a) to e) against the limit defined in Table 6.1.3.1.4-1: a) Measure the power spectrum distribution within two times or more range over the requirement for Occupied Bandwidth specification centring on the current carrier frequency. The characteristic of the filter shall be approximately Gaussian (typical spectrum analyser filter). Other methods to measure the power spectrum distribution are allowed. Only the active transmission part of the transmission packet without any transient periods is used in the measurement. b) Calculate the total power within the range of all frequencies measured in 'a)' and save this value as "Total Power". c) Sum up the power upward from the lower boundary of the measured frequency range in 'a)' and seek the limit frequency point by which this sum becomes 0,5 % of "Total Power" and save this point as "Lower Frequency". ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 25 d) Sum up the power downward from the upper boundary of the measured frequency range in 'a)' and seek the limit frequency point by which this sum becomes 0,5 % of "Total Power" and save this point as "Upper Frequency". e) Calculate the difference ("Upper Frequency" - "Lower Frequency" = "Occupied Bandwidth") between two limit frequencies obtained in 'd)' and 'c)'. 3) When specified transmission duration expires EUT sends loop report.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.3.1.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clauses 6.5.2 and 5.3.2. Occupied channel bandwidth is a measure of the bandwidth containing 99 % of the total integrated mean power of the transmitted spectrum on the assigned channel. Occupied channel bandwidth shall not exceed nominal bandwidth. Table 6.1.3.1.4-1: Occupied channel bandwidth limits requirement Nominal channel bandwidth Test limit < 6.1.3.2 Out of band emissions 6.1.3.2.1 Test purpose To verify that the power of any EUT emission shall not exceed specified level for the specified channel bandwidth.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.3.2.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.3.2.3 Test description
|
6.1.3.2.3.1 Initial conditions Table 6.1.3.2.3.1-1: Initial conditions for out of band emission tests Environment as specified in clause 4.1 Normal, TL/VL, TL/VH, TH/VL, TH/VH Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Lowest, Highest Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length and maximum packet length supported by the EUT, Table G.2.2-6 Transmit powers Maximum transmission power supported by the EUT, Table G.2.1-3 Modulation and coding schemes All MCS supported, Table G.2.2-2 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-5. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) The SS sets the EUT to clause F.5.3 Transmit loop mode operation. 6.1.3.2.3.2 Test procedure 1) The EUT periodically transmits packets to the SS. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 26 2) TS measures the spectrum emission mask compliance according to Tables 6.1.3.2.4-1 and 6.1.3.2.4-2. The active transmission part of the transmission packet including the transient periods is used in the measurement. 3) When specified transmission duration expires EUT sends loop report.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.3.2.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 6.5.3. Test measurement uncertainty is defined in Table C.1.2-1 of the present document. The spectrum emission mask applies to frequencies Ξ starting from the Β± edge (from + /2 or from β /2) of the assigned channel. For frequencies offset greater than Ξ as specified in ETSI TS 103 636-2 [1], Table 6.5.3-2, the spurious requirements in ETSI TS 103 636-2 [1], clause 6.5.4 are applicable. β’ is the carrier centre frequency. β’ is the nominal channel bandwidth. β’ is the transmission bandwidth. β’ is the guard band ( β ) between the closest subcarriers of the adjacent channels. NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. Table 6.1.3.2.4-1: Spectrum emission mask requirement for 30 kHz measurement bandwidth Limit (dBm) Test Tolerance Measurement bandwidth (MBW) / β₯ 1 MHz / < 1 MHz - 0 to /2 β10 β10 10( /1,728) Table C.1.2-1 30 kHz - β0 to β /2 β10 β10 10( /1,728) 30 kHz 0 to 1 MHz /2 to 1 MHz β21 β10 10( /1,728) 30 kHz 0 to β1 MHz β /2 to β1 MHz β21 β10 10( /1,728) 30 kHz NOTE 1: The first centre frequency for a 30 kHz measurement filter is at Ξ= 0,015 MHz, which is /2 + 0,015 MHz from the carrier centre frequency. NOTE 2: The first centre frequency for a 30 kHz measurement filter in the range from /2 to 1 MHz is at Ξ = /2 + 0,015 MHz, which is /2 + /2 + 0,015 MHz from the carrier centre frequency. NOTE 3: Symmetrically similarly as in note 1 and note 2 in negative Ξ frequencies. Table 6.1.3.2.4-2: Spectrum emission mask requirement for 1MHz measurement bandwidth Limit (dBm) Test Tolerance Measurement bandwidth (MBW) β€ , > , 1 MHz to β10 β10 β10 10( /6,912) Table C.1.2-1 1 MHz -1 MHz to β β10 β10 β10 10( /6,912) 1 MHz to 2 β25 β25 β10 10( /6,912) 1 MHz β to β2 β25 β25 β10 10( /6,912) 1 MHz NOTE 1: The first centre frequency for a 1 MHz measurement filter in the range 1 MHz to is at Ξ = 1,5 MHz. NOTE 2: The first centre frequency for a 1 MHz measurement filter in the range to 2 at Ξ= + 0,5 MHz. NOTE 3: Symmetrically similarly as in note 1 and note 2 in negative Ξ frequencies. NOTE: As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth to obtain the equivalent noise bandwidth of the measurement bandwidth. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 27 6.1.3.3 Adjacent channel leakage ratio 6.1.3.3.1 Test purpose To verify that EUT transmitter does not cause unacceptable interference to adjacent channels in terms of Adjacent Channel Leakage power Ratio (ACLR).
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.3.3.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.3.3.3 Test description
|
6.1.3.3.3.1 Initial conditions Table 6.1.3.3.3.1-1: Initial conditions for ACLR tests Environment as specified in clause 4.1 Normal, TL/VL, TL/VH, TH/VL, TH/VH Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Lowest, Highest Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length and maximum packet length supported by the EUT, Table G.2.2-6 Transmit powers Maximum transmission power supported by the EUT, Table G.2.1-3 Modulation and coding schemes All MCS supported, Table G.2.2-2 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-5. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) The SS sets the EUT to clause F.5.3 Transmit loop mode operation. 6.1.3.3.3.2 Test procedure 1) The EUT periodically transmits packets to the SS. 2) TS measures the ACLR compliance according to Table 6.1.3.3.4-1. The active transmission part of the transmission packet including the transient periods is used in the measurement: a) ACLR is measured with a square window on the transmission bandwidth of the adjacent channel. A DFT of the transmission signal is taken and the mean energy of the appropriate bins used to calculate the adjacent channel powers and compared to the mean energy of the appropriate bins on the transmission bandwidth of the desired transmission channel. ACLR is measured independently both on the on both lower and upper side adjacent channels. 3) When specified transmission duration expires EUT sends loop report.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.3.3.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clauses 6.5.5. Test measurement uncertainty is defined in Table C.1.2-1 of the present document. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 28 Table 6.1.3.3.4-1: Adjacent channel leakage ratio requirement Limit (dBc) Test Tolerance -30.0 Table C.1.2-1 6.1.3.4 Spurious emissions 6.1.3.4.1 Test purpose To verify that the EUT transmitter does not cause unacceptable interference to other channels or other systems in terms of transmitter spurious emissions.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.3.4.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.3.4.3 Test description
|
6.1.3.4.3.1 Initial conditions Table 6.1.3.4.3.1-1: Initial conditions for transmitter spurious emissions tests Environment as specified in clause 4.1 Normal Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Lowest, Highest Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length and maximum packet length supported by the EUT, Table G.2.2-6 Transmit powers Maximum transmission power supported by the EUT, Table G.2.1-3 Modulation and coding schemes All MCS supported, Table G.2.2-2 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-5. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) The SS sets the EUT to clause F.5.3 Transmit loop mode operation. 6.1.3.4.3.2 Test procedure 1) The EUT periodically transmits packets to the SS. 2) TS measures the spurious emissions. The active transmission part of the transmission packet including the transient periods is used in the measurement: a) Measure the power of the transmitted signal with a measurement filter of bandwidths according to Table 6.1.3.4.4-1. The centre frequency of the filter shall be stepped in contiguous steps according measurement bandwidth. The measured power shall be verified for each step. 3) When specified transmission duration expires EUT sends loop report.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.1.3.4.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 6.5.4. Test measurement uncertainty is defined in Table C.1.2-1 of the present document. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 29 Table 6.1.3.4.4-1: Transmitter spurious emissions requirement Frequency Range Maximum Level Test Tolerance Measurement bandwidth (MBW) 9 kHz β€ f < 150 kHz -36 dBm Table C.1.2-1 1 kHz 150 kHz β€ f < 30 MHz -36 dBm 10 kHz 30 MHz β€ f < 1 000 MHz -36 dBm 100 kHz 1 GHz β€ f < 12,75 GHz -30 dBm 1 MHz 12,75 GHz β€ f < 5th harmonic of the upper frequency edge in GHz -30 dBm 1 MHz NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. 6.2 Receiver tests 6.2.1 Receiver dynamic range and selectivity 6.2.1.1 Sensitivity 6.2.1.1.1 Test purpose To verify the EUT's ability to receive data with a given average throughput for a specified reference measurement channel, under conditions of low signal level, ideal propagation and no added noise.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.1.1.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.1.1.3 Test description
|
6.2.1.1.3.1 Initial conditions Table 6.2.1.1.3.1-1: Initial conditions for sensitivity testing Environment as specified in clause 4.1 Normal, TL/VL, TL/VH, TH/VL, TH/VH Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Lowest, Highest Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length, Table G.2.2-6 Modulation and coding schemes MCS1, Table G.2.2-2 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-5. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) The SS sets the EUT to clause F.5.4 Receive loop mode operation. 6.2.1.1.3.2 Test procedure 1) The SS periodically transmits packets. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 30 2) The EUT receives packets and responds to the SS. 3) SS decreases the received signal strength for the EUT to REFSENS value defined in Table 6.2.1.1.4-1. 4) SS observes the ACK/NACK feedback from the EUT and measures the test pass/fail criteria according to Annex B. 5) SS deactivates clause F.5.4 Receive loop.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.1.1.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 7.2 and test tolerance in Table C.1.3-1. Table 6.2.1.1.4-1: Receiver sensitivity requirement Bands REFSENS Test Tolerance 1 - 12 and 22 β99,7 β10 10( /1,728) dBm Table C.1.3-1 13 - 15, 20 and 21 β97,7 β10 10( /1,728) dBm 16 - 19 β95,7 β10 10( /1,728) dBm 6.2.1.2 Maximum input level 6.2.1.2.1 Test purpose To verify the EUT's ability to receive data with a given average throughput for a specified reference measurement channel, under conditions of low signal level, ideal propagation and no added noise with maximum input signal at the EUT antenna port.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.1.2.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.1.2.3 Test description
|
6.2.1.2.3.1 Initial conditions Table 6.2.1.2.3.1-1: Initial conditions to maximum input level tests Environment as specified in clause 4.1 Normal Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Mid-range Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length, Table G.2.2-6 Modulation and coding schemes MCS1, Table G.2.2-2 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-5. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) The SS sets the EUT to clause F.5.4 Receive loop mode operation. 6.2.1.2.3.2 Test procedure 1) The SS periodically transmits packets. 2) The EUT receives packets and responds to the SS. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 31 3) Increase the received signal strength for the EUT to the value defined in Table 6.2.1.2.4-1. 4) The SS observes the ACK/NACK feedback from the EUT and measures the test pass/fail criteria according to Annex B. 5) SS deactivates clause F.5.4 Receive loop.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.1.2.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 7.3 and test tolerance in Table C.1.3-1. Table 6.2.1.2.4-1: Maximum input level requirement Limit Test Tolerance β20 dBm Table C.1.3-1 6.2.1.3 Adjacent channel selectivity 6.2.1.3.1 Test purpose To verify the EUT's ability to receive data with a given average throughput for a specified reference measurement channel, in the presence of an adjacent channel signal at a given frequency offset from the centre frequency of the assigned channel, under conditions of ideal propagation and no added noise, thus Adjacent Channel Selectivity (ACS).
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.1.3.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.1.3.3 Test description
|
6.2.1.3.3.1 Initial conditions Table 6.2.1.3.3.1-1: Initial conditions for ACS tests Environment as specified in clause 4.1 Normal Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Mid-range Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length, Table G.2.2-6 Modulation and coding schemes MCS1, Table G.2.2-2 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-6. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) Adjacent channel interference signal shall have identical signal characteristics (e.g. transmission bandwidth , subcarrier width and Fourier transform size) as wanted signal. Interference signal shall have QPSK modulated random data on all occupied subcarriers and the transmit signal shall be transmit pulse-shaped with square root raised cosine filter with roll-off 0,125 as defined in ETSI TS 103 636-2 [1]. 6) The SS sets the EUT to clause F.5.4 Receive loop mode operation. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 32 6.2.1.3.3.2 Test procedure Test procedure is conducted independently both on the lower and upper side adjacent channels: 1) The SS periodically transmits packets. 2) The EUT receives packets and responds to the SS. 3) Set the desired signal strength for the EUT to the value of Table 6.2.1.3.4-1. 4) Increase the adjacent channel interferer signal strength for the EUT to the value defined in Table 6.2.1.3.4-1. 5) The SS observes the ACK/NACK feedback from the EUT and measures the test pass/fail criteria according to Annex B. 6) SS deactivates clause F.5.4 Receive loop.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.1.3.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 7.4 and test tolerance in Table C.1.3-1. β’ is the nominal channel bandwidth. β’ REFSENS is defined in Table 6.2.1.1.4-1. Table 6.2.1.3.4-1: Adjacent channel selectivity requirement RX parameter Value Test Tolerance Desired signal input level REFSENS + 14 dB Table C.1.3-1 Interferer power REFSENS + 39 dB Interferer bandwidth Interferer frequency offset Β± NOTE: The interferer offset is from own signal centre frequency to interferer centre frequency. 6.2.2 Blocking characteristics 6.2.2.1 In-band blocking 6.2.2.1.1 Test purpose To verify the EUT's ability to receive data with an unwanted interfering signal falling into the range from 15 MHz below to 15 MHz above the RD receive band, at which the relative throughput shall meet or exceed the requirement for the specified measurement channels.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.2.1.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.2.1.3 Test description
|
6.2.2.1.3.1 Initial conditions Table 6.2.2.1.3.1-1: Initial conditions for in-band blocking tests Environment as specified in clause 4.1 Normal Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Mid-range Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length, Table G.2.2-6 Modulation and coding schemes MCS1, Table G.2.2-2 ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 33 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-6. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) The SS sets the EUT to clause F.5.4 Receive loop mode operation. 6.2.2.1.3.2 Test procedure Test procedure is conducted independently for all interferer integer frequency offsets for which maximum interference offset defined in Table 6.2.2.1.4-1 applies: 1) The SS periodically transmits packets. 2) The EUT receives packets and responds to the SS. 3) Set the desired signal strength for the EUT to the value of Table 6.2.2.1.4-1. 4) Increase the interferer signal strength for the EUT to the value defined in Table 6.2.2.1.4-1. 5) The SS observes the ACK/NACK feedback from the EUT and measures the test pass/fail criteria according to Annex B. 6) SS deactivates clause F.5.4 Receive loop.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.2.1.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 7.5.2 and test tolerance in Table C.1.3-1: β’ is the nominal channel bandwidth. β’ Frequency of band low edge. β’ Frequency of band high edge. β’ REFSENS is defined in Table 6.2.1.1.4-1. Table 6.2.2.1.4-1: In-band blocking requirement RX parameter Value Test Tolerance Desired signal input level REFSENS + 6 dB Table C.1.3-1 Interferer power REFSENS + 52 dB Interferer bandwidth Interferer frequency offset Β± Γ , β₯2 Maximum interferer frequency offset β 15 MHz + /2, and + 15 MHz) - /2 NOTE 1: The interferer signal characteristic is same as the wanted signal modulated with data. NOTE 2: The interferer offset is from own signal centre frequency to interferer centre frequency. 6.2.2.2 Out of band blocking 6.2.2.2.1 Test purpose To verify the EUT's ability to receive data with an unwanted CW interfering signal falling more than 15 MHz below or above the RD receive band, at which a given average throughput shall meet or exceed the requirement for the specified measurement channels. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 34
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.2.2.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.2.2.3 Test description
|
6.2.2.2.3.1 Initial conditions Table 6.2.2.2.3.1-1: Initial conditions for out of band blocking tests Environment as specified in clause 4.1 Normal Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 One frequency chosen arbitrarily from low or high range Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length, Table G.2.2-6 Modulation and coding schemes MCS1, Table G.2.2-2 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A-6. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) The SS sets the EUT to clause F.5.4 Receive loop mode operation. 6.2.2.2.3.2 Test procedure Test procedure is conducted for the blocker frequency ranges defined in Table 6.2.3.1.4-1 with CW interferer frequency step size of 1 MHz: 1) The SS periodically transmits packets. 2) The EUT receives packets and responds to the SS. 3) Set the desired signal strength for the EUT to the value of Table 6.2.2.2.4-1. 4) Increase the CW interferer signal strength for the EUT to the value defined in Table 6.2.2.2.4-1. 5) The SS observes the ACK/NACK feedback from the EUT and measures the test pass/fail criteria according to Annex B. 6) SS deactivates clause F.5.4 Receive loop.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.2.2.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 7.5.3 and test tolerance in Table C.1.3-1: β’ is the nominal channel bandwidth β’ Frequency of band low edge β’ Frequency of band high edge β’ is the interferer frequency β’ REFSENS is defined in Table 6.2.1.1.4-1 It is allowed to have a number of spurious response exceptions. These number of exceptions is a maximum of 24 or 8 Γ , MHz, whatever is greater depending on the nominal channel bandwidth . For these exceptions the requirement of ETSI TS 103 636-2 [1], clause 7.6 and spurious response conformance test of clause 6.2.2.3 applicable. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 35 Table 6.2.2.2.4-1: Out of band blocking requirement Range 1 Range 2 Range 3 Desired signal input level REFSENS + 6 dB REFSENS + 6 dB REFSENS + 6 dB Interferer frequency β 15 MHz to β 60 MHz β 60 MHz to β 85 MHz β 85 MHz to 1 MHz + 15 MHz to + 60 MHz + 60 MHz to + 85 MHz + 85 MHz to 12, 75 GHz Interferer power -44 dBm -30 dBm -15 dBm Test Tolerance Table C.1.3-1 Table C.1.3-1 Table C.1.3-1 6.2.2.3 Spurious response 6.2.2.3.1 Test purpose To verify the EUT's ability to receive data without exceeding a given degradation due to the presence of an unwanted CW interfering signal at any other frequency at which a response is obtained i.e. for which the out of band blocking limit as specified in clause 6.2.2.2 is not met.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.2.3.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.2.3.3 Test description
|
6.2.2.3.3.1 Initial conditions Table 6.2.2.3.3.1-1: Initial conditions for receive spurious response tests Environment as specified in clause 4.1 Same as for clause 6.2.2.2 Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Same as for clause 6.2.2.2 Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length, Table G.2.2-6 Modulation and coding schemes MCS1, Table G.2.2-2 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-6. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) The SS sets the EUT to clause F.5.4 Receive loop mode operation. 6.2.2.3.3.2 Test procedure Test procedure is conducted for the blocker frequency ranges defined in Table 6.2.3.1.4-1 with CW blocker signal step size of 1 MHz: 1) The SS periodically transmits packets. 2) The EUT receives packets and responds to the SS. 3) Set the desired signal strength for the EUT to the value of Table 6.2.2.2.4-1. 4) Increase the CW interferer signal strength for the EUT to the value defined in Table 6.2.2.2.4-1. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 36 5) The SS observes the ACK/NACK feedback from the EUT and measures the test pass/fail criteria according to Annex B. 6) SS deactivates clause F.5.4 Receive loop.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.2.3.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 7.6 and test tolerance in Table C.1.3-1. β’ is the nominal channel bandwidth. β’ is the interferer frequency Table 6.2.2.3.4-1: Spurious response requirement Test Tolerance Desired signal input level REFSENS + 6 dB Table C.1.3-1 Interferer frequency Spurious response frequencies detected in test of clause 6.2.2.2 Interferer power -44 dBm 6.2.3 Intermodulation characteristics 6.2.3.1 Wide band intermodulation 6.2.3.1.1 Test purpose To verify the EUT's ability to receive data with a given average throughput for a specified reference measurement channel, in the presence of two or more interfering signals which have a specific frequency relationship to the wanted signal, under conditions of ideal propagation and no added noise.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.3.1.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.3.1.3 Test description
|
6.2.3.1.3.1 Initial conditions Table 6.2.3.1.3.1-1: Initial conditions for wideband intermodulation tests Environment as specified in clause 4.1 Normal Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Mid-range Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length, Table G.2.2-6 Modulation and coding schemes MCS1, Table G.2.2-2 1) Connect the SS to the EUT antenna connectors as shown in Annex A Figure A.1-6. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 37 5) The SS sets the EUT to clause F.5.4 Receive loop mode operation. 6.2.3.1.3.2 Test procedure 1) The SS periodically transmits packets. 2) The EUT receives packets and responds to the SS. 3) Set the desired signal strength for the EUT to the value of Table 6.2.3.1.4-1. 4) Increase the CW interferer signal strength for the EUT to the value defined in Table 6.2.3.1.4-1. 5) Increase the modulated interferer signal strength for the EUT to the value defined in Table 6.2.3.1.4-1. 6) The SS observes the ACK/NACK feedback from the EUT and measures the test pass/fail criteria according to Annex B. 7) SS deactivates clause F.5.4 Receive loop.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.3.1.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 7.8 and test tolerance in Table C.1.3-1: β’ is the nominal channel bandwidth. β’ is the frequency of interferer 1, i.e. CW interferer. β’ is the frequency of interferer 2, i.e. modulated interferer. β’ is the power of interferer 1, i.e. CW interferer. β’ is the power of interferer 2, i.e. modulated interferer. Table 6.2.3.1.4-1: Wideband intermodulation requirement RX parameter Value Test Tolerance Desired signal input level REFSENS + 6 dB Table C.1.3-1 Interferer 1 (CW) power -46 dBm Interferer 2 (modulated) power -46 dBm Interferer 2 (modulated) bandwidth Interferer 1 (CW) frequency Β±2 Interferer 2 (modulated) frequency 2 Γ NOTE 1: The modulated interferer signal characteristic is same as the wanted signal modulated with data. NOTE 2: The interferer offset is from own signal centre frequency to interferer centre frequency. 6.2.4 Spectrum emissions 6.2.4.1 Spurious emissions 6.2.4.1.1 Test purpose To verify that the EUT does not cause unacceptable interference to other channels or other systems in terms of spurious emissions generated or amplified by the EUT receiver that appear at the EUT antenna connector.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.4.1.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 38
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.4.1.3 Test description
|
6.2.4.1.3.1 Initial conditions Table 6.2.4.1.3.1-1: Initial conditions for receiver spurious emissions Environment as specified in clause 4.1 Normal Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Lowest, Highest Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length, Table G.2.2-6 Modulation and coding schemes MCS1, Table G.2.2-2 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-5. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) The SS sets the EUT to clause F.4.4 Measurement Mode B. 6.2.4.1.3.2 Test procedure Measure the power with a measurement filter of bandwidths and centre frequencies according to Table 6.2.4.1.4-1 by repeating the steps 1-4 below. The centre frequency of the filter shall be stepped in contiguous steps according to measurement bandwidth: 1) Set measurement filter centre frequency. 2) The SS periodically transmits packets. 3) Measure the EUT spurious emissions. The emissions shall be measured during the period where the receiver is active. 4) SS deactivates clause F.4.4 Measurement Mode B.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.4.1.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 7.7 and test tolerance in Table C.1.3-1. Table 6.2.4.1.4-1: Receiver spurious emissions requirement Frequency band Measurement bandwidth (MBW) Maximum level Test Tolerance 30 MHz β€ f < 1 GHz 100 kHz -57 dBm Table C.1.3-1 1 GHz β€ f β€ 12,75 GHz 1 MHz -47 dBm 6.2.5 Receiver measurements 6.2.5.1 RSSI-1 measurement 6.2.5.1.1 Test purpose To verify the accuracy of EUT's RSSI-1 measurement. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 39
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.5.1.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.5.1.3 Test description
|
6.2.5.1.3.1 Initial conditions Table 6.2.5.1.3.1-1: Initial conditions for RSSI1 measurements Environment as specified in clause 4.1 Normal Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Mid-range Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Continuous transmission of any packet length greater than two subslots, Table G.2.2-6 Modulation and coding schemes MCS1, Table G.2.2-2 Test received signal strength From REFSENS to REFSENS + 70 dB with 1 dB steps 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-6. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) Set the EUT to clause F.4.3 Measurement Mode A. 6) Set the received signal strength according to Table 6.2.5.1.3.1-1. 6.2.5.1.3.2 Test procedure 1) The SS continuously transmits packets without any guard interval between the packets. 2) The EUT measures RSSI-1. 3) SS deactivates clause F.4.3 Measurement Mode A.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.5.1.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 7.7 and test tolerance in Table C.1.3-1. The SNR value reported in REPORT_MEASUREMENT MODE_A shall be compared against accuracy requirement. Factor in the noise floor contribution, the EUT declared typical Noise Figure, to the measurement result between REFSENS < RSSI-1 β€ REFSENS + 10 dB: β’ REFSENS is defined in Table 6.2.1.1.4-1. Table 6.2.5.1.4-1: RSSI-1 measurement accuracy requirement RSSI-1 measured power/dBm Accuracy in normal conditions Test Tolerance REFSENS < RSSI-1 β€ REFSENS + 10 dB Β±5,5 dB Table C.1.3-1 REFSENS + 10 dB < RSSI-1 β€ REFSENS + 60 dB Β±3,5 dB REFSENS + 60 dB < RSSI-1 β€ REFSENS + 70 dB Β±5,5 dB ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 40 6.2.5.2 RSSI-2 measurement 6.2.5.2.1 Test purpose To verify the accuracy of EUT's RSSI-2 measurement.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.5.2.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.5.2.3 Test description
|
6.2.5.2.3.1 Initial conditions Table 6.2.5.2.3.1-1: Initial conditions for RSSI-2 measurement Environment as specified in clause 4.1 Normal Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Mid-range Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length, Table G.2.2-6 Modulation and coding schemes MCS1, Table G.2.2-2 Test received signal strength From REFSENS to REFSENS + 70 dB with 1 dB steps 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-5. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) The SS sets the EUT to clause F.5.4 Receive loop mode operation. 6) Signal levels are set according to Table 6.2.5.2.3.1-1. 6.2.5.2.3.2 Test procedure 1) The SS periodically transmits packets. 2) The EUT receives packet and responds to the SS with RSSI-2 measurement report on each of the packets. 3) SS deactivates clause F.5.4 Receive loop.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.5.2.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 7.7 and test tolerance in Table C.1.3-1. The RSSI-2 value reported in REPORT_RX_LOOP_MODE shall be compared against accuracy requirement: β’ REFSENS is defined in Table 6.2.1.1.4-1. Table 6.2.5.2.4-1: RSSI-2 measurement accuracy requirement RSSI-1 measured power/dBm Accuracy in normal conditions Test Tolerance REFSENS < RSSI-2 β€ REFSENS + 10 dB Β±4 dB Table C.1.3-1 REFSENS + 10 dB < RSSI-2 β€ REFSENS + 60 dB Β±2 dB REFSENS + 60 dB < RSSI-2 β€ REFSENS + 70 dB Β±4 dB ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 41 6.2.5.3 SNR measurement 6.3.5.3.1 Test purpose To verify the accuracy of EUT's SNR measurement.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.5.3.2 Test applicability
|
This test case applies to all types of DECT-2020 NR release 1 RD and forward.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.5.3.3 Test description
|
6.2.5.3.3.1 Initial conditions Table 6.2.5.3.3.1-1: Initial conditions for SNR measurement tests Environment as specified in clause 4.1 Normal Operating bands All operating bands supported, Table G.2.1-1 Carrier frequencies within operating band as specified in clause 4.3.2 Mid-range Bandwidths and numerologies as specified in clause 4.3.2 All numerologies supported, Table G.2.2-1 Packet lengths Two subslot packet length, Table G.2.2-6 Modulation and coding schemes MCS1, Table G.2.2-2 Test SNR range From 5 dB to 25 dB with 1 dB steps. Apply White Gaussian Noise to achieve required SNR for Signal RSSI defined in the next row. Signal RSSI at EUT antenna connector β60 + 10 10( /1,728 ), where is the nominal channel bandwidth 1) Connect the SS to the EUT antenna connectors as shown in Annex A, Figure A.1-5. 2) Radio conditions are set according to clause 4.3.3. 3) Transmission packet parameters are set according to clause 4.3.4. 4) Signal levels are set according to clause 4.3.5. 5) The SS sets the EUT to clause F.5.4 Receive loop mode operation. 6) Signal levels are set according to Table 6.2.5.3.3.1-1. 6.2.5.3.3.2 Test procedure 1) The SS periodically transmits packets. 2) The EUT receives packet and responds to the SS with SNR measurement report on each of the packets. 3) SS deactivates clause F.5.4 Receive loop.
|
a50d0751fba9eb0fb9d16f7b15885dae
|
104 047-1
|
6.2.5.3.4 Test requirement
|
Normative requirement is specified in ETSI TS 103 636-2 [1], clause 7.7 and test tolerance in Table C.1.3-1. The SNR value reported in REPORT_RX_LOOP_MODE shall be compared against accuracy requirement. Table 6.2.5.3.4-1: SNR measurement accuracy requirement SNR range Accuracy in normal conditions Test Tolerance 5 dB < SNR β€ 25 dB Β±3 dB Table C.1.3-1 ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 42 Annex A (informative): Test System A.1 Introduction System Simulator (SS): A device or system, that is capable of generating simulated RD signalling and analysing EUT signalling responses on one or more RF channels, in order to create the required test environment for the EUT. It will also include the following capabilities: 1) Calibrated adjustment of transmission power level to match the received signal strength requirement for given test. 2) Measurement of throughput. 3) Measurement of signalling timing and delays. 4) Ability to simulate DECT-2020 NR signalling. Test System (TS): A combination of devices brought together into a system for the purpose of making one or more measurements on a EUT in accordance with the test case requirements. A test system may include one or more System Simulators if additional signalling is required for the test case. NOTE 1: The above terms are logical definitions to be used for the test methods description used in the present document. In practice, real devices or systems called 'System Simulators' may also include additional measurement capabilities or may only support those features required for the test cases they are designed to perform. NOTE 2: Components in the connection diagrams: The components in the connection diagrams represent ideal components. They are intended to display the wanted signal flow. They do not mandate real implementations. NOTE 3: An abstract test system for transmitter and receiver testing are depicted in Figures A.1-4, A.1-5 and A.1-6. An example realization of such test system is depicted in Figure A.1-10. In this figure a vector signal generator is used as a calibrated transmitter for the receiver testing. A companion device transmits the test commands of Annex F and receives the responses of EUT and delivers them to the test controller. A signal analyser can be used for transmission signal quality analysis. By replacing wired antenna connections with wireless transmissions between SS, EUT and signal analyser the same principle can be applied for radiated measurements. In another realization of the test system a dedicated system tester can encapsulate the complete test system. Connection: Each connection is displayed as a one- or two-sided arrow, showing the intended signal flow. In some cases, for some tests, some connections shown may not be necessary. Circulator: The signal, entering one port, is conducted to the adjacent port, indicated by the arrow. The attenuation among the above-mentioned ports is ideally 0 and the isolation among the other ports is ideally β. Figure A.1-1: Circulator symbol Equipment Under Test (EUT): A RD under test. Splitter: A splitter has one input and 2 or more outputs. The signal at the input is equally divided to the outputs. The attenuation from input to the outputs is ideally 0 and the isolation between the outputs is ideally β. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 43 Figure A.1-2: Splitter symbol Combiner: A combiner has one output and 2 or more inputs. The signals at the inputs are conducted to the output, all with the same, ideally 0 attenuation. The isolation between the inputs is ideally β. Figure A.1-3: Combiner symbol Switch: Contacts a sink (or source) alternatively to two or more sources (or sinks). Interference generator: Source or more sources capable of producing interference signal of desired characteristics in order to create the required test environment for the EUT. Co-channel and adjacent channel interferences are with similar signal characteristics as desired signal has, but with frequency offset as needed. Blocker signal is Continuous Wave (CW) signal at suitable frequency offset. Wideband interference is white noise. Transmission power levels of interference generators should be calibrated and individually adjustable for the test system to create desired input signal characteristics for the EUT. Fader: The fader has one input and one output. The MIMO fading channel is represented by several single faders (e.g. 8 in case of a MIMO antenna configuration 4x2). The correlation among the faders is described in ETSI TS 103 636 2 [1]. In some cases, for some tests, diagrams with fader(s) are referenced when no fading is required; in this case the fader(s) is omitted. Attenuator: Programmable or fixed signal attenuator Figure A.1-4: Basic connection for RX and TX tests Figure A.1-5: Connection for transmitter tests with additional spectrum analyser, vector signal analyser or power sensor ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 44 NOTE: Test setup can have more than one interference generator, and the interference generators may be of different type, such as co-channel interference, adjacent channel interference, CW or wideband interference. Figure A.1-6: Connection for receiver tests with interference NOTE: Each of the N transmitter outputs are split into M. For each of the M receiver inputs the N inputs are faded and added together. White Gaussian noise is added for each receiver antenna separately. Figure A.1-7: Generic N x M Fading Channel Model ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 45 NOTE: It is equivalent to use any of the EUT antennas in reverse direction. Transmit diversity and single antenna transmission as in Figure A.1-9 are subsets of this generic configuration. Figure A.1-8: Receiver testing connection N x M Fading channel Figure A.1-9: Fading channel connection for single antenna receiver testing ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 46 Figure A.1-10: An example realization of transmitter and receiver test setups of Figures A-4, A-5 and A-6 ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 47 Annex B (normative): Receiver testing pass/fail limits B.1 Statistical testing of receiver characteristics B.1.1 Description The test of receiver characteristics is twofold: 1) A signal or a combination of signals is offered to the RX port(s) of the EUT. 2) The ability of the EUT to demodulate/decode this signal is verified by measuring the throughput. The maximum achievable throughput shall be verified in good signal conditions. The signal conditions shall be set at least to a value of the test limit, where the minimum requirement is to reach > 90 % of the maximum throughput supported by the EUT. B.1.2 Mapping the throughput to error ratio B.1.2.1 Defining throughput and bitrate The measured information bit throughput is defined as the sum of the information bit payloads successfully received during the test interval, divided by the duration of the test interval (in seconds). The physical bitrate performance can be observed by deducting the detected physical layer payload packet errors from the total amount of the physical layer packets transmitted during the observation time. = β β β Γ β β B.1.2.2 Mapping the ACK/NACK to error ratio In measurement practice the EUT indicates successfully received information bit payload by signalling an ACK to the SS. If payload is received, but damaged and cannot be decoded, the EUT signals a NACK. The time in the measurement interval is composed of successfully received subframes (ACK), unsuccessfully received subframes (NACK). The pass-fail decision is done by observing: β’ the number of NACKs; β’ the number of ACKs. The measured physical layer Error Rate (ER) is calculated: = Where: β’ = β ; and β’ = β . ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 48 B.1.2.3 Mapping the received packet count to error ratio The EUT records successfully received information bit payload packets and is able to report the number of successfully received packets within the measurement interval. The measured physical layer Error Rate (ER) is calculated: = The following examples of methods are provided for information: β’ Method 1: Obtain the raw data bits received by the EUT and compare them with the sent ones to determine whether packet reception was successful. β’ Method 2: Read out EUT-internal CRC based counter of correctly received packets. β’ Method 3: Read out the physical layer Error Rate (ER) measurement of the EUT. B.1.3 Design of the test The test is defined by the following parameters: 1) Limit of the Error Rate (ER) = 0,10 (Throughput limit = 90 %) 2) Confidence level C = 99 % and reliability R = 90 % B.1.4 Numerical definition of the pass-fail limits Using Bayes success-run theorem the required sample size is based on the confidence level = 0,99 and reliability = 0,90 with a maximum number of failures allowed is given by: = , Γ ( ) , where Ξ§ (1 β) is a Chi-square value for given confidence level C and 2( + 1) degrees of freedom. Table B.1.4-1 has pass-fail limits given by the equation above tabulated. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 49 Table B.1.4-1: Pass-Fail limits 0 47 30 455 60 807 90 1 147 1 67 31 467 61 818 91 1 158 2 85 32 479 62 830 92 1 169 3 101 33 491 63 841 93 1 181 4 117 34 503 64 853 94 1 192 5 132 35 515 65 864 95 1 203 6 146 36 527 66 875 96 1 214 7 160 37 538 67 887 97 1 225 8 175 38 550 68 898 98 1 237 9 188 39 562 69 910 99 1 248 10 202 40 574 70 921 100 1 259 11 215 41 586 71 932 101 1 270 12 229 42 598 72 944 102 1 281 13 242 43 609 73 955 103 1 292 14 255 44 621 74 967 104 1 303 15 268 45 633 75 978 105 1 315 16 281 46 645 76 989 106 1 326 17 294 47 656 77 1 001 107 1 337 18 306 48 668 78 1 012 108 1 348 19 319 49 680 79 1 023 109 1 359 20 332 50 691 80 1 034 110 1 370 21 344 51 703 81 1 046 111 1 381 22 357 52 714 82 1 057 112 1 392 23 369 53 726 83 1 068 113 1 403 24 381 54 738 84 1 080 114 1 415 25 394 55 749 85 1 091 115 1 426 26 406 56 761 86 1 102 116 1 437 27 418 57 772 87 1 113 117 1 448 28 430 58 784 88 1 125 118 1 459 29 442 59 795 89 1 136 119 1 470 B.1.5 Pass-Fail decision rules The pass-fail decision rules apply for a single test, comprising one component in the test vector: β’ having observed 0 errors, pass the test at 47+ samples; β’ having observed 1 error, pass the test at 67+ samples; β’ β¦ β’ having observed 118 errors, pass the test at 1 459+ samples; β’ having observed 119 errors, pass the test at 1 470+ samples; β’ having observed more than 119 errors, fail the test; β’ where x+ means: x or more. NOTE 1: An ideal EUT passes after 47 samples. The maximum test time is 1 470 samples. NOTE 2: It is allowed to deviate from the early decision concept by postponing the decision (pass-fail or continue). Postponing the decision to or beyond the end of Table F.1 requires a pass-fail decision against the test limit: pass for the EUT with ER < 0,10, otherwise fail. NOTE 3: Each sample is a received data packet including CRC. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 50 B.2 No loss of transmission testing of receiver characteristics B.2.1 Description This criterion is only for equipment that does not support receiver statistical testing of clause F.1. The test of receiver characteristics is three-fold: 1) Test system has a bidirectional link setup between EUT and SS. 2) A signal or a combination of signals is offered to the RX port(s) of the EUT. 3) The ability of the EUT to demodulate/decode this signal is verified by verifying transmissions from the EUT to the SS. Wireless transmission is lost when in a bidirectional test setup EUT stops transmissions after it has lost the capability of receiving transmissions from SS. No loss of transmission shall be verified in good signal conditions. Signal conditions shall be set at least to a value of the test limit where the no loss of transmission is verified. B.2.2 Pass-Fail decision rules No loss of transmission shall be verified at least over a period of 60 seconds. NOTE: Pass-Fail decision rule of no loss of transmission testing compared to receiver statistical testing of clause F.1 may lead to significant increase in test durations. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 51 Annex C (normative): Measurement uncertainties and test tolerances C.1 Acceptable uncertainty of Test System C.1.1 Measurement of test environment The measurement accuracy of the RD test environments defined in clause 4.1 of the present document, test environments shall be as specified in Table C.1.1-1. Table C.1.1-1: Test environment measurement accuracy Parameter Accuracy Radio frequency Β±5 Hz Relative Humidity Β±5 % Temperature Β±2 Β°C DC Voltage Β±1 % AC Voltage Β±1,5 % Vibration Β±10 % Vibration frequency Β±0,1 Hz The above values shall apply unless the test environment is otherwise controlled and the specification for the control of the test environment specifies the uncertainty for the parameter. C.1.2 Measurement of transmitter Table C.1.2-1: Measurement uncertainty in transmitter measurements Test Maximum Test System Uncertainty Note 6.1.1.1 Maximum output power Β±0,7 dB, f β€ 3 GHz Β±1,0 dB, 3 GHz < f β€ 4,2 GHz Β±1,3 dB, 4,2 GHz < f β€ 6 GHz 6.1.1.2 Transmit absolute power tolerance Β±0,7 dB, f β€ 3GHz Β±1,0 dB, 3 GHz < f β€ 4,2 GHz Β±1,3 dB, 4,2 GHz < f β€ 6 GHz 6.1.1.3 Transmit OFF power Β±1,5 dB, f β€ 3 GHz Β±1,8 dB, 3 GHz < f β€ 4,2 GHz Β±2,0 dB, 4,2 GHz < f β€ 6 GHz 6.1.1.4 Transmit ON/OFF time mask Β±1,5 dB, f β€ 3 GHz Β±1,8 dB, 3 GHz < f β€ 4,2 GHz Β±2,0 dB, 4,2 GHz < f β€ 6 GHz 6.1.2.1 Centre frequency Β±15 Hz 6.1.2.2 Carrier leakage Β±0,8 dB 6.1.2.3 Error vector magnitude Β±2,5 % 6.1.2.4 Transmitter spectrum flatness Β±1,5 dB 6.1.3.1 Occupied bandwidth 6.1.3.2 Out of band emissions Β±1,5 dB, f β€ 3 GHz Β±1,8 dB, 3 GHz < f β€ 4,2 GHz Β±2,0 dB, 4,2 GHz < f β€ 6 GHz 6.1.3.3 Adjacent channel leakage ratio Β±0,8 dB 6.1.3.4 Spurious emissions Β±2,0 dB, 9 kHz < f β€ 4 GHz Β±4,0 dB, 4 GHz < f β€ 19 GHz ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 52 C.1.3 Measurement of receiver Table C.1.3-1: Measurement uncertainty in receiver measurements Test Maximum Test System Uncertainty Note 6.2.1.1 Sensitivity Β±0,7 dB, β€ 3 GHz Β±1,0 dB, 3 GHz < β€ 4,2 GHz Β±1,3 dB, 4,2 GHz < β€ 6 GHz 6.2.1.2 Maximum input level Β±0,7 dB, β€ 3 GHz Β±1,0 dB, 3 GHz < β€ 4,2 GHz Β±1,3 dB, 4,2 GHz < β€ 6 GHz 6.2.1.3 Adjacent channel selectivity Β±1,1 dB, β€ 3GHz Β±1,5 dB, 3 GHz < β€ 4,2 GHz Β±2,2 dB, 4,2 GHz < β€ 6 GHz Overall, ACS uncertainty comprises three quantities: 1) Wanted signal level error 2) Interferer signal level error 3) Additional impact of interferer ACLR Items 1 and 2 are assumed to be uncorrelated so can be root sum squared to provide the ratio error of the two signals. The interferer ACLR effect is systematic and is added arithmetically. 6.2.2.1 In-band blocking Β±1,4 dB, β€ 3 GHz Β±1,8 dB, 3 GHz < β€ 4,2 GHz Β±2,5 dB, 4,2 GHz < β€ 6 GHz Overall blocking uncertainty can have these contributions: 1) Wanted signal level error 2) Interferer signal level error 3) Interferer ACLR 4) Interferer broadband noise Items 1 and 2 are assumed to be uncorrelated so can be root sum squared to provide the ratio error of the two signals. The Interferer ACLR or Broadband noise effect is systematic and is added arithmetically. 6.2.2.2 Out of band blocking Wanted signal β€ 3 GHz: Β±1,3 dB, 1 MHz < β€ 3 GHz Β±3,2 dB, 3 GHz < β€ 12,75 GHz Wanted signal 3 GHz < β€ 4,2 GHz: Β±1,5 dB, 1 MHz < β€ 3 GHz Β±3,3 dB, 3 GHz < β€ 12,75 GHz Wanted signal 4,2GHz < β€ 6 GHz: Β±1,9 dB, 1 MHz < β€ 3 GHz Β±3,5 dB, 3 GHz < β€ 12,75 GHz Out of band blocking, using CW interferer: β’ f β€ 3,0 GHz β’ Wanted signal level Β± 0,7 dB β’ 3,0 GHz < f β€ 4,2 GHz β’ Wanted signal level Β± 1,0 dB Interferer signal level: β’ Β± 1,0 dB up to 3 GHz β’ Β± 3,0 dB up to 12,75 GHz Interferer ACLR not applicable β’ Impact of interferer Broadband noise 0,1 dB. 6.2.2.3 Spurious response Same as clause 6.2.2.2 ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 53 Test Maximum Test System Uncertainty Note 6.2.3.1 Wide band intermodulation Β±1,4 dB, β€ 3 GHz Β±2,6 dB, 3 GHz < β€ 4,2 GHz Β±3,8 dB, 4,2 GHz < β€ 6 GHz Overall intermodulation uncertainty comprises three quantities: 1) Wanted signal level error 2) CW Interferer level error 3) Modulated Interferer level error Effect of interferer ACLR has not been included as modulated interferer has larger frequency offset The effect of the closer CW signal has twice the effect. Items 1, 2 and 3 are assumed to be uncorrelated so can be root sum squared to provide the combined effect of the three signals. 6.2.4.1 Spurious emissions Β±2,0 dB, 30 MHz < β€ 4 GHz Β±4,0 dB, 4 GHz < β€ 19 GHz 6.2.5.1 RSSI-1 measurement Β±0,7 dB, β€ 3 GHz Β±1,0 dB, 3 GHz < β€ 4,2 GHz Β±1,3 dB, 4,2 GHz < β€ 6 GHz 6.2.5.2 RSSI-2 measurement Β±0,7 dB, β€ 3 GHz Β±1,0 dB, 3 GHz < β€ 4,2 GHz Β±1,3 dB, 4,2 GHz < β€ 6 GHz 6.2.5.3 SNR measurement Β±0,7 dB, β€ 3 GHz Β±1,0 dB, 3 GHz < β€ 4,2 GHz Β±1,3 dB, 4,2 GHz < β€ 6 GHz C.2 Interpretation of measurement results The Test Requirements in the present document have been calculated by relaxing the Minimum Requirements of the core specification using the Test Tolerances (TT) defined in clause C.1. The measurement results returned by the Test System are compared - without any modification - against the Test Requirements as defined by either the "Never fail a good DUT" principle for Test Tolerance equal measurement uncertainty (TT = MU) or "Shared Risk" principle for Test Tolerance equal to 0 (TT = 0). The "Never fail a good DUT" and the "Shared Risk" principles are defined in ETSI ETR 273-1-2 [i.1], clause 6.5. The actual measurement uncertainty of the Test System for the measurement of each parameter shall be included in the test report. The recorded value for the Test System uncertainty shall be, for each measurement, equal to or lower than the appropriate figure in clause C.1 of the present document. If the Test System for a test is known to have a measurement uncertainty greater than that specified in clause C.1, it is still permitted to use this apparatus provided that an adjustment is made value as follows: Any additional uncertainty in the Test System over and above that specified in clause C.1 shall be used to tighten the Test Requirement, making the test harder to pass. For some tests, for example receiver tests, this may require modification of stimulus signals. This procedure will ensure that a Test System not compliant with clause C.1 does not increase the chance of passing a device under test where that device would otherwise have failed the test if a Test System compliant with clause C.1 had been used. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 54 Annex D (normative): Test sites and arrangements for radiated measurements D.1 Introduction This annex describes the use of test sites (including antennas) to perform radiated measurements in accordance with the present document. In addition, the present annex describes the use of a test fixture to perform conducted (relative) measurements on equipment with integral antennas. It also defines the interference signal to be used in the adaptivity tests. Subsequently the following items will be described: β’ Open Area Test Site (OATS). β’ Semi Anechoic Room (SAR). β’ Fully Anechoic Room (FAR). β’ Test fixture for relative measurements. The first three are generally referred to as free field test sites. Both absolute and relative measurements can be performed on these sites. They will be described in clause D.2. Clause D.3 describes the antennas used in these test sites. Where absolute measurements are to be carried out, the chamber should be verified. A detailed verification procedure is described in clause 6 of ETSI TR 102 273-4 [i.6] for the OATS, in clause 6 of ETSI TR 102 273-3 [i.5] for the SAR, and in clause 6 of ETSI TR 102 273-2 [i.4] for the FAR. Information for calculating the measurement uncertainty of measurements on one of these test sites can be found in ETSI TR 100 028-1 [i.2], ETSI TR 100 028-2 [i.3], ETSI TR 102 273-2 [i.4], ETSI TR 102 273-3 [i.5] and ETSI TR 102 273-4 [i.6]. D.2 Radiation test sites D.2.1 Open Area Test Site (OATS) An Open Area Test Site comprises a turntable at one end and an antenna mast of variable height at the other end above a ground plane which, in the ideal case, is perfectly conducting and of infinite extent. In practice, while good conductivity can be achieved, the ground plane size has to be limited. A typical Open Area Test Site is shown in Figure D.2.1-1. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 55 Figure D.2.1-1: A typical Open Area Test Site The ground plane creates a wanted reflection path, such that the signal received by the receiving antenna is the sum of the signals received from the direct and reflected transmission paths. The phasing of these two signals creates a unique received level for each height of the transmitting antenna (or EUT) and the receiving antenna above the ground plane. The antenna mast provides a variable height facility (from 1 m to 4 m) so that the position of the measurement antenna can be optimized for maximum coupled signal between antennas or between an EUT and the measurement antenna. A turntable is capable of rotation through 360Β° in the horizontal plane and it is used to support the test sample (EUT) at a height of usually 1,5 m above the ground plane. The measurement distance and minimum chamber dimensions can be found in clause D.2.4. The distance used in actual measurements shall be recorded with the test results. Further information on Open Area Test Sites can be found in ETSI TR 102 273-4 [i.7]. D.2.2 Semi Anechoic Room (SAR) A Semi Anechoic Room - or anechoic chamber with a conductive ground plane - is an enclosure, usually shielded, whose internal walls and ceiling are covered with radio absorbing material. The floor, which is metallic, is not covered by absorbing material and forms the ground plane. The chamber usually contains an antenna mast at one end and a turntable at the other end. A typical anechoic chamber with a conductive ground plane is shown in Figure D.2.2-1. This type of test chamber attempts to simulate an ideal Open Area Test Site, whose primary characteristic is a perfectly conducting ground plane of infinite extent. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 56 Figure D.2.2-1: A typical Semi Anechoic Room In this facility the ground plane creates a wanted reflection path, such that the signal received by the receiving antenna is the sum of the signals received from the direct and reflected transmission paths. The phasing of these two signals creates a unique received level for each height of the transmitting antenna (or EUT) and the receiving antenna above the ground plane. The antenna mast provides a variable height facility (from 1 m to 4 m) so that the position of the measurement antenna can be optimized for maximum coupled signal between antennas or between an EUT and the measurement antenna. A turntable is capable of rotation through 360Β° in the horizontal plane and it is used to support the test sample (EUT) at a height of usually 1,5 m above the ground plane. The measurement distance and minimum chamber dimensions can be found in clause D.2.4. The distance used in actual measurements shall be recorded with the test results. Further information on Semi Anechoic Rooms can be found in ETSI TR 102 273-3 [i.6]. D.2.3 Fully Anechoic Room (FAR) A Fully Anechoic Room is an enclosure, usually shielded, whose internal walls, floor and ceiling are covered with radio absorbing material. The chamber usually contains an antenna support at one end and a turntable at the other end. A typical Fully Anechoic Room is shown in Figure D.2.3-1. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 57 Figure D.2.3-1: A typical Fully Anechoic Room The chamber shielding and radio absorbing material provide a controlled environment for testing purposes. This type of test chamber attempts to simulate free space conditions. The shielding provides a test space, with reduced levels of interference from ambient signals and other outside effects, whilst the radio absorbing material minimizes unwanted reflections from the walls and ceiling which can influence the measurements. The shielding should be sufficient to eliminate interference from the external environment that would mask any signals that have to be measured. A turntable is capable of rotation through 360Β° in the horizontal plane and it is used to support the EUT at a height of usually 1 m above the absorbing material. The measurement distance and minimum chamber dimensions can be found in clause D.2.4. The distance used in actual measurements shall be recorded with the test results. Further information on Fully Anechoic Rooms can be found in ETSI TR 102 273-2 [i.5]. D.2.4 Measurement Distance The measurement distance should be chosen in order to measure the EUT at far-field conditions. The minimum measurement distance between the equipment and the measurement antenna should be Ξ» or r! β₯ " whichever is the greater: Ξ» = wavelength in m rm = minimum measurement distance between EUT and measurement antenna in m D = largest dimension of physical aperture of the largest antenna in the measurement setup, in m " = distance between outer boundary of radiated near field (Fresnel region) and inner boundary of the radiated far-field (Fraunhofer region) in m, also known as Rayleigh distance ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 58 For those measurements, where these conditions cannot be fulfilled and where the measurement distance would result in measurements in the near field (e.g. while measuring spurious emissions), this should be noted in the test report and the additional measurement uncertainty should be incorporated into the results. D.3 Antennas D.3.1 Introduction Antennas are needed for the radiated measurements on the three test sites described in clause D.2. Depending on its use, the antenna will be designated as "measurement antenna" or "substitution antenna". D.3.2 Measurement antenna The measurement antenna is used to determine the field from the EUT and from the substitution antenna. When the test site is used for the measurement of receiver characteristics, the antenna is used as the transmitting device. The measurement antenna should be mounted on a support capable of allowing the antenna to be used in either horizontal or vertical polarization. Additionally, on an OATS or SAR, the height of the centre of the antenna above the ground should be variable over the specified range (usually 1 m to 4 m). In the frequency band 30 MHz to 1 000 MHz, biconical or Logarithmic Periodic Dipole Antennas (LPDA) are recommended. Above 1 GHz, horn antennas or logarithmic periodic dipole antennas are recommended. D.3.3 Substitution antenna The substitution antenna shall be used to replace the equipment under test in substitution measurements. The substitution antenna shall be suitable for the frequency range and the return loss of the antenna shall be taken into account when calculating the measurement uncertainty. The reference point of the substitution antenna shall coincide with the volume centre of the EUT when its antenna is internal, or the point where an external antenna is connected to the EUT. The distance between the lower extremity of the antenna and the ground shall be at least 30 cm. The substitution antenna shall be calibrated. For below 1 GHz, the calibration is relative to a half wave dipole, while above 1 GHz, an isotropic radiator is the reference. D.4 Test fixture D.4.1 Introduction Conducted measurements may be applied to equipment provided with a (temporary) antenna connector, e.g. by means of a spectrum analyser. In the case of integral antenna equipment with no external (temporary) antenna connector(s) provided, a test fixture can be used to allow relative measurements to be performed at the extremes of temperature. D.4.2 Description of the test fixture The test fixture shall provide a means of coupling to the radio frequency output(s) of the EUT. The impedance of the external connection to the test fixture shall be 50 Ξ© at the working frequencies of the equipment. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 59 The performance characteristics of this test fixture under normal and extreme conditions shall be such that: a) the coupling loss shall be limited to ensure a sufficient dynamic range of the setup; b) the variation of coupling loss with frequency shall not cause errors exceeding Β±2 dB; c) the coupling device shall not include any non-linear elements. D.4.3 Using the test fixture for relative measurements The different steps below describe the principle for performing relative measurements for those requirements where testing needs to be repeated at the extremes of the temperature. Step 1: Perform the measurement under normal conditions on a test site for radiated measurements as described in clause D.2. This will result in an absolute value for the requirement being tested. This value shall be recorded. Step 2: Put the equipment with the test fixture in the temperature chamber. Perform the same measurement at normal conditions in this environment and normalize the measuring equipment to get the same reading as before in step 1. Step 3: Ensure that the RF coupling accuracy remains within the range specified in clause D.4.2, item b). Step 4: Change the temperature in the temperature chamber and perform the measurement again. Due to the normalization done in step 2, the result will be the value for this requirement at the extreme condition. D.5 Guidance on the use of radiation test sites D.5.1 Introduction This clause details procedures, test equipment arrangements and verification that should be carried out before any of the radiated test are undertaken. These schemes are common to all types of test sites described in clause E.2. Where necessary, a mounting bracket of minimal size should be available for mounting the EUT on the turntable. This bracket should be made from low conductivity, low relative permittivity (i.e. # # < 1,5 material(s) such as expanded polystyrene, balsawood, etc. D.5.2 Power supplies for the battery powered EUT All tests should be performed using power supplies wherever possible, including tests on EUT designed for battery only use. For battery powered equipment, power leads should be connected to the EUT's supply terminals (and monitored with a digital voltmeter) but the battery should remain present, electrically isolated from the rest of the equipment, possibly by putting tape over its contacts. The presence of these power cables can, however, affect the measured performance of the EUT. For this reason, they should be made to be "transparent" as far as the testing is concerned. This can be achieved by routing them away from the EUT and down to the either the screen, ground plane or facility wall (as appropriate) by the shortest possible paths. Precautions should be taken to minimize pick-up on these leads (e.g. the leads could be twisted together, loaded with ferrite beads at 0,15 m spacing or otherwise loaded). ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 60 D.5.3 Site preparation The cables to the measuring and substitution antenna should be routed horizontally away from the testing area for a minimum of 2 m (unless, in the case both types of anechoic chamber, a back wall is reached) and then allowed to drop vertically and out through either the ground plane or screen (as appropriate) to the test equipment. Precautions should be taken to minimize pick up on these leads (e.g. dressing with ferrite beads, or other loading). The cables, their routing and dressing should be identical to the verification set-up. NOTE: For ground reflection test sites (i.e. anechoic chambers with ground planes and Open Area Test Sites) which incorporate a cable drum with the antenna mast, the 2 m requirement may be impossible to comply with. Calibration data for all items of test equipment should be available and valid. For test, substitution and measuring antennas, the data should include gain relative to an isotropic radiator (or antenna factor) for the frequency of test. Also, the VSWR of the substitution and measuring antennas should be known. The calibration data on all cables and attenuators should include insertion loss and VSWR throughout the entire frequency range of the tests. All VSWR and insertion loss figures should be recorded in the logbook results sheet for the specific test. Where correction factors/tables are required, these should be immediately available. For all items of test equipment, the maximum errors they exhibit should be known along with the distribution of the error, e.g.: β’ cable loss: Β±0,5 dB with a rectangular distribution; β’ measuring receiver: 1,0 dB (standard deviation) signal level accuracy with a Gaussian error distribution. At the start of measurements, system checks should be made on the items of test equipment used on the test site. D.6 Coupling of signals D.6.1 General The presence of leads in the radiated field may cause a disturbance of that field and lead to additional measurement uncertainty. These disturbances can be minimized by using suitable coupling methods, offering signal isolation and minimum field disturbance (e.g. optical coupling). D.6.2 Data Signals Isolation can be provided by the use of optical, ultrasonic or infra-red means. Field disturbance can be minimized by using a suitable fibre optic connection. Ultrasonic or infra-red radiated connections require suitable measures for the minimization of ambient noise. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 61 Annex E (normative): Procedures for radiated measurements E.1 Introduction The present annex gives the general procedures for radiated measurements using the test sites and arrangements described in Annex D. Preferably, radiated measurements shall be performed in a FAR, see clause E.3. Radiated measurements in an OATS or SAR are described in clause E.2. E.2 Radiated measurements in an OATS or SAR Radiated measurements shall be performed with the aid of a measurement antenna and a substitution antenna, in test sites described in Annex D. The measurement set-up shall be calibrated according to the procedure defined in the present annex. The EUT and the measurement antenna shall be oriented such as to obtain the maximum emitted power level. This position shall be recorded in the measurement report: a) The measurement antenna (device 2 in Figure E.2-1) shall be oriented initially for vertical polarization unless otherwise stated and the EUT (device 1 in Figure E.1) shall be placed on the support in its standard position and switched on. b) The measurement equipment (device 3 in Figure E.2-1) shall be connected to the measurement antenna and set-up according to the specifications of the test. 1) EUT 2) Measurement antenna 3) Measurement equipment Figure E.2-1: Measurement arrangement c) The EUT shall be rotated through 360Β° in a horizontal plane until a higher maximum signal is received. d) The measurement antenna shall be raised or lowered again through the specified height range until a maximum is obtained. This level shall be recorded. This maximum may be a lower value than the value obtainable at heights outside the specified limits. e) This measurement procedure in step c) and step d) above shall be repeated for horizontal polarization. 1 2 3 ground plane 1,5 m specified height range 1 m to 4 m ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 62 E.3 Radiated measurements in a FAR For radiated measurements using a FAR, the procedure is identical to the one described in clause D.2, except that the height scan in step d) is omitted. E.4 Substitution measurement To determine the absolute measurement value a substitution measurement is performed. The following steps have to be performed: 1) Replacing the EUT with the substitution antenna that is depicted as device 1 in Figure E.2-1. The substitution antenna shall have vertical polarization. 2) Connect a signal generator to the substitution antenna, and adjust it to the measurement frequency. 3) If an OATS or a SAR is used, the measurement antenna height shall be varied within the range provided in Figure E.2-1 to ensure that the maximum signal is received. 4) Subsequently, the power of the signal generator is adjusted until the same level is obtained again at the measurement equipment. 5) The radiated power is equal to the power supplied by the signal generator, increased with the substitution antenna gain minus the cable losses (values in dB). 6) This measurement procedure described in step 2) to step 5) above shall be repeated with horizontal polarization for the substitution antenna. For test sites with a fixed setup of the measurement antenna(s) and a reproducible positioning of the EUT, correction values from a verified site calibration can be used alternatively. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 63 Annex F (normative): EUT special conformance test functions F.1 General description F.1.1 Introduction The EUT provides a set of functions in support of conformance testing. The functions are only accessible in test standby mode of the EUT, see clause F.1.2. The SS performs activation and deactivation of the conformance test functions in the EUT by sending test control messages. The messages can be used to: 1) Select EUT test loop function. 2) Select EUT measurement mode function. F.1.2 Test standby mode Accessibility to test control messages is controlled by some means of mechanical interlocking method, manual switching, (e.g. dip-switch, jumper, prom, key-pad code, UART command) or by manufacturer's secure and proprietary over-the-air control test mode control mechanism, as designated by the manufacturer to prevent accidental execution of these messages in a DECT-2020 NR user environment. For testing physical layer functionality, the device can support only the EUT special conformance testing functions without the full DECT-2020 NR MAC, DLC and CVG layers functionality which conformance test setups are defined in ETSI TS 104 047-2 [4]. When the EUT has been configured into a mode whereby the test messages are accessible, the EUT is said to be in the test standby mode. F.1.3 Security protection of test control messages Test control messages are only used in controlled test environment while the EUT is in test standby mode. No security protection of test control messages is used. F.1.4 Protocol implementation extra information for testing A statement made by the manufacturer which contains or references all of the information related to the EUT and its testing environment, which will enable the test laboratory to run an appropriate test suite against the EUT. This shall include: β’ the method by which the equipment can be switched into the test standby mode. This mode is described in clause F.1.2; β’ the test control channel supported by the EUT, given as an absolute channel frequency number as defined in ETSI TS 103 636-2 [1]. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 64 F.2 Test standby mode procedures F.2.1 General In test standby mode the EUT first finds the SS and then awaits control messages from the SS. F.2.2 Connection establishment procedure The EUT may be capable of operating on several operating bands. To establish communication with the SS the EUT finds the SS. During the connection establishment procedure, the SS shall: β’ transmit a TEST_CONTROL_BEACON message every 10 ms on the test control channel; β’ activate reception latest 1 ms after each beacon transmission on the test control channel. The reception shall last for the rest of the 10ms frame until transmission of next TEST_CONTROL_BEACON; β’ if TEST_CONTROL_CONNECT message is received: - send TEST_CONTROL_CONNECT_COMPLETE message on the test control channel; - enter the test control procedure. During the connection establishment procedure, the EUT shall: β’ receive packets on the test control channel; β’ if TEST_CONTROL_BEACON is received: - send TEST_CONTROL_CONNECT message on the test control channel; β’ if TEST_CONTROL_CONNECT_COMPLETE is received: - enter the test control procedure. F.2.3 Test control procedure During test control procedure the SS controls the EUT on the test control channel. The details of these procedures are described in the individual test procedures. Unless otherwise described in a test procedure, all radio operations happen on the test control channel during the test control procedure. Additionally, the SS shall: β’ transmit a TEST_CONTROL_BEACON message every 1 second unless a test case is being run; β’ if communication with the EUT has been lost: - enter the connection establishment procedure. The EUT shall: β’ receive packets from SS; β’ perform test mode specific actions based on the received packets. The modes are defined in clause F.3; β’ if no packets have been received from the SS in 5 seconds: - enter the connection establishment procedure. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 65 F.3 EUT test modes F.3.1 General description F.3.1.1 Overview The EUT test modes provide access to isolated functions of the EUT via the radio interface without introducing wherever possible new physical interfaces just for the reason of conformance testing. The test modes are divided into measurement mode and loop mode. F.3.1.2 EUT measurement mode The measurement mode is activated by transmitting ACTIVATE_MEASUREMENT_MODE message to the EUT. The measurement mode can be operated in different modes: β’ EUT measurement mode A; β’ EUT measurement mode B. In measurement mode A the EUT performs RSSI-1 measurements on the test channel. In measurement mode B the EUT receives and decodes packets from the SS, and measures RSSI-2, and SNR. F.3.1.3 EUT loop mode The loop mode is activated by transmitting ACTIVATE_TX_LOOP_MODE or ACTIVATE_RX_LOOP_MODE message to the EUT. The loop mode can be operated in different modes: β’ EUT Transmit loop mode. β’ EUT Receive loop mode. In EUT Transmit loop mode EUT transmits packets with random PHY Data SDU for TS to analyse the transmitter performance. In EUT Receive loop mode EUT receives and decodes packets from the SS, and measures RSSI-2 and SNR, and transmits an acknowledgement, measurement results and data back to the SS for each packet. F.3.2 Common transmission parameters Unless otherwise specified in a test case: β’ all test control messages shall be transmitted with a transmission power guaranteeing that messages are received correctly without needing to explicitly acknowledge messages or perform retransmissions; β’ all test control messages shall use MCS 1; β’ the short network ID used by the SS in the TEST_CONTROL_BEACON shall be used as the short network ID of all transmitted messages; β’ the 24 MSB bits of the network ID is transmitted in TEST_CONTROL_BEACON; β’ the transmitter identity used by the SS in the TEST_CONTROL_BEACON shall be used as the short RD ID of the SS; β’ the transmitter identity used by the EUT in the TEST_CONTROL_CONNECT message shall be used as the short RD ID of the EUT; ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 66 β’ for the test control messages HARQ shall not be used. F.4 EUT measurement mode procedures F.4.1 General The EUT measurement mode procedures are intended for setting the EUT into a measurement mode where the SS sends a number of packets to the EUT, and the EUT performs measurements over the packets and reports a measurement summary at the end of the measurement mode procedure. F.4.2 Measurement mode activation The SS requests the EUT to activate a measurement mode by transmitting an ACTIVATE_MEASUREMENT_MODE message. Upon receiving the ACTIVATE_MEASUREMENT_MODE the EUT shall: β’ send ACTIVATE_MEASUREMENT_MODE_COMPLETE message; β’ activate measurement mode indicated by MEASUREMEN_MODE field of the received message. Once a measurement mode has been activated, the EUT shall: β’ perform all transmission and reception on the MEASUREMENT_CHANNEL indicated in the ACTIVATE_MEASUREMENT_MODE message. F.4.3 Measurement mode A (RSSI-1) F.4.3.1 Measurement mode A operation In measurement mode A the EUT shall: β’ continuously receive packets and measure RSSI-1 on the MEASUREMENT_CHANNEL starting at the time MEASUREMENT_START_TIME; β’ if DEACTIVATE_MEASUREMENT_MODE packet is received: - send REPORT_MEASUREMENT_MODE_A message; - return to test standby mode. F.4.3.2 Measurement mode A reporting The EUT shall report the last measured RSSI-1 value. F.4.4 Measurement mode B (packet reception) F.4.4.1 Measurement mode B operation In measurement mode B the SS shall: β’ keep its transmission characteristics such as in RSSI signal level or interference level constant between consecutive transmissions. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 67 In measurement mode B the EUT shall: β’ continuously receive packets on the MEASUREMENT_CHANNEL starting at the time MEASUREMENT_START_TIME; β’ for each received packet: - packet measure per-packet RSSI-2PACKET and SNRPACKET; - calculate average RSSI-2 and average SNR as specified in ETSI TS 103 636-2 [1]; - if the received packet is DEACTIVATE_MEASUREMENT_MODE: ο§ send REPORT_MEASUREMENT_MODE_B message; ο§ return to test standby mode. F.4.4.2 Measurement mode B reporting The EUT shall report: β’ received_packet_count, the total number of packets received during the measurement period; β’ average_rssi_2, as specified in ETSI TS 103 636-2 [1]; β’ average_snr, as specified in ETSI TS 103 636-2 [1]. F.5 EUT loop mode procedures F.5.1 General The EUT loop mode is intended for: β’ DECT-2020 NR RF receiver and transmitter testing to receive and transmit DECT-2020 NR packets with controlled transmission characteristics. F.5.2 Loop mode activation The SS requests the EUT to activate a loop mode by transmitting an appropriate ACTIVATE_TX_LOOP_MODE or ACTIVATE_RX_LOOP_MODE message. Upon receiving the ACTIVATE_{TX/RX}_LOOP_MODE the EUT shall: β’ send ACTIVATE_{TX/RX}_LOOP_MODE_COMPLETE message; β’ activate the loop mode indicated by loop_mode_type field of the received message. Once a loop mode has been activated, the EUT shall: β’ perform all packet receptions or transmissions on the loop_channel indicated in the ACTIVATE_{TX/RX}_LOOP_MODE message. F.5.3 Transmit loop mode operation In Transmit loop mode TS shall: β’ receive packets sent by the EUT; β’ analyse EUT transmitter performance. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 68 In Transmit loop mode EUT shall: β’ continuously transmit and count the transmitted packets on loop_channel starting at loop_start_delay from the reception of ACTIVATE_TX_LOOP_MODE message with loop_period interval between packets until loop_duration has expired according to the configuration set by the SS in ACTIVATE_TX_LOOP_MODE message; β’ transmit REPORT_TX_LOOP_MODE after expiration of loop_duration before returning to test standby mode. F.5.4 Receive loop mode operation In Receive loop mode the SS shall: β’ continuously send packets to EUT, and expect ACK/NACK response for each packet; β’ analyse EUT receiver performance based on received ACK/NACK responses, considering also the missing responses. In Receive loop mode the EUT shall: β’ continuously receive packets on the loop_channel starting at loop_start_delay from the reception of the ACTIVATE_TX_LOOP message; and - demodulate and decode received packets; - count the correctly received packets; - measure the per packet RSSI-2 and SNR; β’ if the received packet is RX_LOOP_MODE_DATA: - prepare a response message: ο§ use packet configuration and transmission power specified in ACTIVATE_RX_LOOP_MODE message; ο§ if transmission power exceeds the EUT device class capabilities, use the largest transmission power its device class capabilities allow; ο§ indicate ACK/NACK feedback in the PCC of the response packet according to PDC decoding result; ο§ fill in fields of RX_LOOP_MODE_DATA_RESPONSE: ο§ set the rssi-2 and snr fields; ο§ fill the data field; - send the RX_LOOP_MODE_DATA_RESPONSE message after the time indicated by loop_response_delay: β’ else if the received packet is DEACTIVATE_LOOP_MODE: - send REPORT_LOOP_MODE message; - deactivate the loop mode and return to test standby mode. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 69 F.6 Test protocol messages F.6.1 General F.6.1.1 Message structure Unless otherwise specified for a message, all test protocol messages have Physical Layer Control Field: Type 2, Header Format: 001 as defined in clause 6.2 of ETSI TS 103 636-4 [3], encoded according to ETSI TS 103 636-3 [2], clause 7.5, and mapped onto PCC. PHY Data SDU contains message's fields indicate the fields' octet(s) appended either with all zero or random PN15 data to the transport block size specified in ETSI TS 103 636-3 [2], clause 5.3. PHY Data SDU is encoded according to ETSI TS 103 636-3 [2], clause 7.6 and mapped into PDC. Transmission order is as specified in ETSI TS 103 636-4 [3], clause 4.6. F.6.1.2 Message codes Table F.6.1.2-1 lists the message codes. Table F.6.1.2-1: Message codes Value Message 0x00 Reserved 0x01 TEST_CONTROL_BEACON 0x02 TEST_CONTROL_CONNECT 0x03 TEST_CONTROL_CONNECT_COMPLETE 0x04 ACTIVATE_MEASUREMENT_MODE 0x05 ACTIVATE_MEASUREMENT_MODE_COMPLETE 0x06 DEACTIVATE_MEASUREMENT_MODE 0x07 ACTIVATE_TX_LOOP_MODE 0x08 ACTIVATE_TX_LOOP_MODE_COMPLETE 0x09 ACTIVATE_RX_LOOP_MODE 0x0A ACTIVATE_RX_LOOP_MODE_COMPLETE 0x0B DEACTIVATE_LOOP_MODE 0x0C to 0x0F Reserved 0x10 REPORT_MEASUREMENT_MODE_A 0x11 REPORT_MEASUREMENT_MODE_B 0x12 REPORT_TX_LOOP_MODE 0x13 REPORT_RX_LOOP_MODE 0x13 to 0x1F Reserved 0x20 TX_LOOP_MODE_DATA 0x21 RX_LOOP_MODE_DATA 0x22 RX_LOOP_MODE_DATA _RESPONSE F.6.2 Test control messages F.6.2.1 TEST_CONTROL_BEACON The message is a half-slot packet with Physical Layer Control Field: Type 1, Header Format: 000, as defined in ETSI TS 103 636-4 [3], clause 6.2. PHY Data SDU for this message is described in Table F.6.2.1-1. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 70 Table F.6.2.1-1: TEST_CONTROL_BEACON message Field Octet Description message_code 0 Message code, set to TEST_CONTROL_BEACON network ID 1..3 First 24 bits of the Network ID, EUT shall use this network ID for scrambling code initialization as specified in ETSI TS 103 636-3 [2], clause 7.6.6. data 4β¦(TBS-1) Set to zero F.6.2.2 TEST_CONTROL_CONNECT PHY Data SDU for this message is described in Table F.6.2.2-1. Table F.6.2.2-1: TEST_CONTROL_CONNECT message Field Octet Description message_code 0 Message code, set to TEST_CONTROL_CONNECT data 1β¦(TBS-1) Set to zero F.6.2.3 TEST_CONTROL_CONNECT_COMPLETE PHY Data SDU for this message is described in Table F.6.2.3-1. Table F.6.2.3-1: TEST_CONTROL_CONNECT_COMPLETE message Field Octet Description message_code 0 Message code, set to TEST_CONTROL_CONNECT_COMPLETE status 1 Request status, values: 0: success 1: failure 2-255: reserved data 2β¦(TBS-1) Set to zero F.6.3 Measurement control messages F.6.3.1 ACTIVATE_MEASUREMENT_MODE PHY Data SDU for this message is described in Table F.6.3.1-1. Table F.6.3.1-1: ACTIVATE_MEASUREMENT_MODE message Field Octet Description message_code 0 Message code, set to ACTIVATE_MEASUREMENT_MODE measurement_mode 1 Measurement mode, values: 0: measurement mode A 1: measurement mode B 2-255: reserved measurement_channel 2β¦3 Channel on which the measurement is to take place. Value: absolute channel frequency number as defined in ETSI TS 103 636-2 [1]. measurement_start_time 4 Measurement start time in subslots as delta to the STF of the ACTIVATE_MEASUREMENT_MODE message. data 5β¦(TBS-1) Set to zero F.6.3.2 ACTIVATE_MEASUREMENT_MODE_COMPLETE PHY Data SDU for this message is described in Table F.6.3.2-1. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 71 Table F.6.3.2-1: ACTIVATE_MEASUREMENT_MODE_COMPLETE message Field Octet Description message_code 0 Message code, set to ACTIVATE_MEASUREMENT_MODE_COMPLETE status 1 Request status, values: 0: success 1: failure 2-255: reserved data 2β¦(TBS-1) Set to zero F.6.3.3 DEACTIVATE_MEASUREMENT_MODE PHY Data SDU for this message is described in Table F.6.3.3-1. Table F.6.3.3-1: DEACTIVATE_MEASUREMENT_MODE message Field Octet Description message_code 0 Message code, set to DEACTIVATE_MEASUREMENT_MODE data 1β¦(TBS-1) Set to zero F.6.4 Measurement report messages F.6.4.1 REPORT_MEASUREMENT_MODE_A PHY Data SDU for this message is described in Table F.6.4.1-1. Table F.6.4.1-1: REPORT_MEASUREMENT_MODE_A message Field Octet Description message_code 0 Message code, set to REPORT_MEASUREMENT_MODE_A average_rssi_1 1 Averaged RSSI-1. Value: RSSI-1 measurement reported value as defined in ETSI TS 103 636-2 [1]. data 2β¦(TBS-1) Set to zero F.6.4.2 REPORT_MEASUREMENT_MODE_B PHY Data SDU for this message is described in Table F.6.4.2-1. Table F.6.4.2-1: REPORT_MEASUREMENT_MODE_A message Field Octet Description message_code 0 Message code, set to REPORT_MEASUREMENT_MODE_A average_rssi_2 1 RSSI-2 averaged as specified in clause F.4.4.2. Value: RSSI-2 measurement reported value as defined in ETSI TS 103 636-2 [1]. average_snr 2 SNR averaged as specified in clause F.4.4.2. Value: SNR measurement reported value as defined in ETSI TS 103 636-2 [1]. received_packet_count 3β¦6 Number of packets received during the measurement data 7β¦(TBS-1) Set to zero F.6.5 Loop control messages F.6.5.1 ACTIVATE_TX_LOOP_MODE PHY Data SDU for this message is described in Table F.6.5.1-1. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 72 Table F.6.5.1-1: ACTIVATE_TX_LOOP_MODE message Field Octet Description message_code 0 Message code, set to ACTIVATE_TX_LOOP_MODE loop_mode_type 1 Transmission loop mode type, values: 0: normal 1: normal, STF cover sequence off 2-255: reserved loop_channel 2-3 Channel on which the transmission is to take place. Value: absolute channel frequency number as defined in ETSI TS 103 636-2 [1]. loop_start_delay 4 Transmission loop start time in subslots as delta to the STF of the ACTIVATE_TX_LOOP_MODE message. loop_period 5 Transmission repetition period given in subslots loop_duration 6 Transmission loop duration given in 10 ms frames. Zero value shall be interpreted as single transmission. Otherwise EUT shall implement many transmissions as possible during given number of 10 ms frames with given periodicity. plcf_type 7 PLCF Type as in ETSI TS 103 636-4 [3], clause 6.2, values 0: reserved 1: type 1 2: type 2 3-255: reserved plcf 8..12 or 8..17 PLCF as in ETSI TS 103 636-4 [3], clause 6.2 specifies the transmission format and transmission power EUT should use. Short Network ID, Transmitter Identity and Receiver Identity in EUT transmissions shall be set specified in clause F.3.2, values in these fields shall be disregarded. DF Redundancy version, DF New Data Indication, HARQ process number, Feedback format and Feedback Info in EUT transmissions shall be set by EUT, thus these fields shall be disregarded. data β¦(TBS-1) Set to zero F.6.5.2 ACTIVATE_TX_LOOP_MODE_COMPLETE PHY Data SDU for this message is described in Table F.6.5.2-1. Table F.6.5.2-1: ACTIVATE_TX_LOOP_MODE_COMPLETE message Field Octet Description message_code 0 Message code, set to ACTIVATE_TX_LOOP_MODE_COMPLETE status 1 Request status, values: 0: success 1: failure 2-255: reserved data 2β¦(TBS-1) Set to zero F.6.5.3 ACTIVATE_RX_LOOP_MODE PHY Data SDU for this message is described in Table F.6.5.3-1. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 73 Table F.6.5.3-1: ACTIVATE_RX_LOOP_MODE message Field Octet Description message_code 0 Message code, set to ACTIVATE_RX_LOOP_MODE loop_mode_type 1 Reception loop mode type, values: 0: Receive loop mode, data field in response packet set to zeros 1: Receive loop mode, data field in response packet from random PN15 sequence 2-255: reserved loop_channel 2-3 Channel on which the measurement is to take place. Value: absolute channel frequency number as defined in ETSI TS 103 636-2 [1]. loop_start_delay 4 Reception start time in subslots as delta to the STF of the ACTIVATE_RX_LOOP_MODE message. packet_response_delay 5 Response delay in subslots as delta to the STF of the RX_LOOP_MODE_DATA message to the STF of the RX_LOOP_MODE_DATA_RESPONSE. SS shall not configure delay which exceeds EUT declared HARQ feedback delay ETSI TS 103 636-4 [3], clause 6.4.3.5. EUT HARQ feedback delay is declared in PICS info. plcf_type 6 PLCF Type as in ETSI TS 103 636-4 [3], clause 6.2, values 0: reserved 1: type 1 2: type 2 3-255: reserved plcf 7..11 or 7..16 PLCF as in ETSI TS 103 636-4 [3], clause 6.2. specifies the transmission format and transmission power EUT should use in response transmissions. Short Network ID, Transmitter Identity and Receiver Identity in EUT transmissions shall be set specified in clause F.3.2, values in these fields shall be disregarded. DF Redundancy version, DF New Data Indication, HARQ process number, Feedback format and Feedback Info in EUT transmissions shall be set by EUT, thus these fields shall be disregarded. data β¦(TBS-1) Set to zero F.6.5.4 ACTIVATE_RX_LOOP_MODE_COMPLETE PHY Data SDU for this message is described in Table F.6.5.4-1. Table F.6.5.4-1: ACTIVATE_RX_LOOP_MODE_COMPLETE message Field Octet Description message_code 0 Message code, set to ACTIVATE_RX_LOOP_MODE_COMPLETE status 1 Request status, values: 0: success 1: unspecified error 2: loop channel not supported 3: loop start delay not supported 4: packet response delay not supported 5: plcf type not supported 6: transmission type specified for response not supported 7-255: reserved data 2β¦(TBS-1) Set to zero F.6.5.5 DEACTIVATE_LOOP_MODE PHY Data SDU for this message is described in Table F.6.5.5-1. Table F.6.5.5-1: DEACTIVATE_LOOP_MODE message Field Octet Description message_code 0 Message code, set to DEACTIVATE_LOOP_MODE data 1β¦(TBS-1) Set to zero ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 74 F.6.6 Loop report messages F.6.6.1 REPORT_TX_LOOP_MODE PHY Data SDU for this message is described in Table F.6.6.1-1. Table F.6.6.1-1: REPORT_TX_LOOP_MODE message Field Octet Description message_code 0 Message code, set to REPORT_TX_LOOP_MODE status 1 Operation status, values: 0: success 1: failure 2-255: reserved transmitted_packet_count 2β¦5 Number of transmitted packets data 6β¦(TBS-1) Set to zero F.6.6.2 REPORT_RX_LOOP_MODE PHY Data SDU for this message is described in Table F.6.6.2-1. Table F.6.6.2-1: REPORT_RX_LOOP_MODE message Field Octet Description message_code 0 Message code, set to REPORT_RX_LOOP_MODE or status 1 Request status, values: 0: success 1: failure 2-255: reserved average_rssi_2 2 RSSI-2 averaged as specified in clause F.4.4.2. Value: RSSI-2 measurement reported value as defined in ETSI TS 103 636-2 [1]. average_snr 3 SNR averaged as specified in clause F.4.4.2. Value: SNR measurement reported value as defined in ETSI TS 103 636-2 [1]. received_packet_count 4β¦7 Number of correctly received packets during the measurement data 8β¦(TBS-1) Set to zero F.6.7 Loop action messages F.6.7.1 General Transmit loop action messages are sent by EUT. Receive loop action messages are sent by the SS and responded to by the EUT. The PDU of a loop message may give instructions to the EUT regarding the loop execution. F.6.7.2 TX_LOOP_MODE_DATA PHY Data SDU for this message is described in Table F.6.7.2-1. Table F.6.7.2-1: TX_LOOP_MODE_DATA message Field Octet Description message_code 0 Message code, set to TX_LOOP_MODE_DATA data 1β¦(TBS-1) Random from PN15 sequence ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 75 F.6.7.3 RX_LOOP_MODE_DATA PHY Data SDU for this message is described in Table F.6.7.3-1. Table F.6.7.3-1: RX_LOOP_MODE_DATA message Field Octet Description message_code 0 Message code, set to RX_LOOP_MODE_DATA data 3β¦(TBS-1) Random from PN15 sequence F.6.7.4 RX_LOOP_MODE_DATA_RESPONSE PHY Data SDU for this message is described in Table F.6.7.4-1. Table F.6.7.4-1: RX_LOOP_MODE_ DATA_RESPONSE message Field Octet Description message_code 0 Message code, set to RX_LOOP_MODE_DATA_RESPONSE rssi_2 1 RSSI-2 measurement of the packet being responded to. Value: RSSI-2 measurement reported value as defined in ETSI TS 103 636-2 [1]. snr 2 SNR measurement of the packet being responded to. Value: SNR measurement reported value as defined in ETSI TS 103 636-2 [1]. data 3β¦(TBS-1) Either zeros or from PN15 sequence as specified in ACTIVATE_RX_LOOP_MODE message in clause F.6.5.3. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 76 Annex G (normative): Radio ICS pro forma for DECT-2020 NR Equipment G.0 The right to copy Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the Protocol ICS pro forma in this annex so that it can be used for its intended purposes and may further publish the completed Protocol ICS. G.1 Introduction The purpose of a PICS is to identify those standardized functions which an EUT shall support, those which are optional and those which are conditional on the presence of other functions. It helps to identify which functions an EUT will support when performing conformance testing. It is possible that with different choices in an ICS pro forma, several different sets of test cases will be necessary. Item column The item column contains a number which identifies the item in the table. Item description column The item description column describes in free text each respective item (e.g. parameters, timers, etc.). It implicitly means "is <item description> supported by the implementation?". Reference column The reference column gives reference to the relevant DECT-2020 NR core specifications. Release column The release column indicates the earliest release from which the capability or option is relevant. Mnemonic column The Mnemonic column contains mnemonic identifiers for each item. Status column The status column makes assessments on whether requirements, features, components and other capabilities are required according to a referenced standard and in order to achieve compliance. This assessment provides the following options: m mandatory β the capability shall be supported. o optional β the capability may or may not be supported. c.i conditional β the requirement on the capability ("m", "o", "n/a") depends on the support of other optional or conditional items. "I" is an integer identifying a unique conditional status expression which is defined immediately following the table. n/a not applicable β in the given context, it is not possible to use the capability. o.i qualified optional β for mutually exclusive or selectable options from a set: "i" is an integer which identifies a unique group of related optional items and the logic of their selection which is defined immediately following the table. References to items The mnemonics are used to reference items in the tables. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 77 Prerequisite The items of the current table shall only be filled if the referenced item in the prerequisite indicates a true value. G.2 Pro forma tables G.2.1 Baseline Implementation Capabilities Table G.2.1-1: DECT-2020 NR Operating Bands Supported Item Operating Band Reference Mnemonic Status 1 DECT-2020 NR Frequency band 1 ETSI TS 103 636-2, clause 5.2 pc_dect_band1 o.1 2 DECT-2020 NR Frequency band 2 ETSI TS 103 636-2, clause 5.2 pc_dect_band2 o.1 3 DECT-2020 NR Frequency band 3 ETSI TS 103 636-2, clause 5.2 pc_dect_band3 o.1 4 DECT-2020 NR Frequency band 4 ETSI TS 103 636-2, clause 5.2 pc_dect_band4 o.1 5 DECT-2020 NR Frequency band 5 ETSI TS 103 636-2, clause 5.2 pc_dect_band5 o.1 6 DECT-2020 NR Frequency band 6 ETSI TS 103 636-2, clause 5.2 pc_dect_band6 o.1 7 DECT-2020 NR Frequency band 7 ETSI TS 103 636-2, clause 5.2 pc_dect_band7 o.1 8 DECT-2020 NR Frequency band 8 ETSI TS 103 636-2, clause 5.2 pc_dect_band8 o.1 9 DECT-2020 NR Frequency band 9 ETSI TS 103 636-2, clause 5.2 pc_dect_band9 o.1 10 DECT-2020 NR Frequency band 10 ETSI TS 103 636-2, clause 5.2 pc_dect_band10 o.1 11 DECT-2020 NR Frequency band 11 ETSI TS 103 636-2, clause 5.2 pc_dect_band11 o.1 12 DECT-2020 NR Frequency band 12 ETSI TS 103 636-2, clause 5.2 pc_dect_band12 o.1 13 DECT-2020 NR Frequency band 13 ETSI TS 103 636-2, clause 5.2 pc_dect_band13 o.1 14 DECT-2020 NR Frequency band 14 ETSI TS 103 636-2, clause 5.2 pc_dect_band14 o.1 15 DECT-2020 NR Frequency band 15 ETSI TS 103 636-2, clause 5.2 pc_dect_band15 o.1 16 DECT-2020 NR Frequency band 16 ETSI TS 103 636-2, clause 5.2 pc_dect_band16 o.1 17 DECT-2020 NR Frequency band 17 ETSI TS 103 636-2 , clause 5.2 pc_dect_band17 o.1 18 DECT-2020 NR Frequency band 18 ETSI TS 103 636-2, clause 5.2 pc_dect_band18 o.1 19 DECT-2020 NR Frequency band 19 ETSI TS 103 636-2, clause 5.2 pc_dect_band19 o.1 20 DECT-2020 NR Frequency band 20 ETSI TS 103 636-2, clause 5.2 pc_dect_band20 o.1 21 DECT-2020 NR Frequency band 21 ETSI TS 103 636-2, clause 5.2 pc_dect_band21 o.1 22 DECT-2020 NR Frequency band 22 ETSI TS 103 636-2, clause 5.2 pc_dect_band22 o.1 o.1: It is mandatory to support at least one of these items. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 78 Table G.2.1-2: Special Conformance Testing Functions Item Special Conformance Testing Function Reference Mnemonic Status 1 EUT special conformance test functions ETSI TS 104 407-1, Annex F pc_phycf_test_functions m 2 EUT capability to transmit without STF cover sequence for testing purposes ETSI TS 104 407-1, clause 5.2 pc_phycf_tx_wo_stfcs o.1 Table G.2.1-3: DECT-2020 NR Radio Device Class G.2.2 PHY Implementation Capabilities Table G.2.2-1: PHY numerology support Table G.2.2-2: PHY Modulation and Coding Support Item Radio Device Class Reference Mnemonic Status 1 Class I ETSI TS 103 636-2, clause 6.2.1 pc_rd_class1 o.1 2 Class II ETSI TS 103 636-2, clause 6.2.1 pc_rd_class2 o.1 3 Class III ETSI TS 103 636-2, clause 6.2.1 pc_rd_class3 o.1 4 Class IV ETSI TS 103 636-2, clause 6.2.1 pc_rd_class4 o.1 o.1: It is mandatory to support at least one of these items. Item PHY Numerologies Reference Mnemonic Status 1 = 1, = 1 ETSI TS 103 636-3, clause 4.3 pc_phy_num_mu1_beta1 o.1 2 = 1, = 2 ETSI TS 103 636-3, clause 4.3 pc_phy_num_mu1_beta2 o.1 3 = 1, = 4 ETSI TS 103 636-3, clause 4.3 pc_phy_num_mu1_beta4 o.1 4 = 2, = 1 ETSI TS 103 636-3, clause 4.3 pc_phy_num_mu2_beta1 o.1 5 = 2, = 2 ETSI TS 103 636-3, clause 4.3 pc_phy_num_mu2_beta2 o.1 6 = 4, = 1 ETSI TS 103 636-3, clause 4.3 pc_phy_num_mu4_beta1 o.1 o.1: It is mandatory to support at least one of these items. Item Modulation and Coding Support Reference Mnemonic Status 1 MCS0 ETSI TS 103 636-3, Annex A; ETSI TS 103 636-4], clause 6.2.1 pc_phy_mcs0 m 2 MCS1 ETSI TS 103 636-3, Annex A; ETSI TS 103 636-4, clause 6.2.1 pc_phy_mcs1 m 3 MCS2 ETSI TS 103 636-3, Annex A; ETSI TS 103 636-4, clause 6.2.1 pc_phy_mcs2 o.1 4 MCS3 ETSI TS 103 636-3, Annex A; ETSI TS 103 636-4, clause 6.2.1 pc_phy_mcs3 o.1 5 MCS4 ETSI TS 103 636-3, Annex A; ETSI TS 103 636-4, clause 6.2.1 pc_phy_mcs4 o.1 6 MCS5 ETSI TS 103 636-3, Annex A; ETSI TS 103 636-4, clause 6.2.1 pc_phy_mcs5 o.1 7 MCS6 ETSI TS 103 636-3, Annex A; ETSI TS 103 636-4, clause 6.2.1 pc_phy_mcs6 o.1 8 MCS7 ETSI TS 103 636-3, Annex A; ETSI TS 103 636-4, clause 6.2.1 pc_phy_mcs7 o.1 9 MCS8 ETSI TS 103 636-3, Annex A; ETSI TS 103 636-4,clause 6.2.1 pc_phy_mcs8 o.1 10 MCS9 ETSI TS 103 636-3, Annex A; ETSI TS 103 636-4, clause 6.2.1 pc_phy_mcs9 o.1 11 MCS10 ETSI TS 103 636-3, Annex A; ETSI TS 103 636-4, clause 6.2.1 pc_phy_mcs10 o.1 12 MCS11 ETSI TS 103 636-3, Annex A; ETSI TS 103 636-4, clause 6.2.1 pc_phy_mcs11 o.1 o.1: Implies support of all lower order of MCSs. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 79 Table G.2.2-3: PHY MIMO Spatial Stream Support Table G.2.2-4: PHY Number of HARQ Processes Support Table G.2.2-5: PHY Soft Buffer Size Support Table G.2.2-6: PHY Packet Length Support Item Packet Length Reference Mnemonic Status 1 1 subslot ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss1 m 2 2 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss2 m 3 3 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss3 o.1 4 4 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss4 o.1 Item Maximum number of spatial streams Reference Mnemonic Status 1 Single spatial stream ETSI TS 103 636-3, clause 7.2; ETSI TS 103 636-4, clause 6.2.1 pc_phy_mimo_ss1 m 2 Two spatial streams ETSI TS 103 636-3, clause 7.2; ETSI TS 103 636-4, clause 6.2.1 pc_phy_mimo_ss2 o.1 3 Four spatial stream ETSI TS 103 636-3, clause 7.2; ETSI TS 103 636-4, clause 6.2.1 pc_phy_mimo_ss4 o.1 4 Eight spatial streams ETSI TS 103 636-3, clause 7.2; ETSI TS 103 636-4, clause 6.2.1 pc_phy_mimo_ss8 o.1 o.1: Implies support of lower order of spatial streams. Item Number of HARQ processes Reference Mnemonic Status 1 Single process ETSI TS 103 636-3, clause 6.1.5 and Annex B pc_phy_harq_nps1 m 2 Two process ETSI TS 103 636-3, clause 6.1.5 and Annex B pc_phy_harq_nps2 o.1 3 Four process ETSI TS 103 636-3, clause 6.1.5 and Annex B pc_phy_harq_nps4 o.1 4 Eight process ETSI TS 103 636-3, clause 6.1.5 and Annex B pc_phy_harq_nps8 o.1 o.1: Implies support of lower order of HARQ processes. Item Soft buffer size Reference Mnemonic Status 1 16k ETSI TS 103 636-3, clause 6.1.5 and Annex B pc_phy_harq_soft16k o.1 2 25k ETSI TS 103 636-3, clause 6.1.5 and Annex B pc_phy_harq_soft25k o.1 3 32k ETSI TS 103 636-3, clause 6.1.5 and Annex B pc_phy_harq_soft32k o.1 4 64k ETSI TS 103 636-3, clause 6.1.5 and Annex B pc_phy_harq_soft64k o.1 5 128k ETSI TS 103 636-3, clause 6.1.5 and Annex B pc_phy_harq_soft128k o.1 6 256k ETSI TS 103 636-3, clause 6.1.5 and Annex B pc_phy_harq_soft256k o.1 7 512k ETSI TS 103 636-3, clause 6.1.5 and Annex B pc_phy_harq_soft512k o.1 8 1M ETSI TS 103 636-3, clause 6.1.5 and Annex B pc_phy_harq_soft1M o.1 9 2M ETSI TS 103 636-3, clause 6.1.5 and Annex B pc_phy_harq_soft2M o.1 o.1: It is mandatory to support at least one of these items. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 80 Item Packet Length Reference Mnemonic Status 5 5 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss5 o.1 6 6 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss6 o.1 7 7 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss7 o.1 8 8 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss8 o.1 9 9 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss9 o.1 10 10 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss10 o.1 11 11 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss11 o.1 12 12 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss12 o.1 13 13 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss13 o.1 14 14 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss14 o.1 15 15 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss15 o.1 16 16 subslots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_ss16 o.1 17 1 slot ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl1 o.1 18 2 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl2 o.1 19 3 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl3 o.1 20 4 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl4 o.1 21 5 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl5 o.1 22 6 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl6 o.1 23 7 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl7 o.1 24 8 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl8 o.1 25 9 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl9 o.1 26 10 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl10 o.1 27 11 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl11 o.1 28 12 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl12 o.1 29 13 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl13 o.1 30 14 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl14 o.1 31 15 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl15 o.1 32 16 slots ETSI TS 103 636-3, clause 5.1; ETSI TS 103 636-4, clause 6.2.1 pc_phy_len_sl16 o.1 o.1: Implies support of all shorter packet lengths for given numerology. ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 81 Annex H (informative): Change history Date Version Information about changes April 2024 V0.0.1 Early draft June 2024 V0.0.2 DECT(24)000140r1 - Radio conformance, test mode DECT(24)000141 - Radio conformance, transmit power DECT(24)000142 - Radio conformance, transmit signal quality DECT(24)000143 - Radio conformance, transmit spectrum emissions DECT(24)000144 - Radio conformance, receiver dynamic range and selectivity DECT(24)000145 - Radio conformance, receiver blocking characteristics DECT(24)000146 - Radio conformance, receiver intermodulation characteristics DECT(24)000147r1 - Radio conformance, receiver spectrum emissions DECT(24)000148r1 - Radio conformance, receiver measurements DECT(24)000152r3 - Radio conformance, connection diagrams August 2025 V0.0.3 DECT(25)000164 September 2025 V0.0.4 DECT(25)000184 September 2025 V0.0.5 DECT(25)000203 ETSI ETSI TS 104 047-1 V1.1.1 (2025-10) 82 History Version Date Status V1.1.1 October 2025 Publication
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
1 Scope
|
The present document defines Test Purposes for ETSI TS 103 962 [1] and ETSI TS 103 963 [2] written in the format of a TSS&TP using the notation TPLan (ETSI ETR 266 [i.8], ETSI ES 202 553 [3]) extended to address the description of test purposes taking into account requirements from Common Criteria Part 2 [8]. The latter is necessary to support conformity to the EUCC programme (for each of CRA [i.1] and NIS2 [i.2] in addition to the CSA [i.3]).
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
2 References
| |
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
2.1 Normative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 103 962: "CYBER; Optical Network and Device Security; Security provisions in Optical Access Network Devices". [2] ETSI TS 103 963: "CYBER; Optical Network and Device Security; Security provisions in transport network devices". [3] ETSI ES 202 553: "Methods for Testing and Specification (MTS); TPLan: A notation for expressing Test Purposes". [4] ETSI TS 103 924: "Optical Network and Device Security; Catalogue of Requirements". [5] ETSI TS 103 961: "CYBER; Optical Network and Device Security; Security provisions for the management of Optical Network devices and services". [6] ETSI TS 102 165-2: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Methods and protocols; Part 2: Protocol Framework Definition; Security Counter Measures". NOTE: This deliverable is being updated and the relevant clause numbering will be retained. [7] Common Criteria CCMB-2022-11-006: "Common Methodology for Information Technology", Security Evaluation, November 2022, Revision 1. [8] Common Criteria CCMB-2022-11-002: "Common Criteria for Information Technology Security Evaluation; Part 2: Security functional components", November 2022, Revision 1.
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. ETSI ETSI TS 103 993 V1.1.1 (2025-09) 8 [i.1] Regulation (EU) 2024/2847 of the European Parliament and of the Council of 23 October 2024 on horizontal cybersecurity requirements for products with digital elements and amending Regulations (EU) No 168/2013 and (EU) 2019/1020 and Directive (EU) 2020/1828 (Cyber Resilience Act). [i.2] Directive (EU) 2022/2555 of the European Parliament and of the Council of 14 December 2022 on measures for a high common level of cybersecurity across the Union, amending Regulation (EU) No 910/2014 and Directive (EU) 2018/1972, and repealing Directive (EU) 2016/1148 (NIS 2 Directive). [i.3] Regulation (EU) 2019/881 of the European Parliament and of the Council of 17 April 2019 on ENISA (the European Union Agency for Cybersecurity) and on information and communications technology cybersecurity certification and repealing Regulation (EU) No 526/2013 (Cybersecurity Act). [i.4] ETSI TS 103 996: "Cyber Security (CYBER); ONDS Protection profile - Test cases". [i.5] ETSI TS 104 013: "Cyber Security (CYBER); ONDS PP for ONDS management protocols and services". [i.6] ETSI TR 103 866: "Cyber Security (CYBER); Implementation of the Revised Network and Information Security (NIS2) Directive applying Critical Security Controls". [i.7] ETSI TS 102 165-3: "Cyber Security (CYBER); Methods and Protocols for Security Part 3: Vulnerability Assessment extension for TVRA". [i.8] ETSI ETR 266: "Methods for Testing and Specification (MTS); Test Purpose style guide". [i.9] Common Criteria CEM-2001/0015R: "Common Methodology for Information Technology Security Evaluation Part 2: Evaluation Methodology", Supplement: ALC_FLR - Flaw Remediation. [i.10] ETSI TS 103 486: "CYBER; Identity Management and Discovery for IoT". [i.11] NIST SP 800-63B: "Digital Identity Guidelines Authentication and Lifecycle Management".
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
3 Definition of terms, symbols and abbreviations
| |
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI ES 202 553 [3] apply.
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
3.2 Symbols
|
Void.
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AC Access Control CC Common Criteria CIA Confidentiality Integrity Availability DPIA Data Protection Impact Assessment EAL Evaluation Assurance Level ECC Error Correcting Code EUCC EU Common Criteria Certification Scheme FIPS Federal Information Processing Standard GDPR General Data Protection Regulation ETSI ETSI TS 103 993 V1.1.1 (2025-09) 9 HW Hardware ICS Implementation Conformance Statement ICV Integrity Check Value IUT Implementation Under Test L2TP Layer 2 Tunneling Protocol MAC Message Authentication Code OAN Optical Access Network OLT Optical Line Terminal ON Optical Network OND Optical Network Device ONDS Optical Network Device Security ONDS-M Optical Network Device Security - Management entity OTN Optical Transport Network PICS Protocol ICS PP Protection Profile RAM Random Access Memory RoT Root of Trust RTS Root of Trust for Storage RtS Root of Trust for Storage RTV Root of Trust for Verification SAR Security Assurance Requirement NOTE: From CCMB-2022-11-002 [8]. SBOM Software Bill of Materials SFR Security Functional Requirement NOTE: From CCMB-2022-11-002 [8]. TOE Target of Evaluation TP Test Purpose TSF TOE Security Function TSS Test Suite Structure TVP Time Variant Parameter TVRA Threat Vulnerability Risk Analysis VPN Virtual Private Network
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
4 Review of base standard
|
As outlined in each of ETSI TS 103 962 [1] and ETSI TS 103 963 [2], Table 1 identifies, for each statement of the PICS in ETSI TS 103 962 [1] and ETSI TS 103 963 [2], the nature of the test to verify conformance to the requirement. Where conformance can be verified by an automated test to identify a pass or fail verdict the PICS statement is labelled as "conformance". In the case that conformance to the requirement cannot be determined by an automated test, but rather would require examination of design documentation, some form of open box testing, or some other form of expert evaluation, the PICS statement is labelled as "evaluation". Table 1: Assessment of test mode for each PICS statement from ETSI TS 103 962 [1] and ETSI TS 103 963 [2] Item Requirement Status Evaluation/ Conformance Req-1 An access device shall distinguish and keep separate the user and network domains in the device. M Evaluation Req-2 ON systems shall be designed to be secure by default and to support the functionality required by the CIA paradigm. M Evaluation Req-3 At initialization and at runtime all links shall be established and security associations created within the trust and security policy established by the operator of the equipment/network. M Conformance Req-4 Any link enabled during, and post-initialization, shall support periodic re-establishment of the security association. M Conformance Req-5 The principles of least privilege and least persistence shall apply to all security associations. M Evaluation Conformance ETSI ETSI TS 103 993 V1.1.1 (2025-09) 10 Item Requirement Status Evaluation/ Conformance Req-6 In accordance with the least persistence principle security associations shall not be maintained for longer than required. M Evaluation Req-7 If any software verification fails that software and any supporting elements shall not participate in any security association. M Conformance Req-8 All ON entities shall be able to report the form of CIA protections that are available and operational to authorized entities. M Conformance (management) Req-9 An OAN device shall be integrated to the wider ON and telecommunications system of which it is a component. M Evaluation Req-10 An OAN device shall consist of at least 1 (one) execution environment. M Evaluation Req-11 An OAN device's execution environment shall have 1 (one) initial root of trust. M Evaluation Req-12 The execution environment shall have at least one executable code block. M Evaluation Req-13 There should be a discrete execution environment for each side and discrete roots of trust for each side. R Evaluation Req-14 If an OAN device supports a multi-occupancy client environment it shall provide confidentiality services at the client side to ensure physical and cryptographic separation of distinct clients. M C Evaluation (conformance (see note 1)) Req-15 The OAN Device shall have a root of trust used for initialisation to enable secure boot capabilities. M Evaluation Req-16 The OAN Device shall implement a root of trust where the scope of functions enabled by the root of trust shall be defined in succeeding clauses of the present document. M Evaluation (see note 2) Req-17 The guidelines given in NIST SP 800-164 [i.3] shall be followed in order to provide the following local (device specific) trust services: Root of Trust for Storage (RTS); Root of Trust for Verification (RTV); Policy Enforcement Engine. M Evaluation Req-18 The manufacturer of the OAN Device shall attest to the provision of the root of trust by reference to the method applied. M Evaluation Req-19 The manufacturer of the OAN Device shall publish the attestation of the provision of the root of trust in the technical specification of the OAN Device. M Evaluation Req-20 The presence of the hardware root of trust shall be asserted by a platform specific attribute certificate. M Evaluation Conformance (management (see note 3)) Req-21 All cryptographic modules shall be designed to be crypto-agile. M Conformance Req-22 The specific cryptographic algorithms for each security association shall be defined by the security policy. M Conformance Req-23 Cryptographic algorithms should be sufficient to inhibit known cryptanalysis attacks and mechanisms. R Evaluation Req-24 The broad assumption that the key is secure applies and therefore advice on exploits of key material should be made available and key update mechanisms implemented to inhibit attacks using such exploited key material. R Evaluation Req-25 The security processes shall be self-monitoring and report detected errors to the local security authority which may in turn report errors to a remote, central, security authority. M Conformance Req-26 All ON devices shall be identified with a canonical/root identity and, optionally, additional semantic identifiers identifying their functional nature. M Conformance Req-27 Where provided, the semantic identifier shall be used to indicate the functional nature of the entity. M C Conformance Req-28 The attestation of function shall be verifiable by reference to a 3rd party. M Conformance Req-29 The authentication process shall verify the ON entity's identity (e.g. a globally unique device address) to a shared key assignment M Conformance Req-30 The to be authenticated identity shall be an attribute of the authentication protocol. M Conformance Req-31 The identity shall always be authenticated on first presentation and periodically thereafter. M Conformance Req-32 In order to be consistent with the principle of least persistence an authenticated session shall expire after a set time. M Evaluation Conformance (see note 4) ETSI ETSI TS 103 993 V1.1.1 (2025-09) 11 Item Requirement Status Evaluation/ Conformance Req-33 The length of an authentication session shall be set by the Authentication-Session-Time-Limit variable. M Conformance Req-34 The Authentication-Session-Time-Limit variable shall be established for each security association. M Conformance Req-35 A device shall be identified in order to be admitted to the operator's trust domain. M Conformance Req-36 Within the trust domain the trust domain manager shall verify the capability of each device. M Conformance Req-37 An ON device shall present an identifier to each of the client and the network side of the device. M Conformance Evaluation (see note 12) Req-38 It should not be feasible to determine/infer the identifier presented to one side from knowledge of the identifier presented to the other side. R Evaluation (see note 5) Req-39 Any identifier presented by the device shall be authenticated by the receiving device. M Conformance Req-40 A key shall be associated to an attribute or identifier of the OAN Device. M Conformance Req-41 The binding of key to the attribute or identifier shall be maintained for each security association. M Conformance Req-42 A symmetric keyed security association shall identify the following elements: Associated identity or Associated capability; Root key-id (if part of a key hierarchy); CIA purpose (one of authentication, encryption, integrity); Algorithm. M Conformance Req-43 A Message Authentication Code (MAC) method should be used in established security associations as an alternative to simple integrity check functions where the integrity, MAC, key is pre- defined or established as a session specific key. R Conformance Evaluation (note 6) Req-44 The MAC approach to authentication as outlined in ETSI TS 102 165-2 [6] shall apply. M Evaluation Req-45 Random challenges used in any MAC based authentication shall be generated using a true source of randomness. M Evaluation Req-46 Software only functions shall not be used to generate random challenges. M Evaluation Req-47 A challenge-response method should be used at initialisation and for key establishment, key refresh, events. R Evaluation Req-48 Only cryptographically relevant challenge response schemes shall be used. M Evaluation Req-49 The challenge response approach to authentication as outlined in ETSI TS 102 165-2 [6] shall apply. M Evaluation Req-50 Random challenges used in any challenge-response protocol shall be generated using a true source of randomness. M Evaluation Req-51 A device should only be able to perform a self-attestation of its identity at initialisation. R Evaluation Req-52 The self-attestation shall be provided in the form of a digital signature and include a signed public key. M C Conformance Req-53 In order to perform self-attestation of identity the OAN device shall be able to securely generate cryptographic keys associated with identifiers, and to securely store the private cryptographic material. M C Evaluation (see note 7) Req-54 The OAN device shall have a source of true randomness with entropy at least equal to the required security strength of the cryptographic operations that rely upon this randomness. M Evaluation Req-55 The OAN device shall have a root of trust for storage to store private cryptographic material (private key). M Evaluation (see note 7) Req-56 In accordance with ETSI TS 103 486 [i.10] the identity (canonical) and identifying attributes of a device should be attested to by an appropriate independent 3rd party. R Conformance Req-57 Proofs of identity shall be made available to corresponding parties using identity based public key certificates that clearly identify the attesting authority and that are able to resolve to the Root Authority for the trust domain. M Conformance Req-58 A device should only be able to perform a self-attestation of its capability at initialisation. R C Evaluation Req-59 The self-attestation shall be provided in the form of a digital signature and include a self-signed public key. M C Conformance ETSI ETSI TS 103 993 V1.1.1 (2025-09) 12 Item Requirement Status Evaluation/ Conformance Req-60 Identifying attributes of a device should be attested to by an independent 3rd party. The public key of the relevant attribute authority should be installed locally to the device. R Conformance Req-61 Proofs of identity shall be made available to corresponding parties using an attribute based public key certificate that clearly identify the attesting authority and that are able to resolve to the Root Authority for the trust domain. R Conformance Req-62 All exchanged discrete messages shall have their integrity verified on reception at the device. M Conformance Req-63 The integrity check function shall be cryptographically strong and may be included in a MAC for symmetric keyed associations, or in a digital signature for asymmetric keyed associations. M Evaluation Req-64 Any message that fails the integrity check shall be discarded and an error reported. M Conformance Req-65 In order to mitigate against replay attacks a Time Variant Parameter (TVP) should be included with the plaintext prior to calculation of the Integrity Check Value (ICV). R Conformance Req-66 All transmissions made from the OLT towards the network should be protected by a confidentiality security association. R Conformance Req-67 Where used the security association should identify: The encryption algorithm; The mode used for application of the algorithm; the end points. R C Conformance Req-68 Where the chosen encryption mode requires a per-block variant parameter (e.g. in counter mode) the means to establish the initial value and increment the variant parameter shall be stated in the security association. M C Evaluation (see note 8) Conformance Req-69 Every access device shall have a root of trust for storage (RtS). M Evaluation (see notes 1 and 2) Req-70 For an access device there should be independent RtSs for the user/client side and for the network side of the device. R Evaluation Req-71 All data in OAN devices shall be made available to authorized entities using the principle of least privilege. M Conformance (see note 9) Req-72 The access control mechanism shall follow the policy model outlined in ETSI TS 102 165-2 [6]. M Evaluation Req-73 Each protected Object in the OAN device shall be protected by an access control policy. M Evaluation (see note 10) Req-74 The access control policy shall be evaluated on each access attempt. M Conformance Req-75 The policy shall consist of 1 or more rules each of which shall be evaluated in turn. M Conformance Req-76 Every denied access attempt shall be recorded. M Conformance Req-77 The record of each denied access attempt shall include at least the following: subject-identifier; object-identifier; date/time of failed access attempt; logical and (if available) physical location of the object; if available the logical and physical location of the subject. M Conformance ETSI ETSI TS 103 993 V1.1.1 (2025-09) 13 Item Requirement Status Evaluation/ Conformance Req-78 If an object has multiple access control errors the OAN device, in collaboration with the ONDS-M, shall set a reporting threshold for making an exception report. M Conformance Req-79 If any rule fails because it cannot be determined (the calculation cannot be made for any reason) permission shall not be granted and an exception raised. M Conformance Req-80 If an exception is raised it shall include the details of the rule that failed. M Conformance Req-81 The default access control condition for all objects shall be "do not allow"/"do not permit". M Conformance Req-82 The following rules shall be implemented in OAN devices: CFG-AC; CK-AC; DEV-AC; PAC-AC. The rules are detailed in ETSI TS 103 962 [1] M Conformance (see note 11) Req-83 The overall access control policy should be defined in such a way that all rules of a policy have to pass in order to permit access. R Conformance Req-84 A policy shall only set access control permission to True where all rules of any policy pass M Conformance NOTE 1: For Req-14 where it is required to demonstrate physical and cryptographic separation of distinct clients in the case of a multi-occupancy client environment it may be necessary to evaluate the design documentation to assess that the capability exists and also perform automated conformance tests to verify the underlying function. NOTE 2: For Req-16 the existence of the root of trust and where it is applied shall be verified against the design documentation which shall clearly identify when it is invoked and for what purpose. NOTE 3: For Req-20 the presence of the hardware root of trust may also be verified by demonstration of conformance to an evaluated PP for the root of trust. NOTE 4: In Req-32 the rationale for the expiry time and its justification is expected to be subject to review of the design documentation and the actual behaviour tested in an automated conformance test. NOTE 5: Req-38 asks that it should not be feasible to determine/infer the identifier presented to one side from knowledge of the identifier presented to the other side which may be demonstrated by examination of the design documentation that should illustrate the analysis that gives confidence the requirement is met. NOTE 6: In Req-43 the design documentation should make clear where a MAC is applied (the evaluation element of the test) and a conformance test can be used to verify the MAC operation. NOTE 7: For Req-53 this is an application of the RoT identified in Req-16 and Req-20. NOTE 8: Req-68 requires evaluation of the design documentation to validate the use of the chosen encryption mode and then conformance tests can be used to verify the operation. NOTE 9: For Req-71 conformance tests of the access control protocol and associated policies is expected. NOTE 10: For Req-73 the design documentation shall make clear what is addressed by the access control policy. NOTE 11: Req-82 requires that the specific rules are transposed to the access control model that is implemented. NOTE 12: Req-37 applies only for OAN devices, OTN devices do not present their identity to clients.
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
5 Test suite structure
|
The test suite structure is defined using TPLan (see ETSI ES 202 553 [3]). The TSS header shall be as below: TSS : ONDS_TSS title : 'TSS&TP for testing of ETSI TS 103 962 and TS 103 963' version : 1.0 date : xx.yy.2025 -- could also be written as xx/yy/2025 or xx-yy-2025 author : 'ETSI TC CYBER' Given the nature of security testing where in certain cases an absolute pass or fail judgement can be difficult to assign, the analysis identifies, for each test purpose, the evaluation criteria that applies in order to provide a pass or fail assignment. The terminology of Common Criteria Part 2 [8] is applied and the extension and application of TPLan that applies for the SFRs from Common Criteria that apply to the present document is given in Annex A. The base standards for the purpose of the present document are defined using the xref keyword as below. xref BaseStandards {TS1103962, TS103963} ETSI ETSI TS 103 993 V1.1.1 (2025-09) 14 Tests are grouped for the purposes of the present document using the structure of ETSI TS 103 962 [1] and ETSI TS 103 963 [2] as a guide and identified as follows: 1) Identification and authentication 2) Confidentiality and integrity protection of data transfer 3) Access control 4) Device provisions The further classification of tests into sub-groups follow the general classification in [1] and [2] for those requirements identified as "Conformance" in Table 1. A second set of groups and sub-groups is identified for the same broad groupings to address those requirements identified in Table 1 as "Evaluation". These groups and associated sub-groups are identified using TPLan as below and are specified for convenience of the tester. Group 1 addresses requirements 26 to 31, 33 to 37, 39 to 43, 52, 56-57, and 59-61 of [1] and [2]. group 1 'Identification and authentication' objective 'Verification of requirements from Clause 5 of xref' end group 1 'Identification and authentication' Group 2 addresses requirements 62 and 64-67 of [1] and [2]. group 2 'Confidentiality and integrity protection of data transfer' objective 'Verification of requirements from Clause 6 of xref' end group 2 'Confidentiality and integrity protection of data transfer' Group 3 addresses requirements 3-4, 7-8, 21-22 and 25 of [1] and [2]. group 3 'Access control' objective 'Verification of requirements from Clause 7 of xref' end group 1 'Access control' Group 4 addresses requirements β¦ of [1] and [2]. group 4 'Device provisions' objective 'Verification of requirements from Clause 4 of xref' end group 4 'Device provisions' Group 5 addresses those requirements identified in Table 1 as for "evaluation" and identify additional test purposes mapped to the Common Criteria (CC) Security Functional Requirements (SFRs) as outlined in Annex A. group 5 'Evaluation provisions' objective 'Verification of those requirements from xref that are marked for evaluation' end group 5 'Evaluation provisions'
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
6 Test purposes
| |
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
6.1 Overview
|
Each test purpose examines a requirement and identifies the objective of the test (written in the summary field), the particular requirement(s) that are being tested, and the configuration necessary to conduct the test. As outlined in ETSI ES 202 553 [3] each test is described by any necessary configuration and preconditions, and a series of stimuli and responses. Where extensions to TPLan are made as in the present clause these are added to the header (see ETSI ES 202 553 [3], clause C.2.3). ETSI ETSI TS 103 993 V1.1.1 (2025-09) 15
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
6.2 Configurations, keywords and preconditions
|
Many of the requirements identified in ETSI TS 103 962 [1] and ETSI TS 103 963 [2] can be summarized as providing preconditions within the test configuration. Thus the following requirements are identified as preconditions using the keyword "with": with {IUT 'having a canonical identifier'} -- Req-26 with {IUT 'having a semantic identifier'} -- Req-27 with {IUT 'having a semantic identifier attested to by a 3rd party'} -- Req-28 with {IUT 'set a non-zero value for the Authentication-Session-Time-Limit variable'} -- Req-33 with {IUT 'having at least 1 (one) execution environment'} -- Req-10, Req-12 with {IUT 'having discrete execution environments for client and network'} -- Req-13 with {IUT 'having 1 initial root of trust'} -- Req-11, Req-16, Req-18, Req-19, Req-20 with {IUT 'having a root of trust to enable secure boot'} -- Req-15 with {IUT 'having a hardware based root of trust'} -- Req-54, Req-17 with {IUT 'having the root of trust for storage and verification'} -- Req-69, Req-70, Req-55 with {IUT 'having crypto-agile cryptographic modules'} -- Req-21 with {IUT 'having proof of presence of hardware root of trust'} -- Req-20 with {IUT 'having cryptographic algorithms robust against known cryptanalysis'} -- Req-23, with {IUT 'having a cryptographic key generation algorithm'} -- Req-53 with {IUT 'having generated a true random element'} - Req-45, 50, -54 with {IUT 'having a random value generator not based only on software'} -- Req-46 with {IUT 'having been designed to be secure by default'} -- Req-2 with {IUT 'having physical and cryptographic separation of tenants'} -- Req-1, Req-14 NOTE 1: Many other requirements may be satisfied by a combination of one or more of the above pre-conditions, for example Req-9 is satisfied by a combination of the requirements related to execution environment and the establishment of security associations (see clause 6.3.1). The following states are defined as conditions: def condition NotIdentified, Identified, NotAuthenticated, Authenticated def condition InAuthenticationSession The following timers and values are defined in order to ensure the principle of least persistence (Req-3, Req-5, Req-6) can be tested (these timers also satisfy Req-32, Req-33, and Req-34 (time limit) and each of Req-76, Req-78 and Req-81 (failure limit)): def value AuthenticationSessionTimeLimit '600' β Default value of authentication session in seconds def value AuthenticationAttemptFailureLimit '3' - Default value for number of allowed auth fails def value AccessAttemptFailureLimit '3' - Default value for number of allowed access control fails def value UserInactivityTimeLimit '120' - Default value of inactivity timeout in seconds def value AccessControl {Permit|Deny}'Deny' -- Default is that access is denied (Req-81) def value SecurityAssociationTimeLimit '120' -- (Req-6) NOTE 2: There is no defined value for the session time limit in [1] and [2], thus the value selected here is for testing purposes only. NOTE 3: There is no defined value for the number of times an access control or authentication attempt failure is tolerated [1] and [2], thus the value selected here is for testing purposes only. The following keywords are defined for the access control capabilities. def word verifies -- used when verifying, for example, an integrity check value def word discards -- used when a test or condition fails and no further processing is performed def word permit -- when access control determins that access is allowed def word deny -- when access control determins that access is not allowed def word encrypts -- for use in cases where content is encrypted by the IUT def word decrypts -- for use in cases where content is decrypted by the IUT def word evaluates -- used to test an access control policy or rule def word expires -- used to identify a timer has expired Where authentication is achieved by an exchange of messages the message shall contain the to be authenticated identity (Req-30). def event authentication-request -- For challenge response authentication (Req-45 through Req-50) def event authentication-response -- For challenge response authentication (Req-45 through Req-50) def event authentication-claim {} -- used to assert an identity (Req-43, Req-44) def event authentication-verification -- for verifying that authentication has succeeded ETSI ETSI TS 103 993 V1.1.1 (2025-09) 16 Many SFRs as described in Common Criteria Part 2 [i.4] are not easily mapped to the stimulus-response model of TPLan and the following additional header elements are defined to enable such a mapping to make sense by defining states that identify the pre- and post- conditions for the application of the identified SFRs. def event auditable-event-notification -- Used for Functional Class FAU (Security Audit) def event auditable-event-response -- Used for Functional Class FAU (Security Audit)
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
6.3 Test purposes per group
| |
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
6.3.1 Identification and authentication
|
TP Id ONDS-IA-001 Test Objective The identity shall always be authenticated on first presentation and periodically thereafter (the latter also is used to verify the operation of periodic re-establishment of a security association (here for authentication)) Reference REQ-31, REQ-30, REQ-4, REQ-8 (implicit), REQ-22, REQ-29 Configuration PICS Selection Initial conditions with {IUT in NotIdentified and NotAuthenticated} with {IUT 'having relevant algorithms and key formats defined in the security policy} Expected behaviour ensure that { when {IUT receives 'Startup' or 'Reauthentication timer expires'} then [IUT sends authentication-claim containing 'semantic or canonical identifier'} when {IUT receives authentication-verification} then {IUT in Authenticated and Identified} } NOTE: Requirement 8, that requires the reporting of the form of CIA protections is implicit in TP ONDA-IA-001.
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
6.3.2 Confidentiality and integrity protection of data transfer
|
TP Id ONDS-CI-001 Test Objective Verify that inbound messages contain an Integrity Check Value (ICV) that is tested for correctness whilst the authentication period is still valid Reference REQ-62, REQ-65 Configuration PICS Selection Initial conditions with {IUT in Identified and Authenticated} -- verifies that authentication period is valid Expected behaviour ensure that { when {the IUT receives 'any message' containing 'ICV' and containing 'TVP'} then {the IUT generates 'calculated-ICV'} β gives 'calculated-ICV' when {the IUT verifies 'calculated-ICV' is equal to 'ICV'} then {the IUT permits 'any message'} } TP Id ONDS-CI-002 Test Objective Verify that inbound messages contain an Integrity Check Value (ICV) that is tested for correctness whilst the authentication period is still valid and is discarded on ICV failure and an alert raised Reference REQ-64 Configuration PICS Selection Initial conditions with {IUT in Identified and Authenticated} -- verifies that authentication period is valid ETSI ETSI TS 103 993 V1.1.1 (2025-09) 17 Expected behaviour ensure that { when {the IUT receives 'any message' containing 'ICV' and containing 'TVP'} then {the IUT generates 'calculated-ICV'} when {the IUT verifies 'calculated-ICV' is not equal to 'ICV'} then {the IUT discards 'any message' and the IUT reports 'ICV verification error'} } TP Id ONDS-CI-003 Test Objective Verify that messages made from the OLT are protected by a confidentiality security association Reference REQ-66 Configuration PICS Selection Initial conditions with {IUT in Identified and Authenticated} -- verifies that authentication period is valid Expected behaviour ensure that { when {the IUT sends 'any message'} then {the IUT encrypts 'any message'} }
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
6.3.3 Access control
|
TP Id ONDS-AC-001 Test Objective Evaluate access control policy on each access attempt Reference REQ-74, REQ-82 (implicit) Configuration PICS Selection Initial conditions with {IUT in Identified and Authenticated} -- verifies that authentication period is valid Expected behaviour ensure that { when {IUT configuration-data is accessed} then {IUT evaluates 'if policy conditions are met'} when {evaluation is true} then {PERMIT} } TP Id ONDS-AC-002 Test Objective Record failed access attempt Reference REQ-76, REQ-77, REQ-79, REQ-80, REQ-82 (implicit) Configuration PICS Selection Initial conditions with {IUT in Identified and Authenticated} -- verifies that authentication period is valid Expected behaviour ensure that { when {IUT configuration-data is accessed} then {IUT evaluates 'if policy conditions are met'} when {evaluation is false} then {DENY and Record-access-control-error and 'Record rule that caused the error'} } ETSI ETSI TS 103 993 V1.1.1 (2025-09) 18 TP Id ONDS-AC-003 Test Objective Verify that all access control rules are tested and pass to allow access control as Permit Reference REQ-75, REQ-83, REQ-84 Configuration PICS Selection Initial conditions with {IUT in Identified and Authenticated and AccessControl is Deny} Expected behaviour ensure that { when {IUT 'protected data' is accessed and 'policy contains n rules'} then {IUT evaluates 'rule 1' and 'rule 2' and β¦ 'rule n'} when {evaluation is true} then {set AccessControl to Permit} }
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
6.3.4 Device provisions
|
TP Id ONDS-DEV-001 Test Objective If any software verification fails ensure that that software and any supporting elements shall not participate in any security association Reference REQ-7 Configuration PICS Selection Initial conditions with {IUT in Identified and Authenticated and AccessControl is Deny} Expected behaviour ensure that { when {IUT 'protected data' is accessed and 'policy contains n rules'} then {IUT evaluates 'rule 1' and 'rule 2' and β¦ 'rule n'} when {evaluation is true} then {set AccessContol to Permit} } TP Id ONDS-DEV-002 Test Objective To verify secure boot uses a root of trust Reference REQ-7 Configuration PICS Selection Initial conditions with {IUT in Identified and Authenticated and AccessControl is Deny} Expected behaviour ensure that { when {IUT 'protected data' is accessed and 'policy contains n rules'} then {IUT evaluates 'rule 1' and 'rule 2' and β¦ 'rule n'} when {evaluation is true} then {set AccessControl to Permit} }
|
cdcdc4f679e113535a93610fb5262d1d
|
103 993
|
6.3.5 Evaluation provisions
|
The majority of test purposes for requirements identified as for "evaluation" are defined as pre-conditions in clause 6.2. A small number of the "evaluation" requirements can only be assessed by detailed evaluation of the design documents (as identified in several requirements). In all cases the TPLan outlines given in the present document should be addressed by the evaluator alongside the guidance given in Common Criteria for Information Technology, Evaluation Methodology [7]. ETSI ETSI TS 103 993 V1.1.1 (2025-09) 19 Annex A (normative): TPLan extensions for ONDS and Common Criteria A.1 SFR structure The following SFR modules are identified as applicable to the present document from ETSI TS 103 962 [1] and ETSI TS 103 963 [2] and given in ETSI TS 103 996 [i.4]: β’ FAU_GEN.1.2 Audit data generation β’ FCS_CKM.1.1 Cryptographic key generation β’ FCS_CKM.2 Cryptographic key distribution β’ FCS_CKM.3 Cryptographic key access β’ FCS_CKM.6 Timing and event of cryptographic key destruction β’ FCS_COP.1.1 Cryptographic operation β’ FCS_RNG.1 Generation of random numbers β’ FDP_ACC.1 Subset Access Control β’ FDP_ACF.1 Security attribute based access control β’ FDP_SDC.1 Stored data confidentiality β’ FDP_SDI.1.1 Stored data integrity monitoring β’ FIA_AFL.1 Authentication failure handling β’ FIA_API.1 Authentication proof of identity β’ FIA_ATD.1 User attribute definition β’ FIA_UAU.1 Timing of authentication β’ FIA_UID.1 Timing of identification β’ FMT_MSA.1 Management of security attributes β’ FMT_MSA.3 Static attribute initialization β’ FMT_SMR.1 Security roles β’ FMT_SMF.1 Specification of Management Functions β’ FPT_HWROT.1 Root of trust based on HW β’ FPT_INI.1 TSF initialization β’ FTA_SSL.3 TSF-initiated termination β’ FTP_ITC.1 - Inter-TSF trusted channel Each SFR from CC gives guidance on how the requirement is to be evaluated. This evaluation is addressed as a test purpose in the present document, and the present annex creates a template TPLan structure for each SFR that can be applied for the main body of the present document. NOTE: The full TPLan structure is not shown as the set of header elements is taken from those identified in clause 6 or as shown in clause A.2 of the present document. ETSI ETSI TS 103 993 V1.1.1 (2025-09) 20 A.2 Application of TSS&TP styles to SFRs from ETSI TS 103 996 A.2.0 Note Where no specific TPLan assessment is given the provisions of Common Criteria for Information Technology, Evaluation Methodology [7] apply. A.2.1 FAU_GEN.1.2 Audit data generation As described in ETSI TS 103 996 [i.4] the SFR FAU_GEN.1.2 is intended to satisfy requirements 76, 77 and 80 from ETSI TS 103 962 [1] and ETSI TS 103 963 [2]. It is the IUT that is tested and the TSF within the IUT that is implicitly tested. Thus in general terms for the IUT as specified in [1] and [2] and where FAU_GEN.1.2 is used (with FAU_GEN.1.1 implied): ensure that { when {IUT receives 'audit-function-started' or 'audit-function-stopped' or any-event in 'detailed auditable event' or 'FW-update' or 'SW-update' or 'access attempt to log record' or 'access to TEI management'} then {IUT generates 'detailed audit record'} -- SFR_FAU_GEN.1.2 } The above is also addressed in the access control test purposes given in clause 6.3.3 of the present document. A.2.2 FCS_CKM.1.1 Cryptographic key generation As described in ETSI TS 103 996 [i.4] the SFR FCS_CKM.1.1 is intended to satisfy requirements 24, 41 and 52 from ETSI TS 103 962 [1] and ETSI TS 103 963 [2]. As stated in [i.4] no specific cryptographic provisions are made but rather ask that the OND implementer refers to best practice, as in Annex D of ETSI TS 103 924 [4]. For this the tester has to be able to deliver a stimulus that requires the IUT to generate a cryptographic key that can be shown to have been generated only by the key generation algorithm claimed by the implementation. with {IUT 'having a cryptographic key generation algorithm'} ensure that { when {IUT receives 'cryptographic key generation request'} then {IUT generates 'key in accordance with a specified cryptographic key generation algorithm'} } A.2.3 FCS_CKM.2 Cryptographic key distribution As described in ETSI TS 103 996 [i.4] the SFR FCS_CKM.2 is intended to satisfy requirement 52 from ETSI TS 103 962 [1] and ETSI TS 103 963 [2]. As for clause A.2.2, it is stated in [i.4] that no specific cryptographic provisions are made but rather ask that the OND implementer refers to best practice, as in Annex D of ETSI TS 103 924 [4]. For this the tester has to be able to deliver a stimulus that requires the IUT to distribute a cryptographic key that can be shown to have been distributed only by the key distribution method claimed by the implementation. with {IUT 'having a cryptographic key distribution mechanism'} ensure that { when {IUT receives 'cryptographic key distribution request'} then {IUT sends 'key in accordance with a specified cryptographic key distribution mechanism'} } ETSI ETSI TS 103 993 V1.1.1 (2025-09) 21 A.2.4 FCS_CKM.3 Cryptographic key access As defined in ETSI TS 103 996 [i.4] the SFR FCS_CKM.3 is intended to satisfy all the requirements identified in ETSI TS 103 962 [1] and ETSI TS 103 963 [2] that require a cryptographic keyed operation outside of the TOE. As stated in [i.4] best practice is followed wherein keys are only made available to the function requiring them and are not available by any other mechanism. However it is also noted in the application notes of CC Part 2 [8] that this component is intended to allow the specification of requirements on the usage of keys outside the TOE (e.g. backup, archival, escrow, recovery) which are not supported by [1] and [2]. NOTE: FCS_CKM.3 does not intend to describe the key management or access to keys on the TOE. A.2.5 FCS_CKM.6 Timing and event of cryptographic key destruction In best practice whenever a key is no longer in use it should be destroyed. This is stated in the SFR from CC Part 2 [8] as "The TSF shall destroy [assignment: list of cryptographic keys (including keying material)] when [selection: no longer needed, [assignment: other circumstances for key or keying material destruction]]." ensure that { when {IUT receives 'destroy cryptographic keys command' containing 'Key-id'} then {IUT destroys 'all material identified by Key-id'} } A.2.6 FCS_COP.1.1 Cryptographic operation In CC Part 2 [8] the SFR is stated as "The TSF shall perform [assignment: list of cryptographic operations] in accordance with a specified cryptographic algorithm [assignment: cryptographic algorithm] and cryptographic key sizes [assignment: cryptographic key sizes] that meet the following: [assignment: list of standards]." However, in ETSI TS 103 996 [i.4] it is stated that "The base requirements do not specify cryptographic algorithms or key sizes, but rather refer to best practice". Thus for testing purposes the following preconditions are defined including references to a number of FIPS documents that define commonly used cryptographic algorithms. with {IUT 'having an algorithm for authentication'} with {IUT 'having an algorithm for producing an integrity check value'} with {IUT 'having an algorithm for encryption'} with {IUT 'having an algorithm for decryption'} with {IUT 'having an algorithm for signature creation'} with {IUT 'having an algorithm for singature verification'} def value SymmetricKeySize '128' def value AsymmetricKeySize-ECC '256' -- for equivalence to 128-bit symmetric key def value AsymmetricKeySize-RSA '3072' -- for equivalence to 128-bit symmetric key xref CryptoStandards {FIPS197, FIPS180-4, FIPS186-4, FPIS186-5} A.2.7 FCS_RNG.1 Generation of random numbers As identified in ETSI TS 103 996 [i.4] the generation of random numbers is required by the OND having a physical or non-physical-true or deterministic random number generator. This is addressed using TPLan by defining the following pre-conditions. with {IUT 'having a physical random number generator'} with {IUT 'having a deterministic random number generator'} A.2.8 FDP_ACC.1 Subset Access Control For ONDs the access control test purposes are defined in clause 6.3.3 of the present document. ETSI ETSI TS 103 993 V1.1.1 (2025-09) 22 A.2.9 FDP_ACF.1 Security attribute based access control The model identified in ETSI TS 103 962 [1] and ETSI TS 103 963 [2], and declared in ETSI TS 103 996 [i.4], is policy and attribute based access control. A.2.10 FDP_SDC.1 Stored data confidentiality As identified in ETSI TS 103 996 [i.4] all sensitive user data is expected to be confidential while it is stored in persistent memory. This is addressed by TPLan as a set of pre-conditions given below. with {IUT 'having password stored in a manner consistent with clause 5.1.1 of NIST SP 800-63B'} with {IUT 'having sensitive user data stored confidentiality in persistent memory'} A.2.11 FDP_SDI.1.1 Stored data integrity monitoring As defined in CC Part 2 [8] and for the requirements identified in ETSI TS 103 996 [i.4] it is expected that the memory used for data storage is able to identify, report, and ideally, correct integrity errors arising from accidental (unintentional) errors (e.g. hardware glitches). This is addressed by defining the following TPLan pre-condition. with {IUT 'having memory for user data storage capable of identifying integrity errors'} NOTE 1: The wording in CC Part 2 [8] uses the term "monitor for integrity errors" which is interpreted for the present document as having the meaning of "identify integrity errors" as monitoring is an implicit action in being able to identify. NOTE 2: Error Correcting Code (ECC) memory chips can be used to automatically correct errors in RAM by generating Hamming Codes of the memory entry and, if used, may claim to meet the identified pre-condition. A.2.12 FIA_AFL.1 Authentication failure handling The general assumption in the present document and in ETSI TS 103 962 [1] and ETSI TS 103 963 [2] is that a common failure handling mechanism is applied across the OND. This is specifically handled for ONDs using the test purposes identified in clause 6.3.1 of the present document and by the defined constant defined in clause 6.2. A.2.13 FIA_API.1 Authentication proof of identity The CC Part 2 [8] statement requires that the TSF provide an authentication mechanism to prove the identity of an entity by including a list of properties to an external entity. In TPLan this is addressed by requiring specific elements in the authentication messages (see clause 6.2). The following TPLan elements are indicative. ensure that { when {IUT receives authentication-request containing 'property in list of properties'} β¦ } A.2.14 FIA_ATD.1 User attribute definition In CC Part 2 [8] the behaviour of FIA_ATD.1 requires that the TSF maintains a list of the security attributes belonging to individual users. For the present document where attribute based access control is considered then the rules defined as part of ONDS-AC-003 apply. A.2.15 FIA_UAU.1 Timing of authentication In CC Part 2 [8] the description of the behaviour of FIA_UAU.1 is that the TSF shall allow only some, listed, TSF-mediated actions on behalf of the user to be performed before the user is authenticated. The test purpose therefore shall be written in such a way that both positive and negative behaviour can be assessed, i.e. test that each allowed action is permitted, and that any other action is denied. ETSI ETSI TS 103 993 V1.1.1 (2025-09) 23 NOTE: This is addressed specifically for the OND case in clause 6.3.1 of the present document. It is reasonable to model the allowed actions as part of the access control policy and then to have authentication as an attribute of certain access control rules. In doing this the provisions and tests of clause 6.3.3 apply (see also clause A.2.16 for the similar case of actions before identification). TP Id Test Objective To verify that only listed actions are allowed to be performed before the user is authenticated Reference FIA_UAU.1 Timing of authentication from CC Part 2 [8] Configuration PICS Selection Initial conditions with {IUT in NotAuthenticated } Expected behaviour ensure that { when {IUT receives 'any event'} then {IUT evaluates 'if policy conditions are met'} when {evaluation is true} then {PERMIT} } A.2.16 FIA_UID.1 Timing of identification In CC Part 2 [8] the description of the behaviour of FIA_UID.1 is that the TSF shall allow only some, listed, TSF-mediated actions on behalf of the user to be performed before the user is identified. The test purpose therefore shall be written in such a way that both positive and negative behaviour can be assessed, i.e. test that each allowed action is permitted, and that any other action is denied. NOTE: This is addressed specifically for the OND case in clause 6.3.1 of the present document. It is reasonable to model the allowed actions as part of the access control policy and to have identification as an attribute of certain access control rules. In doing this the provisions and tests of clause 6.3.3 apply. TP Id Test Objective To verify that only listed actions are allowed to be performed before the user is identified Reference FIA_UID.1 Timing of identification from CC Part 2 [8] Configuration PICS Selection Initial conditions with {IUT in NotIdentified } Expected behaviour ensure that { when {IUT receives 'any event'} then {IUT evaluates 'if policy conditions are met'} when {evaluation is true} then {PERMIT} } A.2.17 FMT_MSA.1 Management of security attributes As per CC Part 2 [8] it is recognized that FMT_MSA.1 is addressed by the access control policy where the "security attributes" are specific assets to which access is restricted (see clause 6.3.3 of the present document). A.2.18 FMT_MSA.3 Static attribute initialization Whilst CC Part 2 [8] states that the purpose of this SFR is to strictly control security attributes this is within the overall access control suite identified for the present document by the test purposes in clause 6.3.3. For the more general application of this SFR in which is it intended to verify that the default values of security attributes are appropriately either permissive or restrictive in nature the following pre-conditions apply and test purposes apply. ETSI ETSI TS 103 993 V1.1.1 (2025-09) 24 NOTE: Restrictive attributes are those where only values specifically allowed by the application are permitted, any other value is denied. Permissive attributes are those whose allowed values are set by the specific context. EXAMPLE 1: If an attribute value can take only the values 1,3 and 5 then it is possible to test for permit for only those values and to confirm that deny is true for any other value. EXAMPLE 2: If an attribute can take a range of values it is determined as permissive and testing should address a sufficient number of values in the range, at the limits of the range, and outside the limits of the range to determine correct behaviour. with {IUT 'having attributes used in access control being restrictive'} ensure that { when {IUT receives 'access control request' containing 'attribute'} then [IUT verifies 'attribute' is 'restrictive'} } with {IUT 'having attributes used in access control being permissive'} ensure that { when {IUT receives 'access control request' containing 'attribute'} then [IUT verifies 'attribute' is 'permissive'} } A.2.19 FMT_SMR.1 Security roles Roles are defined as states that can be measured and upon which actions can be taken. def condition Administrator, User -- FMT_SMR.1.1 def value user_roles {'list of allowed user actions'} -- FMT_SMR.1.2 def value admin_roles {'list of allowed administrator actions'} -- FMT_SMR.1.2 NOTE: It is expected that in addition to the roles themselves that the system will map assets (functions, access control conditions to data, and so forth) to each role which is seen in the list of values given above. EXAMPLE: An access control rule may include statements such as "if role is user then permit user action". A.2.20 FMT_SMF.1 Specification of Management Functions In CC Part 2 [8] each SFR has an identified management function (e.g. for FAI_UAU.1 the expected management functions are to establish the threshold for authentication failures and to define the actions to be taken in the event of authentication failure and these are defined for ONDs in clauses 6.2 and 6.3.1 of the present document). As such the specific test purposes for FMT_SMF.1 are not distinct but form part of each SFR and no specific generalization of this SFR is given. A.2.21 FPT_HWROT.1 Root of trust based on HW The base CC Part 2 [8] does not specify FPT_HWROT but it is defined in ETSI TS 103 996 [i.4] as an extension. The intent is that there is a root of trust implemented as immutable HW based module for storing sensitive data. This is addressed in TPLan as a precondition. with {IUT 'having a hardware based root of trust'} See also the set of preconditions given in clause 6.2 of the present document. A.2.22 FPT_INI.1 TSF initialization In CC Part 2 [8] the statement for FPT_INI.1 is given as follows "The TOE shall provide an initialization function which is self-protected for integrity and authenticity". The broad assumption for the OND case is that the boot software can have its integrity and authenticity verified, which may require that the software is signed and that the signature is verified. with {IUT 'having signed boot image'} ensure that { when {IUT receives 'initialisation request'} ETSI ETSI TS 103 993 V1.1.1 (2025-09) 25 then [IUT verifies 'signature of boot image'} } A.2.23 FTA_SSL.3 TSF-initiated termination In CC Part 2 [8] the SFR FTA_SSL.3 applies for interactive user sessions and requires that a timer is established for how long such sessions can be inactive (see clause 6.2 of the present document). ensure that { when {IUT expires UserInactivityTimeLimit} then [IUT closes 'interactive session'} } NOTE: There is not expected to be significant levels of interactive user sessions in an OND but such sessions may be used for remote configuration and thus form part of the access control rules. A.2.24 FTP_ITC.1 - Inter-TSF trusted channel The purpose of FTP_ICT.1 in the context of OND is to ensure that any remote entity is within the trust domain of the OND. This can be implemented using, for example, a VPN protocol such as IPsec or L2TP. In each case the result is that the remote entity and the OND are securely connected where the trusted channel is between known (identified and authenticated) parties, and where any data on the channel is protected from eavesdropping and manipulation. with {IUT 'having a distinct channel to a remote management entity'} -- trusted channel with {IUT 'having trusted channel encrypted'} with {IUT 'having trusted channel with integrity protection'} with {IUT 'having end-points of the trusted channel authenticated'} ensure that { when {IUT receives 'remote connection request from the remote management entity'} then {IUT directs 'remote connection to use trusted channel'} } ETSI ETSI TS 103 993 V1.1.1 (2025-09) 26 Annex B (informative): Considerations for the EUCC PP programme NOTE 1: The mapping given here is indicative and does not claim to be the only mapping that is possible, rather it is a reasonable mapping that aligns the content of the main body of the present document to the essential requirements of the CRA and is intended to show that the PP can be used in any claim of the product that conforms to the PP (the present document) is also conformant to the CRA. It may be possible, and reasonable, for other mappings to be identified. The text of the present annex maps the suite of test purposes given in the main body of the present document to the expectations of the Cyber Resilience Act [i.1] and of the interpretation of the CRA for substantial and high levels of evaluation defined in the Cyber Security Act [i.3]. NOTE 2: The provisions and recommendations given in ETSI TR 103 866 [i.6] for the application of security controls in the NIS2 domain apply to the ONDS domain. ETSI ETSI TS 103 993 V1.1.1 (2025-09) 27 Table B.1: Essential Cybersecurity requirements relating to the properties of products with digital elements Id Text from CRA - Annex I Test process Determination 1 Products with digital elements shall be designed, developed and produced in such a way that they ensure an appropriate level of cybersecurity based on the risks; Evaluation of the summary TVRA given in the ONDS requirements catalogue and by reference to any equivalent analysis indicated by the submitting entity. Using the tools from Common Criteria this should include evaluation of the following Security Assurance Requirements: ADV_ARC.1 ALC_CMC.3 ALC_CMS.2 ADV_TDS.1 or ADV_TDS.2 (depending on the EAL claim). See note. Pass or fail based on the evaluation report. 2 On the basis of the cybersecurity risk assessment referred to in Article 13(2) of Regulation (EU) 2024/2847 [i.1] and where applicable, products with digital elements shall: 2a be made available on the market without known exploitable vulnerabilities; Evaluation of the design process and by a limited degree of penetration testing consistent with AVA_VAN for the intended market and attacker capability (see ETSI TS 102 165-3 [i.7] for a guide to prepare the penetration test). Pass or fail based on the evaluation report. 2b be made available on the market with a secure by default configuration, unless otherwise agreed between manufacturer and business user in relation to a tailor-made product with digital elements, including the possibility to reset the product to its original state; On the assumption that secure by default is defined then a pass or fail is given based on the evaluation report. 2c ensure that vulnerabilities can be addressed through security updates, including, where applicable, through automatic security updates that are installed within an appropriate timeframe enabled as a default setting, with a clear and easy-to-use opt-out mechanism, through the notification of available updates to users, and the option to temporarily postpone them; 2d ensure protection from unauthorized access by appropriate control mechanisms, including but not limited to authentication, identity or access management systems, and report on possible unauthorized access; ETSI ETSI TS 103 993 V1.1.1 (2025-09) 28 Id Text from CRA - Annex I Test process Determination 2e protect the confidentiality of stored, transmitted or otherwise processed data, personal or other, such as by encrypting relevant data at rest or in transit by state of the art mechanisms, and by using other technical means; 2f protect the integrity of stored, transmitted or otherwise processed data, personal or other, commands, programs and configuration against any manipulation or modification not authorized by the user, and report on corruptions; 2g process only data, personal or other, that are adequate, relevant and limited to what is necessary in relation to the intended purpose of the product with digital elements (minimisation of data); This should be documented in a DPIA and also comply to relevant data protection regulation (e.g. GDPR). Pass or fail based on evaluation of the DPIA and selective sampling of data to ensure non-essential data is rejected. 2h protect the availability of essential and basic functions, also after an incident, including through resilience and mitigation measures against denial-of-service attacks; Evaluation of the session termination and the security architecture: FTA_SSL.3 ADV_ARC.1 On the evaluation of the SFR/SAR-results, a pass or fail is given in the evaluation report. 2i minimize the negative impact by the products themselves or connected devices on the availability of services provided by other devices or networks; Evaluation of the event reporting, the security architecture and the user guidance: FAU_GEN.1 AGD_OPE.1 ADV_ARC.1 On the evaluation of the SFR/SAR-results, a pass or fail is given in the evaluation report. ETSI ETSI TS 103 993 V1.1.1 (2025-09) 29 Id Text from CRA - Annex I Test process Determination 2j be designed, developed and produced to limit attack surfaces, including external interfaces; Evaluation of the security architecture, the design, the functional specification and the vulnerability assessment: ADV_ARC.1 ADV_TDS.2 or ADV_TDS.3 ADV_FSP.3 or ADV_FSP.4 AVA_VAN.2 or AVA_VAN.3 On the evaluation of the SAR- results, a pass or fail is given in the evaluation report. 2k be designed, developed and produced to reduce the impact of an incident using appropriate exploitation mitigation mechanisms and techniques; Evaluation of the event reporting, user roles, security architecture, the functional specification: ADV_ARC.1 ADV_TDS.2 or ADV_TDS.3 ADV_FSP.3 or ADV_FSP.4 On the evaluation of the SAR- results, a pass or fail is given in the evaluation report. 2l provide security related information by recording and monitoring relevant internal activity, including the access to or modification of data, services or functions, with an opt-out mechanism for the user; Evaluation of the event reporting, of the management functions and the user roles: FAU_GEN.1 FMT_SMF.1 FMT_SMR.1 On the evaluation of the SFR- results, a pass or fail is given in the evaluation report. 2m provide the possibility for users to securely and easily remove on a permanent basis all data and settings and, where such data can be transferred to other products or systems, ensure that this is done in a secure manner. Evaluation of the functionalities to destroy keys and data, and of the security architecture: FCS_CKM.6 AGD_OPE.1 ADV_ARC.1 On the evaluation of the SFR/SAR-results, a pass or fail is given in the evaluation report. NOTE: The summary analysis given in the OND [4] requirements catalogue did not include an analysis against the cited SARs. ETSI ETSI TS 103 993 V1.1.1 (2025-09) 30 Table B.2: Essential Cybersecurity requirements relating to Vulnerability handling requirements of products with digital elements Id Text from CRA - Annex I Test process Determination Manufacturers of products with digital elements shall 1 Identify and document vulnerabilities and components contained in products with digital elements, including by drawing up a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies of the products. Evaluation of the provided vulnerability processing covering the reception, examination, the assignment of its nature and risk, and the assignment of the affected component using an SBOM. Based on the coverage of provided vulnerability process documentation covering the aspect in question, a pass or fail of the CRA SR is given in the evaluation report. 2 In relation to the risks posed to products with digital elements, address and remediate vulnerabilities without delay, including by providing security updates; where technically feasible, new security updates shall be provided separately from functionality updates. Evaluation of the mitigation means in dependency of the before made nature and risk assignment. The description should cover the aspects. Evaluation of the procedure for the provision of security updates. Based on the coverage of provided vulnerability process documentation covering the aspect in question, a pass or fail of the CRA SR is given in the evaluation report. 3 Apply effective and regular tests and reviews of the security of the product with digital elements. Evaluation of the development security testing process documentation. Based on the coverage of provided vulnerability process documentation covering the aspect in question, a pass or fail of the CRA SR is given in the evaluation report. 4 Once a security update has been made available, share and publicly disclose information about fixed vulnerabilities, including a description of the vulnerabilities, information allowing users to identify the product with digital elements affected, the impacts of the vulnerabilities, their severity and clear and accessible information helping users to remediate the vulnerabilities; in duly justified cases, where manufacturers consider the security risks of publication to outweigh the security benefits, they may delay making public information regarding a fixed vulnerability until after users have been given the possibility to apply the relevant patch. Evaluation of the provided vulnerability processing, including now the policy for coordinated public disclosure procedures after provision of mitigations to the users. Based on the coverage of provided vulnerability process documentation covering the aspect in question, a pass or fail of the CRA SR is given in the evaluation report. 5 Put in place and enforce a policy on coordinated vulnerability disclosure. Evaluation of the provided vulnerability processing, including now the policy for disclosure. Based on the coverage of provided vulnerability process documentation covering the aspect in question, a pass or fail of the CRA SR is given in the evaluation report. ETSI ETSI TS 103 993 V1.1.1 (2025-09) 31 Id Text from CRA - Annex I Test process Determination 6 Take measures to facilitate the sharing of information about potential vulnerabilities in their product with digital elements as well as in third party components contained in that product, including by providing a contact address for the reporting of the vulnerabilities discovered in the product with digital elements. Evaluation of the provided vulnerability processing, including now the policy for disclosure of the vulnerability to affected third party component suppliers based on the SBOM. Based on the coverage of provided vulnerability process documentation covering the aspect in question, a pass or fail of the CRA SR is given in the evaluation report. 7 Provide for mechanisms to securely distribute updates for products with digital elements to ensure that vulnerabilities are fixed or mitigated in a timely manner and, where applicable for security updates, in an automatic manner. Evaluation of the security update provision facility, and, depending on the administration of the TOE, whether an automated download is configurable. Based on the coverage of provided vulnerability process documentation covering the aspect in question, a pass or fail of the CRA SR is given in the evaluation report. 8 Ensure that, where security updates are available to address identified security issues, they are disseminated without delay and, unless otherwise agreed between a manufacturer and a business user in relation to a tailor-made product with digital elements, free of charge, accompanied by advisory messages providing users with the relevant information, including on potential action to be taken. Evaluation of the provided vulnerability processing, including now the policy for disclosure of the vulnerability and the related communication. Based on the coverage of provided vulnerability process documentation covering the aspect in question, a pass or fail of the CRA SR is given in the evaluation report. NOTE: For vulnerability reporting in general the provisions of the ALC_FLR - Flaw Remediation, defined in [i.9] apply, in particular ALC_FLR.2, Evaluation of flaw remediation wherein the evaluator assesses the overall flaw remediation process of the developer. This is addressed more fully in the derived EUCC PP of ETSI TS 103 996 [i.4]. ETSI ETSI TS 103 993 V1.1.1 (2025-09) 32 History Document history V1.1.1 September 2025 Publication
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
1 Scope
|
The present document addresses the specific RF technical characteristics and methods of measurements required by ECC Decision (20)02 [i.1] for base stations, cab radio user equipment and terminals other than cab radio intended to be used for the Future Railway Mobile Communications System (FRMCS) and operating in bands as listed in Table 1-1. Table 1-1: List of supported 3GPP bands and modes of operation Band name Uplink Downlink Duplex mode RAT n100 874,4 - 880 MHz 919,4 - 925 MHz FDD 5G NR n101 1 900 - 1 910 MHz 1 900 - 1 910 MHz TDD 5G NR The technical characteristics and methods of measurements have been derived from, and are consistent with ECC Decision (20)02 [i.1], Commission Implementing Decision (EU) 2021/1730 [i.2], ETSI TS 138 101-1 [1], ETSI TS 138 104 [2], ETSI TS 138 141-1 [3], ETSI TS 138 508-1 [4] and ETSI TS 138 521-1 [5]. For the clauses not specifically mentioned in the present document, compliance with the above mentioned 3GPP Technical Specifications (TS) is also required for BS and UE. Only BS type 1-C characteristics in the previously mentioned specifications apply for the base station specifications given in the present document.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
2 References
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
2.1 Normative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found in the ETSI docbox. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents are necessary for the application of the present document. [1] ETSI TS 138 101-1 (V18.9.0): "5G; NR; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone (3GPP TS 38.101-1 version 18.9.0 Release 18)". [2] ETSI TS 138 104 (V18.9.0): "5G; NR; Base Station (BS) radio transmission and reception (3GPP TS 38.104 version 18.9.0 Release 18)". [3] ETSI TS 138 141-1 (V18.9.0): "5G; NR; Base Station (BS) conformance testing Part 1: Conducted conformance testing (3GPP TS 38.141-1 version 18.9.0 Release 18)". [4] ETSI TS 138 508-1 (V18.6.0): "LTE; 5G; 5GS; User Equipment (UE) conformance specification; Part 1: Common test environment (3GPP TS 38.508-1 version 18.6.0 Release 18)". [5] ETSI TS 138 521-1 (V18.6.0): "5G; NR; User Equipment (UE) conformance specification; Radio transmission and reception; Part 1: Range 1 standalone (3GPP TS 38.521-1 version 18.6.0 Release 18)". [6] ETSI EN 302 208 (V3.4.1): "Radio Frequency Identification Equipment operating in the band 865 MHz to 868 MHz with power levels up to 2 W and in the band 915 MHz to 921 MHz with power levels up to 4 W; Harmonised Standard for access to radio spectrum". [7] ETSI TS 136 101 (V18.9.0): "LTE; Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception (3GPP TS 36.101 version 18.9.0 Release 18)". ETSI ETSI TS 103 793 V1.1.1 (2025-11) 7
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long-term validity. The following referenced documents may be useful in implementing an ETSI deliverable or add to the reader's understanding, but are not required for conformance to the present document. [i.1] ECC Decision (20)02: "Harmonised use of the paired frequency bands 874.4-880.0 MHz and 919.4-925.0 MHz and of the unpaired frequency band 1900-1910 MHz for Railway Mobile Radio (RMR)". [i.2] Commission Implementing Decision (EU) 2021/1730 of 28 September 2021 on the harmonised use of the paired frequency bands 874,4-880,0 MHz and 919,4-925,0 MHz and of the unpaired frequency band 1900-1910 MHz for Railway Mobile Radio. [i.3] ETSI TR 103 791: "Rail Telecommunications (RT); Future Railway Mobile Communication System (FRMCS); Terminology for FRMCS specifications".
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
3 Definition of terms, symbols and abbreviations
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
3.1 Terms
|
For the purposes of the present document, the terms given in ETSI TR 103 791 [i.3] and the following apply: local area base station: equipment class characterized by requirements derived from Pico Cell scenarios with a BS to UE minimum coupling loss equal to 45 dB NOTE: As defined in ETSI TS 138 104 [2], clause 4.4. medium range base station: equipment class characterized by requirements derived from Micro Cell scenarios with a BS to UE minimum coupling loss equals to 53 dB NOTE: As defined in ETSI TS 138 104 [2], clause 4.4. PCMAX_L,f,c: UE's lowest configurable maximum output power for carrier f of serving cell c in each slot NOTE: As defined in ETSI TS 138 521-1 [5], clause 6.2.4. TRANSFORM_PRECODER_ENABLED: transform precoding is enabled (DFT-s-OFDM UL waveform is configured) NOTE: As defined in ETSI TS 138 508-1 [4], Table 4.6.3-118. wide area base station: equipment class characterized by requirements derived from Macro Cell scenarios with a BS to UE minimum coupling loss equal to 70 dB NOTE: As defined in ETSI TS 138 104 [2], clause 4.4.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
3.2 Symbols
|
For the purposes of the present document, the following symbols apply: BWChannel channel bandwidth NRB transmission bandwidth configuration, expressed in units of resource blocks PEIRP EIRP value ETSI ETSI TS 103 793 V1.1.1 (2025-11) 8
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ACLR Adjacent Channel Leakage Ratio BS Base Station BW BandWidth C_RNTI Cell Radio Network Temporary Identifier CP-OFDM Cyclic Prefix Orthogonal Frequency Division Multiplexing CW Continuous Wave DCI Downlink Control Information DFT-s-OFDM Discrete Fourier Transform-spread Orthogonal Frequency Division Multiplexing DL DownLink EIRP Equivalent Isotropically Radiated Power E-UTRA Enhanced Universal Terrestrial Radio Access FDD Frequency Division Duplex FRMCS Future Railway Mobile Communications System HARQ Hybrid Automatic Repeat Request ID Identifier LTE Long Term Evolution MAC Medium Access Control MU Measurement Uncertainty NR New Radio OCNG OFDMA Channel Noise Generator OFDMA Orthogonal Frequency Division Multiple Access PDCCH Physical Downlink Control CHannel PDSCH Physical Downlink Shared CHannel PUSCH Physical Uplink Shared CHannel QPSK Quadrature Phase Shift Keying RAT Radio Access Technology RB Resource Block REFSENS Reference Sensitivity RFID Radio Frequency IDentification RMC Reference Measurement Channel RRC Radio Resource Control Rx Receiver SCS SubCarrier Spacing SRD Short Range Devices SS System Simulator TDD Time Division Duplex TE Test Equipment Tx Transmitter UE User Equipment UL UpLink
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
4 Band definitions
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
4.1 n100
|
The operating band and channel arrangement specifications defined for band n100 in ETSI TS 138 101-1 [1], clause 5 shall apply. Only 5 MHz wide channel bandwidth shall be considered for band n100.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
4.2 n101
|
The operating band and channel arrangement specifications defined for band n101 in ETSI TS 138 101-1 [1], clause 5 shall apply. ETSI ETSI TS 103 793 V1.1.1 (2025-11) 9
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
5 Specifications for base stations
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.1 Output power
|
The specifications defined in ETSI TS 138 104 [2], clauses 6.2.1 and 6.2.4 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.2 Spurious emissions
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.2.0 General
|
The limits defined in ETSI TS 138 104 [2], Table 6.6.5.2.1-2 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.2.1 n100
|
In addition to the requirements defined in clause 5.2.0, for a base station transmitting in n100, the limits defined in ETSI TS 138 104 [2], Tables 6.6.5.2.3-1 and 6.6.5.2.3-13 shall apply to European frequency bands listed in Annex A.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.2.2 n101
|
In addition to the requirements defined in clause 5.2.0, for a base station transmitting in n101, the limits defined in ETSI TS 138 104 [2], Tables 6.6.5.2.3-1 and 6.6.5.2.3-12 shall apply to European frequency bands listed in Annex A.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.2.3 Operating band unwanted emissions
|
For wide area base stations, the limits defined in ETSI TS 138 104 [2], Table 6.6.4.2.2.2-1 shall apply. For medium range base stations, the limits defined in ETSI TS 138 104 [2], Tables 6.6.4.2.3-1 and 6.6.4.2.3-2 shall apply. For local area base stations, the limits defined in ETSI TS 138 104 [2], Table 6.6.4.2.4-1 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.3 Reference sensitivity
|
The specifications defined in ETSI TS 138 104 [2], clause 7.2.2 for frequency bands n100 and n101 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.4 Receiver intermodulation
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.4.1 n100
|
The specifications defined in ETSI TS 138 104 [2], clauses 7.7.2 and 7.7.3 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.4.2 n101
|
The specifications defined in ETSI TS 138 104 [2], clause 7.7.2 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.5 In-band blocking
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.5.1 n100
|
The specifications defined in ETSI TS 138 104 [2], clauses 7.4.2.2 and 7.4.2.5 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.5.2 n101
|
The specifications defined in ETSI TS 138 104 [2], clause 7.4.2.2 shall apply. ETSI ETSI TS 103 793 V1.1.1 (2025-11) 10
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.6 Out-of-band blocking
| |
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.6.1 n100
|
The specifications defined in ETSI TS 138 104 [2], clause 7.5.2 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
5.6.2 n101
|
The specifications defined in ETSI TS 138 104 [2], clauses 7.5.2 and 7.5.5 shall apply.
|
9d41333a56d064c976d8032fae056f46
|
103 793
|
6 Specifications for cab radio user equipment
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.