I.2 Concrete scenarios

36.521-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA)Part 1: Conformance testingRadio transmission and receptionRelease 17TSUser Equipment (UE) conformance specification

I.2.1 Tests for minimum requirements varying between releases, without introduction of new features

Different minimum requirement between different releases of 3GPP TS 36.101 [2] without introduction of new features represent scenarios according to Annex I.1 bullets 4) a) and b).

In TS 36.521-1 are specified one "original test" and several "additional tests" respectively applicable to the appropriate releases. This is shown graphically in Figure I.2.1-1.

Figure I.2.1-1: Mapping of minimum requirements to conformance tests, when minimum requirements are specified in multiple releases

Rule:

Following tests and clauses are specified in TS 36.521-1:

Original tests:

<x.x.x> <Test>

Additional tests:

<x.x.x>_<y> <Test> (<Release> <UE capability>)

where:

<x.x.x> = number of the original test

<y> = incrementing clause number (Arabic numeral)

<Test> = title of the original test

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

<UE capability> = optional identifier showing the UE capability, which leads to additional test. To be included only when there is already a test with the same title for the same release.

Examples:

1.2.3 Virtual test

1.2.3_1 Virtual test (Rel‑9 and forward)

1.2.3_2 Virtual test (Rel‑10 and forward)

I.2.2 Tests for CA (Carrier aggregation)

I.2.2.1 CA Tx tests (Chapter 6)

CA Transmitter minimum requirements in 3GPP TS 36.101 [2] are already specified in separate clauses from the legacy requirements, bearing the suffix "A" in the number and "for CA" in the title. However minimum requirements have a wide coverage in terms of Annex I.1 bullet 3).

In TS 36.521-1 are specified several separate "individual tests" for different CA scenarios and UE capabilities.

Rule:

Following tests and clauses are specified in TS 36.521-1:

Test group clause:

<x.x.x>A <Test> for CA

Individual tests:

<x.x.x>A.<y> <Test> for CA (<CA type> <DL/UL support> <BW Class> <Release>)

where:

<x.x.x> = number of the corresponding legacy test (if available), or number derived from TS 36.101 without potential suffix "A" (if no legacy test available)

<y> = incrementing clause number (Arabic numeral)

<Test> = title of the corresponding legacy test (if available), or title derived from TS 36.101 without potential suffix "for CA" (if no legacy test available)

<CA type> = mandatory identifier {intra-band contiguous; intra-band non-contiguous; inter-band}

<DL/UL support>= mandatory identifier {DL CA without UL CA; DL CA and UL CA}

<BW Class> = optional identifier showing UE CA Bandwidth class {Class B; Class C; Class D; Class E; Class F}. To be included only for intra-band contiguous scenarios, if there is already a test with the same title.

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3 Virtual test

1.2.3A Virtual test for CA

1.2.3A.1 Virtual test for CA (intra-band contiguous DL CA and UL CA)

1.2.3A.2 Virtual test for CA (inter-band DL CA and UL CA)

1.2.3A.3 Virtual test for CA (intra-band non-contiguous DL CA and UL CA)

1.2.3A.4 Virtual test for CA (3UL CA)

I.2.2.2 CA Rx tests (Chapter 7)

Same as for Transmitter tests (Chapter 6) in Annex I.2.2.1 with following exception:

Examples:

1.2.3 Virtual test

1.2.3A Virtual test for CA

1.2.3A.1 Virtual test for CA (intra-band contiguous DL CA and UL CA)

1.2.3A.2 Virtual test for CA (intra-band contiguous DL CA without UL CA)

1.2.3A.3 Virtual test for CA (inter-band DL CA without UL CA)

1.2.3A.4 Virtual test for CA (intra band non-contiguous DL CA without UL CA)

1.2.3A.5 Virtual test for CA (3DL CA)

1.2.3A.6 Virtual test for CA (inter-band DL CA and UL CA)

1.2.3A.7 Virtual test for CA (4DL CA)

1.2.3A.8 Virtual test for CA (5DL CA)

I.2.2.3 CA Performance tests (Chapter 8)

CA Performance minimum requirements in 3GPP TS 36.101 [2] are specified mostly in the same clause with the legacy requirements, as additional test points marked with CA capability identifiers. CA introduces a new feature in terms of Annex I.1 bullet 4) c). Furthermore the set of CA test points has a wide coverage in terms of Annex I.1 bullet 3).

