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-2003404 | Maintenance of procedure of cross-slot scheduling power saving techniques | discussion | vivo | Rel-16 |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | ||
R1-2003487 | Remaining issues on cross-slot scheduling power saving techniques | discussion | ZTE |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | |||
R1-2003519 | Remaining issues on cross-slot scheduling based power saving | discussion | Huawei, HiSilicon | NR_UE_pow_sav-Core | Rel-16 |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | |
R1-2003631 | Remaining issues on Power saving scheme with cross-slot scheduling | discussion | CATT |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | |||
R1-2003665 | Remaining issues on cross-slot scheduling adaptation | discussion | MediaTek Inc. |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | |||
R1-2003746 | Remaining details of cross-slot scheduling for power saving | discussion | Intel Corporation | Rel-16 |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | ||
R1-2003885 | Remaining issues for cross-slot scheduling | discussion | Samsung |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | |||
R1-2003958 | Remaining issues on cross-slot scheduling procedure | discussion | CMCC |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | |||
R1-2003994 | Remaining issues on cross-slot scheduling | discussion | Spreadtrum Communications | Rel-16 |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | ||
R1-2004026 | Remaining issues on procedure of cross-slot scheduling power saving techniques | discussion | LG Electronics | NR_UE_pow_sav-Core | Rel-16 |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | |
R1-2004102 | Remaining issues for cross-slot scheduling | discussion | OPPO |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | |||
R1-2004187 | Remaining issues on cross-slot scheduling for UE power saving | discussion | Sony |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | |||
R1-2004307 | Remaining issues of cross-slot scheduling for UE power saving | discussion | InterDigital |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | |||
R1-2004358 | Remaining issues for cross-slot scheduling | discussion | Ericsson |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | |||
R1-2004399 | Maintenance for procedure of cross-slot scheduling power saving techniques | discussion | NTT DOCOMO, INC. | Rel-16 |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | ||
R1-2004468 | Remaining issues in cross-slot scheduling power saving | discussion | Qualcomm Incorporated | NR_UE_pow_sav-Core | Rel-16 |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | |
R1-2004578 | Procedure of cross-slot scheduling power saving techniques | discussion | Nokia, Nokia Shanghai Bell |
R1-ah-38103 AI: 7.2.7.2 |
not treated | [WTS] [JSN] | |||
R1-2004669 | Summary#1 for Procedure of cross-slot scheduling power saving techniques |
discussion revised to R1-2004765 |
Moderator (MediaTek) | NR_UE_pow_sav-Core | Rel-16 |
R1-ah-38103 AI: 7.2.7.2 |
revised | [WTS] [JSN] | |
R1-2004765 | Summary#2 for Procedure of cross-slot scheduling power saving techniques |
discussion revision of R1-2004669 revised to R1-2004971 |
Moderator (MediaTek) | NR_UE_pow_sav-Core | Rel-16 |
R1-ah-38103 AI: 7.2.7.2 |
noted | [WTS] [JSN] | |
R1-2004971 | Summary#3 for Procedure of cross-slot scheduling power saving techniques |
discussion revision of R1-2004765 |
Moderator (MediaTek) | NR_UE_pow_sav-Core | Rel-16 |
R1-ah-38103 AI: 7.2.7.2 |
noted | [WTS] [JSN] |
20 documents (0.35599207878113 seconds)