LTE RELEASE 10 INFORMATION Pursuant KDB Publication 941225 D05A. 1) FCC ID of the specific device(s) covered by the KDB inquiry. 2AU8HSTP310 2) Provide references to the standards used in the design of the product for each device
(FCC ID) in the KDB inquiry, to help identify product implementation and testing requirements, including:
a) The LTE release and version numbers of the 3GPP documents used to implement Release10Cat6 the specific device(s). b) The associated 3GPP release and version numbers required for power ETSI TS 136 521-1 V12.5.0 . measurements and RF test setup conditions. 3) When carrier aggregation applies, implementation and measurement details for the following are necessary:
a) Intra-band and inter-band carrier aggregation requirements for both uplink and including Wi-Fi offloading using LTE-U, LAA or LWA related NA downlink, protocols:
aggregation. i) Support of contiguous and non-contiguous component carriers for intra-band NA ii) The frequency band combinations supported for inter-band carrier aggregation. NA iii) The number of component carriers, including all combinations, supported for NA intra-band and inter-band carrier aggregation in the uplink and downlink. iv) The channel bandwidth configurations applicable to each carrier aggregation configuration and the applicable carrier aggregation Bandwidth Classes; A F, etc. v) Whether restrictions are applied to certain channel combinations. vi) The RB combinations or certain variant protocols supported by the carrier aggregation configurations. NA NA NA b) When carrier aggregation is limited to downlink only; i.e., there is no uplink carrier aggregation, uplink maximum output power (single carrier) is measured for the supported combinations of downlink carrier aggregation:
i) According to the frequency bands and channel bandwidths allowed for the NA uplink and downlink configuration combinations. ii) Uplink maximum output power is measured with downlink carrier aggregation active, only for the channel with highest measured maximum output power when downlink carrier aggregation is inactive, to confirm that when downlink carrier aggregation is active uplink maximum output power remains within the specified tune-up tolerance limits and not more than dB higher than the maximum output power measured when downlink carrier aggregation inactive. results;
(a) The implemented CA configurations must be clearly identified along with for example, CA_(band #)(bandwidth the power measurement class) for intra-band configurations and CA_(band #)(bandwidth class)-(band #)(bandwidth class) for inter-band configurations, with respect to the number of carriers being aggregated. In some cases, multiple CA configurations are defined for different combinations of allowed channel bandwidth, which must be clearly identified to support the power measurement results. It should also be identified if all component carriers
(CC) can be used as the primary and secondary carrier (PCC and SCC);
therefore, uplink power measurements should be considered with the applicable combinations of PCC and SCC.
(b) The channel numbers and channel frequencies for both uplink and downlink must be clearly documented for the power measurement. The uplink channel is selected according to b) ii) above. The downlink channels selected to perform the uplink power measurement must satisfy 3GPP channel spacing
(5.4.1A of 3GPP TS 36.521 or equivalent) and channel bandwidth (5.4.2A) requirements. The nominal channel spacing is determined by [BW1 + BW2 0.1*|BW1 BW2|]/2 MHz, where BW1 and BW2 are the channel bandwidths of the CC in a 2-CC aggregation configuration. NA NA NA NA
(c) The downlink PCC channel should be paired with the uplink channel according to normal configurations, as if there is no carrier aggregation. The to the PCC and remain within the downlink SCC should be adjacent for downlink band intra-band CA. For non-contiguous intra-band CA, the SCC should be selected to provide maximum separation from the PCC and must remain fully within the downlink transmission band. For inter-band CA, the SCC should be near the middle of its transmission band. transmission contiguous
(d) When it is unclear a KDB inquiry should be submitted to determine the NA downlink channel selection for the applicable CA configurations. iii) When the uplink maximum output power conditions in ii) are not satisfied, a KDB inquiry is required to determine if SAR evaluation for the uplink with downlink carrier aggregation active may be necessary. iv) When SAR is not required for downlink only carrier aggregation and provided it is fully documented in the SAR report according to procedures in this KDB, a PAG is also not required. c) When uplink carrier aggregation applies, maximum output power and tune-up in each carrier aggregation tolerance specified for each component carrier configuration are required to determine the SAR test configurations. i) When power reduction applies, the maximum output power specifications and measured results with and without carrier aggregation in the reduced power configurations are also necessary. ii) When the maximum output power specified for production units, including tune-up tolerance, varies across channel bandwidth, modulation, RB allocation, channels etc., the conditions must be clearly identified in the KDB inquiry to address SAR testing concerns. d) A clear description of the test equipment and setup is required to support the power NA and SAR measurement results. e) Any other restrictions or limitations associated with the carrier aggregation NA implementation must be clearly identified. NA NA NA NA NA NA 4) When enhanced SC-FDMA is supported for uplink transmissions, details of the limitations and restrictions are necessary to determine SAR NA implementation, measurement requirements, including:
a) Decoupling of control and data transmissions to enable simultaneous transmission NA of PUCCH and PUSCH. b) Non-contiguous data transmission with clustered SC-FDMA to enable NA non-contiguous subcarriers in PUSCH transmissions. c) Issues relating to dynamic switching among the SC-FDMA schemes also need NA consideration to determine SAR test configurations. d) When a partially allocated PUSCH, a cluster of partially allocated PUSCH or a fully allocated PUSCH is transmitted simultaneously either with or without PUCCH, peak to average power ratio of the signal can increase substantially above Rel. 8 implementations. The SAR testing concerns for these need additional consideration. 5) When multiple transmit antennas are used to support uplink MIMO or other transmit diversity configurations, details of the implementation and operation for such features are necessary to determine SAR measurement concerns. These are currently considered on a case-by-case basis for all emerging Rel. 10 LTE products until sufficient information and testing expertise can be established to prepare guidance. 6) UE category and descriptions of the category requirements for supporting carrier aggregation, uplink MIMO and other UE configurations should be clearly described in the KDB inquiry and SAR report. NA 7) While it is highly unexpected and until more can be learned, if it is suspected that the hardware or firmware associated with any LTE Rel. 10 features may introduce SAR influences for a product; for example, certain network enhancement features such as CoMP, HetNet, Relay, SON, cross carrier scheduling, eICIC, enhanced downlink MIMO, MBMS, M2M/D2D support etc., the potential of SAR concerns and any hardware, firmware or other limitations or restrictions applied to alleviate such concerns must be explained in the KDB inquiry and equipment certification filing
(Technical Description exhibit). 8) Detailed descriptions of SVLTE or similar support in any carrier aggregation NA configurations to identify other SAR measurement concerns. NA NA NA 9) Description of the device and other transmitters/antennas contained within it to identify NA various standalone and/or simultaneous transmission SAR testing concerns.