3GPP TSG RAN WG1 #124	R1-260XXXX

Gothenburg, SE, Feb. 9th ~ 13th, 2026

Source:	Chair

Title:	Draft Agenda

Document for:	Decision

Meeting registration:	The deadline is Monday, Feb 2nd, 08:00 UTC

Tdoc request:	The deadline is Friday, Jan 30th, 15:00 UTC

Tdoc submission:	The deadline is Friday, Jan 30th, 23:59 UTC

Opening of the meeting (Day 1: 9:00 am)

Call for IPR

I draw your attention to your obligations under the 3GPP Partner Organizations' IPR policies. Every Individual Member organization is obliged to declare to the Partner Organization or Organizations of which it is a member any IPR owned by the Individual Member or any other organization which is or is likely to become essential to the work of 3GPP.

The attention of the delegates to this meeting was drawn to the fact that 3GPP Individual Members have the obligation under the IPR Policies of their respective Organizational Partners to inform their respective Organizational Partners of Essential IPRs they become aware of. The delegates were asked to take note that they were thereby invited: to investigate whether their organization or any other organization owns IPRs which were, or were likely to become Essential in respect of the work of 3GPP. to notify their respective Organizational Partners of all potential IPRs, e.g., for ETSI, by means of the IPR Statement and the Licensing declaration forms (http://www.etsi.org/WebSite/document/Legal/IPRForms.doc).

Competition Law Statement

The attention of the delegates to this meeting was drawn to the fact that 3GPP activities are subject to antitrust and competition laws and that compliance with said laws is therefore required of any participant of this WG meeting including the Chair and Vice Chairs. In case of question, please contact your legal counsel. The present meeting will be conducted with strict impartiality and in the interests of 3GPP. Furthermore, delegates were reminded that timely submission of work items/contributions in advance of WG meetings is important to allow for full and fair consideration of such matters.

Network Usage Conditions

Users shall not use the network to engage in illegal activities. This includes activities such as copyright violation, hacking, espionage or any other activity that may be prohibited by local laws. Users shall not engage in non-work related activities that consume excessive bandwidth or cause significant degradation of the performance of the network. Since the network is a shared resource, users should exercise some basic etiquette when using the 3GPP network at a meeting. It is understood that high bandwidth applications such as downloading large files or video streaming might be required for business purposes, but delegates should be strongly discouraged in performing these activities for personal use. Downloading a movie or doing something in an interactive environment for personal use essentially wastes bandwidth that others need to make the meeting effective. The meeting chairman should remind end users that the network is a shared resource; the more one user grabs, the less there is for another. Email and its attachments already take up significant bandwidth (certain email programs are not very bandwidth efficient). In case of need the chair can ask the delegates to restrict IT usage to things that are essential for the meeting itself. Don’t place your WiFi device in ad-hoc mode Don’t set up a personal hotspot in the meeting room Do try 802.11a if your WiFi device supports it Don’t manually allocate an IP address Don’t be a bandwidth hog by streaming video, playing online games, or downloading huge files Don’t use packet probing software which clogs the local network (e.g., packet sniffers, port scanners)

Consensus Principles Reminder

Decision PCG54/10: PCG approved to incorporate the following text to the agendas of each and every TSG and Working Group on “Consensus principles reminder”: The attention of the delegates to the meeting is drawn to the fact that 3GPP endeavours to reach consensus on all decisions and therefore depends on a cooperative spirit of the Individual Members. In particular, Individual Members are encouraged to seek a consensus-based solution and only to sustain objections as a very last resort, and where absolutely necessary and well justified. The leadership will conduct the present meeting in a manner whereby informal methods of reaching consensus are encouraged, whilst ensuring that well justified concerns are taken into account.

Streamlined Standards

Endorsement RAN#107: RAN endorsed the following working principle for 6G (in RP-250766): 3GPP to create lean and streamlined standards for 6G, e.g., by dimensioning an appropriate set of functionalities, minimizing the adoption of multiple options for the same functionality, avoiding excessive configurations, etc. Any exception to the above shall be well justified.

Check-in for Registered Delegates

The attention of the delegates to this meeting was drawn to the fact that it is not permitted to check in other delegates on their behalf. In the event of technical difficulties preventing check-in, delegates should present themselves in person to the Secretary.

Approval of Agenda

R1-2600001	Draft Agenda of RAN1#124 meeting	RAN1 Chair

R1-2600004	RAN1#124 Meeting Timelines, Scope, Process	RAN1 Chair, ETSI MCC

R1-2600406	Draft Agenda of RAN1#124 meeting	RAN1 Chair

Highlights from RAN plenary

R1-2600002	Highlights from RAN#110	RAN1 Chair

Approval of Minutes from previous meetings

R1-2600003	Report of RAN1#123 meeting	ETSI MCC

Incoming Liaison Statements

R19 AI/ML

R1-2600016	LS on RAN check point of R20 NR_AIML_air_Ph2	RAN4, vivo, Ericsson

RAN4 confirmed the feasibility of option 3 in LS that RAN1 can take it into account, corresponding action has been taken after RANP discussion and reflected in updated WID, no need of additional discussion on this LS in RAN1.

R1-2600021	LS on AI/ML UE sided data collection	SA2, Samsung, vivo

SA2 updated RAN and RAN2 about the discussion status on how to support the transfer of standardized data over UP for UE data collection for UE-side model training, which has been discussed in RAN#110 and RANP has concluded in RP-253847 a way forward that

Way forward agreement on UE sided data collection:

To avoid parallel work in 5G and 6G, no normative work in Rel-20 for UE side data collection. Focus data collection framework work on 6G, and use the lesson learned across all the WGs to design something for 6G.

From RAN perspective, we see value for SA2/SA5 and SA3 to complete/finalize their study so we can use the lessons learned for 6G.

The fact that 5G didn’t have normative phase does not preclude standardized solutions in 6G.

No need of additional discussion on this LS in RAN1.

R1-2600024	LS on completion of Study on AI/ML consistency alignment	SA, T-Mobile

SA2 informed all related TSGs and WGs that SA conducted the Study on AI/ML consistency alignment in TR 22.850 and the TR was approved in SA#110, and confirmed no further work planned on this activity. No need of dedicated discussion on this LS in RAN1.

R1-2600012	LS on definition of "ground truth label" in AI/ML-based Positioning Case 3a	RAN3, Huawei

RAN3 is asking RAN1 to consider the above RAN3 captured definition of “ground truth label” and provide feedback. To be handled under AI 8.1, Moderator Yufei (Ericsson)

Relevant Tdocs:

R1-2600613	Draft LS reply on definition of “ground truth label” in AI/ML-based Positioning Case 3a	Nokia

R1-2600284	Draft reply LS on definition of “ground truth label” in AI/ML-based Positioning Case 3a	CATT

R19-LTM

R1-2600006	LS on CSI-IM resources/sets in LTM-Candidate	RAN2, Huawei

RAN2 is asking RAN1 in the LS that whether it is the correct understanding that, in one LTM-Candidate, the network needs to configure at most one CSI-IM-ResourceSet and at most 8 CSI-IM-Resource. RAN1 action is needed, to be handled under AI 7, Moderator Hong (Apple)

Relevant Tdocs:

R1-2600246	Discussion on RAN2 LS on CSI-IM resources/sets in LTM-Candidate	Spreadtrum, UNISOC

R1-2600277	Draft reply LS to RAN2 on on CSI-IM resources/sets in LTM-Candidate	ZTE Corporation, Sanechips

R1-2600285	Draft reply LS on CSI-IM resources/sets in LTM-Candidate	CATT

R1-2600374	Discussion on LS on CSI-IM resources/sets in LTM-Candidate	Nokia

R1-2600468	Draft reply LS on CSI-IM resourcessets in LTM-Candidate	vivo

R1-2600718	Draft reply LS on CSI-IM resources/sets in LTM-Candidate	Samsung

R1-2601440	Draft reply to LS on CSI-IM resources/sets in LTM-Candidate	Huawei, HiSilicon

R1-2600011	Reply LS on per-band UE capabilities for LTM	RAN2, Ericsson

RAN2 is asking RAN1 and RAN4 whether it should be clarified also for the capabilities rach-EarlyTA-Measurement-r18, ta-IndicationCellSwitch-r18, and ue-TA-Measurement-r18 that “if the UE indicates this capability in one band of a FR, it indicates the same capability values for all supported bands in that FR”. RAN1 action is needed, to be handled under AI 8.8, Moderator Hong (Apple)

Relevant Tdocs:

R1-2600163	Discussion on Reply LS on per-band UE capabilities for LTM	OPPO

R1-2600278	Draft reply LS to RAN2 on per-band UE capabilities for LTM	ZTE Corporation, Sanechips

R1-2600286	Draft reply LS on per-band UE capabilities for LTM	CATT

R1-2600373	Discussion on Reply LS on Per-band UE Capabilities for LTM	Nokia

R1-2600469	Draft reply LS on per-band UE capabilities for LTM	vivo

R1-2600719	Draft reply LS on per band UE capabilities for LTM	Samsung

R1-2601441	Discussion on Reply LS on per-band UE capabilities for LTM	Huawei, HiSilicon

R19 LP-WUS

R1-2600005	Reply LS on CN assigned subgroup ID for LP-WUS	RAN2, Ericsson

R1-2600013	Reply LS on CN assigned subgroup ID for LP-WUS	RAN3, Ericsson

Reply LS from RAN2 and RAN3 to SA2‘ LS on CN assigned subgroup ID for LP-WUS, RAN1 cc-ed only, no action needed.

R19 NR/IoT-NTN

R1-2600010	LS on Linear polarization orientation RRC signalling for NR NTN	RAN2, Eutelsat

RAN2 is asking RAN4 whether the signalling of the linear polarization orientation by the network to the UE can be useful for NR NTN and to provide any related feedback. RAN1 cc-ed only. Procedure-wise, it is good to leave it to RAN4 to clarify first. No RAN1 action is needed in this meeting.

Relevant Tdoc:

R1-2600282	Discussion on LS reply on Linear polarization orientation RRC signalling for NR NTN	CATT

R1-2600009	LS on MPDCCH narrowband selection for CB-Msg3-EDT	RAN2, Nokia

RAN2 is asking RAN1 to take into consideration the agreement “The determination of the MPDCCH narrowband for CB-Msg4 monitoring is based on the value of (Contention Resolution identifier included in CB-Msg3 mod 2) (to be captured in MAC).” RAN1 action is needed according to relevant Tdocs, to be handled under AI 8.7.2, Moderator Gilles (MediaTek)

Relevant Tdocs:

R1-2600283	Discussion on LS reply on MPDCCH narrowband selection for CB-Msg3-EDT	CATT

R1-2601030	Discussion on LS from RAN2 on MPDCCH narrowband configuration for CB-Msg3-EDT	Nokia

R1-2601064	On RAN2 LS on MPDCCH narrowband selection for CB-Msg3-EDT	Ericsson

R1-2600018	Reply LS on CQI reporting for CB-Msg3 EDT for eMTC UE	RAN4, CMCC

RAN4 is RAN1 and RAN2 to clarify whether it is possible for a eMTC UE to measure CQI before CB-MSG3 transmission. RAN1 action is needed, to be handled under AI 8.7.2, Moderator Gilles (MediaTek)

Relevant Tdocs:

R1-2600162	Discussion on LS on CQI reporting for CB-Msg3 EDT for eMTC UE	OPPO

R1-2600409	Discussion on the LS on CQI reporting for CB-Msg3 EDT for eMTC UE	Xiaomi

R1-2600471	Draft reply LS on CQI reporting for CB-Msg3 EDT for eMTC UE	vivo

R1-2600637	Discussion on LS on CQI reporting for CB-Msg3 EDT for eMTC UE	OPPO

R1-2600638	Draft reply LS on CQI reporting for CB-Msg3 EDT for eMTC UE	OPPO

R1-2600471	Draft reply LS on CQI reporting for CB-Msg3 EDT for eMTC UE	vivo

R1-2600637	Discussion on LS on CQI reporting for CB-Msg3 EDT for eMTC UE	OPPO

R1-2600638	Draft reply LS on CQI reporting for CB-Msg3 EDT for eMTC UE	OPPO

R1-2601065	On RAN4 Reply LS on CQI reporting for CB-Msg3 EDT for eMTC UE	Ericsson

R1-2601245	On CQI reporting for CB-Msg3 EDT for eMTC UE	Qualcomm Incorporated

R1-2601233	Discussion on the reply LS on CQI reporting for CB-Msg3 EDT for eMTC UE	ZTE Corporation, Sanechips

R1-2600019	LS Reply on precompensation for NB-IoT NTN TDD mode	RAN4, Iridium

RAN4 confirms that RAN1 agreements and assumptions with respect to NTN NB-IoT UL pre-compensation for 249 frequency band have been taken into account. No further RAN1 action is needed.

R16 UE 1Tx-1Tx switch

R1-2600015	LS on UE 1Tx-1Tx switching period capability for NR inter-band UL CA and SUL band combinations	RAN4, Xiaomi

RAN4 has discussed the RF requirements to allow 1Tx UE to support 1Tx-1Tx switching for NR inter-band UL CA and SUL band combinations from the releases earlier than release 18. Now, RAN4 has discussed the possibility of enabling this optional feature from Rel-16 without affecting RAN1 specifications, that’s why RAN1 was cc-ed only, however, it was raised that RAN1 should be involved and it was confirmed that RAN1 will proceed it. RAN1 action is needed, to be handled under AI 7, Moderator Yanping (Xiaomi).

R1-2600095	Discussion on 1Tx-1Tx UL switching	Spreadtrum, UNISOC

R1-2600164	Discussion on RAN4 LS for UE 1Tx-1Tx switching	OPPO

R1-2600407	Discussion on UE 1Tx-1Tx switching period capability from Rel-16	Xiaomi, vivo, China Telecom, Huawei, HiSilicon, China Unicom, Ericsson, CMCC, CATT

R1-2600979	Discussion on RAN4 LS on 1Tx-1Tx UL switching for 1Tx UE	ZTE Corporation, Sanechips

R1-2601422	Discussion on UE 1Tx-1Tx switching period capability for NR inter-band UL CA and SUL band combinations	Nokia

R1-2600017	LS on MAC CE TA command alignment for NB-IoT over NTN	RAN4, Nordic Semiconductor

RAN4 is asking RAN1 to consider aligning MAC-CE TA command timeline defined in TS 36.213 to that in RAN4 specification TS 36.133. RAN1 action is needed, to be handled under AI 6, Moderator Karol (Nordic).

R1-2600281	Discuss on LS reply on MAC CE TA command alignment for NB-IoT over NTN	CATT

R1-2600408	Discussion on the LS on MAC CE TA command alignment for NB-IoT over NTN	Xiaomi

R1-2600470	Discussion on MAC CE TA command alignment for NB-IoT over NTN	vivo

R1-2600639	Discussion on LS on MAC CE TA command alignment for NB-IoT over NTN	OPPO

R1-2600640	Draft reply LS on MAC CE TA command alignment for NB-IoT over NTN	OPPO

R1-2601061	On RAN4 LS on TA command adjust timing for NB-IoT NTN	Ericsson, Nordic Semiconductor, Qualcomm Incorporated, MediaTek

R1-2601232	Discussion on the LS on MAC CE TA command alignment for NB-IoT over NTN	ZTE Corporation, Sanechips

R19-NES

R1-2600007	LS on DCI 2_9 for SSB adaptation for deactivated SCells	RAN2, Nokia

RAN2 confirmed that the UE can receive common DCI format 2_9 for SSB adaptation for a deactivated SCell but the UE shall ignore it for the deactivated SCell, and it requests RAN1 to take it into account and make necessary update if any. RAN1 action needed, to be discussed under AI 8.5, Moderator Seonwook (LG)

Relevant Tdocs:

R1-2600161	Discussion on LS for DCI2_9 for SSB adaptation	OPPO

R1-2600243	Discussion on RAN2 LS on DCI 2_9 for SSB adaptation	Nokia

R1-2600247	Discussion on RAN2 LS on DCI 2_9 for SSB adaptation for deactivated SCells	Spreadtrum, UNISOC

R19-ISAC

R1-2600022	LS on aspects related to RAN coordination	SA2, OPPO

SA2 asks RAN3 to take into account the conclusions defined in clause 8 of TR 23.700-14 for their study and provide the feedback to the above questions. Procedure-wise, it is good to leave it to RAN4 to clarify first. No RAN1 action is needed in this meeting.

R1-2600974	Draft reply on LS on Sensing aspects related to RAN coordination	ZTE Corporation, Sanechips

R20 IoT-NTN

R1-2600020	Reply LS on issues related to support of IMS voice over NB-IoT NTN connected to EPC	SA1, Qualcomm

SA1 inform SA2 that support for more than one (simultaneous) IMS voice call is not required in this Release, but support for Dual-Tone Multi-Frequency (DTMF) is required. RAN1 cc-ed only, no immediate RAN1 action is needed in this meeting, though it could be considered under AI 9.7, if any

R1-2600008	Reply LS on Rel-19 higher layers parameters list Post RAN1#122bis	RAN2, Ericsson

RAN2 informs RAN1 the action and issues that RAN1 should be aware of after receiving RAN1‘s latest lists of higher layer parameters for LTE and NR for Rel-19 work items and TEI. RAN1 cc-ed only. No immediate RAN1 action needed.

R1-2600014	LS on R19 RAN4 UE feature list for NR	RAN4, CMCC

RAN4 informs RAN2 its latest RAN4 UE feature list for NR. RAN1 cc-ed only. No immediate RAN1 action needed.

R1-2600023	Reply LS on traffic model study in RAN1	SA4, InterDigital

SA4 asks RAN1 to take the above information and any future information from SA4 into account when defining detailed realistic traffic models. However, according to RANP decision in RP-253828 on Proposals 1 of RP-253828, i.e., Ensure that any work on AI traffic characteristics in the RAN domain takes place in one place only (lead by RAN2) to avoid fragmentation and duplication with feedback from SA4 on AI traffic characteristics. No RAN1 action needed for a while.

R1-2600025	Inquiry for Liaison on Innovative Modulation and Coding Schemes	ISO/IEC JTC 1/SC 6/AG 4 MCS Innovation

Convenor of ISO/IEC JTC 1/SC 6/AG 4 MCS (Modulation Coding Schemes) is seeking to explore the possibility of establishing a liaison and collaboration mechanism with RAN1. Reply LS could be considered, to be handled under AI 10.3.2, Moderator Jing (Qualcomm).

R1-2600579	LS on publication of ETSI ISG MAT Group Report on “Classification of Candidate Multiple Access Techniques for 6G and their comparison with specified 3GPP features”	ETSI ISG MAT

ETSI ISG MAT is sharing with 3GPP TSG RAN WG1 the publication of the first Group Report GR MAT 001 v1.1.1 with title “Classification of Candidate Multiple Access Techniques for 6G and their comparison with specified 3GPP features”. Reply LS could be considered, but not urgent.

Pre-Rel-19 E-UTRA Maintenance

Only essential corrections – a rejected draft CR will be marked in red

For maintenance on RAN1 specifications, individual draft CRs are to be submitted. Final endorsed CR will be sourced by “Moderator (company name)” and other co-sourcing companies (if any).

Maintenance issues on Pre-Rel-19 E-UTRA will be discussed in RAN1 adhoc1 session (chaired by Sorour).

R1-26xxxxx	Session Notes of AI 6	Ad-Hoc Chair (Ericsson)

R1-2600720	Draft CR for MAC CE TA command alignment for NB-IoT over NTN	Samsung

R1-2601439	Draft CR on MAC CE TA command alignment for NB-IoT over NTN	Huawei, HiSilicon

Pre-Rel-19 NR Maintenance

Only essential corrections – a rejected draft CR will be marked in red

For maintenance on RAN1 specifications, individual draft CRs are to be submitted. For more efficient review, please use/fill the release and WI code fields when requesting tdoc numbers for draft CRs. Final endorsed CR will be sourced by “Moderator (company name)” and other co-sourcing companies (if any).

Maintenance issues on Pre-Rel-19 E-UTRA will be discussed in RAN1 adhoc1 session (chaired by Hiroki).

R1-26xxxxx	Session Notes of AI 7	Ad-Hoc Chair (NTT DOCOMO, INC.)

R1-2600709	Draft CR on channel conveying over DMRS port in TS 38.211	ZTE Corporation, Sanechips

R1-2600721	Discussion on the DM-RS assumption for CSI calculation	Samsung

R1-2600722	Draft CR on the total number of modulation symbols in case of CP-OFDM	Samsung

R1-2600810	Tx utilization with dualUL	Apple

R1-2601086	Applicable Koffset for application time of TA command in NTN	Ofinno

R1-2601087	Applicable Koffset for application time of TA command in TS 38.213	Ofinno

R1-2601088	Power control parameters for RACH-less handover or RACH-less LTM cell switch in TS 38.213	Ofinno

R1-2601100	Draft CR on determination of circular buffer length for TBoMS under limited buffer rate matching	Ofinno

R1-2601101	Draft CR on determination of circular buffer length for UL-SCH under limited buffer rate matching	Ofinno

R1-2601361	Discussion on QCL properties from default beam in Rel-17	Google

Maintenance on Rel-19 NR and E-UTRA

The maximum number of contributions per company/organization/university is limited to 1 per agenda item unless stated otherwise.

For Rel-19 maintenance, only essential corrections will be considered. Only text proposals are to be submitted (no individual draft CRs, please!).

For each text proposal, companies are to provide relevant information (e.g. reason for change, summary of change, consequences if not approved) in a clear and concise manner

Maintenance on Artificial Intelligence (AI)/Machine Learning (ML) for NR Air Interface

Note: Maximum one contribution per company/organization/university. For efficient review, please use the following sections in your contribution corresponding to the maintenance issues, if any:

Specification support for beam management

Specification support for positioning accuracy enhancements

Specification support for CSI prediction

[124-R19-AI/ML] Email discussion on AI/ML – Juan (Qualcomm)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 8.1	Ad-Hoc Chair (Ericsson)

R1-2600092	Maintenance of Rel-19 AI/ML for air interface	Huawei, HiSilicon

R1-2600267	Discussion on maintenance of AI for Air Interface	ZTE Corporation, Sanechips

R1-2600287	Maintenance on Rel-19 AI/ML for NR air interface	CATT

R1-2600472	Maintenance on AI/ML for NR Air Interface	vivo

R1-2600528	Maintenance on Rel-19 AI/ML	InterDigital, Inc.

R1-2600624	Maintenance for AI/ML for NR Air Interface	Google

R1-2600654	Remaining Issues on AIML for NR Air Interface	NEC

R1-2600723	Remaining issue on AI/ML for NR Air Interface	Samsung

R1-2600736	FL summary #0 for AI/ML in beam management	Moderator (Samsung)

R1-2600737	FL summary #1 for AI/ML in beam management	Moderator (Samsung)

R1-2600982	Maintenance on AI/ML for NR Air Interface	Sharp

R1-2601043	Remaining Issues of Rel-19 AIML for NR Air Interface	Ericsson

R1-2601082	Maintenance on AI/ML for NR Air Interface	Nokia

Maintenance on NR MIMO Phase 5

Note: Maximum one contribution per company/organization/university. For efficient review, please use the following sections in your contribution corresponding to the maintenance issues, if any:

Enhancements for UE-initiated/event-driven beam management

CSI enhancements

Support for 3-antenna-port codebook-based transmissions

Enhancement for asymmetric DL sTRP/UL mTRP scenarios.

[124-R19-MIMO] Email discussion on MIMO – Eko (Samsung)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 8.2	Ad-Hoc Chair (Ericsson)

R1-2600084	Maintenance of MIMO Phase 5	Huawei, HiSilicon

R1-2600130	FL Summary Support for 3TX CB-based Uplink; First Round	Moderator (InterDigital, Inc.)

R1-2600172	Remaining Issues of NR MIMO Phase 5	OPPO

R1-2600274	Maintenance on NR MIMO Phase 5	ZTE Corporation, Sanechips

R1-2600288	Maintenance on NR MIMO Phase 5	CATT

R1-2600473	Maintenance on NR MIMO phase 5	vivo

R1-2600594	Maintenance on NR MIMO Phase 5	Ofinno

R1-2600724	Remaining issue on NR MIMO Phase 5	Samsung

R1-2600725	Moderator Summary#1 on Rel-19 CSI enhancements: Round 1	Moderator (Samsung)

R1-2600726	Moderator Summary#1 on Rel-19 CSI enhancements: Round 2	Moderator (Samsung)

R1-2600862	Remaining issues on NR MIMO Phase 5	Fujitsu

R1-2601044	Maintenance of NR MIMO Phase 5	Nokia Corporation

R1-2601154	Summary #1 on Rel-19 asymmetric DL sTRP/UL mTRP	Moderator (OPPO)

R1-2601200	Maintenance on NR MIMO Phase 5	China Telecom

R1-2601305	Maintenance of NR MIMO Phase 5	Ericsson

R1-2601348	Remaining issues on UEI CSI report	ASUSTeK

Maintenance on Evolution of NR duplex operation: Sub-band full duplex (SBFD)

Note: Maximum one contribution per company/organization/university. For efficient review, please use the following sections in your contribution corresponding to the maintenance issues, if any:

SBFD TX/RX/measurement procedures

SBFD random access operation

CLI handling

[124-R19-SBFD] Email discussion on SBFD – Xinghua (Huawei)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 8.3	Ad-Hoc Chair (NTT DOCOMO, INC.)

R1-2600091	Maintenance of Rel-19 SBFD	Huawei, HiSilicon

R1-2600168	Maintenance on NR duplex operation	OPPO

R1-2600268	Discussion on maintenance of SBFD	ZTE Corporation, Sanechips

R1-2600289	Maintenance on SBFD	CATT

R1-2600474	Maintenance on evolution of NR duplex operation: SBFD	vivo

R1-2600595	Maintenance on evolution of NR duplex operation	Ofinno

R1-2600617	Maintenance of SBFD	Nokia

R1-2600652	Maintenance on SBFD procedure	NEC

R1-2600727	Remaining Issues on NR duplex operation	Samsung

R1-2600863	Remaining issues on SBFD operation	Fujitsu

R1-2600932	Maintenance on SBFD	Sharp

R1-2601157	Maintenance on SBFD	Ericsson

R1-2601158	Maintenance on Evolution of NR duplex operation: Sub-band full duplex (SBFD)	NTT DOCOMO, INC.

R1-2601235	Maintenance on SBFD TX/RX/measurement procedures	ITRI

R1-2601246	Maintenance for NR duplex evolution	Qualcomm Incorporated

R1-2601373	Remaining issue on SBFD	ASUSTeK

R1-2601417	Maintenance on SBFD operation	WILUS Inc.

Maintenance on Solutions for Ambient IoT (Internet of Things) in NR

Note: Maximum one contribution per company/organization/university.

[124-R19-A-IoT] Email discussion on A-IoT – Jingwen (CMCC)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 8.4	Ad-Hoc Chair (NTT DOCOMO, INC.)

R1-2600171	Maintenance on Rel-19 Ambient IoT	OPPO

R1-2600290	Remaining issues on Rel-19 A-IoT	CATT

R1-2600410	Discussion on remaining issues for Ambient IoT in NR	Xiaomi

R1-2600657	Maintenance on Solutions for Ambient IoT in NR	NEC

R1-2600728	Maintenance issues on Rel-19 A-IoT	Samsung

R1-2601159	Maintenance on solutions for Ambient IoT in NR	NTT DOCOMO, INC.

R1-2601247	Mainenance for Rel19 Ambient IoT	Qualcomm Incorporated

Maintenance on Enhancements of network energy savings for NR

Note: Maximum one contribution per company/organization/university. For efficient review, please use the following sections in your contribution corresponding to the maintenance issues, if any:

On-demand SSB SCell operation

On-demand SIB1 for idle/inactive mode UEs

Adaptation of common signal/channel transmissions

[124-R19-NES] Email discussion on NES– Ajit (Ericsson)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 8.5	Ad-Hoc Chair (Ericsson)

R1-2600074	Maintenance on Rel-19 Network Energy Savings	Huawei, HiSilicon

R1-2600244	Maintenance on Enhancements of network energy savings	Nokia

R1-2600291	Maintenance on enhancements of network energy savings for NR	CATT

R1-2600475	Maintenance on NR Rel-19 NES	vivo

R1-2600542	Remaining issues on enhancements of NES for NR	LG Electronics

R1-2600596	Maintenance of Enhancements of NES	Ofinno

R1-2600644	Maintenance on enhancements of network energy savings for NR	Sharp

R1-2600729	Maintenance on enhancements of network energy savings for NR	Samsung

R1-2600897	FL summary 1 for on-demand SIB1 in idle/inactive mode	Moderator (MediaTek Inc.)

R1-2600898	FL summary 2 for on-demand SIB1 in idle/inactive mode	Moderator (MediaTek Inc.)

R1-2600899	FL summary 3 for on-demand SIB1 in idle/inactive mode	Moderator (MediaTek Inc.)

R1-2600900	FL summary 4 for on-demand SIB1 in idle/inactive mode	Moderator (MediaTek Inc.)

R1-2600906	Draft CR 38.211 for correcting RRC parameters for R19 NES	Ericsson

Maintenance on Low-power wake-up signal and receiver for NR (LP-WUS/WUR)

Note: Maximum one contribution per company/organization/university. For efficient review, please use the following sections in your contribution corresponding to the maintenance issues, if any:

LP-WUS and LP-SS design

LP-WUS operation in IDLE/INACTIVE modes

LP-WUS operation in CONNECTED modes

[124-R19-LP-WUS] Email discussion on LP-WUS – Xueming (vivo)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 8.6	Ad-Hoc Chair (NTT DOCOMO, INC.)

R1-2600082	Maintenance on LP-WUS/WUR	Huawei, HiSilicon

R1-2600173	WUS monitoring occasions for LP-WUS/WUR	OPPO

R1-2600214	Maintenance on low-power wake-up signal and receiver for NR	Ericsson

R1-2600476	Maintenance on NR Rel-19 LP-WUS	vivo

R1-2600529	Maintenance on LP-WUS operation	InterDigital, Inc.

R1-2600597	Maintenance of LP-WUS Operation	Ofinno

R1-2600730	Maintenance on low-power wake-up signal and receiver for NR	Samsung

R1-2601215	Maintenance on LP-WUS	ZTE Corporation, Sanechips

Maintenance on Non-Terrestrial Networks (NTN) for NR Phase 3, Internet of Things (IoT) Phase 3, and IoT-NTN TDD mode

R1-26xxxxx	Session Notes of AI 8.7	Ad-Hoc Chair (Ericsson)

Maintenance for Rel-19 NR NTN

Note: Maximum one contribution per company/organization/university for R_NTN_Ph3, potential RAN1 impact from NR_NTN_Ku_bands and NR_IoT_NTN_req_test_enh.

Note: For efficient review, please use the following sections in your contribution corresponding to the maintenance issues, if any:

NR_NTN_Ph3

RAN1 impact from NR_NTN_Ku_bands and NR_IoT_NTN_req_test_enh

R1-2600075	Maintenance for Rel-19 NR NTN	Huawei, HiSilicon

R1-2600166	Maintenance for Rel-19 NR NTN	OPPO

R1-2600256	Remaining issues on Rel-19 NR NTN	ZTE Corporation, Sanechips

R1-2600316	Maintenance for Rel-19 NR NTN	CATT

R1-2600411	Maintenance for Rel-19 NR NTN	Xiaomi

R1-2600477	Maintenance on Rel-19 NR NTN	vivo

R1-2600731	Maintenance for Rel-19 NR NTN	Samsung

R1-2600776	Maintenance for Rel-19 NR-NTN	Ericsson

R1-2601059	Discussion on remaining maintenance issues for Rel-19 NR NTN	Nokia

R1-2601160	Maintenance of R19 NR-NTN	NTT DOCOMO, INC.

R1-2601199	Maintenance on NR NTN	Pengcheng Laboratory

R1-2601248	Maintenance for Rel-19 NR NTN	Qualcomm Incorporated

Maintenance for Rel-19 IoT NTN

Note: Maximum one contribution per company/organization/university for IoT_NTN_Ph3 and IoT_NTN_TDD

Note: For efficient review, please use the following sections in your contribution corresponding to the maintenance issues, if any:

IoT_NTN_Ph3

IoT_NTN_TDD

R1-2600076	Maintenance for IoT NTN Phase 3	Huawei, HiSilicon

R1-2600167	Maintenance for Rel-19 IoT NTN	OPPO

R1-2600257	Remaining issues on Rel-19 IoT NTN	ZTE Corporation, Sanechips

R1-2600317	Maintenance for Rel-19 IoT NTN	CATT

R1-2600478	Maintenance on CB-Msg3 and CB-Msg4 for Rel-19 IoT NTN	vivo

R1-2600732	Maintenance for Rel-19 IoT NTN	Samsung

R1-2601028	Maintenance for Rel19 IoT-NTN	Nokia

R1-2601063	Maintenance for Rel-19 IoT-NTN	Ericsson

R1-2601098	Clarification on type of subframes to count for IoT NTN TDD	Iridium, CCL, Nokia

R1-2601117	FL Summary #1 for Rel-19 IoT-NTN maintenance	Moderator (Sony)

R1-2601118	FL Summary #2 for Rel-19 IoT-NTN maintenance	Moderator (Sony)

R1-2601119	Final FL summary for Rel-19 IoT-NTN maintenance	Moderator (Sony)

R1-2601249	Maintenance for Rel-19 IoT NTN	Qualcomm Incorporated

Maintenance on others

Note: Maximum one contribution per company/organization/university, including MCE Phase 3, LB-CA, 7-24GHz for NR, ISAC, Mobility Phase 4, XR Phase 3, LTE-based 5G broadcast Phase 2 and endorsed R19 TEI proposals.

Note: For more efficient review, please use/fill the WI code field when requesting tdoc numbers according to the proposals for individual items, if any. Maximum one contribution per WI code

[124-R19-others] Email discussion on Maintenance on others – Hiroki (Ad-Hoc Chair)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 8.8	Ad-Hoc Chair (NTT DOCOMO, INC.)

R1-2600094	Correction of Rel-19 enhancements for channel modeling for 7-24 GHz	VIAVI Solutions

R1-2600169	Maintenance on low-band CA via switching	OPPO

R1-2600170	Maintenance on ISAC channel modelling	OPPO

R1-2600275	Maintenance on Mobility Phase 4	ZTE Corporation, Sanechips

R1-2600372	Maintenance on measurement related enhancements for LTM	Nokia

R1-2600479	Maintenance on 7-24GHz Channel Modelling and LB CA	vivo

R1-2600521	Naming corrections for LTM	ROHDE & SCHWARZ

R1-2600598	maintenance on mobility enhancement 4	Ofinno

R1-2600711	Maintenance for 7—24 GHz channel model	Ericsson

R1-2600733	Maintenance on other Rel-19 topics	Samsung

R1-2600811	FL summary #1 of Low band carrier aggregation via switching	Moderator (Apple)

R1-2600812	FL summary #2 of Low band carrier aggregation via switching	Moderator (Apple)

R1-2600978	Maintenance on Low band carrier aggregation via switching	ZTE Corporation, Sanechips

R1-2601089	Discussion on low-band CA with switching	Ofinno

R1-2601213	Corrections on lowband carrier aggregation via switching	Ericsson

R1-2601363	Correction on TCI state determination for CLTM	Google

Maintenance on UE features

Note: Maximum one contribution per company/organization/university, including UE Features of Batch A/B/C of RAN1#123. For efficient review, please use the following sections in your contribution corresponding to the maintenance issues for Batch A, Batch B and Batch C, if any. Maximum one contribution per Batch.

UE features Batch A - NTN_Ph3

UE features Batch A - IoT_NTN_Ph3

UE features Batch A - IoT_NTN_TDD

UE features Batch A - TEI19 with [Common_PDCCH_rep_TN])