In TS 36.521-1 are specified several separate "individual tests" for different CA scenarios and UE capabilities.

Rule:

Following tests and clauses are specified in TS 36.521-1:

Test group clause:

<x.x.x>_A <Test> for CA

Individual tests:

<x.x.x>_A.<y> <Test> for CA (<CA type > <DL/UL support> <Release>)

where:

<x.x.x> = number of the corresponding legacy test (if available), or number derived from TS 36.101 without potential suffix "A" (if no legacy test available)

<y> = incrementing clause number (Arabic numeral)

<Test> = title of the corresponding legacy test (if available), or title derived from TS 36.101 without potential "for CA" (if no legacy test available)

<CA type> = mandatory identifier {intra-band contiguous; intra-band non-contiguous; inter-band}

<DL/UL support> = mandatory identifier {DL CA}

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3 Virtual test

1.2.3_A Virtual test for CA

1.2.3_A.1 Virtual test for CA (2DL CA)

1.2.3_A.2 Virtual test for CA (3DL CA)

1.2.3_A.3 Virtual test for CA (4DL CA)

1.2.3_A.4 Virtual test for CA (5DL CA)

I.2.3 Tests for UL-MIMO (Uplink Multiple Antenna Transmission)

I.2.3.1 UL-MIMO Tx tests (Chapter 6)

UL-MIMO Transmitter minimum requirements in 3GPP TS 36.101 [2] are already specified in separate clauses from the legacy requirements, bearing the suffix "B" in the number and "for UL-MIMO" in the title.

Rule:

Following tests and clauses are specified in TS 36.521-1:

Test group clause:

<x.x.x>B <Test> for UL-MIMO

Individual tests:

<x.x.x>B.<y> <Test> for UL-MIMO (<Release>)

where:

<x.x.x> = number of the corresponding legacy test (if available), or number derived from TS 36.101 without potential suffix "B" (if no legacy test available)

<y> = incrementing clause number (Arabic numeral)

<Test> = title of the corresponding legacy test (if available), or title derived from TS 36.101 without potential suffix "for UL-MIMO" (if no legacy test available)

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3 Virtual test

1.2.3B Virtual test for UL-MIMO

I.2.3.2 UL-MIMO Rx tests (Chapter 7)

Same as for Transmitter tests (Chapter 6) in Annex I.2.3.1.

I.2.4 Tests for eDL-MIMO (Enhanced Downlink Multiple Antenna Transmission)

I.2.4.1 eDL MIMO Performance tests (Chapter 8)

eDL MIMO Performance minimum requirements in 3GPP TS 36.101 [2] are specified in separate clauses from the legacy requirements. In some cases the minimum requirements have a wide coverage in terms of Annex I.1 bullet 3) a) with respect of the presence of a simultaneous interfering transmission a) with respect of the presence of a simultaneous interfering transmission.

In TS 36.521-1 are specified several separate "individual tests" for eDL-MIMO.

Rule:

Following tests and clauses are specified in TS 36.521-1:

Test group clause:

<x.x.x>_D <Test> for eDL-MIMO

Individual tests:

<x.x.x>_D.<y> <Test> for eDL-MIMO (<Release>)

where:

<x.x.x> = number of the corresponding legacy test (if available), or number derived from TS 36.101 without potential suffix (if no legacy test available).

<y> =optional incrementing clause number (Arabic numeral) (if many individual tests).

<Test> = title of the corresponding legacy test (if available), or title derived from TS 36.101 without potential suffix potential suffix (if no legacy test available).

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.4 Virtual test

1.2.4_D Virtual test for eDL-MIMO

I.2.4.2 eDL MIMO CSI tests (Chapter 9)

eDL MIMO CSI minimum requirements in 3GPP TS 36.101 [2] are specified in separate clauses from legacy requirements.

Rule:

Following tests and clauses are specified in TS 36.521-1:

Test group clause:

<x.x.x>_D <Test> for eDL-MIMO

Individual tests:

<x.x.x>_D.<y> <Test> for eDL-MIMO (<Release>)

where:

<x.x.x> = number of the corresponding legacy test (if available), or number derived from TS 36.101 without potential suffix (if no legacy test available).

