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-2004586 Impacts of independent configuration of intra-UE prioritization in PHY and MAC layers discussion CATT NR_IIOT-Core R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2004587 Considerations on SR Prioritization discussion CATT NR_IIOT-Core R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2004588 MAC TP addressing PHY limitations for equal-priority collisions discussion CATT NR_IIOT-Core R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2004738 Priority of SR triggered by BFR or LBT failure discussion vivo, ZTE corporation, OPPO R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2004739 Text proposal for the UE autonomous retransmission discussion vivo, Samsung R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2004885 Avoid providing second MAC PDU with the same L1 priority to PHY discussion SHARP Corporation R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2004890 On prioritization handling for PUSCH and PUSCH with the same L1 priority discussion Fujitsu NR_IIOT-Core Rel-16 R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2004891 On prioritization handling for SR and PUSCH with the same L1 priority discussion Fujitsu NR_IIOT-Core Rel-16 R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2004900 Handling of autonomous transmissions following a BWP switch discussion Lenovo, Motorola Mobility NR_IIOT-Core Rel-16 R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2004922 Intra-UE Prioritization with the Same L1-Priority discussion Nokia, Nokia Shanghai Bell NR_IIOT-Core Rel-16 R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2004923 Handling of Absence of PHY-based or LCH-based prioritization configuration discussion Nokia, Nokia Shanghai Bell NR_IIOT-Core Rel-16 R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2004959 On interaction between LCH-based and PHY-based prioritization discussion Ericsson NR_IIOT-Core R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2004960 Remaining issues on intra-UE priortization discussion Ericsson NR_IIOT-Core R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2004961 CG/SPS remaining issues discussion Ericsson R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2005070 Discussion on LCH-based prioritization and PHY-based prioritization discussion Huawei, HiSilicon NR_IIOT-Core Rel-16 R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2005124 Consideration on the intra-UE multiplexing involved SR discussion ZTE, Sanechips NR_IIOT-Core Rel-16 R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2005149 Remaining issues of Intra-UE prioritizations discussion Sony NR_IIOT-Core Rel-16 R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2005337 Open issues on intra-UE prioritization discussion OPPO NR_IIOT-Core Rel-16 R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2005503 Intra-UE prioritization with the same L1 priority discussion LG Electronics Inc. NR_IIOT-Core Rel-16 R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2005565 SR-data prioritization regarding MAC CE-triggered SR discussion ASUSTeK NR_IIOT-Core Rel-16 R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2005566 Handling UL grant prioritization with non-overlapping PUSCH duration discussion

revision of R2-2003648

ASUSTeK NR_IIOT-Core Rel-16 R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2005647 MAC Impact of MAC-PHY Misalignment in Prioritization discussion Samsung NR_IIOT-Core Rel-16 R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]
R2-2005648 Correction to Prioritization between SR and Random Access Related Uplink Grant discussion Samsung NR_IIOT-Core Rel-16 R2-ah-38105

AI: 6.7.3.1

available [WTS] [JSN]

23 documents (0.35260701179504 seconds)