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-2209392 | Consideration on the Temporary UE Capability Restriction for the Dual (Tx/Rx) MUSIM | discussion | ZTE Corporation, Sanechips | NR_DualTxRx_MUSIM-Core | Rel-18 |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | |
R2-2209423 | Potential Solutions on temporary UE capability restriction and removal of restriction | discussion | OPPO | NR_DualTxRx_MUSIM-Core | Rel-18 |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | |
R2-2209575 | UE Capability Update for Dual-Active MUSIM | discussion | Qualcomm Incorporated |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | |||
R2-2209596 | Discussion on Dual Tx/Rx Multi-SIM for NR | discussion | Vodafone | Rel-18 |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | ||
R2-2209638 | Possible solutions to indicate temporary capability reduction for Rel-18 MUSIM | discussion | Intel Corporation | NR_DualTxRx_MUSIM-Core | Rel-18 |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | |
R2-2209856 | Discussion on Dual Tx/Rx Multi-SIM | discussion | ASUSTeK | NR_DualTxRx_MUSIM-Core | Rel-18 |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | |
R2-2210001 | Solutions of Temporary capability restriction for MUSIM | discussion | NEC | NR_DualTxRx_MUSIM-Core | Rel-18 |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | |
R2-2210007 | Discussion on UE capability update for MUSIM | discussion | Huawei, HiSilicon | NR_DualTxRx_MUSIM-Core | Rel-18 |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | |
R2-2210018 | Discussion on UE-initiated SCell deactivation and activation | discussion | Huawei, HiSilicon |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | |||
R2-2210060 | Capability sharing issue for SRS Tx switching capability | discussion | Xiaomi | NR_DualTxRx_MUSIM-Core | Rel-18 |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | |
R2-2210071 | Candidate solutions for Dual TX/RX MUSIM operation | discussion | Nokia, Nokia Shanghai Bell | Rel-18 |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | ||
R2-2210390 | Potential solutions for Rel-18 Multi-SIM | discussion | vivo | NR_DualTxRx_MUSIM-Core | Rel-18 |
R2-119-bis-e AI: 8.17.2.2 |
noted | [WTS] [JSN] | |
R2-2210422 | eMUSIM Solutions | discussion | Sharp |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | |||
R2-2210446 | [Draft] LS on DLUL interruption due to capability switching |
LS out LS To: RAN4 |
vivo | NR_DualTxRx_MUSIM-Core |
R2-119-bis-e AI: 8.17.2.2 |
withdrawn | [WTS] [JSN] | ||
R2-2210514 | Discussion on R18 MUSIM Solutions | discussion | MediaTek Inc. | NR_DualTxRx_MUSIM-Core |
R2-119-bis-e AI: 8.17.2.2 |
noted | [WTS] [JSN] | ||
R2-2210534 | Possible solution for dual Rx/Tx MUSIM devices | discussion | DENSO CORPORATION | NR_DualTxRx_MUSIM-Core |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | ||
R2-2210583 | General soluion for Rel-18 MUSIM | discussion | LG Electronics | NR_DualTxRx_MUSIM-Core | Rel-18 |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | |
R2-2210596 | Analysis on dual Tx/Rx Multi-SIM | discussion | Lenovo Information Technology | NR_DualTxRx_MUSIM-Core | Rel-18 |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | |
R2-2210730 | Discussion on capability coordination for MUSIM | discussion | Samsung | NR_DualTxRx_MUSIM-Core | Rel-18 |
R2-119-bis-e AI: 8.17.2.2 |
available | [WTS] [JSN] | |
R2-2210823 | Report of [AT119bis-e][211][MUSIM] MUSIM solutions for Rel-18 (QC) | report | Qualcomm Incorporated | NR_DualTxRx_MUSIM-Core | Rel-18 |
R2-119-bis-e AI: 8.17.2.2 |
noted | [WTS] [JSN] |
20 documents (0.33541202545166 seconds)