<y> =optional incrementing clause number (Arabic numeral) (if many individual tests).

<Test> = title of the corresponding legacy test (if available), or title derived from TS 36.101 without potential suffix (if no legacy test available).

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.4 Virtual test

1.2.4_D Virtual test for eDL-MIMO

I.2.5 Tests for eICIC (Enhanced Intercarrier Interference Cancellation / Coordination)

I.2.5.1 eICIC Performance tests (Chapter 8)

eICIC Performance minimum requirements in 3GPP TS 36.101 [2] are specified in separate clauses from the legacy requirements. The set of eICIC test points have a wide coverage in terms of Annex I.1 bullet 3)a) with respect of the ABS type (Non-MBSFN / MBSFN). In TS 36.521-1 are specified several separate "individual tests" for eICIC.

Rule:

Following tests and clauses are specified in TS 36.521-1:

Test group clause:

<x.x.x>_C <Test> for eICIC

Individual tests:

<x.x.x>_C.<y> <Test> for eICIC (<ABS-type> <Release>)

where:

<x.x.x> = number of the corresponding legacy test (if available), or number derived from TS 36.101 without potential suffix (if no legacy test available).

<y> =optional incrementing clause number (Arabic numeral) (if many individual tests).

<Test> = title of the corresponding legacy test (if available), or title derived from TS 36.101 without potential suffix (if no legacy test available).

<ABS-Type> = mandatory identifier {non-MBSFN ABS, MBSFN ABS}

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.4 Virtual test

1.2.4_C Virtual test for eICIC

1.2.4_C.1 Virtual test for eICIC (non-MBSFN ABS)

1.2.4_C.2 Virtual test for eICIC (MBSFN ABS)

I.2.5.2 eICIC CSI tests (Chapter 9)

Same as for Performance tests (Chapter 8) in Annex I.2.5.1.

I.2.6 Tests for feICIC (Further Enhanced Non CA-based ICIC for LTE)

I.2.6.1 feICIC Performance tests (Chapter 8)

feICIC Performance minimum requirements in 3GPP TS 36.101 [2] are specified in separate clauses from the legacy requirements. The set of feICIC test points have a wide coverage in terms of Annex I.1 bullet 3)a) with respect of the ABS type (Non-MBSFN / MBSFN). In TS 36.521-1 are specified several separate "individual tests" for feICIC.

Rule:

Following tests and clauses are specified in TS 36.521-1:

Test group clause:

<x.x.x>_E <Test> for feICIC

Individual tests:

<x.x.x>_E.<y> <Test> for feICIC (<ABS-type> <Release>)

where:

<x.x.x> = number of the corresponding legacy test (if available), or number derived from TS 36.101 without potential suffix (if no legacy test available).

<y> =optional incrementing clause number (Arabic numeral) (if many individual tests).

<Test> = title of the corresponding legacy test (if available), or title derived from TS 36.101 without potential suffix (if no legacy test available).

<ABS-Type> = mandatory identifier {non-MBSFN ABS, MBSFN ABS}

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.6 Virtual test

1.2.6_E Virtual test for feICIC

1.2.6_E.1 Virtual test for feICIC (non-MBSFN ABS)

1.2.6_E.2 Virtual test for eICIC (MBSFN ABS)

I.2.6.2 feICIC CSI tests (Chapter 9)

Same as for Performance tests (Chapter 8) in Annex I.2.6.1.

I.2.7 Tests for DL ComP (Downlink Coordinated Multipoint Transmission)

I.2.7.1 CoMP Performance tests (Chapter 8)

CoMP Performance minimum requirements in 3GPP TS 36.101 [2] are specified in separate clauses from the legacy requirements. The set of CoMP test points may have a wide coverage in terms of Annex I.1 bullet 3)a) with respect of the number of CSI processes (Single / Multiple CSI process) etc. In such cases in TS 36.521-1 are specified several separate "individual tests" for CoMP.

Rule:

Following tests and clauses are specified in TS 36.521-1:

Test (group) clause:

<x.x.x>_F <Test> for CoMP

Individual tests:

<x.x.x>_F.<y> <Test> < CSI Process number > for CoMP (<Release>)

where:

<x.x.x> = number derived from TS 36.101.

