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 |
---|---|---|---|---|---|---|---|---|---|
R2-1914411 | Intra-UE prioritization framework considering RAN1/RAN2 agreements |
discussion revised to R2-2000486 |
CATT | NR_IIOT-Core | Rel-16 |
R2-108 AI: 6.7.3.2 |
noted | [WTS] [JSN] | |
R2-1914413 | MAC PDU Priority Determination |
discussion revision of R2-1912211 |
CATT | NR_IIOT-Core | Rel-16 |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | |
R2-1914414 | Equal-priority Handling |
discussion revision of R2-1912212 |
CATT | NR_IIOT-Core | Rel-16 |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | |
R2-1914415 | The Prioritization between MAC CEs and UL Data |
discussion revision of R2-1912216 |
CATT | NR_IIOT-Core | Rel-16 |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | |
R2-1914758 | Main functions of intra-UE data-data prioritization | discussion | Ericsson | NR_IIOT-Core |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | ||
R2-1914878 | Intra-UE Prioritization for Overlapping PUSCHs | discussion | InterDigital | FS_NR_IIOT | Rel-16 |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | |
R2-1914879 | L2 aspects of priority level indication | discussion | InterDigital | FS_NR_IIOT | Rel-16 |
R2-108 AI: 6.7.3.2 |
noted | [WTS] [JSN] | |
R2-1914969 | Discussion on the UE handling for the equal priority of uplink grants |
discussion revision of R2-1905762 |
vivo |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | |||
R2-1915018 | Equal priority handling for CG and CG collision | discussion | Spreadtrum Communications |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | |||
R2-1915097 | Intra-UE prioritization involving configured grant | discussion | OPPO | Rel-16 |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | ||
R2-1915139 | Solution for intra-UE prioritization | discussion | Huawei, HiSilicon | NR_IIOT-Core |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | ||
R2-1915342 | Priority Value of an Uplink Grant | discussion | Samsung | NR_IIOT-Core | Rel-16 |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | |
R2-1915491 | Intra-UE Prioritization with Per-Grant Priority Indication: MAC Perspectives | discussion | Nokia, Nokia Shanghai Bell | NR_IIOT-Core | Rel-16 |
R2-108 AI: 6.7.3.2 |
noted | [WTS] [JSN] | |
R2-1915742 | Intra UE prioritization of UL Data and Data | discussion | Intel Corporation | NR_IIOT-Core | Rel-16 |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | |
R2-1915830 | MAC prioritization for Intra-UE prioritization | discussion | Qualcomm Incorporated |
R2-108 AI: 6.7.3.2 |
noted | [WTS] [JSN] | |||
R2-1915918 | Remaining issues in intra-UE prioritization | discussion | LG Electronics Inc. | NR_IIOT-Core |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | ||
R2-1916000 | Handling for CG resource collision of equal priority | discussion | CMCC | NR_IIOT-Core | Rel-16 |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | |
R2-1916019 | Discussion on RRC configurations of L1 parameters for eURLLC | discussion | Huawei, HiSilicon | NR_L1enh_URLLC-Core | Rel-16 |
R2-108 AI: 6.7.3.2 |
noted | [WTS] [JSN] | |
R2-1916076 | Consideration on HARQ conflict between configured grant and dynamic grant |
discussion revision of R2-1913047 |
ZTE Corporation, Sanechips | NR_IIOT-Core | Rel-16 |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | |
R2-1916185 | Impacts of L1 priorities on data prioritization | discussion | Fujitsu | NR_IIOT-Core | Rel-16 |
R2-108 AI: 6.7.3.2 |
available | [WTS] [JSN] | |
R2-1916526 | Summary of Offline 52: TP for LCH-priority based Data-Data and SR-Data prioritization | draftCR | Samsung | NR_IIOT-Core | Rel-16 |
R2-108 AI: 6.7.3.2 |
noted | [WTS] [JSN] |
21 documents (0.37187910079956 seconds)