Please enter the search related information in the fields below. Partial information works, e.g. "SP-21
" in the "tdoc" field lists all TSG SA documents from 2021. Regular expressions mostly work in all fields (e.g. "2[34].501
" in the "Spec" field lists all documents related to 23.501 and 24.501. Capitalization is disregarded, i.e. "3GPP
" gives the same results as "3gpp
".
Download results in JSON format
tdoc | Title | Type / Revs | Source | Spec / CR | S/WID | Release | Meeting | Status | Links |
---|---|---|---|---|---|---|---|---|---|
R1-2200998 | UE Procedures for UCI Multiplexing and Prioritization | discussion | Ericsson |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |||
R1-2200999 | Interaction of MAC and PHY for Intra-UE Multiplexing/Prioritization | discussion | Ericsson |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |||
R1-2201000 | Physical Layer Intra-UE Multiplexing/Prioritization and UL Skipping | discussion | Ericsson |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |||
R1-2201001 | Resolving Overlapping SPS HARQ-ACK with Repetition | discussion | Ericsson |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |||
R1-2201075 | Discussion on SRS resource indication for Type 1 CG | discussion | vivo | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |
R1-2201076 | Draft 38.214 CR on Parameter Indication for Type 1 CG | draftCR | vivo | NR_L1enh_URLLC-Core | Rel-17 |
R1-108-e AI: 7.2.5 |
withdrawn | [WTS] [JSN] | |
R1-2201160 | Discussion on UE procedures for UCI multiplexing and prioritization | discussion | ZTE | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |
R1-2201293 | Discussion and draft CR on scheduling and HARQ enhancement | draftCR | OPPO | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |
R1-2201294 | Remaining issues on intra-UE prioritization and multiplexing | discussion | OPPO |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |||
R1-2201326 | Discussion on intra-UE multiplexing/prioritization for eURLLC | discussion | CATT |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |||
R1-2201402 | [Draft CR] Correction on UE procedure for intra-UE prioritization/multiplexing | draftCR | Nokia, Nokia Shanghai Bell | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |
R1-2201403 | Clarification on HARQ-ACK feedback of multiple SPS configurations with PUCCH repetition | discussion | Nokia, Nokia Shanghai Bell |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |||
R1-2201624 | Corrections on SRS | discussion | Huawei, HiSilicon | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
noted | [WTS] [JSN] | |
R1-2201625 | Remaining issues on UL prioritization and UL skipping | discussion | Huawei, HiSilicon | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |
R1-2201626 | Remaining issues on UCI multiplexing and prioritization | discussion | Huawei, HiSilicon | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |
R1-2201627 | Remaining issues on UL prioritization cases related to SP-CSI | discussion | Huawei, HiSilicon | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |
R1-2201656 | Clarification on HARQ-ACK for SPS PDSCH | discussion | Ericsson Inc. |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |||
R1-2201756 | Remaining issues on intra-UE multiplexing/prioritization for eURLLC | discussion | Apple |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |||
R1-2201821 | 38.213 corrections on RRC parameter for URLLC | draftCR | ASUSTeK | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
endorsed | [WTS] [JSN] | |
R1-2201823 | 38.214 corrections on RRC parameter for URLLC | draftCR | ASUSTeK | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
endorsed | [WTS] [JSN] | |
R1-2201992 | Remaining issues on intra-UE multiplexing/prioritization | discussion | Samsung |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |||
R1-2202120 | Draft CR on SRS resource set trigger for DCI format 2_3 |
draftCR revised to R1-2202680 |
Qualcomm Incorporated | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
revised | [WTS] [JSN] | |
R1-2202188 | Corrections on time domain resource allocation procedure for a PUSCH scheduled by RAR UL grant or by DCI format 0_0 |
draftCR revised to R1-2202700 |
Sharp | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
revised | [WTS] [JSN] | |
R1-2202439 | Corrections on BWP switching using DCI format 0_2/1_2 | discussion | Huawei, HiSilicon | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
not treated | [WTS] [JSN] | |
R1-2202570 | Summary of preparation phase email discussion for Rel-16 eURLLC | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
noted | [WTS] [JSN] | |
R1-2202629 | Summary#1 of email discussion [108-e-R16-URLLC-05] Miscellaneous corrections on Rel-16 URLLC |
discussion revised to R1-2202630 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
revised | [WTS] [JSN] | |
R1-2202630 | Final summary of email discussion [108-e-R16-URLLC-05] Miscellaneous corrections on Rel-16 URLLC |
discussion revision of R1-2202629 |
Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
noted | [WTS] [JSN] | |
R1-2202680 | Correction on determination of SRS resource set triggered by DCI format 2_3 |
CR revision of R1-2202120 |
Moderator (Huawei), HiSilicon, Qualcomm | 38.214 16.8.0 CR#238 catF | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
agreed | [WTS] [JSN] |
R1-2202681 | Correction on determination of SRS resource set triggered by DCI format 2_3 | CR | Moderator (Huawei), HiSilicon, Qualcomm | 38.214 17.0.0 CR#239 catA | NR_L1enh_URLLC-Core | Rel-17 |
R1-108-e AI: 7.2.5 |
agreed | [WTS] [JSN] |
R1-2202700 | Corrections on time domain resource allocation procedure for a PUSCH scheduled by RAR UL grant or by fallbackRAR UL grant |
CR revision of R1-2202188 |
Moderator (Sharp), Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Apple, ZTE | 38.214 16.8.0 CR#243 catF | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
agreed | [WTS] [JSN] |
R1-2202701 | Corrections on time domain resource allocation procedure for a PUSCH scheduled by RAR UL grant or by fallbackRAR UL grant | CR | Moderator (Sharp), Nokia, Nokia Shanghai Bell, Huawei, HiSilicon, Apple, ZTE | 38.214 17.0.0 CR#244 catA | NR_L1enh_URLLC-Core | Rel-17 |
R1-108-e AI: 7.2.5 |
agreed | [WTS] [JSN] |
R1-2202718 | Summary of [108-e-R16-URLLC-06]: Corrections on time domain resource allocation procedure for a PUSCH scheduled by RAR UL grant | discussion | Moderator (Sharp) | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
noted | [WTS] [JSN] | |
R1-2202729 | Summary of [108-e-NR-L1enh-URLLC-02] Discussion on remaining issues on UL prioritization and UL skipping | discussion | Moderator (vivo) | NR_IIOT-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
noted | [WTS] [JSN] | |
R1-2202730 | Draft Reply LS on Intra UE Prioritization Scenario |
LS out LS is reply to R2-2008599, R2-2106746 LS To: RAN2 revised to R1-2202734 |
Moderator (vivo) | NR_IIOT-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
revised | [WTS] [JSN] | |
R1-2202733 | Summary of [108-e-R16-URLLC-04] Issue#6: Discussion on determination of SRS resource set triggered by DCI format 2_3 | discussion | Moderator (Huawei) | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
noted | [WTS] [JSN] | |
R1-2202734 | Reply LS on Intra UE Prioritization Scenario |
LS out LS is reply to R2-2008599, R2-2106746 LS To: RAN2 revision of R1-2202730 |
RAN1, vivo | NR_IIOT-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
approved | [WTS] [JSN] | |
R1-2202772 | Summary of [108-e-R16-URLLC-03] Issue#4: Clarification on HARQ-ACK feedback of multiple SPS configurations with PUCCH repetition | discussion | Moderator (Nokia) | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
noted | [WTS] [JSN] | |
R1-2202916 | Summary of email discussion [108-e-R16-URLLC-01] on UCI multiplexing and prioritization in Rel-16 | discussion | Moderator (Apple) | NR_L1enh_URLLC-Core | Rel-16 |
R1-108-e AI: 7.2.5 |
noted | [WTS] [JSN] |
38 documents (0.35441899299622 seconds)