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-162368 | On priority classes for uplink LBT | discussion | MediaTek Inc. | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |
R2-162393 | Random Access for eLAA | discussion | Samsung | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
available | [WTS] [JSN] | |
R2-162394 | UL scheduling for eLAA | discussion | Samsung | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
available | [WTS] [JSN] | |
R2-162427 | RAN2 work scope and work plan for the enhanced LAA WID | discussion | Huawei, Ericsson | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |
R2-162428 | Consideration on RACH for LAA Scell | discussion | Huawei, HiSilicon | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |
R2-162429 | Considerations on Qos control and UL transmission on LAA Scell | discussion | Huawei, HiSilicon | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |
R2-162430 | UL HARQ handling for LAA Scell | discussion | Huawei, HiSilicon | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |
R2-162469 | Uplink QoS support for UL LAA | discussion | Intel Corporation | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |
R2-162470 | UL HARQ and DRX for UL LAA | discussion | Intel Corporation | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |
R2-162471 | RACH procedure for UL LAA | discussion | Intel Corporation | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |
R2-162669 | RAN2 aspects of UL LAA | discussion | Nokia, Alcatel-Lucent Shanghai Bell | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |
R2-162743 | Asynchronous UL HARQ for LAA | discussion | Ericsson | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |
R2-162744 | Dropping of initial UL HARQ transmission in LAA | discussion | Ericsson | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |
R2-162745 | Impact on Random Access due to LBT | discussion | Ericsson | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |
R2-162746 | Modelling of LBT for LAA | discussion | Ericsson | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |
R2-162747 | Multi-subframe scheduling | discussion | Ericsson | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
available | [WTS] [JSN] | |
R2-162748 | Routing restrictions in LAA | discussion | Ericsson | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
available | [WTS] [JSN] | |
R2-162858 | Logical Channel Prioritization in LAA | discussion | LG Electronics Inc. | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
available | [WTS] [JSN] | |
R2-162894 | PHR aspect for supporting UL LAA | discussion | LG Electronics Inc. | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
available | [WTS] [JSN] | |
R2-162895 | Random Access aspect in LAA | discussion | LG Electronics Inc. |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |||
R2-162896 | LBT impact on UL HARQ operation | discussion | LG Electronics Inc. |
R2-93 AI: 8.1.1 |
available | [WTS] [JSN] | |||
R2-162911 | RACH Procedure for Enhanced LAA | discussion | QUALCOMM CDMA Technologies |
R2-93 AI: 8.1.1 |
noted | [WTS] [JSN] | |||
R2-163109 | Draft LS on RAN2 agreements on eLAA (to: RAN1; cc: -; contact: Huawei) |
LS out revised to R2-163146 |
Huawei | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
revised | [WTS] [JSN] | |
R2-163146 | LS on RAN2 agreements on eLAA (to: RAN1; cc: -; contact: Huawei) |
LS out revision of R2-163109 |
RAN2 | LTE_eLAA-Core | Rel-14 |
R2-93 AI: 8.1.1 |
approved | [WTS] [JSN] |
24 documents (0.33584594726562 seconds)