<y> = optional incrementing clause number (Arabic numeral) (if many individual tests).

<Test> = title derived from TS 36.101.

<CSI Process number> = optional identifier {with Single CSI process, with Multiple CSI processes} (if many individual tests)

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3 Virtual test

1.2.3_F Virtual test for CoMP

1.2.3_F.1 Virtual test with Single CSI process for CoMP

1.2.3_F.2 Virtual test with Multiple CSI processes for CoMP

I.2.7.2 CoMP CSI tests (Chapter 9)

Same as for Performance tests (Chapter 8) in Annex I.2.7.1.

I.2.8 Tests for Further eDL-MIMO (Enhanced Downlink Multiple Antenna Transmission) Enhancement for LTE-A

I.2.8.1 eDL MIMO Enhancement CSI tests (Chapter 9)

Further eDL MIMO Enhancement for LTE-A CSI minimum requirements in 3GPP TS 36.101 [2] are specified in separate clauses from the legacy requirements.

Rule:

Following tests and clauses are specified in TS 36.521-1:

<x.x.x> <Test> for eDL-MIMO Enhancement

Individual tests:

<x.x.x>< _y> <Test> for eDL-MIMO Enhancement (<Release>)

where:

<x.x.x> = number derived from the corresponding requirement clause in TS 36.101.

<_y> = optional incrementing clause number (Arabic numeral) with preceding underscore. To be applied only when there is already a test with the same title for earlier releases.

<Test> = title derived from the corresponding requirement clause in TS 36.101.

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3 Virtual test for eDL-MIMO Enhancement

1.2.3_1 Virtual test for eDL-MIMO Enhancement (Rel-13 and forward)

I.2.9 Tests for UE category 0

I.2.9.1 UE category 0 Tx tests (Chapter 6)

UE category 0 specific Transmitter minimum requirements in 3GPP TS 36.101 [2] are specified in separate clauses from the legacy requirements, bearing the suffix "E" in the number and "for UE category 0" in the title. In other cases where no category 0 specific requirements exist, the legacy requirements apply. To maintain consistency all test cases for UE category 0 to be specified in TS 36.521-1 are handled similarly.

Rule:

Following tests and clauses are specified in TS 36.521-1:

<x.x.x>E <Test> for UE category 0

<x.x.x>E<_y> <Test> for UE category 0 (<Release>)

where:

<x.x.x> = number of the corresponding legacy test (if available), or number derived from TS 36.101 without potential suffix "E" (if no legacy test available)

<_y> = optional incrementing clause number (Arabic numeral) with preceding underscore. To be applied only when there is already a test with the same title for earlier releases.

<Test> = title of the corresponding legacy test (if available), or title derived from TS 36.101 without potential "for UE category 0" (if no legacy test available)

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3 Virtual test

1.2.3E Virtual test for UE category 0

1.2.3E_1 Virtual test for UE category 0 (Rel-13 and forward)

I.2.9.2 UE category 0 Rx tests (Chapter 7)

Same as for Transmitter tests (Chapter 6) in Annex I.2.9.1.

I.2.9.3 UE category 0 Performance tests (Chapter 8)

UE category 0 Performance minimum requirements in 3GPP TS 36.101 [2] are already specified in separate clauses from the legacy requirements.

Rule:

Following tests and clauses are specified in TS 36.521-1:

<x.x.x> <Test> for UE category 0

<x.x.x><_y> <Test> for UE category 0 (<Release>)

where:

<x.x.x> = number derived from the corresponding requirement clause in TS 36.101

<_y> = optional incrementing clause number (Arabic numeral) with preceding underscore. To be applied only when there is already a test with the same title for earlier releases.

<Test> = title derived from the corresponding requirement clause in TS 36.101

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3 Virtual test for UE category 0

1.2.3_1 Virtual test for UE category 0 (Rel-13 and forward)

I.2.9.4 UE category 0 CSI tests (Chapter 9)

Same as for Performance tests (Chapter 8) in Annex I.2.9.3.

I.2.9A Tests for UE category M1

I.2.9A.1 UE category M1 Tx tests (Chapter 6)

