4 General conducted test conditions and declarations

38.176-13GPPIntegrated Access and Backhaul (IAB) conformance testingNRPart 1: conducted conformance testingRelease 17TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

4.1 Measurement uncertainties and test requirements

4.1.1 General

The requirements of this clause apply to all applicable tests in part 1 of the present document, i.e. to all conducted tests defined for FR1. The frequency ranges FR1 and FR2 are defined in clause 5.1 of TS 38.174 [2].

The minimum requirements are given in TS 38.174 [2] and the references therein. Test Tolerances for the conducted test requirements explicitly stated in the present document are given in Annex C of the present document.

Test Tolerances are individually calculated for each test. The Test Tolerances are used to relax the minimum requirements to create test requirements.

When a test requirement differs from the corresponding minimum requirement, then the Test Tolerance applied for the test is non-zero. The Test Tolerance for the test and the explanation of how the minimum requirement has been relaxed by the Test Tolerance are given in Annex C.

4.1.2 Acceptable uncertainty of Test System

4.1.2.1 General

The maximum acceptable uncertainty of the Test System is specified below for each test defined explicitly in the present specification, where appropriate. The maximum acceptable uncertainty of the Test System for test requirements included by reference is defined in the respective referred test specification.

For IAB type 1-H when a requirement is applied per TAB connector then the test uncertainty is applied to the measured value. When a requirement is applied for a group of TAB connectors then the test uncertainty is applied to sum of the measured power on each TAB connector in the group.

The Test System shall enable the stimulus signals in the test case to be adjusted to within the specified tolerance and the equipment under test to be measured with an uncertainty not exceeding the specified values. All tolerances and uncertainties are absolute values, and are valid for a confidence level of 95 %, unless otherwise stated.

A confidence level of 95 % is the measurement uncertainty tolerance interval for a specific measurement that contains 95 % of the performance of a population of test equipment.

For RF tests, it should be noted that the uncertainties in clause 4.1.2 apply to the Test System operating into a nominal 50 ohm load and do not include system effects due to mismatch between the DUT and the Test System.

4.1.2.2 Measurement of transmitter

Table 4.1.2.2-1: Maximum Test System uncertainty for transmitter tests

Clause	Maximum Test System Uncertainty	Derivation of Test System Uncertainty
6.2 IAB output power	±0.7 dB, f ≤ 3 GHz ±1.0 dB, 3 GHz < f ≤ 6 GHz (Note)
6.3.1 IAB-DU Output power dynamics	± 0.4 dB
6.3.2 IAB-MT Output power dynamics	±0.7 dB, BW ≤ 40MHz ±1.0 dB, 40MHz < f ≤ 100MHz
6.4.1 Transmit OFF power	±2.0 dB, f ≤ 3 GHz ±2.5 dB, 3 GHz < f ≤ 6 GHz (Note)
6.4.2 Transmitter transient period	N/A
6.5.2.1 IAB-DU Frequency error	± 12 Hz
6.5.2.2 IAB-MT Frequency error	±15 Hz, f ≤ 3.0GHz ±36 Hz, f > 3.0GHz
6.5.3 EVM	± 1%
6.5.4 Time alignment error	± 25 ns
6.6.5 Timing error between IAB-DU and IAB-MT	[± 25 ns]
6.6.2 Occupied bandwidth	10 MHz IAB Channel BW: ±100 kHz 15 MHz, 20 MHz, 25 MHz, 30 MHz, 40 MHz, 50 MHz IAB Channel BW: ±300 kHz 60 MHz, 70 MHz, 80 MHz, 90 MHz, 100 MHz IAB Channel BW: ±600 kHz
6.6.3 Adjacent Channel Leakage power Ratio (ACLR)	ACLR/ CACLR BW ≤ 20MHz: ±0.8 dB BW > 20MHz: ±1.2 dB Absolute power ±2.0 dB, f ≤ 3 GHz Absolute power ±2.5 dB, 3 GHz < f ≤ 6 GHz (Note) CACLR BW ≤ 20MHz: ±0.8 dB BW > 20MHz: ±1.2 dB CACLR absolute power ±2.0 dB, f ≤ 3 GHz CACLR absolute power ±2.5 dB, 3 GHz < f ≤ 6 GHz (Note)
6.6.4 Operating band unwanted emissions	±1.5 dB, f ≤ 3 GHz ±1.8 dB, 3 GHz < f ≤ 6 GHz (Note)
6.6.5.5.1.1 Transmitter spurious emissions, Mandatory Requirements	9 kHz < f ≤ 4 GHz: ±2.0 dB 4 GHz < f ≤ 19 GHz: ±4.0 dB 19 GHz < f ≤ 26 GHz: ±4.5 dB
6.6.5.5.1.2 Transmitter spurious emissions, Additional spurious emission requirements	±2.0 dB for > -60 dBm, f ≤ 3 GHz ±2.5 dB, 3 GHz < f ≤ 4.2 GHz ±3.0 dB, 4.2 GHz < f ≤ 6 GHz ±3.0 dB for ≤ -60 dBm, f ≤ 3 GHz ±3.5 dB, 3 GHz < f ≤ 4.2 GHz ±4.0 dB, 4.2 GHz < f ≤ 6 GHz
6.6.5.2.3 Transmitter spurious emissions, Co-location	±3.0 dB
6.7 Transmitter intermodulation (interferer requirements) This tolerance applies to the stimulus and not the measurements defined in 6.6.3, 6.6.4 and 6.6.5	The value below applies only to the interfering signal and is unrelated to the measurement uncertainty of the tests in 6.6.3 (ACLR), 6.6.4 (OBUE) and 6.6.5 (spurious emissions) which have to be carried out in the presence of the interferer. ±1.0 dB	The uncertainty of interferer has double the effect on the result due to the frequency offset
NOTE: Test system uncertainty values for 4.2 GHz < f ≤ 6 GHz apply for IAB operates in licensed spectrum only.

4.1.2.3 Measurement of receiver

Table 4.1.2.3-1: Maximum Test System uncertainty for receiver tests

Clause	Maximum Test System Uncertainty	Derivation of Test System Uncertainty
7.2 Reference sensitivity level	±0.7 dB, f ≤ 3 GHz ±1.0 dB, 3 GHz < f ≤ 4.2 GHz ±1.2 dB, 4.2 GHz < f ≤ 6 GHz
7.3 Dynamic range	±0.3 dB
7.4.1 Adjacent channel selectivity	±1.4 dB, f ≤ 3 GHz ±1.8 dB, 3 GHz < f ≤ 4.2 GHz ±2.1 dB, 4.2 GHz < f ≤ 6 GHz (NOTE 2)	Overall system uncertainty comprises three quantities: 1. Wanted signal level error 2. Interferer signal level error 3. Additional impact of interferer leakage 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 leakage effect is systematic, and is added arithmetically. Test System uncertainty = SQRT (wanted_level_error² + interferer_level_error²) + leakage effect. f ≤ 3 GHz Wanted signal level ±0.7 dB Interferer signal level ±0.7 dB 3 GHz < f ≤ 4.2 GHz Wanted signal level ±1.0 dB Interferer signal level ±1.0 dB 4.2 GHz < f ≤ 6 GHz Wanted signal level ±1.22 dB Interferer signal level ±1.22 dB f ≤ 6 GHz Impact of interferer leakage 0.4 dB
7.4.2 In-band blocking (General blocking)	±1.6 dB, f ≤ 3 GHz ±2.0 dB, 3 GHz < f ≤ 4.2 GHz ±2.2 dB, 4.2 GHz < f ≤ 6 GHz (NOTE 2)
7.4.2 In-band blocking (Narrow band blocking)	±1.4 dB, f ≤ 3 GHz ±1.8 dB, 3 GHz < f ≤ 4.2 GHz ±2.1 dB, 4.2 GHz < f ≤ 6 GHz (NOTE 2)
7.5.5.1, 7.5.5.3 Out-of-band blocking (General requirements)	f_wanted ≤ 3GHz 1MHz < f_interferer ≤ 3 GHz: ±1.3 dB 3.0GHz < f_interferer ≤ 4.2 GHz: ±1.5 dB 4.2GHz < f_interferer ≤ 12.75 GHz: ±3.2 dB 3GHz < f_wanted ≤ 4.2GHz: 1MHz < f_interferer ≤ 3 GHz: ±1.5 dB 3.0GHz < f_interferer ≤ 4.2 GHz: ±1.7 dB 4.2GHz < f_interferer ≤ 12.75 GHz: ±3.3 dB 4.2GHz < f_wanted ≤ 6.0GHz: 1MHz < f_interferer ≤ 3 GHz: ±1.7 dB 3.0GHz < f_interferer ≤ 4.2 GHz: ±1.8 dB 4.2GHz < f_interferer ≤ 12.75 GHz: ±3.3 dB	Overall system uncertainty comprises three quantities: 1. Wanted signal level error 2. Interferer signal level error 3. 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 Broadband noise effect is systematic, and is added arithmetically. Test System uncertainty = SQRT (wanted_level_error² + interferer_level_error²) + Broadband noise effect. Out of band blocking, using CW interferer: Wanted signal level: ±0.7 dB up to 3 GHz ±1.0 dB up to 4.2 GHz ±1.22 dB up to 6 GHz Interferer signal level: ±1.0 dB up to 3 GHz ±1.2 dB up to 4.2 GHz ±3.0 dB up to 12.75 GHz Impact of interferer Broadband noise 0.1 dB
7.5.5.2, 7.5.5.4 Out-of-band blocking (Co-location requirements)	Co-location blocking, using CW interferer: ±2.5 dB, f ≤ 3.0 GHz ±2.6 dB, 3.0 GHz < f ≤ 4.2 GHz ±2.7 dB, 4.2 GHz < f ≤ 6.0 GHz	Co-location 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.0dB 4.2 GHz < f ≤ 6.0 GHz Wanted signal level ± 1.22 dB f ≤ 6.0 GHz Interferer signal level: ± 2.0 dB Interferer ACLR not applicable Impact of interferer Broadband noise 0.4 dB
7.6 Receiver spurious emissions	30 MHz ≤ f ≤ 4 GHz: ±2.0 dB 4 GHz < f ≤ 19 GHz: ±4.0 dB 19 GHz < f ≤ 26 GHz: ±4.5 dB
7.7 Receiver intermodulation	±1.8 dB, f ≤ 3.0 GHz ±2.4 dB, 3.0 GHz < f ≤ 4.2 GHz ±3.0 dB, 4.2 GHz < f ≤ 6.0 GHz (NOTE 2)	Overall system uncertainty comprises four quantities: 1. Wanted signal level error 2. CW Interferer level error 3. Modulated Interferer level error 4. Impact of interferer ACLR 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. The interferer ACLR effect is systematic, and is added arithmetically. Test System uncertainty = SQRT [(2 x CW_level_error)² +(mod interferer_level_error)² +(wanted signal_level_error)²] + ACLR effect. f ≤ 3.0 GHz Wanted signal level ± 0.7dB CW interferer level ± 0.5 dB Mod interferer level ± 0.7 dB 3.0 GHz < f ≤ 4.2 GHz Wanted signal level ± 1.0 dB CW Interferer level ± 0.7 dB Mod Interferer level ± 1.0 dB 4.2 GHz < f ≤ 6 GHz Wanted signal level ± 1.22 dB CW Interferer level ± 0.98 dB Mod Interferer level ± 1.22 dB f ≤ 6 GHz Impact of interferer ACLR 0.4 dB
7.8 In-channel selectivity	±1.4 dB, f ≤ 3 GHz ±1.8 dB, 3 GHz < f ≤ 4.2 GHz ±2.1 dB, 4.2 GHz < f ≤ 6 GHz (NOTE 2)
NOTE 1: Unless otherwise noted, only the Test System stimulus error is considered here. The effect of errors in the throughput measurements due to finite test duration is not considered. NOTE 2: Test system uncertainty values for 4.2 GHz < f ≤ 6 GHz apply for IAB operates in licensed spectrum only.

