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-2107025 | Discussion on Configured Time for AS-based Solution | discussion | OPPO | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2107026 | Further Consideration for Busy Indication | discussion | OPPO | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2107027 | Interaction between AS-based and NAS-based Solution for Network Switching | discussion | OPPO | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2107237 | Considerations on Busy Indication Approach | discussion | Samsung |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |||
| R2-2107265 | Analysis on AS-based solution and NAS-based solution | discussion | China Telecommunications |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |||
| R2-2107301 | NAS and AS procedures and their interaction for aperiodic gap request | discussion | Intel Corporation | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2107327 | Open Issues on Network Switching | discussion | CATT | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2107459 | Network switching with leaving RRC Connected State of Multi-SIM | discussion | China Telecommunication | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2107477 | Network switching for Multi-USIM devices during dual connectivity | discussion | Samsung |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |||
| R2-2107597 | Signaling aspects of MUSIM Network Switching | discussion | Apple | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2107598 | MUSIM Band Conflict-RRC Processing Delay-Caller ID Requirements | discussion | Apple | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2107781 | Open issues on scheduling gap for network switching | discussion | NEC | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2107789 | RAN Initiated Network switching with Leaving RRC_CONNECTED | discussion | SHARP Corporation |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |||
| R2-2107791 | Open Issues for MUSIM Network Switching | discussion | Charter Communications, Inc |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |||
| R2-2107807 | Further analysis on NAS level solutions for RRC-INACTIVE | discussion | Nokia, Nokia Shanghai Bell | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | ||
| R2-2107808 | On switching notification solutions for MUSIM operation | discussion | Nokia, Nokia Shanghai Bell | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | ||
| R2-2107856 | Open Issues on Switching Notification | discussion | vivo |
R2-115-e AI: 8.3.3 |
noted | [WTS] [JSN] | |||
| R2-2107857 | Summary of Switching message details | discussion | vivo |
R2-115-e AI: 8.3.3 |
noted | [WTS] [JSN] | |||
| R2-2107891 | Switching notification and busy indication | discussion | Lenovo, Motorola Mobility | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | ||
| R2-2107973 | Discussion on switching procedure without leaving RRC_CONNECTED state | discussion | Ericsson |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |||
| R2-2107975 | Discussion on switching procedure for leaving RRC_CONNECTED state | discussion | Ericsson |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |||
| R2-2108031 | On coordinated switch from NW for MUSIM device | discussion | Huawei, HiSilicon | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2108051 | Discussion on Busy Indication in Inactive State |
discussion revision of R2-2105683 |
Sony | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2108052 | Discussion on AS based Leaving in MultiSIM | discussion | Sony | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2108075 | Consideration on the busy indication at Inactive state | discussion | ZTE Corporation, Sanechips | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2108076 | Interaction between AS-based solution and NAS-based solution for network switching | discussion | ZTE Corporation, Sanechips | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2108077 | Summary of [Post114-e][243][MUSIM] Gap handling | discussion | ZTE Corporation, Sanechips | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
noted | [WTS] [JSN] | |
| R2-2108121 | On busy indication in RRC_INACTIVE | discussion | Huawei, HiSilicon |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |||
| R2-2108182 | Further consideration on the remaining issues of scheduling Gap | discussion | ZTE Corporation, Sanechips | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2108360 | Busy Indication in Multi-SIM | discussion | Qualcomm Incorporated |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |||
| R2-2108361 | Leaving Connected state in Multi-SIM | discussion | Qualcomm Incorporated |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |||
| R2-2108387 | Discussion about the usage of the autonomous gap | discussion | Xiaomi Communications |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |||
| R2-2108709 | Interaction between NAS and AS for network switching | discussion | ASUSTeK | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2108725 | Considerations on SIM Swithcing |
discussion revision of R2-2106110 |
LG Electronics | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2108726 | Scheduling Gap Handling | discussion | LG Electronics | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2108732 | Further discussion on switching message details | discussion | Samsung Electronics Co., Ltd | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2108737 | Busy indication in INACTIVE mode |
discussion revision of R2-2106351 |
MediaTek Inc. | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2108755 | Procedures for MSIM UE notification on network switching |
discussion revision of R2-2105445 |
Futurewei Technologies |
R2-115-e AI: 8.3.3 |
reserved | [WTS] [JSN] | |||
| R2-2108804 | Signalling design on busy indication procedure |
discussion revised to R2-2111186 |
DENSO CORPORATION | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
not treated | [WTS] [JSN] | |
| R2-2108855 | Reply LS on NAS-based busy indication |
LS out LS is reply to R2-2106970 LS To: SA2, RAN3 revision of R2-2108856 |
RAN2 | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
approved | [WTS] [JSN] | |
| R2-2108856 | [Draft] Reply LS on NAS-based busy indication |
LS out LS is reply to R2-2106970 LS To: SA2, RAN3 revised to R2-2108855 |
Intel | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
revised | [WTS] [JSN] | |
| R2-2108861 | LS on gap handling for MUSIM |
LS out LS To: RAN4 |
RAN2 | LTE_NR_MUSIM-Core | Rel-17 |
R2-115-e AI: 8.3.3 |
approved | [WTS] [JSN] |
42 documents (0.34589695930481 seconds)