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 |
|---|---|---|---|---|---|---|---|---|---|
| R4-2006014 | Discussion on RLM in NR-U | discussion | ZTE Corporation | NR_unlic-Core | Rel-16 |
R4-ah-38108 AI: 6.1.5. |
noted | [WTS] [JSN] | |
| R4-2006158 | On RLM requirements in NR-U | discussion | Qualcomm Incorporated | NR_unlic-Core | Rel-16 |
R4-ah-38108 AI: 6.1.5. |
noted | [WTS] [JSN] | |
| R4-2006858 | Discussion on RLM requirement for NR-U | discussion | MediaTek inc. | NR_unlic-Core | Rel-16 |
R4-ah-38108 AI: 6.1.5. |
noted | [WTS] [JSN] | |
| R4-2007263 | CR to 38.133: clarification of RLM requirements | CR | Nokia, Nokia Shanghai Bell | 38.133 16.3.0 CR#720 catF | NR_unlic-Core | Rel-16 |
R4-ah-38108 AI: 6.1.5. |
not pursued | [WTS] [JSN] |
| R4-2007264 | Discussion on RLM requirements in NR-U | discussion | Nokia, Nokia Shanghai Bell | NR_unlic-Core | Rel-16 |
R4-ah-38108 AI: 6.1.5. |
noted | [WTS] [JSN] | |
| R4-2007341 | On RLM for NR-U | discussion | OPPO | NR_unlic-Core | Rel-16 |
R4-ah-38108 AI: 6.1.5. |
noted | [WTS] [JSN] | |
| R4-2007387 | Beam management in NR-U | discussion | Ericsson | NR_unlic-Core | Rel-16 |
R4-ah-38108 AI: 6.1.5. |
noted | [WTS] [JSN] | |
| R4-2007388 | CR: Introduction of link recovery requirements with CCA |
CR revised to R4-2008572 |
Ericsson | 38.133 16.3.0 CR#724 catB | NR_unlic-Core | Rel-16 |
R4-ah-38108 AI: 6.1.5. |
revised | [WTS] [JSN] |
| R4-2007698 | CR on removing candidate in RLM requirements in Rel-15 | CR | Huawei, Hisilicon | 38.133 15.9.0 CR#771 catF | NR_unlic-Core | Rel-15 |
R4-ah-38108 AI: 6.1.5. |
not pursued | [WTS] [JSN] |
| R4-2007699 | CR on removing candidate in RLM requirements in Rel-16 | CR | Huawei, Hisilicon | 38.133 16.3.0 CR#772 catB | NR_unlic-Core | Rel-16 |
R4-ah-38108 AI: 6.1.5. |
not pursued | [WTS] [JSN] |
| R4-2007703 | Discussion on RLM and link recovery for NR-U | discussion | Huawei, Hisilicon | NR_unlic-Core | Rel-16 |
R4-ah-38108 AI: 6.1.5. |
noted | [WTS] [JSN] | |
| R4-2007970 | On RLM in NR-U | discussion | Ericsson | NR_unlic-Core | Rel-16 |
R4-ah-38108 AI: 6.1.5. |
noted | [WTS] [JSN] | |
| R4-2007971 | Introduction of RLM requirements for NR-U |
CR revised to R4-2008573 |
Ericsson | 38.133 16.3.0 CR#868 catB | NR_unlic-Core | Rel-16 |
R4-ah-38108 AI: 6.1.5. |
revised | [WTS] [JSN] |
| R4-2008572 | CR: Introduction of link recovery requirements with CCA |
CR revision of R4-2007388 |
Ericsson | 38.133 16.3.0 CR#7241 catB | NR_unlic-Core | Rel-16 |
R4-ah-38108 AI: 6.1.5. |
endorsed | [WTS] [JSN] |
| R4-2008573 | Introduction of RLM requirements for NR-U |
CR revision of R4-2007971 |
Ericsson | 38.133 16.3.0 CR#8681 catB | NR_unlic-Core | Rel-16 |
R4-ah-38108 AI: 6.1.5. |
endorsed | [WTS] [JSN] |
15 documents (0.36348390579224 seconds)