|
|
| 36.300 | 1355 | - | B | 16.7.0 | Rel-17 | Running CR to 36300 for Multi-USIM devices support |
R2-2203437
| agreed | RAN2#117-e | Ericsson |
RP-220488
| approved | RAN#95-e | RAN2 | 17.0.0 | LTE_NR_MUSIM-Core |
|
|
|
| 36.300 | 1349 | 1 | B | 16.6.0 | Rel-17 | Running CR to 36300 for Multi-USIM devices support |
R2-2111438
| endorsed | RAN2#116-e | Ericsson |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 36.300 | 1349 | - | B | 16.6.0 | Rel-17 | Running CR to 36300 for Multi-USIM devices support |
R2-2110789
| revised | RAN2#116-e | Ericsson |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 36.304 | 0845 | 1 | B | 17.0.0 | Rel-17 | Introduction of Multi-USIM devices to 36.304 |
R2-2206859
| agreed | RAN2#118-e | China Telecom |
RP-221730
| approved | RAN#96 | RAN2 | 17.1.0 | LTE_NR_MUSIM-Core |
|
|
|
| 36.304 | 0845 | - | B | 17.0.0 | Rel-17 | Introduction of Multi-USIM devices to 36.304 |
R2-2204542
| revised | RAN2#118-e | China Telecom |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 36.304 | 0842 | 2 | B | 16.6.0 | Rel-17 | Introduction of Multi-USIM devices to 36.304 |
R2-2203804
| | RAN2#117-e | China Telecommu... |
| | | | | LTE_NR_MUSIM, L... |
|
|
|
| 36.304 | 0842 | 1 | B | 16.6.0 | Rel-17 | Introduction of Multi-USIM devices to 36.304 |
R2-2203651
| revised | RAN2#117-e | China Telecommu... |
| | | | | LTE_NR_MUSIM, L... |
|
|
|
| 36.304 | 0842 | - | B | 16.6.0 | Rel-17 | Introduction of Multi-USIM devices to 36.304 |
R2-2203273
| revised | RAN2#117-e | China Telecommu... |
| | | | | LTE_NR_MUSIM, L... |
|
|
|
| 36.331 | 4822 | - | F | 17.0.0 | Rel-17 | Correction on UE behavior for NAS-based busy indication in RRC_INACTIVE |
R2-2206574
| agreed | RAN2#118-e | Samsung |
RP-221730
| approved | RAN#96 | RAN2 | 17.1.0 | LTE_NR_MUSIM-Core |
|
|
|
| 36.331 | 4808 | 1 | F | 17.0.0 | Rel-17 | Corrections on MUSIM in LTE |
R2-2206170
| agreed | RAN2#118-e | Samsung |
RP-221730
| approved | RAN#96 | RAN2 | 17.1.0 | LTE_NR_MUSIM-Core |
|
|
|
| 36.331 | 4808 | - | F | 17.0.0 | Rel-17 | Corrections on MUSIM in LTE |
R2-2205848
| revised | RAN2#118-e | Samsung Electro... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 36.331 | 4769 | 1 | B | 16.7.0 | Rel-17 | Introduction of MUSIM for LTE |
R2-2203750
| agreed | RAN2#117-e | Samsung |
RP-220488
| approved | RAN#95-e | RAN2 | 17.0.0 | LTE_NR_MUSIM-Core |
|
|
|
| 36.331 | 4769 | - | B | 16.7.0 | Rel-17 | Introduction of MUSIM for LTE |
R2-2203013
| revised | RAN2#117-e | Samsung Electro... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 36.413 | 1794 | - | B | 16.3.0 | Rel-17 | BLCR36413 for support for Multi-USIM devices |
R3-205987
| | RAN3#110-e | ZTE |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.133 | 2375 | 1 | F | 17.5.0 | Rel-17 | CR on New gap pattern for MUSIM |
R4-2210986
| agreed | RAN4#103-e | Ericsson |
RP-221682
| approved | RAN#96 | RAN4 | 17.6.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.133 | 2375 | - | F | 17.5.0 | Rel-17 | CR on New gap pattern for MUSIM |
R4-2209448
| revised | RAN4#103-e | Ericsson |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.133 | 2282 | - | B | 17.4.0 | Rel-17 | Big CR: RRM requirements for Rel-17 NR MUSIM |
R4-2207539
| agreed | RAN4#102-e | vivo |
RP-220345
| approved | RAN#95-e | RAN4 | 17.5.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.300 | 0631 | - | F | 17.3.0 | Rel-17 | Clarification on paging collision avoidance for MUSIM |
R2-2301558
| | RAN2#121 | Samsung |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.300 | 0548 | - | F | 17.1.0 | Rel-17 | Stage-2 corrections on MUSIM |
R2-2208724
| agreed | RAN2#119-e | Samsung |
RP-222522
| approved | RAN#97-e | RAN2 | 17.2.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.300 | 0526 | - | F | 17.1.0 | Rel-17 | Update to gap handling for Multi-USIM (38.300) |
R2-2208033
| merged | RAN2#119-e | Ericsson |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.300 | 0522 | - | F | 17.1.0 | Rel-17 | Correction on MUSIM related changes |
R2-2208000
| merged | RAN2#119-e | Nokia, Nokia Sh... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.300 | 0507 | - | F | 17.1.0 | Rel-17 | Corrections on Gap Activation Limitation |
R2-2207236
| | RAN2#119-e | OPPO |
| | | | | NR_MG_enh-Core,... |
|
|
|
| 38.300 | 0506 | - | F | 17.1.0 | Rel-17 | Corrections on NW Switching for Multi-SIM with or without Leaving RRC_CONNECTED_38.300 |
R2-2207231
| merged | RAN2#119-e | OPPO |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.300 | 0500 | - | F | 17.1.0 | Rel-17 | CR on the Gap Numbers Restriction |
R2-2207164
| merged | RAN2#119-e | ZTE Corporation... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.300 | 0422 | 1 | B | 16.8.0 | Rel-17 | Running CR to 38300 for Multi-USIM devices support |
R2-2204227
| agreed | RAN2#117-e | Ericsson |
RP-220488
| approved | RAN#95-e | RAN2 | 17.0.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.300 | 0422 | - | B | 16.8.0 | Rel-17 | Running CR to 38300 for Multi-USIM devices support |
R2-2203436
| revised | RAN2#117-e | Ericsson |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.300 | 0396 | 1 | B | 16.7.0 | Rel-17 | Running CR to 38300 for Multi-USIM devices support |
R2-2111439
| endorsed | RAN2#116-e | Ericsson |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.300 | 0396 | - | B | 16.7.0 | Rel-17 | Running CR to 38300 for Multi-USIM devices support |
R2-2110790
| revised | RAN2#116-e | Ericsson |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.306 | 0978 | - | B | 17.6.0 | Rel-18 | MUSIM paging cause forwarding |
R2-2312195
| revised | RAN2#124 | vivo, Samsung |
| | | | | LTE_NR_MUSIM-Co... |
|
|
|
| 38.306 | 0764 | 1 | B | 17.1.0 | Rel-17 | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.306) |
R2-2209073
| agreed | RAN2#119-e | Intel Corporation |
RP-222527
| approved | RAN#97-e | RAN2 | 17.2.0 | NR_MBS-Core, NR... |
|
|
|
| 38.306 | 0763 | - | F | 17.1.0 | Rel-17 | Corrections on Capability for MUSIM UE |
R2-2207238
| not pursued | RAN2#119-e | OPPO |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.306 | 0703 | 2 | B | 17.0.0 | Rel-17 | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.306) |
R2-2206849
| agreed | RAN2#118-e | Intel Corporation |
RP-221756
| approved | RAN#96 | RAN2 | 17.1.0 | NR_MBS-Core, NR... |
|
|
|
| 38.306 | 0672 | 2 | B | 16.7.0 | Rel-17 | Introduction of MUSIM UE Capabilities |
R2-2203802
| merged | RAN2#117-e | Huawei, HiSilicon |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.306 | 0672 | 1 | B | 16.7.0 | Rel-17 | Introduction of MUSIM UE Capabilities |
R2-2202697
| revised | RAN2#117-e | Huawei, HiSilicon |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.306 | 0672 | - | B | 16.7.0 | Rel-17 | Running CR to 38306 for MUSIM UE Capabilities |
R2-2202010
| revised | RAN2#116-bis-e | Huawei, HiSilicon |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.321 | 1401 | - | F | 17.1.0 | Rel-17 | MAC corrections on MUSIM |
R2-2208725
| agreed | RAN2#119-e | Samsung |
RP-222522
| approved | RAN#97-e | RAN2 | 17.2.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.321 | 1386 | - | F | 17.1.0 | Rel-17 | corrections on RACH procedure during MUSIM gaps |
R2-2208462
| merged | RAN2#119-e | vivo |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.321 | 1248 | - | F | 17.0.0 | Rel-17 | Clarification on MAC behaviour during MUSIM gaps |
R2-2205042
| | RAN2#118-e | NEC |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 4554 | - | A | 18.0.0 | Rel-18 | Field conditions for MUSIM gap |
R2-2400759
| not pursued | RAN2#125 | Ericsson |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 4553 | - | F | 17.7.0 | Rel-17 | Field conditions for MUSIM gap |
R2-2400758
| not pursued | RAN2#125 | Ericsson |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 4414 | - | B | 17.6.0 | Rel-18 | MUSIM paging cause forwarding |
R2-2312196
| revised | RAN2#124 | vivo, Samsung |
| | | | | LTE_NR_MUSIM-Co... |
|
|
|
| 38.331 | 4026 | - | F | 17.4.0 | Rel-17 | Correction on CHO execution while T346g is running |
R2-2303771
| not pursued | RAN2#121-bis-e | Lenovo |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3851 | 1 | F | 17.3.0 | Rel-17 | Miscellaneous correction of NR RRC support for MUSIM |
R2-2302206
| agreed | RAN2#121 | vivo |
RP-230688
| approved | RAN#99 | RAN2 | 17.4.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3851 | - | F | 17.3.0 | Rel-17 | Miscellaneous correction of NR RRC support for MUSIM |
R2-2300898
| revised | RAN2#121 | vivo |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3838 | - | F | 17.3.0 | Rel-17 | CR for clarification of the starting SFN of MUSIM aperiodic gap |
R2-2300793
| not pursued | RAN2#121 | Huawei, HiSilicon |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3768 | - | F | 17.2.0 | Rel-17 | Correction on re-establishment procedure while T346g is running |
R2-2213215
| agreed | RAN2#120 | Samsung Electro... |
RP-223409
| approved | RAN#98-e | RAN2 | 17.3.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3731 | - | F | 17.2.0 | Rel-17 | CR on the MUSIM Gap Configuration |
R2-2212746
| not pursued | RAN2#120 | ZTE Corporation... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3730 | - | F | 17.2.0 | Rel-17 | Miscellaneous Correction on MUSIM |
R2-2212745
| | RAN2#120 | ZTE Corporation... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3671 | - | F | 17.2.0 | Rel-17 | Clarifications on Aperiodic gap configuration |
R2-2212111
| not pursued | RAN2#120 | Nokia Solutions... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3642 | - | F | 17.2.0 | Rel-17 | Miscellaneous correction of NR RRC support for MUSIM |
R2-2211801
| | RAN2#120 | vivo |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3621 | 2 | B | 17.2.0 | Rel-17 | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331) |
R2-2213038
| agreed | RAN2#120 | Intel Corporation |
RP-223415
| approved | RAN#98-e | RAN2 | 17.3.0 | NR_MBS-Core, NR... |
|
|
|
| 38.331 | 3475 | - | F | 17.1.0 | Rel-17 | Clarification on Joint Gap Configuration |
R2-2209091
| agreed | RAN2#119-e | MediaTek Inc. |
RP-222524
| approved | RAN#97-e | RAN2 | 17.2.0 | NR_MG_enh-Core,... |
|
|
|
| 38.331 | 3428 | - | F | 17.1.0 | Rel-17 | Correction on MUSIM gap configuration |
R2-2208496
| merged | RAN2#119-e | MediaTek Inc. |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3422 | 2 | F | 17.1.0 | Rel-17 | Miscellaneous correction of NR RRC support for MUSIM |
R2-2209214
| agreed | RAN2#119-e | vivo |
RP-222522
| approved | RAN#97-e | RAN2 | 17.2.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3422 | 1 | F | 17.1.0 | Rel-17 | Correction of NR RRC support for MUSIM |
R2-2208727
| revised | RAN2#119-e | vivo |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3422 | - | F | 17.1.0 | Rel-17 | Correction of NR RRC support for MUSIM |
R2-2208461
| revised | RAN2#119-e | vivo |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3343 | - | F | 17.1.0 | Rel-17 | Clarification for MUSIM Assistance Information in DC for reconfiguration with Sync |
R2-2207994
| not pursued | RAN2#119-e | Nokia, Nokia Sh... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3342 | - | F | 17.1.0 | Rel-17 | Applicability of otherConfig MUSIM IEs for SRB3 |
R2-2207987
| not pursued | RAN2#119-e | Nokia, Nokia Sh... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3335 | - | F | 17.1.0 | Rel-17 | Corrections to MUSIM gaps |
R2-2207958
| merged | RAN2#119-e | Huawei, HiSilicon |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3244 | 1 | B | 17.1.0 | Rel-17 | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331) |
R2-2209074
| agreed | RAN2#119-e | Intel Corporation |
RP-222527
| approved | RAN#97-e | RAN2 | 17.2.0 | NR_MBS-Core, NR... |
|
|
|
| 38.331 | 3236 | - | F | 17.1.0 | Rel-17 | Corrections on NW Switching for Multi-SIM with or without Leaving RRC_CONNECTED_38.331 |
R2-2207232
| merged | RAN2#119-e | OPPO |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3225 | - | F | 17.1.0 | Rel-17 | CR on the MUSIM-GapInfo |
R2-2207165
| merged | RAN2#119-e | ZTE Corporation... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3182 | - | F | 17.0.0 | Rel-17 | Correction on UE behavior for NAS-based busy indication in RRC_INACTIVE |
R2-2206575
| agreed | RAN2#118-e | Samsung |
RP-221730
| approved | RAN#96 | RAN2 | 17.1.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3116 | - | F | 17.0.0 | Rel-17 | [S676] Correction on handling of musim-GapConfig in RRC_INACTIVE_Opt 2 |
R2-2205767
| | RAN2#118-e | Samsung Electro... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3115 | - | F | 17.0.0 | Rel-17 | [S676] Correction on handling of musim-GapConfig in RRC_INACTIVE_Opt 1 |
R2-2205765
| | RAN2#118-e | Samsung Electro... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3014 | 3 | F | 17.0.0 | Rel-17 | Correction of NR RRC support for MUSIM |
R2-2206835
| agreed | RAN2#118-e | vivo |
RP-221730
| approved | RAN#96 | RAN2 | 17.1.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3014 | 2 | F | 17.0.0 | Rel-17 | Correction of NR RRC support for MUSIM |
R2-2206625
| revised | RAN2#118-e | vivo(Rapporteur) |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3014 | 1 | F | 17.0.0 | Rel-17 | Correction of NR RRC support for MUSIM |
R2-2206169
| revised | RAN2#118-e | vivo(Rapporteur) |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 3014 | - | F | 17.0.0 | Rel-17 | Correction of NR RRC support for MUSIM |
R2-2204892
| revised | RAN2#118-e | vivo(Rapporteur) |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 2998 | 2 | B | 17.0.0 | Rel-17 | Release-17 UE capabilities based on R1 and R4 feature lists (TS38.331) |
R2-2206847
| agreed | RAN2#118-e | Intel Corporation |
RP-221756
| approved | RAN#96 | RAN2 | 17.1.0 | NR_MBS-Core, NR... |
|
|
|
| 38.331 | 2919 | 1 | B | 16.7.0 | Rel-17 | Introduction of NR RRC support for MUSIM |
R2-2204207
| agreed | RAN2#117-e | vivo (Rapporteur) |
RP-220488
| approved | RAN#95-e | RAN2 | 17.0.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 2919 | - | B | 16.7.0 | Rel-17 | Capture RAN2 agreements on RRC for MUSIM |
R2-2202962
| revised | RAN2#117-e | vivo(Rapporteur) |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 2875 | 2 | B | 16.7.0 | Rel-17 | Introduction of MUSIM UE Capabilities |
R2-2203801
| merged | RAN2#117-e | Huawei, HiSilicon |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 2875 | 1 | B | 16.7.0 | Rel-17 | Introduction of MUSIM UE Capabilities |
R2-2202696
| revised | RAN2#117-e | Huawei, HiSilicon |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.331 | 2875 | - | B | 16.7.0 | Rel-17 | Running CR to 38331 for MUSIM UE Capabilities |
R2-2202009
| revised | RAN2#116-bis-e | Huawei, HiSilicon |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.413 | 0846 | - | F | 17.0.0 | Rel-17 | Avoid R17 paging to legacy UE (NGAP CR) |
R3-223655
| | RAN3#116-e | Qualcomm Incorp... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.413 | 0811 | 2 | F | 17.0.0 | Rel-17 | MUSIM Correction on NGAP |
R3-223957
| agreed | RAN3#116-e | Ericsson, Nokia... |
RP-221137
| approved | RAN#96 | RAN3 | 17.1.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.413 | 0782 | - | F | 17.0.0 | Rel-17 | Correction of MUSIM Cause |
R3-223154
| | RAN3#116-e | Nokia, Nokia Sh... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.413 | 0724 | 3 | B | 16.8.0 | Rel-17 | Introduction of MultiSIM support over NG |
R3-222664
| agreed | RAN3#115-e | Nokia, Nokia Sh... |
RP-220219
| approved | RAN#95-e | RAN3 | 17.0.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.413 | 0724 | 2 | B | 16.8.0 | Rel-17 | Introduction of MultiSIM support over NG |
R3-221574
| revised | RAN3#115-e | Nokia, Nokia Sh... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.413 | 0724 | 1 | B | 16.8.0 | Rel-17 | Introduction of MultiSIM support over NG |
R3-221128
| endorsed | RAN3#114-bis-e | Nokia, Nokia Sh... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.413 | 0724 | - | B | 16.8.0 | Rel-17 | Support for Multi-USIM devices |
R3-220364
| revised | RAN3#114-bis-e | Nokia, Nokia Sh... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.413 | 0581 | - | B | 16.5.0 | Rel-17 | Support for Multi-USIM devices |
R3-211791
| | RAN3#112-e | Nokia, Nokia Sh... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.413 | 0560 | - | B | 16.4.0 | Rel-17 | Support for Multi-USIM devices |
R3-210730
| | RAN3#111-e | Nokia, Nokia Sh... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.413 | 0474 | - | B | 16.3.0 | Rel-17 | BLCR38413 for support for Multi-USIM devices |
R3-205988
| | RAN3#110-e | ZTE |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.423 | 0599 | - | B | 16.5.0 | Rel-17 | Support for Multi-USIM devices |
R3-211792
| | RAN3#112-e | Nokia, Nokia Sh... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.423 | 0561 | - | B | 16.4.0 | Rel-17 | Support for Multi-USIM devices |
R3-210731
| | RAN3#111-e | Nokia, Nokia Sh... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.423 | 0468 | - | B | 16.3.0 | Rel-17 | BLCR38423 for support for Multi-USIM devices |
R3-205989
| | RAN3#110-e | ZTE |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.463 | 0677 | 1 | B | 16.8.0 | Rel-17 | Introduction of MultiSIM support over E1 |
R3-221577
| withdrawn | RAN3#115-e | Samsung, Ericss... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.463 | 0677 | - | B | 16.8.0 | Rel-17 | Introduction of MultiSIM support over E1 |
R3-221132
| endorsed | RAN3#114-bis-e | Samsung, Ericss... |
| | | | | LTE_NR_MUSIM-Core |
|
|
|
| 38.473 | 0957 | - | F | 17.0.0 | Rel-17 | Clarification on Paging Cause |
R3-223633
| agreed | RAN3#116-e | Qualcomm Incorp... |
RP-221137
| approved | RAN#96 | RAN3 | 17.1.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.473 | 0887 | 2 | F | 17.0.0 | Rel-17 | Correction to MUSIM |
R3-223956
| agreed | RAN3#116-e | Huawei, ZTE, Ra... |
RP-221137
| approved | RAN#96 | RAN3 | 17.1.0 | LTE_NR_MUSIM-Core |
|
|
|
| 38.822 | 0008 | - | B | 16.2.0 | Rel-17 | Running CR to 38822 for MUSIM UE Capabilities |
R2-2202008
| noted | RAN2#116-bis-e | Huawei, HiSilicon |
| | | | | LTE_NR_MUSIM-Core |
|