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-1914367 | Remaining Issues of UL LBT Failure |
discussion revised to R2-2000148 |
vivo |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | |||
R2-1914400 | Remaining issues on consistent uplink LBT failure for NR-U | discussion | OPPO | NR_unlic-Core | Rel-16 |
R2-108 AI: 6.2.2.2 |
noted | [WTS] [JSN] | |
R2-1914572 | Handling of UL LBT failures | discussion | Intel Corporation | NR_unlic-Core | Rel-16 |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-1914791 | LBT failure report on SCell | discussion | ZTE Corporation, Sanechips |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | |||
R2-1914864 | Draft LS on Uplink LBT failure indication |
LS out LS To: RAN1 revised to R2-1916371 |
Qualcomm Incorporated | NR_unlic-Core | Rel-16 |
R2-108 AI: 6.2.2.2 |
revised | [WTS] [JSN] | |
R2-1914882 | Handling UL LBT Failures | discussion | InterDigital | NR_unlic-Core | Rel-16 |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-1915015 | LBT Failures Handling in Non-Connected State |
discussion revised to R2-2000563 |
Spreadtrum Communications, Huawei, HiSilicon |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | |||
R2-1915016 | Inconsecutive UL LBT Failures Handling | discussion | Spreadtrum Communications |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | |||
R2-1915105 | UE behavior upon consistent LBT failure | discussion | Lenovo, Motorola Mobility | NR_unlic-Core | Rel-16 |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-1915141 | Handling of UL LBT failure | discussion | Huawei, HiSilicon | NR_unlic-Core |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | ||
R2-1915177 | Remaining issue on detecting UL LBT Failures | discussion | PANASONIC R&D Center Germany |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | |||
R2-1915197 | Details on determining consistent LBT failure of a BWP |
discussion revised to R2-2000904 |
CMCC | Rel-16 |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | ||
R2-1915544 | Remaining issues on consistent LBT failures |
discussion revision of R2-1913260 |
MediaTek Inc. | NR_unlic-Core | Rel-16 |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-1915765 | Remaining details of UL LBT failure mechanism | discussion | Qualcomm Incorporated |
R2-108 AI: 6.2.2.2 |
noted | [WTS] [JSN] | |||
R2-1915802 | Adapting the BFD mechanism for consistent LBT failure detection | discussion | Google Inc. | Rel-16 |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | ||
R2-1915870 | Handling consistent UL LBT failures | discussion | Ericsson | NR_unlic-Core | Rel-16 |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-1915885 | UL LBT failure detection | discussion | Nokia, Nokia Shanghai Bell, InterDigital, MediaTek, OPPO | NR_unlic-Core | Rel-16 |
R2-108 AI: 6.2.2.2 |
noted | [WTS] [JSN] | |
R2-1915886 | UL LBT failure report | discussion | Nokia, Nokia Shanghai Bell | NR_unlic-Core | Rel-16 |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-1916094 | Remaining Issues on Consistent LBT Failure Detection in NRU | discussion | Charter Communications, Inc |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | |||
R2-1916118 | Handling LBT failures for support of wideband operations | discussion | ETRI | NR_unlic-Core | Rel-16 |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-1916200 | Cell (re)selection after consecutive UL LBT failures | discussion | LG Electronics Inc | NR_unlic-Core | Rel-16 |
R2-108 AI: 6.2.2.2 |
available | [WTS] [JSN] | |
R2-1916371 | Draft LS on consistent Uplink LBT failure detection mechanism |
LS out LS To: RAN1 revision of R2-1914864 revised to R2-1916380 |
Qualcomm Incorporated | NR_unlic-Core | Rel-16 |
R2-108 AI: 6.2.2.2 |
revised | [WTS] [JSN] | |
R2-1916380 | LS on consistent Uplink LBT failure detection mechanism |
LS out LS To: RAN1 LS reply in R1-2001397 revision of R2-1916371 |
RAN2 | NR_unlic-Core | Rel-16 |
R2-108 AI: 6.2.2.2 |
approved | [WTS] [JSN] | |
R2-1916382 | Report of offline-403 - Remaining issues of consistent UL LBT failure | discussion | OPPO |
R2-108 AI: 6.2.2.2 |
noted | [WTS] [JSN] |
24 documents (0.35588097572327 seconds)