4.1.2.4 Measurement of performance requirements

{Editor note: table(s) to added}

4.1.3 Interpretation of measurement results

The measurement results returned by the Test System are compared – without any modification – against the test requirements as defined by the Shared Risk principle.

The Shared Risk principle is defined in Recommendation ITU-R M.1545 [4].

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 4.1.2 of the present document.

If the Test System for a test is known to have a measurement uncertainty greater than that specified in clause 4.1.2, it is still permitted to use this apparatus provided that an adjustment is made as follows.

Any additional uncertainty in the Test System over and above that specified in clause 4.1.2 shall be used to tighten the test requirement, making the test harder to pass. For some tests e.g. receiver tests, this may require modification of stimulus signals. This procedure will ensure that a Test System not compliant with clause 4.1.2 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 4.1.2 had been used.

4.2 Conducted requirement reference points

4.2.1 IAB type 1-H

IAB type 1-H requirements are defined for two points of reference, signified by radiated requirements and conducted requirements.

Figure 4.2.1-1: Radiated and conducted reference points for IAB type 1-H

Radiated characteristics are defined over the air (OTA), where the operating band specific radiated interface is referred to as the Radiated Interface Boundary (RIB). Radiated requirements are also referred to as OTA requirements. The (spatial) characteristics in which the OTA requirements apply are detailed for each requirement.

NOTE: Radiated conformance requirements are captured in TS 38.176-2 [3] and are out of scope of the present document.

Conducted characteristics are defined at individual or groups of TAB connectors at the transceiver array boundary, which is the conducted interface between the transceiver unit array and the composite antenna.

The transceiver unit array is part of the composite transceiver functionality generating modulated transmit signal structures and performing receiver combining and demodulation.

The transceiver unit array contains an implementation specific number of transmitter units and an implementation specific number of receiver units. Transmitter units and receiver units may be combined into transceiver units. The transmitter/receiver units have the ability to transmit/receive parallel independent modulated symbol streams.

The composite antenna contains a radio distribution network (RDN) and an antenna array. The RDN is a linear passive network which distributes the RF power generated by the transceiver unit array to the antenna array, and/or distributes the radio signals collected by the antenna array to the transceiver unit array, in an implementation specific way.

How a conducted requirement is applied to the transceiver array boundary is detailed in the respective requirement clause.

4.3 IAB classes

4.3.1 IAB-DU class

The requirements in the present document apply to Wide Area IAB-DU, Medium Range IAB-DU and Local Area IAB-DU unless otherwise stated. For IAB type 1-H, IAB-DU classes are defined as indicated below:

– Wide Area IAB-DU are characterised by requirements derived from Macro Cell scenarios with a BS to UE minimum coupling loss equal to 70 dB.

– Medium Range IAB-DU are characterised by requirements derived from Micro Cell scenarios with a BS to UE minimum coupling loss equals to 53 dB.

– Local Area IAB-DU are characterised by requirements derived from Pico Cell scenarios with a BS to UE minimum coupling loss equal to 45 dB.

4.3.2 IAB-MT class

The requirements in the present document apply to Wide Area IAB-MT and Local Area IAB-MT classes unless otherwise stated.

For IAB type 1-H, IAB-MT classes are defined as indicated below:

– Wide Area IAB-MT are characterised by requirements derived from Macro Cell and/or Micro Cell scenarios.

– Local Area IAB-MT are characterised by requirements derived from Pico Cell and /or Micro Cell scenarios.

4.4 Regional requirements

Some requirements in the present document may only apply in certain regions either as optional requirements, or as mandatory requirements set by local and regional regulation. It is normally not stated in the 3GPP specifications under what exact circumstances the regional requirements apply, since this is defined by local or regional regulation.

Table 4.4-1 lists all requirements in the present specification that may be applied differently in different regions.

Table 4.4-1: List of regional requirements

Clause number	Requirement	Comments
5.2	Operating bands	Some NR operating bands may be applied regionally.
6.2.3	IAB output power: Additional requirements	These requirements may be applied regionally as additional IAB output power requirements.
6.6.2	Occupied bandwidth	The requirement may be applied regionally. There may also be regional requirements to declare the occupied bandwidth according to the definition in present specification.
6.6.4.2	Operating band unwanted emission	Category A or Category B operating band unwanted emissions limits may be applied regionally.
6.6.4.2.5.1	Operating band unwanted emission	The IAB may have to comply with the additional requirements, when deployed in regions where those limits are applied, and under the conditions declared by the manufacturer.
6.6.5.2.1,	Tx spurious emissions,	Category A or Category B spurious emission limits, as defined in Recommendation ITU-R SM.329 [5], may apply regionally. The emission limits for IAB type 1-H specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation.
6.6.5.2.2,	Tx spurious emissions: additional requirements, OTA Tx spurious emissions: additional requirements	These requirements may be applied for the protection of system operating in frequency ranges other than the IAB operating band.
6.7.2.1	Transmitter intermodulation,	Interfering signal positions that are partially or completely outside of any downlink operating band of the IAB are not excluded from the requirement in Japan in Band n77, n78, n79.
7.6.2, 7.6.3	Rx spurious emissions,	The emission limits for IAB type 1-H specified as the basic limit + X (dB) are applicable, unless stated differently in regional regulation.

4.5 IAB configurations

4.5.1 IAB type 1-H

4.5.1.1 Transmit configurations

Unless otherwise stated, the conducted transmitter characteristics in clause 6 are specified at the transceiver array boundary at the TAB connector(s) with a full complement of transceiver units for the configuration in normal operating conditions.

Figure 4.5.1.1-1: Transmitter test ports

Unless otherwise stated, for the tests in clause 6 of the present document, the requirement applies for each transmit TAB connector.

4.5.1.2 Receive configurations

Unless otherwise stated, the conducted receiver characteristics in clause 7 are specified at the TAB connector with a full complement of transceiver units for the configuration in normal operating conditions.

Figure 4.5.1.2-1: Receiver test ports

For the tests in clause 7 of the present document, the requirement applies at each receive TAB connector.

Conducted receive requirements are tested at the TAB connector, with the remaining receiver units(s) disabled or their TAB connector(s) being terminated.

4.5.1.3 Power supply options

If the IAB type 1-H is supplied with a number of different power supply configurations, it may not be necessary to test RF parameters for each of the power supply options, provided that it can be demonstrated that the range of conditions over which the equipment is tested is at least as great as the range of conditions due to any of the power supply configurations.

4.5.2 IAB with integrated Iuant BS modem

Unless otherwise stated, for the tests in the present document, the integrated Iuant BS modem shall be switched OFF. Spurious emissions according to clauses 6.6.5 and 7.6 shall be measured only for frequencies above 20 MHz with the integrated Iuant BS modem switched ON.

4.6 Manufacturer declarations

The following IAB type 1-H declarations listed in table 4.6-1, when applicable to the IAB-DU or IAB-MT under test, are required to be provided by the manufacturer for the conducted requirements testing of the IAB type 1-H. Declarations may be provided independently for IAB-MT and IAB-DU.

For the IAB type 1-H declarations required for the radiated requirements testing, refer to TS 38.176-2 [3].

Table 4.6-1 Manufacturer declarations for IAB-type 1-H conducted test requirements