UE features Batch B - UE NR_duplex_evo

UE features Batch B - NR_LPWUS

UE features Batch B - XR phase 3

UE features Batch B - NR_MC_enh2

UE features Batch B - NR_LBCA

UE features Batch C - NR_AIML_air

UE features Batch C - NR_MIMO_Ph5

UE features Batch C - Netw_Energy_NR_enh

UE features Batch C - NR_Mob_Ph4

UE features Batch C - LTE_terr_bcast_Ph2

UE features Batch C - TEI19 with other than [Common_PDCCH_rep_TN]

[124-R19-UE features] Email discussion on Maintenance on UE features – Hiroki (Ad-Hoc Chair)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 8.9	Ad-Hoc Chair (NTT DOCOMO, INC.)

R1-2600165	UE features for Batch A/B/C	OPPO

R1-2600276	Discussion on UE features	ZTE Corporation, Sanechips

R1-2600292	UE features for Batch A	CATT

R1-2600480	Maintenance on UE features Batch A: NTN_Ph3 and TEI19 with [Common_PDCCH_rep_TN]	vivo

R1-2600734	UE features Batch A	Samsung

R1-2600735	UE features Batch C	Samsung

R1-2600885	Discussion on UE features for AI/ML for NR Air Interface	LG Electronics

R1-2601161	Remaining issues on R19 UE features	NTT DOCOMO, INC.

R1-2601216	Summary of UE Features Batch C	Moderator (AT&T)

R1-2601250	Maintenance on UE features	Qualcomm Incorporated

R1-2601330	UE features Batch A (NTN and TEI19)	Nokia

R1-2601409	Discussion on UE features for NR-NTN	CSCN

R1-2601438	Maintenance on UE features	Huawei, HiSilicon

Release 20 NR

The maximum number of contributions per company/organization/university is limited to 1 per agenda item unless stated otherwise.

Artificial Intelligence (AI)/Machine Learning (ML) for NR air interface enhancements

Please refer to RP-253340 for detailed scope of the WI.

[124-R20-AI/ML] Email discussion on Rel-20 AI/ML – Chenxi (Qualcomm)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 9.1	Ad-Hoc Chair (Ericsson)

CSI spatial/frequency compression without temporal aspects (“Case 0”)

Including target CSI type, measurement and report configuration, CQI RI determination, payload determination, quantization configuration codebook, UCI mapping, CSI processing criteria and timeline, priority rules for CSI reports, as well as NW data collection for training, and performance monitoring.

R1-2600066	Discussion on CSI spatial/frequency compression without temporal aspects (“Case 0”)	FUTUREWEI

R1-2600072	AI/ML for CSI compression	Ericsson

R1-2600079	Discussion on Inference, data collection, and monitoring related aspects for CSI compression	Huawei, HiSilicon

R1-2600096	Discussion on AIML for CSI compression	Spreadtrum, UNISOC

R1-2600174	Discussion on CSI spatial/frequency compression without temporal aspects	OPPO

R1-2600269	Discussion on CSI spatial/frequency compression without temporal aspects	ZTE Corporation, Sanechips

R1-2600318	Specification on AI/ML-based CSI spatial/frequency compression	CATT

R1-2600356	CSI Spatial/temporal compression without temporal aspects	Tejas Network Limited

R1-2600364	CSI spatial/frequency compression without temporal aspects (“Case 0”)	MediaTek Inc.

R1-2600375	Discussion on CSI spatial/frequency compression without temporal aspects	CMCC

R1-2600412	Discussion on two-sided AI based spatial domain and frequency domain CSI compression	Xiaomi

R1-2600481	Discussion on AI/ML CSI compression	vivo

R1-2600534	Discussion on CSI compression	TCL

R1-2600535	Discussion on Lifecycle Management for AI/ML-based CSI Compression	Southeast University

R1-2600589	AI/ML CSI spatial/frequency compression without temporal aspects	InterDigital, Inc.

R1-2600625	AI/ML based CSI Compression	Google

R1-2600646	Discussions on CSI spatial/frequency compression without temporal aspects	Sharp

R1-2600667	Discussion on CSI compression without temporal aspects	NEC

R1-2600680	Discussion on CSI spatial/frequency compression	China Telecom

R1-2600738	Views on two-sided model based CSI compression	Samsung

