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-2000148 | Remaining Issues of UL LBT Failure |
discussion revision of R2-1914367 |
vivo |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | |||
R2-2000415 | Remaining issues on consistent uplink LBT failure for NR-U | discussion | OPPO | NR_unlic-Core | Rel-16 |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-2000449 | Remaining issues on UL LBT failures handling | discussion | Intel Corporation | NR_unlic-Core | Rel-16 |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-2000534 | LBT failure handling considering SUL aspect | discussion | Samsung | NR_unlic-Core | Rel-16 |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-2000563 | LBT Failures Handling in Non-Connected State |
discussion revision of R2-1915015 |
Spreadtrum Communications |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | |||
R2-2000603 | SpCell LBT Failure MAC CE Delivery | discussion | Apple, vivo | NR_unlic-Core | Rel-16 |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-2000737 | Handling of consistent UL LBT failures during HO |
discussion revision of R2-1913064 |
ITRI | NR_unlic-Core |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | ||
R2-2000772 | [Eri10] SR resources for consistent LBT failure | discussion | Fujitsu | NR_unlic-Core | Rel-16 |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-2000822 | UE behavior upon consistent LBT failure | discussion | Lenovo, Motorola Mobility | NR_unlic-Core | Rel-16 |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-2000840 | Remaining issues on consistent LBT failures and BWP switching | discussion | MediaTek Inc. | NR_unlic-Core | Rel-16 |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-2000904 | On counting the LBT failure of a BWP with multiple sub-bands |
discussion revision of R2-1915197 |
CMCC | Rel-16 |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | ||
R2-2000941 | Uplink transmission upon detection of LBT failure | discussion | Nokia, Nokia Shanghai Bell | NR_unlic-Core | Rel-15 |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-2000957 | Remaining issue on handling UL LBT failure | discussion | Huawei, HiSilicon | NR_unlic-Core | Rel-16 |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-2000963 | Remaining issues on LBT failure MAC CE | discussion | Huawei, HiSilicon | NR_unlic-Core | Rel-16 |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-2000999 | The remaining issues for UL LBT failure | discussion | ZTE Corporation, Sanechips | Rel-16 |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] | ||
R2-2001207 | Handling consistent UL LBT failures | discussion | Ericsson | NR_unlic-Core |
R2-ah-37793 AI: 6.2.2.2 |
available | [WTS] [JSN] |
16 documents (0.37192702293396 seconds)