Declaration identifier	Declaration	Description	Applicability
Declaration identifier	Declaration	Description	IAB-DU type 1-H	IAB-MT type 1-H
D.1	IAB requirements set	Declaration of one of the IAB requirement’s set as defined for IAB type 1-H.	x	x
D.2	IAB class	IAB class of the IAB, declared as Wide Area IAB, Medium Range IAB, or Local Area IAB.	x	x
D.3	Operating bands and frequency ranges	List of NR operating band(s) supported by single-band connector(s) and/or multi-band connector(s) of the IAB-DU or IAB-MT and if applicable, frequency range(s) within the operating band(s) that the IAB can operate in. Declarations shall be made per TAB connector for IAB type 1-H.	x	x
D.4	Spurious emission category	Declare the IAB-DU or IAB-MT spurious emission category as either category A or B with respect to the limits for spurious emissions, as defined in Recommendation ITU-R SM.329 [5].	x	x
D.5	Additional operating band unwanted emissions	The manufacturer shall declare whether the IAB-DU or IAB-MT under test is intended to operate in geographic areas where the additional operating band unwanted emission limits defined in clause 6.6.4.5 apply.	x	x
D.6	Co-existence with other systems	The manufacturer shall declare whether the IAB-DU or IAB-MT under test is intended to operate in geographic areas where one or more of the systems GSM850, GSM900, DCS1800, PCS1900, UTRA FDD, UTRA TDD, E-UTRA, PHS and/or NR operating in another band are deployed.	x	x
D.7	Co-location with other IAB	The manufacturer shall declare whether the IAB-DU or IAB-MT under test is intended to operate co-located with IAB of one or more of the systems GSM850, GSM900, DCS1800, PCS1900, UTRA FDD, UTRA TDD, E-UTRA and/or NR operating in another band.	x	x
D.8	Single band connector or multi-band connector	Declaration of the single band or multi-band capability of single band connector(s) or multi-band connector(s), declared for every connector.	x	x
D.9	Contiguous or non-contiguous spectrum operation support	Ability to support contiguous or non-contiguous (or both) frequency distribution of carriers when operating multi-carrier. Declared per single band connector or multi-band connector, per operating band.	x	x
D.10	void	void
D.11	Maximum IAB RF Bandwidth	Maximum IAB RF Bandwidth in the operating band for single-band operation. Declared per supported operating band, per TAB connector for IAB type 1-H. (Note 2)	x	x
D.12	Maximum IAB RF Bandwidth for multi-band operation	Maximum IAB RF Bandwidth for multi-band operation. Declared per supported operating band, per TAB connector for IAB type 1-H.	x	x
D.13	Total RF bandwidth (BW_tot)	Total RF bandwidth BW_tot of transmitter and receiver, declared per the band combinations (D.27).	x	x
D.14	NR supported channel bandwidths and SCS	NR supported SCS and channel bandwidths per supported SCS. Declared per supported operating band, per TAB connector for IAB type 1-H.	x	x
D.15	CA only operation	Declaration of CA-only operation (with equal power spectral density among carriers) but not multiple carriers, declared per operating band per TAB connector for IAB type 1-H.	x	x
D.16	Single or multiple carrier	Capable of operating with a single carrier (only) or multiple carriers. Declared per supported operating band, per TAB connector for IAB type 1-H.	x	x
D.17	Maximum number of supported carriers per operating band in single band operation	Maximum number of supported carriers per supported operation band in single band operation. Declared per supported operating band, per TAB connector for IAB type 1-H. (Note 2)	x	x
D.18	Maximum number of supported carriers per operating band in multi-band operation	Maximum number of supported carriers per supported operation band in multi-band operation. (Note 2)	x	x
D.19	Total maximum number of supported carriers in multi-band operation	Maximum number of supported carriers for all supported operating bands in multi-band operation. Declared for all connectors (D.18).	x	x
D.20	Other band combination multi-band restrictions	Declare any other limitations under simultaneous operation in the declared band combinations (D.38) for each multi-band connector which have any impact on the test configuration generation. Declared for every multi-band connector.	x	x
D.21	Rated carrier output power (P_rated,c,AC, or P_rated,c,TABC)	Conducted rated carrier output power, per single band connector or multi-band connector. Declared per supported operating band, per TAB connector for IAB type 1-H. (Note 1, 2)	x	x
D.22	Rated total output power (P_rated,t,AC, or P_rated,t,TABC)	Conducted total rated output power. Declared per supported operating band, per TAB connector for IAB type 1-H. For multi-band connectors declared for each supported operating band in each supported band combination. (Note 1, 2)	x	x
D.23	Rated multi-band total output power, P_{rated,MB,TABC}	Conducted multi-band rated total output power. Declared per supported operating band combinations, per multi-band connector. (Note 1)	x	x
D.24	N_cells	Number corresponding to the minimum number of cells that can be transmitted by a IAB in a particular operating band with transmission on all TAB connectors supporting the operating band.	x	x
D.25	Maximum supported power difference between carriers	Maximum supported power difference between carriers. Declared per supported operating band, per TAB connector for IAB type 1-H. (Note 3).	x	x
D.26	Maximum supported power difference between carriers is different operating bands	Supported power difference between any two carriers in any two different supported operating bands. Declared per supported operating band combination, per multi-band connector.	x	x
D.27	Operating band combination support	List of operating bands combinations supported by single-band connector(s) and/or multi-band connector(s) of the IAB. Declared per TAB connector for IAB type 1-H.	x	x
D.28	void	void
D.29	Intra-system interfering signal declaration list	List of single band connector(s) or multi-band connector(s) for which an intra-system interfering signal level is required to be declared. Declaration is required if the intra-system interfering signal level is larger than the co-location interfering signal level.	x	x
D.30	Intra-system interfering signal level	The interfering signal level in dBm. Declared per supported operating band, per TAB connector for IAB type 1-H covered by D.29.	x	x
D.31	TAE groups	Set of declared TAB connector beam forming groups on which the TAE requirements apply. All TAB connectors belong to at least one TAB connector beam forming group (even if it’s a TAB connector beam forming group consisting of one connector). The smallest possible number of TAB connector beam forming groups need to be declared such that there is no TAB connector not contained in at least one of the declared TAB connector beam forming groups. Declared per supported operating band.	x
D.32	Equivalent connectors	List of TAB connector of IAB type 1-H, which have been declared equivalent. Equivalent connectors imply that the TAB connector of IAB type 1-H, are expected to behave in the same way when presented with identical signals under the same operating conditions. All declarations made for the TAB connector of IAB type 1-H are identical and the transmitter unit and/or receiver unit driving the TAB connector of IAB type 1-H are of identical design.	x	x
D.33	TAB connector RX min cell group	Declared as a group of TAB connectors to which RX requirements are applied. This declaration corresponds to group of TAB connectors which are responsible for receiving a cell when the IAB type 1-H setting corresponding to the declared minimum number of cells (N_cells) with transmission on all TAB connectors supporting an operating band.	X	x
D.34	TAB connector TX min cell group	Declared group of TAB connectors to which TX requirements are applied. This declaration corresponds to group of TAB connectors which are responsible for transmitting a cell when the IAB type 1-H setting corresponding to the declared minimum number of cells (N_cells) with transmission on all TAB connectors supporting an operating band.	x	x
D.35	void	void
D.36	Relation between supported maximum RF bandwidth, number of carriers and Rated total output power	If the rated total output power and total number of supported carriers are not simultaneously supported, the manufacturer shall declare the following additional parameters: – The reduced number of supported carriers at the rated total output power; – The reduced total output power at the maximum number of supported carriers.	x	x
D.37	TAB connectors used for performance requirement testing	To reduce test complexity, declaration of a representative (sub)set of TAB connectors to be used for performance requirement test purposes. At least one TAB connector mapped to each demodulation branch is declared.	x	x
D.38	Inter-band CA	Band combinations declared to support inter-band CA (per CA capable multi-band connector(s), as in D.15). Declared for every multi-band connector which support CA.	x	x
D.39	Intra-band contiguous CA	Bands declared to support intra-band contiguous CA (per CA capable single band connector(s) or multi-band connector(s), as in D.15). Declared per TAB connector for IAB type 1-H.	x	x
D.40	Intra-band non-contiguous CA	Bands declared to support intra-band non-contiguous CA (per CA capable single band connector(s) or multi-band connector(s), as in D.15). Declared per or TAB connector for IAB type 1-H..	x	x
D.41	void	void
D.42	void	void
D.43	void	void
D.IAB-1	Same RF implementation.	Declaration whether IAB-MT and IAB-DU have same RF implementation.	x	x
D.IAB-2	IAB simultaneous operation	Declare support of IAB simultaneous operation, simultaneous transmission, or simultaneous reception or both.	x	x
D.IAB-3	Maximum power imbalance for IAB simultaneous transmission	Declare the maximum PSD offset in dB of IAB-MT carrier and IAB-DU carrier for IAB simultaneous transmission	x	x
D.100	PUSCH mapping type	Declaration of the supported PUSCH mapping type as specified in TS 38.211 [9], i.e., type A, type B or both.	x
D.101	PUSCH additional DM-RS positions	Declaration of the supported additional DM-RS position(s), i.e., pos0, pos1 or both.	x
D.102	PUCCH format	Declaration of the supported PUCCH format(s) as specified in TS 38.211 [9], i.e., format 0, format 1, format 2, format 3, format 4.	x
D.103	PRACH format and SCS	Declaration of the supported PRACH format(s) as specified in TS 38.211 [9], i.e., format: 0, A1, A2, A3, B4, C0, C2. Declaration of the supported SCS(s) per supported PRACH format with short sequence, as specified in TS 38.211 [9], i.e., 15 kHz, 30 kHz or both.	x
D.104	Additional DM-RS for PUCCH format 3	Declaration of the supported additional DM-RS for PUCCH format 3: without additional DM-RS, with additional DM-RS or both.	x
D.105	Additional DM-RS for PUCCH format 4	Declaration of the supported additional DM-RS for PUCCH format 4: without additional DM-RS, with additional DM-RS or both.	x
D.106	PUCCH multi-slot	Declaration of multi-slot PUCCH support.	x
D.107	UL CA	For the highest supported SCS, declaration of the carrier combination with the largest aggregated bandwidth. If there is more than one combination, the carrier combination with the largest number of carriers shall be declared.	x
D.108	Modulation order	Declaration of the supported modulation order, i.e. QPSK, 16QAM, 64QAM	x
D.109	DFT-s-OFDM	Declaration of the supported of DFT-s-OFDM, i.e. supported or not supported.	x
D.200	256QAM for PDSCH for FR1	Declaration of the supported of 256QAM modulation scheme for PDSCH for FR1, i.e. supported or not supported.		x
D.201	Maximum number of ports across all configured NZP-CSI-RS resources per CC	Declaration of the maximum number of ports across all configured NZP-CSI-RS resources per CC, i.e. 2, 4, 8, 12, 16, 24, 32, 40, 48 … ,256 or not supported.		x
D.202	Maximum number of PDSCH MIMO layers	Declaration of the the maximum number of spatial multiplexing layer(s) supported by the UE for DL reception, i.e. 2, 4, 8 or not supported.		x
NOTE 1: If an IAB-DU or IAB-MT is capable of 256QAM DL operation then two rated output power declarations may be made. One declaration is applicable when configured for 256QAM transmissions and the other declaration is applicable when not configured for 256QAM transmissions. NOTE 2: Parameters for contiguous or non-contiguous spectrum operation in the operating band are assumed to be the same unless they are separately declared. When separately declared, they shall still use the same declaration identifier. NOTE 3: The power difference is declared at highest rated output power. NOTE 4: For declaration applied both IAB-MT and IAB-DU, it can be applied to IAB simultaneous operation where applicable.

