3GPP TSG-RAN WG2 Meeting #119-e R2-22xxxxx
eMeeting, 17th – 26th August, 2022
CR-Form-v12.1
CHANGE REQUEST
38.331 CR CRNum rev - Current version: 17.1.0
For HELP on using this form: comprehensive instructions can be found at
http://www.3gpp.org/Change-Requests.
Proposed change affects: UICC apps ME X Radio Access Network X Core Network
Title: Correction to additionalSpectrumEmission in NR CA in n77
Source to WG: Ericsson
Source to TSG: R2
Work item code: NR_newRAT-Core Date: 2022-08-22
Category: F Release: Rel-17
Use one of the following categories: Use one of the following releases:
F (correction) Rel-8 (Release 8)
A (mirror corresponding to a change in an earlier Rel-9 (Release 9)
release) Rel-10 (Release 10)
B (addition of feature), Rel-11 (Release 11)
C (functional modification of feature) …
D (editorial modification) Rel-15 (Release 15)
Detailed explanations of the above categories can Rel-16 (Release 16)
be found in 3GPP TR 21.900. Rel-17 (Release 17)
Rel-18 (Release 18)
Reason for change: The solution to the extended use of n77 sub-bands in the USA and Canada
included introduction of:
- New UE capabilities (extendedBand-n77-r16 and extendedBand-n77-
2-r17) indicated by UE that support both the original n77 sub-range
and the added (or extended) sub-range.
- New NS values (NS_55/57), indicated in system information in cells of
the extended subrange to prevent idle mode UEs (that do not indicate
support of the extendedBand-n77-r16/extendedBand-n77-2-r17) to
camp and access the cell. Note that NS_55/NS_57 do not imply any
additional spectrum emission requirement (ie, same as NS_01).
In RRC, the gNb indicates the cell’s NS value in the field
additionalSpectrumEmission. For NR CA, the field description of the field
additionalSpectrumEmission requires that the ”Network configures the same
value in additionalSpectrumEmission for all uplink carrier(s) of the same band
with UL configured”. This ensures that a UE can unambiguously determine
which additional spectrum emission table to apply across all carriers of the
band.
Furthermore, gNB is expected to signal the same values in dedicated
signalling to UE (ServingCellConfigCommon) as is signalled in SIB1
(ServingCellConfigCommonSIB).
In combination, these two requirements are conflicting on how to configure UL
CA in n77 (with at least one cell from original subrange and at least one cell
from the extended subrange).
RAN2 agreed that for UL CA in n77. the network may configure either
NS_55/57 or NS_01 for UL carrier(s) in the extended subrange, and NS_01
for the remaining uplink carrier(s) in this band.
Summary of change: Specify in the field description for additionalSpectrumEmission and in an
additionala note that if NS_55/NS_57 is applicable for at least one uplink
carrier for the extended in a CA configuration, the network may configure
either NS_55/NS_57 or NS_01 for UL carrier(s) NS_01 for the remaining
uplink carrier(s) of the same band.
Both UEs and Networks operating in n77 extended sub-band (supporting
extendedBand-n77-r16/extendedBand-n77-2-r17) are expected to support this
CR.
Impact Analysis
Impacted 5G architecture options: NR SA, (NG)EN-DC, NE-DC,NR-DC
Impacted functionality: Intra-band UL CA in n77
Inter-operability:
1. If the network is implemented according to the CR and the UE is not, the
UE may reject the configuration and trigger re-establishment, since UE does
not expect different NS values for UL carriers of the same band.
2. If the UE is implemented according to the CR and the network is not, there
are no interoperability problems. However, the network may still not configure
UL CA for n77 in some case.
Consequences if not The network cannot configure n77 UL CA with one cell in n77 original
approved: subrange and one cell in extended subrange.
Clauses affected: 6.3.2. Appendix C
Y N
Other specs N Other core specifications TS/TR ... CR ...
affected: N Test specifications TS/TR ... CR ...
(show related CRs) N O&M Specifications TS/TR ... CR ...
Other comments:
This CR's revision history:
3
6.3.2 Radio resource control information elements
<First change>
– FrequencyInfoUL
The IE FrequencyInfoUL provides basic parameters of an uplink carrier and transmission thereon.
FrequencyInfoUL information element
-- ASN1START
-- TAG-FREQUENCYINFOUL-START
FrequencyInfoUL ::= SEQUENCE {
frequencyBandList MultiFrequencyBandListNR OPTIONAL, -- Cond FDD-OrSUL
absoluteFrequencyPointA ARFCN-ValueNR OPTIONAL, -- Cond FDD-OrSUL
scs-SpecificCarrierList SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier,
additionalSpectrumEmission AdditionalSpectrumEmission OPTIONAL, -- Need S
p-Max P-Max OPTIONAL, -- Need S
frequencyShift7p5khz ENUMERATED {true} OPTIONAL, -- Cond FDD-TDD-OrSUL-Optional
...
}
-- TAG-FREQUENCYINFOUL-STOP
-- ASN1STOP
3GPP
4
FrequencyInfoUL field descriptions
absoluteFrequencyPointA
Absolute frequency of the reference resource block (Common RB 0). Its lowest subcarrier is also known as Point A. Note that the lower edge of the actual carrier is not defined
by this field but rather in the scs-SpecificCarrierList (see TS 38.211 [16], clause 4.4.4.2).
additionalSpectrumEmission
The additional spectrum emission requirements to be applied by the UE on this uplink. If the field is absent, the UE uses value 0 for the additionalSpectrumEmission (see TS
38.101-1 [15], table 6.2.3.1-1A, and TS 38.101-2 [39], table 6.2.3.1-2). Network configures the same value in additionalSpectrumEmission for all uplink carrier(s) of the same
band with UL configured, except for additionalSpectrumEmission value corresponding to NS_55/NS_57. If NS_55/NS_57 (see TS 38.101-1 [15], table 6.2.3.1-1) is applicable
for at least one uplink carrier, the network may configure either NS_55/NS_57 or NS_01 for these uplink carriers, and NS_01 for the remaining uplink carrier(s) of the same
band. The additionalSpectrumEmission is applicable all uplink carriers of the same band with UL configured.
frequencyBandList
List containing only one frequency band to which this carrier(s) belongs. Multiple values are not supported.
frequencyShift7p5khz
Enable the NR UL transmission with a 7.5 kHz shift to the LTE raster. If the field is absent, the frequency shift is disabled.
p-Max
Maximum transmit power allowed in this serving cell. The maximum transmit power that the UE may use on this serving cell may be additionally limited by p-NR-FR1
(configured for the cell group) and by p-UE-FR1 (configured total for all serving cells operating on FR1). If absent, the UE applies the maximum power according to TS 38.101-
1 [15] in case of an FR1 cell or TS 38.101-2 [39] in case of an FR2 cell. In this release of the specification, if p-Max is present on a carrier frequency in FR2, the UE shall ignore
the field and applies the maximum power according to TS 38.101-2 [39]. Value in dBm. This field is ignored by IAB-MT, the IAB-MT applies output power and emissions
requirements, as specified in TS 38.174 [63].
scs-SpecificCarrierList
A set of carriers for different subcarrier spacings (numerologies). Defined in relation to Point A. The network configures a scs-SpecificCarrier at least for each numerology
(SCS) that is used e.g. in a BWP (see TS 38.211 [16], clause 5.3).
Conditional Presence Explanation
FDD-OrSUL The field is mandatory present if this FrequencyInfoUL is for the paired UL for a DL (defined in a FrequencyInfoDL) or if this
FrequencyInfoUL is for a supplementary uplink (SUL). It is absent, Need R, otherwise (if this FrequencyInfoUL is for an
unpaired UL (TDD).
FDD-TDD-OrSUL-Optional The field is optionally present, Need R, if this FrequencyInfoUL is for the paired UL for a DL (defined in a FrequencyInfoDL),
or if this FrequencyInfoUL is for an unpaired UL (TDD) in certain bands (as defined in clause 5.4.2.1 of TS 38.101-1 and in
clause 5.4.2.1 of TS 38.104 [12]), or if this FrequencyInfoUL is for a supplementary uplink (SUL). It is absent, Need R,
otherwise.
<Skip>
3GPP
5
Annex C (normative):List of CRs Containing Early Implementable Features and
Corrections
This annex lists the Change Requests (CRs) whose changes may be implemented by a UE of an earlier release than which the CR was approved in (i.e. CRs that contain on their
coversheets the sentence "Implementation of this CR from Rel-N will not cause interoperability issues").
3GPP
6
Table C-1: List of CRs Containing Early Implementable Features and Corrections
TDoc Number (RP-xxxxxx): CR CR Number(s) CR Earliest Additional Information
Title Revision Implementable
Number(s) Release
RP-200335: Correction on usage 1141 2 Release 15
of access category 2 for UAC for
RNA update
RP-201185: Introduction of 1464 5 Release 15
signalling for high-speed train
scenarios
RP-201216: Release-16 UE 1665 2 Release 15 Early implementation part is referring to
capabilities based on RAN1, the aspect covered by R2-2006203:
RAN4 feature lists and RAN2 Extension of CSI-RS capabilities per
codebook type
RP-202768: UE behaviour when 2107 2 Release 15
UL 7.5KHz shift is not supported
RP-202790: Correction on uac- 2130 1 Release 15
AccessCategory1-
SelectionAssistanceInfo
RP-211483: Clarification on the 2581 1 Release 15
initiation of RNA update
RP-201190: Introduction of eCall 1670 - Release 15
over IMS for NR
RP-212598: Distinguishing support 2810 2 Release 15
of extended band n77
RP-213342: Duty cycle signalling 2817 1 Release 15
for power class 1.5
RP-213345: CR on 38.331 for 2859 1 Release 15
introducing UE capability of
txDiversity
RP-220497: Introduction of 2898 2 Release 16
function for RRM enhancements
for Rel-17 NR FR1 HST
RP-221721: CR on the CBM/IBM 2916 2 Release 16
reporting-38331
RP-221736: Distinguishing support 3078 2 Release 15
of band n77 restrictions in Canada
[n77 Canada]
RP-22xxxx: Correction to xxxx - Release 15
additionalSpectrumEmission in NR
CA in n77
3GPP
7
<End of changes>
3GPP
