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-154250 | Report of [91#21][LTE/CAfe] Capability signalling enhancements |
report revised to R2-154895 |
Nokia Networks | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
revised | [WTS] [JSN] | |
R2-154293 | Discussion on UE capability signaling for B5C | discussion | Intel Corporation | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
available | [WTS] [JSN] | |
R2-154340 | UE CA capability signalling for B5C | discussion | Huawei, HiSilicon | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
available | [WTS] [JSN] | |
R2-154404 | Discussion on C-RNTI handling for CA beyond 5CCs | discussion | NTT DOCOMO INC. | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
noted | [WTS] [JSN] | |
R2-154423 | C-RNTI collision problem in Rel-13 CA enhancements | discussion | Samsung Telecommunications | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
noted | [WTS] [JSN] | |
R2-154456 | 36.300 CR for capturing B5C and PUCCH on SCell |
draftCR revised to R2-154982 |
Nokia Networks, NTT DOCOMO, INC. | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
revised | [WTS] [JSN] | |
R2-154457 | Running 36.331 CR for capturing B5C and PUCCH on Scell |
draftCR revised to R2-154984 |
Nokia Networks | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
revised | [WTS] [JSN] | |
R2-154458 | RRC CR open items | other | Nokia Networks | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
noted | [WTS] [JSN] | |
R2-154468 | Configuration for cross-carrier scheduling for Rel-13 UEs | discussion | Samsung Telecommunications | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
noted | [WTS] [JSN] | |
R2-154592 | Dual connectivity with 32 CCs | discussion | Nokia Networks | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
noted | [WTS] [JSN] | |
R2-154672 | On CRNTI collisions | discussion | Ericsson | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
noted | [WTS] [JSN] | |
R2-154732 | UE capability size reduction | other | Samsung Telecommunications | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
available | [WTS] [JSN] | |
R2-154759 | Capability signalling for more than 5 carriers | discussion | Ericsson | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
available | [WTS] [JSN] | |
R2-154895 | Report of [91#21][LTE/CAfe] Capability signalling enhancements |
report revision of R2-154250 |
Nokia Networks | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
noted | [WTS] [JSN] | |
R2-154905 | Running 36.300 CR to capture agreements on carrier aggregation enhancements | draftCR | Nokia Networks | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
endorsed | [WTS] [JSN] | |
R2-154982 | 36.300 CR for capturing B5C and PUCCH on SCell |
draftCR revision of R2-154456 revised to RP-151957 |
Nokia Networks, NTT DOCOMO, INC. | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
endorsed | [WTS] [JSN] | |
R2-154983 | Draft LS to RAN4 on Capability signalling enhancements (to: RAN4; cc: -; contact: Nokia Networks) |
LS out revised to R2-155006 |
Nokia Networks | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
revised | [WTS] [JSN] | |
R2-154984 | Running 36.331 CR for capturing B5C and PUCCH on Scell |
draftCR revision of R2-154457 |
Nokia Networks | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
postponed | [WTS] [JSN] | |
R2-155006 | LS on CA band combination indexing (to: RAN4; cc: -; contact: Nokia Networks) |
LS out revision of R2-154983 |
RAN2 | LTE_CA_enh_b5C-Core | Rel-13 |
R2-91 AI: 07.02.02.1 |
approved | [WTS] [JSN] |
19 documents (0.27796292304993 seconds)