UE category M1 specific Transmitter minimum requirements in 3GPP TS 36.101 [2] are specified in separate clauses from the legacy requirements, bearing the suffix "E" in the number and "for UE category M1" in the title. Suffix “E” is also used for UE category 0. In other cases, where no category M1 specific requirements exist, the legacy requirements apply. To maintain consistency all test cases for UE category M1 to be specified in TS 36.521-1 are handled similarly, but suffix "EA" is used to distinguish from UE category 0 test cases using suffix "E".

Rule:

Following tests and clauses are specified in TS 36.521-1:

<x.x.x>EA <Test> for UE category M1

<x.x.x>EA<_y> <Test> for UE category M1 (<CEMode><Release>)

where:

<x.x.x> = number of the corresponding legacy test (if available), or number derived from TS 36.101 without potential suffix "E" (if no legacy test available)

<_y> = optional incrementing clause number (Arabic numeral) with preceding underscore. To be applied only when there is already a test for CEModeA or a test with the same title for earlier releases.

<Test> = title of the corresponding legacy test (if available), or title derived from TS 36.101 without potential "for UE category M1" (if no legacy test available)

<CEMode> = optional identifier showing the CEMode applicability of the test. Can only take value CEModeB and is applied only if a corresponding CEModeA test exists.

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3 Virtual test

1.2.3EA Virtual test for UE category M1

1.2.3EA_1 Virtual test for UE category M1 (Rel-13 and forward)

I.2.9A.2 UE category M1 Rx tests (Chapter 7)

Same as for Transmitter tests (Chapter 6) in Annex I.2.9A.1.

I.2.9A.3 UE category M1 Performance tests (Chapter 8)

UE category M1 Performance minimum requirements in 3GPP TS 36.101 [2] are already specified in separate clauses from the legacy requirements.

Rule:

Following tests and clauses are specified in TS 36.521-1:

<x.x.x> <Test> for UE category M1

<x.x.x><_y> <Test> for UE category M1 (<CEMode><Release>)

where:

<x.x.x> = number derived from the corresponding requirement clause in TS 36.101

<_y> = optional incrementing clause number (Arabic numeral) with preceding underscore. To be applied only when there is already a test for CEModeA or a test with the same title for earlier releases.

<Test> = title derived from the corresponding requirement clause in TS 36.101

<CEMode> = optional identifier showing the CEMode applicability of the test. Can only take value CEModeB and is applied only if a corresponding CEModeA test exists.

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3 Virtual test for UE category M1

1.2.3_1 Virtual test for UE category M1 (Rel-13 and forward)

I.2.9A.4 UE category M1 CSI tests (Chapter 9)

Same as for Performance tests (Chapter 8) in Annex I.2.9A.3.

I.2.9B Tests for UE category M2

I.2.9B.1 UE category M2 Tx tests (Chapter 6)

UE category M2 specific Transmitter minimum requirements in 3GPP TS 36.101 [2] are specified in separate clauses from the legacy requirements and category M1 requirements, bearing the suffix "E" in the number and "for UE category M2" in the title. Suffix “E” is also used for UE category 0. In other cases, where no category M2 specific requirements exist, the legacy requirements apply. To maintain consistency all test cases for UE category M2 to be specified in TS 36.521-1 are handled similarly, but suffix "EC" is used to distinguish from UE category 0 test cases using suffix "E", category M1 test cases using suffix "EA" and category 1bis test cases using suffix “EB”.

Rule:

Following tests and clauses are specified in TS 36.521-1:

<x.x.x>EC <Test> for UE category M2

<x.x.x>EC<_y> <Test> for UE category M2 (<CEMode><Release>)

where:

<x.x.x> = number of the corresponding legacy test (if available), or number derived from TS 36.101 without potential suffix "E" (if no legacy test available)

<_y> = optional incrementing clause number (Arabic numeral) with preceding underscore. To be applied only when there is already a test for CEModeA or a test with the same title for earlier releases.

<Test> = title of the corresponding legacy test (if available), or title derived from TS 36.101 without potential "for UE category M2" (if no legacy test available)

<CEMode> = optional identifier showing the CEMode applicability of the test. Can only take value CEModeB and is applied only if a corresponding CEModeA test exists.

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3 Virtual test

1.2.3EC Virtual test for UE category M2

1.2.3EC_1 Virtual test for UE category M2 (Rel-14 and forward)