R1-2600778	Views on AI/ML-based CSI spatial/frequency compression without temporal aspects	Lenovo

R1-2600845	On remaining details of AI based spatial/frequency domain CSI compression	Apple

R1-2600864	Discussion on CSI spatial/frequency compression with AI/ML	Fujitsu

R1-2600879	Discussion on inference, data collection, and monitoring related aspects for CSI compression	KT Corp.

R1-2600886	Discussion on CSI spatial/frequency compression without temporal aspects	LG Electronics

R1-2600939	CSI spatial/frequency compression without temporal aspects (“Case 0”)	HONOR

R1-2600988	Discussion on AI/ML-based CSI compression	ETRI

R1-2601034	Discussion on CSI spatial/frequency compression	Transsion Holdings

R1-2601039	CSI spatial/frequency compression without temporal aspects (“Case 0”)	Fraunhofer HHI, Fraunhofer IIS

R1-2601083	CSI spatial/frequency compression without temporal aspects	Nokia

R1-2601094	Discussion on Inference related aspects for AI CSI compression	Ofinno

R1-2601095	Discussion on inter-vendor training collaboration for two-sided AI/ML models	Ofinno

R1-2601108	CSI Spatial/Frequency Compression Without Temporal Aspects (“Case 0”)	TOYOTA Info Technology Center

R1-2601111	Discussion on inference and other aspects for AI/ML-based CSI compression	Panasonic

R1-2601162	Discussion on CSI spatial/frequency compression without temporal aspects (“Case 0”)	NTT DOCOMO, INC.

R1-2601251	CSI spatial-frequency compression via two-sided model	Qualcomm Incorporated

R1-2601252	FL summary 1 on 9.1.1 for CSI compression via two-sided model	Moderator (Qualcomm Incorporated)

R1-2601253	FL summary 2 on 9.1.1 for CSI compression via two-sided model	Moderator (Qualcomm Incorporated)

R1-2601254	FL summary 3 on 9.1.1 for CSI compression via two-sided model	Moderator (Qualcomm Incorporated)

R1-2601255	FL summary 4 on 9.1.1 for CSI compression via two-sided model	Moderator (Qualcomm Incorporated)

R1-2601290	Discussion on inference related aspects in AI/ML based CSI compression	Quectel

R1-2601316	Discussion on CSI spatial/frequency compression (Case-0)	Rakuten Mobile, Inc

R1-2601350	Discussion on AIML based CSI compression	ASUSTeK

R1-2601388	Discussion on CSI spatial/frequency compression without temporal aspects ("Case-0")	CEWiT

R1-2601434	Inference related aspects of AI/ML-Based CSI compression	Pengcheng Laboratory, BUPT

Inter-vendor training collaboration for two-sided AI/ML models

Including specification of standardized dataset format/content plus dataset exchange, as well as pairing and RAN4 related issues.

R1-2600067	Discussion on inter-vendor training collaboration for two-sided AI/ML models	FUTUREWEI

R1-2600073	Inter-vendor training collaboration for two-sided AI/ML models	Ericsson

R1-2600080	Discussion on Inter-vendor training collaboration and pairing for two-sided AI/ML models	Huawei, HiSilicon

R1-2600097	Discussion on Inter-vendor training collaboration for two-sided AI/ML models	Spreadtrum, UNISOC

R1-2600175	Inter-vendor training collaboration for AI/ML CSI compression	OPPO

R1-2600270	Discussion on inter-vendor training collaboration for two-sided AI/ML models	ZTE Corporation, Sanechips

R1-2600319	Inter-vendor training collaboration for two-sided AI/ML models	CATT

R1-2600357	Inter-vendor training collaboration for two-sided AI/ML models	Tejas Network Limited

R1-2600365	Inter-vendor training collaboration for two-sided AI/ML models	MediaTek Inc.

R1-2600376	Discussion on inter-vendor training collaboration for CSI compression	CMCC

R1-2600413	Discussion on inter-vendor training collaboration for two-sided AI/ML models	Xiaomi

R1-2600482	Discussion on inter-vendor training collaboration for two-sided AI/ML models	vivo

R1-2600587	Discussion on Inter-vendor training collaboration for two-sided AI/ML models	NEC

R1-2600590	Inter-vendor training collaboration for two-sided AI/ML models	InterDigital, Inc.

R1-2600626	Inter-Vendor Collaboration for AI/ML based CSI Compression	Google

R1-2600681	Discussion on inter-vendor training collaboration for two-sided AI/ML models	China Telecom

R1-2600739	Views on Inter-vendor training collaboration for two-sided AI/ML models	Samsung

R1-2600861	Discussion on inter-vendor collaboration for CSI compression	TCL

R1-2600865	Discussion on inter-vendor training collaboration for two-sided AI/ML models	Fujitsu

R1-2600887	Discussion on Inter-vendor training collaboration for two-sided AI/ML models	LG Electronics

R1-2600940	Inter-vendor training collaboration for two-sided AI/ML models	HONOR

R1-2600989	Discussion on inter vendor training collaboration for two-sided AI/ML models	ETRI

R1-2601026	Inter-vendor training collaboration for two-sided AI/ML models	Lenovo

R1-2601084	Inter-vendor training collaboration for two-sided AI/ML models	Nokia

R1-2601109	Inter-Vendor Training Collbaration For Two-Sided AI/ML Models	TOYOTA Info Technology Center

R1-2601112	Discussion on inter-vendor training collaboration for two-sided AI/ML models	Panasonic

R1-2601120	Discussion on Inter-Vendor Training Collaboration for Two-Side AI/ML Models	Sony

R1-2601149	Inter-vendor training collabration for two-sided AI/ML models	Apple

R1-2601150	FL summary # 1 for inter-vendor training collaboration	Moderator (Apple)

R1-2601151	FL summary # 2 for inter-vendor training collaboration	Moderator (Apple)

R1-2601152	FL summary # 3 for inter-vendor training collaboration	Moderator (Apple)

R1-2601153	FL summary # 4 for inter-vendor training collaboration	Moderator (Apple)

R1-2601163	Discussion on Inter-vendor training collaboration for two-sided AI/ML models	NTT DOCOMO, INC.

R1-2601256	Inter-vendor training collaboration for two-sided CSI compression use case	Qualcomm Incorporated

R1-2601291	Discussion on inter-vendor training collaboration for two-sided models	Quectel

R1-2601307	Discussion on inter-vendor training collaboration aspects for two-sided AI/ML models	KT Corp.

R1-2601351	Discussion on pairing aspect	ASUSTeK

NR MIMO Phase 6

Please refer to RP-252936 for detailed scope of the WI.

[124-R20-MIMO] Email discussion on Rel-20 MIMO – Darcy (MTK)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 9.2	Ad-Hoc Chair (Ericsson)

Improvement of SRS capacity and coverage

Including a) Multiple frequency-domain starting positions for SRS repetition, and b) Cross-slot SRS between one U slot and one adjacent S slot.

R1-2600085	Improvement of SRS capacity and coverage	Huawei, HiSilicon

R1-2600098	Discussion on improvement of SRS capacity and coverage	Spreadtrum, UNISOC

R1-2600131	NR MIMO Phase 6: SRS Enhancement	InterDigital, Inc.

R1-2600176	Discussion on enhancement of SRS capacity and coverage for MIMO phase 6	OPPO

R1-2600225	Discussion on enhancement of SRS capacity and coverage for MIMO phase 6	TCL

R1-2600272	Discussion on improvement of SRS capacity and coverage	ZTE Corporation, Sanechips

R1-2600320	Discussion on enhancements for SRS capacity and coverage	CATT

R1-2600321	Moderator summary on improvement of SRS capacity and coverage: Round1	Moderator (CATT)

R1-2600322	Moderator summary on improvement of SRS capacity and coverage: Round2	Moderator (CATT)

R1-2600323	Moderator summary on improvement of SRS capacity and coverage: Round3	Moderator (CATT)

R1-2600324	Moderator summary on improvement of SRS capacity and coverage: Round4	Moderator (CATT)

R1-2600337	Improvement of SRS capacity and coverage	Tejas Network Limited

R1-2600350	Improvement of SRS capacity and coverage	MediaTek Inc.

R1-2600414	Discussion on the SRS capacity and coverage enhancement	Xiaomi

R1-2600483	Discussion on improvement of SRS capacity and coverage	vivo

R1-2600618	Improvement of SRS Capacity and Coverage	Nokia

R1-2600675	Discussion on improvement of SRS capacity and coverage	NEC

R1-2600682	Discussion on SRS capacity and coverage improvement	China Telecom

R1-2600710	On Rel-20 improvement of SRS capacity and coverage	Ericsson

R1-2600740	Views on Improvement of SRS capacity and coverage	Samsung

R1-2600779	Improvement of SRS capacity and coverage	Lenovo

R1-2600813	On Rel-20 MIMO SRS capacity and coverage improvement	Apple

R1-2600866	Discussion on improvement of SRS capacity and coverage	Fujitsu

R1-2600881	Discussion on improvement of SRS capacity and coverage	Panasonic

R1-2600888	Discussion on Enhancing DL CSI acquisition	LG Electronics

R1-2600941	Discussion on improvement of SRS capacity and coverage	HONOR

R1-2600990	Discussion on improvement of SRS capacity and coverage for NR MIMO Phase 6	ETRI

R1-2601121	Further discussion on improvements of SRS capacity and coverage	Sony

R1-2601164	Discussion on Improvement of SRS capacity and coverage	NTT DOCOMO, INC.

R1-2601257	SRS enhancements in 5G MIMO Phase 6	Qualcomm Incorporated

R1-2601317	Improvement of SRS capacity and coverage	Sharp

R1-2601328	Discussion on Improvement of SRS Capacity and Coverage	Rakuten Mobile, Inc

R1-2601357	Views on improvement of SRS capacity and coverage	KDDI Corporation

Enhancing DL CSI acquisition

Including a) Early SRS/CSI/CSI-RS triggering, and b) CSI-RS density reduction for 48, 64, and 128 CSI-RS ports.

R1-2600064	Enhancing DL CSI acquisition	FUTUREWEI

R1-2600086	DL CSI acquisition enhancement	Huawei, HiSilicon

R1-2600099	Discussion on enhancing DL CSI acquisition	Spreadtrum, UNISOC

R1-2600132	NR MIMO Phase 6: DL CSI Enhancement	InterDigital, Inc.

R1-2600177	Discussions on Enhancing DL CSI Acquisition	OPPO

R1-2600226	Discussions on Enhancing DL CSI Acquisition	TCL

R1-2600273	Discussion on enhancing DL CSI acquisition	ZTE Corporation, Sanechips

R1-2600325	Discussion on enhancing DL CSI acquisition	CATT

R1-2600338	Enhancing DL CSI acquisition	Tejas Network Limited

R1-2600351	Enhancing DL CSI acquisition	MediaTek Inc.

R1-2600371	On DL CSI Acquisition Enhancements for FR1	Nokia

R1-2600415	Discussion on enhancing DL CSI acquisition	Xiaomi

R1-2600484	Discussion on enhancing DL CSI acquisition	vivo

R1-2600599	Discussion on enhancing DL CSI acquisition	Ofinno

R1-2600647	Moderator summary on enhancing DL CSI acquisition (Round 0)	MediaTek Inc.

R1-2600648	Moderator summary on enhancing DL CSI acquisition (Round 1)	MediaTek Inc.

R1-2600649	Moderator summary on enhancing DL CSI acquisition (Round 2)	MediaTek Inc.

R1-2600650	Moderator summary on enhancing DL CSI acquisition (Round 3)	MediaTek Inc.

R1-2600655	Discussion on Enhancing DL CSI acquisition	NEC

R1-2600741	Views on Enhancing DL CSI acquisition	Samsung

R1-2600777	Enhancing DL CSI acquisition	Lenovo

R1-2600814	On Rel-20 MIMO CSI enhancement	Apple

R1-2600867	Discussion on enhancing DL CSI acquisition	Fujitsu

R1-2600981	Discussion on early DL CSI acquisition design	Fainity Innovation

R1-2600991	Discussion on enhancing DL CSI acquisition for NR MIMO Phase 6	ETRI

R1-2601067	Discussion on Early DL CSI Acquisition Enhancements	Panasonic

R1-2601122	Further discussion on DL CSI acquisition enhancements	Sony

R1-2601165	Discussion on Enhancing DL CSI acquisition	NTT DOCOMO, INC.

R1-2601204	Discussion on enhancing DL CSI acquisition	Google

R1-2601236	Discussion on DL CSI acquisition	ITRI, Acer Incorporated

R1-2601258	DL CSI acquisition enhancements in 5G MIMO Phase 6	Qualcomm Incorporated

R1-2601289	Enhancing DL CSI acquisition	Sharp

R1-2601327	Enhanced DL CSI acquisition for MIMO Phase 6	Ericsson

R1-2601332	Discussion on Enhancement of DL CSI Acquisition	Rakuten Mobile, Inc

R1-2601405	Discussion on Enhancing DL CSI acquisition	LG Electronics

R1-2601406	Discussion on enhancing DL CSI acquisition	NICT

Study of Enhancements for solutions for Ambient IoT (Internet of Things) in NR outdoor for active devices

Please refer to RP-253394 for detailed scope of the SI.

[124-R20-A-IoT] Email discussion on Rel-20 A-IoT – Jay (LGE)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 9.3	Ad-Hoc Chair (NTT DOCOMO, INC.)

Evaluations

Including necessary evaluation assumptions of deployment scenarios for coverage and coexistence, evaluations of achievable cell edge data rate and link budget, as well as applicability and necessity of Device 2b and Device C to given scenarios.

R1-2600068	Evaluations for R20 A-IoT	FUTUREWEI

R1-2600087	Evaluation for active A-IoT device in outdoor scenario	Huawei, HiSilicon

R1-2600100	Evaluations for outdoor Ambient IoT	Spreadtrum, UNISOC

R1-2600178	Discussion on EVM for Rel-20 A-IoT	OPPO

R1-2600209	Discussion on Rel-20 A-IoT evaluation assumptions and results	Ericsson

R1-2600326	Evaluation methodology for A-IoT outdoor deployment scenarios	CATT

R1-2600367	Evaluation for Rel-20 AIoT	Nokia

R1-2600377	Discussion on evaluation results	CMCC

R1-2600416	Discussion on evaluation methodology for Ambient IoT in NR outdoor for active devices	Xiaomi

R1-2600450	Discussion on evaluation for active Ambient IoT device	ZTE Corporation, Sanechips

R1-2600462	FL summary #1 for Ambient IoT: “9.3.1 Evaluations”	Moderator (Huawei)

R1-2600463	FL summary #2 for Ambient IoT: “9.3.1 Evaluations”	Moderator (Huawei)

R1-2600464	FL summary #3 for Ambient IoT: “9.3.1 Evaluations”	Moderator (Huawei)

R1-2600465	Ambient IoT evaluation results spreadsheet for TR38.769	Moderator (Huawei)

R1-2600466	Summary of Ambient IoT evaluation results for TR38.769	Moderator (Huawei)

R1-2600485	Evaluation on Coverage for R20 AIoT	vivo

R1-2600544	Evaluations for Rel-20 Ambient IoT SI	LG Electronics

R1-2600658	Evaluations for Ambient IoT	NEC

R1-2600742	Evaluations for Rel-20 Ambient IoT	Samsung

R1-2601073	Evaluations for Active AIoT Devices	InterDigital, Inc.

R1-2601166	Study on evaluations for Ambient IoT outdoor for active device	NTT DOCOMO, INC.

R1-2601259	Evaluations for Ambient IoT in NR outdoor for active devices	Qualcomm Incorporated

R1-2601445	Evaluation for Rel-20 AIoT	IIT Kanpur

Study of air interface for Device 2b/C

Please refer to the first paragraph of objective 1 for the given conditions. Including study necessary and feasible changes to the Rel-19 air interface for Device 2b/C.

R2D signals, channels, waveform and procedures

Including necessary and feasible change to R2D waveform and modulation, line coding, FEC, CRC and repetitions, bandwidth, timing and Sync signals, L1 control/scheduling, and multiplexing

R1-2600069	R2D Air Interface for Device 2b/C	FUTUREWEI

R1-2600088	Study on R2D signals, channels, waveform and procedures	Huawei, HiSilicon

R1-2600101	Discussion on R2D signals, channels, waveform and procedures for Ambient IoT	Spreadtrum, UNISOC

R1-2600179	Discussion on necessary and feasible change to R2D for Rel-20 A-IoT	OPPO

R1-2600210	R2D signals, channels, waveform, and procedures	Ericsson

R1-2600327	Study of R2D signals, channels, and waveform and procedure of A-IoT enhancement for device 2b/C	CATT

R1-2600360	Discussion on AIoT R2D signals, channels, and procedures	Tejas Network Limited

R1-2600368	AIoT R2D signals, channels, waveform and procedures	Nokia

R1-2600378	Discussion on R2D signals, channels, waveform and procedures	CMCC

R1-2600417	Discussion on R2D signals, channels, waveform and procedures for Device 2b/C	Xiaomi

R1-2600451	Discussion on R2D design for active Ambient IoT device	ZTE Corporation, Sanechips

R1-2600486	Discussion on R2D Aspects for R20 AIoT	vivo

R1-2600487	FL summary #1 on AI 9.3.2.1 R2D Aspects for R20 AIoT	Moderator (vivo)

R1-2600488	FL summary #2 on AI 9.3.2.1 R2D Aspects for R20 AIoT	Moderator (vivo)

R1-2600489	FL summary #3 on AI 9.3.2.1 R2D Aspects for R20 AIoT	Moderator (vivo)

R1-2600490	FL summary #4 on AI 9.3.2.1 R2D Aspects for R20 AIoT	Moderator (vivo)

R1-2600491	FL summary #5 on AI 9.3.2.1 R2D Aspects for R20 AIoT	Moderator (vivo)

R1-2600545	R2D air interface for Device 2b/C	LG Electronics

R1-2600659	Study on R2D signals, channels, waveform and procedures	NEC

R1-2600705	Discussion on A-IoT Air Interface for R2D	Panasonic

R1-2600743	Study on R2D aspects of air interface for Device 2b/C	Samsung

R1-2600815	On R2D design details for device 2b/C	Apple

R1-2600965	Discussion on R2D signals, channels, waveform and procedures	Sharp

R1-2600992	Discussion on R2D signals, channels, waveform and procedures	ETRI

R1-2601020	Discussion on R2D for R20 Ambient IoT	Lenovo

R1-2601074	R2D Design for Active AIoT Devices	InterDigital, Inc.

R1-2601123	R2D signals, channels, waveform and procedures	Sony

R1-2601167	Study on R2D design and procedures for Ambient IoT outdoor for active device	NTT DOCOMO, INC.

R1-2601260	Study of R2D designs for Device 2b/C	Qualcomm Incorporated

R1-2601292	Discussion on R2D signals, channels, waveform and procedures	Quectel

R1-2601300	Discussion on R2D signals, channels, waveform and procedures for Ambient IoT	China Telecom

R1-2601338	Discussion on R2D signals, channels, waveform and procedures for Ambient IoT	TCL

R1-2601368	On AIoT R2D design for Rel.20 Device 2b/C	Sequans Communications

R1-2601444	Discussion on R2D signals, channels, waveform and procedures	IIT Kanpur

D2R signals, channels, waveform and procedures

Including necessary and feasible change to D2R waveform and modulation, FEC, CRC and repetition, bandwidth, timing and Sync signals, multiplexing/multiple access, and scheduling.

R1-2600070	D2R Air Interface for Device 2b/C	FUTUREWEI

R1-2600089	Study on D2R signals, channels, waveform and procedures	Huawei, HiSilicon

R1-2600102	Discussion on D2R signals, channels, waveform and procedures for Ambient IoT	Spreadtrum, UNISOC

R1-2600180	Discussion on necessary and feasible change to D2R for Rel-20 A-IoT	OPPO

R1-2600211	D2R signals, channels, waveform, and procedures	Ericsson

R1-2600328	Study of D2R signals, channels, and waveform and procedure of A-IoT enhancement for device 2b/C	CATT

