Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 38.101-1  Word version:  17.4.0

Top   Top   Up   Prev   Next
1…   4…   5…   5.2A   5.2B…   5.3…   6…   6.3…   6.5…   7…   7.5…   A…

 

4  GeneralWord‑p. 23

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

The present document is a Single-RAT 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-1.
The Minimum Requirements given in this specification make no allowance for measurement uncertainty. The test specification TS 38.521-1 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 [5].
Up

4.2  Applicability of minimum requirementsWord‑p. 23

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)
All the requirements for intra-band contiguous and non-contiguous CA apply under the assumption of the same slot format indicated by UL-DL-configuration-common in the PCell and SCells for NR SA.
e)
The requirements for Tx diversity in this release are applied for UE which indicates IE [txDiversity-r16].
Up

4.3  Specification suffix informationWord‑p. 23

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)
BDual-Connectivity (DC)
CSupplement Uplink (SUL)
DUL MIMO
EV2X
FShared spectrum channel access
GTx Diversity (TxD)
HCarrier Aggregation(CA) for UL MIMO
 
A terminal which supports the above features needs to meet both the general requirements and the additional requirement applicable to the additional clause (suffixes A to F) in clause 5, clause 6 and clause 7. Where there is a difference in requirement between the general requirements and the additional clause requirements (suffixes A to F) in clause 5, clause 6 and clause 7, the tighter requirements are applicable unless stated otherwise in the additional clause.
A terminal which supports more than one feature in clause 5, clause 6 and clause 7 shall meet all of the separate corresponding requirements.
For a terminal that supports SUL for the band combination specified in Table 5.2C-1, the current version of the specification assumes the terminal is configured with active transmission either on UL carrier or SUL carrier at any time in one serving cell and the UE requirements for single carrier shall apply for the active UL or SUL carrier accordingly.
For a terminal that supports operation in shared spectrum, the current version of this specification assumes in the uplink sub-bands within a wideband channel shall be contiguously allocated to the UE. The uplink requirements for one or more non-transmitted sub-bands between two transmitted sub-bands does not form a part of the current version of this specification.
Up

Up   Top   ToC