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-2002582 Clarification on the LBT Failure Indication discussion vivo R2-ah-38104

AI: 6.2.2

not treated [WTS] [JSN]
R2-2002583 Discussion on the UE Processing Time for Autonomous Retransmission discussion vivo R2-ah-38104

AI: 6.2.2

not treated [WTS] [JSN]
R2-2002613 Clash between NR-U and IIoT for the configured grant discussion Samsung NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

not treated [WTS] [JSN]
R2-2002614 Prioritization between initial TX and re-TX on CG in NR-U CR Samsung 38.321 16.0.0 CR#706 catF NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

not treated [WTS] [JSN]
R2-2002837 Discussion incoming RAN1 LS on LBT failure indication discussion OPPO NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

not treated [WTS] [JSN]
R2-2002848 Remaining critical issues for LBT failures discussion Qualcomm Incorporated R2-ah-38104

AI: 6.2.2

not treated [WTS] [JSN]
R2-2002931 Stopping ongoing Random Access procedure discussion LG Electronics Inc. NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

noted [WTS] [JSN]
R2-2003004 Remaining issue on 2-step random access in NR-U discussion Huawei, HiSilicon NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

not treated [WTS] [JSN]
R2-2003005 Discussion on the MAC CE for NR-U discussion Huawei, HiSilicon NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

not treated [WTS] [JSN]
R2-2003006 Discussion on PDCCH group switching for NR-U discussion Huawei, HiSilicon NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

not treated [WTS] [JSN]
R2-2003031 Flushing HARQ buffer of the pending HARQ process in NR-U CR LG Electronics Polska 38.321 16.0.0 CR#717 catF NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

not treated [WTS] [JSN]
R2-2003050 Draft CR on LBT failure handling in MAC draftCR Nokia, Nokia Shanghai Bell NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

not treated [WTS] [JSN]
R2-2003409 Corrections of NR-U in 38.321 CR

revised to R2-2003875

Ericsson 38.321 16.0.0 CR#726 catF NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

revised [WTS] [JSN]
R2-2003410 UEs not supporting gap-less msgA transmission discussion Ericsson NR_unlic-Core, NR_2step_RACH-Core Rel-16 R2-ah-38104

AI: 6.2.2

not treated [WTS] [JSN]
R2-2003411 Post109e#39 NR-U MAC open issues discussion

revised to R2-2003951

Ericsson NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

revised [WTS] [JSN]
R2-2003498 MsgA PUSCH LBT failure impact discussion CMCC Rel-16 R2-ah-38104

AI: 6.2.2

not treated [WTS] [JSN]
R2-2003875 Corrections of NR operating with shared spectrum channel access in 38.321 CR

revision of R2-2003409

revised to R2-2005331

Ericsson 38.321 16.0.0 CR#7261 catF NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

endorsed [WTS] [JSN]
R2-2003951 Post109e#39 NR-U MAC open issues discussion

revision of R2-2003411

Ericsson NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

noted [WTS] [JSN]
R2-2003952 Summary of NR-U User plane discussion InterDigital R2-ah-38104

AI: 6.2.2

noted [WTS] [JSN]
R2-2003966 [Draft] reply LS on UL LBT failure recovery for the target cell LS out

LS is reply to R4-2002282

LS To: RAN4

revised to R2-2003972

InterDigital NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

revised [WTS] [JSN]
R2-2003972 [Draft] reply LS on UL LBT failure recovery for the target cell LS out

LS is reply to R4-2002282

LS To: RAN4

revision of R2-2003966

revised to R2-2003973

InterDigital NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

revised [WTS] [JSN]
R2-2003973 Reply LS on UL LBT failure recovery for the target cell LS out

LS is reply to R4-2002282

LS To: RAN4

revision of R2-2003972

RAN2 NR_unlic-Core Rel-16 R2-ah-38104

AI: 6.2.2

approved [WTS] [JSN]

22 documents (0.34598207473755 seconds)