R1-2600361	Discussion on AIoT D2R signals, channels, and procedures	Tejas Network Limited

R1-2600369	AIoT D2R signals, channels, waveform and procedures	Nokia

R1-2600379	Discussion on D2R signals, channels, waveform and procedures	CMCC

R1-2600418	Discussion on D2R signals, channels, waveform and procedures for Device 2b/C	Xiaomi

R1-2600452	Discussion on D2R design for active Ambient IoT device	ZTE Corporation, Sanechips

R1-2600492	Discussion on D2R Aspects for R20 AIoT	vivo

R1-2600546	D2R air interface for Device 2b/C	LG Electronics

R1-2600660	Study on D2R signals, channels, waveform and procedures	NEC

R1-2600744	Study on D2R aspects of air interface for Device 2b/C	Samsung

R1-2600816	On D2R design details for device 2b/C	Apple

R1-2600942	Study on D2R signals, channels, waveform and procedures	HONOR

R1-2600959	Discussion on D2R transmissions for active ambient IoT	TCL

R1-2600966	Discussion on D2R signals, channels, waveform and procedures	Sharp

R1-2600968	Discussion on D2R signals, channels, waveform and procedures for Ambient IoT	China Telecom

R1-2601021	Discussion on D2R for R20 Ambient IoT	Lenovo

R1-2601075	D2R Design for Active AIoT Devices	InterDigital, Inc.

R1-2601168	Study on D2R design and procedures for Ambient IoT outdoor for active device	NTT DOCOMO, INC.

R1-2601261	Study of D2R designs for Device 2b/C	Qualcomm Incorporated

R1-2601299	Discussion on D2R multiplexing/multiple access for A-IoT active device	ASUSTeK

R1-2601386	Discussion on D2R signals, channels, waveform and procedures for Ambient IoT	China Telecom

R1-2601443	Discussion on D2R signals, channels, waveform and procedures	IIT Kanpur

R1-2601453	FL Summary #1 for 9.3.2.2. D2R signals, channels, waveform and procedures	Moderator (Qualcomm)

R1-2601454	FL Summary #2 for 9.3.2.2. D2R signals, channels, waveform and procedures	Moderator (Qualcomm)

R1-2601455	FL Summary #3 for 9.3.2.2. D2R signals, channels, waveform and procedures	Moderator (Qualcomm)

R1-2601456	FL Summary #4 for 9.3.2.2. D2R signals, channels, waveform and procedures	Moderator (Qualcomm)

R1-2601457	FL Summary #5 for 9.3.2.2. D2R signals, channels, waveform and procedures	Moderator (Qualcomm)

Other procedures

Including necessary and feasible change to other procedures such as for initial frequency acquisition and broadcast information acquisition, random access, timing offsets, DO-A, power control and Device localization.

R1-2600071	Other Air Interface Procedures	FUTUREWEI

R1-2600090	Study on other procedures for A-IoT	Huawei, HiSilicon

R1-2600103	Discussion on other procedure for Ambient IoT	Spreadtrum, UNISOC

R1-2600181	Discussion on other procedures for Rel-20 A-IoT	OPPO

R1-2600212	Other procedures of A-IoT	Ericsson

R1-2600329	Study of general procedures of A-IoT enhancement for device 2b/C	CATT

R1-2600362	Discussion on other procedures of AIoT	Tejas Network Limited

R1-2600370	Other procedures for AIoT	Nokia

R1-2600380	Discussion on other procedures	CMCC

R1-2600419	Discussion on other procedures for Device 2b/C	Xiaomi

R1-2600453	Discussion on other procedures for active Ambient IoT device	ZTE Corporation, Sanechips

R1-2600493	Discussion on Other Procedures for R20 AIoT	vivo

R1-2600547	Other procedures for Device 2b/C	LG Electronics

R1-2600548	FL summary #1 for 9.3.2.3 “Other procedures for Device 2b/C”	Moderator (LG Electronics)

R1-2600549	FL summary #2 for 9.3.2.3 “Other procedures for Device 2b/C”	Moderator (LG Electronics)

R1-2600550	FL summary #3 for 9.3.2.3 “Other procedures for Device 2b/C”	Moderator (LG Electronics)

R1-2600551	FL summary #4 for 9.3.2.3 “Other procedures for Device 2b/C”	Moderator (LG Electronics)

R1-2600552	FL summary #5 for 9.3.2.3 “Other procedures for Device 2b/C”	Moderator (LG Electronics)

R1-2600661	Study on other procedures for Device 2b and C	NEC

R1-2600683	Discussion on other procedures for Ambient IoT	China Telecom

R1-2600713	Discussion on A-IoT other procedures	Panasonic

R1-2600745	Study on other procedures of air interface for Device 2b/C	Samsung

R1-2600817	On other procedures for device 2b/C	Apple

R1-2600967	Discussion on other procedures	Sharp

R1-2600993	Discussion on other procedures for A-IoT	ETRI

R1-2601022	Discussion on other procedures for R20 Ambient IoT	Lenovo

R1-2601076	Procedures for Active AIoT Devices	InterDigital, Inc.

R1-2601124	System information and DO-A aspects for Ambient IoT outdoor devices	Sony

R1-2601169	Study on other procedures for Ambient IoT outdoor for active device	NTT DOCOMO, INC.

R1-2601262	Study of other procedures for Device 2b/C	Qualcomm Incorporated

R1-2601293	Discussion on other procedures for Device 2b/C	Quectel

R1-2601301	Discussion on procedures for A-IoT active device	ASUSTeK

R1-2601341	Discussion on other procedures for Ambient IoT	TCL

R1-2601347	Discussion on other procedures for Device 2b/C	KT Corp.

R1-2601442	Discussion on other aspects of Rel-20 AIoT	IIT Kanpur

R1-2601450	Discussion on other procedures for R20 A-IoT	Fraunhofer HHI, Fraunhofer IIS

Coverage Enhancement Phase 3

Please refer to RP-252824 for detailed scope of the WI.

[124-R20-CE] Email discussion on Rel-20 CE– Hang (China Telecom)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 9.4	Ad-Hoc Chair (NTT DOCOMO, INC.)

Coverage enhancement

Including PRACH coverage enhancements, PUSCH repetition scheduled by DCI 0_0 with C-RNTI and Extending pi/2-BPSK to more MCS entries.

R1-2600083	Coverage enhancements for NR Phase 3	Huawei, HiSilicon

R1-2600104	Discussion on NR Coverage enhancement	Spreadtrum, UNISOC

R1-2600129	Coverage enhancements for NR Phase 3	Nokia

R1-2600182	Discussion on further enhancement for coverage enhancement	OPPO

R1-2600238	Discussion on coverage enhancement	LG Electronics

R1-2600258	Discussion on coverage enhancement	ZTE Corporation, Sanechips

R1-2600330	Discussion on coverage enhancement	CATT

R1-2600344	Coverage enhancements for NR Phase 3	Tejas Network Limited

R1-2600420	Discussion on coverage enhancement	Xiaomi

R1-2600494	Further discussions on NR phase 3 coverage enhancements	vivo

R1-2600562	Coverage enhancements	Lenovo

R1-2600580	Coverage enhancement for NR Phase 3	InterDigital, Inc.

R1-2600684	Discussion on NR coverage enhancements Phase 3	China Telecom

R1-2600685	FL's summary #1 on NR coverage enhancements Phase 3	Moderator (China Telecom)

R1-2600686	FL's summary #2 on NR coverage enhancements Phase 3	Moderator (China Telecom)

R1-2600687	FL's summary #3 on NR coverage enhancements Phase 3	Moderator (China Telecom)

R1-2600688	FL's summary #4 on NR coverage enhancements Phase 3	Moderator (China Telecom)

R1-2600746	Discussion on Coverage Enhancement	Samsung

R1-2600818	Discussion on coverage enhancements for NR Phase 3	Apple

R1-2600882	Discussion on coverage enhancement	Transsion Holdings

R1-2600936	NR Coverage Enhancement Phase 3	Panasonic

R1-2600983	Discussions on further coverage enhancement for NR	Sharp

R1-2600994	Discussion on coverage enhancements	ETRI

R1-2601032	Discussion on Rel-20 Coverage Enhancement	Ericsson

R1-2601102	Views on Coverage Enhancement Phase 3	Ofinno

R1-2601170	Discussions on coverage enhancement	NTT DOCOMO, INC

R1-2601202	Discussion on coverage enhancement	DENSO CORPORATION

R1-2601237	Discussion on NR Coverage enhancement Phase 3	ITRI, Acer Incorporated

R1-2601263	Coverage enhancement Phase 3	Qualcomm Incorporated

R1-2601296	Discussion on NR coverage enhancements Phase 3	KT Corp.

R1-2601349	Discussion on coverage enhancement	ASUSTeK

R1-2601389	Views on NR Coverage Enhancements	CEWiT

Study on Integrated Sensing And Communication (ISAC) for NR

Please refer to RP-253246 for detailed scope of the SI.

[124-R20-ISAC] Email discussion on Rel-20 ISAC – Yingyang (Xiaomi)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 9.5	Ad-Hoc Chair (NTT DOCOMO, INC.)

Evaluation assumptions and performance evaluation

Including study of metrics, measurements, and relevant measurement quantization for UAV use case.

R1-2600081	Performance metric, methodologies, and initial evaluation results for ISAC	Huawei, HiSilicon

R1-2600105	Discussion on evaluation assumptions and performance evaluations on ISAC	Spreadtrum, UNISOC

R1-2600183	Discussion of ISAC evaluation in 5GA	OPPO

R1-2600331	Discussion on evaluation methodology and evaluation results for R20 ISAC for NR	CATT, CICTCI

R1-2600363	Evaluation assumptions and performance evaluation for ISAC	EURECOM

R1-2600381	Discussion on sensing measurement and evaluation result	CMCC

R1-2600446	Discussion on performance evaluation for ISAC	Xiaomi

R1-2600495	Evaluation methodology and performance evaluation for 5G-A ISAC	vivo

R1-2600538	Discussion on evaluation assumptions and performance evaluation for NR ISAC	Panasonic

R1-2600574	Evaluation assumptions and performance evaluation of ISAC for NR	InterDigital, Inc.

R1-2600620	Evaluation assumptions and performance evaluations for ISAC NR	Tiami Networks

R1-2600622	Performance evaluations of ISAC for NR	Nokia

R1-2600689	Discussion on ISAC evaluation assumptions and performance evaluation	China Telecom

R1-2600708	Discussion on ISAC for NR	Ericsson

R1-2600747	Discussion on ISAC Evaluation assumptions and performance evaluation	Samsung

R1-2600792	Discussion on ISAC performance evaluations	T-Mobile USA Inc.

R1-2600819	On Rel-20 Integrated Sensing And Communication (ISAC) for NR	Apple

R1-2600846	Discussion on ISAC Performance Evaluation	NIST

R1-2600902	Discussion on ISAC evaluation assumptions and performance evaluation	MediaTek Inc.

R1-2600973	Discussion on 5G-A ISAC evaluation	ZTE Corporation, Sanechips, Shanghai Jiao Tong University, Pengcheng Laboratory

R1-2600995	Discussion on evaluation assumptions and performance evaluation for NR ISAC	ETRI

R1-2601031	Discussion on NR ISAC evalution assumption and performance evaluation	LG Electronics

R1-2601055	On ISAC performance evaluations and assumptions	Lenovo

R1-2601125	On 5G NR ISAC evaluation assumptions and performance evaluation	Sony

R1-2601171	Evaluation assumptions and performance evaluation for ISAC	NTT DOCOMO, INC

R1-2601234	Discussion on evaluation assumptions and performance evaluation for NR ISAC	Panasonic

R1-2601264	Evaluation Assumptions and performance evaluation for UAV gNB-monostatic sensing	Qualcomm Incorporated

R1-2601358	Discussion on Performance Evaluations for Rel-20 ISAC	Google Korea LLC

R1-2601377	Evaluation results of NR ISAC	Moderator (Xiaomi)

R1-2601378	Details on evaluation of NR ISAC reported by companies	Moderator (Xiaomi)

R1-2601379	Summary on [Post-123-R20-ISAC-evaluation]	Moderator (Xiaomi)

R1-2601380	Summary #1 on evaluations for NR ISAC	Moderator (Xiaomi)

R1-2601381	Summary #2 on evaluations for NR ISAC	Moderator (Xiaomi)

R1-2601382	Summary #3 on evaluations for NR ISAC	Moderator (Xiaomi)

R1-2601383	Summary #4 on evaluations for NR ISAC	Moderator (Xiaomi)

R1-2601384	Summary #5 on evaluations for NR ISAC	Moderator (Xiaomi)

R1-2601385	Summary #6 on evaluations for NR ISAC	Moderator (Xiaomi)

R1-2601390	Discussion on ISAC evaluation assumptions and performance evaluation for 5G NR	CEWiT

R1-2601407	Discussion and Evaluations for NR ISAC	VIAVI, CMCC

Non-Terrestrial Networks (NTN) for NR Phase 4

Please refer to RP-253137 for detailed scope of the SI for NR-NTN Phase 4.

R1-2600253	Work plan for NR NTN Phase 4	Moderator (THALES)

R1-2601321	Draft TR 38.742 Study on GNSS (Global Navigation Satellite System) resilient NR-NTN (Non-Terrestrial Networks) operation	Rapporteur (Thales)

[124-R20-NR-NTN] Email discussion on Rel-20 NR-NTN – Mohamed (Thales)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 9.6	Ad-Hoc Chair (Ericsson)

NR-NTN GNSS resilience

R1-2600065	Discussion on Rel-20 GNSS resilient NR NTN operation	FUTUREWEI

R1-2600077	GNSS resilience for NR-NTN	Huawei, HiSilicon

R1-2600106	Discussion on NR-NTN GNSS resilience	Spreadtrum, UNISOC

R1-2600184	Discussion on NR-NTN GNSS resilience	OPPO

R1-2600237	On NR-NTN GNSS resilience	Ericsson

R1-2600248	Considerations on GNSS resilient NR-NTN operation	THALES

R1-2600249	FL Summary #1: Study on GNSS resilient NR-NTN operation	Moderator (THALES)

R1-2600250	FL Summary #2: Study on GNSS resilient NR-NTN operation	Moderator (THALES)

R1-2600251	FL Summary #3: Study on GNSS resilient NR-NTN operation	Moderator (THALES)

R1-2600252	FL Summary #4: Study on GNSS resilient NR-NTN operation	Moderator (THALES)

R1-2600259	Discussion on NR-NTN GNSS resilience	ZTE Corporation, Sanechips

R1-2600332	Discussion on NR-NTN GNSS resilience	CATT

R1-2600341	GNSS Resilient operation for NR-NTN - 5G Adv	Tejas Network Limited

R1-2600382	Discussion on NR-NTN GNSS resilience	CMCC

R1-2600421	Further discussion on NR NTN GNSS resilience	Xiaomi

R1-2600449	Discussion on the GNSS resilient NR-NTN operation	TCL

R1-2600496	Discussions on NR-NTN GNSS resilience	vivo

R1-2600524	Discussion on NR-NTN GNSS resilience	Fraunhofer IIS, Fraunhofer HHI

R1-2600577	IMU Views on NR-NTN GNSS Resilience	IMU

R1-2600581	NR-NTN GNSS resilience	InterDigital, Inc.

R1-2600619	Discussion on GNSS resilient NR-NTN operation	TOYOTA Info Technology Center

R1-2600677	Discussion on NR-NTN GNSS resilience	NEC

R1-2600690	Discussion on NR-NTN GNSS resilience	China Telecom

R1-2600748	Discussion on NR-NTN GNSS resilience	Samsung

R1-2600784	GNSS-resilient NR-NTN operation	ST Engineering iDirect

R1-2600794	Considerations for GNSS-resilient NR-NTN operation	ESA, Thales

R1-2600806	Discussion on NR NTN GNSS Resilience	Amazon Web Services

R1-2600820	Discussion on NR-NTN GNSS resilience	Apple

R1-2600858	NR NTN GNSS resilient operation	Sharp

R1-2600903	Discussion on NR-NTN GNSS resilience	MediaTek Inc.

R1-2600943	Discussion on NR-NTN GNSS resilience	HONOR

R1-2600962	Discussion on GNSS resilient NR-NTN operation	LG Electronics

R1-2600971	Discussion on GNSS resilient NR-NTN	Panasonic

R1-2600996	Discussion on NR-NTN GNSS resilient operations	ETRI

R1-2601041	Location uncertainty reduction and mitigation techniques	Eutelsat Group

R1-2601058	Discussion on GNSS resilient NR-NTN operation	Lenovo

R1-2601060	Discussion on GNSS resilient operation for NR over NTN	Nokia

R1-2601077	Discussion on NR-NTN GNSS resilience	Airbus

R1-2601090	Discussion on NR-NTN GNSS resilience	Ofinno

R1-2601126	On Solutions for NR-NTN GNSS Resilience	Sony

R1-2601172	Discussion on NR-NTN GNSS resilience	NTT DOCOMO, INC.

R1-2601231	Discussion of Using DL Timestamps for Initial Access	Johns Hopkins University APL

R1-2601265	NR NTN GNSS resilience	Qualcomm Incorporated

R1-2601318	Discussion on NR-NTN GNSS resilience	Google Korea LLC

R1-2601322	Discussion on NR-NTN GNSS resilience	CAICT

R1-2601391	Discussion on GNSS Resilient Operation for NR NTN	CEWiT

R1-2601410	Discussion on GNSS resilience for NR-NTN	CSCN

Non-Terrestrial Networks (NTN) for Internet of Things (IoT) Phase 4

Please refer to RP-251867 for detailed RAN1 scope of the WI.

[124-R20-IoT-NTN] Email discussion on Rel-20 IoT-NTN – Mohamed (Shiqi)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 9.7	Ad-Hoc Chair (Ericsson)

Semi-persistent scheduling for DL/UL data transmission for voice packets

R1-2600078	Disccussion on the DL/UL SPS for NB-IoT-NTN to support VoIP over GSO	Huawei, HiSilicon

R1-2600107	Discussion on semi-persistent scheduling for data transmission for voice packets	Spreadtrum, UNISOC

R1-2600185	Discussion on SPS for DL/UL data transmission for voice packets	OPPO

R1-2600260	Discussion on SPS for IoT-NTN	ZTE Corporation, Sanechips

R1-2600333	Semi-persistent scheduling for DL/UL data transmission for voice packets	CATT

R1-2600422	Discussion on semi-persistent scheduling for voice over IoT-NTN	Xiaomi

R1-2600497	Discussions on Semi-persistent scheduling for DL/UL data transmission for voice packets	vivo

R1-2600678	Discussion on Semi-persistent scheduling for DLUL data transmission for voice packets	NEC

R1-2600749	Discussion on Semi-persistent scheduling for DL/UL data transmission for voice packets	Samsung

R1-2600821	Discussion on semi-persistent scheduling for IoT-NTN voice packets	Apple

R1-2600857	Semi-persistent scheduling for UL/DL data transmission for voice packets	TCL

R1-2600859	SPS support for NTN IoT voice traffic	Sharp

R1-2600904	Discussion on Semi-persistent scheduling for DL/UL data transmission for voice packets	MediaTek Inc.

R1-2600963	Discussion on SPS for DL/UL data transmission for voice packets	LG Electronics

R1-2600997	Discussion on SPS for the support of voice over NB-IoT NTN	ETRI

R1-2601029	Discussion on SPS for data transmission for voice packets	Nokia

R1-2601066	Support of Voice-over-GEO for NB-IoT NTN	Ericsson

R1-2601266	SPS for IoT NTN	Qualcomm Incorporated

R1-2601433	Discussion on SPS for DL/UL data transmission for voice packets	Google Korea LLC

Rel-20 Study of 6GR

Please refer to RP-253876 for the scope of the SI. The maximum number of contributions per company/organization/university is limited to 1 per agenda item unless stated otherwise.