4.7 Test configurations

4.7.1 General

The test configurations shall be constructed using the methods defined below, subject to the parameters declared by the manufacturer for the supported RF configurations as listed in clause 4.6. The test configurations to use for conformance testing are defined for each supported RF configuration in clauses 4.8.3 and 4.8.4.

The applicable test models for generation of the carrier transmit test signal are defined in clause 4.9.

NOTE: If required, carriers are shifted to align with the channel raster.

4.7.2 Test signal used to build Test Configurations

The signal’s channel bandwidth and subcarrier spacing used to build IAB Test Configurations shall be selected according to table 4.7.2-1.

Table 4.7.2-1: Signal to be used to build IAB TCs

Operating Band characteristics		F_{DL_high} – F_{DL_low} <100 MHz	F_{DL_high} – F_{DL_low} ≥ 100 MHz
TC signal	BW_channel	10 MHz (Note 1)	20 MHz (Note 1)
characteristics	Subcarrier spacing	Smallest supported subcarrier spacing
NOTE 1: If this channel bandwidth is not supported, the narrowest supported channel bandwidth shall be used.

4.7.3 IABTC1: Contiguous spectrum operation

4.7.3.1 General

The purpose of test configuration IABTC1 is to test all IAB requirements excluding CA occupied bandwidth.

For IABTC1 used in receiver tests only the two outermost UL carriers and two outermost DL carriers within each supported operating band need to be generated by the test equipment;

4.7.3.2 IABTC1 generation

IABTC1 shall be constructed on a per band basis using the following method:

– Declared maximum IAB RF Bandwidth supported for contiguous spectrum operation (D.11) shall be used;

– For IAB not supporting simultaneous transmission between IAB-DU and IAB-MT, select the IAB carrier to be tested according to 4.7.2 and place it adjacent to the lower IAB RF Bandwidth edge. Place same signals adjacent to the upper IAB RF Bandwidth edge.

– For IAB supporting simultaneous transmission between IAB-DU and IAB-MT, select the IAB UL carrier to be tested according to 4.7.2 and place it adjacent to the lower IAB RF Bandwidth edge. Place the same IAB UL carrier adjacent to the upper IAB RF Bandwidth edge. Select the IAB DL carrier to be tested according to 4.7.2 and place it adjacent to the already placed IAB UL carrier at the lower IAB RF Bandwidth edge. Place the same IAB DL carrier adjacent to the already placed IAB UL carrier at the upper IAB RF Bandwidth edge.

– For transmitter tests, select as many IAB carriers (according to 4.7.2) that the IAB supports within an operating band and fit in the rest of the declared maximum IAB RF Bandwidth (D.11). Place the carriers adjacent to each other starting from the upper IAB RF Bandwidth edge. The nominal channel spacing defined in TS 38.174 [2], clause 5.4.1 shall apply.

The test configuration should be constructed sequentially on a per band basis for all component carriers of the inter-band CA bands declared to be supported by the IAB and are transmitted using the same TAB connector. All configured component carriers are transmitted simultaneously in the tests where the transmitter should be ON.

4.7.3.3 IABTC1 power allocation

Set the power spectral density of each carrier to the same level so that the sum of the carrier powers equals the rated total output power (P_rated,t,AC, or P_rated,t,TABC, D.22) for IAB according to the manufacturer’s declaration in clause 4.6.

4.7.4 IABTC2: Contiguous CA occupied bandwidth

4.7.4.1 General

IABTC2 in this clause is used to test CA occupied bandwidth.

4.7.4.2 IABTC2 generation

The CA specific test configuration should be constructed on a per band basis using the following method:

– All component carrier combinations supported by the IAB, which have different sum of channel bandwidth of component carrier, shall be tested. For all component carrier combinations which have the same sum of channel bandwidth of component carriers, only one of the component carrier combinations shall be tested.

– Of all component carrier combinations which have same sum of channel bandwidth of component carrier, select those with the narrowest carrier with the smallest supported subcarrier spacing at the lower IAB RF Bandwidth edge.

– Of the combinations selected in the previous step, select one with the narrowest carrier with the smallest supported subcarrier spacing at the upper IAB RF Bandwidth edge.

– If there are multiple combinations fulfilling previous steps, select the one with the smallest number of component carrier.

– If there are multiple combinations fulfilling previous steps, select the one with the widest carrier with the smallest supported subcarrier spacing being adjacent to the lowest carrier.

– If there are multiple combinations fulfilling previous steps, select the one with the widest carrier with the smallest supported subcarrier spacing being adjacent to the highest carrier.

– If there are multiple combinations fulfilling previous steps, select the one with the widest carrier with the smallest supported subcarrier spacing being adjacent to the carrier which has been selected in the previous step.

– If there are multiple combinations fulfilling previous steps, repeat the previous step until there is only one combination left.

– The nominal channel spacing defined in TS 38.174 [2], clause 5.4.1 shall apply.

4.7.4.3 IABTC2 power allocation

Set the power spectral density of each carrier to be the same level so that the sum of the carrier powers equals the rated total output power (P_rated,t,AC, or P_rated,t,TABC, D.22) for IAB according to the manufacturer’s declaration in clause 4.6.

4.7.5 IABTC3: Non-contiguous spectrum operation

4.7.5.1 General

The purpose of IABTC3 is to test all IAB requirements excluding CA occupied bandwidth.

For IABTC3 used in receiver tests, outermost DL and UL carriers for each sub-block need to be generated by the test equipment; other supported carriers are optional to be generated.

4.7.5.2 IABTC3 generation

IABTC3 is constructed on a per band basis using the following method:

– For IAB not supporting simultaneous transmission between IAB-DU and IAB-MT, select the IAB carrier to be tested according to clause 4.7.2. Place it adjacent to the upper IAB RF Bandwidth edge and another carrier (as described in clause 4.7.2) adjacent to the lower IAB RF Bandwidth edge.

– For IAB supporting simultaneous transmission between IAB-DU and IAB-MT, select the IAB UL carrier to be tested according to 4.7.2 and place it adjacent to the lower IAB RF Bandwidth edge. Place the same IAB UL carrier adjacent to the upper IAB RF Bandwidth edge. Select the IAB DL carrier to be tested according to 4.7.2 and place it adjacent to the already placed IAB UL carrier at the upper IAB RF Bandwidth edge. Place the same IAB DL carrier adjacent to the already placed IAB UL carrier at the lower IAB RF Bandwidth edge.

– For single-band operation receiver tests, if the remaining gap is at least 15 MHz (or 60 MHz if channel bandwidth of the carrier to be tested is 20 MHz) plus two times the channel BW used in the previous step and the IAB supports at least 4 carriers, place a carrier of this BW adjacent to each already placed carrier for each sub-block. The nominal channel spacing defined in TS 38.174 [2], clause 5.4.1 shall apply.

– The sub-block edges adjacent to the sub-block gap shall be determined using the specified F_{offset_high} and F_{offset_low}for the carriers adjacent to the sub-block gap.

4.7.5.3 IABTC3 power allocation

Set the power of each carrier to the same level so that the sum of the carrier powers equals the rated total output power (P_rated,t,AC, or P_rated,t,TABC, D.22) for IAB according to the manufacturer’s declaration in clause 4.6.

4.7.6 IABTC4: Multi-band test configuration for full carrier allocation

4.7.6.1 General

The purpose of IABTC4 is to test multi-band operation aspects considering maximum supported number of carriers.

4.7.6.2 IABTC4 generation

IABTC4 is based on re-using the previously specified test configurations (IABTC1, IABTC2 and IABTC3) applicable per band involved in multi-band operation. It is constructed using the following method:

– The IAB RF Bandwidth of each supported operating band shall be the declared maximum IAB RF Bandwidth in multi-band operation (D.12).

– The number of carriers of each supported operating band shall be the declared maximum number of supported carriers per operating band in multi-band operation (D. 18). Carriers shall be selected according to 4.7.2 and shall first be placed at the outermost edges of the declared maximum Radio Bandwidth. Additional carriers shall next be placed at the IAB RF Bandwidths edges, if possible.

– The allocated IAB RF Bandwidth of the outermost bands shall be located at the outermost edges of the declared maximum Radio Bandwidth.

– Each concerned band shall be considered as an independent band and the carrier placement in each band shall be according to IABTC1, where the declared parameters for multi-band operation shall apply. The mirror image of the single-band test configuration shall be used in each alternate band(s) and in the highest band being.

– If only three carriers are supported, two carriers shall be placed in one band according to the relevant test configuration while the remaining carrier shall be placed at the edge of the maximum Radio Bandwidth in the other band.

