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-2004419 | Discussion on LBT Failure Detection and Recovery During HO with DAPS and CHO | discussion | vivo |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |||
| R2-2004420 | LBT Impacts on the TCI State Switching | discussion | vivo |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |||
| R2-2004421 | [Draft] Reply LS on UE Declaring Beam Failure due to LBT Failures During Active TCI Switching |
LS out LS To: RAN4 |
vivo | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |
| R2-2004425 | Clarification on when to use one-octet or four-octet LBT failure MAC CE | discussion | Samsung | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |
| R2-2004426 | Clarification on the variable LBT_COUNTER | discussion | Samsung | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |
| R2-2004549 | Remaining issues on UL LBT failure | discussion | OPPO | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |
| R2-2004598 | Discussion about LBT failure and beam failure relation | discussion | Nokia, Nokia Shanghai Bell | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |
| R2-2004599 | Draft Reply LS on UE declaring beam failure due to LBT failures |
LS out LS is reply to R4-2005365 LS To: TSG RAN WG4 |
Nokia, Nokia Shanghai Bell | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |
| R2-2004616 | UE declaring beam failure due to LBT failures during active TCI switching | discussion | ZTE Corporation, Sanechips |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |||
| R2-2004659 | UL LBT failures interactions with DAPS and CHO | discussion | Intel Corporation | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |
| R2-2004660 | Draft CR for UL LBT failures under DAPS handover | draftCR | Intel Corporation | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |
| R2-2004671 | Beam failure declaration due to TC switching failure | discussion | Intel Corporation | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |
| R2-2004974 | LBT failure recovery for DAPS and CHO | discussion | Huawei, HiSilicon | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |
| R2-2004975 | Remaining issue on 2-step random access for NRU | discussion | Huawei, HiSilicon | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |
| R2-2004976 | DraftCR on pending status for HARQ process in NR-U |
discussion revised to R2-2005053, R2-2005054 |
Huawei, HiSilicon | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
revised | [WTS] [JSN] | |
| R2-2005049 | Consistent LBT failure in DAPS | discussion | Spreadtrum Communications |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |||
| R2-2005050 | Consistent LBT failure in CHO | discussion | Spreadtrum Communications |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |||
| R2-2005053 | Text Proposal |
discussion revision of R2-2004976 |
Huawei, HiSIlicon | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
withdrawn | [WTS] [JSN] | ||
| R2-2005054 | Text proposal for the pending status for HARQ process in NR-U |
discussion revision of R2-2004976 |
Huawei, HiSilicon |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |||
| R2-2005329 | LBT failure detection and recovery for DAPS and CHO | discussion | Ericsson | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |
| R2-2005330 | UE declaring beam failure due to LBT failures during active TCI switching | discussion | Ericsson | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |
| R2-2005333 | Report on [Post109bis-e][935]][NR-U] MAC open issues (Ericsson) | discussion | Ericsson | NR_unlic-Core | Rel-16 |
R2-ah-38105 AI: 6.2.2 |
noted | [WTS] [JSN] | |
| R2-2005550 | Handling of UL LBT failure for DAPS and CHO | discussion | Qualcomm Incorporated |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |||
| R2-2005713 | Consideration on DAPS and CHO in NR-U | discussion | ZTE Corporation, Sanechips |
R2-ah-38105 AI: 6.2.2 |
available | [WTS] [JSN] | |||
| R2-2006084 | Summary of NR-U User plane | discussion | Lenovo |
R2-ah-38105 AI: 6.2.2 |
noted | [WTS] [JSN] |
25 documents (0.36857891082764 seconds)