Note 1: Additional more guidance/information, please refer to R1-2600002 (Highlights from RAN#110)

Note 2: All AI/ML labelled proposals need to be discussed together with relevant non-AI/ML labelled mechanisms under individual agenda, respectively, for justifying/verifying respective performance and gain, so AI/ML labelled proposals will be treated when relevant non-AI/ML labelled proposals are discussed under individual agenda, unless stated otherwise.

Note 3： EE labelled proposals are discussed under individual agenda, unless stated otherwise.

Note 4: All contributions should only be input into an agenda without any sub-agenda, i.e., we can't input contribution under AI 10.5.x if it has sub-agenda AI 10.5.x.1/2/3, while we can input contributions under AI 10.5.x if AI 10.5.x is the lowest level of agenda.

R1-2601173	Workplan for Rel-20 Study of 6GR	NTT DOCOMO, China Mobile, AT&T, Vodafone

R1-2601174	TR 38.760-1 “Study on 6G Radio RAN1 aspects” v0.1.0	NTT DOCOMO, INC. (TR edtor)

Evaluation assumptions for 6GR air interface

Update of traffic models and evaluation models that can be commonly used for evaluating technology proposals.

[124-R20-6GR-Evaluation] Email discussion on Rel-20 6GR-Evaluation – Jinhuan (Huawei)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600026	On remaining aspects of 6GR evaluations	Nokia

R1-2600137	Evaluation assumptions for 6GR air interface	Huawei, HiSilicon

R1-2600187	Evaluation assumption for 6GR air interface	OPPO

R1-2600227	Discussion on evaluation assumptions for 6GR air interface	ZTE Corporation, Sanechips

R1-2600293	Further discussion on evaluation assumptions for 6GR air interface	CATT

R1-2600383	Discussion on evaluation assumptions for 6GR air interface	CMCC

R1-2600423	Discussion on evaluation assumptions for 6GR air interface	Xiaomi

R1-2600498	Remaining issues on evaluation assumptions and traffic models for 6GR	vivo

R1-2600526	Evaluation assumptions for 6GR air interface	InterDigital, Inc.

R1-2600591	Traffic modelling for 6GR air interface	NVIDIA

R1-2600691	Discussion on evaluation assumptions for haptic traffic models	China Telecom

R1-2600750	Evaluation assumptions for 6GR	Samsung

R1-2600790	Fixed Wireless Access Scenarios	T-Mobile USA, Ericsson, MediaTek, Nokia, Verizon

R1-2600822	On evaluation assumptions for 6GR air interface	Apple

R1-2600901	Evaluation assumptions for 6GR air interface	MediaTek Inc.

R1-2600913	Evaluation assumptions for 6GR	Sharp

R1-2600933	Evaluation assumptions for 6GR	Intel Corporation

R1-2600998	Discussion on evaluation assumptions for 6GR air interface	ETRI

R1-2601045	Evaluation assumptions for 6GR	Ericsson

R1-2601091	Discussion on Evaluation assumptions for 6GR air interface	Ofinno

R1-2601175	Discussion on Evaluation assumptions for 6GR air interface	NTT DOCOMO, INC.

R1-2601267	Evaluation assumptions for 6GR air interface	Qualcomm Incorporated

R1-2601356	Evaluation Assumptions for 6GR Air Interface	Tejas Network Limited, CEWiT, IIT Madras

R1-2601369	On Evaluation Assumptions for the 6GR air interface	Google Korea LLC

R1-2601414	FLS#1 on evaluation assumptions for 6GR air interface	Moderator (Huawei)

R1-2601415	FLS#2 on evaluation assumptions for 6GR air interface	Moderator (Huawei)

R1-2601416	FLS#3 on evaluation assumptions for 6GR air interface	Moderator (Huawei)

R1-2601436	Evaluation assumptions for 6GR air interface	Sony

Waveform for 6GR air interface

Waveform

Note 1: Including proposals for improving spectrum efficiency, power efficiency, coexistence and coverage, etc.

[124-R20-6GR-Waveform] Email discussion on Rel-20 6GR-Waveform – Klaus (Nokia)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 10.2.1	Ad-Hoc Chair (NTT DOCOMO, INC.)

R1-2600027	On remaining aspects of waveform for 6GR	Nokia

R1-2600138	Waveform for 6GR air interface	Huawei, HiSilicon

R1-2600188	On waveform enhancements/additions for 6G Radio	OPPO

R1-2600239	Discussion on waveform for 6GR	LG Electronics

R1-2600255	Discussion on waveform for 6GR air interface	THALES

R1-2600261	Views on the waveform for 6G	ZTE Corporation, Sanechips

R1-2600295	Discussions on waveform for 6GR	CATT

R1-2600366	Waveform design for 6G air interface	Tejas Network Limited

R1-2600384	Discussion on the waveform design for 6G radio	CMCC

R1-2600424	Further discussion on 6GR waveform	Xiaomi

R1-2600499	Discussion on Waveform for 6GR air interface	vivo

R1-2600572	Discussion on Waveform for 6GR Air Interface	IMU, Turkcell

R1-2600584	Discussion on 6G Waveform	NEC

R1-2600612	Waveform for 6GR Air Interface	Cohere Technologies

R1-2600627	Waveform for 6GR Air Interface	Google

R1-2600716	Discussions on 6G Waveforms	Lekha Wireless Solutions

R1-2600751	Discussion on waveform for 6GR	Samsung

R1-2600786	Feature Lead summary #1 on 6G waveform	Nokia

R1-2600787	Feature Lead summary #2 on 6G waveform	Nokia

R1-2600788	Feature Lead summary #3 on 6G waveform	Nokia

R1-2600789	Feature Lead summary #4 on 6G waveform	Nokia

R1-2600801	Waveform for 6GR air interface	InterDigital, Inc.

R1-2600823	On Waveforms for 6GR air interface	Apple

R1-2600909	Waveform for 6GR air interface	MediaTek Inc.

R1-2600914	Study on waveform for 6GR	Sharp

R1-2600999	Discussion on 6GR waveform	ETRI, University of Surrey

R1-2601019	Discussion on New Waveform for 6GR Air Interface	Shanghai Jiao Tong University, NERC-DTV

R1-2601047	Discussion on 6GR waveform design	Hanbat National University

R1-2601080	Discussion on Waveform for 6GR	Lenovo

R1-2601092	Discussion on waveform for 6GR air interface	Ofinno

R1-2601110	New waveform for 6GR air interface	NICT

R1-2601113	Discussion on waveform for 6GR air interface	Panasonic

R1-2601127	Waveforms for 6GR	Sony

R1-2601156	On waveform for 6GR	Ericsson

R1-2601176	Discussion on Waveform	NTT DOCOMO, INC

R1-2601212	Discussion on waveform for 6GR air interface	Pengcheng Laboratory

R1-2601268	Waveforms for 6GR	Qualcomm Incorporated

R1-2601294	Discussion on waveform for 6G air interface	Quectel

R1-2601354	Discussion on waveform for 6GR air interface	KDDI Corporation

R1-2601366	Enhancements for pi/2-BPSK DFT-s-OFDM: Overlapped Allocations	Wisig Networks, IITH

Channel coding and modulation for 6GR interface

Note 1: Including metrics/criteria that can be used for evaluating technology proposals and for down selecting proposals

Channel coding

[124-R20-6GR-Channel coding] Email discussion on Rel-20 6GR- Channel coding and Modulation – Mengzhu (ZTE)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 10.3.1	Ad-Hoc Chair (Ericsson)

R1-2600028	On remaining aspects of channel coding in 6GR	Nokia

R1-2600108	Discussion on channel coding for 6GR	Spreadtrum, UNISOC

R1-2600139	Channel coding for 6GR air interface	Huawei, HiSilicon

R1-2600189	Discussion on 6G channel coding	OPPO

R1-2600296	Channel coding for 6G control channel and data channel	CATT

R1-2600385	Discussion on channel coding for 6GR interface	CMCC

R1-2600425	Further discussion on 6GR channel coding	Xiaomi

R1-2600447	Complexity Metric for LDPC codes	Spark NZ Ltd

R1-2600454	Discussion on channel coding for 6GR	ZTE Corporation, Sanechips

R1-2600500	Discussion on Channel Coding for 6GR air interface	vivo

R1-2600522	Discussion on Channel Coding for Small Block Lengths	EURECOM

R1-2600537	Channel coding study for 6GR Discussion and Decision	LG Electronics

R1-2600566	Discussion on Channel Coding for 6GR air interface	Shanghai Jiao Tong University, NERC-DTV

R1-2600583	Discussion on Channel Coding Aspects for 6G	NEC

R1-2600715	Channel coding enhancements for 6GR air interface	InterDigital, Inc.

R1-2600752	Discussion on channel coding for 6GR	Samsung

R1-2600802	Channel coding for 6GR air interface	NVIDIA

R1-2600824	Considerations of 6GR channel coding	Apple

R1-2600868	Discussion on channel coding for 6GR	Fujitsu

R1-2600907	Channel coding for 6GR	Ericsson

R1-2600935	LDPC extension for data rate beyond NR range	Intel Corporation

R1-2600937	Channel coding for 6GR air interface	MediaTek Inc.

R1-2600969	On 6GR channel coding	KT Corp.

R1-2601000	Discussion on 6GR channel coding	ETRI, ESA, Thales

R1-2601024	LDPC decoder throughput and chip area	AccelerComm, Orange, Vodafone

R1-2601025	LDPC decoder throughput and chip area	AccelerComm, Orange, Vodafone

R1-2601037	Channel coding for 6GR	C-DOT

R1-2601056	6G Channel Coding for Control Channels	Lenovo

R1-2601057	Discussion on Channel Coding for 6G	Lenovo

R1-2601085	Views on 6GR LDPC code	Verizon, CMCC, China Telecom, China Unicom, Samsung, ZTE, Sanechips, Apple, Qualcomm, MediaTek, Meta

R1-2601144	Discussion on channel coding	Panasonic

R1-2601177	Discussion on 6GR channel coding	NTT DOCOMO, INC.

R1-2601203	Views on LDPC coding and decoding enhancements for 6GR	Jio Platforms

R1-2601217	Views on Channel Coding for 6GR	AT&T

R1-2601269	Channel coding for 6GR	Qualcomm Incorporated

R1-2601306	Channel coding study for 6GR	LG Electronics Inc.

R1-2601319	Discussion on channel coding for 6GR air interface	Google Korea LLC

R1-2601362	On channel coding aspects	Vodafone, Orange, AccelerComm, Deutsche Telekom, AT&T, British Telecom

R1-2601372	Channel coding aspects for 6GR	Fraunhofer IIS, Fraunhofer HHI

R1-2601413	Discussion on channel coding for 6GR air interface	CSCN

R1-2601423	Views on LDPC coding and decoding enhancements for 6GR	Jio Platforms

R1-2601452	Discussion on channel coding for 6GR air interface	CSCN

Modulation, Joint channel coding and modulation

Note 1: Including different designs of constellation, and mechanisms for MCS indication, where modulation mechanisms may assume different evaluation assumptions.

[124-R20-6GR-Modulation, joint channel coding and modulation] Email discussion on Rel-20 6GR-Modulation,joint channel coding and modulation –Jing (Qualcomm)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 10.3.2	Ad-Hoc Chair (Ericsson)

R1-2600029	On remaining aspects of modulation in 6GR	Nokia

R1-2600109	Discussion on modulation, joint channel coding and modulation for 6GR	Spreadtrum, UNISOC

R1-2600140	Channel coding for data channel	Huawei, HiSilicon

R1-2600141	Modulation for 6GR air interface	Huawei, HiSilicon

R1-2600190	Discussion on modulation, joint channel coding and modulation for 6GR	OPPO

R1-2600297	Modulation and Joint channel coding and modulation for 6G network	CATT

R1-2600335	Discussion on modulation for 6GR	LG Electronics

R1-2600342	Discussion on modulation for 6GR	Tejas Network Limited

R1-2600386	Discussion on modulation schemes for 6GR interface	CMCC

R1-2600426	Discussion on modulation for 6GR air interface	Xiaomi

R1-2600455	Discussion on modulation for 6GR	ZTE Corporation, Sanechips

R1-2600501	Discussion on Modulation for 6GR air interface	vivo

R1-2600564	IMU Views on Modulation for 6GR Air Interface	IMU

R1-2600585	Discussion on Modulation Aspects for 6G	NEC

R1-2600753	Discussion on modulation for 6GR	Samsung

R1-2600774	Modulation, joint channel coding and modulation for 6GR air interface	InterDigital, Inc.

R1-2600791	Modulation for 6GR air interface	Ericsson

R1-2600799	Discussion on 6GR modulation	Lenovo

R1-2600825	On modulation for 6G air interface	Apple

R1-2600910	Modulation for 6GR air interface	MediaTek Inc.

R1-2601001	Discussion on 6GR modulation	ETRI

R1-2601114	Discussion on modulation for 6GR air interface	Panasonic

R1-2601128	Discussions on joint channel coding and modulation by DBICM for 6GR	Sony

R1-2601178	Discussion on modulation	NTT DOCOMO, INC

R1-2601218	Views on Modulation for 6GR	AT&T

R1-2601270	Modulation, joint channel coding and modulation	Qualcomm Incorporated

Energy efficiency

Update of evaluation assumptions for power consumption.

[124-R20-6GR-Energy efficiency] Email discussion on Rel-20 6GR- Energy efficiency – Magnus, Weide (Ericsson, MTK)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600030	On remaining aspects of EE evaluations	Nokia

R1-2600049	6G Energy Efficiency	FUTUREWEI

R1-2600110	Discussion on energy efficiency	Spreadtrum, UNISOC

R1-2600142	Evaluation assumptions on energy efficiency	Huawei, HiSilicon

R1-2600197	Discussion on evaluations for 6G Energy Efficiency	OPPO

R1-2600294	Discussion on evaluation methodology and assumptions for energy efficiency	CATT

R1-2600358	Energy Efficiency in 6G	Tejas Network Limited

R1-2600387	Discussion on Energy Efficiency of 6GR interface	CMCC

R1-2600427	Discussion on energy efficiency for 6GR	Xiaomi

R1-2600456	Discussion on energy efficiency for 6GR	ZTE Corporation, Sanechips

R1-2600502	Remaining issues on evaluation methodologies for 6GR power consumption	vivo

R1-2600530	6GR Energy efficiency	InterDigital, Inc.

R1-2600553	Discussion on energy efficiency for 6GR	LG Electronics

R1-2600600	Views on 6GR Energy Efficiency	Ofinno

R1-2600754	Discussion on energy efficiency for 6GR	Samsung

R1-2600826	On remaining issues for energy efficiency evaluation assumptions	Apple

R1-2600960	6GR energy efficiency	Ericsson

R1-2601106	Discussion on 6GR Energy Efficiency	Lenovo

R1-2601179	Discussion on Energy Efficiency for 6GR	NTT DOCOMO, INC

R1-2601205	Discussion on 6G energy efficiency	Google

R1-2601219	Views on Energy Efficiency for 6GR	AT&T

R1-2601240	Evaluation assumptions for 6GR energy efficiency	MediaTek Inc.

R1-2601271	Energy Efficiency in 6GR	Qualcomm Incorporated

R1-2601315	Views on energy efficiency for 6GR	Jio Platforms

R1-2601323	Discussion on energy efficiency and energy saving	CAICT

R1-2601364	On 6GR energy efficiency power model updates for SBFD	Vodafone, Telecom Italia, Deutsche Telekom

R1-2601392	Discussion on Energy Efficiency	CEWiT

Multi-antenna system

Note 1: Including proposals for both Sing-TRP and Multi-TRP

General aspects and frameworks

Note 1: Contributions under this agenda (AI 10.5.0) for identifying candidates and frameworks of duplexing types, for spectrum utilization, for aggregation, for TN&NTN, scalability related aspects, and for targeting coverage, frame structure, the maximum bandwidth at network side and UE side, etc.

[124-R20-6GR-General, Synchronization and Beam Measurement] Email discussion on Rel-20 6GR- General aspects of initial access and mobility – Xinghua, Yanping (Huawei, Xiaomi)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600031	Overall aspects of the 6GR multi-antenna system	Nokia

R1-2600050	6G General Aspects and Frameworks	FUTUREWEI

R1-2600111	Discussion on 6GR general aspects and frameworks	Spreadtrum, UNISOC

R1-2600143	Discussion on general aspects and framework	Huawei, HiSilicon

R1-2600186	General aspects and frameworks for 6GR multi-antenna system	OPPO

R1-2600262	Views on general aspects and frameworks	ZTE Corporation, Sanechips

R1-2600298	Discussion on general aspects and frameworks for 6G	CATT, CICTCI

R1-2600336	Views on General aspects and Frame Structure	Tejas Network Limited

R1-2600388	General aspects and frameworks of 6GR	CMCC

R1-2600428	Discussion on 6G general aspects and frameworks	Xiaomi

R1-2600461	Overview on general aspects and frameworks	TCL

R1-2600503	Discussion on 6GR general aspects and frameworks	vivo

R1-2600536	Discussion on general aspects and frameworks for 6GR	LG Electronics

R1-2600563	General aspects and frameworks	Lenovo

R1-2600573	6G general aspects and frameworks	Ericsson

R1-2600588	MIMO frameworks for 6GR Air Interface	National Spectrum Consortium

R1-2600593	General aspects and frameworks for multi-antenna system	NVIDIA

R1-2600601	Views on General aspects and frameworks	Ofinno

R1-2600645	General aspect and frameworks of 6GR air interface	Panasonic

R1-2600676	Discussion on general aspects and frameworks	NEC

R1-2600692	Discussion on 6G general aspects and frameworks	China Telecom

R1-2600755	Discussion on General aspects and frameworks for 6GR	Samsung

R1-2600809	General aspects and framework for 6GR	InterDigital, Inc.

R1-2600827	On general aspects and frameworks	Apple

R1-2600869	Discussion on 6GR duplex types and frame structure	Fujitsu

R1-2600893	6G general aspects and frameworks	MediaTek Inc.

R1-2600915	General aspects and frameworks for 6GR	Sharp

R1-2600944	Discussion on general aspects and frameworks of 6GR	HONOR

R1-2600950	General aspects and frameworks on 6G spectrum utilization	Pengcheng Laboratory

R1-2600985	Discussion on cell-free design of 6GR MIMO	PML

R1-2601002	Discussion on general aspects and frameworks for 6GR	ETRI

R1-2601070	6GR General Aspects and Frameworks	Fraunhofer IIS, Fraunhofer HHI

R1-2601107	Considerations for 6GR General Aspects and Frameworks	Semtech Neuchatel SA

R1-2601129	6GR general aspects and framework	Sony

R1-2601147	Discussion on 6G general aspects and frameworks	Kyocera

R1-2601155	Discussions on 6G Multi-antenna System Design	CAICT

R1-2601180	Discussion on 6GR general aspects and frameworks	NTT DOCOMO, INC

R1-2601181	Summary on [Post-123-R20-6GR-Overall]	Moderator (NTT DOCOMO)

R1-2601220	6GR General Aspects and Framework	AT&T

R1-2601272	General aspects and framework	Qualcomm Incorporated

R1-2601297	Discussion on 6GR general aspects and frameworks	KT Corp.

R1-2601334	Discussion on the General Aspects and Framework of 6GR Multi-Antenna System	Rakuten Mobile, Inc

R1-2601353	Discussion on general aspects and frameworks	KDDI Corporation

R1-2601355	Considerations on general aspects and frameworks for 6GR air interface	ITL

R1-2601360	On 6GR coverage target	Vodafone, Deutsche Telekom, Orange, Bouygues Telecom, Telecom Italia, British Telecom

R1-2601371	6GR General aspects and frameworks	Google Korea LLC

R1-2601393	Views on 6GR General aspects and frameworks	CEWiT

R1-2601418	Discussion on General aspects and Frameworks for 6G Radio	WILUS Inc.

Initial access and mobility

Note 1: Targeting unified design under Sing-TRP and Multi-TRP for all candidate duplexing types, for spectrum utilization, for aggregation, for TN&NTN, scalability related aspects, maximum bandwidth at network side and UE side, and for targeting coverage, if applicable.

Synchronization acquisition and beam measurement

Note 1: Including synchronization signal/channel design (e.g., SSB), and transmission, and other design for facilitating synchronization acquisition, e.g., jointly with CSI-RS or other reference signal, On-demand sync signal(s), SIB/Paging transmission, measurement for mobility.

R1-2600032	On synchronization acquisition and beam measurement	Nokia

R1-2600051	6G Synchronization Acquisition and Beam Measurement	FUTUREWEI

R1-2600112	Discussion on 6GR synchronization acquisition and beam measurement	Spreadtrum, UNISOC

R1-2600144	Synchronization acquisition and beam measurement for 6GR	Huawei, Hisilicon

R1-2600198	Discussion on Synchronization acquisition and beam measurement for 6GR	OPPO

R1-2600240	Discussion on Synchronization acquisition and beam measurement for 6GR	LG Electronics

R1-2600263	Discussion on Synchronization acquisition and beam measurement	ZTE Corporation, Sanechips

R1-2600279	Discussion on synchronization acquisition and beam measurement	TCL

R1-2600299	Discussion on synchronization acquisition and beam measurement	CATT, CICTCI

R1-2600352	Synchronization acquisition and beam measurement	Tejas Network Limited

R1-2600389	Discussion on synchronization acquisition and beam measurement	CMCC

R1-2600429	Discussion on synchronization acquisition and beam measurement for 6GR	Xiaomi

R1-2600460	Discussion on Synchronization acquisition and beam measurement for 6GR	BYD

R1-2600467	Synchronization acquisition and beam measurement	Ericsson

R1-2600504	Discussions on 6GR synchronization acquisition and beam measurement	vivo

R1-2600527	Synchronization acquisition and beam measurement	InterDigital, Inc.

R1-2600567	IMU Views on 6GR SSB Design	IMU

R1-2600602	Initial views on 6GR Synchronization Acquisition	Ofinno

R1-2600663	Discussion on synchronization acquisition and beam measurement during initial access	NEC

R1-2600693	Discussion on synchronization acquisition and beam measurement	China Telecom

R1-2600756	Discussion on synchronization acquisition and beam measurement for 6GR	Samsung

R1-2600808	Initial access design for 6GR	Panasonic

R1-2600828	On synchronization acquisition and beam measurement	Apple

R1-2600870	Discussion on synchronization acquisition and beam measurement	Fujitsu

R1-2600883	Discussion on design of the synchronization	Transsion Holdings

R1-2600894	Views on Synchronization acquisition and beam measurement	MediaTek Inc.

R1-2600916	Discussion on synchronization acquisition and beam measurement	Sharp

R1-2600945	Discussion on synchronization acquisition and beam measurement	HONOR

R1-2600970	On synchronization acquisition and beam measurement	KT Corp.

R1-2601003	Discussion on initial access and beam acquisition for 6GR	ETRI

R1-2601071	Synchronization Acquisition and Beam Measurement for 6GR	Fraunhofer IIS, Fraunhofer HHI

R1-2601079	Discussion on 6GR synchronization	Philips International B.V.

R1-2601103	Discussion on Synchronization signal design, acquisition and beam measurement	Lenovo

R1-2601130	6GR synchronisation and beam management	Sony

R1-2601182	Discussion on synchronization acquisition and beam measurement	NTT DOCOMO, INC

R1-2601206	Discussion on synchronization acquisition and beam measurement	Google

R1-2601221	Requirements for the 6GR Initial Access Design	AT&T

R1-2601273	Synchronization acquisition and beam measurement	Qualcomm Incorporated

R1-2601295	Discussion on synchronization acquisition and beam measurement	Quectel

R1-2601313	Synchronization acquisition and beam measurement	ITL

R1-2601336	Discussion on synchronization acquisition and beam measurement	KDDI Corporation

R1-2601375	Discussion on synchronization of 6GR	ASUSTeK

R1-2601394	Synchronization acquisition and beam measurement	CEWiT

R1-2601411	Discussion on synchronization acquisition and beam measurement	CSCN

R1-2601419	Discussion on Synchronization acquisition and beam measurement	WILUS Inc.

PRACH and RACH procedure

Note 1: Including design of PRACH and transmission, and RACH procedure

[124-R20-6GR-PRACH] Email discussion on Rel-20 6GR-PRACH and RACH procedure – Daewon (IDC)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600033	On PRACH and RACH procedure	Nokia

R1-2600052	Discussion on 6G PRACH Design and RACH Procedure	FUTUREWEI

R1-2600113	Discussion on 6GR PRACH and RACH procedure	Spreadtrum, UNISOC

R1-2600145	PRACH and RACH procedure for 6GR	Huawei, HiSilicon

R1-2600199	RACH of 6GR air interface	OPPO

R1-2600241	Discussion on PRACH and RACH procedure for 6GR	LG Electronics

R1-2600245	PRACH and RACH procedure	EURECOM

R1-2600264	Discussion on PRACH and RACH procedure	ZTE Corporation, Sanechips

R1-2600280	Discussion on PRACH and RACH procedure	TCL

R1-2600300	Discussion on PRACH and RACH procedure	CATT, CICTCI

R1-2600390	Discussion on 6GR PRACH design and RACH procedure	CMCC

R1-2600430	Discussion on PRACH and RACH procedure for 6GR	Xiaomi

R1-2600505	Discussions on 6GR RACH design and RA procedures	vivo

R1-2600539	Discussion on PRACH and RACH procedure	Tejas Network Limited

R1-2600565	IMU views on PRACH and RACH procedure	IMU

R1-2600603	Initial views on 6GR PRACH and RACH Procedure	Ofinno

R1-2600664	Discussion on PRACH and RACH procedure for 6GR	NEC

R1-2600694	Discussion on PRACH and RACH procedure	China Telecom

R1-2600757	Discussion on PRACH and RACH procedure design for 6GR	Samsung

R1-2600800	PRACH and RACH procedure	InterDigital, Inc.

R1-2600829	PRACH and RACH Procedure	Apple

R1-2600871	Discussion on PRACH and RACH procedure	Fujitsu

R1-2600884	Discussion on PRACH design and RACH procedure	Transsion Holdings

R1-2600895	Views on PRACH and RACH procedure	MediaTek Inc.

R1-2600917	Discussion on PRACH and RACH procedure	Sharp

R1-2600938	PRACH and RACH procedure for 6GR	Lenovo

R1-2600984	Discussion on PRACH and RACH procedure design for 6GR	Fainity Innovation

R1-2601004	Discussion on 6GR PRACH and RACH procedure	ETRI

R1-2601040	Discussion on PRACH and RACH procedure	Ericsson

R1-2601042	Discussion on PRACH and RACH procedure	Panasonic

R1-2601049	Discussion on PRACH design for 6GR	Fraunhofer HHI,Fraunhofer IIS

R1-2601131	6GR PRACH and RACH procedure	Sony

R1-2601183	Discussion on PRACH and RACH procedure	NTT DOCOMO, INC

R1-2601207	Discussion on PRACH and RACH procedure	Google

R1-2601274	PRACH and RACH procedure	Qualcomm Incorporated

R1-2601376	Discussion on PRACH and RACH procedure	KDDI Corporation

R1-2601395	PRACH and RACH procedure	CEWiT

Bandwidth operation

Note 1: Including bandwidth operation during initial access and right after initial access, e.g., procedure and mechanism for switching from initial bandwidth to larger bandwidth for larger bandwidth capable UE. When and where to discuss more complicated cases of bandwidth operation (e.g., bandwidth operation under connected mode in single carrier or multiple carriers, etc) will be considered with the progress of the study.

[124-R20-6GR-Bandwidth operation] Email discussion on Rel-20 6GR-Bandwidth operation – Chiouwei (MTK)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600034	On aspects of bandwidth operation in 6GR	Nokia

R1-2600053	6G Bandwidth Operation	FUTUREWEI

R1-2600114	Discussion on bandwidth operation for 6GR	Spreadtrum, UNISOC

R1-2600146	Bandwidth operation for 6GR	Huawei, HiSilicon

R1-2600200	Bandwidth operation for 6GR during and right after initial access	OPPO

R1-2600242	Discussion on Bandwidth Operation for 6GR	LG Electronics

R1-2600265	Discussion on bandwidth operation	ZTE Corporation, Sanechips

R1-2600301	Discussion on bandwidth operation	CATT

R1-2600391	Discussion on bandwidth operation	CMCC

R1-2600431	Discussion on bandwidth operation for 6GR	Xiaomi

R1-2600506	Discussions on 6GR bandwidth operation	vivo

R1-2600540	Discussion on Initial Access Bandwidth operation	Tejas Network Limited

R1-2600604	Initial views on 6GR Bandwidth Operation	Ofinno

R1-2600614	Bandwidth operation in initial access	Nordic Semiconductor ASA

R1-2600621	Bandwidth operation for 6GR	InterDigital, Inc.

R1-2600665	Discussion on bandwidth operation for 6GR	NEC

R1-2600695	Discussion on bandwidth operation for 6GR	China Telecom

R1-2600758	Bandwidth operation	Samsung

R1-2600830	Bandwidth operation	Apple

R1-2600847	Bandwidth Operation	Lenovo

R1-2600853	Discussion on bandwidth operation	Panasonic

R1-2600854	Discussion on bandwidth operation	Fujitsu

R1-2600896	Bandwidth operation for 6GR	MediaTek Inc.

R1-2600918	Discussion on Bandwidth operation for 6GR air interface	Sharp

R1-2600951	FL Summary 1 on Bandwidth Operation for 6GR	Moderator (MediaTek Inc.)

R1-2600952	FL Summary 2 on Bandwidth Operation for 6GR	Moderator (MediaTek Inc.)

R1-2600953	FL Summary 3 on Bandwidth Operation for 6GR	Moderator (MediaTek Inc.)

R1-2600961	Bandwidth operation	Ericsson

R1-2601005	Discussion on bandwidth operation for 6GR	ETRI

R1-2601035	Discussion on bandwidth operation	Transsion Holdings

R1-2601072	Bandwidth Operation in 6GR Initial Access	Fraunhofer IIS, Fraunhofer HHI

R1-2601184	Discussion on bandwidth operation	NTT DOCOMO, INC

R1-2601208	Discussion on bandwidth operation	Google

R1-2601275	Bandwidth operation	Qualcomm Incorporated

R1-2601335	Discussion on bandwidth operation during initial access	TCL

R1-2601396	Discussion on Bandwidth operation	CEWiT

R1-2601420	Discussion on Bandwidth operation	WILUS Inc.

R1-2601426	Discussion on bandwidth operation for 6GR	Kookmin University

R1-2601437	6GR bandwidth operation	Sony

MIMO operation

Note 1: Including schemes/mechanisms about how to transmit different channels or signals, and associated aspects

Note 2: How/where to transmit downlink control channels will be discussed under AI 10.5.2.1, what to be transmitted/indicated will be discussed under AI 10.5.4.1. Similarly, how/where to transmit PDSCH/PUSCH, such as Time/frequency domain resource allocation schemes, etc, will be discussed under AI 10.5.2.2/10.5.2.3.

Downlink transmission scheme(s) for downlink control channels

Note 1: Including downlink transmission scheme for downlink channel and signals, e.g., PDCCH, associated downlink DMRS design (if any), scrambling sequence, and control channel structure, like REG/CCE, CORESET bandwidth, where downlink DMRS design, as well as mechanism for supporting MRSS.

[124-R20-6GR-Transmission scheme for DL control channel] Email discussion on Rel-20 6GR-How to transmit downlink control channel – Dimitri (Nokia)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600035	On downlink transmission schemes for downlink control channels in 6GR	Nokia

R1-2600115	Discussion on downlink transmission scheme(s) for downlink control channels for 6GR	Spreadtrum, UNISOC

R1-2600147	Downlink transmission scheme(s) for downlink control channels	Huawei, HiSilicon

R1-2600206	Discussion of transmission scheme(s) for downlink control channels	OPPO

R1-2600218	Downlink transmission scheme(s) for downlink control channels	TCL

R1-2600302	DL transmission scheme for 6G downlink control channel	CATT, CICTCI

R1-2600353	Discussions on Physical layer control channel for 6G	Tejas Network Limited

R1-2600392	Downlink transmission scheme(s) for downlink control channels	CMCC

R1-2600432	Discussion on downlink control channel, scheduling for downlink and uplink transmission	Xiaomi

R1-2600507	Discussions on downlink transmission schemes for 6GR downlink control channels	vivo

R1-2600554	Discussion on DL transmission schemes for DL control channels	LG Electronics

R1-2600605	Downlink transmission scheme(s) for downlink control channels	Ofinno

R1-2600623	Downlink transmission scheme(s) for downlink control channels	Lenovo

R1-2600628	Downlink Transmission Scheme for Downlink Control Channel	Google

R1-2600651	Discussion on downlink transmission scheme(s) for downlink control channels	NEC

R1-2600696	Discussion on downlink transmission scheme(s) for downlink control channels	China Telecom

R1-2600759	Discussion on downlink transmission scheme(s) for downlink control channels	Samsung

R1-2600831	Transmission for downlink control channels	Apple

R1-2600849	Transmission schemes and procedures for 6GR downlink control channels	InterDigital, Inc.

R1-2600855	Discussion on downlink transmission schemes for downlink control channels	Fujitsu

R1-2600919	Downlink transmission scheme(s) for downlink control channels	Sharp

R1-2600946	Discussion on the downlink transmission schemes for downlink control channels	HONOR

R1-2600975	Transmission schemes for downlink control channels	ZTE Corporation, Sanechips

R1-2601006	Discussion on DL control channels for 6GR	ETRI

R1-2601046	DL Control Channel Transmission for 6GR	Ericsson

R1-2601132	Discussion on downlink transmission scheme(s) for downlink control channels	Sony

R1-2601145	Discussion on transmission schemes for DCI	Panasonic

R1-2601185	Discussion on Downlink transmission scheme(s) for downlink control channels	NTT DOCOMO, INC.

R1-2601238	Discussion on downlink transmission scheme(s) for downlink control channels	MediaTek Inc.

R1-2601276	Downlink transmission scheme(s) for downlink control channels	Qualcomm Incorporated

R1-2601324	Discussion on Transmission Schemes for Downlink Control Channels	Rakuten Mobile, Inc

R1-2601346	Two-Step PDCCH for Inter-User Interference Reduction in MU-MIMO	Orange, Deutsche Telekom, AccelerComm

R1-2601427	Discussion on DL control channels	Kookmin University

Downlink transmission scheme(s) for downlink shared channels

Note 1: Including downlink transmission scheme for downlink channel, e.g., PDSCH, associated downlink DMRS design (if any), scrambling sequence, mechanism for layer mapping and modulation may consider different evaluation assumptions, as well as mechanism for supporting MRSS.

[124-R20-6GR-Transmission scheme for DL shared channel] Email discussion on Rel-20 6GR-How to transmit downlink shared channel – Sven, Yushu (Ericsson, Google)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600036	On downlink transmission schemes for downlink shared channels in 6GR	Nokia

R1-2600054	Discussion on downlink transmission schemes for downlink shared channels for 6GR air interface	FUTUREWEI

R1-2600116	Discussion on downlink transmission scheme(s) for downlink shared channels for 6GR	Spreadtrum, UNISOC

R1-2600148	Transmission schemes for 6GR DL shared channels	Huawei, HiSilicon

R1-2600191	Downlink transmission scheme for downlink shared channels	OPPO

R1-2600219	Transmission schemes for 6GR DL shared channels	TCL

R1-2600228	Discussion on downlink transmission scheme(s) for downlink shared channels	ZTE Corporation, Sanechips

R1-2600303	Discussion on downlink transmission schemes for downlink shared channels	CATT

R1-2600334	Downlink transmission schemes for PDSCH	Ericsson Telecom S.A. de C.V.

R1-2600345	Downlink transmission scheme(s) for downlink data channels	MediaTek Inc.

R1-2600355	Discussions on Downlink Transmission Scheme for 6G	Tejas Network Limited

R1-2600393	Discussion on downlink transmission scheme(s) for downlink shared channels	CMCC

R1-2600433	Discussion on DL transmission scheme(s)	Xiaomi

R1-2600508	Discussion on downlink transmission schemes for 6GR downlink shared channels	vivo

R1-2600629	Downlink Transmission Scheme for Downlink Shared Channel	Google

R1-2600641	Discussion on downlink transmission scheme(s) for downlink shared channels	LG Electronics

R1-2600670	Downlink on transmission scheme(s) for downlink shared channels	NEC

R1-2600697	Discussion on downlink transmission scheme(s) for downlink shared channels	China Telecom

R1-2600760	Discussion on downlink transmission scheme(s) for downlink shared channels	Samsung

R1-2600780	Study for downlink transmission scheme(s) for downlink shared channels	Lenovo

R1-2600793	Discussion on downlink transmission scheme(s) for 6GR downlink shared channels	BeammWave AB

R1-2600803	Downlink transmission schemes for downlink shared channels	NVIDIA

R1-2600832	Views on downlink transmission schemes for downlink shared channels	Apple

R1-2600850	Transmission schemes and procedures for 6GR downlink shared channels	InterDigital, Inc.

R1-2600872	Discussion on downlink transmission schemes for downlink shared channels	Fujitsu

R1-2600920	Discussion on downlink transmission schemes for downlink shared channels	Sharp

R1-2600934	DL transmission scheme for DL shared channels	Panasonic

R1-2600947	Downlink transmission scheme(s) for downlink shared channels	HONOR

R1-2600954	FL Summary #3 on Downlink Transmission Scheme for Downlink Shared Channel	Moderator (Google), Moderator (Ericsson)

R1-2600955	FL Summary #5 on Downlink Transmission Scheme for Downlink Shared Channel	Moderator (Google), Moderator (Ericsson)

R1-2600956	FL Summary #7 on Downlink Transmission Scheme for Downlink Shared Channel	Moderator (Google), Moderator (Ericsson)

R1-2601007	Discussion on downlink transmission scheme(s) for downlink shared channels in 6GR	ETRI

R1-2601023	Discussion on downlink transmission schemes for downlink shared channels	Fainity Innovation

R1-2601050	Discussion on downlink transmission scheme(s) for downlink shared channels	Shanghai Jiao Tong University, NERC-DTV

R1-2601054	MIMO enhancements for the 6GR physical layer	BBC, Imperial College London, VIAVI Solutions, ETRI, Federated Telecoms Hub

R1-2601133	Discussion of downlink transmission scheme(s) for downlink shared channels	Sony

R1-2601186	Discussion on Downlink transmission scheme(s) for downlink shared channels	NTT DOCOMO, INC.

R1-2601222	Discussion on 6GR DL Shared Channel Framework	AT&T

R1-2601277	Downlink transmission scheme(s) for downlink shared channels	Qualcomm Incorporated

R1-2601326	On transmission schemes for downlink shared channel in 6GR	Fraunhofer IIS, Fraunhofer HHI

R1-2601329	Discussion on downlink transmission scheme(s) for downlink shared channels	KDDI Corporation (TTC)

R1-2601337	Discussion on Transmission Schemes for Downlink Shared Channels	Rakuten Mobile, Inc

R1-2601424	Discussion on downlink transmission scheme for downlink shared channels	BUPT, X-NET

R1-2601428	FL Summary #1 on Downlink Transmission Scheme for Downlink Shared Channel	Moderator (Ericsson), Moderator (Google)

R1-2601429	FL Summary #2 on Downlink Transmission Scheme for Downlink Shared Channel	Moderator (Ericsson), Moderator (Google)

R1-2601430	FL Summary #4 on Downlink Transmission Scheme for Downlink Shared Channel	Moderator (Ericsson), Moderator (Google)

R1-2601431	FL Summary #6 on Downlink Transmission Scheme for Downlink Shared Channel	Moderator (Ericsson), Moderator (Google)

R1-2601432	On Codeword-to-Layer Mapping Granularity and Its Efficiency in 6G MIMO	BT plc

Uplink transmission scheme(s) for uplink channels

Note 1: Including uplink transmission scheme for uplink channel, e.g., PUSCH, PUCCH, corresponding up link DMRS design (if any), and scrambling sequence.

[124-R20-6GR-Transmission scheme for UL channels] Email discussion on Rel-20 6GR-How to transmit uplink channels – Naoya, Younrok (NTT DOCOMO, Samsung)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600037	On transmission schemes for uplink channels in 6GR	Nokia

R1-2600055	Uplink transmission scheme(s) for uplink channels	FUTUREWEI

R1-2600117	Discussion on uplink transmission schems(s) for uplink channels for 6GR	Spreadtrum, UNISOC

R1-2600149	Transmission schemes for 6GR UL channels	Huawei, HiSilicon

R1-2600192	Discussions on 6GR Uplink Transmission	OPPO

R1-2600220	Transmission schemes for 6GR UL channels	TCL

R1-2600229	Discussion on uplink transmission scheme(s) for uplink channels	ZTE Corporation, Sanechips

R1-2600304	Discussion on uplink transmission schemes for uplink channels	CATT

R1-2600346	Uplink transmission scheme(s) for uplink channels	MediaTek Inc.

R1-2600394	Discussion on uplink transmission scheme(s) for uplink channels	CMCC

R1-2600434	Discussion on UL transmission scheme(s)	Xiaomi

R1-2600509	Discussion on uplink transmission schemes for 6GR uplink channels	vivo

R1-2600569	Discussion on transmission schemes for uplink channels in 6GR	BJTU

R1-2600630	Uplink Transmisison Scheme for Uplink Channels	Google

R1-2600642	Discussion on uplink transmission scheme(s) for uplink channels	LG Electronics

R1-2600671	Discussion on uplink transmission scheme(s) for uplink channels	NEC

R1-2600698	Discussion on UL transmission schemes for PUSCH and PUCCH	China Telecom

R1-2600761	Discussion on uplink transmission scheme(s) for uplink channels	Samsung

R1-2600785	Study for uplink transmission scheme(s) for uplink channels	Lenovo

R1-2600795	Discussion on uplink transmission scheme(s) for uplink channels	BeammWave AB

R1-2600804	Uplink transmission schemes for uplink channels	NVIDIA

R1-2600833	Views on uplink transmission schemes for uplink channels	Apple

R1-2600851	Transmission schemes and procedures for 6GR uplink channels	InterDigital, Inc.

R1-2600873	Discussion on uplink transmission in 6GR	Fujitsu

R1-2600921	Discussions on uplink transmission schemes for uplink channels	Sharp

R1-2601008	Discussion on uplink transmission scheme(s) for uplink channels	ETRI

R1-2601033	Uplink transmission scheme(s) for uplink channels	Ericsson

R1-2601115	Discussion on uplink transmission scheme for uplink channels	Panasonic

R1-2601134	Discussion of uplink transmission scheme(s) for uplink channels	Sony

R1-2601187	Discussion on Uplink transmission scheme(s) for uplink channels	NTT DOCOMO, INC.

R1-2601223	Discussion on 6GR UL Channel Framework	AT&T

R1-2601228	FL Summary #1 on Uplink transmission scheme(s) for uplink channels	Moderator (Docomo). Moderator (Samsung)

R1-2601229	FL Summary #2 on Uplink transmission scheme(s) for uplink channels	Moderator (Docomo), Moderator (Samsung)

R1-2601230	FL Summary #3 on Uplink transmission scheme(s) for uplink channels	Moderator (Docomo), Moderator (Samsung)

R1-2601278	Uplink transmission schemes for uplink channels	Qualcomm Incorporated

R1-2601331	Discussion on uplink transmission scheme(s) for uplink channels	KDDI Corporation (TTC)

R1-2601339	Discussion on Transmission Schemes for Uplink Channels	Rakuten Mobile, Inc

R1-2601370	Enhancements for Uplink Data and Control Channels: Low-PAPR Waveforms and Pre-DFT Multiplexing	Wisig Networks, IITH

R1-2601397	Discussion on Uplink transmission scheme(s) for uplink channels	CEWiT

Beam management for downlink and uplink

Note 1: Including proposals for beam management related aspects, such as beam indication, beam report and beam recovery, etc.

[124-R20-6GR-Beam management] Email discussion on Rel-20 6GR-Beam management – Bo, Hong (ZTE, Apple)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600038	On beam management for downlink and uplink in 6GR	Nokia

R1-2600056	Discussion on beam management for downlink and uplink for 6GR air interface	FUTUREWEI

R1-2600093	Beam Management for Multi-TRP transmission in 6GR	Kyocera Corporation

R1-2600118	Discussion on beam management for downlink and uplink for 6GR	Spreadtrum, UNISOC

R1-2600150	Beam management for downlink and uplink	Huawei, HiSilicon

R1-2600193	Discussions on 6GR multi-beam operation	OPPO

R1-2600221	Beam management for downlink and uplink	TCL

R1-2600230	Discussion on beam management for downlink and uplink	ZTE Corporation, Sanechips

R1-2600305	Discussion on beam management for 6GR	CATT

R1-2600347	Beam management and mobility	MediaTek Inc.

R1-2600395	Discussion on beam management for downlink and uplink transmission	CMCC

R1-2600435	Discussion on beam management for downlink and uplink	Xiaomi

R1-2600510	Discussion on beam management for 6GR downlink and uplink	vivo

R1-2600568	Discussion on AI-Driven Beam Management Methods	BJTU

R1-2600606	Initial views on Beam Management	Ofinno

R1-2600631	Beam Management for Downlink and Uplink	Google

R1-2600656	Beam management for downlink and uplink	NEC

R1-2600699	Discussion on beam management for downlink and uplink	China Telecom

R1-2600762	Views on beam management for downlink and uplink in 6GR	Samsung

R1-2600781	Discussion on beam management for downlink and uplink in 6GR	Lenovo

R1-2600796	Discussion on beam management for 6GR downlink and uplink	BeammWave AB

R1-2600834	On beam management aspects for downlink and uplink	Apple

R1-2600852	Beam management and TCI framework for 6GR MIMO operation	InterDigital, Inc.

R1-2600874	Discussion on beam management in 6GR	Fujitsu

R1-2600889	Discussion on beam management for downlink and uplink	LG Electronics

R1-2600912	Beam management for DL and UL	Panasonic

R1-2600922	Beam management for downlink and uplink	Sharp

R1-2601009	Discussion on beam management for 6GR	ETRI

R1-2601027	Discussion on beam management for downlink and uplink	Ericsson

R1-2601036	Discussion on beam management for downlink and uplink	Transsion Holdings

R1-2601069	Discussion on Beam Management Procedures for 6GR	Panasonic

R1-2601135	Discussion on beam management for downlink and uplink	Sony

R1-2601188	Discussion on Beam management for downlink and uplink	NTT DOCOMO, INC.

R1-2601214	Discussion on beam management for downlink and uplink in 6GR	Pengcheng Laboratory

R1-2601224	Discussion on 6GR Beam Management Framework	AT&T

R1-2601279	Beam management for downlink and uplink	Qualcomm Incorporated

R1-2601325	On beam management for downlink and uplink in 6GR	Fraunhofer IIS, Fraunhofer HHI

R1-2601340	Discussion on Beam Management of Downlink and Uplink	Rakuten Mobile, Inc

R1-2601398	Discussion on Beam management for 6GR	CEWiT

CSI acquisition and report

Aspects of downlink-based CSI acquisition

Note 1: Including proposals for CSI-RS design, transmission, CSI acquisition and report with CSI-RS and/or other channels/signals (e.g., DMRS) for different usages, e.g., mobility, early acquisition, less measurements, report with different mechanisms considering precoder and overhead, as well as transmission mechanism for CSI report, e.g., PUCCH.

[124-R20-6GR-Aspects of DL based CSI acquisition] Email discussion on Rel-20 6GR-Aspects of DL based CSI acquisition – Feifei, Hao (Samsung, vivo)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600039	On downlink-based CSI acquisition in 6GR	Nokia

R1-2600057	Discussion on aspects of downlink-based CSI acquisition for 6GR air interface	FUTUREWEI

R1-2600119	Discussion on aspects of downlink-based CSI acquisition for 6GR	Spreadtrum, UNISOC

R1-2600133	6GR CSI: Aspects of Downlink-based CSI Acquisition	InterDigital, Inc.

R1-2600151	Aspects of downlink-based CSI acquisition	Huawei, HiSilicon

R1-2600194	Discussion on downlink based CSI acquisition	OPPO

R1-2600222	Aspects of downlink-based CSI acquisition	TCL

R1-2600231	Discussion on aspects of downlink-based CSI acquisition	ZTE Corporation, Sanechips

R1-2600306	Discussion on downlink-based CSI acquisition for 6GR	CATT

R1-2600339	Aspects of downlink-based CSI acquisition	Tejas Network Limited

R1-2600348	Aspects of downlink-based CSI acquisition	MediaTek Inc.

R1-2600396	Discussion on downlink-based CSI acquisition	CMCC

R1-2600436	Discussion on DL CSI acquisition for 6GR	Xiaomi

R1-2600511	Discussion on aspects of downlink-based CSI acquisition for 6GR	vivo

R1-2600559	IMU Views on Downlink-based CSI Acquisition	IMU

R1-2600571	Discussion on downlink based CSI acquisition	BJTU

R1-2600607	Views on Aspects of downlink-based CSI acquisition	Ofinno

R1-2600632	Aspects of Downlink Based CSI Acquisition	Google

R1-2600672	Discussion on downlink-based CSI acquisition	NEC

R1-2600700	Discussion on aspects of downlink-based CSI acquisition	China Telecom

R1-2600763	Discussion on DL-based CSI acquisition and CSI-RS design	Samsung

R1-2600797	Discussion on aspects of downlink-based CSI acquisition	BeammWave AB

R1-2600805	Downlink-based CSI acquisition for 6GR air interface	NVIDIA

R1-2600835	Views on downlink-based CSI acquisition	Apple

R1-2600848	Aspects of downlink-based CSI acquisition	Lenovo

R1-2600875	Discussion on downlink-based CSI acquisition	Fujitsu

R1-2600880	Discussion on aspects of downlink-based CSI acquisition	KT Corp.

R1-2600890	Discussion on aspects of downlink-based CSI acquisition	LG Electronics

R1-2600911	Aspects of downlink-based CSI acquisition for 6GR study	Intel Corporation

R1-2600923	Aspects of downlink-based CSI acquisiton	Sharp

R1-2600948	Discussion on downlink-based CSI acquisition	HONOR

R1-2600980	Downlink CSI acquisition aspects for 6G	Fraunhofer IIS, Fraunhofer HHI

R1-2601010	Discussion on downlink-based CSI acquisition for 6GR	ETRI

R1-2601038	Views on aspects of downlink-based CSI Acquisition	Ericsson

R1-2601051	Discussion on downlink based CSI acquisition	Shanghai Jiao Tong University, NERC-DTV

R1-2601052	Discussion on downlink based CSI acquisition	Shanghai Jiao Tong University, NERC-DTV

R1-2601053	Discussion on downlink based CSI acquisition	Shanghai Jiao Tong University, NERC-DTV

R1-2601068	Discussion on DL-based CSI Acquisition for 6G	Panasonic

R1-2601136	Discussion of aspects of downlink-based CSI acquisition	Sony

R1-2601189	Discussion on Aspects of downlink-based CSI acquisition	NTT DOCOMO, INC.

R1-2601225	Aspects of DL-based 6GR Channel Acquisition	AT&T

R1-2601280	Aspects of downlink-based CSI acquisition	Qualcomm Incorporated

R1-2601308	Feature lead summary #1 on DL-based CSI acquisition	Moderator (Samsung), Moderator (vivo)

R1-2601309	Feature lead summary #2 on DL-based CSI acquisition	Moderator (Samsung), Moderator (vivo)

R1-2601310	Feature lead summary #3 on DL-based CSI acquisition	Moderator (Samsung), Moderator (vivo)

R1-2601311	Feature lead summary #4 on DL-based CSI acquisition	Moderator (Samsung), Moderator (vivo)

R1-2601312	Feature lead summary #5 on DL-based CSI acquisition	Moderator (Samsung), Moderator (vivo)

R1-2601333	Discussion on downlink-based CSI acquisition	KDDI Corporation

R1-2601342	Discussion on Aspects of Downlink-Based CSI Acquisition	Rakuten Mobile, Inc

R1-2601352	Discussion on CSI acquisition	ASUSTeK

R1-2601399	Views on DL CSI acquisition in 6G	CEWiT

R1-2601425	Discussion on downlink-based CSI acquisition	BUPT, X-NET

R1-2601435	Discussion on aspects of downlink-based CSI acquisition for 6GR	Pengcheng Laboratory, ZGC Institute of Ubiquitous-X Innovation and Application

R1-2601451	Views on aspects of downlink-based CSI Acquisition	Ericsson

(revision of R1-2601038)

Aspects of uplink-based CSI acquisition

Note 1: Including proposals for SRS design, transmission, acquisition for different usages.

[124-R20-6GR-Aspects of UL based CSI acquisition] Email discussion on Rel-20 6GR-Aspects of UL based CSI acquisition – Qiubin (CATT)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600040	On uplink-based CSI acquisition in 6GR	Nokia

R1-2600058	Aspects of uplink-based CSI acquisition	FUTUREWEI

R1-2600120	Discussion on aspects of uplink-based CSI acquisition for 6GR	Spreadtrum, UNISOC

R1-2600134	6GR CSI: Aspects of Uplink-based CSI Acquisition	InterDigital, Inc.

R1-2600152	Aspects of uplink-based CSI acquisition	Huawei, HiSilicon

R1-2600195	Discussion on uplink based CSI acquisition	OPPO

R1-2600223	Aspects of uplink-based CSI acquisition	TCL

R1-2600232	Discussion on aspects of uplink-based CSI acquisition	ZTE Corporation, Sanechips

R1-2600307	Discussion on uplink-based CSI acquisition for 6GR	CATT

R1-2600340	Aspects of uplink-based CSI acquisition	Tejas Network Limited

R1-2600349	Aspects of uplink-based CSI acquisition	MediaTek Inc.

R1-2600397	Discussion on uplink-based CSI acquisition	CMCC

R1-2600437	Discussion on UL CSI acquisition for 6GR	Xiaomi

R1-2600512	Discussion on aspects of uplink-based CSI acquisition for 6GR	vivo

R1-2600592	Uplink-based CSI acquisition for 6GR air interface	NVIDIA

R1-2600633	Aspects of Uplink Based CSI Acquisition	Google

R1-2600673	Discussion on uplink-based CSI acquisition	NEC

R1-2600701	Discussion on aspects of uplink-based CSI acquisition	China Telecom

R1-2600764	Discussion on UL-based CSI acquisition and SRS design	Samsung

R1-2600782	Aspects of uplink-based CSI acquisition	Lenovo

R1-2600836	On UL-based CSI acquisition for 6GR	Apple

R1-2600876	Discussion on uplink-based CSI acquisition	Fujitsu

R1-2600891	Discussion on aspects of uplink-based CSI acquisition	LG Electronics

R1-2600924	Aspects of uplink-based CSI acquisition	Sharp

R1-2601011	Discussion on uplink-based CSI acquisition for 6GR	ETRI

R1-2601096	Discussion on aspects of uplink-based CSI acquisition	Ofinno

R1-2601137	Discussion of aspects of uplink-based CSI acquisition	Sony

R1-2601190	Discussion on Aspects of uplink-based CSI acquisition	NTT DOCOMO, INC.

R1-2601226	Aspects of UL-based 6GR Channel Acquisition	AT&T

R1-2601281	Aspects of uplink-based CSI acquisition	Qualcomm Incorporated

R1-2601302	Moderator summary#1 on uplink-based CSI acquisition	Moderator (CATT)

R1-2601303	Moderator summary#2 on uplink-based CSI acquisition	Moderator (CATT)

R1-2601304	Moderator summary#3 on uplink-based CSI acquisition	Moderator (CATT)

R1-2601343	Discussion on Aspects of Uplink-Based CSI Acquisition	Rakuten Mobile, Inc

R1-2601365	Discussion on UL-based CSI Acquisition for 6G	Panasonic

R1-2601408	Views on aspects of uplink-based CSI acquisition	Ericsson

Other aspects

Note 1: Including proposals for CSI acquisition and report jointly considering both downlink and uplink, other reference signal(s) design and transmission, e.g., for tracking, etc.

[124-R20-6GR-Other Aspects related to CSI] Email discussion on Rel-20 6GR-Other Aspects related to CSI – Bingchao (Lenovo)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600041	Other aspects of 6GR physical layer operation	Nokia

R1-2600059	Other Aspects for CSI acquisition	FUTUREWEI

R1-2600121	Discussion on other aspects of CSI acquisition and report for 6GR	Spreadtrum, UNISOC

R1-2600135	6GR CSI: Considerations for Evaluation of AI/ML-based Solution	InterDigital, Inc.

R1-2600153	Other aspects for MIMO operation	Huawei, HiSilicon

R1-2600196	Other aspects for CSI acquisition	OPPO

R1-2600224	Other aspects for MIMO operation	TCL

R1-2600233	Discussion on other aspects of CSI acquisition and report	ZTE Corporation, Sanechips

R1-2600308	Discussion on other aspects for CSI acquisition and report	CATT

R1-2600398	Discussion on other aspects of CSI acquisition and report	CMCC

R1-2600438	Discussion on other aspects	Xiaomi

R1-2600513	Discussion on other aspects of CSI acquisition for 6GR	vivo

R1-2600578	Other aspects	Ericsson España S.A.

R1-2600634	Other Aspects of CSI Acquisition	Google

R1-2600674	Discussion on other aspects for CSI and reference signals	NEC

R1-2600765	Discussion on other aspects on CSI acquisition and report	Samsung

R1-2600783	Discussion on miscellaneous aspects on CSI acquisition and report	Lenovo

R1-2600837	On other aspects of CSI acquisition	Apple

R1-2600860	On time/frequency tracking RS in connected mode	MediaTek Inc.

R1-2600877	Discussion on 6GR PTRS and TRS design	Fujitsu

R1-2600892	Discussion on TRS, PTRS and reciprocity based CSI	LG Electronics

R1-2601097	Discussion on other aspects of CSI acquisition and report	Ofinno

R1-2601191	Discussion on Other aspects of CSI acquisition and report	NTT DOCOMO, INC.

R1-2601201	Discussion on other aspects of CSI acquisition and report	Pengcheng Laboratory

R1-2601282	Other aspects of CSI acquisition and reporting	Qualcomm Incorporated

R1-2601344	Discussion on Other Aspects of CSI Acquisition	Rakuten Mobile, Inc

Downlink control channel, scheduling and HARQ operation

Note 1: Including proposals for all candidate duplexing types, for spectrum utilization, and for aggregation, such as flexible utilization of spectrum resources for DL and UL over different carriers/bands, as well as flexible utilization of spectrum resources for DL and UL over different carriers/bands.

Note 2: Including proposals for both broadcast and unicast.

Downlink control channel, scheduling for downlink and uplink transmission

Note 1: Including proposals for downlink control channel design, e.g., DCI format, fields in different DCI for different usages, as well as reliability improvement.

[124-R20-6GR-DL control channel and scheduling] Email discussion on Rel-20 6GR-What to transmit in DL control – Xiaodong, Sigen (CMCC, Apple)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600042	On downlink control channel, scheduling for downlink and uplink transmission	Nokia

R1-2600122	Discussion on downlink control channel, scheduling for DL and UL transmission for 6GR	Spreadtrum, UNISOC

R1-2600154	Downlink control information and data scheduling	Huawei, HiSilicon

R1-2600207	Discussion of DL control channel and scheduling	OPPO

R1-2600309	Design of DL control channel and DCI for 6G scheduling	CATT

R1-2600354	Downlink Control Channel scheduling for downlink and uplink	Tejas Network Limited

R1-2600399	Downlink control channel, scheduling for downlink and uplink transmission	CMCC

R1-2600439	Discussion on transmission schemes for downlink control channel	Xiaomi

R1-2600514	Discussions on 6GR DL control channel and DL/UL scheduling	vivo

R1-2600560	IMU Views on 6GR Control Channel Design	IMU

R1-2600575	Discussion on downlink control channel, scheduling for downlink and uplink transmission	TCL

R1-2600615	Downlink control channel and scheduling for downlink and uplink transmission	InterDigital, Inc.

R1-2600643	Downlink control channel design and downlink/uplink scheduling for 6GR	LG Electronics

R1-2600666	Discussion on DCI and scheduling	NEC

R1-2600702	Discussion on DCI design for 6GR	China Telecom

R1-2600766	Downlink control channel, scheduling for downlink and uplink transmission	Samsung

R1-2600838	On downlink control channel and scheduling for downlink and uplink transmissions in 6GR	Apple

R1-2600878	Discussion on downlink control channel and scheduling for DL/UL transmission	Fujitsu

R1-2600908	Downlink control channel and DL/UL scheduling	Ericsson

R1-2600925	Discussion on downlink control channel for scheduling of downlink and uplink transmissions	Sharp

R1-2600957	Discussion on downlink control channel and scheduling	Lenovo

R1-2600976	Study on downlink control and scheduling	ZTE Corporation, Sanechips

R1-2601012	Discussion on downlink control channel and scheduling mechanism	ETRI

R1-2601104	Downlink control and scheduling aspects	Ofinno

R1-2601138	Discussion on 6G Downlink Control Channel for UL/DL Scheduling	Sony

R1-2601146	Discussion on DCI for DL and UL transmission	Panasonic

R1-2601192	Discussion on DL control channel and scheduling for DL and UL transmission	NTT DOCOMO, INC.

R1-2601239	Discussion on downlink control channel, scheduling for downlink and uplink transmission	MediaTek Inc.

R1-2601283	Downlink control channel, scheduling for downlink and uplink transmission	Qualcomm Incorporated

R1-2601298	Discussion on downlink control channel and downlink/uplink scheduling	KT Corp.

R1-2601387	Downlink control channel, scheduling for downlink and uplink transmission	Google Korea LLC

R1-2601400	Downlink control channel scheduling for downlink and uplink transmission	CEWiT

R1-2601404	Flexible Scheduling for Downlink and Uplink Transmissions	Fraunhofer IIS, Fraunhofer HHI

Downlink and uplink transmission without downlink control channel

Note 1: TBD when to start detailed design, however, its impact on HARQ can be considered in AI 10.5.4.3

HARQ related Aspects

Note 1: Including proposals for timing line, content and report mechanism (e.g., PUCCH or other mechanism).

[124-R20-6GR-HARQ related] Email discussion on Rel-20 6GR-HARQ related – Kevin (OPPO)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600043	Views on HARQ related aspects in 6GR	Nokia

R1-2600123	Discussion on 6GR HARQ related aspects	Spreadtrum, UNISOC

R1-2600155	HARQ related aspects for 6GR	Huawei, HiSilicon

R1-2600205	Discussion on HARQ for 6GR	OPPO

R1-2600310	Discussion on HARQ related aspects for 6GR	CATT

R1-2600400	Discussion on 6GR HARQ design	CMCC

R1-2600440	Discussion on 6G HARQ related aspects	Xiaomi

R1-2600515	Discussion on 6GR HARQ related aspects	vivo

R1-2600555	Discussion on HARQ related aspects for 6GR	LG Electronics

R1-2600576	Discussion on HARQ related aspects	TCL

R1-2600616	HARQ related aspects	InterDigital, Inc.

R1-2600635	HARQ Related Aspects	Google

R1-2600653	Discussion on HARQ related operation	NEC

R1-2600703	Discussion on HARQ related aspects	China Telecom

R1-2600714	HARQ for 6GR	Lenovo

R1-2600767	On 6GR HARQ Related Aspects	Samsung

R1-2600839	On HARQ related aspects	Apple

R1-2600856	Discussion on HARQ related aspects	Fujitsu

R1-2600926	Discussion on HARQ related Aspects for 6GR air interface	Sharp

R1-2600977	Discussion on HARQ related aspects for 6GR	ZTE Corporation, Sanechips

R1-2601013	Discussion on HARQ related Aspects	ETRI

R1-2601048	Scheduling and HARQ operation for 6GR	Ericsson, T-Mobile USA

R1-2601099	HARQ related aspects	Qualcomm Incorporated

R1-2601105	HARQ related aspects	Ofinno

R1-2601116	Discussion on HARQ related aspects for 6GR	Panasonic

R1-2601139	Discussion on 6G HARQ Related Aspects	Sony

R1-2601193	Discussion on HARQ-related aspects for 6GR	NTT DOCOMO, INC.

R1-2601359	Discussion on HARQ related aspects in 6GR	MediaTek Inc.

R1-2601401	Discussion on HARQ related Aspects	CEWiT

Handling of potential multiple uplink transmissions

Note 1: Including proposals for handling of potential simultaneous transmission, or misalignment between different transmissions, e.g., between PUSCH and PUCCH in same carrier/different carriers, etc

Other physical layer signals, channels and procedure

Note 1: Including proposals for interference measurements for some scenarios, e.g., CLI, etc, as well as proposals for UE to report other information than CSI and HARQ.

[124-R20-6GR-Other signals, channels, and procedures] Email discussion on Rel-20 6GR-Other signals, channels, and procedures – Li (OPPO)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600044	On other physical layer signals, channels and procedures in 6GR	Nokia

R1-2600124	Discussion on other physical layer signals, channels and procedure for 6GR	Spreadtrum, UNISOC

R1-2600156	Other physical layer signals and procedures	Huawei, HiSilicon

R1-2600208	Discussion on other physical layer signals, channels and procedure	OPPO

R1-2600213	Other physical layer signals, channels and procedure	Ericsson

R1-2600271	Discussion on 6G other physical layer signals, channels and procedure	ZTE Corporation, Sanechips

R1-2600311	Discussion on interference measurements and UE reporting for PHY-layer information beyond CSI and HARQ	CATT

R1-2600401	Discussion on interference measurements, report and management	CMCC

R1-2600441	Considerations on 6GR SR and BSR transmission schemes	Xiaomi

R1-2600516	Discussion on other physical layer signals, channels and procedure for 6GR	vivo

R1-2600525	Other physical layer signals, channels and procedure	InterDigital, Inc.

R1-2600541	Other physical layer signals, channels and procedure	TCL

R1-2600608	Views on Other physical layer signals, channels and procedure	Ofinno

R1-2600636	Other Physical Layer Signals and Procedure	Google

R1-2600662	Discussion on Other physical layer signals, channels and procedure	NEC

R1-2600768	Discussion on other physical layer signals, channels and procedure	Samsung

R1-2600840	On other physical layer signals, channels and procedure	Apple

R1-2600927	Discussions on other physical layer signals, channels and procedure	Sharp

R1-2601014	Discussion on other physical-layer signal and procedure	ETRI

R1-2601194	Discussion on other physical layer signals, channels and procedures	NTT DOCOMO, INC

R1-2601227	Views on 6GR AI/ML use case prioritization	AT&T

R1-2601241	On UE feedback for joint energy efficiency optimization	MediaTek Inc.

R1-2601284	Other physical layer signals, channels and procedure	Qualcomm Incorporated

R1-2601447	FL Summary #1 for 10.5.5	Moderator (OPPO)

R1-2601448	FL Summary #2 for 10.5.5	Moderator (OPPO)

R1-2601449	FL Summary #3 for 10.5.5	Moderator (OPPO)

WUS and operation

Note 1: For schemes/mechanisms that are different from leveraging the design of other agendas.

Downlink WUS and operation

Design of WUS with OFDM based sequence

Note 1: Including Contributions for design target, applicable scenarios, etc.

[124-R20-6GR-Design of WUS] Email discussion on Rel-20 6GR-Design of WUS – Magnus (Ericsson)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600045	On the design of WUS with OFDM based sequence	Nokia

R1-2600060	Discussion on 6G Design of WUS with OFDM based Sequence	FUTUREWEI

R1-2600125	Discussion on design of WUS with OFDM based sequence for 6GR	Spreadtrum, UNISOC

R1-2600157	Design of WUS with OFDM based sequence	Huawei, HiSilicon

R1-2600201	Discussion on the signal design of DL WUS	OPPO

R1-2600215	Design of WUS with OFDM based sequence	Ericsson

R1-2600234	Discussion on design of DL-WUS with OFDM based sequence	TCL

R1-2600312	Discussion on design of WUS with OFDM based sequences	CATT

R1-2600359	Design of WUS with OFDM based sequence	Tejas Network Limited

R1-2600402	Discussion on the sequence design for DL WUS in 6GR	CMCC

R1-2600442	Discussion on Downlink WUS with OFDM based sequence for 6GR	Xiaomi

R1-2600457	Discuss on DL WUS with OFDM based sequence	ZTE Corporation, Sanechips

R1-2600517	Discussion on design of 6GR DL WUS with OFDM based sequence	vivo

R1-2600523	Discussion on design of WUS with OFDM based sequence	EURECOM

R1-2600531	DL WUS and operation in 6GR	InterDigital, Inc.

R1-2600556	Discussion on design of DL WUS with OFDM based sequence for 6GR	LG Electronics

R1-2600561	IMU Views on Downlink Wake-Up Signal	IMU

R1-2600609	Initial views on DL WUS Design	Ofinno

R1-2600668	Discussion on design of WUS with OFDM based sequence	NEC

R1-2600706	Discussion on Design of WUS with OFDM based sequence	Panasonic

R1-2600717	Discussion on WUS design with OFDM based sequence	Lenovo

R1-2600769	Discussion on design of WUS with OFDM based sequence	Samsung

R1-2600841	Design of 6G DL WUS with OFDM based sequence	Apple

R1-2600928	Disscussion on Design of WUS with OFDM based sequence	Sharp

R1-2600949	Discussion on the design of WUS based on OFDM sequence	HONOR

R1-2601015	Discussion on design of WUS with OFDM based sequence	ETRI

R1-2601140	Discussion on the design of WUS with OFDM based sequence	Sony

R1-2601148	Discussion on Design of WUS with OFDM based sequence	Kyocera

R1-2601195	Discussion on Design of WUS with OFDM based sequence	NTT DOCOMO, INC

R1-2601209	Discussion on design of WUS with OFDM based sequence	Google

R1-2601242	Design of downlink WUS with OFDM based sequence	MediaTek Inc.

R1-2601285	DL WUS Design	Qualcomm Incorporated

R1-2601314	DL WUS design	Nordic Semiconductor ASA

WUS operation in RRC states

[124-R20-6GR-WUS operation in RRC states] Email discussion on Rel-20 6GR-WUS operation in RRC states – Xin (vivo)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600046	On WUS operation in different RRC states	Nokia

R1-2600061	Discussion on 6G WUS Operation in RRC States	FUTUREWEI

R1-2600126	Discussion on WUS operation in RRC states for 6GR	Spreadtrum, UNISOC

R1-2600158	WUS operation in RRC states	Huawei, HiSilicon

R1-2600202	Discussion on 6G WUS operation in different RRC states	OPPO

R1-2600216	WUS operation in RRC states	Ericsson

R1-2600235	Discussion on DL-WUS operation in RRC states	TCL

R1-2600313	Discussion on WUS operation in RRC states	CATT

R1-2600403	Discussion on the DL WUS for 6GR	CMCC

R1-2600443	Discussion on Downlink WUS in RRC states for 6GR	Xiaomi

R1-2600458	Discuss on DL WUS operation	ZTE Corporation, Sanechips

R1-2600518	Discussions on 6GR DL WUS operation in RRC states	vivo

R1-2600532	WUS operation in RRC states for 6GR	InterDigital, Inc.

R1-2600557	Discussion on DL WUS operation in RRC states for 6GR	LG Electronics

R1-2600610	Initial views on DL WUS in RRC States	Ofinno

R1-2600669	Discussion on WUS operation in RRC states	NEC

R1-2600707	Discussion on WUS operation in RRC states	Panasonic

R1-2600770	Discussion on WUS operation in RRC states	Samsung

R1-2600798	WUS operation in RRC states	Lenovo

R1-2600842	6G DL WUS operation in RRC states	Apple

R1-2600929	Discussion on WUS operation in RRC states	Sharp

R1-2601016	Discussion on WUS operation in RRC states	ETRI

R1-2601141	Discussion on WUS operation in RRC states	Sony

R1-2601196	Discussion on WUS operation in RRC states	NTT DOCOMO, INC

R1-2601210	Discussion on WUS operation in RRC states	Google

R1-2601243	WUS operation in RRC states	MediaTek Inc.

R1-2601286	DL WUS Operation	Qualcomm Incorporated

R1-2601367	Considerations for design and/or operation of WUS	NICT

R1-2601421	Discussion on WUS operation in RRC states for 6G Radio	WILUS Inc.

Uplink WUS and operation

Note 1: Identify the feasibility and necessity of uplink WUS, and schemes/mechanisms thar are different from leveraging the of the design of other agendas, etc

[124-R20-6GR-Uplink WUS] Email discussion on Rel-20 6GR-Uplink WUS– Seonwook (LGE)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-2600047	On Uplink WUS and corresponding operation	Nokia

R1-2600062	Discussion on 6G Uplink WUS and Operation	FUTUREWEI

R1-2600127	Discussion on uplink WUS and operation for 6GR	Spreadtrum, UNISOC

R1-2600159	UL-WUS and Operation	Huawei, HiSilicon

R1-2600203	Discussion on 6GR UL WUS and operations	OPPO

R1-2600217	Uplink WUS and operation	Ericsson

R1-2600236	Discussion on uplink WUS design and operation	TCL

R1-2600314	Discussion on uplink WUS and operation	CATT

R1-2600404	Discussion on uplink WUS and operation	CMCC

R1-2600444	Discussion on Uplink WUS and operation for 6GR	Xiaomi

R1-2600459	Discuss on UL WUS and operation	ZTE Corporation, Sanechips

R1-2600519	Discussions on 6GR uplink WUS and operation	vivo

R1-2600533	Uplink WUS and operation for 6GR	InterDigital, Inc.

R1-2600558	Discussion on UL WUS and operation for 6GR	LG Electronics

R1-2600570	IMU Views on Uplink Wake-Up Signal (UL-WuS)	IMU

R1-2600586	Discussion on UL-WUS Aspects in 6G	NEC

R1-2600611	Initial views on UL WUS	Ofinno

R1-2600771	Uplink WUS and operation	Samsung

R1-2600775	Uplink WUS and operation	Tejas Network Limited

R1-2600843	On 6G UL WUS and operation	Apple

R1-2600930	Study on uplink WUS and operation for 6GR	Sharp

R1-2601017	Discussion on uplink WUS and operation for 6GR	ETRI

R1-2601081	Uplink WUS and operation for 6GR	Lenovo

R1-2601142	Discussion on the Uplink WUS and operation	Sony

R1-2601197	Discussion on Uplink WUS and operation	NTT DOCOMO, INC

R1-2601211	Discussion on uplink WUS and operation	Google

R1-2601244	Uplink WUS and operation	MediaTek Inc.

R1-2601287	UL WUS Design and Operation	Qualcomm Incorporated

R1-2601374	Discussion on UL WUS	ASUSTeK

R1-2601402	Discussion on Uplink WUS and operation	CEWiT

R1-2601446	Uplink WUS Operation	Fraunhofer IIS, Fraunhofer HHI

WUS operation with other functionalities

NTN

NTN specific requirements and design for GNSS based operation

Note 1: Including common part for GNSS based operation and GNSS-less/resilient operation, as well as NTN specific evaluation assumptions.

[124-R20-6GR-NTN specific] Email discussion on Rel-20 6GR-NTN specific– Alberto (Qualcomm)

To be used for sharing updates on online/offline schedule, details on what is to be discussed in online/offline sessions, tdoc number of the moderator summary for online session, etc

R1-26xxxxx	Session Notes of AI 10.7.1	Ad-Hoc Chair (Ericsson)

R1-2600048	On NTN specific requirements and design for GNSS based operation in 6GR	Nokia

R1-2600063	Discussion on 6G NTN	FUTUREWEI

R1-2600128	Discussion on 6GR NTN specific requirements and design for GNSS based operation	Spreadtrum, UNISOC

R1-2600160	Requirements and Design for 6G NTN	Huawei, HiSilicon

R1-2600204	Discussion on 6GR NTN for GNSS based operation	OPPO

R1-2600254	Considerations on 6G NTN	THALES

R1-2600266	Discussion on NTN for 6G	ZTE Corporation, Sanechips

R1-2600315	NTN specific requirements and design for GNSS based operation	CATT

R1-2600343	NTN Specific Requirements & Design for GNSS Based Operation for 6GR	Tejas Network Limited

R1-2600405	Discussion on NTN specific requirements and design for GNSS based operation	CMCC

R1-2600445	6GR NTN specific requirements and design for GNSS based operation	Xiaomi

R1-2600448	NTN specific requirements and design for GNSS based operation	TCL

R1-2600520	Discussions on NTN specific requirements and design for GNSS based operation for 6GR	vivo

R1-2600582	NTN specific requirements and design for GNSS based operation for 6GR	InterDigital, Inc.

R1-2600679	Discussion on NTN specific requirements and design for GNSS based operation	NEC

R1-2600704	Discussion on NTN specific requirements and design for GNSS based operation	China Telecom

R1-2600712	Discussion on NTN specific requirements and design for GNSS based operation	Fraunhofer IIS, Fraunhofer HHI

R1-2600772	Discussion on NTN specific requirements and design for GNSS based operation	Samsung

R1-2600807	Design and requirements for GNSS based NTN operation	Amazon Web Services

R1-2600844	On NTN specific requirements and design for GNSS based operation for 6GR	Apple

R1-2600905	Discussion on NTN specific requirements and design for GNSS based operation	MediaTek Inc.

R1-2600931	Discussion on NTN in 6G	Sharp

R1-2600958	Discussion on NTN specific requirements and design for GNSS based operation	Lenovo

R1-2600964	Discussion on NTN specific design for GNSS based operation	LG Electronics

R1-2600972	Discussion on requirement and design for 6GR NTN	Panasonic

R1-2601018	On the GNSS-based NTN operation for 6GR	ETRI

R1-2601062	An initial view on 6GR NTN	Ericsson

R1-2601078	Positioning, Navigation and Timing (PNT) in 6GR NTN	Airbus, ESA, Fraunhofer IIS, Thales, Iridium, Novamint, Sateliot, TNO, SES, Eutelsat

R1-2601093	Discussion on NTN specific requirements	Ofinno

R1-2601143	On 6G NTN Requirements and Design	Sony

R1-2601198	Discussion on NTN specific requirements and design for GNSS based operation	NTT DOCOMO, INC.

R1-2601288	NTN specific requirements and design for GNSS based operations	Qualcomm Incorporated

R1-2601320	Discussion on NTN specific requirements and design for GNSS based operation	Google Korea LLC

R1-2601403	Discussion on 6GR NTN specific requirements and design	CEWiT

R1-2601412	Discussion on NTN specific requirements and design	CSCN

R1-2601452	Discussion on NTN specific requirements and design	CSCN

(Revision of R1-2601452)

NTN specific requirements and design for GNSS-less/resilient operation

Placeholder only. No contributions before RAN1#126.

R1-2600136	Discussion on NR-NTN GNSS resilience	SageRAN

Sensing

Note 1: Including PHY functionalities and procedures for ISAC

Placeholder only. No contributions before RAN1#124b.

Evaluations

Note 1: Including deployment scenarios, performance evaluation, and potential extension of channel model, if necessary, for targeted use cases.

Placeholder only. No contributions before RAN1#124b.

Aspects of integration with communication

Note 1: Including proposals for reusing and dedicated reference signal based on waveforms for communications, measurement and report for different use cases, etc. (could be part of AI 10.5.3)

Placeholder only. No contributions before RAN1#124b.

Waveform for sensing

Placeholder only. No contributions before RAN1#124b.

AI/ML for RAN#111

Note 1: Considering the spirit of RP-253864, RAN1 will provide a preliminary assessment about all available use cases based on the discussion in the past three meetings and send LS to report to RANP. No additional company contributions are needed. Only FL summary is allowed based on all that we have already had at hand.

R1-2600773	On AI/ML use cases for 6GR	Moderator (Samsung)

R1-2600986	Observations and agreements for AI/ML in 6GR interface	Moderator (Samsung)

R1-2600987	Draft LS on 6GR AI/ML use cases	Moderator (Samsung)

Closing of the meeting (Day 5, 16:00 pm at the latest)