– If the sum of the maximum IAB RF Bandwidths of each supported operating bands is larger than the declared Total RF Bandwidth BW_tot (D.13) of transmitter and receiver for the declared band combinations of the IAB, repeat the steps above for test configurations where the IAB RF Bandwidth of one of the operating band shall be reduced so that the Total RF Bandwidth of transmitter and receiver is not exceeded and vice versa.

– If the sum of the maximum number of supported carriers per operating band in multi-band operation (D.18) is larger than the declared total maximum number of supported carriers in multi-band operation (D. 19), repeat the steps above for test configurations where in each test configuration the number of carriers of one of the operating band shall be reduced so that the total number of supported carriers is not exceeded and vice versa.

4.7.6.3 IABTC4 power allocation

Unless otherwise stated, set the power of each carrier in all supported operating bands to the same power so that the sum of the carrier powers equals the rated total output power (P_rated,t,AC or P_rated,t,TABC, D.22) according to the manufacturer’s declaration.

If the allocated power of a supported operating band(s) exceeds the declared rated total output power of the operating band(s) in multi-band operation, the exceeded part shall, if possible, be reallocated into the other band(s). If the power allocated for a carrier exceeds the rated output power declared for that carrier, the exceeded power shall, if possible, be reallocated into the other carriers.

4.7.7 IABTC5: Multi-band test configuration with high PSD per carrier

4.7.7.1 General

The purpose of IABTC5 is to test multi-band operation aspects considering higher PSD cases with reduced number of carriers and non-contiguous operation (if supported) in multi-band mode.

4.7.7.2 IABTC5 generation

IABTC5 is based on re-using the existing test configuration applicable per band involved in multi-band operation. It is constructed using the following method:

– The IAB RF Bandwidth of each supported operating band shall be the declared maximum IAB RF Bandwidth in multi-band operation (D.12).

– The allocated IAB RF Bandwidth of the outermost bands shall be located at the outermost edges of the declared Maximum Radio Bandwidth.

– The maximum number of carriers is limited to two per band. Carriers shall be selected according to 4.7.2 and shall first be placed at the outermost edges of the declared Maximum Radio Bandwidth for outermost bands and at the IAB RF Bandwidths edges for middle band(s) if any. Additional carriers shall next be placed at the IAB RF Bandwidths edges, if possible.

– Each concerned band shall be considered as an independent band and the carrier placement in each band shall be according to IABTC3, where the declared parameters for multi-band operation shall apply. Narrowest supported NR channel bandwidth and smallest subcarrier spacing shall be used in the test configuration.

– If only one carrier can be placed for the concerned band(s), the carrier(s) shall be placed at the outermost edges of the declared maximum radio bandwidth for outermost band(s) and at one of the outermost edges of the supported frequency range within the IAB RF Bandwidths for middle band(s) if any.

– If the sum of the maximum IAB RF Bandwidth of each supported operating bands is larger than the declared Total RF Bandwidth BW_tot (D.13) of transmitter and receiver for the declared band combinations of the IAB, repeat the steps above for test configurations where the IAB RF Bandwidth of one of the operating band shall be reduced so that the Total RF Bandwidth BW_tot of transmitter and receiver is not exceeded and vice versa.

4.7.7.3 IABTC5 power allocation

Unless otherwise stated, set the power of each carrier in all supported operating bands to the same power so that the sum of the carrier powers equals the total rated output power (P_rated,t,AC or P_rated,t,TABC, D.22) according to the manufacturer’s declaration.

4.8 Applicability of requirements

4.8.1 General

4.8.2 Requirement set applicability

In table 4.8.2-1, the requirement applicability for each requirement set of IAB-DU and IAB-MT is defined. For each requirement, the applicable requirement clause in the specification is identified. Requirements not included in a requirement set is marked not applicable (NA).

Table 4.8.2-1: Requirement set applicability for IAB-DUs and IAB-MTs

Requirement	IAB-DU Requirement set	IAB-MT Requirement set
Output power	6.2	6.2
Output power dynamics	6.3	6.3
Transmit ON/OFF power	6.4	6.4
Transmitted signal quality	6.5	6.5
Occupied bandwidth	6.6.2	6.6.2
ACLR	6.6.3	6.6.3
Operating band unwanted emissions	6.6.4	6.6.4
Transmitter spurious emissions	6.6.5	6.6.5
Transmitter intermodulation	6.7.5	6.7.5
Reference sensitivity level	7.2	7.2
Dynamic range	7.3	NA
In-band selectivity and blocking	7.4	7.4
Out-of-band blocking	7.5	7.5
Receiver spurious emissions	7.6	7.6
Receiver intermodulation	7.7	7.7
In-channel selectivity	7.8	NA
Performance requirements	8	8

4.8.3 Applicability of test configurations for single-band operation

The applicable test configurations are specified in the tables below for each the supported RF configuration, which shall be declared according to clause 4.6. The generation and power allocation for each test configuration is defined in clause 4.7. This clause contains the test configurations for an IAB node capable of single carrier, multi-carrier and/or CA operation in both contiguous and non-contiguous spectrum in single band.

For an IAB node declared to be capable of single carrier operation only (D.16), a single carrier (SC) shall be used for testing.

For an IAB node declared to support multi-carrier and/or CA operation in contiguous spectrum within a single band (D.15-D.16), the test configurations in the second column of table 4.8.3-1 shall be used for testing.

For an IAB node declared to support multi-carrier and/or CA operation in contiguous and non-contiguous spectrum within a single band (D.15-D.16) and where the parameters in the manufacture’s declaration according to clause 4.6 are identical for contiguous (C) and non-contiguous (NC) spectrum operation (D.9), the test configurations in the third column of table 4.8.3-1 shall be used for testing.

For an IAB node declared to support multi-carrier and/or CA in operation contiguous and non-contiguous spectrum within a single band (D.15-D.16) and where the parameters in the manufacture’s declaration according to clause 4.6 are not identical for contiguous (C) and non-contiguous (NC) spectrum operation (D.9), the test configurations in the fourth column of table 4.8.3-1 shall be used for testing.

For an IAB node declared to support IAB simultaneous operation (D.IAB-2) in contiguous and non-contiguous spectrum within a single band (D.15-D.16) and where the parameters in the manufacture’s declaration according to clause 4.6 are identical for contiguous (C) and non-contiguous (NC) spectrum operation (D.9), the test configurations in the third column of table 4.8.3-2 shall be used for testing of simultaneous operation.

For an IAB node declared to support IAB simultaneous operation (D.IAB-2) in contiguous and non-contiguous spectrum within a single band (D.15-D.16) and where the parameters in the manufacture’s declaration according to clause 4.6 are not identical for contiguous (C) and non-contiguous (NC) spectrum operation (D.9), the test configurations in the fourth column of table 4.8.3-2 shall be used for testing of simultaneous operation.

Unless otherwise stated, single carrier configuration (SC) tests shall be performed using signal with narrowest supported channel bandwidth and the smallest supported sub-carrier spacing.

Table 4.8.3-1: Test configurations for a IAB capable of multi-carrier and/or CA in a single band

IAB test case	Contiguous spectrum capable IAB	C and NC capable IAB with identical parameters	C and NC capable IAB with different parameters
Output power	IABTC1	IABTC1	IABTC1, IABTC3
RE Power control dynamic range (only applied to IAB-DU)	Tested with Error Vector Magnitude	Tested with Error Vector Magnitude	Tested with Error Vector Magnitude
Total power dynamic range	SC	SC	SC
Transmit ON/OFF power (only applied to NR TDD IAB)	IABTC1	IABTC1	IABTC1, IABTC3
Frequency error	Tested with Error Vector Magnitude	Tested with Error Vector Magnitude	Tested with Error Vector Magnitude
Error Vector Magnitude	IABTC1	IABTC1	IABTC1, IABTC3
Time alignment error (only applied to IAB-DU)	IABTC1	IABTC1	IABTC1, IABTC3
Occupied bandwidth	SC, IABTC2 (Note 1)	SC, IABTC2 (Note 1)	SC, IABTC2 (Note 1)
Adjacent Channel Leakage power Ratio (ACLR)	IABTC1	IABTC3	IABTC1, IABTC3
Cumulative ACLR requirement in non-contiguous spectrum	–	IABTC3	IABTC3
Operating band unwanted emissions	IABTC1, SC (Note 2)	IABTC1, IABTC3, SC (Note 2)	IABTC1, IABTC3, SC (Note 2)
Transmitter spurious emissions	IABTC1	IABTC3	IABTC1, IABTC3
Transmitter intermodulation	IABTC1	IABTC1, IABTC3	IABTC1, IABTC3
Reference sensitivity level	SC	SC	SC
Dynamic range	SC	SC	SC
Adjacent Channel Selectivity (ACS)	IABTC1	IABTC3	IABTC1, IABTC3
In-band blocking	IABTC1	IABTC3	IABTC1, IABTC3
Out-of-band blocking	IABTC1	IABTC3	IABTC1, IABTC3
Receiver spurious emissions	IABTC1	IABTC3	IABTC1, IABTC3
Receiver intermodulation	IABTC1	IABTC3	IABTC1, IABTC3
In-channel selectivity (only applied to IAB-DU)	SC	SC	SC
Note 1: IABTC2 is only applicable when contiguous CA is supported. Note 2: OBUE SC shall be tested using the widest supported channel bandwidth and the highest supported sub-carrier spacing.

Table 4.8.3-2: Test configurations for a IAB capable of simultaneous operation in a single band

