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-1912095 | Remaining issues on detecting uplink LBT failure for NR-U | discussion | OPPO |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |||
| R2-1912096 | Uplink LBT failure revoery for NR-U | discussion | OPPO |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |||
| R2-1912177 | Remaining Issues on Uplink LBT Failure | discussion | vivo |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |||
| R2-1912178 | Issue on the Autonomous BWP Switching in NR-U |
discussion revised to R2-1914366 |
vivo |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |||
| R2-1912243 | LBT Failures Handling in Non-Connected State | discussion | Spreadtrum Communications, Huawei, HiSilicon |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |||
| R2-1912244 | Inconsecutive UL LBT Failures Handling | discussion | Spreadtrum Communications |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |||
| R2-1912304 | Details of the Uplink LBT failure mechanism | discussion | Qualcomm Incorporated |
R2-107 AI: 6.2.2.2 |
noted | [WTS] [JSN] | |||
| R2-1912474 | Recovery of consistent UL LBT failures | discussion | Samsung | NR_unlic-Core | Rel-16 |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |
| R2-1912569 | Handling UL LBT Failures in NR-U | discussion | PANASONIC R&D Center Germany |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |||
| R2-1912625 | Detecting and Handling of UL LBT failures | discussion | Intel Corporation | NR_unlic-Core | Rel-16 |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |
| R2-1912684 | Impact of systematic LBT failure on UL transmission procedure |
discussion revision of R2-1910099 |
Lenovo, Motorola Mobility | NR_unlic-Core | Rel-16 |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |
| R2-1912889 | Handling UL LBT Failures in MAC | discussion | InterDigital | NR_unlic-Core | Rel-16 |
R2-107 AI: 6.2.2.2 |
noted | [WTS] [JSN] | |
| R2-1912937 | Further consideration on consistent LBT failures | discussion | CMCC | Rel-16 |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | ||
| R2-1912988 | Consecutive failed connection attempts in NR-U | discussion | Nokia, Nokia Shanghai Bell | NR_unlic-Core | Rel-16 |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |
| R2-1913029 | UL LBT failure handling | discussion | Huawei, HiSilicon | Rel-16 |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | ||
| R2-1913064 | Handling of consistent UL LBT failures during HO |
discussion revised to R2-2000737 |
ITRI | NR_unlic-Core |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | ||
| R2-1913130 | Problems in BFD-inspired detection mechanism for consistent UL LBT failures | discussion | LG Electronics Inc. | NR_unlic-Core |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | ||
| R2-1913162 | UE behavior upon consistenB2:AE10t UL LBT failures | discussion | Fujitsu | NR_unlic-Core | Rel-16 |
R2-107 AI: 6.2.2.2 |
withdrawn | [WTS] [JSN] | |
| R2-1913260 | On consistent LBT failures |
discussion revised to R2-1915544 |
MediaTek Inc. | NR_unlic-Core | Rel-16 |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |
| R2-1913287 | Remaining issues on UL LBT | discussion | Nokia, Nokia Shanghai Bell | NR_unlic-Core | Rel-16 |
R2-107 AI: 6.2.2.2 |
noted | [WTS] [JSN] | |
| R2-1913293 | UE behavior upon consisten UL LBT failures | discussion | Fujitsu | NR_unlic-Core | Rel-16 |
R2-107 AI: 6.2.2.2 |
withdrawn | [WTS] [JSN] | |
| R2-1913294 | UE behavior upon consistent UL LBT failures | discussion | Fujitsu | NR_unlic-Core | Rel-16 |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |
| R2-1913375 | Recovery from consistent LBT failures | discussion | ZTE Corporation, Sanechips | Rel-16 |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | ||
| R2-1913479 | Consistent LBT failure detection | discussion | Google Inc. | Rel-16 |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | ||
| R2-1913504 | Handling LBT failures | discussion | Ericsson | NR_unlic-Core | Rel-16 |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |
| R2-1913649 | Remaining Issues on Persistent LBT Failures in NRU | discussion | Charter Communications, Inc |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |||
| R2-1913913 | Further considerations on handling UL LBT failures | discussion | ETRI | NR_unlic-Core | Rel-16 |
R2-107 AI: 6.2.2.2 |
not treated | [WTS] [JSN] | |
| R2-1914054 | Summary of discussion on UL LBT | discussion | InterDigital |
R2-107 AI: 6.2.2.2 |
noted | [WTS] [JSN] |
28 documents (0.35448598861694 seconds)