I.2.9B.2 UE category M2 Rx tests (Chapter 7)

Same as for Transmitter tests (Chapter 6) in Annex I.2.9B.1.

I.2.9B.3 UE category M2 Performance tests (Chapter 8)

UE category M2 Performance minimum requirements in 3GPP TS 36.101 [2] are already specified in separate clauses from the legacy requirements.

Rule:

Following tests and clauses are specified in TS 36.521-1:

<x.x.x> <Test> for UE category M2

<x.x.x><_y> <Test> for UE category M2 (<CEMode><Release>)

where:

<x.x.x> = number derived from the corresponding requirement clause in TS 36.101

<_y> = optional incrementing clause number (Arabic numeral) with preceding underscore. To be applied only when there is already a test for CEModeA or a test with the same title for earlier releases.

<Test> = title derived from the corresponding requirement clause in TS 36.101

<CEMode> = optional identifier showing the CEMode applicability of the test. Can only take value CEModeB and is applied only if a corresponding CEModeA test exists.

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3 Virtual test for UE category M2

1.2.3_1 Virtual test for UE category M2 (Rel-14 and forward)

I.2.9B.4 UE category M2 CSI tests (Chapter 9)

Same as for Performance tests (Chapter 8) in Annex I.2.9B.3.

I.2.10 Tests for SCE-L1 (Small Cell Enhancements-Physical layer)

I.2.10.1 SCE-L1 Receiver tests (Chapter 7)

The set of 256QAM test points may have a wide coverage in terms of Annex I.1 bullet 3)c) with respect of the different UE capabilities (UE category 11-16), modulation mode and coding rate required and Annex I.1 bullet 4)a)etc with the addition of new requirements and new defined RMC for SCE-L1. In such cases in TS 36.521-1 are specified several separate "individual tests" for SCE-L1.

Rule:

Following tests and clauses are specified in TS 36.521-1:

Test (group) clause:

<x.x.x>_H <Test> for SCE-L1

Individual tests:

<x.x.x>_H.<y> <Test> for SCE-L1 (<Release>)

where:

<x.x.x> = number derived from TS 36.101.

<y> = optional incrementing clause number (Arabic numeral) (if many individual tests).

<Test> = title derived from TS 36.101.

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3 Virtual test

1.2.3_H Virtual test for SCE-L1

I.2.10.2 SCE-L1 Performance tests (Chapter 8)

The set of 256QAM test points may have a wide coverage in terms of Annex I.1 bullet 3)c) with respect of the different UE capabilities (UE category 11-16) and demodulation mode required and Annex I.1 bullet 4)c)etc with the addition of new test points introducing new features of 256QAM for SCE-L1. In such cases in TS 36.521-1 are specified several separate "individual tests" for SCE-L1.

Rule:

Following tests and clauses are specified in TS 36.521-1:

Test (group) clause:

<x.x.x>_H <Test> for SCE-L1

Individual tests:

<x.x.x>_H.<y> <Test> for SCE-L1 (<Release>)

where:

<x.x.x> = number derived from TS 36.101.

<y> = optional incrementing clause number (Arabic numeral) (if many individual tests).

<Test> = title derived from TS 36.101.

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3 Virtual test

1.2.3_H Virtual test for SCE-L1

1.2.3_H.1 Virtual test for SCE-L1(Single Carrier)

1.2.3_H.2 Virtual test for SCE-L1(2DL CA)

1.2.3_H.3 Virtual test for SCE-L1(3DL CA)

I.2.10.3 SCE-L1 CSI tests (Chapter 9)

SCE-L1 Performance minimum requirements in 3GPP TS 36.101 [2] are specified in separate clauses from the legacy requirements. The set of SCE-L1 test points may have a wide coverage in terms of Annex I.1 bullet 3)b) and c) etc. In such cases in TS 36.521-1 are specified several separate "individual tests" for SCE-L1.

Rule:

Following tests and clauses are specified in TS 36.521-1:

Test (group) clause:

<x.x.x>_H <Test> for SCE-L1

Individual tests:

<x.x.x>_H.<y> <Test> for SCE-L1 (<Release>)

where:

<x.x.x> = number derived from TS 36.101.

<y> = optional incrementing clause number (Arabic numeral) (if many individual tests).

