hash
stringlengths
32
32
doc_id
stringlengths
5
12
section
stringlengths
5
1.47k
content
stringlengths
0
6.67M
19eaceb417a28bf040422bcad9ef7619
34.121-1
10.3.2.4.1 Initial conditions
Test environment: normal; see clauses G.2.1 and G.2.2. Frequencies to be tested: mid range; see clause G.2.4. 1) Connect the SS and AWGN noise source and fading simulators to the UE antenna connector as shown in figure Figure A.11. 2) The UL Reference Measurement Channel parameters are defined in Annex C.11. 3) Set the...
19eaceb417a28bf040422bcad9ef7619
34.121-1
10.3.2.4.2 Procedure
NOTE: The measurement principle of the missed hold test (step 3 to 5) is as follows: Upon the UE transmission on E-DPCCH and E-DPDCH, the SS responds as follows: Cell 1 responds "up" on the E-RGCH and a fixed SG on the E-AGCH. Cell 2 responds DTX=hold. The SS reads the transport format, signalled on the E-DPCCH, corres...
19eaceb417a28bf040422bcad9ef7619
34.121-1
10.3.2.5 Test Requirements
For table 10.3.2.5.1, the missed HOLD probability shall be below the specified value in Table 10.3.2.5.2. For table 10.3.2.5.1, the average downlink E-RGCH Ec/Ior power ratio shall be below the specified value for the missed DOWN probabilities in Table 10.3.2.5.3 Table 10.3.2.5.1: Test scenario parameters for E-RGCH – ...
19eaceb417a28bf040422bcad9ef7619
34.121-1
10.4 Demodulation of E-DCH Absolute Grant Channel (E-AGCH)
19eaceb417a28bf040422bcad9ef7619
34.121-1
10.4.1 Single link performance
19eaceb417a28bf040422bcad9ef7619
34.121-1
10.4.1.1 Definition and applicability
The receive characteristics of the E-DCH Absolute Grant Channel (E-AGCH) in multi-path fading environment is determined by the missed detection probability. The requirements and this test apply to Release 6 and later releases for all types of UTRA for the FDD UE that support HSDPA and E-DCH.
19eaceb417a28bf040422bcad9ef7619
34.121-1
10.4.1.2 Minimum requirement
For the parameters specified in Table 10.4.1.1 the average downlink E-AGCH Ec/Ior power ratio shall be below the specified value for the missed detection probability in Table 10.4.1.2. Table 10.4.1.1: Test parameters for E-AGCH detection – single link Parameter Unit Missed detection dBm/3.84 MHz -60 Phase reference - P...
19eaceb417a28bf040422bcad9ef7619
34.121-1
10.4.1.3 Test Purpose
The aim of the test is to verify that the missed detection probability of the E-AGCH channel does not exceed 0.01.
19eaceb417a28bf040422bcad9ef7619
34.121-1
10.4.1.4 Method of test
19eaceb417a28bf040422bcad9ef7619
34.121-1
10.4.1.4.1 Initial conditions
Test environment: normal; see clause G.2.1 and G.2.2. Frequencies to be tested: mid range; see clause G.2.4 1) Connect the SS and AWGN noise source and fading simulator to the UE antenna connector as shown in Figure A.10. 2) The UL Reference Measurement Channel parameters are defined in Annex C.11. 3) Set the test para...
19eaceb417a28bf040422bcad9ef7619
34.121-1
10.4.1.4.2 Procedure
1) The SS shall signal 100% ACK on the E-HICH for all processes. 2) The SS shall signal the Absolute Grants according to the E-AGCH information sequence as defined in Table 10.4.1.3. 3) The SS shall analyse the E-TFCI transmitted on the E-DPCCH for each E-DCH TTI to determine if a missed detection event has occurred by...
19eaceb417a28bf040422bcad9ef7619
34.121-1
10.4.1.5 Test Requirements
The missed detection probability shall not exceed to the values specified in Table 10.4.1.3a. The missed detection probability = the ratio of (missed detection event)/ (all detected E-TFCI event) ≤ 0.01. Tables 10.4.1.3 and 10.4.1.3a define the primary level settings including test tolerance and test parameters for the...
19eaceb417a28bf040422bcad9ef7619
34.121-1
11 Performance requirement (MBMS)
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.1 General
The performance requirements for the UE in this subclause are specified for the propagation conditions specified in Annex D.2 and the Downlink Physical channels specified in Annex E.5B. Unless otherwise stated the receiver characteristics are specified at the antenna connector of the UE. For UEs with more than one rece...
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.2 Demodulation of MTCH
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.2.1 Definition and applicability
The receive characteristic of the MTCH is determined by RLC SDU error rate (RLC SDU ER). RLC SDU ER is specified for each individual data rate of the MTCH. The requirement is valid for all RRC states for which the UE has capabilities for MBMS. The requirements and this test apply to Release 6 and later releases for all...
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.2.2 Minimum requirement
For the parameters specified in Table 11.2.2.1 the average downlink S-CCPCH_Ec /Ior power ratio shall be below the specified value for the RLC SDU ER shown in Table 11.2.2.2. Table 11.2.2.1: Parameters for MTCH detection Parameter Unit Test 1 Test 2 Test 3 Phase reference - P-CPICH dBm/3.84 MHz -60 dB -3 -3 -3 MTCH Dat...
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.2.3 Test Purpose
The aim of the test is to verify that the RLC SDU error rate (RLC SDU ER) for each individual data rate of the MTCH channel does not exceed 0.1. The test shall be performed in CELL_PCH state only.
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.2.4 Method of test
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.2.4.1 Initial conditions
Test environment: normal; see clauses G.2.1 and G.2.2. Frequencies to be tested: mid range; see clause G.2.4. 1) Connect the SS and AWGN noise source and fading simulator to the UE antenna connector as shown in Figure A.23. 2) The DL Reference Measurement Channel parameters are defined in Annex C.12.1. 3) The configura...
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.2.4.2 Procedure
1) Initiate the variables NSS_ACC to 0. 2) SS shall start the test by sending valid MAC headers and RLC SDUs on the MTCH radio bearer for 164 seconds (10 seconds in the second or later iteration) on each Radio Link. The delays of Radio Link 2 and 3 compared with Radio Link 1 are specified in Table 11.2.5.1. SS stores t...
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.2.5 Test Requirements
Table 11.2.5.1: Parameters for MTCH detection Parameter Unit Test 1 Test 2 Test 3 Phase reference - P-CPICH dBm/3.84 MHz -60 Cell1 dB -2.4 -2.4 -2.4 Cell2 dB -2.4 -2.4 -2.4 Cell3 dB -2.4 -2.4 -2.4 MTCH Data Rate 128 kbps 256 kbps 128 kbps Transmission Time Interval ms 40 40 80 Propagation condition VA3 Number of Radio ...
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.3 Demodulation of MTCH and cell identification
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.3.1 Definition and applicability
MBMS combining is not controlled by a network but instead it is autonomously handled by a terminal. UE has to be able to receive MTCH and identify intra-frequency neighbour cells according to the requirements. The receive characteristic of the MTCH combined with cell identification is determined by RLC SDU error rate (...
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.3.2 Minimum requirements
For the parameters specified in Table 11.3.2.1 the average downlink S-CCPCH_Ec/Ior power ratio shall be below the specified value for the RLC SDU error rate shown in Table 11.3.2.2. The cell reselection parameters are given in clause in Table 11.3.2.3. The different cells are assumed to be time aligned. Table 11.3.2.1:...
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.3.3 Test purpose
To verify that the SDU error rate does not exceed the value at the S-CCPCH_Ec/Ior specified in table 11.3.2.2.
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.3.4 Method of test
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.3.4.1 Initial conditions
Test environment: normal; see clauses G.2.1 and G.2.2. Frequencies to be tested: mid range; see clause G.2.4. 1) Connect the SS and AWGN noise source and fading simulators to the UE antenna connector as shown in Figure A.23. 2) The DL Reference Measurement Channel (128kbps 40ms TTI) parameters are defined in Annex C.12...
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.3.4.2 Procedures
1) Initiate the variables NSS to 0. 2) The SS configures and activates cell 1 to 3 with RF parameters according to Stage 1 conditions in Table 11.3.5.1. 3) The SS transmits valid MAC headers and RLC SDUs on the MTCH radio bearer for 2 seconds during Stage 1, 0.8 seconds during Stage 2 and 2 seconds during T3. The SS ch...
19eaceb417a28bf040422bcad9ef7619
34.121-1
11.3.5 Test requirements
The test parameters are specified in table 11.3.5.1. Table 11.3.5.1: Parameters for MTCH demodulation requirements with cell identification Parameter Unit Test 1 Stage 1 Stage 2 Stage 2 Time in each stage S 2 0.8 2 Phase reference - P-CPICH dBm/3.84 MHz -70 -73 -70 Cell1 dB -2.4 0.6 -2.4 Cell2 dB -2.4 0.6 -infinity Cel...
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
1 Scope
The present document specifies the protocol conformance testing for testing a MCData Server for compliance to the Mission Critical Data (MCData) over LTE protocol requirements defined by 3GPP. The present document addresses only MCData Server-Client, and, MCData Server-Server communication scenarios. It does not cover ...
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific. - For a specific reference, subsequent revisions do not apply. - Fo...
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
3 Definitions of terms, symbols and abbreviations
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
3.1 Terms
For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. For the purpose of the present document, the following terms given in TS 23.282 [33] apply: Auto-rec...
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
3.2 Symbols
Void.
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1]. CSK Client-Server Key DS Data Streaming ECGI E-UTRAN Cell Glob...
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
4 General
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
4.1 Test methodology
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
4.1.1 Testing of optional functions and procedures
Any function or procedure which is optional, may be subject to a conformance test if it is implemented in the MCData Server. A declaration by the MCData Server supplier (to use the Implementation Conformance Statement (ICS) proforma specified in TS 36.579-4 [4]) is used to determine whether an optional function/procedu...
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
4.1.2 Test interfaces and facilities
Detailed descriptions of the MCData test interfaces and special facilities for testing are provided in TS 36.509 [19].
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
4.2 Implicit testing
For some 3GPP MCData protocol features conformance is not verified explicitly in the present document. This does not imply that correct functioning of these features is not essential, but that these are implicitly tested to a sufficient degree in tests which are not explicitly dedicated to test the feature.
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
4.3 Repetition of tests
As a general rule, the test cases specified in the present document are highly reproducible and do not need to be repeated unless otherwise stated.
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
4.4 Handling of differences between conformance requirements in different releases of cores specifications
The conformance requirements which determine the scope of each test case are explicitly copy-pasted from relevant core specifications in the especially dedicated for this clause of each test with the title 'Conformance requirements'. NOTE: When in the copy/pasted text there are references to other specifications the re...
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
4.5 Reference conditions
The reference environments used by all signalling and protocol tests is specified in TS 36.579-1 [2]. Where a test requires an environment that is different, this will be specified in the test itself. For all test cases in this document unless specified otherwise the condition MCDATA applies for all message contents.
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
4.6 Generic setup procedures
A set of basic generic procedures for MCData Client-Server communication are described in TS 36.579-1 [2]. These procedures will be used in numerous test cases throughout the present document.
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
5 MCData Client Configuration
Editor’s Note: Intended for MCData server conformance test cases for configuration, authentication, authorization, and registration.
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
6 MCData Server - MCData Client operation
Editor’s Note: Intended for MCData server conformance test cases for communications between the MCData server under test and a client.
d3d27ffa25f98b699e8f75bb3e42d6fe
36.579-9
7 MCData Server - MCData Server operation
Editor’s Note: Intended for MCData server conformance test cases for communications between the MCData server under test and another MCData server. Annex A (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2023-03 RAN5#98 R5-230771 - - - Introduction of TS 36.579-9 0....
13cb58e12ff5ede787a144eecae59b45
36.579-8
1 Scope
The present document specifies the protocol conformance testing for testing a MCVideo Server for compliance to the Mission Critical Video (MCVideo) over LTE protocol requirements defined by 3GPP. The present document addresses only MCVideo Server-Client, and, MCVideo Server-Server communication scenarios. It does not c...
13cb58e12ff5ede787a144eecae59b45
36.579-8
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific. - For a specific reference, subsequent revisions do not apply. - Fo...
13cb58e12ff5ede787a144eecae59b45
36.579-8
3 Definitions of terms, symbols and abbreviations
13cb58e12ff5ede787a144eecae59b45
36.579-8
3.1 Terms
For the purposes of the present document, the terms given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1]. For the purpose of the present document, the following terms and definitions given in TS 24.281 [26]...
13cb58e12ff5ede787a144eecae59b45
36.579-8
3.2 Symbols
Void.
13cb58e12ff5ede787a144eecae59b45
36.579-8
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1]. ECGI E-UTRAN Cell Global Identification FFS For Further Study ICS Implem...
13cb58e12ff5ede787a144eecae59b45
36.579-8
4 General
13cb58e12ff5ede787a144eecae59b45
36.579-8
4.1 Test methodology
13cb58e12ff5ede787a144eecae59b45
36.579-8
4.1.1 Testing of optional functions and procedures
Any function or procedure which is optional, may be subject to a conformance test if it is implemented in the MCVideo Server. A declaration by the MCVideo Server supplier (to use the Implementation Conformance Statement (ICS) proforma specified in TS 36.579-4 [4]) is used to determine whether an optional function/proce...
13cb58e12ff5ede787a144eecae59b45
36.579-8
4.1.2 Test interfaces and facilities
Detailed descriptions of the MCVideo test interfaces and special facilities for testing are provided in TS 36.509 [19].
13cb58e12ff5ede787a144eecae59b45
36.579-8
4.2 Implicit testing
For some 3GPP MCVideo protocol features conformance is not verified explicitly in the present document. This does not imply that correct functioning of these features is not essential, but that these are implicitly tested to a sufficient degree in tests which are not explicitly dedicated to test the feature.
13cb58e12ff5ede787a144eecae59b45
36.579-8
4.3 Repetition of tests
As a general rule, the test cases specified in the present document are highly reproducible and do not need to be repeated unless otherwise stated.
13cb58e12ff5ede787a144eecae59b45
36.579-8
4.4 Handling of differences between conformance requirements in different releases of cores specifications
The conformance requirements which determine the scope of each test case are explicitly copy-pasted from relevant core specifications in the especially dedicated for this clause of each test with the title 'Conformance requirements'. NOTE: When in the copy/pasted text there are references to other specifications the re...
13cb58e12ff5ede787a144eecae59b45
36.579-8
4.5 Reference conditions
The reference environments used by all signalling and protocol tests is specified in TS 36.579-1 [2]. Where a test requires an environment that is different, this will be specified in the test itself. For all test cases in this document unless specified otherwise the condition MCVIDEO applies for all message contents.
13cb58e12ff5ede787a144eecae59b45
36.579-8
4.6 Generic setup procedures
A set of basic generic procedures for MCVideo Client-Server communication are described in TS 36.579-1 [2]. These procedures will be used in numerous test cases throughout the present document.
13cb58e12ff5ede787a144eecae59b45
36.579-8
5 MCVideo Client Configuration
Editor’s Note: Intended for MCVideo server conformance test cases for configuration, authentication, authorization, and registration.
13cb58e12ff5ede787a144eecae59b45
36.579-8
6 MCVideo Server - MCVideo Client operation
Editor’s Note: Intended for MCVideo server conformance test cases for communications between the MCVideo server under test and a client.
13cb58e12ff5ede787a144eecae59b45
36.579-8
7 MCVideo Server - MCVideo Server operation
Editor’s Note: Intended for MCVideo server conformance test cases for communications between the MCVideo server under test and another MCVideo server. Annex A (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2023-03 RAN5#98 R5-230770 - - - Introduction of TS 36.579-8...
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
1 Scope
The present document is a technical report for Dual Connectivity (EN-DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) under Rel-16 time frame. The purpose is to gather the relevant background information and studies in order to address Dual Connectivity (EN-DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL)for the ...
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific. - For a specific reference, subsequent revisions do not apply. - Fo...
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
3 Definitions, symbols and abbreviations
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
3.1 Definitions
For the purposes of the present document, the terms and definitions given in TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 [1].
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
3.2 Symbols
For the purposes of the present document, the following symbols apply: <symbol> <Explanation>
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
3.3 Abbreviations
For the purposes of the present document, the abbreviations given in TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 [1].
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
4 Background
The present document is a technical report for Dual Connectivity (EN-DC) of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL) under Rel-16 time frame. It covers both the UE and BS side. The document is divided in two different parts: - General part: this part covers BS and UE specific which is band combination independent....
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
4.1 TR Maintenance
A single company is responsible for introducing all approved TPs in the current TR, i.e. TR editor. However, it is the responsibility of the contact person of each band combination to ensure that the TPs related to the band combination have been implemented.
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
5 EN-DC of 1 LTE band (1DL/1UL) and 1 NR band (1DL/1UL): General Part
5.1 Maximum Sensitivity Degradation (MSD) analysis 5.1.1 Inter-band EN-DC within FR1 For each inter-band DC band combination, sensitivity degradation is allowed for a band if it is impacted by UL harmonic interference, harmonic mixing, close proximity of bands, cross band isolation, and intermodulation interference fr...
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6 EN-DC of 1 LTE band (1DL/1UL) and 1 NR band: Specific Band Combination Part
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1 Inter-band EN-DC within FR1
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.1 DC_5_n79
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.1.1 Operating bands for DC
Table 6.1.1..1-1: DC band combination of 1 LTE band + 1 NR band EN-DC band E-UTRA Band NR Band Single UL allowed DC_5_n79 5 n79 No
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.1.2 Configuration for DC
Table 6.1.2.2-1: Inter-band EN-DC configurations of 1 LTE band + 1 NR band EN-DC configuration Uplink EN-DC configuration (NOTE 1) E-UTRA configuration NR configuration DC_5A_n79A DC_5A_n79A 5A n79A
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.1.3 Maximum output power for DC
Table 6.1.1.3-1: Maximum output power for inter-band EN-DC of 1 LTE band + 1 NR band DC configuration Power class 3 (dBm) Tolerance (dB) DC_5A_n79A 23 +2/-3
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.1.4 Spurious emission band UE co-existence for DC
Table 6.1.1.4-1: Spurious emissions for inter-band EN-DC of 1 LTE band + 1 NR band E-UTRA and NR DC Configuration Spurious emission Protected band Frequency range (MHz) Maximum Level (dBm) MBW (MHz) NOTE DC_5A_n79A Bands 1, 2, 3, 4, 5, 7, 8, 10, 12, 13, 14, 17, 24, 25, 28, 29, 30, 31, 34, 38, 40, 42, 43, 45, 48, 50, 51...
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.1.5 MSD analysis for DC
For 2UL/2DL UE coexistence study 2nd, 3rd, 4th and 5th order harmonics and 2nd, 3rd, 4th and 5th order intermodulation products were calculated and presented in Table 6.1.1.5-1 Table 6.1.1.5-1: Harmonic and IMD analysis UE UL carriers fx_low fx_high fy_low fy_high UL frequency (MHz) 824 849 4400 5000 2nd harmonics freq...
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.2 DC_3_n41
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.2.1 Operating bands for DC
Table 6.1.2.1-1: Band combinations for EN-DC (two bands) EN-DC band E-UTRA Band NR Band Single UL allowed DC_3_n41 3 n41 No
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.2.2 Configuration for DC
Table 6.1.2.2-1: Inter-band EN-DC configurations (two bands) EN-DC configuration Uplink EN-DC configuration E-UTRA configuration NR configuration DC_3A_n41A DC_3A_n41A 3A n41A
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.2.3 Maximum output power for DC
Table 6.1.2.3-1: Maximum output power for inter-band EN-DC (two bands) DC configuration Power class 3 (dBm) Tolerance (dB) DC_3A_n41A 23 +/-2
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.2.4 Spurious emission band UE co-existence for DC
Interference analysis for DC_3A_n41A is shown in Table 6.1.2.4-1. Table 6.1.2.4-1: Harmonics and IMD products for DC_3A_n41A UE UL carriers fx_low fx_high fy_low fy_high 2nd harmonics frequency limits 2*fx_low 2*fx_high 2* fy_low 2* fy_high 3420 3570 4992 5380 3rd harmonics frequency limits 3*fx_low 3*fx_high 3* fy_low...
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.2.5 MSD for DC
Reference sensitivity exceptions due to cross band isolation are specified for DC_3A_n41A in Table 6.1.2.5-1 with uplink configuration specified in Table 6.1.2.5-2. Table 6.1.2.5-1: Reference sensitivity exceptions due to cross band isolation EN-DC configuration UL band DL band MSD 5 MHz (dB) 10 MHz (dB) 15 MHz (dB) 20...
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.3 DC_3_n1, DC_3-3_n1
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.3.1 Operating bands for DC
Table 6.1.3.1-1: DC band combination of 1 LTE band + 1 NR band EN-DC band E-UTRA Band NR Band Single UL allowed DC_3_n1 3 n1 Yes DC_3-3_n1 CA_3-3 n1 Yes
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.3.2 Configuration for DC
Table 6.1.3.2-1: Inter-band EN-DC configurations of 1 LTE band + 1 NR band EN-DC configuration Uplink EN-DC configuration (NOTE 1) E-UTRA configuration NR configuration DC_3A_n1A DC_3A_n1A 3A n1A DC_3C_n1A DC_3A_n1A DC_3C_n1A 3C n1A DC_3A-3A_n1A DC_3A_n1A CA_3A-3A n1A
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.3.3 Maximum output power for DC
Table 6.1.3.3-1: Maximum output power for inter-band EN-DC of 1 LTE band + 1 NR band DC configuration Power class 3 (dBm) Tolerance (dB) DC_3A_n1A DC_3C_n1A 23 +2/-3
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.3.4 Spurious emission band UE co-existence for DC
Table 6.1.3.4-1: Spurious emissions for inter-band EN-DC of 1 LTE band + 1 NR band E-UTRA and NR DC Configuration Spurious emission Protected band Frequency range (MHz) Maximum Level (dBm) MBW (MHz) NOTE DC_3A_n1A E-UTRA Band 1, 5, 7, 8, 11, 18, 19, 20, 21, 26, 27, 28, 31, 32, 38, 40, 41, 43, 44, 50, 51, 65, 67, 72, 73...
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.3.5 MSD analysis for DC
For 2UL/2DL UE coexistence study 2nd, 3rd, 4th and 5th order harmonics and 2nd, 3rd, 4th and 5th order intermodulation products were calculated and presented in Table 6.1.3.5-1 Table 6.1.3.5-1: Harmonic and IMD analysis UE UL carriers fx_low fx_high fy_low fy_high UL frequency (MHz) 1710 1785 1920 1980 2nd harmonics fr...
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.4 DC_7_n77, DC_7-7_n77
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.4.1 Operating bands for DC
Table 6.1.4.1-1: DC band combination of 1 LTE band + 1 NR band EN-DC band E-UTRA Band NR Band Single UL allowed DC_7_n773 7 n77 No DC_7-7_n773 CA_7-7 n77 No NOTE 3: Applicable for UE supporting inter-band carrier aggregation with mandatory simultaneous Rx/Tx capability
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.4.2 Configuration for DC
Table 6.1.4.2-1: Inter-band EN-DC configurations of 1 LTE band + 1 NR band EN-DC configuration Uplink EN-DC configuration (NOTE 1) E-UTRA configuration NR configuration DC_7A_n77A DC_7A_n77A 7A n77A DC_7A-7A_n77A DC_7A_n77A CA_7A-7A n77A
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.4.3 Maximum output power for DC
Table 6.1.4.3-1: Maximum output power for inter-band EN-DC of 1 LTE band + 1 NR band DC configuration Power class 3 (dBm) Tolerance (dB) DC_7A_n77A 23 +2/-3
60867663a50f38ca462c3e99d4cdca20
37.716-11-11
6.1.4.4 Spurious emission band UE co-existence for DC
Table 6.1.4.4-1: Spurious emissions for inter-band EN-DC of 1 LTE band + 1 NR band E-UTRA and NR DC Configuration Spurious emission Protected band Frequency range (MHz) Maximum Level (dBm) MBW (MHz) NOTE DC_7A_n77A E-UTRA Band 1, 2, 3, 4, 5, 7, 8, 10, 11, 18, 19, 20, 21, 26, 27, 28, 31, 32, 33, 34, 40, 50, 51, 65, 66, ...