6 Test environments for Signalling test
38.508-13GPP5GSPart 1: Common test environmentRelease 17TSUser Equipment (UE) conformance specification
6.1 Requirements of test equipment
6.1.1 Requirements common for conducted and OTA tests
The requirements of test equipment specified in this subclause apply to Signalling test cases defined in TS 38.523-1 [12], in addition to the common requirements of test equipment specified in clause 4.2 of this specification.
Test equipment shall be able to simulate cells of Radio Access Technologies NR, E-UTRA, and UTRA. The number of cells to be simulated simultaneously by the test equipment shall not exceed the resources specified in Table 6.1-1
Table 6.1-1: Maximum resources in terms of number / configuration of cells to be simulated simultaneously in a test setup
Simulation of |
Max. number of cells |
Max. number of cells |
Max. number of cells |
||||
Conducted |
OTA(FR1+FR2) |
OTA(FR2) |
Conducted |
OTA |
Conducted |
OTA |
|
NR single-mode networks (FDD or TDD) |
4 cells |
4 cells |
4 cells |
n/a |
n/a |
n/a |
n/a |
NR dual-mode networks (FDD and TDD) |
4 cells |
4 cells |
4 cells |
n/a |
n/a |
n/a |
n/a |
NR networks involving Carrier Aggregation |
4 cells |
4 cells |
4 cells |
n/a |
n/a |
n/a |
n/a |
NR dual connectivity (NR-DC) |
4 cells |
4 cells |
4 cells |
n/a |
n/a |
n/a |
n/a |
NR dual connectivity (EN-DC) |
4 cells |
4 cells |
4 cells |
2 cells |
2 cells |
n/a |
n/a |
NR dual connectivity (EN-DC) involving Carrier Aggregation |
4 cells |
4 cells |
4 cells |
2 cells |
2 cells |
n/a |
n/a |
Mixed E-UTRA / NR networks |
4 cells |
4 cells |
4 cells |
2 cells |
2 cells |
n/a |
n/a |
Mixed UTRA / NR networks |
4 cells |
4 cells |
4 cells |
n/a |
n/a |
2 cells |
2 cells |
Note 1: No differentiation between cell configuration types (as defined in clause 6.3.1) here, because these types are only relevant to specific test cases and their TTCN-3 implementation. Note 2: Only network scenarios specified in clauses 4.4.1 and 6.3.2.1 have been covered. Note 3: In case of Carrier Aggregation, each cell can act as a SpCell, an SCell, or a standalone cell (not used as a CA component carrier). Note 4: In order to support test case requirements for conducted and OTA test methods, the number of active cells at any given time should be minimised in order to ensure maximum re use of SS Tx/Rx resources. |
Exceptions to the requirements outlined above are possible but need special evidence to be provided explicitly in the test case prose and should be allowed only if the test case purpose cannot be met otherwise.
Due to limited power level range for FR2 OTA test methods, when defining test cases requirements, care shall be taken to ensure that the number of active cells is minimised as this has an impact to have distinguishable power level difference. Cells that are used in initial parts of test cases and are no longer required for the rest of the procedure shall be clearly defined as Non-suitable "Off" cell to facilitate re use of SS Tx/Rx resources.
NR FR2 signal levels are defined along with a calibration procedure as well as uncertainty. Therefore, maximum 4 FR2 OTA Cells can be configured and activated including the test cases involving idle or connected mode measurements.
NR FR1+FR2 OTA calibration procedure is undefined which does not restrict to configure maximum 4 FR1+FR2 OTA cells. However, caution must be taken as specified in clause 6.2.2.2.3.
E-UTRA OTA calibration procedure is undefined which does not restrict to configure maximum 2 E-UTRA OTA cells. However, caution must be taken as specified in clause 6.2.2.2.4.
UTRA OTA calibration procedure is undefined which does not restrict to configure maximum 2 UTRA OTA cells. However, caution must be taken as specified in clause 6.2.2.2.5.
6.1.2 Requirements for conducted test method
No requirements are specified in addition to the common requirements described in clause 4.2 and clause 6.1.1.
6.1.3 Requirements for OTA test method
6.1.3.1 General
Editor’s Note: The UE pre-configuration mentioned below to disable UL Tx diversity schemes shall be voided once a test methodology solution to minimize spectral flatness artefacts between TE and UE over all test points is defined.
The DFF or IFF based OTA test methodologies, defined in Annex B.1 should be used for Signalling test.
NOTE: For single cell test cases, usage of NF test methodology is not precluded.
Clause 6.1.3.2 describes a sample OTA measurement test setup and clause 6.1.3.3 describes approaches to select a UE orientation.
For conformance testing using the OTA test environment, the UE under test shall be pre-configured with UL Tx diversity schemes disabled to account for single polarization System Simulator (SS) in the test environment. The UE under test may transmit with dual polarization. This approach also applies to calibration stage..
6.1.3.2 Sample OTA Measurement Test Setup
Please refer to Figure 6.1.3.2-1 for a sample OTA measurement test setup.
Figure 6.1.3.2-1: Sample OTA measurement setup
NOTE: Figure 6.1.3.2-1 is for illustrative purposes only.
For 5G NR signalling test cases, depending on the dynamic range of measurements the system complexity can be reduced. In the switch unit, as shown in Figure 6.1.3.2-1, the switches K7, K8, K9, K10 can be removed. The amplifier (PA/LNA) is optional. For the "single cell" and "multiple cell" test cases, the gNB emulator can be directly connected to the feed horn.
6.1.3.3 Procedure for selecting UE Orientation and for calibration
Set calibrated power level at the centre of the quiet zone for each polarization individually [FFS].
Before starting the test, the UE orientation with which the test system can provide a wide enough dynamic range to perform the test scenarios needs to be identified in order to obtain sufficient link budget.
The UE orientation can be determined by either of the approaches below:
– Approach 1: UE vendor declares the direction in which the measurement has to be made. In this case, the declaration confirms that the Rx Beam peak conditions in FR2 specified in TS 38.133 [13] Annex B are met
– Approach 2: Perform an Rx-beam peak search
For Approach 2 an Rx beam peak search needs to be performed as per the procedure in TS 38.521-2 [15] Annex K, which finds the direction in which Rx Beam peak conditions in FR2 specified in TS 38.133 [13] Annex B are met.
RSRP measurements can be configured by SS in X2NR meas configurations using FFS preambles in NSA (Ex – RRC_Connected with connectivity parameter E-UTRA with MCG Only bearer established and meas config enabled for event B1 (Ex-per TC 8.2.3.1.1 of TS 38.523-1)) and FFS preambles in SA modes.
When signal level calibrated with a reference antenna (only applicable to single-cell test cases without thresholds):
– The RSRP reported from the DUT is within [±FFSdB] of expected RSRP mentioned in Table 6.2.2.2-1.
When signal level calibrated with the RSRP-based calibration:
– Before starting the tests, Rx-beam peak directions need to be determined using Approach 1 or Approach 2 above. Rx beam peak direction may depend on the operating band under test. If Rx-beam peak directions for all the operating bands required for test scenarios are identical, three different levels in Table 6.2.2.2-2 can be used in the test scenarios.
– Rx-beam peak directions are decided to be ‘identical’, if the detected beam peak positions are direct neighbours on the measurement grid.
If Rx-beam peak directions are identical:
1. Position the UE so that the Rx beam peak direction is aligned towards the measurement antenna.
2. Make the UE report SS-RSRP at each frequency used in the test scenarios, while setting the downlink SS power at the centre of the quiet zone to -82dBm/SCS. Here, the SS-RSRP reported levels are denoted as PRSRP(f).
3. Calculate ‘Delta(NRf)’ for each carrier frequency used in the test case, using the equation: Delta(NRf) = PRSRP(f) + 82.
6.1.3.4 Handling of Thresholds
Where a threshold value is specified in the test case (value identified as THtest case) it is signalled to the UE with a value THsig according to table 6.1.3.4-1.
Table 6.1.3.4-1: Handling of signalled threshold values
Type of Threshold |
Signalled value |
Comment |
Absolute |
THsig(f) = THtest case + Delta(NRf) |
Delta(NRf) value according to the frequency of the cell being compared to the threshold |
Relative, intra-frequency |
THsig(f) = THtest case |
|
Relative, inter-frequency |
a3-Offset sig = a3-Offset test case + Delta(NRfn) – Delta(NRfp) |
Delta(NRfp) is the Delta value for the SpCell frequency Delta(NRfn) is the Delta value for the neighbour cell frequency |
Relative, inter-frequency, Event A6 |
a6-Offset sig = a6-Offset test case + Delta(NRfn) – Delta(NRfs) |
Delta(NRfs) is the Delta value for the SCell frequency Delta(NRfn) is the Delta value for the neighbour cell frequency |
6.1.4 Requirements for timer tolerances
The timer tolerances specified for the test environment in this subclause apply to all Signalling test cases defined in TS 38.523-1 [12] unless otherwise specified.
All the timers used during testing are within a tolerance margin given by the equation below. If for a specific test a different tolerance value is required, then this should be specified in the relevant test document (i.e. the document where the test is described).
Timer tolerance = 10%.
6.2 Reference test conditions
6.2.1 Physical Channel Allocations
6.2.1.1 Antennas
If the UE has two or more Rx antennas, the same downlink signal is applied to each one, except if MIMO is tested. All UE Rx antennas shall be connected.
If the UE has one Rx antenna, the downlink signal is applied to it.
6.2.1.2 Downlink physical channels and physical signals
In general for signalling test cases the power allocation for downlink physical channels and signals is specified in relation to a reference cell power.
Unless specifically specified otherwise in a signalling test case prose, all cells use only one beam.
In case of only one beam per cell this reference cell power is the EPRE of the secondary synchronization signal (SSS) and referred to as “SS/PBCH SSS EPRE”.
In case of more than one beam per cell the power levels of the different SS/PBCH blocks may be different what makes it difficult to specify the EPREs of other physical channels and signals relative to the EPRE of any SSS. Therefore for multiple beams test cases the power levels are specified relative to the reference cell power.
For single beam per cell test cases the power allocation of downlink physical channels for signalling test cases is specified in table 6.2.1.2-1, for multiple beams per cell test cases the power allocation is specified in table 6.2.1.2-2.
Table 6.2.1.2-1: Power allocation for OFDM symbols and reference signals for signalling test cases (single beam)
Parameter |
Unit |
Value |
Comment |
SSS transmit power |
dBm/SCS |
Test specific (Note 1) |
referred to as “SS/PBCH SSS EPRE” |
EPRE ratio of PSS to SSS |
dB |
0 |
|
EPRE ratio of PBCH DMRS to SSS |
dB |
0 |
|
EPRE ratio of PBCH to PBCH DMRS |
dB |
0 |
|
EPRE ratio of PDCCH DMRS to SSS |
dB |
0 |
|
EPRE ratio of PDCCH to PDCCH DMRS |
dB |
0 |
|
EPRE ratio of PDSCH DMRS to SSS |
dB |
0 |
|
EPRE ratio of PDSCH to PDSCH DMRS |
dB |
-3 |
To reduce interference from PDSCH of intra-frequency neighbour cells. |
EPRE ratio of PTRS to PDSCH |
dB |
3 |
i.e. the EPRE ratio of PTRS to SSS is 0dB |
Note 1: Power level chosen to align with cell power level as specified in clause 6.2.2. |
Table 6.2.1.2-2: Power allocation for OFDM symbols and reference signals for signalling test cases (multiple beam)
Parameter |
Unit |
Value |
Comment |
Reference cell power EPRECellRef |
dBm/SCS |
Test specific (Note 1) |
|
EPRE ratio of SSSSSB#N to EPRECellRef |
dB |
Test specific (Note 2) |
power of SSS within SSB with index N |
EPRE ratio of PSSSSB#N to SSSSSB#N |
dB |
0 |
power of PSS within SSB with index N |
EPRE ratio of PBCH DMRSSSB#N to SSSSSB#N |
dB |
0 |
power of PBCH DMRS within SSB with index N |
EPRE ratio of PBCHSSB#N to PBCH DMRSSSB#N |
dB |
0 |
power of PBCH within SSB with index N |
EPRE ratio of PDCCH DMRS to EPRECellRef |
dB |
0 |
(Note 3) |
EPRE ratio of PDCCH to PDCCH DMRS |
dB |
0 |
|
EPRE ratio of PDSCH DMRS to EPRECellRef |
dB |
0 |
(Note 3) |
EPRE ratio of PDSCH to PDSCH DMRS |
dB |
-3 |
To reduce interference from PDSCH of intra-frequency neighbour cells. |
EPRE ratio of PTRS to PDSCH |
dB |
3 |
i.e. the EPRE ratio of PTRS to EPRECellRef is 0dB |
EPRE ratio of CSI-RSN to EPRECellRef |
dB |
Test specific (Note 2) |
power of CSI-RS with index N; CSI-RS configured if required by a test case in TS 38.523-1 [12] |
Note 1: Power level chosen to align with cell power level as specified in clause 6.2.2. Note 2: Test cases may specify “OFF” in which case the attenuation shall result in an absolute EPRE value being equal or less than the power level specified for a non-suitable "Off" cell in clause 6.2.2. Note 3: In general the UE cannot distinguish from which beam DL data is sent ⇒ PDCCH and PDSCH are considered as cell specific rather than beam specific. |
6.2.1.3 Sidelink physical channels and physical signals
In general for signalling test cases the power allocation for sidelink physical channels and signals is specified in relation to a reference NR-SS-UE power.
The power allocation of sidelink physical channels for signalling test cases is specified in table 6.2.1.3-1.
Table 6.2.1.3-1: Power allocation for OFDM symbols and reference signals for signalling test cases
Parameter |
Unit |
Value |
Comment |
Reference NR-SS-UE power EPRENRSSUERef |
dBm/SCS |
Test specific (Note 1) |
|
EPRE ratio of S-SSS to EPRENRSSUERef |
dB |
Test specific (Note 2) |
Power of S-SSS within S-SSB S-SSB configured if required by a test case in TS 38.523-1 [12] |
EPRE ratio of S-PSS to S-SSS |
dB |
0 |
Power of S-PSS within S-SSB S-SSB configured if required by a test case in TS 38.523-1 [12] |
EPRE ratio of PSBCH DMRS to S-SSS |
dB |
0 |
Power of PSBCH DMRS within S-SSB S-SSB configured if required by a test case in TS 38.523-1 [12] |
EPRE ratio of PSBCH to PSBCH DMRS |
dB |
0 |
Power of PSBCH within S-SSB S-SSB configured if required by a test case in TS 38.523-1 [12] |
EPRE ratio of PSCCH DMRS to EPRENRSSUERef |
dB |
0 |
|
EPRE ratio of PSCCH to PSCCH DMRS |
dB |
0 |
|
EPRE ratio of PSSCH DMRS to EPRENRSSUERef |
dB |
0 |
|
EPRE ratio of PSSCH to PSSCH DMRS |
dB |
0 |
|
EPRE ratio of PSFCH to PSSCH |
dB |
0 |
|
EPRE ratio of SL CSI-RS to EPRENRSSUERef |
dB |
Test specific (Note 2) |
Power of SL CSI-RS; SL CSI-RS configured if required by a test case in TS 38.523-1 [12] |
EPRE ratio of SL PT-RS to PSSCH |
dB |
0 |
|
Note 1: Power level chosen to align with NR-SS-UE power level as specified in clause 6.2.2. Note 2: Test cases may specify “OFF” in which case the attenuation shall result in an absolute EPRE value being equal or less than the power level specified for a "Off" NR-SS-UE in clause 6.2.2. |
6.2.2 Signal levels
6.2.2.1 Signal Levels for conducted testing
This section applies to the test cases, which use conducted testing for each configured cell or each configured NR-SS-UE.
For NR FR1 cell, the downlink power settings in Table 6.2.2.1-1 and 6.2.2.1-2 are used unless otherwise specified in a test case.
Table 6.2.2.1-1: Default Downlink power levels for FR1 NR cell (5MHz – 25MHz)
SCS(kHz) |
Unit |
Channel bandwidth |
|||||
5MHz |
10MHz |
15MHz |
20MHz |
25MHz |
|||
Channel BW Power |
15 |
dBm |
-63 |
-60 |
-58 |
-57 |
-56 |
30 |
dBm |
-67 |
-63 |
-61 |
-60 |
-59 |
|
60 |
dBm |
N/A |
-67 |
-65 |
-63 |
-62 |
|
SS/PBCH SSS EPRE |
All |
dBm/SCS (Note 3) |
-88 |
-88 |
-88 |
-88 |
-88 |
Note 1: The channel bandwidth powers are informative, based on -88 dBm/ SCS(SubCarrier Spacing) SS/PBCH SSS EPRE, then scaled according to the number of RBs and rounded to the nearest integer dBm value. Full RE allocation with no boost or deboost is assumed. Note 2: The power level is specified at each UE Rx antenna. Note 3: DL level is applied for any of the Subcarrier Spacing configuration () with the same power spectrum density of -88 dBm/SCS(SubCarrier Spacing). |
Table 6.2.2.1-2: Default Downlink power levels for FR1 NR cell (30MHz – 100MHz)
SCS(kHz) |
Unit |
Channel bandwidth |
|||||||
30MHz |
40MHz |
50MHz |
60MHz |
80MHz |
90MHz |
100MHz |
|||
Channel BW Power |
15 |
dBm |
-55 |
-54 |
-53 |
N/A |
N/A |
N/A |
N/A |
30 |
dBm |
-58 |
-57 |
-56 |
-55 |
-54 |
-53 |
-53 |
|
60 |
dBm |
-61 |
-60 |
-59 |
-58 |
-57 |
-56 |
-56 |
|
SS/PBCH SSS EPRE |
All |
dBm/SCS (Note 3) |
-88 |
-88 |
-88 |
-88 |
-88 |
-88 |
-88 |
Note 1: The channel bandwidth powers are informative, based on -88dBm/SCS(SubCarrier Spacing) SS/PBCH SSS EPRE, then scaled according to the number of RBs and rounded to the nearest integer dBm value. Full RE allocation with no boost or deboost is assumed. Note 2: The power level is specified at each UE Rx antenna. Note 3: DL level is applied for any of the Subcarrier Spacing configuration () with a power spectrum density of -88dBm/SCS(SubCarrier Spacing). |
With simultaneous transmission of 24 RBs, a maximum of -78dBm/SCS SS/PBCH SSS EPRE can be allocated as cell power level.
The default settings of suitable cells and non-suitable cells for NR are specified in table 6.2.2.1-3.
Cells which are expected to be undetectable for UE under test shall fulfil the condition of non-suitable "Off" cell in table 6.2.2.1-3.
Table 6.2.2.1-3: Default settings of suitable / non-suitable cells
Power level type |
NR |
E-UTRAN |
UTRAN |
|
Unit |
Power level |
|||
Serving cell |
dBm/SCS |
-88 |
Table 6.2.2.1-1 [2] |
Table 6.1.1 (FDD) [52] |
Suitable neighbour intra-frequency cell |
dBm/SCS |
-94 |
Table 6.2.2.1-1 [2] |
Table 6.1.2 (FDD) [52] |
Suitable neighbour inter-frequency cell |
dBm/SCS |
-99 |
Table 6.2.2.1-1 [2] |
Table 6.1.2 (FDD) [52] |
Non-suitable cell |
dBm/SCS |
-115 |
Table 6.2.2.1-1 [2] |
Table 6.1.3 (FDD) [52] |
Non-suitable "Off" cell |
dBm/SCS |
≤ -145 |
Table 6.2.2.1-1 [2] |
Table 6.1.4 (FDD) [52] |
Note 1: The power level is specified in terms of SS/PBCH SSS EPRE instead of RSRP as RSRP is a measured value and cannot be directly controlled by the Full RE allocation with no boost or deboost is assumed. SS. Note 2: The power level is specified at each UE Rx antenna. Note 3: DL level is applied for any of the Subcarrier Spacing configuration () with the same power spectrum density of -88dBm/SCS. Note 4: The default settings assume that the UE is making relative measurements of neighbour cells compared to the serving cell. |
The default signal level uncertainty is specified in table 6.2.2.1-4 for any level specified, unless a tighter uncertainty is specified by a test case in TS 38.523-1 [12].
Table 6.2.2.1-4: SS signal level uncertainty
Absolute signal level uncertainty for each cell |
Relative signal level uncertainty between multiple cells |
|
Intra-frequency |
+/-3 dB at each test port |
+/-3 dB |
Inter-frequency |
+/-3 dB at each test port |
See Note 1 |
Note 1: For Inter-frequency cells the relative signal level uncertainty between multiple cells is determined by the absolute uncertainty of each cell, and does not have any additional constraint. |
SS/PBCH SSS EPRE setting should be equal to or higher than -115 dBm except for Non-suitable "Off" cell. The figure is chosen to ensure that for all bands the DL signal is within the RSRP measurement range specified in TS 38.133 [13], taking into account the SS default absolute signal level uncertainty.
NOTE: (The power spectral density of a white noise source; specified in TS 38.133 [13]) can be assumed to be -Infinity [dBm/SCS] for all intra and inter frequency test cases. It is applicable to both idle mode and connected mode in TS 38.523-1 [12], unless otherwise specified in specific test cases.
For NR-SS-UE, the sidelink power settings in Table 6.2.2.1-5 is used unless otherwise specified in a test case.
Table 6.2.2.1-5: Default settings of NR-SS-UE power and signal level uncertainty
Power level type |
NR-SS-UE |
Absolute signal level uncertainty for each NR-SS-UE |
|
Unit |
Power level |
||
NR-SS-UE (default value) |
dBm/15kHz |
-85 |
+/-3 dB |
NR-SS-UE ("Off") |
dBm/15kHz |
≤ -145 |
+/-3 dB |
Note 1: The power level is specified at each Rx antenna of the UE under test. |
6.2.2.1.1 Measurement accuracy and side conditions
RSRP measurement accuracy in RRC_CONNECTED state is specified in table 6.2.2.1.1-1, derived from TS 38.133 [13] clauses 10.1.2 and 10.1.4 selecting Normal condition with maximum Io less than -50 dBm/BWChannel. The ranges and side conditions in TS 38.133 [13] clauses 10.1.2 and 10.1.4 apply. This measurement accuracy is applicable to connected mode test cases specified in TS 38.523-1 [12]. For the serving cell and suitable neighbour cells, the following side conditions shall be satisfied including the effect of signal level uncertainty.
– RSRP ≥ -124 dBm
– RSRP Ês/Iot > -6 dB
– Io: 117.5 dBm/SCS for 15kHz SCS and -114.5 dBm/SCS for 15kHz SCS dBm/SCS … -50 dBm/BWChannel (for absolute and relative RSRP measurement accuracy).
RSRP measurement accuracy in RRC_CONNECTED state is specified in table 6.2.2.1.1-1, derived from TS 38.133 [13] clauses 10.1.2 and 10.1.4 selecting Normal condition.
Table 6.2.2.1.1-1: RSRP measurement accuracy in RRC_CONNECTED state
Absolute RSRP measurement accuracy |
Relative RSRP measurement accuracy |
|
Intra-frequency |
+/-8 dB |
+/-3 dB |
Inter-frequency |
+/-8 dB |
+/-4.5 dB |
6.2.2.2 Signal Levels for OTA testing
6.2.2.2.1 General
This section applies to the test cases, which require at least one of the configured cells to be a FR2 NR cell.
The following assumption is made for OTA testing:
– AWGN is not configured in the test case
6.2.2.2.2 Signal Levels for FR2 OTA NR cells
For NR FR2 cell, the downlink power settings in Table 6.2.2.2.2-1 are used unless otherwise specified in a test case.
Table 6.2.2.2.2-1: Default Downlink power levels for FR2 NR cell (50MHz – 400MHz)
SCS(kHz) |
Unit |
Channel bandwidth |
||||
50MHz |
100MHz |
200MHz |
400MHz |
|||
Channel BW Power |
60 |
dBm |
FFS |
FFS |
FFS |
FFS |
120 |
dBm |
-57 |
-57 |
-57 |
-57 |
|
SS/PBCH SSS EPRE |
All |
dBm/SCS |
-82 |
-82 |
-82 |
-82 |
Note 1: The channel bandwidth powers are informative, based on -82 dBm/SCS SS/PBCH SSS EPRE, then scaled according to the number of RBs and rounded to the nearest integer dBm value. A maximumRE allocation of 24 simultaneously transmitted RBs with no boost or deboost is assumed. Note 2: The power level is specified at the centre of quiet zone. |
The default settings of suitable cells and non-suitable cells for NR FR2 are specified in table 6.2.2.2.2-2.
NR FR2 cells which are expected to be undetectable for UE under test shall fulfil the condition of non-suitable "Off" cell in table 6.2.2.2.2-2.
Table 6.2.2.2.2-2: Default settings of suitable / non-suitable FR2 NR cells
Power level type |
NR |
||
Unit |
Power level |
||
Serving cell |
dBm/SCS |
-82 |
|
Suitable neighbour intra-frequency cell |
dBm/SCS |
-91 |
|
Suitable neighbour inter-frequency cell |
dBm/SCS |
-91 |
|
Non-suitable cell |
dBm/SCS |
-100 |
|
Non-suitable "Off" cell |
dBm/SCS |
≤-139 |
|
Note 1: The power level is specified in terms of SS/PBCH SSS EPRE instead of RSRP as RSRP is a measured value and cannot be directly controlled by the SS. Note 2: The power level is specified at the centre of quiet zone. Note 3: DL level is applied for any of the Subcarrier Spacing configuration (µ) with the same power spectrum density in dBm/SCS (SubCarrier Spacing). |
The test system default signal level uncertainty is specified in tables 6.2.2.2.2-3 and 6.2.2.2.2-4 for any level specified, unless a tighter uncertainty is specified by a test case in TS 38.523-1 [12].
Table 6.2.2.2.2-3: SS Absolute FR2 NR signal level uncertainty
Absolute signal level uncertainty |
|
At each frequency |
+/-6 dB at centre of the quiet zone |
Table 6.2.2.2.2-4: SS Relative FR2 NR signal level uncertainty
Relative signal level uncertainty between any two SS EPRE levels at the same frequency |
|
At each frequency |
+/-2.0 dB |
6.2.2.2.3 Signal Levels for FR1 OTA NR cell(s) with FR2 OTA NR cell(s)
For NR cell in FR1 with FR2 NR, since the NR FR1 OTA link is uncalibrated in the signalling test setup, -88dBm/SCS should be applied as defined in the table 6.2.2.1-1 and table 6.2.2.1-2. -88dBm/SCS is suggested value and it is left to the TE vendor to ensure that NR cell power level fulfils the cell selection criteria.
The default settings of suitable cells and non-suitable cells for NR in FR1 with FR2 NR are specified in table 6.2.2.2-7.
NR Cells in FR1 with FR2 NR which are expected to be undetectable for UE under test shall fulfil the condition of non-suitable "Off" cell in table 6.2.2.2.3-1.
Table 6.2.2.2.3-1: Default settings of suitable / non-suitable NR cells in FR1 with NR FR2
Power level type |
NR |
||
Unit |
Power level |
||
Serving cell |
dBm/SCS |
-88 |
|
Non-suitable "Off" cell |
dBm/SCS |
≤-156 |
|
Note 1: The power level is specified in terms of SS/PBCH SSS EPRE instead of RSRP as RSRP is a measured value and cannot be directly controlled by the SS. Note 2: The power level is specified at the centre of quiet zone. |
The following assumptions are considered for the test cases configuring at least one FR1 OTA NR cell:
– Multiple inter-frequency FR1 OTA NR cells can be configured.
– Only two power levels are allowed: Serving cell power level or Non-suitable "Off" cell power level (as defined in Table 6.2.2.2.3-1)
– If FR1 OTA NR cell does not require:
– Cell Reselection measurements and
– Connected Mode measurements and
– Cell Selection between two active cells and
– Multiple Signal Levels
– Multiple FR1 OTA NR cells can be activated.
– Else
– No more than one FR1 OTA NR cell is activated.
6.2.2.2.4 Signal Levels for OTA E-UTRA cell(s) with FR2 OTA NR cell(s)
For E-UTRA cell with FR2 NR, since the LTE OTA link is uncalibrated in the signalling test setup, the table 6.2.2.2.4-1 provides only suggestive value. It is left to the TE vendor to ensure that LTE cell power level fulfils the cell selection criteria.
Table 6.2.2.2.4-1: Default Downlink power levels for E-UTRA cells with NR FR2
Unit |
Channel bandwidth |
||||||
1.4 MHz |
3 MHz |
5 MHz |
10 MHz |
15 MHz |
20 MHz |
||
Number of RBs |
6 |
15 |
25 |
50 |
75 |
100 |
|
Channel BW Power |
dBm |
-77 |
-73 |
-71 |
-68 |
-66 |
-65 |
RS EPRE |
dBm/15kHz |
-96 |
-96 |
-96 |
-96 |
-96 |
-96 |
Note 1: The channel bandwidth powers are informative, based on -96 dBm/15kHz RS_EPRE, then scaled according to the number of RBs and rounded to the nearest integer dBm value. Full RE allocation with no boost or deboost is assumed. Note 2: The power level is specified at the centre of quiet zone. |
The default setting of suitable cells for E-UTRA with FR2 NR are specified in table 6.2.2.2.4-2.
E-UTRA Cells with FR2 NR which are expected to be undetectable for UE under test shall fulfil the condition of non-suitable "Off" cell in table 6.2.2.2.4-2.
Table 6.2.2.2.4-2: Default settings of suitable / non-suitable E-UTRA cells with NR FR2
Power level type |
E-UTRAN |
||
Unit |
Power level |
||
Serving cell |
dBm/15KHz |
-96 |
|
Non-suitable "Off" cell |
dBm/15KHz |
≤-156 |
|
Note 1: The power level is specified in terms ofcell-specific RS EPRE instead of RSRP as RSRP is a measured value and cannot be directly controlled by the SS. Note 2: The power level is specified at the centre of quiet zone. |
The following assumptions are considered for the test cases configuring at least one OTA E-UTRA cell:
– Multiple inter-frequency OTA E-UTRA cells can be configured.
– Only two power levels are allowed: Serving cell power level or Non-suitable "Off" cell power level (as defined in Table 6.2.2.2.4-2)
– If OTA E-UTRA cell does not require:
– Cell Reselection measurements and
– Connected Mode measurements and
– Cell Selection between two active cells and
– Multiple Signal Levels,
– Multiple OTA E-UTRA cells can be activated.
– Else
– No more than one OTA E-UTRA cell is activated.
6.2.2.2.5 Signal Levels for OTA UTRA cell(s) with FR2 OTA NR cell(s)
For UTRA OTA cell with FR2 NR, the UTRA OTA link is uncalibrated in the signalling test setup.
UTRA Cells with FR2 NR which are expected to be undetectable for UE under test shall fulfil the condition of non-suitable "Off" cell in table 6.2.2.2.5-1.
Table 6.2.2.2.5-1: Default settings of suitable / non-suitable UTRA cells with NR FR2
Power level type |
UTRAN |
||
Unit |
Power level |
||
Serving cell |
dBm/3.84 MHz |
-60 |
|
Non-suitable "Off" cell |
dBm/3.84 MHz |
≤-132 |
|
Note 1: The power level is specified in terms of CPICH_Ec instead of CPICH_RSCP as RSCP is a receiver measurement and only CPICH_Ec can be directly controlled by the SS. Note 2: The power level is specified at the centre of quiet zone. |
The following assumptions are considered for the test cases configuring at least one OTA UTRA cell:
– Multiple inter-frequency OTA UTRA cells can be configured.
– Only two power levels are allowed: Serving cell power level or Non-suitable "Off" cell power level (as defined in Table 6.2.2.2.5-1)
– If OTA UTRA cell does not require:
– Cell Reselection measurements and
– Connected Mode measurements and
– Cell Selection between two active cells and
– Multiple Signal Levels,
– Multiple OTA UTRA cells can be activated.
– Else
– No more than one OTA UTRA cell is activated.
6.2.3 Default test frequencies
Editor’s note: For FR2 test frequencies using 100 MHz default channel bandwidth it is FFS if 100MHz channel bandwidth can be used for FR2 multicell protocol testing.
6.2.3.1 Test frequencies for NR standalone signalling testing
The default channel bandwidth for signalling test is specified per NR band. The test frequencies are defined so that no frequency overlapping takes place, in order to avoid unnecessary inter-frequency interference.
For signalling test cases, the mapping of frequency ranges to NR test frequencies are as follows:
– for band with only one test frequency (e.g. n51): Low Range (NRf1);
– for band with up to two test frequencies: Low Range (NRf1) and High Range (NRf2);
– for band with up to three test frequencies: Low Range (NRf1), Mid Range (NRf2) and High Range (NRf3);
– for band with up to four test frequencies: Low Range (NRf1), Mid Low Range (NRf2), Mid High Range (NRf3) and High Range (NRf4);
The signalling test frequencies NRf5, NRf6, NRf7 are mapped respectively as NRf1, NRf2, NRf3 on the operating band for inter-band.
The test frequencies, subcarrier spacing, default channel bandwidth, SS/PBCH block and CORESET#0 parameters for signalling is specified in Table 6.2.3.1-1 (FDD FR1 BW 5MHz), Table 6.2.3.1-2 (FDD FR1 BW 10MHz), Table 6.2.3.1-3 (TDD FR1 BW 5MHz), Table 6.2.3.1-4 (TDD FR1 BW 10MHz), Table 6.2.3.1-4A (TDD FR1 BW 60MHz), Table 6.2.3.1-4B (TDD FR1 BW 20MHz for RedCap UE), Table 6.2.3.1-5 (TDD FR1 BW 100MHz), Table 6.2.3.1-5A (TDD FR1 BW 20MHz for RedCap UE),Table 6.2.3.1-6 (TDD FR2 BW 100MHz) and Table 6.2.3.1-7 (NR FDD FR1 SUL bands).
Table 6.2.3.1-1: Test frequencies for NR FDD FR1 bands using 5 MHz channel bandwidth
NR Band |
SCS [kHz] |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] |
Carrier centre [ARFCN] |
point A [MHz] |
absoluteFrequencyPointA[ARFCN] |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) Note 1 |
offsetToPointA [PRBs] Note 1 |
||
n5 |
15 |
5 |
25 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.15 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||
Mid-Low |
878.2 |
175640 |
873.79 |
174758 |
12 |
15 |
2197 |
175730 |
0 |
1 |
2 (4) |
17 |
|||||
Mid-High |
884.8 |
176960 |
878.23 |
175646 |
24 |
2212 |
176930 |
8 |
1 |
0 (0) |
25 |
||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.5 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||||||
Mid-Low |
833.2 |
166640 |
824.47 |
164894 |
36 |
– |
– |
– |
– |
– |
– |
– |
|||||
Mid-High |
839.8 |
167960 |
817.03 |
163406 |
114 |
– |
– |
– |
– |
– |
– |
– |
|||||
n8 |
15 |
5 |
25 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.8 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||
Mid-Low |
937.5 |
187500 |
933.09 |
186618 |
12 |
15 |
2343 |
187470 |
8 |
1 |
0 (0) |
13 |
|||||
Mid-High |
947.5 |
189500 |
940.93 |
188186 |
24 |
2368 |
189410 |
0 |
0 |
0 (0) |
24 |
||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.8 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||||||
Mid-Low |
892.5 |
178500 |
883.77 |
176754 |
36 |
– |
– |
– |
– |
– |
– |
– |
|||||
Mid-High |
902.5 |
180500 |
879.73 |
175946 |
114 |
– |
– |
– |
– |
– |
– |
– |
|||||
n12 |
15 |
5 |
25 |
Downlink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.12 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||
Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.12 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||||||
n14 |
15 |
5 |
25 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.14 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.14 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||||||
n20 |
15 |
5 |
25 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.20 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||
Mid-Low |
801.8 |
160360 |
797.39 |
159478 |
12 |
15 |
2003 |
160330 |
8 |
1 |
0 (0) |
13 |
|||||
Mid-High |
810.2 |
162040 |
803.63 |
160726 |
24 |
2024 |
162010 |
8 |
1 |
0 (0) |
25 |
||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.20 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||||||
Mid-Low |
842.8 |
168560 |
834.07 |
166814 |
36 |
– |
– |
– |
– |
– |
– |
– |
|||||
Mid-High |
851.2 |
170240 |
828.43 |
165686 |
114 |
– |
– |
– |
– |
– |
– |
– |
|||||
n24 |
15 |
5 |
25 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.24 for DL bandwidth=5 MHz, UL bandwidth=5 MHz and SCS=15 kHz |
|||||||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.24 for DL bandwidth=5 MHz, UL bandwidth=5 MHz and SCS=15 kHz |
|||||||||||||||
n26 |
15 |
5 |
25 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.26 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||
Mid-Low |
871.5 |
174300 |
867.09 |
173418 |
12 |
15 |
2178 |
174270 |
8 |
1 |
0 (0) |
13 |
|||||
Mid-High |
881.5 |
176300 |
874.93 |
174986 |
24 |
2203 |
176210 |
0 |
0 |
0 (0) |
24 |
||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.26 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||||||
Mid-Low |
826.5 |
165300 |
817.77 |
163554 |
36 |
– |
– |
– |
– |
– |
– |
– |
|||||
Mid-High |
836.5 |
167300 |
813.73 |
162746 |
114 |
– |
– |
– |
– |
– |
– |
||||||
n29 |
15 |
5 |
25 |
Downlink (SDL) |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.29 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||
n30 |
15 |
5 |
25 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.30 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.30 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||||||
n70 |
15 |
5 |
25 |
Downlink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.70 for DL bandwidth=5 MHz, UL bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||
Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.70 for DL bandwidth=5 MHz, UL bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||||||
n71 |
15 |
5 |
25 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.71 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||
Mid-Low |
629.5 |
125900 |
625.09 |
125018 |
12 |
15 |
1573 |
125810 |
0 |
0 |
0 (0) |
12 |
|||||
Mid-High |
639.5 |
127900 |
632.93 |
126586 |
24 |
1598 |
127930 |
4 |
1 |
1 (2) |
27 |
||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.71 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||||||
Mid-Low |
675.5 |
135100 |
666.77 |
133354 |
36 |
– |
– |
– |
– |
– |
– |
– |
|||||
Mid-High |
685.5 |
137100 |
662.73 |
132546 |
114 |
– |
– |
– |
– |
– |
– |
– |
|||||
n76 |
15 |
5 |
25 |
Downlink (SDL) |
Low |
Same values as for Low range in clause 4.3.1.1.1.76 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||
Note 1: The CORESET#0 Index and the associated CORESET#0 Offset refers to Table 13-1 in TS 38.213 [22]. The value of CORESET#0 Index is signalled in controlResourceSetZero (pdcch-ConfigSIB1) in the MIB. The offsetToPointA IE is expressed in units of resource blocks assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2. |
Table 6.2.3.1-2: Test frequencies for NR FDD FR1 bands using 10 MHz channel bandwidth
NR Band |
SCS [kHz] |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] |
Carrier centre [ARFCN] |
point A [MHz] |
absoluteFrequencyPointA[ARFCN] |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) Note 1 |
offsetToPointA [PRBs] Note 1 |
|||||
n1 |
15 |
10 |
52 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.1 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||
Mid-Low |
2131.7 |
426340 |
2124.86 |
424972 |
12 |
15 |
5321 |
425770 |
2 |
0 |
0 (0) |
12 |
||||||||
Mid-High |
2148.3 |
429660 |
2139.3 |
427860 |
24 |
5364 |
429150 |
10 |
1 |
0 (0) |
25 |
|||||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.1 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||||||
Mid-Low |
1941.7 |
388340 |
1930.54 |
386108 |
36 |
– |
– |
– |
– |
– |
– |
– |
||||||||
Mid-High |
1958.3 |
391660 |
1933.1 |
386620 |
114 |
– |
– |
– |
– |
– |
– |
– |
||||||||
n2 |
15 |
10 |
52 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.2 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||
Mid-Low |
1951.7 |
390340 |
1944.86 |
388972 |
12 |
15 |
4871 |
389770 |
2 |
0 |
0 (0) |
12 |
||||||||
Mid-High |
1968.3 |
393660 |
1959.3 |
391860 |
24 |
4914 |
393150 |
10 |
1 |
0 (0) |
25 |
|||||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.2 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||||||
Mid-Low |
1871.7 |
374340 |
1860.54 |
372108 |
36 |
– |
– |
– |
– |
– |
– |
– |
||||||||
Mid-High |
1888.3 |
377660 |
1863.1 |
372620 |
114 |
– |
– |
– |
– |
– |
– |
– |
||||||||
n3 |
15 |
10 |
52 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.3 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||
Mid-Low |
1831.7 |
366340 |
1824.86 |
364972 |
12 |
15 |
4571 |
365770 |
2 |
0 |
0 (0) |
12 |
||||||||
Mid-High |
1853.3 |
370660 |
1844.3 |
368860 |
24 |
4625 |
370090 |
2 |
0 |
0 (0) |
24 |
|||||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.3 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||||||
Mid-Low |
1736.7 |
347340 |
1725.54 |
345108 |
36 |
– |
– |
– |
– |
– |
– |
– |
||||||||
Mid-High |
1758.3 |
351660 |
1733.1 |
346620 |
114 |
– |
– |
– |
– |
– |
– |
– |
||||||||
n7 |
15 |
10 |
52 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.7 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||
Mid-Low |
2645 |
529000 |
2638.16 |
527632 |
12 |
15 |
6605 |
528490 |
10 |
1 |
0 (0) |
13 |
||||||||
Mid-High |
2665 |
533000 |
2656 |
531200 |
24 |
6658 |
532610 |
2 |
1 |
2 (4) |
29 |
|||||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.7 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||||||
Mid-Low |
2525 |
505000 |
2513.84 |
502768 |
36 |
– |
– |
– |
– |
– |
– |
– |
||||||||
Mid-High |
2545 |
509000 |
2519.8 |
503960 |
114 |
– |
– |
– |
– |
– |
– |
– |
||||||||
n25 |
15 |
10 |
52 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.25 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||
Mid-Low |
1953.3 |
390660 |
1946.46 |
389292 |
12 |
15 |
4878 |
390270 |
2 |
1 |
2 (4) |
17 |
||||||||
Mid-High |
1971.7 |
394340 |
1962.7 |
392540 |
24 |
4924 |
393890 |
6 |
1 |
1 (2) |
27 |
|||||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.25 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||||||
Mid-Low |
1873.3 |
374660 |
1862.14 |
372428 |
36 |
– |
– |
– |
– |
– |
– |
– |
||||||||
Mid-High |
1891.7 |
378340 |
1866.5 |
373300 |
114 |
– |
– |
– |
– |
– |
– |
– |
||||||||
n28 |
15 |
10 |
52 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.28 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||
Mid-Low |
774.7 |
154940 |
767.86 |
153572 |
12 |
15 |
1930 |
154370 |
2 |
0 |
0 (0) |
12 |
||||||||
Mid-High |
786.3 |
157260 |
777.3 |
155460 |
24 |
1959 |
156750 |
10 |
1 |
0 (0) |
25 |
|||||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.28 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||||||
Mid-Low |
719.7 |
143940 |
708.54 |
141708 |
36 |
– |
– |
– |
– |
– |
– |
– |
||||||||
Mid-High |
731.3 |
146260 |
706.1 |
141220 |
114 |
– |
– |
– |
– |
– |
– |
– |
||||||||
n65 |
15 |
10 |
52 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.65 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||
Mid-Low |
2141.7 |
428340 |
2134.86 |
426972 |
12 |
15 |
5349 |
427950 |
2 |
1 |
2 (4) |
17 |
||||||||
Mid-High |
2168.3 |
433660 |
2159.3 |
431860 |
24 |
5414 |
433210 |
6 |
1 |
1 (2) |
27 |
|||||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.65 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||||||
Mid-Low |
1951.7 |
390340 |
1940.54 |
388108 |
36 |
– |
– |
– |
– |
– |
– |
– |
||||||||
Mid-High |
1978.3 |
395660 |
1953.1 |
390620 |
114 |
– |
– |
– |
– |
– |
– |
– |
||||||||
n66 |
15 |
10 |
52 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.66 for DL bandwidth=10 MHz, UL bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||
Mid-Low |
2141.7 |
428340 |
2134.86 |
426972 |
12 |
15 |
5349 |
427950 |
2 |
1 |
2 (4) |
17 |
||||||||
Mid-High |
2168.3 |
433660 |
2159.3 |
431860 |
24 |
5414 |
433210 |
6 |
1 |
1 (2) |
27 |
|||||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.66 for DL bandwidth=10 MHz, UL bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||||||
Mid-Low |
1741.7 |
348340 |
1730.54 |
346108 |
36 |
– |
– |
– |
– |
– |
– |
– |
||||||||
Mid-High |
1768.3 |
353660 |
1743.1 |
348620 |
114 |
– |
– |
– |
– |
– |
– |
– |
||||||||
n74 |
15 |
10 |
52 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.74 for bandwidth=5 MHz and SCS=15 kHz. |
||||||||||||||
Mid-Low |
1491 |
298200 |
1484.16 |
296832 |
12 |
15 |
3720 |
297630 |
2 |
0 |
0 (0) |
12 |
||||||||
Mid-High |
1502 |
300400 |
1493 |
298600 |
24 |
3749 |
300010 |
2 |
1 |
2 (4) |
29 |
|||||||||
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.74 for bandwidth=5 MHz and SCS=15 kHz. |
||||||||||||||||||
Mid-Low |
1443 |
288600 |
1431.84 |
286368 |
36 |
– |
– |
– |
– |
– |
– |
– |
||||||||
Mid-High |
1454 |
290800 |
1428.8 |
285760 |
114 |
– |
– |
– |
– |
– |
– |
– |
||||||||
n75 |
15 |
10 |
52 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.75 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||
(SDL) |
Mid-Low |
1462 |
292400 |
1455.16 |
291032 |
12 |
15 |
– |
291824 |
31 |
– |
0 |
– |
|||||||
Note 2 |
Mid-High |
1487 |
297400 |
1478 |
295600 |
24 |
– |
296824 |
31 |
– |
0 |
– |
||||||||
Note 1: The CORESET#0 Index and the associated CORESET#0 Offset refers to Table 13-1 in TS 38.213 [22]. The value of CORESET#0 Index is signalled in controlResourceSetZero (pdcch-ConfigSIB1) in the MIB. The offsetToPointA IE is expressed in units of resource blocks assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2. Note 2: FR1 carrier without any coreset is indicated in the MIB by setting =31, controlResourceSetZero=0 and searchSpaceZero = 0 (TS 38.213 [22], clause 13). |
Table 6.2.3.1-3: Test frequencies for NR TDD FR1 bands using 5 MHz channel bandwidth
NR Band |
SCS [kHz] |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] |
Carrier centre [ARFCN] |
point A [MHz] |
absoluteFrequencyPointA[ARFCN] |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) Note 1 |
offsetToPointA [PRBs] Note 1 |
||
n34 |
15 |
5 |
25 |
Downlink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.34 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||
n51 |
15 |
5 |
25 |
Downlink |
Low |
Same values as for Low range in clause 4.3.1.1.1.51 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||
n53 |
15 |
5 |
25 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.53 for bandwidth=5 MHz and SCS=15 kHz. |
|||||||||||
Note 1: For TDD FR1 bands typically the default SCS=30kHz is chosen. For n34 and n53 where SCS=30kHz would limit test coverage to one cell scenarios, SCS=15kHz and 5MHz CBW have been chosen to enable testing of scenarios with up to two cells. |
Table 6.2.3.1-4: Test frequencies for NR TDD FR1 bands using 10 MHz channel bandwidth
NR Band |
SCS [kHz] |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] |
Carrier centre [ARFCN] |
point A [MHz] |
absoluteFrequencyPointA[ARFCN] |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) Note 1 |
offsetToPointA [PRBs] Note 1 |
||
n38 |
30 |
10 |
24 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.38 for bandwidth=10 MHz and SCS=30 kHz. |
|||||||||||
& |
Mid-Low |
2588.3 |
517660 |
2579.66 |
515932 |
12 |
30 |
6470 |
517690 |
10 |
0 |
2 (2) |
28 |
||||
Uplink |
Mid-High |
2601.7 |
520340 |
2588.74 |
517748 |
24 |
6505 |
520370 |
10 |
0 |
2 (2) |
52 |
|||||
n39 |
30 |
10 |
24 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.39 for bandwidth=10 MHz and SCS=30 kHz. |
|||||||||||
& |
Mid-Low |
1895 |
379000 |
1886.36 |
377272 |
12 |
30 |
4736 |
378970 |
14 |
0 |
1 (1) |
26 |
||||
Uplink |
Mid-High |
1905 |
381000 |
1892.04 |
378408 |
24 |
4761 |
380910 |
18 |
0 |
0 (0) |
48 |
|||||
n40 |
30 |
10 |
24 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.40 for bandwidth=10 MHz and SCS=30 kHz. |
|||||||||||
& |
Mid-Low |
2335 |
467000 |
2326.36 |
465272 |
12 |
30 |
5839 |
467090 |
6 |
0 |
3 (3) |
30 |
||||
Uplink |
Mid-High |
2365 |
473000 |
2352.04 |
470408 |
24 |
5914 |
473090 |
6 |
0 |
3 (3) |
54 |
|||||
n48 |
30 |
10 |
24 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.48 for bandwidth=10 MHz and SCS=30 kHz. |
|||||||||||
& |
Mid-Low |
3601.65 |
640110 |
3593.01 |
639534 |
12 |
30 |
7917 |
640128 |
18 |
0 |
2 (2) |
28 |
||||
Uplink |
Mid-High |
3648.33 |
643222 |
3635.37 |
642358 |
24 |
7949 |
643200 |
2 |
0 |
1 (1) |
50 |
|||||
n50 |
30 |
10 |
24 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.50 for bandwidth=10 MHz and SCS=30 kHz. |
|||||||||||
& |
Mid-Low |
1462 |
292400 |
1453.36 |
290672 |
12 |
30 |
3655 |
292370 |
14 |
0 |
1 (1) |
26 |
||||
Uplink |
Mid-High |
1487 |
297400 |
1474.04 |
294808 |
24 |
|
3716 |
297370 |
14 |
0 |
1 (1) |
50 |
||||
Note 1: The CORESET#0 Index and the associated CORESET#0 Offset refers to Table 13-4 in TS 38.213 [22] for all bands in the table. The value of CORESET#0 Index is signalled in controlResourceSetZero (pdcch-ConfigSIB1) in the MIB. The offsetToPointA IE is expressed in units of resource blocks assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2. |
Table 6.2.3.1-4A: Test frequencies for NR TDD FR1 bands using 60 MHz channel bandwidth for non-RedCap UE
NR Band |
SCS [kHz] |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] |
Carrier centre [ARFCN] |
point A [MHz] |
absoluteFrequencyPointA[ARFCN] |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) Note 1 |
offsetToPointA [PRBs] Note 1 |
||
n41 |
30 |
60 |
162 |
Downlink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.41 for bandwidth=60 MHz and SCS=30 kHz. |
Table 6.2.3.1-4B: Test frequencies for NR TDD FR1 bands using 20 MHz channel bandwidth for RedCap UE
NR Band |
SCS [kHz] |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] |
Carrier centre [ARFCN] |
point A [MHz] |
absoluteFrequencyPointA[ARFCN] |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) Note 1 |
offsetToPointA [PRBs] Note 1 |
||
n41 |
30 |
20 |
51 |
Downlink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.41 for bandwidth=20 MHz and SCS=30 kHz. |
Table 6.2.3.1-5: Test frequencies for NR TDD FR1 bands using 100 MHz channel bandwidth for non-RedCap UE
NR Band |
SCS [kHz] |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] |
Carrier centre [ARFCN] |
point A [MHz] |
absoluteFrequencyPointA[ARFCN] |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) Note 1 |
offsetToPointA [PRBs] Note 1 |
||
n77 |
30 |
100 |
273 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.77 for bandwidth=100 MHz and SCS=30 kHz. |
|||||||||||
& |
Mid-Low |
3616.68 |
641112 |
3563.22 |
637548 |
12 |
30 |
7896 |
638112 |
12 |
0 |
1 (1) |
26 |
||||
Uplink |
Mid-High |
3883.32 |
658888 |
3825.54 |
655036 |
24 |
8081 |
655872 |
20 |
0 |
0 (0) |
48 |
|||||
n78 |
30 |
100 |
273 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.78 for bandwidth=100 MHz and SCS=30 kHz. |
|||||||||||
& |
Mid-Low |
3483.33 |
632222 |
3429.87 |
628658 |
12 |
30 |
7804 |
629280 |
22 |
0 |
3 (3) |
30 |
||||
Uplink |
Mid-High |
3616.68 |
641112 |
3558.9 |
637260 |
24 |
7896 |
638112 |
12 |
0 |
1 (1) |
50 |
|||||
n79 |
30 |
100 |
273 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.79 for bandwidth=100 MHz and SCS=30 kHz. |
|||||||||||
& |
Mid-Low |
4616.67 |
707778 |
4563.21 |
704214 |
12 |
30 |
8592 |
704928 |
18 |
6 |
1 (4) |
38 |
||||
Uplink |
Mid-High |
4783.35 |
718890 |
4725.57 |
715038 |
24 |
8720 |
717216 |
18 |
54 |
1 (4) |
160 |
|||||
Note 1: The CORESET#0 Index and the associated CORESET#0 Offset refers to Table 13-4 in TS 38.213 [22] for all bands in the table except for band n79 where Table 13-6 apply. The value of CORESET#0 Index is signalled in controlResourceSetZero (pdcch-ConfigSIB1) in the MIB. The offsetToPointA IE is expressed in units of resource blocks assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2. |
Table 6.2.3.1-5A: Test frequencies for NR TDD FR1 bands using 20 MHz channel bandwidth for RedCap UE
NR Band |
SCS [kHz] |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] |
Carrier centre [ARFCN] |
point A [MHz] |
absoluteFrequencyPointA[ARFCN] |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) Note 1 |
offsetToPointA [PRBs] Note 1 |
||
n77 |
30 |
20 |
51 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.77 for bandwidth=20 MHz and SCS=30 kHz. |
|||||||||||
& |
Mid-Low |
3603.33 |
640222 |
3589.83 |
639322 |
12 |
30 |
7915 |
639936 |
14 |
0 |
3 (3) |
30 |
||||
Uplink |
Mid-High |
3896.67 |
659778 |
3878.85 |
658590 |
24 |
8118 |
659424 |
18 |
0 |
0 (0) |
48 |
|||||
n78 |
30 |
20 |
51 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.78 for bandwidth=20 MHz and SCS=30 kHz. |
|||||||||||
& |
Mid-Low |
3470.01 |
631334 |
3456.51 |
630434 |
12 |
30 |
7822 |
631008 |
22 |
0 |
1 (1) |
26 |
||||
Uplink |
Mid-High |
3630 |
642000 |
3612.18 |
640812 |
24 |
7933 |
641664 |
12 |
0 |
1 (1) |
50 |
|||||
Note 1: The CORESET#0 Index and the associated CORESET#0 Offset refers to Table 13-4 in TS 38.213 [22] for all bands in the table except for band n79 where Table 13-6 apply. The value of CORESET#0 Index is signalled in controlResourceSetZero (pdcch-ConfigSIB1) in the MIB. The offsetToPointA IE is expressed in units of resource blocks assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2. |
Table 6.2.3.1-6: Test frequencies for NR TDD FR2 bands using 100 MHz channel bandwidth
NR Band |
SCS [kHz] |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] |
Carrier centre [ARFCN] |
point A [MHz] |
absoluteFrequencyPointA[ARFCN] |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) Note 1 |
offsetToPointA [PRBs] Note 1 |
||
n257 |
120 |
100 |
66 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.2.1.1 for bandwidth=100 MHz and SCS=120 kHz. |
|||||||||||
& |
Mid-Low |
27516.6 |
2071109 |
27451.8 |
2070029 |
12 |
120 |
22444 |
2070811 |
7 |
6 |
1 (4) |
44 |
||||
Uplink |
Mid-High |
28483.32 |
2087221 |
28401.24 |
2085853 |
24 |
22500 |
2086939 |
3 |
7 |
1 (4) |
70 |
|||||
n258 |
120 |
100 |
66 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.2.1.2 for bandwidth=100 MHz and SCS=120 kHz. |
|||||||||||
& |
Mid-Low |
25350 |
2034999 |
25285.2 |
2033919 |
12 |
120 |
22318 |
2034523 |
2 |
3 |
0 (0) |
30 |
||||
Uplink |
Mid-High |
26400 |
2052499 |
26317.92 |
2051131 |
24 |
22379 |
2052091 |
0 |
2 |
1 (4) |
60 |
|||||
n259 |
120 |
100 |
66 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.2.1.3 for bandwidth=100 MHz and SCS=120 kHz. |
|||||||||||
& |
Mid-Low |
40850.04 |
2293333 |
40785.24 |
2292253 |
12 |
120 |
23215 |
2292859 |
3 |
3 |
0 (0) |
30 |
||||
Uplink |
Mid-High |
42150 |
2314999 |
42067.92 |
2313631 |
24 |
23290 |
2314459 |
6 |
0 |
0 (0) |
48 |
|||||
n260 |
120 |
100 |
66 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.2.1.4 for bandwidth=100 MHz and SCS=120 kHz. |
|||||||||||
& |
Mid-Low |
38016.6 |
2246109 |
37951.8 |
2245029 |
12 |
120 |
23051 |
2245627 |
11 |
2 |
0 (0) |
28 |
||||
Uplink |
Mid-High |
38983.32 |
2262221 |
38901.24 |
2260853 |
24 |
23107 |
2261755 |
7 |
3 |
0 (0) |
54 |
|||||
n261 |
120 |
100 |
66 |
Downlink |
Low, High |
Same values as for Low and High range in clause 4.3.1.2.1.5 for bandwidth=100 MHz and SCS=120 kHz. |
|||||||||||
& |
Mid-Low |
27800.04 |
2075833 |
27735.24 |
2074753 |
12 |
120 |
22460 |
2075419 |
9 |
1 |
1 (4) |
34 |
||||
Uplink |
Mid-High |
28050 |
2079999 |
27967.92 |
2078631 |
24 |
22474 |
2079451 |
2 |
0 |
0 (0) |
48 |
|||||
Note 1: The CORESET#0 Index and the associated CORESET#0 Offset refers to Table 13-8 in TS 38.213 [22]. The value of CORESET#0 Index is signalled in controlResourceSetZero (pdcch-ConfigSIB1) in the MIB. The offsetToPointA IE is expressed in units of resource blocks assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2. |
Table 6.2.3.1-7: Test frequencies for NR FDD FR1 SUL bands
NR Band |
SCS [kHz] |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] |
Carrier centre [ARFCN] |
point A [MHz] |
AbsoluteFrequencyPointA [ARFCN] |
offsetToCarrier [Carrier PRBs] |
|
n80 |
15 |
10 |
52 |
Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in table 4.3.1.1.1.80-1 for bandwidth=10 MHz and SCS=15 kHz. |
||||
n81 |
15 |
10 |
52 |
Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in table 4.3.1.1.1.81-1 for bandwidth=10 MHz and SCS=15 kHz. |
||||
n82 |
15 |
10 |
52 |
Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in table 4.3.1.1.1.82-1 for bandwidth=10 MHz and SCS=15 kHz. |
||||
n83 |
15 |
10 |
52 |
Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in table 4.3.1.1.1.83-1 for bandwidth=10 MHz and SCS=15 kHz. |
||||
n84 |
15 |
10 |
52 |
Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in table 4.3.1.1.1.84-1 for bandwidth=10 MHz and SCS=15 kHz. |
||||
n86 |
15 |
10 |
52 |
Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in table 4.3.1.1.1.86-1 for bandwidth=10 MHz and SCS=15 kHz. |
||||
n97 |
15 |
10 |
52 |
Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in table 4.3.1.1.1.97-1 for bandwidth=10 MHz and SCS=15 kHz. |
||||
n99 |
15 |
10 |
52 |
Uplink |
Low, High |
Same values as for Low and High range in clause 4.3.1.1.1.99-1 for bandwidth=10 MHz and SCS=15 kHz. |
6.2.3.2 Test frequencies for EN-DC band combinations for signalling testing
6.2.3.2.1 General
The default channel bandwidths for EN-DC signalling test are specified per NR and E-UTRA band. The test frequencies are defined so that no frequency overlapping takes place, in order to avoid unnecessary inter-frequency interference.
6.2.3.2.2 E-UTRA 1CC and NR 1CC
For EN-DC Inter-band case with E-UTRA 1CC and NR 1CC (one E-UTRA band and one NR band) the EN-DC configurations are specified in clause 4.3.1.4.1.2 for EN-DC with NR FR1 and 4.3.1.5.1.2 for EN-DC with NR FR2.
The E-UTRA and NR test frequencies are specified in TS 36.508 [2], clause 6.2.3.1 for the E-UTRA band (E-UTRA f1, f2, f3 and f4); and in clause 6.2.3.1 for the NR band (NRf1, NRf2, NRf3, NRf4) and for the secondary NR band (NRf5, NRf6, NRf7) of the secondary EN-DC inter-band configuration.
For EN-DC Intra-band Contiguous case with E-UTRA 1CC and NR 1CC the EN-DC configurations and the test frequencies are specified in Table 6.2.3.2-1.
For EN-DC Intra-band Non-Contiguous with E-UTRA 1CC and NR 1CC case the EN-DC configurations and test frequencies are specified in Table 6.2.3.2-2.
For EN-DC Intra-Band Contiguous and EN-DC Intra-Band Non-Contiguous cases with E-UTRA 1CC and NR 1CC the mapping of frequency ranges to NR test frequencies NRf1, NRf2, NRf3, and NRf4 to PSCell; and to E-UTRA test frequencies f1, f2, f3, and f4 for PCell are as follows:
– for band combinations with only one test frequency: Low Range (NRf1, f1);
– for band combinations with up to two frequencies: Low Range (NRf1, f1), High Range (NRf2, f2);
– for band combinations with up to three frequencies: Mid Range (NRf3, f3), Low Range (NRf1, f1) and High Range (NRf2, f2);
– for band combinations with up to four frequencies: Mid-Low Range (NRf3, f3), High Range (NRf2, f2), Low Range (NRf1, f1) and Mid-High Range (NRf4, f4).
Table 6.2.3.2.2-1: Test frequencies for EN-DC Intra-band Contiguous configurations with E-UTRA 1CC and NR 1CC
EN-DC channel bandwidth combination |
CC |
Bandwidth [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] Note 2 |
Carrier centre [ARFCN] |
point A |
absoluteFrequencyPointA |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
|
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) |
offsetToPointA [PRBs] |
|
DC_(n)41AA |
E-UTRA CC1 |
20 |
100 |
Downlink & Uplink |
Low, High |
Same values as for Low and High range values in Table 4.3.1.4.2.41.1-2 (SCS 30 kHz, 30 kHz NR raster and NR CC at the band edges) and EN-DC channel bandwidth combination “E-UTRA: 20MHz + NR: 60MHz”. |
|||||||||||
NR CC1 |
60 |
162 |
Downlink & Uplink |
Low, High |
|||||||||||||
DC_(n)71AA |
E-UTRA |
5 |
25 |
Downlink |
Low, Mid, High |
Same values as for Low, Mid and High range values in Table 4.3.1.4.2.71.1-1 (SCS 15 kHz, 100 kHz NR raster and NR CC at the band edges) and EN-DC channel bandwidth combination “E-UTRA: 5MHz + NR: 5MHz”. |
|||||||||||
CC1 |
Uplink |
Low, Mid, High |
|||||||||||||||
NR |
5 |
25 |
Downlink |
Low, Mid, High |
|||||||||||||
CC1 |
Uplink |
Low, Mid, High |
Table 6.2.3.2.2-2: Test frequencies for EN-DC Intra-Band Non-Contiguous configurations with E-UTRA 1CC and NR 1CC
EN-DC channel bandwidth combination |
CC |
Bandwidth [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] Note 2 |
Carrier centre [ARFCN] |
point A |
absoluteFrequencyPointA |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
|
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) |
offsetToPointA [PRBs] |
|
DC_41A_n41A |
E-UTRA CC1 |
20 |
100 |
Downlink & Uplink |
Low |
Same values as for Test Frequency ID = ”Low with maxWgap (NR – E-UTRA)” in Table 4.3.1.4.41.1-1 with NR SCS=30 kHz and CBW=60MHz; and E-UTRA CBW=20 MHz. |
|||||||||||
NR CC1 |
60 |
162 |
Downlink & Uplink |
Low |
6.2.3.2.3 E-UTRA 1CC and NR CA 2CC
For EN-DC Inter-band case with E-UTRA 1CC and NR CA 2CC the EN-DC configurations are specified in clauses 4.3.1.4.1.2 (two bands) and 4.3.1.4.1.3 (three bands) for EN-DC and NR CA 2CC with FR1 bands, 4.3.1.5.1.2 (two bands) and 4.3.1.5.1.3 (three bands) for EN-DC with NR CA 2CC with FR2 bands and 4.3.1.6.1.2 for EN-DC and NR CA 2CC´with FR1 and FR2 bands.
For EN-DC Inter-band case (3 bands), the E-UTRA test frequencies are specified in TS 36.508 [2], clause 6.2.3.1 for the E-UTRA band (E-UTRA f1) and the NR test frequencies are specified in clause 6.2.3.1 for the NR band used as PSCell (NRf1, NRf2, NRf3, NRf4) and for the NR band used as SCell (NRf5, NRf6, NRf7).
For EN-DC Inter-band case (2 bands) with NR Intra-band contiguous CA 2CC and NR Intra-band non-contiguous CA 2CC, the E-UTRA test frequencies are specified in TS 36.508 [2], clause 6.2.3.1 for the E-UTRA band (E-UTRA f1) and the NR test frequencies are specified in clause 6.2.3.4 for the NR CA CC1 used as PSCell (NRf1, NRf3) and for the NR CA CC2 used as SCell (NRf2, NRf4,).
For EN-DC Intra-band Contiguous case with E-UTRA 1CC and NR CA 2CC the EN-DC configurations and the test frequencies are specified in Table 6.2.3.2.3-1.
For EN-DC Intra-band Non-Contiguous case with E-UTRA 1CC and NR 2CC the EN-DC configurations and test frequencies are specified in Table 6.2.3.2.3-2.
For EN-DC Intra-Band Contiguous and EN-DC Intra-Band Non-Contiguous cases with E-UTRA 1CC and NR CA 2CC the mapping of frequency ranges to NR test frequencies NRf1 for PSCell (CC1) and NRf2 for SCell (CC2); and to E-UTRA test frequency f1 for PCell is:
– for band combinations with only one test frequency: Low Range (NRf1=CC1, NRf2=CC2, f1); and
– for band combinations with up to two frequencies: Low Range (NRf1=CC1, NRf2=CC2, f1), High Range (NRf3=CC1, NRf4=CC2, f2).
Editor’s note: No EN-DC Intra-band Contiguous configurations with NR CA 2CC have yet been introduced in TS 38.101-3.
Table 6.2.3.2.3-1: Test frequencies for EN-DC Intra-band Contiguous configurations with E-UTRA 1CC and NR CA 2CC
FFS
Editor’s note: No EN-DC Intra-band Non-Contiguous configurations with NR CA 2CC have yet been introduced in TS 38.101-3.
Table 6.2.3.2.3-2: Test frequencies for EN-DC Intra-Band Non-Contiguous configurations with E-UTRA 1CC and NR CA 2CC
FFS
6.2.3.2a Test frequencies for NE-DC band combinations for signalling testing
6.2.3.2a.1 General
The default channel bandwidths for NE-DC signalling test are specified per NR and E-UTRA band. The test frequencies are defined so that no frequency overlapping takes place, in order to avoid unnecessary inter-frequency interference.
6.2.3.2a.2 NR 1CC and E-UTRA 1CC
For NE-DC Inter-band case with NR 1CC and E-UTRA 1CC (one NR band and one E-UTRA band) the NE-DC configurations are specified in clause 4.3.1.4a.1.2 for NE-DC with NR FR1.
The NR and E-UTRA test frequencies are specified in clause 6.2.3.1 for the NR band (NRf1, NRf2, NRf3, NRf4) and for the secondary NR band (NRf5, NRf6, NRf7) of the secondary NE-DC inter-band configuration; and in TS 36.508 [2], clause 6.2.3.1 for the E-UTRA band (E-UTRA f1, f2, f3 and f4).
6.2.3.3 Test frequencies for NR and E-UTRA Inter-RAT signalling testing
For NR and E-UTRA Inter-RAT testing, it is assumed that the NR and E-UTRA bands under test are different in order to avoid unnecessary interferences:
– for NR bands, the frequencies NRf1, NRf2, NRf3 and NRf4 are mapped as per clause 6.2.3.1
– for E-UTRA bands, the signalling test frequencies E-UTRA f1, E-UTRA f2, E-UTRA f3 and E-UTRA f4 are mapped respectively on f1, f2, f3 and f4 as per TS 36.508 [2] clause 6.2.3.1.
6.2.3.4 Test frequencies for NR CA configurations for signalling testing
The default channel bandwidths for NR CA signalling test are specified per NR band. The test frequencies are defined so that no frequency overlapping takes place, in order to avoid unnecessary inter-frequency interference.
For NR CA Inter-band case (2 bands) the NR CA configurations are specified in clause 4.3.1.1.2 for NR CA within FR1, in clause 4.3.1.2.2 for NR CA within FR2 and in clause 4.3.1.3.1 for NR CA between FR1and FR2. NR test frequencies are specified in clause 6.2.3.1 for the NR band used as PCell (NRf1, NRf2, NRf3, NRf4) and for the NR band used as Scell (NRf5, NRf6, NRf7).
For NR CA Intra-band Contiguous case (2 CCs) the NR CA configurations and the test frequencies are specified in Table 6.2.3.4-1 for FR1 and in Table 6.2.3.4-2 for FR2. For NR CA Intra-band Non-Contiguous (2 CCs) case the NR CA configurations and test frequencies are specified in Table 6.2.3.4-3 for FR1 and in Table 6.2.3.4-4 for FR2.
For NR CA Intra-Band Contiguous case (2 CCs) and NR CA Intra-Band Non-Contiguous case (2 CCs) the mapping of frequency ranges to NR test frequencies NRf1, NRf2, NRf3, and NRf4 and PCell (CC1) and SCell (CC2) are as follows:
– for Intra-band configurations with only one test frequency: Low Range (NRf1=CC1 and NRf2=CC2); and
– for Intra-band configurations with up to two frequencies: Low Range (NRf1=CC1 and NRf2=CC2), High Range (NRf3=CC1 and NRf4=CC2)
For NR CA Intra-band Contiguous case (3 CCs) the NR CA configurations and the test frequencies are specified in Table 6.2.3.4-2a for FR2.
For NR CA Intra-Band Contiguous case (3CCs) the mapping of frequency ranges to NR test frequencies NRf1, NRf2, and NRf3 and PCell (CC1) and SCell (CC2, CC3) are as follows:
– For Intra-band configurations with up to three frequencies: Low Range (NRf1=CC1, NRf2=CC2, NRf3=CC3)
Table 6.2.3.4-1: Test frequencies for NR CA Intra-band Contiguous configurations with FR1
NR CA configuration |
CC |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] Note 2 |
Carrier centre [ARFCN] |
point A |
absoluteFrequencyPointA |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
|
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) |
offsetToPointA [PRBs] |
|
CA_n41C |
CC1 |
60 |
162+162 |
Downlink |
Low |
Same values as for Low range in Table 4.3.1.1.3.41.1-1 for CBW combination 60+60 and SCS=30 kHz. |
|||||||||||
CC2 |
60 |
162 |
& Uplink |
||||||||||||||
CA_n48B |
CC1 |
10 |
24 |
Downlink |
Low |
Same values as for Low and High ranges in Table 4.3.1.1.3.48.1-2 for CBW combination 10+10 and SCS=30 kHz. |
|||||||||||
CC2 |
10 |
24 |
& Uplink |
High |
|||||||||||||
CA_n66B |
CC1 |
10 |
52 |
Downlink |
Low |
Same values as for Low and High ranges in Table 4.3.1.1.3.66.1-1 for CBW combination 10+15 and SCS=15 kHz. |
|||||||||||
CC2 |
15 |
79 |
& Uplink |
High |
|||||||||||||
CA_n77C |
CC1 |
100 |
273 |
Downlink |
Low |
Same values as for Low and High ranges in Table 4.3.1.1.3.77.1-1 for CBW combination 100+100 and SCS=30 kHz. |
|||||||||||
CC2 |
100 |
273 |
& Uplink |
High |
|||||||||||||
CA_n78C |
CC1 |
100 |
273 |
Downlink |
Low |
Same values as for Low and High ranges in Table 4.3.1.1.3.78.1-1 for CBW combination 100+100 and SCS=30 kHz. |
|||||||||||
CC2 |
100 |
273 |
& Uplink |
High |
Table 6.2.3.4-2: Test frequencies for NR CA Intra-band Contiguous configurations with FR2
NR CA configuration |
CC |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] Note 2 |
Carrier centre [ARFCN] |
point A |
absoluteFrequencyPointA |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
|
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) |
offsetToPointA [PRBs] |
|
CA_n257G |
CC1, |
100+100 |
66+66 |
Downlink |
Low |
Same values as for Low and High ranges in Table 4.3.1.2.3.1.6-4 for CBW combination 100+100 and SCS=120 kHz. |
|||||||||||
CC2 |
& Uplink |
High |
|||||||||||||||
CA_n258G |
CC1, |
100+100 |
66+66 |
Downlink |
Low |
Same values as for Low and High ranges in Table 4.3.1.2.3.2.6-2 for CBW combination 100+100 and SCS=120 kHz. |
|||||||||||
CC2 |
& Uplink |
High |
|||||||||||||||
CA_n260G |
CC1, |
100+100 |
66+66 |
Downlink |
Low |
Same values as for Low and High ranges in Table 4.3.1.2.3.4.6-2 for CBW combination 100+100 and SCS=120 kHz. |
|||||||||||
CC2 |
& Uplink |
High |
|||||||||||||||
CA_n261G |
CC1, |
100+100 |
66+66 |
Downlink |
Low |
Same values as for Low and High ranges in Table 4.3.1.2.3.5.6-2 for CBW combination 100+100 and SCS=120 kHz. |
|||||||||||
CC2 |
& Uplink |
High |
Table 6.2.3.4-2a: Test frequencies for NR CA Intra-band Contiguous configurations with FR2 (3CC)
NR CA configuration |
CC |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] Note 2 |
Carrier centre [ARFCN] |
point A |
absoluteFrequencyPointA |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
|
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) |
offsetToPointA [PRBs] |
|
CA_n257H |
CC1, CC2,CC3 |
100+100+100 |
66+66+66 |
Downlink & Uplink |
Low |
Same values as for Low range in Table 4.3.1.2.3.1.7-4 for CBW combination 100+100+100 and SCS=120 kHz. |
|||||||||||
CA_n258H |
CC1, CC2,CC3 |
100+100+100 |
66+66+66 |
Downlink & Uplink |
Low |
Same values as for Low range in Table 4.3.1.2.3.2.7-2 for CBW combination 100+100+100 and SCS=120 kHz. |
|||||||||||
CA_n260H |
CC1, CC2,CC3 |
100+100+100 |
66+66+66 |
Downlink & Uplink |
Low |
Same values as for Low range in Table 4.3.1.2.3.4.7-1 for CBW combination 100+100+100 and SCS=120 kHz. |
|||||||||||
CA_n261H |
CC1, CC2,CC3 |
100+100+100 |
66+66+66 |
Downlink & Uplink |
Low |
Same values as for Low range in Table 4.3.1.2.3.5.7-2 for CBW combination 100+100+100 and SCS=120 kHz. |
|||||||||||
Table 6.2.3.4-3: Test frequencies for NR CA Intra-Band Non-Contiguous configurations with FR1
NR CA configuration |
SB |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] Note 2 |
Carrier centre [ARFCN] |
point A |
absoluteFrequencyPointA |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
|
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) |
offsetToPointA [PRBs] |
|
CA_n48(2A) |
SB1 |
10+10 |
24+24 |
Downlink |
Low |
Same values as for Low and High ranges in Table 4.3.1.1.5.48-2 for CBW combination 10+10 and SCS=30 kHz. |
|||||||||||
SB2 |
& Uplink |
High |
|||||||||||||||
CA_n66(2A) |
SB1 |
10+10 |
52+52 |
Downlink |
Low |
Same values as for Low and High ranges in Table 4.3.1.1.5.66-1 for CBW combination 10+10 and SCS=15 kHz. |
|||||||||||
SB2 |
& Uplink |
High |
|||||||||||||||
CA_n71(2A) |
SB1, |
10+10 |
52+52 |
Downlink |
Low |
Same values as for Low and High ranges in Table 4.3.1.1.5.71-1 for CBW combination 10+10 and SCS=15 kHz. |
|||||||||||
SB2 |
& Uplink |
High |
|||||||||||||||
CA_n78(2A) |
SB1 |
50+50 |
133+ |
Downlink |
Low |
Same values as for Low and High ranges in Table 4.3.1.1.5.78-2 for CBW combination 50+50 and SCS=30 kHz. |
|||||||||||
SB2 |
133 |
& Uplink |
High |
Table 6.2.3.4-4: Test frequencies for NR CA Intra-Band Non-Contiguous configurations with FR2
NR CA configuration |
CC |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] Note 2 |
Carrier centre [ARFCN] |
point A |
absoluteFrequencyPointA |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
|
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) |
offsetToPointA [PRBs] |
|
CA_n261(2A) |
CC1 |
100 |
66 |
Downlink |
Low |
Same values as for Low and High ranges in Table 4.3.1.2.4.5.1-1 for CBW combination 100+100 and SCS=120 kHz. |
|||||||||||
CC2 |
100 |
66 |
& Uplink |
High |
6.2.3.5 Test frequencies for MFBI signalling testing
For signalling test cases, the mapping of MFBI frequency ranges to NR test frequencies are as follows: Low Range (NRf1), Mid Range (NRf2) and High Range (NRf3).
The test frequencies, subcarrier spacing, default channel bandwidth, SS/PBCH block and CORESET#0 parameters for signalling are specified in Table 6.2.3.5-1 and Table 6.2.3.5-1A(for RedCap UE).
Table 6.2.3.5-1: Test frequencies for MFBI NR bands in FR1 for non-RedCap UE
NR Band |
MFBI overlapping NR Band |
SCS [kHz] |
Bandwidth [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] |
Carrier centre [ARFCN] |
point A [MHz] |
absoluteFrequencyPointA[ARFCN] |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) |
offsetToPointA [PRBs] |
||
n2 |
n25 |
15 |
10 |
52 |
Downlink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.2 for bandwidth=10 MHz and SCS=15 kHz. |
|||||||||||
Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.2 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||||
n25 |
n2 |
15 |
10 |
52 |
Downlink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.2 for bandwidth=10 MHz and SCS=15 kHz. |
|||||||||||
Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.2 for bandwidth=10 MHz and SCS=15 kHz. |
||||||||||||||||
n38 |
n41 |
15 |
10 |
52 |
Downlink & Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.38 for bandwidth=10 MHz and SCS=15 kHz. |
|||||||||||
n41 |
n38 |
15 |
10 |
52 |
Downlink & Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.38 for bandwidth=10 MHz and SCS=15 kHz. |
|||||||||||
n77 |
n78 |
30 |
100 |
273 |
Downlink & Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.78 for bandwidth=100 MHz and SCS=30 kHz. |
|||||||||||
n78 |
n77 |
30 |
100 |
273 |
Downlink & Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.78 for bandwidth=100 MHz and SCS=30 kHz. |
Table 6.2.3.5-1A: Test frequencies for MFBI NR bands in FR1 for RedCap UE
NR Band |
MFBI overlapping NR Band |
SCS [kHz] |
Bandwidth [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] |
Carrier centre [ARFCN] |
point A [MHz] |
absoluteFrequencyPointA[ARFCN] |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
Offset Carrier CORESET#0 [RBs] |
CORESET#0 Index (Offset [RBs]) |
offsetToPointA [PRBs] |
||
n2 |
n25 |
Same values as in Table 6.2.3.5-1 |
||||||||||||||||
n25 |
n2 |
Same values as in Table 6.2.3.5-1 |
||||||||||||||||
n38 |
n41 |
Same values as in Table 6.2.3.5-1 |
||||||||||||||||
n41 |
n38 |
Same values as in Table 6.2.3.5-1 |
||||||||||||||||
n77 |
n78 |
30 |
20 |
51 |
Downlink & Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.78 for bandwidth=20 MHz and SCS=30 kHz. |
|||||||||||
n78 |
n77 |
30 |
20 |
51 |
Downlink & Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.1.1.78 for bandwidth=20 MHz and SCS=30 kHz. |
Table 6.2.3.5-2: Test frequencies for MFBI NR bands in FR2
NR Band |
MFBI overlapping NR Band |
SCS [kHz] |
Bandwidth [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] |
Carrier centre [ARFCN] |
point A [MHz] |
absoluteFrequencyPointA[ARFCN] |
offsetToCarrier [Carrier PRBs] |
SS block SCS [kHz] |
GSCN |
absoluteFrequencySSB [ARFCN] |
Offset Carrier CORESET#0 [RBs] Note 2 |
CORESET#0 Index (Offset [RBs]) Note 1 |
offsetToPointA [PRBs] Note 1 |
||||||||
n257 |
n258 |
120 |
100 |
66 |
Downlink & Uplink |
Low |
26557.08 |
2055117 |
26509.56 |
2054325 |
0 |
120 |
22388 |
2054683 |
0 |
1 (4) |
1 |
8 |
||||||
Mid |
27006.36 |
2062605 |
26811.96 |
2059365 |
102 |
22414 |
2062171 |
0 |
1 (4) |
1 |
212 |
|||||||||||||
High |
27438.36 |
2069805 |
26665.08 |
2056917 |
504 |
22439 |
2069371 |
0 |
1 (4) |
1 |
1016 |
|||||||||||||
n257 |
n261 |
120 |
100 |
66 |
Downlink & Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.2.1.5 for bandwidth=100 MHz and SCS=120 kHz. |
|||||||||||||||||
n258 |
n257 |
120 |
100 |
66 |
Downlink & Uplink |
Low |
26557.08 |
2055117 |
26509.56 |
2054325 |
0 |
120 |
22388 |
2054683 |
11 |
0 |
1 (4) |
8 |
||||||
Mid |
27006.36 |
2062605 |
26811.96 |
2059365 |
102 |
22414 |
2062171 |
11 |
0 |
1 (4) |
212 |
|||||||||||||
High |
27438.36 |
2069805 |
26665.08 |
2056917 |
504 |
22439 |
2069371 |
11 |
0 |
1 (4) |
1016 |
|||||||||||||
n261 |
n257 |
120 |
100 |
66 |
Downlink & Uplink |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.2.1.5 for bandwidth=100 MHz and SCS=120 kHz. |
|||||||||||||||||
Note 1: The CORESET#0 Index and the associated CORESET#0 Offset refers to Table 13-1 in TS 38.213 [22]. The value of CORESET#0 Index is signalled in controlResourceSetZero (pdcch-ConfigSIB1) in the MIB. The offsetToPointA IE is expressed in units of resource blocks assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2. Note 2: The parameter Offset Carrier CORESET#0 specifies the offset from the lowest subcarrier of the carrier and the lowest subcarrier of CORESET#0. It corresponds to the parameter ΔFOffsetCORESET-0-Carrier in Annex C expressed in number of common RBs. |
6.2.3.6 Test frequencies for NR DC configurations for signalling testing
The default channel bandwidths for NR DC signalling test are specified per NR band. The test frequencies are defined so that no frequency overlapping takes place, in order to avoid unnecessary inter-frequency interference.
For NR DC in FR1 (2 bands, 2CC) the NR DC configurations are specified in clause 4.3.1.1.7.1 for 1CC FR1 and 1CC FR1. NR test frequencies are specified in clause 6.2.3.1 for the NR band used as PCell (NRf1, NRf2, NRf3, NRf4) and for the NR band used as PSCell (NRf5, NRf6, NRf7).
For NR DC between FR1 and FR2 (2 bands, 2CC) the NR DC configurations are specified in clause 4.3.1.3.2.1 for 1CC FR1 and 1CC FR2. NR test frequencies are specified in clause 6.2.3.1 for the NR band used as PCell (NRf1, NRf2, NRf3, NRf4) and for the NR band used as PSCell (NRf5, NRf6, NRf7).
For NR DC between FR1 and FR2 with NR intra-band contiguous CA (2 bands, 3CC) the NR DC configurations are specified in clause 4.3.1.3.2.1 for 1CC FR1 and 2CC FR2. NR test frequencies are specified in clause 6.2.3.1 for the NR FR1 band used as PCell (NRf1) and in Table 6.2.3.4-2 for NR intra-band contiguous CA as PSCell (CC1, NRf5) and SCell (CC2, NRf6).
6.2.3.7 Test frequencies for NR sidelink configurations for signalling testing
The default channel bandwidths for NR sidelink signalling test are specified per NR sidelink operation band. The test frequencies are defined so that no frequency overlapping takes place, in order to avoid unnecessary inter-frequency interference.
For signalling test cases, the mapping of frequency ranges to NR sidelink test frequencies are as follows:
– for band with only one test frequency: Low Range (NRf1);
– for band with up to two test frequencies: Low Range (NRf1) and High Range (NRf2);
– for band with up to three test frequencies: Low Range (NRf1), Mid Range (NRf2) and High Range (NRf3);
The test frequencies, subcarrier spacing, default channel bandwidth and S-SSBparameters for signalling is specified in Table 6.2.3.7-1 for PC5-only operations.
For concurrent operation case the operation configurations are specified in clause 4.3.1.8.2.1 for inter-band concurrent cases. The test frequencies for signalling are specified in Table 6.2.3.7-1 for PC5 carrier and in clause 6.2.3.1 for Uu carrier.
For tests which need NR PC5 carrier and NR Uu carrier but not concurrent operation case, the test frequencies for signalling are specified in Table 6.2.3.7-1 for PC5 carrier in clause 6.2.3.1 for Uu carrier.
Table 6.2.3.7-1: Test frequencies for NR Sidelink operating bands using 10 MHz channel bandwidth
NR Band |
SCS [kHz] |
CBW [MHz] |
carrierBandwidth [PRBs] |
Range |
Carrier centre [MHz] |
Carrier centre [ARFCN] |
point A [MHz] |
sl-absoluteFrequencyPointA |
offsetToCarrier [Carrier PRBs] |
sl-absoluteFrequencySSB [ARFCN] |
n47 |
15 |
10 |
52 |
Low, Mid, High |
Same values as for Low, Mid and High range in clause 4.3.1.8.1.2 for bandwidth=10 MHz and SCS=15 kHz. For sl-absoluteFrequencySSB, same value as for S-SSB Low in clause 4.3.1.8.1.2 for bandwidth=10 MHz and SCS=15 kHz is used. |
6.3 Reference system configurations
6.3.1 Default System Information configurations
6.3.1.1 Intra-frequency neighbouring cell list in SIB3 for NR cells
Intra-frequency neighbouring cell list for signalling test cases is defined in table 6.3.1.1-1. This table is referred to in the default contents of IE intraFreqNeighCellList in SIB3 defined in table 4.6.2-2.
Table 6.3.1.1-1: Intra-frequency neighbouring cell lists for NR cells
cell ID |
Test Frequency |
intra-frequency neighbouring cell list |
|||
number of entries |
physCellId[n] |
||||
1 |
1 |
3 |
|||
NR Cell 1 |
NRf1 |
3 |
NR Cell 2 |
NR Cell 4 |
NR Cell 11 |
NR Cell 2 |
NRf1 |
3 |
NR Cell 1 |
NR Cell 4 |
NR Cell 11 |
NR Cell 4 |
NRf1 |
3 |
NR Cell 1 |
NR Cell 2 |
NR Cell 11 |
NR Cell 11 |
NRf1 |
3 |
NR Cell 1 |
NR Cell 2 |
NR Cell 4 |
NR Cell 3 |
NRf2 |
1 |
NR Cell 23 |
– |
– |
NR Cell 23 |
NRf2 |
1 |
NR Cell 3 |
– |
– |
Editor’s Note: The intra-frequency NR neighbouring cell list for signalling NAS test cases when cells are on same PLMN is FFS.
6.3.1.2 Inter-frequency carrier frequency list in SIB4 for NR cells
Inter-frequency NR carrier frequency list for signalling test cases is defined in table 6.3.1.2-1. This table is referred to in the default contents of IE interFreqCarrierFreqList in SIB4 defined in table 4.6.2-3.
Table 6.3.1.2-1: Inter-frequency carrier frequency lists for NR cells
cell ID |
Test Frequency |
interFreqCarrierFreqList |
|||
number of entries |
dl-CarrierFreq[n] |
||||
1 |
2 |
3 |
|||
NR Cell 1 NR Cell 2 NR Cell 4 NR Cell 11 |
NRf1 (Note 2) |
3 |
NRf2 |
NRf3 |
NRf5 |
NR Cell 3 NR Cell 23 |
NRf2 (Note 2) |
3 |
NRf1 |
NRf3 |
NRf5 |
NR Cell 6 |
NRf3 (Note 2) |
3 |
NRf1 |
NRf2 |
NRf5 |
NR Cell 10 |
NRf5 (Note 3) |
3 |
NRf1 |
NRf2 |
NRf3 |
Note 1: Depending on the Band under test, NRf3 may not be applicable. Note 2: In case of Test frequency NRf1, NRf2 and NRf3, dl-CarrierFreq NRf5 as part of inter-frequency list is applicable only in case of multi-band scenarios. Note 3: Test frequency NRf5 is applicable only in case of multi-band scenarios. |
Editor’s Note: The inter-frequency NR carrier frequency list for signalling NAS test cases when cells are on same PLMN is FFS.
6.3.1.3 E-UTRA carrier frequency list in SIB5 for NR cells
The frequency mapping of E-UTRA cells are defined as per TS 36.508 [2] clause 4.4.2 and TS 36.508 [2] clause 6.3.2 for NGC NAS test cases, E-UTRA frequency mapping is according to clause 6.2.3.3. E-UTRA carrier frequency list for signalling test cases is defined in table 6.3.1.3-1. This table is referred to in the default contents of IE carrierFreqListEUTRA in SIB5 defined in table 4.6.2-4.
Table 6.3.1.3-1: E-UTRA carrier frequency lists for NR cells
interFreqCarrierFreqList |
|
number of entries |
carrierFreq[n] |
1 |
|
1 |
E-UTRA f1 |
2 |
E-UTRA f2 |
3 |
E-UTRA f3 |
4 |
E-UTRA f4 |
Note 1: E-UTRAf1, E-UTRAf2, E-UTRAf3, E-UTRAf4 are according to clause 6.2.3.3 Note 2: Depending on the Band under test, E-UTRA f2 or E-UTRA f3 or E-UTRA f4 may not be applicable. |
Table 6.3.1.3-2: Void
6.3.2 Default configurations for NAS test cases
The default configurations specified in this subclause apply only to NAS test cases. They apply to all NAS test cases unless otherwise specified.
6.3.2.1 Simulated network scenarios for NAS test cases
Simulated network scenarios for NAS test cases to be tested are specified in the pre-test conditions of each individual test case.
Any combination is allowed with the following restrictions:
– a maximum 3 cells on the same frequency can be used, i.e. only 3 cells out of NGC Cell A, NGC Cell B, NGC Cell C and NGC Cell D may be used simultaneously in each individual test case when cells in the test case are in different PLMNs (refer to Table 6.3.2.2-3).
6.3.2.2 Simulated NAS cells
Simulated NAS cells and default NAS parameters are specified in Table 6.3.2.2-1. Unless otherwise specified in a test case, default radio parameters of the NAS cells are specified as per Table 6.3.2.2-2.
Unless otherwise specified, the default parameters specified in clause 4.4.2 will also apply to all NAS cells.
Table 6.3.2.2-1: Default NAS parameters for simulated NAS cells
NAS cell ID |
Tracking Area |
TA# list (Note 1) |
5G-GUTI (Note 2) |
|||||||
TA# |
PLMN |
TAC |
AMF Identifier |
5G-TMSI |
||||||
MCC |
MNC |
AMF Region ID |
AMF Set ID |
AMF Pointer |
||||||
NGC Cell A |
TAI-1 |
(Note 3) |
1 |
TAI-1 |
254 |
1 |
1 |
Arbitrarily selected according to TS 23.003 subclause 2.10.1 [26]. |
||
NGC Cell B |
TAI-2 |
(Note 3) |
2 |
TAI-2 |
254 |
1 |
1 |
|||
NGC Cell C |
TAI-3 |
(Note 3) |
3 |
TAI-3 |
252 |
1 |
1 |
|||
NGC Cell D |
TAI-4 |
(Note 3) |
4 |
TAI-4 |
252 |
1 |
1 |
|||
NGC Cell E |
TAI-12 |
002 |
101 |
3 |
TAI-12 |
244 |
1 |
1 |
||
NGC Cell F |
TAI-11 |
003 |
101 |
2 |
TAI-11 |
239 |
1 |
1 |
||
NGC Cell G |
TAI-7 |
(Note 4) |
02 |
1 |
TAI-7 |
238 |
1 |
1 |
||
NGC Cell H |
TAI-8 |
(Note 4) |
02 |
2 |
TAI-8 |
237 |
1 |
1 |
||
NGC Cell I |
TAI-9 |
002 |
101 |
1 |
TAI-9 |
244 |
1 |
1 |
||
NGC Cell J |
TAI-10 |
003 |
101 |
1 |
TAI-10 |
236 |
1 |
1 |
||
Note 1: The value(s) in the column TA# list indicates TAI(s) included in the response messages of the registration procedure for initial access or mobility (REGISTRATION ACCEPT) when the UE performs the registration procedure on a corresponding cell. Note 2: The value in the column 5G-GUTI indicates GUTI included in the response messages of the registration procedure (REGISTRATION ACCEPT) when the UE performs the registration procedure on a corresponding cell. Note 3: Set to the same Mobile Country Code and Mobile Network Code stored in EFIMSI on the test USIM card (subclause 4.8.3). Note 4: Set to the same Mobile Country Code stored in EFIMSI on the test USIM card (subclause 4.8.3). |
Table 6.3.2.2-2: Default radio parameters for simulated NAS cells when cells are in same PLMN and access stratum is NR
NAS cell ID |
Frequency |
NR cell ID (Note 1) |
NGC Cell A |
NRf1 |
NR Cell 1 |
NGC Cell B |
NRf1 |
NR Cell 2 |
NGC Cell C |
NRf1 |
NR Cell 4 |
NGC Cell D |
NRf1 |
NR Cell 11 |
NGC Cell E |
NA |
NA |
NGC Cell F |
NRf2 |
NR Cell 3 |
NGC Cell G |
NA |
NA |
NGC Cell H |
NA |
NA |
NGC Cell I |
NA |
NA |
NGC Cell J |
NRf2 |
NR Cell 12 |
Note 1: Default NR parameters for simulated NR cells are as specified in Table 4.4.2-2. Note 2: Simultaneous co-existence of active NGC cells defined on the same frequency and same SSB-Index is not recommended (in line with Table 4.4.2-2 Note 3). |
Table 6.3.2.2-3: Default PLMN and radio parameters for simulated NAS cells when cells are in different PLMNs and access stratum is NR
NAS cell ID |
PLMN |
Frequency |
NR cell ID (Note 1) |
NGC Cell A |
MCC/MNC=MCC/MNC in USIM |
NRf1 |
NR Cell 1 |
NGC Cell B |
MCC/MNC=MCC/MNC in USIM |
NRf1 |
NR Cell 2 |
NGC Cell C |
MCC/MNC=MCC/MNC in USIM |
NRf1 |
NR Cell 4 |
NGC Cell D |
MCC/MNC=MCC/MNC in USIM |
NRf1 |
NR Cell 11 |
NGC Cell E |
MCC=002 MNC=101 |
NRf2 |
NR Cell 3 |
NGC Cell F |
MCC=003 MNC=101 |
NRf4 |
NR Cell 14 |
NGC Cell G |
MCC = MCC in USIM MNC=02 |
NRf2 |
NR Cell 12 |
NGC Cell H |
MCC = MCC in USIM MNC=02 |
NRf2 |
NR Cell 23 |
NGC Cell I |
MCC=002 MNC=101 |
NRf3 |
NR Cell 6 |
NGC Cell J |
MCC=002 MNC=101 |
NRf3 |
NR Cell 13 |
Note 1: Default NR parameters for simulated NR cells are as specified in Table 4.4.2-2 Note 2: Simultaneous co-existence of active NGC cells defined on the same frequency and same SSB-Index is not recommended (in line with Table 4.4.2-2 Note 3). |
6.3.3 Cell configuration types
6.3.3.1 Introduction
For the purpose of test equipment resource management, different types of cell configurations are defined with different capabilities.
For E-UTRA cells, please refer to TS 36.508 [2] clauses 6.3.3 and 6.3.4.
The default NR cell configuration type is Full Cell: this NR cell configuration has, in minimum, all DL and UL physical channels and physical signals configured, as defined in subclause 4.2.2.
When not mentioned explicitly in a test case prose, an NR cell is of type Full Cell. The following subclauses define different NR cell types with lower capabilities than the Full Cell.
6.3.3.2 SCell types
When testing NR CA, the following NR SCell types may be specifically mentioned in the test case prose:
– Active SCell: An NR cell that may become an SCell at any point of time during the test case and which, while being an SCell, may be activated.
– Inactive SCell: An NR cell that may become an SCell at any point of time during the test case but is never activated while being an SCell.
SCell activation is defined as SS sending an SCell Activation/Deactivation MAC CE to the UE to activate the SCell.
Note that an Active SCell will not become an Inactive SCell if the SCell is deactivated via an SCell Activation/Deactivation MAC CE or after the sCellDeactivationTimer timer expires.
6.4 Signalling Test Case specific USIM Configurations
6.4.1 General
The default USIM fields are specified in section 4.8.3. Specific USIM fields are set according to the USIM configuration specified in the tables below. PLMN settings are defined in TS 36.523-1 [42] Table 6.0.1-1.
Note: Changes to any existing USIM configuration can be done only if the change WILL NOT HAVE IMPACT on any of the tests which are referring to the configuration! To establish whether this might be the case, the test case author needs to review all tests in all RAN5 test specifications, which refer to the particular USIM configuration e.g. all test cases in TS 38.523-1 [12].
Table 6.4.1-1: USIM Configuration 1
USIM field |
Priority |
Value |
Access Technology Identifier |
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN1. |
||
EFPLMNwAcT |
1 |
Default |
Default |
2 |
PLMN17 |
All specified |
|
3 |
PLMN16 |
NG-RAN |
|
Remaining mandatory entries use default values |
|||
EFOPLMNwACT |
1 |
PLMN15 |
All specified |
Remaining defined entries use default values |
|||
EFHPLMNwAcT |
1 |
PLMN1 |
NG-RAN |
EFUST |
Services 20, 42, 43 and 74 are supported. Service 71 is not supported (there is no EHPLMN list). |
||
EFHPPLMN |
1 (6 minutes) |
Table 6.4.1-2: USIM Configuration 2
USIM field |
Priority |
Value |
Access Technology Identifier |
EF5GS3GPPLOCI |
PLMN4 |
||
EFPLMNwAcT |
Empty |
||
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN1. |
||
EFUST |
Service n°71 and n°74 are "available" |
||
EFEHPLMN |
1 |
PLMN15 |
|
2 |
PLMN1 |
||
EFLRPLMNSI |
01 |
Table 6.4.1-3: USIM Configuration 3
USIM field |
Priority |
Value |
Access Technology Identifier |
EF5GS3GPPLOCI |
PLMN4 |
||
EFPLMNwAcT |
Empty |
||
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN1. |
||
EFUST |
Service n°74 is "available" |
||
EFEHPLMN |
Empty |
||
EFLRPLMNSI |
01 |
Table 6.4.1-4: USIM configuration 4
USIM field |
Priority |
Value |
Access Technology Identifier |
EFEHPLMN |
1 |
PLMN1 |
|
Remaining mandatory entries use default values |
|||
EFPLMNwAcT |
1 |
PLMN2 |
NG-RAN |
Remaining mandatory entries use default values |
|||
EFOPLMNwACT |
1 |
PLMN3 |
NG-RAN |
Remaining mandatory entries use default values |
|||
EFUST |
Services 20, 42 and 71 are supported. |
||
EF5GS3GPPLOCI |
FF FF…FF FE 01 (20 Bytes) |
||
EFEPSLOCI |
FF FF…FF FE 01 (18 Bytes) |
||
EFPSLOCI |
FF FF…FE FF 01 (14 Bytes) |
||
EFLOCI |
FF FF…FE FF 01 (11 Bytes) |
||
Note: LOCI fields of this USIM configuration may get overwritten upon execution of test cases using a UICC loaded with this USIM configuration. The test operator shall ensure that USIM contents are as per this table before each execution of a test case that requires this USIM configuration. |
Table 6.4.1-5: USIM configuration 5
USIM field |
Priority |
Value |
Access Technology Identifier |
EF5GS3GPPLOCI |
PLMN4 (See preamble) |
||
EFPLMNwAcT |
Empty |
||
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN1. |
||
EFUST |
Service 71 is not supported |
||
Service 74 is supported. |
|||
EFLRPLMNSI |
00 |
||
EFEHPLMN |
0xFF..FF |
Table 6.4.1-6: USIM configuration 6
USIM field |
Priority |
Value |
Access Technology Identifier |
EF5GS3GPPLOCI |
PLMN1 (See preamble) |
||
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN3. |
||
EFPLMNwAcT |
1 |
PLMN1 |
NG-RAN |
Remaining mandatory entries use default values |
|||
EFOPLMNwACT |
1 |
PLMN2 |
NG-RAN |
2 |
PLMN4 |
NG-RAN |
|
Remaining defined entries use default values |
|||
EFUST |
Service 71 is not supported |
Table 6.4.1-7: USIM configuration 7
USIM field |
Priority |
Value |
Access technology |
Comment |
E.FPLMNwAcT |
1 |
PLMN13 |
NG-RAN |
|
2 |
PLMN13 |
E-UTRAN |
||
EFOPLMNwAcT |
1 |
PLMN2 |
All |
|
2 |
PLMN14 |
E-UTRAN |
||
3 |
PLMN13 |
NG-RAN |
||
EF5GS3GPPLOCI |
FF FF…FF FE 01 (20 Bytes) |
|||
EFEPSLOCI |
FF FF…FF FE 01 (18 Bytes) |
|||
EFPSLOCI |
FF FF…FE FF 01 (14 Bytes) |
|||
EFLOCI |
FF FF…FE FF 01 (11 Bytes) |
|||
Note: LOCI fields of this USIM configuration may get overwritten upon execution of test cases using a UICC loaded with this USIM configuration. The test operator shall ensure that USIM contents are as per this table before each execution of a test case that requires this USIM configuration. |
Table 6.4.1-8: USIM configuration 8
USIM field |
Priority |
Value |
Access technology |
Comment |
EFOPLMNwAcT |
1 |
PLMN15 |
NG-RAN |
|
2 |
PLMN15 |
E-UTRAN |
||
3 |
PLMN17 |
E-UTRAN |
||
4 |
PLMN16 |
NG-RAN |
||
EF5GS3GPPLOCI |
FF FF…FF FE 01 (20 Bytes) |
|||
EFEPSLOCI |
FF FF…FF FE 01 (18 Bytes) |
|||
EFPSLOCI |
FF FF…FE FF 01 (14 Bytes) |
|||
EFLOCI |
FF FF…FE FF 01 (11 Bytes) |
|||
EFUST |
Service n°127 is not"available" |
|||
Note: LOCI fields of this USIM configuration may get overwritten upon execution of test cases using a UICC loaded with this USIM configuration. The test operator shall ensure that USIM contents are as per this table before each execution of a test case that requires this USIM configuration. |
Table 6.4.1-9: USIM configuration 9
USIM field |
Priority |
Value |
Access technology |
Comment |
EFPLMNwAcT |
1 |
PLMN1 |
NG-RAN |
|
2 |
PLMN15 |
E-UTRAN |
||
EFHPPLMN |
1(=6 min) |
The HPLMN Search Period on the USIM shall be set to 6 minutes. |
Table 6.4.1-10: USIM configuration 10
USIM field |
Priority |
Value |
Access Technology Identifier |
EFOPLMNwACT |
1 |
PLMN14 |
NG-RAN |
2 |
PLMN13 |
NG-RAN |
|
3 |
PLMN2 |
NG-RAN |
|
Remaining defined entries use default values |
|||
EFUST |
Service n°127 is "available" |
||
EFHPPLMN |
1(=6 min) |
||
EF5GS3GPPLOCI |
FF FF…FF FE 01 (20 Bytes) |
||
EFEPSLOCI |
FF FF…FF FE 01 (18 Bytes) |
||
EFPSLOCI |
FF FF…FE FF 01 (14 Bytes) |
||
EFLOCI |
FF FF…FE FF 01 (11 Bytes) |
||
Note: LOCI fields of this USIM configuration may get overwritten upon execution of test cases using a UICC loaded with this USIM configuration. The test operator shall ensure that USIM contents are as per this table before each execution of a test case that requires this USIM configuration. |
Table 6.4.1-11: USIM configuration 11
USIM field |
Priority |
Value |
Access Technology Identifier |
||||
EF5GS3GPPLOCI |
PLMN15 (See preamble) |
||||||
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN1 |
||||||
EFPLMNwAcT |
1 |
Default |
Default |
||||
2 |
PLMN16 |
NG-RAN |
|||||
Remaining defined entries use default values |
Default |
||||||
EFOPLMNwACT |
1 |
PLMN15 |
NG-RAN |
||||
Remaining defined entries use default values |
Default |
||||||
EFHPLMNwAcT |
1 |
PLMN1 |
NG-RAN |
||||
EFUST |
Services 20, 42, 43, 74 and 96 are supported. Service 71 is not supported (there is no EHPLMN list) |
||||||
EFHPPLMN |
1 (6 minutes) |
||||||
EFNASCONFIG |
MinimumPeriodicSearchTimer set to 7 minutes |
Table 6.4.1-12: USIM configuration 12
USIM field |
Priority |
Value |
Access technology |
Comment |
EFPLMNwAcT |
3GPP TS 31.102, Annex E |
The EF is empty. |
||
EFOPLMNwAcT |
1 |
PLMN2 |
NG-RAN |
|
2 |
PLMN13 |
E-UTRAN |
||
3 |
PLMN13 |
NG-RAN |
||
EFUST |
Service n°127 is not"available" |
|||
EF5GS3GPPLOCI |
FF FF…FF FE 01 (20 Bytes) |
|||
EFEPSLOCI |
FF FF…FF FE 01 (18 Bytes) |
|||
EFPSLOCI |
FF FF…FE FF 01 (14 Bytes) |
|||
EFLOCI |
FF FF…FE FF 01 (11 Bytes) |
|||
Note: LOCI fields of this USIM configuration may get overwritten upon execution of test cases using a UICC loaded with this USIM configuration. The test operator shall ensure that USIM contents are as per this table before each execution of a test case that requires this USIM configuration. |
Table 6.4.1-13: USIM configuration 13
USIM field |
Priority |
Value |
Access technology |
Comment |
EFOPLMNwAcT |
1 |
PLMN2 |
NG-RAN |
|
2 |
PLMN2 |
E-UTRAN |
||
3 |
PLMN13 |
NG-RAN |
Table 6.4.1-14: Void
Table 6.4.1-15: USIM Configuration 15
USIM field |
Priority |
Value |
Access Technology Identifier |
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN1. |
||
EFFPLMN |
PLMN2 |
Table 6.4.1-16: Void
Table 6.4.1-17: USIM Configuration 17
USIM field |
Priority |
Value |
Access Technology Identifier |
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN1. |
||
EFPLMNwAcT |
1 |
PLMN1 |
NG-RAN |
EFUST |
Service n°126 is "available". |
||
EFEHPLMN |
PLMN1 |
||
EFUAC_AIC and EFACC |
For Bits b4 and b8 in byte 1 of EFACC (defined in TS 31.102 clause 4.2.15), only single bit is set to 1. Bits b1 and b2 in byte 1 of EFUAC_AIC (defined in TS 31.102 clause 4.4.11.7), and all remaining bits of EFACC and EFUAC_AIC are set to 0. |
Table 6.4.1-18: USIM Configuration 18
USIM field |
Priority |
Value |
Access Technology Identifier |
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN1. |
||
EFPLMNwAcT |
1 |
PLMN2 |
NG-RAN |
EFHPLMNwAcT |
1 |
PLMN1 |
NG-RAN |
EFUST |
Service n°126 (for UAC Access Identities Configuration) defined in TS 31.102 clause 4.2.8 is declared "available" |
||
EFUAC_AIC |
Bit b1 in byte 1 defined in TS 31.102 clause 4.4.11.7 is set to 1 and bit b2 in byte 1 is set to 0. |
Table 6.4.1-19: USIM Configuration 19
USIM field |
Priority |
Value |
Access Technology Identifier |
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN1. |
||
EFPLMNwAcT |
1 |
PLMN2 |
NG-RAN |
EFHPLMNwAcT |
1 |
PLMN1 |
NG-RAN |
EFUST |
Service n°126 (for UAC Access Identities Configuration) defined in TS 31.102 clause 4.2.8 is declared "available" |
||
EFUAC_AIC |
Bit b2 in byte 1 defined in TS 31.102 clause 4.4.11.7 is set to 1 and bit b1 in byte 1 is set to 0. |
Table 6.4.1-20: USIM Configuration 20
USIM field |
Priority |
Value |
Access Technology Identifier |
EFECC |
144, 117 |
Table 6.4.1-21: USIM configuration 21
USIM field |
Priority |
Value |
Access Technology Identifier |
EFOPLMNwACT |
1 |
PLMN14 |
NG-RAN |
2 |
PLMN13 |
NG-RAN |
|
3 |
PLMN2 |
NG-RAN |
|
Remaining defined entries use default values |
|||
EFUST |
Service n°127 is not "available" |
||
EFHPPLMN |
1(=6 min) |
||
EF5GS3GPPLOCI |
FF FF…FF FE 01 (20 Bytes) |
||
EFEPSLOCI |
FF FF…FF FE 01 (18 Bytes) |
||
EFPSLOCI |
FF FF…FE FF 01 (14 Bytes) |
||
EFLOCI |
FF FF…FE FF 01 (11 Bytes) |
||
Note: LOCI fields of this USIM configuration may get overwritten upon execution of test cases using a UICC loaded with this USIM configuration. The test operator shall ensure that USIM contents are as per this table before each execution of a test case that requires this USIM configuration. |
Table 6.4.1-22: USIM Configuration 22
USIM field |
Priority |
Value |
Access Technology Identifier |
EFUST |
Service n°19 and n°51 defined in TS 31.102 clause 4.2.8 is declared "service not available" |
Table 6.4.1-23: USIM Configuration 23
USIM field |
Priority |
Value |
Access Technology Identifier |
EFUST |
Service n°4 Service Dialling Numbers (SDN), Service n°99 URI support by UICC, Service n°89 eCall Data and Service n°112 eCall Data over IMS are available |
||
EFEST |
Services n°1 Fixed Dialling Numbers (FDN) is disabled |
||
EFSDN |
Two entries of SDNs, eCall Test Number (123456) and eCall reconfiguration number (345678) |
||
EFSDNURI |
Two entries of SDNs, eCall Test Number (tel:123456) and eCall reconfiguration number (tel:345678) |
Table 6.4.1-24: USIM Configuration 24
USIM field |
Priority |
Value |
Access Technology Identifier |
EFUST |
Service n°2 Fixed Dialling Numbers (FDN), Service n°99 URI support by UICC, Service n°89 eCall Data and Service n°112 eCall Data over IMS are available |
||
EFEST |
Service n°1 Fixed Dialling Numbers (FDN) is enabled |
||
EFFDN |
Two entries of FDNs, eCall Test Number (123456) and eCall reconfiguration number (345678) |
||
EFFDNURI |
Two entries of FDNs, eCall Test Number (tel:123456) and eCall reconfiguration number (tel:345678) |
Table 6.4.1-25: USIM Configuration 25
USIM field |
Priority |
Value |
Access Technology Identifier |
EFIMSI |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN15. |
Table 6.4.1-26: USIM Configuration 26
USIM field |
Priority |
Value |
Access Technology Identifier |
EFUST |
Service n°2 Fixed Dialling Numbers (FDN), Service n°99 URI support by UICC, Service n°89 eCall Data and Service n°112 eCall Data over IMS are available |
||
EFEST |
Service n°1 Fixed Dialling Numbers (FDN) is enabled |
||
EFFDN |
Two entries of FDNs, eCall Test Number (123456) and eCall reconfiguration number (345678) |
||
EFFDNURI |
Two entries of FDNs, eCall Test Number (tel:123456) and eCall reconfiguration number (tel:345678) |
||
EFFPLMN |
The HPLMN (MCC+MNC) of the IMSI is set to PLMN4. |