IAB test case	Contiguous spectrum capable IAB	C and NC capable IAB with identical parameters	C and NC capable IAB with different parameters
Output power	IABTC1	IABTC1	IABTC1, IABTC3
Transmit ON/OFF power (only applied to NR TDD IAB)	IABTC1	IABTC1	IABTC1, IABTC3
Frequency error	Tested with Error Vector Magnitude	Tested with Error Vector Magnitude	Tested with Error Vector Magnitude
Error Vector Magnitude	IABTC1	IABTC1	IABTC1, IABTC3
Time alignment error between IAB-DU and IAB-MT	IABTC1	IABTC1	IABTC1, IABTC3
Adjacent Channel Leakage power Ratio (ACLR)	IABTC1	IABTC3	IABTC1, IABTC3
Cumulative ACLR requirement in non-contiguous spectrum	–	IABTC3	IABTC3
Operating band unwanted emissions	IABTC1 (Note 2)	IABTC1, IABTC3 (Note 2)	IABTC1, IABTC3 (Note 2)
Transmitter spurious emissions	IABTC1	IABTC3	IABTC1, IABTC3
Transmitter intermodulation	IABTC1	IABTC1, IABTC3	IABTC1, IABTC3
Adjacent Channel Selectivity (ACS)	IABTC1	IABTC3	IABTC1, IABTC3
In-band blocking	IABTC1	IABTC3	IABTC1, IABTC3
Out-of-band blocking	IABTC1	IABTC3	IABTC1, IABTC3
Receiver spurious emissions	IABTC1	IABTC3	IABTC1, IABTC3
Receiver intermodulation	IABTC1	IABTC3	IABTC1, IABTC3
Note 1: IABTC2 is only applicable when contiguous CA is supported. Note 2: OBUE SC shall be tested using the widest supported channel bandwidth and the highest supported sub-carrier spacing.

Table 4.8.4-2: Test configuration for a IAB capable of simultaneous operation in multi-band operation

IAB test case	Test configuration
	Common connector	Separate connectors
Output power	IABTC1/3 (Note 1), IABTC4	IABTC1/3 (Note 1), IABTC4
RE Power control dynamic range (only applied to IAB-DU)	Tested with Error Vector Magnitude	Tested with Error Vector Magnitude
Transmit ON/OFF power (only applied to NR TDD IAB)	IABTC4	IABTC4
Frequency error	Tested with Error Vector Magnitude	Tested with Error Vector Magnitude
Error Vector Magnitude	IABTC1/3 (Note 1), IABTC4	IABTC1/3 (Note 1), IABTC4
Time alignment error between IAB-DU and IAB-MT	IABTC1/3 (Note 1), IABTC5 (Note 2)	IABTC1/3 (Note 1), IABTC5 (Note 2)
Adjacent Channel Leakage power Ratio (ACLR)	IABTC1/3 (Note 1), IABTC5 (Note 4)	IABTC1/3 (Note 1, 5), IABTC5 (Note 4, 5)
Cumulative ACLR requirement in non-contiguous spectrum	IABTC3 (Note 1), IABTC5 (Note 4)	IABTC3 (Note 1, 5)
Operating band unwanted emissions	IABTC1/3 (Note 1), IABTC5, SC (Note 7)	IABTC1/3 (Note 1, 5), IABTC5 (Note 5)
Transmitter spurious emissions	IABTC1/3 (Note 1), IABTC5	IABTC1/3 (Note 1, 5), IABTC5 (Note 5)
Transmitter intermodulation	IABTC1/3 (Note 1)	IABTC1/3 (Note 1, 5)
Adjacent Channel Selectivity (ACS)	IABTC5	IABTC1/3 (Note 1), IABTC5 (Note 6)
In-band blocking	IABTC5	IABTC1/3 (Note 1), IABTC5 (Note 6)
Out-of-band blocking	IABTC5	IABTC1/3 (Note 1), IABTC5 (Note 6)
Receiver spurious emissions	IABTC1/3 (Note 1), IABTC5	IABTC1/3 (Note 1, 5), IABTC5 (Note 5)
Receiver intermodulation	IABTC5	IABTC1/3 (Note 1), IABTC5 (Note 6)
Note 1: IABTC1 and/or IABTC3 shall be applied in each supported operating band. Note 2: IABTC5 is only applicable when inter-band CA is supported. Note 3: Void. Note 4: IABTC5 may be applied for Inter RF Bandwidth gap only. Note 5: For single-band operation test, other TAB connector(s) is (are) terminated. Note 6: IABTC5 is only applicable for multi-band receiver.

4.8.4 Applicability of test configurations for multi-band operation

For an IAB node declared to be capable of multi-band operation, the test configuration in table 4.8.4-1 and/or table 4.8.3-1 shall be used for testing. In the case where multiple bands are mapped on common multi-band connector, the test configuration in the second column of table 4.8.4-1 shall be used. In the case where multiple bands are mapped on common single-band connector, the test configuration in table 4.8.3-1 shall be used. In the case where multiple bands are mapped on separate single-band connector or multi-band connector, the test configuration in the third column of table 4.8.4-1 shall be used.

For an IAB node declared to be capable of IAB simultaneous operation of multi-band operation, the test configuration in table 4.8.4-2 and/or table 4.8.3-2 shall be used for testing. In the case where multiple bands are mapped on common multi-band connector, the test configuration in the second column of table 4.8.4-2 shall be used. In the case where multiple bands are mapped on common single-band connector, the test configuration in table 4.8.3-2 shall be used. In the case where multiple bands are mapped on separate single-band connector or multi-band connector, the test configuration in the third column of table 4.8.4-2 shall be used.

Unless otherwise stated, single carrier configuration (SC) tests shall be performed using signal with narrowest supported channel bandwidth and the smallest supported sub-carrier spacing.

Table 4.8.4-1: Test configuration for a IAB capable of multi-band operation

IAB test case	Test configuration
	Common connector	Separate connectors
Output power	IABTC1/3 (Note 1), IABTC4	IABTC1/3 (Note 1), IABTC4
RE Power control dynamic range (only applied to IAB-DU)	Tested with Error Vector Magnitude	Tested with Error Vector Magnitude
Total power dynamic range	SC	SC
Transmit ON/OFF power (only applied to NR TDD IAB)	IABTC4	IABTC4
Frequency error	Tested with Error Vector Magnitude	Tested with Error Vector Magnitude
Error Vector Magnitude	IABTC1/3 (Note 1), IABTC4	IABTC1/3 (Note 1), IABTC4
Time alignment error (only applied to IAB-DU)	IABTC1/3 (Note 1), IABTC5 (Note 2)	IABTC1/3 (Note 1), IABTC5 (Note 2)
Occupied bandwidth	SC, IABTC2 (Note 3)	SC, IABTC2 (Note 3)
Adjacent Channel Leakage power Ratio (ACLR)	IABTC1/3 (Note 1), IABTC5 (Note 4)	IABTC1/3 (Note 1, 5), IABTC5 (Note 4, 5)
Cumulative ACLR requirement in non-contiguous spectrum	IABTC3 (Note 1), IABTC5 (Note 4)	IABTC3 (Note 1, 5)
Operating band unwanted emissions	IABTC1/3 (Note 1), IABTC5, SC (Note 7)	IABTC1/3 (Note 1, 5), IABTC5 (Note 5), SC(Note 7)
Transmitter spurious emissions	IABTC1/3 (Note 1), IABTC5	IABTC1/3 (Note 1, 5), IABTC5 (Note 5)
Transmitter intermodulation	IABTC1/3 (Note 1)	IABTC1/3 (Note 1, 5)
Reference sensitivity level	SC	SC
Dynamic range	SC	SC
Adjacent Channel Selectivity (ACS)	IABTC5	IABTC1/3 (Note 1), IABTC5 (Note 6)
In-band blocking	IABTC5	IABTC1/3 (Note 1), IABTC5 (Note 6)
Out-of-band blocking	IABTC5	IABTC1/3 (Note 1), IABTC5 (Note 6)
Receiver spurious emissions	IABTC1/3 (Note 1), IABTC5	IABTC1/3 (Note 1, 5), IABTC5 (Note 5)
Receiver intermodulation	IABTC5	IABTC1/3 (Note 1), IABTC5 (Note 6)
In-channel selectivity (only applied to IAB-DU)	SC	SC
Note 1: IABTC1 and/or IABTC3 shall be applied in each supported operating band. Note 2: IABTC5 is only applicable when inter-band CA is supported. Note 3: IABTC2 is only applicable when contiguous CA is supported. Note 4: IABTC5 may be applied for Inter RF Bandwidth gap only. Note 5: For single-band operation test, other TAB connector(s) is (are) terminated. Note 6: IABTC5 is only applicable for multi-band receiver. Note 7: OBUE SC shall be tested using the widest supported channel bandwidth and the highest supported sub-carrier spacing.

4.9 RF channels and test models

4.9.1 RF channels

For the single carrier testing many tests in this TS are performed with appropriate frequencies in the bottom, middle and top channels of the supported frequency range of the IAB. These are denoted as RF channels B (bottom), M (middle) and T (top).

Unless otherwise stated, the test shall be performed with a single carrier at each of the RF channels B, M and T.

Many tests in this TS are performed with the maximum IAB RF Bandwidth located at the bottom, middle and top of the supported frequency range in the operating band. These are denoted as B_RFBW (bottom), M_RFBW (middle) and T_RFBW (top).

Unless otherwise stated, the test shall be performed at B_RFBW, M_RFBW and T_RFBW defined as following:

– B_RFBW: maximum IAB RF Bandwidth located at the bottom of the supported frequency range in the operating band.

– M_RFBW: maximum IAB RF Bandwidth located in the middle of the supported frequency range in the operating band.

– T_RFBW: maximum IAB RF Bandwidth located at the top of the supported frequency range in the operating band.

Occupied bandwidth test in this TS is performed with the aggregated IAB channel bandwidth and sub-block bandwidths located at the bottom, middle and top of the supported frequency range in the operating band. These are denoted as B_{BW Channel CA}(bottom), M_{BW Channel CA} (middle) and T_{BW Channel CA} (top) for contiguous spectrum operation.

Unless otherwise stated, the test for contiguous spectrum operation shall be performed at B_{BW Channel CA}, M_{BW Channel CA}and T_{BW Channel CA}defined as following:

– B_{BW Channel CA}: aggregated IAB channel bandwidth located at the bottom of the supported frequency range in each operating band;

– M_{BW Channel CA}: aggregated IAB channel bandwidth located close in the middle of the supported frequency range in each operating band;

– T_{BW Channel CA}: aggregated IAB channel bandwidth located at the top of the supported frequency range in each operating band.

For IAB capable of multi-band operation, unless otherwise stated, the test shall be performed at B_RFBW_T’_RFBW and B’_RFBW_T_RFBW defined as following:

– B_RFBW_T’_RFBW: the IAB RF Bandwidths located at the bottom of the supported frequency range in the lowest operating band and at the highest possible simultaneous frequency position, within the Maximum Radio Bandwidth, in the highest operating band.

– B’_RFBW_T_RFBW: the IAB RF Bandwidths located at the top of the supported frequency range in the highest operating band and at the lowest possible simultaneous frequency position, within the Maximum Radio Bandwidth, in the lowest operating band.

NOTE: B_RFBW_T’_RFBW = B’_RFBW_T_RFBW = B_RFBW_T_RFBW when the declared Maximum Radio Bandwidth spans all operating bands. B_RFBW_T_RFBW means the IAB RF Bandwidths are located at the bottom of the supported frequency range in the lower operating band and at the top of the supported frequency range in the upper operating band.

When a test is performed by a test laboratory, the position of B, M and T for single carrier, B_RFBW, M_RFBW and T_RFBWfor single band operation, B_{BW Channel CA}, M_{BW Channel CA} and T_{BW Channel CA}forcontiguous spectrum operation in each supported operating band, the position of B_RFBW_T’_RFBW and B’_RFBW_T_RFBW in the supported operating band combinations shall be specified by the laboratory. The laboratory may consult with operators, the manufacturer or other bodies.

4.9.2 Test models

4.9.2.1 General

The following clauses will describe the FR1 test models needed for IAB type 1-H. Note that the NR FR1 test models are also applicable to IAB type 1-O conformance testing in TS 38.176-2 [3].

4.9.2.2 FR1 test models for IAB-DU

FR1 test model in clause 4.9.2.2 in TS 38.141-1[13] applies to IAB-DU as below:

NR-FR1-TM1.1 applies to IAB-DU-FR1-TM1.1

NR-FR1-TM1.2 applies to IAB-DU-FR1-TM1.2

NR-FR1-TM2 applies to IAB-DU-FR1-TM2

NR-FR1-TM2a applies to IAB-DU-FR1-TM2a

NR-FR1-TM3.1 applies to IAB-DU-FR1-TM3.1

NR-FR1-TM3.1a applies to IAB-DU-FR1-TM3.1a

NR-FR1-TM3.2 applies to IAB-DU-FR1-TM3.2

NR-FR1-TM3.3 applies to IAB-DU-FR1-TM3.3

Testing models applying to NB-IoT operation in clause 4.9.2.2 in TS 38.141-1[13] are not applicable to IAB-DU.

4.9.2.3 FR1 test models for IAB-MT

4.9.2.3.1 General

The set-up of physical channels for transmitter tests shall be according to one of the FR1 test models (IAB-MT- FR1‑TM) below. A reference to the applicable test model is made within each test.

The following general parameters are used by all IAB-MT test models:

– Duration is 2 radio frames for TDD (20 ms)

– The slots are numbered 0 to 10×2^µ – 1 where µ is the numerology corresponding to the subcarrier spacing

– N_RB is the maximum transmission bandwidth configuration seen in clause 5.3.2 in TS 38.174[2].

– Normal CP

– Virtual resource blocks of localized type

IAB-MT test models are derived based on the uplink/downlink configuration as shown in the table 4.9.2.3.1-1 using information element TDD-UL-DL-ConfigCommon as defined in TS 38.331 [14].

Table 4.9.2.3.1-1: Configurations of TDD for IAB type 1-H test models

Field name	Value
referenceSubcarrierSpacing (kHz)	15	30	60
Periodicity (ms) for dl-UL-TransmissionPeriodicity	5	5	5
nrofDownlinkSlots	3	7	14
nrofDownlinkSymbols	10	6	12
nrofUplinkSlots	1	2	4
nrofUplinkSymbols	2	4	8

Common physical channel parameters for all IAB-MT FR1 test models are specified in table 4.9.2.3.1-2 and table 4.9.2.3.1-3 for PUSCH. Specific physical channel parameters for IAB-MT FR1 test models are described in clauses 4.9.2.3.2 to 4.9.2.3.5.

Table 4.9.2.3.1-2: Common physical channel parameters for PUSCH for IAB type 1-H test models

Parameter	Value
Mapping type	PUSCH mapping type A
dmrs-TypeA-Position for the first DM-RS symbol	pos2
dmrs-AdditionalPosition for additional DM-RS symbol(s)	Pos1
dmrs-Type for comb pattern	Configuration type 1
maxLength	1
Ratio of PUSCH EPRE to DM-RS EPRE	0 dB

Table 4.9.2.3.1-3: Common physical channel parameters for PUSCH by RNTI for IAB type 1-H test models

Parameter	Value
PUSCH

4.9.2.3.2 FR1 test model 1.1 (IAB-MT-FR1-TM1.1)

This model shall be used for tests on:

– IAB output power

– Transmit ON/OFF power

– Unwanted emissions

– Occupied bandwidth

– ACLR

– Operating band unwanted emissions

– Transmitter spurious emissions

– Transmitter intermodulation

– Receiver spurious emissions

Common physical channel parameters are defined in clause 4.9.2.3.1. Specific physical channel parameters for IAB-MT-FR1-TM1.1 are defined in table 4.9.2.3.2-1.

Table 4.9.2.3.2-1: Specific physical channel parameters of IAB-MT-FR1-TM1.1

Parameter	Value
# of PRBs PUSCH	N_RB
Modulation PUSCH	QPSK

4.9.2.3.3 FR1 test model 2 (IAB-MT-FR1-TM2)

This model shall be used for tests on:

– Total power dynamic range (at lower PSD TX power limit at min power)

– Transmitted signal quality

– EVM of single 64QAM PRB allocation (at lower PSD TX power limit at min power)

– Frequency error (at min power)

Common physical channel parameters are defined in clause 4.9.2.3.1. Specific physical channel parameters for IAB-MT-FR1-TM2 are defined in table 4.9.2.3.3-1.

Table 4.9.2.3.3-1: Specific physical channel parameters of IAB-MT-FR1-TM2

Parameter

Value

# of 64QAM PUSCH PRBs

Level of boosting (dB)

Location of 64QAM PRB

Slot	RB	n
3n	0
3n+1
3n+2

# of PUSCH PRBs which are not allocated

4.9.2.3.3a FR1 test model 2a (IAB-MT-FR1-TM2a)

This model shall be used for tests on:

– EVM of single 256QAM PRB allocation (at min power)

– Frequency error (at min power)

Common physical channel parameters are defined in clause 4.9.2.3.3. Physical channel parameters and numbers of the allocated PRB are defined in table 4.9.2.3.3-1 with all 64QAM PUSCH PRBs replaced by 256QAM PUSCH PRBs.

4.9.2.3.4 FR1 test model 3.1 (IAB-MT-FR1-TM3.1)

This model shall be used for tests on:

– Output power dynamics

– Total power dynamic range (upper TX PSD power limit at max power with all 64QAM PRBs allocated)

– Transmitted signal quality

– Frequency error (at max power)

– EVM for modulation (at max power)

Common physical channel parameters are defined in clause 4.9.2.3.1. Physical channel parameters are defined in table 4.9.2.3.2-1 with all QPSK PUSCH PRBs replaced with selected modulation order PUSCH PRBs according to the corresponding test procedure.

4.9.2.3.5 FR1 test model 3.1a (IAB-MT-FR1-TM3.1a)

This model shall be used for tests on:

– Output power dynamics

– Total power dynamic range (upper TX PSD power limit at max power with all 256QAM PRBs allocated)

– Transmitted signal quality

– Frequency error (at max power)

– EVM for 256QAM modulation (at max power)

Common physical channel parameters are defined in clause 4.9.2.3.1. Physical channel parameters are defined in table 4.9.2.3.2-1 with all QPSK PUSCH PRBs replaced by 256QAM PUSCH PRBs.

4.9.2.4 Data content of Physical channels and Signals for IAB-MT-FR1-TM

4.9.2.4.1 General

Randomisation of the data content is obtained by utilizing a PN sequence generator and the length-31 Gold sequence scrambling of TS 38.211 [9], clause 5.2.1 which is invoked by all physical channels prior to modulation and mapping to the RE grid.

Initialization of the scrambler and RE-mappers as defined in TS 38.211 [9] use the following additional parameters:

– , Physical layer cell identity = 1 is used as the default physical layer cell identity

– q = 0 (single code word)

– Rank 1, single layer

4.9.2.4.2 PUSCH

– Generate the required amount of bits from the output of the PN23 sequence generator [15]. The PN sequence generator is initialized with a starting seed of "all ones" in the first allocated slot of each frame. The PN sequence is continuous over the slot boundaries.

– Perform user specific scrambling according to TS 38.211 [9], clause 6.3.1.1.

– Perform modulation of the scrambled bits with the modulation scheme defined for each user according to TS 38.211 [9], clause 6.3.1.2

–

– Perform mapping of the complex-valued symbols to layer according to TS 38.211 [9], clause 6.3.1.3.

– Perform PUSCH mapping according to TS 38.211 [9] using parameters listed in table 4.9.2.3-2.

– DM-RS sequence generation according to TS 38.211 [9], clause 6.4.1.1.1 where l is the OFDM symbol number within the slot with the symbols indicated by table 4.9.2.2-3.

–

– DM-RS mapping according to TS 38.211 [9], clause 6.4.1.1.3 using parameters listed in table 4.9.2.2-3.

