| R2-2503424 Discussion on other aspects of SBFD.docx |
3GPP TSG-RAN WG2 Meeting #129bis R2-2503424
St.Julians, Malta, May 19th – 23rd, 2025
Source: CATT
Title: Discussion on other aspects for SBFD
Agenda Item: 8.11.3
Document for: Discussion
1. |
Conclusion
Based on the analysis in section 2, the proposals are summarized as following:
Spotted issues in RRC running CR
Proposal 1-1: Support the running CR that pucch-CSI-ResourceList is extended directly in CSI-ReportConfig with PUCCH-CSI-ResourceExt-v19xy.
Proposal 1-2: RAN2 agree that the IE reportQuantity is extended directly in CSI-ReportConfig. Merge the TP1 below in to the RRC running CR.
------------------------------------TP1 on CSI-ReportConfig ---------------------------------------------------------------
.
.
.
]],
[[
nrofReportedCLImeasureResources-r19 ENUMERATED {n1, n2, n3, n4} OPTIONAL, -- Need R
pucch-CSI-ResourceListExt-r19 SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-ResourceExt-v19xy OPTIONAL, -- Need R
symbolType-r19 ENUMERATED {sbfd, non-sbfd} OPTIONAL, -- Need R
]]
}
Proposal 2: RAN2 agree to use Uplink-powerControl-v19xy in ServingCellConfig and merge the TP2 into the RRC running CR.
---------------------------------------------TP2 on ServingCellConfig -----------------------------------------------------
ServingCellConfig information element
-- ASN1START
-- TAG-SERVINGCELLCONFIG-START
ServingCellConfig ::= SEQUENCE {
.
.
.
[[
mimoParam-v1850 SetupRelease {MIMOParam-v1850} OPTIONAL -- Need M
]]
.
.
.
MIMOParam-v1850 ::= SEQUENCE {
additionalTDDConfig-perPCI-ToAddModList-r18 SEQUENCE (SIZE (1..maxNrofAdditionalPCI-r17)) OF AdditionalTDDConfig-perPCI-ToAddMod-r18
OPTIONAL, -- Cond 2TA-TDD-Only
additionalTDDConfig-perPCI-ToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofAdditionalPCI-r17)) OF AdditionalPCIIndex-r17
OPTIONAL -- Need N
}
Design of CLI measurement and reporting
Proposal 3: RAN2 discuss the TP3 on CSI-ResourceConfig and merge it into the RRC running CR:
---------------------------------------------TP3 on CSI-ResourceConfig------------------------------------
CSI-ResourceConfig ::= SEQUENCE {
]]
}
Proposal 4-1: RAN2 agree the data structure of CSI-MeasConfig including these lists:
cli-RSSI-MeasurementResourceSetToAddModList
cli-RSSI-MeasurementResourceSetToReleaseList
cli-RSSI-MeasurementResourceToAddModList
cli-RSSI-MeasurementResourceToReleaseList
srs-RSRP-MeasurementResourceSetToAddModList
srs-RSRP-MeasurementResourceSetToReleaseList
srs-RSRP-MeasurementResourceToAddModList
srs-RSRP-MeasurementResourceToReleaseList
Proposal 4-2: RAN2 agree the data structure as below if proposal 4-1 is agreed:
cli-RSSI-MeasurementResourceSetToAddModList
CLI-RSSI-MeasurementResourceSet
cli-RSSI-MeasurementResourceSetId
cli-RSSI-MeasurementResourceIdList
aperiodicTriggeringOffset
cli-RSSI-MeasurementResourceToAddModList
CLI-RSSI-MeasurementResource
cli-RSSI-MeasurementResourceId
startSymbol
nrofSymbols
startPRB
nrofPRBs
cli-RSSI-PeriodicityAndOffset
qclInfo-Periodic-CLI-RSSI-MeasurementResource
srs-RSRP-MeasurementResourceSetToAddModList
SRS-RSRP-MeasurementResourceSet
srs-RSRP-MeasurementResourceSetId
srs-RSRP-MeasurementResourceIdList
aperiodicTriggeringOffset
srs-RSRP-MeasurementResourceToAddModList
SRS-RSRP-MeasurementResource
srs-RSRP-MeasurementResourceId
srs-Resource
qcl-InfoPeriodicSRS-RSRP-MeasurementResource
Proposal 4-3: RAN2 discuss and merge the TP4 on CSI-MeasConfig into the RRC running CR:
------------------------------------------------TP4 on CSI-MeasConfig------------------------------------------------------
CSI-MeasConfig ::= SEQUENCE {
.
.
.
]]
Proposal 4-4: The corresponding elements in the TP4 will be defined as separate IEs in RRC:
CLI-RSSI-MeasurementResource,
CLI-RSSI-MeasurementResourceId,
CLI-RSSI-MeasurementResourceSet,
CLI-RSSI-MeasurementResourceSetId,
SRS-RSRP-MeasurementResource,
SRS-RSRP-MeasurementResourceId,
SRS-RSRP-MeasurementResourceSet ,
SRS-RSRP-MeasurementResourceSetId.
LS to RAN1 on the observed issues in R1-2503155
Proposal 5: RAN2 to send an LS to RAN1 to indicate the spotted issue in RRC parameter list:
- The range of resourceSetCLI should start from 1 instead of 0.
Others
Proposal 6: Confirm the Working assumption: The configured SP CLI measurement resource sets are initially deactivated upon (re-) configuration by upper layers and after reconfiguration with sync.
4. |
| R2-2503441.docx |
3GPP TSG-RAN WG2 Meeting #130 R2-2503441
St Julian’s, Malta, 19 – 23 May 2025
Agenda item: 8.11.3
Source: Xiaomi
Title: Other aspects of SBFD
Document for: Discussion and Decision
|
Conclusion
In this contribution, we discuss RAN2 aspects of SBFD, and propose the following:
Proposal 1: (RRC-2) “Early UL synchronization with an LTM candidate cell” and “RACH-based LTM” are not supported in SBFD symbols.
Proposal 2: In SP CLI measurement resource set activation/deactivation MAC CE, field SP CLI measurement resource set ID refers to either cli-RSSI-MeasResourceSetId-r19 or srs-RSRP-MeasResourceSetId-r19.
Proposal 3: RAN2 to discuss whether PUSCH quality difference between SBFD and non-SBFD symbols should be addressed or not.
|
| R2-2503647 Discussion on the SBFD related issues.docx |
3GPP TSG-RAN WG2 Meeting #130 R2-2503647
St.Julians, Malta, May 19th – 23rd, 2025
Agenda Item: 8.11.3
Source: OPPO
Title: Discussion on the SBFD related issues
Document for: Discussion and Decision
|
Conclusion
According to the analysis provided above, we have the following observations and proposals:
Observation 1: The SSB in SBFD symbol is within DL subband.
Observation 2: The legacy RLM or BFR procedure can make use of multiple RS resources, e.g. some RS resources in SBFD symbols and others in non-SBFD symbols.
Observation 3: The current BFD procedure in MAC is per serving cell or per BFD-RS set of serving cell configured with two BFD-RS sets, i.e. BFI_COUNTER does not reset when the serving beam changes.
Proposal 1: Wait for RAN1/RAN4 inputs on whether a separate measurement gap for SBFD symbol is needed.
Proposal 2: The RLM/BFR procedure does not differentiate between the SBFD symbol and the non-SBFD symbol.
Proposal 3: The additional RO of SBFD symbol is not supported for the OD-SIB1 request.
Proposal 4: Wait for more inputs from the Rel-19 NES discussion before deciding whether/how to support SBFD RO for the PRACH configuration adaptation.
|
| R2-2503875 Discussion on L3 measurements in SBFD.docx |
3GPP TSG-RAN WG2 Meeting #130 R2-2503875
St Julian's, Malta, 19 - 23 May 2025
Source: ZTE Corporation
Title: Discussion on L3 measurements in SBFD
Agenda item: 8.11.3
Document for: Discussion and Decision
|
Conclusion
In this contribution, we propose the following observation and proposals:
L3 measurement filtering on SBFD symbol:
Observation 1: The SSB and CSI-RS can be allocated and measured by the UE on the SBFD symbols, for L1 measurement and L3 measurement.
Observation 2: Due to the interference, even if the RS transmission power is the same, the received RS-RSRP/RSRQ/SINR on SBFD symbols will be different than the received RS-RSRP/RSRQ/SINR on non-SBFD symbols.
Observation 3: Since the SBFD configuration and SSB beam/index/periodicity are cell-specific and pretty fixed, it is very likely that some specific SSB beam directions are always on the SBFD symbols.
Observation 4: If UE only takes the several specific SSB beam directions on SBFD symbol and non-SBFD symbol for L3 measurement, the UE cannot well evaluate the cell quality equally/accurately since a cell may have multiple beams with different directions.
Observation 5: When generating L3 measurements, the SSB beams on the SBFD symbols should also be taken into L3 filtering with equal possibility compared to the SSB beams on the non-SBFD symbols, in order to evaluate the cell quality fairly/accurately.
Proposal 1: Support UE to generate L3 measurement using the RS (CSI-RS/SSB) beam measurements made on SBFD symbols.
Proposal 2: gNB configures additional power threshold to UE, the additional power threshold is used for the consolidation of cell measurement from the beam measurements made on SBFD symbols.
Gap requirement for RRM measurement on SBFD symbol:
Observation 6: The configured or active BWP of a cell may be divided into UL subband and DL subband when SBFD configuration is enabled in the cell.
Observation 7: The frequency resource of the configured MOs (measurement objects) may be allocated in the UE’s UL subband on SBFD symbols.
Observation 8: Whether UE needs a gap to measure a MO that is not within the DL subband on SBFD symbol has RAN2 specification impact, e.g. need for gap design in 38.331, and the gap provision rule in 38.300.
Proposal 3: If a MO is on SBFD symbol but it is not within the DL subband (even if the MO is within current active BWP), UE needs measurement gap to measure such MO. Send LS to RAN4 to confirm this understanding.
Serving cell measurement on SBFD symbol:
Observation 9: If all the NCD SSBs of a cell are restricted to be within DL subband, it is hard for gNB to allocate a proper DL/UL subband frequency division.
Proposal 4: RAN2 sends LS to RAN1 (cc RAN4) to ask whether the CD SSB and/or NCD SSB(s) of a cell should be allocated within DL subband.
Proposal 5: gNB should ensure that the servingCellMO associated with each configured BWP should be configured within the DL subband of the cell, in order to reduce the measurement gap requirement for serving cell measurements.
|
| R2-2503896 SBFD - other aspects.docx |
3GPP TSG-RAN WG2 Meeting #130 R2-2503896
Saint Julian’s, Malta, 19 – 23 May 2025
Agenda item: 8.11.3
Source: Nokia
Title: Other Aspects of SBFD
WID/SID: NR_duplex_evo-Core - Release 19
Document for: Discussion and Decision
1 |
Conclusion
Proposal 1: RAN2 needs to add signaling of SBFD parameters (up to RAN1) within SIB1 which implicitly also means they should be added to ServingCellConfigCommon
Proposal 2: It is up to RAN1 and RAN4 to discuss the configuration of a valid symbol type for RLM/BFD measurements
Proposal 3: RAN2 to agree that separate Layer 3 measurement report for CSI-RS resources in SBFD symbol is not supported and ask for concerns to RAN4 (if any).
Proposal 4: On the potential support of SBFD with dual connectivity (DC), RAN2 prioritizes EN-DC over other DC types.
Proposal 5: The NW should ensure that when establishing voice calls and especially emergency calls (at least for non SBFD aware UEs), resources are not allocated to SBFD symbols (i.e. resources should be DL-only or UL-only symbols).
|
| R2-2504040 SBFD other aspects.docx |
3GPP TSG-RAN WG2 Meeting #130 R2-2504040
St.Julians, Malta, May 19th – 23rd , 2025
Agenda Item: 8.11.3
Source: vivo
Title: SBFD other aspects
Document for: Discussion and Decision
|
Conclusion
Based on the discussion, we have the following observation and proposals:
Proposal 1: SBFD operation is not supported on SUL.
|
| R2-2504225.docx |
3GPP TSG-RAN2 Meeting #130 R2-2504225
St. Julians, Malta, May 19th – 23rd, 2025
Agenda item: 8.11.3
Source: Qualcomm Incorporated
Title: Other aspects of SBFD
WID/SID: NR_duplex_evo-Core – Release 19
Document for: Discussion and Decision
|
Conclusion
We have the following observations, and we’d recommend RAN2 to discuss and adopt the following proposals:
Proposal 1: For UE-specific dedicated RRC configuration on SBFD time/frequency configuration, RAN2 wait for RAN1 further decision on whether support.
Proposal 2: For L1 based UE-to-UE CLI reporting configuration, the resourcesForChannelMeasurement is reused for CLI measurement with the associated ID of CLI resource, i.e., SRS-RSRP and CLI-RSSI resource. The resourcesForChannelMeasurement should be described to cover SRS-RSRP and CLI-RSSI resource.
Proposal 3: The RRC parameters of carrier in CSI-ReportConfig and bwp-Id in the associated CSI-ResourceConfig are reused for CLI measurement resource configurations. The description of these two RRC parameters is updated accordingly to associate with the CLI resource.
Proposal 4: For L1 based UE-to-UE CLI reporting configuration, the AP trigger based CLI-RSSI and SRS-RSRP reporting and periodic based CLI-RSSI reporting is supported.
Proposal 5: The legacy Aperiodic CSI Trigger State Subselection MAC CE is reused to indicate the selection status of the aperiodic trigger states configured for CLI reporting.
Proposal 6: For L1 based UE-to-UE CLI measurement configuration, the configuration of CLI-RSSI resource based on the existing Rel-16 CLI-RSSI resource pattern is supported.
Proposal 7: The separate BFD/BFR procedure on SBFD symbols is not supported.
Proposal 8: UE does not expect to be simultaneously configured with both L3 and L1 UE-to-UE CLI measurement and report resources.
|
| R2-2504328 Discussion on resource configuration aspect in SBFD.docx |
3GPP TSG-RAN WG2 Meeting #130 R2-2504328
St.Julians, Malta, May 19th – 23rd, 2025
Agenda Item: 8.11.3
Source: InterDigital, Inc.
Title: Discussion on resource configuration aspect in SBFD
Document for: Discussion
1. |
Conclusion
Proposal 1: Support to configure dedicated logical channel(s) for SBFD resource allocation (e.g., latency reduction).
Proposal 2: Support to separate resource configuration (e.g., SR ID, PUCCH) to request an UL grant with SBFD symbols.
Proposal 3: Support to separate the resource configuration provided by UE-dedicated RRC signaling from the network enabling either RACH configuration option 1 or option 2.
Proposal 4: Discuss when to request an UL grant with SBFD symbols (or non-SBFD symbols) based on the conditions. The detailed conditions are FFS.
4. |
| R2-2504447 SBFD others.docx |
3GPP TSG-RAN WG2 Meeting #130 R2-2504447
St Julian, Malta, 19th – 23rd May 2025
Agenda item: 8.11.3
Source: Samsung
Title: Other Aspects of SBFD
WID/SID: NR_duplex_evo-Core
Document for: Discussion and Decision
|
Conclusion
Proposal 1: For cli-RSSI-MeasurementResourceSetList and srs-RSRP-MeasurementResourceSetList, only CLI-RSSI-MeasurementResourceSetList-r19 and SRS-RSRP-MeasurementResourceSetList-r19 are needed i.e. no CHOICE structure for this fields.
Proposal 2: Additional restriction to ignore the legacy mandatory field (csi-RS-ResourceSetList) in CSI-ResourceConfig IE is needed if the new CLI measurement resource set is configured.
Proposal 3: RAN2 agree below aspects for CSI-ReportConfig.
New report entities for SRS-RSRP and CLI-RSSI are added in reportQuantity.
Usage of reportConfigType could be added in the field description, such that “for SBFD CLI measurement report configuration, only aperiodic is set”.
Proposal 4: Add the text to ignore the legacy mandatory field of resourceForChannel if the new resourcesForChannelCLI-r19 is present.
Proposal 5: RAN2 confirm that the legacy Aperiodic CSI Trigger State Subselection MAC CE is also used to indicate the selection status of the Aperiodic Trigger States configured for aperiodic CLI measurement report.
Proposal 6: RAN2 confirm that exchange of the information on the activation/deactivation of SRS between gNBs is not supported in Rel-19.
Proposal 7: RAN2 does not support the separate BFD/BFR procedure for SBFD symbols but below proposal in [2] could be used for enhancement of BFD/BFR for SBFD without specification impact.
Keep the legacy BFD and BFR procedure in the MAC layer, i.e., no need for the MAC entity to trigger BFD and BFR for non SBFD symbols and SBFD symbols separately
The network configures the valid symbol type for CSI-RS based RLM/BFD/CBD measurement i.e. SBFD symbols could be used for this RLM/BFD/CBD measurement.
Proposal 8: RAN2 consider to support the separate Layer3 measurement report for CSI-RS resources in SBFD symbol.
|
| R2-2504640 Other aspects about the evolution of duplex operation.docx |
3GPP TSG-RAN WG2 Meeting #130 R2-2504640
St. Julian’s, Malta, 19th – 23rd May, 2025
Agenda Item: 8.11.3
Source: Huawei, HiSilicon
Title: Other aspects about the evolution of duplex operation
Document for: Discussion and Decision
1 |
Conclusion
Based on the above discussion we have the following proposals:
Proposal 1: RAN2 to confirm that the field sbfd-RACH-SingleConfig-r19 is included in RACH-ConfigCommonSBFD-r19 in BWP-UplinkCommon.
Proposal 2: The combination of LTM and SBFD is not supported in Rel-19.
4 |