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 |
|---|---|---|---|---|---|---|---|---|---|
| R1-2000197 | Corrections on the channel access procedure in TS 37.213 | discussion | Huawei, HiSilicon | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | |
| R1-2000255 | Remaining issues on the channel access procedures | discussion | vivo | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
withdrawn | [WTS] [JSN] | ||
| R1-2000309 | Remaining issues on the channel access procedures | discussion | vivo | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | ||
| R1-2000392 | Maintenance on the channel access procedure for NR-U | discussion | ZTE, Sanechips |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | |||
| R1-2000411 | Remaining Issues on Channel Access Procedures for NR-U | discussion | Nokia, Nokia Shanghai Bell |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | |||
| R1-2000437 | Remaining issues on channel access for NR-U operation | discussion | MediaTek Inc. |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | |||
| R1-2000470 | Discussion on the remaining issues of channel access procedure | discussion | OPPO | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | ||
| R1-2000544 | Remaining issues on channel access procedures | discussion | Fujitsu | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | ||
| R1-2000610 | Channel access procedures for NR-U | discussion | Samsung | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | |
| R1-2000663 | Remaining issues of channel access procedure for NR-U | discussion | LG Electronics | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | |
| R1-2000724 | Channel access mechanism for NR-unlicensed | discussion | Intel Corporation | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | ||
| R1-2000767 | Remaining issues on CP extension | discussion | NEC | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | |
| R1-2000799 | Feature Lead’s Summary on Channel Access Procedures |
discussion revised to R1-2001202 |
Nokia |
R1-ah-37786 AI: 7.2.2.2.1 |
revised | [WTS] [JSN] | |||
| R1-2000826 | Channel access procedures | discussion | Ericsson | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | |
| R1-2000873 | Remaining issues and corrections on channel access procedure for NR-U | discussion | Sharp | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | |
| R1-2000912 | Channel access procedures for NR-U | discussion | NTT DOCOMO, INC. | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | ||
| R1-2000934 | Remaining issues on channel access procedure for NR-U | discussion | WILUS Inc. | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | |
| R1-2000956 | TP for Channel access procedures for NR unlicensed | discussion | Qualcomm Incorporated | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | |
| R1-2001088 | Corrections to channel access procedures | other | Futurewei |
R1-ah-37786 AI: 7.2.2.2.1 |
not treated | [WTS] [JSN] | |||
| R1-2001202 | Feature Lead’s Summary#2 on Channel Access Procedures |
discussion revision of R1-2000799 |
Nokia | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
noted | [WTS] [JSN] | |
| R1-2001311 | Outcome of email discussions [100e-NR-unlic-NRU-ChAccess-01] | discussion | Nokia | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
endorsed | [WTS] [JSN] | |
| R1-2001312 | Outcome of email discussions [100e-NR-unlic-NRU-ChAccess-02] |
discussion revised to R1-2001482 |
Nokia | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
revised | [WTS] [JSN] | |
| R1-2001313 | Outcome of email discussions [100e-NR-unlic-NRU-ChAccess-03] | discussion | Nokia | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
endorsed | [WTS] [JSN] | |
| R1-2001314 | Outcome of email discussions [100e-NR-unlic-NRU-ChAccess-04] | discussion | Nokia | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
endorsed | [WTS] [JSN] | |
| R1-2001396 | TPs for CP extension from email discussion [100e-NR-unlic-NRU-ChAccess-03] | discussion | Nokia | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
endorsed | [WTS] [JSN] | |
| R1-2001397 | Reply LS on consistent Uplink LBT failure detection mechanism |
LS out LS is reply to R2-1916380 LS To: RAN2 |
RAN1, Nokia | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
approved | [WTS] [JSN] | |
| R1-2001482 | Outcome of email discussions [100e-NR-unlic-NRU-ChAccess-02] |
discussion revision of R1-2001312 |
Nokia | NR_unlic-Core | Rel-16 |
R1-ah-37786 AI: 7.2.2.2.1 |
endorsed | [WTS] [JSN] |
27 documents (0.32755303382874 seconds)