4.10 Requirements for contiguous and non-contiguous spectrum

A spectrum allocation where an IAB-DU or IAB-MT operates can either be contiguous or non-contiguous. Unless otherwise stated, the requirements in the present specification apply for IAB-DU and IAB-MT configured for both contiguous spectrum operation and non-contiguous spectrum operation.

For IAB-DU or IAB-MT operation in non-contiguous spectrum, some requirements apply both at the IAB RF Bandwidth edges and inside the sub-block gaps. For each such requirement, it is stated how the limits apply relative to the IAB RF Bandwidth edges and the sub-block edges respectively.

4.11 Requirements for IAB capable of multi-band operation

For multi-band connector the conducted test requirements in clause 6 and 7 apply separately to each supported operating band unless otherwise stated. For some requirements, it is explicitly stated that specific additions or exclusions to the requirement apply at multi-band connector(s) as detailed in the requirement clause. For IAB-DU or IAB-MT capable of multi-band operation, various structures in terms of combinations of different transmitter and receiver implementations (multi-band or single band) with mapping of transceivers to one or more TAB connectors for IAB type 1-H in different ways are possible. For multi-band connector(s) the exclusions or provisions for multi-band apply. For single-band connector(s), the following applies:

– Single-band transmitter spurious emissions, operating band unwanted emissions, ACLR, transmitter intermodulation and receiver spurious emissions requirements apply to this connector that is mapped to single-band.

– If the IAB-DU or IAB-MT is configured for single-band operation, single-band requirements shall apply to this connector configured for single-band operation and no exclusions or provisions for multi-band capable IAB-DU or IAB-MT are applicable. Single-band requirements are tested separately at the connector configured for single-band operation, with all other TAB connectors terminated.

An IAB type 1-H may be capable of supporting operation in multiple operating bands with one of the following implementations of TAB connectors in the transceiver array boundary:

– All TAB connectors are single-band connectors.

– Different sets of single-band connectors support different operating bands, but each TAB connector supports only operation in one single operating band.

– Sets of single-band connectors support operation in multiple operating bands with some single-band connectors supporting more than one operating band.

– All TAB connectors are multi-band connectors.

– A combination of single-band sets and multi-band sets of TAB connectors provides support of the type IAB type 1-H capability of operation in multiple operating bands.

Unless otherwise stated all requirements specified for an operating band apply only to the set of TAB connectors supporting that operating band.

In the case of an operating band being supported only by single-band connectors in a TAB connector TX min cell group or a TAB connector RX min cell group, single-band requirements apply to that set of TAB connectors.

In the case of an operating band being supported only by multi-band connectors supporting the same operating band combination in a TAB connector TX min cell group or a TAB connector RX min cell group, multi-band requirements apply to that set of TAB connectors.

For multi-band connectors supporting the bands for TDD, the RF requirements in the present specification assume no simultaneous uplink and downlink occur between the bands.

NOTE 1: The case of an operating band being supported by both multi-band connectors and single-band connectors in a TAB connector TX min cell group or a TAB connector RX min cell group is not covered by the present release of the present document.

NOTE 2: The case of an operating band being supported by multi-band connectors which are not all supporting the same operating band combination in a TAB connector TX min cell group or a TAB connector RX min cell group is not covered by the present release of the present document.

4.12 Format and interpretation of tests

Each test has a standard format:

X Title

All tests are applicable to all equipment within the scope of the present document, unless otherwise stated.

X.1 Definition and applicability

This clause gives the general definition of the parameter under consideration and specifies whether the test is applicable to all equipment or only to a certain subset. Required manufacturer declarations may be included here.

X.2 Minimum requirement

This clause contains the reference to the clause to the 3GPP reference (or core) specification which defines the minimum requirement.

X.3 Test purpose

This clause defines the purpose of the test.

X.4 Method of test

X.4.1 General

In some cases there are alternative test procedures or initial conditions. In such cases, guidance for which initial conditions and test procedures can be applied are stated here. In the case only one test procedure is applicable, that is stated here.

X.4.2y First test method

X.4.2y.1 Initial conditions

This clause defines the initial conditions for each test, including the test environment, the RF channels to be tested and the basic measurement set-up.

X.4.2y.2 Procedure

This clause describes the steps necessary to perform the test and provides further details of the test definition like domain (e.g. frequency-span), range, weighting (e.g. bandwidth), and algorithms (e.g. averaging). The procedure may comprise data processing of the measurement result before comparison with the test requirement (e.g. average result from several measurement positions).

X.4.3y Alternative test method (if any)

If there are alternative test methods, each is described with its initial conditions and procedures.

X.5 Test requirement

This clause defines the pass/fail criteria for the equipment under test, see clause 4.1.3 (Interpretation of measurement results). Test requirements for every minimum requirement referred in clause X.2 are listed here. Cases where minimum requirements do not apply need not be mentioned.

4.13 Test efficiency optimization

When manufacture declares the same RF implementation for IAB-MT and IAB-DU (D.IAB-1) and the declarations in table 4.13-1 are the same for IAB-DU and IAB-MT, it is sufficient to test only IAB-MT or IAB-DU with the test requirement applicability according to Table 4.13-2 for Tx requirements and Table 4.13-3 for Rx requirements.

For IAB type 1-H it is required that the DUT selection between requirements follows following rules:

– Out of maximum output transmit power, modulation quality and ACLR, operating band unwanted emissions and transmitter general spurious emissions, IAB-DU and IAB-MT are required to be the DUT at least once,

– Out of reference sensitivity, receiver spurious emissions, receiver intermodulation, IAB-DU and IAB-MT are required to be the DUT at least once.

In some cases, the test requirements are the same but the MU for the IAB-MT may be larger than for the IAB-DU. In cases where the test efficiency optimization is applicable the lower MU value should be used.

Table 4.13-1: Declarations required to be the same for IAB-DU and IAB-MT for test efficiency optimization to apply

Declaration identifier	Declaration	Additional conditions	Applicability
			IAB-DU type 1-H	IAB-MT type 1-H
D.2	IAB class	Medium range IAB-DU can apply test efficiency optimization with wide area IAB-MT in case other declarations in this table are the same.	x	x
D.3	Operating bands and frequency ranges		x	x
D.8	Single band connector or multi-band connector		x	x
D.11	Maximum IAB RF Bandwidth		x	x
D.13	Total RF bandwidth (BW_tot)		x	x
D.14	NR supported channel bandwidths and SCS		x	x
D.17	Maximum number of supported carriers per operating band in single band operation		x	x
D.18	Maximum number of supported carriers per operating band in multi-band operation		x	x
D.19	Total maximum number of supported carriers in multi-band operation		x	x
D.20	Other band combination multi-band restrictions		x	x
D.21	Rated carrier output power (P_rated,c,AC, or P_rated,c,TABC)		x	x
D.22	Rated total output power (P_rated,t,AC, or P_rated,t,TABC)		x	x

Table 4.13-2: Test requirement applicability for TX requirements

Tx requirement		Test efficiency optimization applicable	Test requirement applicability (Note 1)
Maximum output power		Yes
Output power dynamics (only for IAB-DU)		No	(Note 2)
Output power dynamics (only for IAB-MT)		No	(Note 2)
Transmitter OFF power		Yes
Transient period		Yes
IAB-DU Frequency Error		No	(Note 2)
IAB-MT Frequency Error		No	(Note 2)
Modulation quality		Yes
Time alignment error (only for IAB-DU)		No	(Note 2)
Occupied bandwidth		Yes
ACLR		Yes
Operating band unwanted emission		Yes
Transmitter spurious emission	General requirement
	Additional spurious emissions
	Co-location with other base stations
OTA transmitter intermodulation		Yes
Note 1: Test requirement applicability defines how to select whether IAB-DU or IAB-MT test requirement is applied. In case no applicability definition is provided or the applicability definition test requirement is the same for IAB-DU and IAB-MT, either can apply. NOTE 2: Test efficiency optimization is not applicable and therefore original test requirement applies.

Table 4.13-3: Test requirement applicability for receiver requirements

Rx requirement		Test efficiency optimization applicable	Test requirement applicability (Note 1)
Reference sensitivity		Yes
Dynamic range (only for IAB-DU)		No	(Note 2)
Adjacent channel selectivity		Yes	IAB-MT
In-band blocking		Yes	IAB-MT
Out-of-band blocking	General requirement		IAB-MT
	Co-location requirement
Receiver spurious emissions		Yes
Receiver intermodulation		Yes	IAB-MT
In-channel selectivity (only for IAB-DU)		No	(Note 2)
Note 1: Test requirement applicability defines how to select whether IAB-DU or IAB-MT test requirement is applied. In case no applicability definition is provided or the applicability definition test requirement is the same for IAB-DU and IAB-MT, either can apply. NOTE 2: Test efficiency optimization is not applicable and therefore original test requirement applies.

4.14 Requirements for IAB-DU and IAB-MT capable of simultaneous operation

IAB-DU and IAB-MT can be configured as IAB Simultaneous Operation based on declaration. Unless otherwise stated, the requirements in the present specification apply for IAB-MT and IAB-DU of IAB-node configured as IAB Simultaneous Operation. For IAB-DU and IAB-MT simultaneous transmission, the requirements for IAB-DU apply. For IAB-DU and IAB-MT simultaneous reception, the requirements for IAB-MT apply.

For IAB-node in IAB Simultaneous Operation, as detailed in the requirement clause, transmitter requirements apply whatever the type of transmitter considered and for all transmission modes foreseen by the manufacturer’s specification as detailed in the requirement clause.

NOTE: For IAB node operating as simultaneous transmission of IAB-DU and IAB-MT, the manufacturer can provide different declarations on power imbalance between IAB-DU and IAB-MT for verification on Modulation quality and ACLR according to the conformance specification declaration requirements.

For IAB-node in IAB Simultaneous Operation, as detailed in the requirement clause, receiver requirements shall be met for any transmitter setting unless otherwise stated.