Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 38.101-3  Word version:  17.4.0

Top   Top   Up   Prev   Next
1…   4…   5…   6…   7…   A…

 

4  GeneralWord‑p. 16

4.1  Relationship between minimum requirements and test requirementsWord‑p. 16

The present document is interwork specification for NR UE, covering RF characteristics and minimum performance requirements. Conformance to the present specification is demonstrated by fulfilling the test requirements specified in the conformance specification TS 38.521-3.
The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification TS 38.521-3 defines test tolerances. These test tolerances are individually calculated for each test. The test tolerances are used to relax the minimum requirements in this specification to create test requirements. For some requirements, including regulatory requirements, the test tolerance is set to zero.
The measurement results returned by the test system are compared - without any modification - against the test requirements as defined by the shared risk principle.
The shared risk principle is defined in Recommendation ITU-R M.1545 [6].
Up

4.2  Applicability of minimum requirementsWord‑p. 17

a)
In this specification the Minimum Requirements are specified as general requirements and additional requirements. Where the Requirement is specified as a general requirement, the requirement is mandated to be met in all scenarios
b)
For specific scenarios for which an additional requirement is specified, in addition to meeting the general requirement, the UE is mandated to meet the additional requirements.
c)
The spurious emissions power requirements are for the long-term average of the power. For the purpose of reducing measurement uncertainty it is acceptable to average the measured power over a period of time sufficient to reduce the uncertainty due to the statistical nature of the signal.
d)
Terminal that supports EN-DC or NE-DC configuration shall meet E-UTRA requirements as specified in TS 36.101 and NR requirements as in TS 38.101-1 and TS 38.101-2 unless otherwise specified in this specification.
e)
All the requirements for intra-band contiguous and non-contiguous EN-DC or NE-DC apply under the assumption of the same uplink-downlink and special subframe configurations in the E-UTRA and slot format indicated by UL-DL-configurationCommon and UL-DL-configurationDedicated in the NR for the EN-DC or NE-DC.
f)
For EN-DC or NE-DC combinations with CA configurations for E-UTRA and/or NR, all the requirements for E-UTRA and/or NR all the requirements for E-UTRA and/or NR intra-band contiguous and non-contiguous CA apply under the assumption of the same slot format indicated by UL-DL-configurationCommon and UL-DL-configurationDedicated in the PSCell and SCells for NR and the same uplink-downlink and special subframe configurations in Pcell and SCells for E-UTRA.
A terminal which supports an EN-DC or NE-DC configuration shall support:
  • If any subsets of the EN-DC or NE-DC configuration do not specify its own bandwidth combination sets in clause 5.3B, then the terminal shall support the same E-UTRA bandwidth combination sets it signals the support for in E-UTRA CA configuration part of E-UTRA - NR DC and shall support the same NR bandwidth combination sets it signals the support for in NR CA configuration part of E-UTRA - NR DC.
Else if one of the subsets of the EN-DC or NE-DC configuration specify its own bandwidth combination sets in clause 5.3B, then the terminal shall support a product set of channel bandwidth for each band specified by E-UTRA bandwidth combination sets, NR bandwidth combination sets, and EN-DC or NE-DC bandwidth combination sets it singnals the support.A terminal which supports an inter-band EN-DC or NE-DC configuration with a certain UL configuration shall support the all lower order DL configurations of the lower order EN-DC or NE-DC combinations, which have this certain UL configuration and the fallbacks of this UL configuration.
A terminal which supports NE-DC configurations shall meet the minimum requirements for corresponding EN-DC configuration, unless otherwise specified.
For CA or DC configurations, which include FR2 intra-band CA combinations with multiple FR2 sub-blocks, where at least one of the sub-blocks is a contiguous CA combination :
  • if the field partialFR2-FallbackRX-Req is not present, the UE shall meet all applicable UE RF requirements for the highest order CA configuration and all associated fallback CA configurations;
  • if the field partialFR2-FallbackRX-Req is present, for each FR2 intra-band CA configuration with multiple sub-blocks that the UE indicates support for explicitly in UE capability signalling: the in-gap UE RF requirements in clauses 7.5A, 7.5B, 7.6A, 7.6B apply as the equivalent requirements for the associated fallback FR2 intra-band CA configurations with the same number of sub-blocks, where at least one of the sub-blocks consists of a contiguous CA configuration. The UE shall meet all applicable UE RF requirements for fallback CA configurations with a lesser number of sub-blocks;
  • regardless of the field partialFR2-FallbackRX-Req, the UE shall meet all DL out-of-gap requirements for all lower order fallback CA configurations.
Terminal that supports inter-band NR-DC between FR1 and FR2 configuration shall meet the requirements for corresponding CA configuration (suffix A), unless otherwise specified.
Up

4.3  Specification suffix informationWord‑p. 18

Unless stated otherwise the following suffixes are used for indicating at 2nd level clause, shown in Table 4.3-1.
Clause suffix Variant
NoneSingle Carrier
ACarrier Aggregation (CA) between FR1 and FR2
BDual-Connectivity (DC) with and without SUL including UL sharing from UE perspective, inter-band NR DC between FR1 and FR2
DUL MIMO
EV2X
FShared spectrum channel access
 
Up

Up   Top   ToC