<Test> = title derived from TS 36.101.

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3 Virtual test

1.2.3_H Virtual test for SCE-L1

I.2.11 Tests for ProSe

I.2.11.1 ProSe Tx tests (Chapter 6)

ProSe specific Transmitter minimum requirements in 3GPP TS 36.101 [2] are specified in separate clauses from the legacy requirements, bearing the suffix "D" in the number and "for ProSe" in the title. The set of ProSe test points may have a wide coverage in terms of Annex I.1 bullet 3)b) and c) with respect of type of ProSe operation and UE capability (Discovery / Communication) etc. In such cases in TS 36.521-1 are specified several separate "individual tests" for ProSe.

Rule:

Following tests and clauses are specified in TS 36.521-1:

<x.x.x>D <Test> for ProSe

<x.x.x>D<.y><_z> <Test> for ProSe <Mode> (<Release>)

where:

<x.x.x> = number derived from TS 36.101 without suffix "D"

<.y> = incrementing clause number (Arabic numeral).

<_z> = optional incrementing clause number (Arabic numeral) with preceding underscore. To be applied only when there is already a test with the same title for earlier releases.

<Test> = title derived from TS 36.101 without "for ProSe"

<Mode> = mandatory identifier {Direct Discovery; Direct Communication}

<Release> = optional identifier showing the release applicability of the test. To be included only when there is already a test with the same title for earlier releases.

Examples:

1.2.3D Virtual test for ProSe

1.2.3D.1 Virtual test for ProSe Direct Discovery

1.2.3D.2 Virtual test for ProSe Direct Communication

1.2.3D.2_1 Virtual test for ProSe Direct Communication (Release 13 and forward)

I.2.11.2 ProSe Rx tests (Chapter 7)

Same as for Transmitter tests (Chapter 6) in Annex I.2.11.1.

I.2.11.3 ProSe Performance tests (Chapter 8)

ProSe Performance minimum requirements in 3GPP TS 36.101 [2] are already specified in separate clauses from the legacy requirements.

Rule:

Following tests and clauses are specified in TS 36.521-1:

FFS

I.2.11.4 ProSe CSI tests (Chapter 9)

Same as for Performance tests (Chapter 8) in Annex I.2.11.3.

I.2.12 Tests for 4 Rx antenna ports

I.2.12.1 4 Rx antenna ports Rx tests (Chapter 7)

4 Rx antenna ports minimum requirements in 3GPP TS 36.101 [2] are specified in the same clauses as the legacy requirements. The reference sensitivity requirements in section 7.3 are separate from the old test, but the rest of the Receiver tests have the same requirements as the old tests (tested at a level based on REFSENS). But since the test points are different, new variant test cases are still needed.

In TS 36.521-1 separate 2Rx and 4Rx tests are specified for Rel8 and Rel9 tests, but 4Rx is added to the existing tests starting from Rel10 test cases.

Rule:

Following tests and clauses are specified in TS 36.521-1:

Test group before introducing 4Rx:

<x.x.x> <Test> (Rel8 or Rel9)

<y.y.y> <Test> (Rel10 or later)

Test group after introducing 4Rx:

<x.x.x> <Test> for 2Rx

<x.x.x>_1 <Test> for 4Rx

<y.y.y> <Test> for 2Rx and 4Rx

where:

<x.x.x> = number of the corresponding legacy test.

<y> = incrementing clause number (Arabic numeral)

<Test> = title of the corresponding legacy test

(Release) = Release applicability (applicable from), which is not part of the title

Examples:

1.2.3 Virtual test (Rel8)

1.2.3_1 Virtual test with 4 Rx antenna ports (Rel10)

1,2,4 Virtual test (Rel10)

I.2.12.2 4 Rx antenna ports Performance tests (Chapter 8)

4 Rx antenna ports Performance minimum requirements in 3GPP TS 36.101 [2] are specified in separate clauses from the legacy requirements. Separate test cases for 4Rx antenna ports are needed in TS 36.521-1 with test case numbering following TS 36.101[2] numbering,

I.2.12.3 4 Rx antenna ports CSI tests (Chapter 9)

TBD

Annex J (normative):
Modified MPR behaviour

Editor’s note: The modifiedMPRbehavior is given in the Annex H.1 of TS 36.101.