|
|
| 23.008 | 0575 | 2 | B | 16.1.0 | Rel-16 | Introduce support for 5G SRVCC in PS Network Access Mode Data (5GS) |
C4-201091
| agreed | CT4#96-e | BlackBerry UK L... |
CP-200022
| approved | CT#87-e | CT4 | 16.2.0 | 5G_SRVCC |
|
|
|
| 23.008 | 0575 | 1 | B | 16.1.0 | Rel-16 | Introduce support for 5G SRVCC in PS Network Access Mode Data (5GS) |
C4-200479
| revised | CT4#96-e | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 23.008 | 0575 | - | B | 16.1.0 | Rel-16 | Introduce support for 5G SRVCC in PS Network Access Mode Data (5GS) |
C4-200179
| withdrawn | CT4#96 | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0377 | - | A | 18.0.0 | Rel-18 | Cancelling AMF location at 5G-SRVCC from NG-RAN to 3GPP UTRAN |
S2-2308424
| withdrawn | SA2#158 | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC, TEI17 |
|
|
|
| 23.216 | 0376 | 1 | F | 17.1.0 | Rel-17 | Cancelling AMF location at 5G-SRVCC from NG-RAN to 3GPP UTRAN |
S2-2308423
| withdrawn | SA2#158 | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC, TEI17 |
|
|
|
| 23.216 | 0376 | - | F | 17.1.0 | Rel-17 | Cancelling AMF location at 5G-SRVCC from NG-RAN to 3GPP UTRAN |
S2-2307235
| revised | SA2#157 | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC, TEI17 |
|
|
|
| 23.216 | 0374 | 1 | A | 17.0.0 | Rel-17 | AMF interaction with GMLC at SRVCC for an Emergency session |
S2-2204956
| agreed | SA2#151-e | Nokia, Nokia Sh... |
SP-220391
| approved | SA#96 | SA WG2 | 17.1.0 | 5G_SRVCC |
|
|
|
| 23.216 | 0374 | - | A | 17.0.0 | Rel-17 | AMF interaction with GMLC at SRVCC for an Emergency session |
S2-2204088
| revised | SA2#151-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0373 | 1 | F | 16.5.0 | Rel-17 | Failure cases for SRVCC from NR to UTRAN |
S2-2201674
| agreed | SA2#149-e | Nokia, Nokia Sh... |
SP-220066
| approved | SA#95-e | SA WG2 | 17.0.0 | TEI17, 5G_SRVCC |
|
|
|
| 23.216 | 0373 | - | F | 16.5.0 | Rel-16 | Failure cases for SRVCC from NR to UTRAN |
S2-2200285
| revised | SA2#149-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0372 | 2 | F | 16.6.0 | Rel-16 | AMF interaction with GMLC at SRVCC for an Emergency session |
S2-2204955
| agreed | SA2#151-e | Nokia, Nokia Sh... |
SP-220391
| approved | SA#96 | SA WG2 | 16.7.0 | 5G_SRVCC |
|
|
|
| 23.216 | 0372 | 1 | F | 16.6.0 | Rel-16 | AMF interaction with GMLC at SRVCC for an Emergency session |
S2-2204087
| revised | SA2#151-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0372 | - | F | 16.5.0 | Rel-16 | AMF interaction with GMLC at SRVCC for an Emergency session |
S2-2200109
| revised | SA2#149-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0371 | - | F | 16.5.0 | Rel-16 | MSC Server performing a TMSI reallocation and a MAP Update Location at 5G-SRVCC |
S2-2200108
| agreed | SA2#149-e | Nokia, Nokia Sh... |
SP-220043
| approved | SA#95-e | SA WG2 | 16.6.0 | 5G_SRVCC |
|
|
|
| 23.216 | 0367 | 1 | F | 16.3.0 | Rel-16 | SRVCC operation impossible indication for 5G emergency SRVCC |
S2-2002369
| agreed | SA2#137-E | ZTE |
SP-200066
| approved | SA#87-E | SA WG2 | 16.4.0 | 5G_SRVCC |
|
|
|
| 23.216 | 0367 | - | C | 16.3.0 | Rel-16 | SRVCC operation impossible indication for 5G emergency SRVCC |
S2-2002287
| revised | SA2#137-E | ZTE |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0366 | 1 | F | 16.3.0 | Rel-16 | Mega CR on editorial corrections for 5G_SRVCC |
S2-2002368
| agreed | SA2#137-E | China Unicom |
SP-200066
| approved | SA#87-E | SA WG2 | 16.4.0 | 5G_SRVCC |
|
|
|
| 23.216 | 0366 | - | D | 16.3.0 | Rel-16 | Mega CR on editorial corrections for 5G_SRVCC |
S2-2002180
| revised | SA2#137-E | China Unicom |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0364 | - | F | 16.3.0 | Rel-16 | Clarify STN-SR update and removal by UDM |
S2-2001058
| agreed | SA2#136-AH | BlackBerry UK Ltd. |
SP-200066
| approved | SA#87-E | SA WG2 | 16.4.0 | 5G_SRVCC |
|
|
|
| 23.216 | 0363 | - | F | 16.3.0 | Rel-16 | Enable a UE to indicate 5G SRVCC support when registering with EPS and 3G/4G SRVCC support when registering with 5GS |
S2-2000109
| noted | SA2#136-AH | Vivo Mobile Com... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0361 | - | F | 16.2.0 | Rel-16 | Clarification on the EBI allocation when 5G SRVCC is deployed |
S2-1909419
| not treated | SA2#135 | ZTE |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0360 | - | F | 16.2.0 | Rel-16 | Clarification on the interface enahncement between AMF and MME_SRVCC |
S2-1909418
| agreed | SA2#135 | ZTE |
SP-191072
| approved | SA#86 | SA WG2 | 16.3.0 | 5G_SRVCC |
|
|
|
| 23.216 | 0359 | - | F | 16.2.0 | Rel-16 | PDU Session release due to 5G SRVCC |
S2-1909052
| agreed | SA2#135 | Ericsson |
SP-191072
| approved | SA#86 | SA WG2 | 16.3.0 | 5G_SRVCC |
|
|
|
| 23.216 | 0358 | 5 | C | 16.3.0 | Rel-16 | 5G-SRVCC from NG-RAN to UTRAN for emergency session |
S2-2001112
| agreed | SA2#136-AH | ORANGE, BlackBe... |
SP-200066
| approved | SA#87-E | SA WG2 | 16.4.0 | 5G_SRVCC |
|
|
|
| 23.216 | 0358 | 4 | F | 16.3.0 | Rel-16 | 5G-SRVCC from NG-RAN to UTRAN for emergency session |
S2-2001051
| revised | SA2#136-AH | ORANGE, BlackBe... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0358 | 3 | F | 16.3.0 | Rel-16 | 5G-SRVCC from NG-RAN to UTRAN for emergency session |
S2-2000100
| revised | SA2#136-AH | ORANGE, BlackBe... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0358 | 2 | F | 16.2.0 | Rel-16 | 5G-SRVCC from NG-RAN to UTRAN for emergency session |
S2-1911907
| | SA2#136 | ORANGE, BlackBe... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0358 | 1 | F | 16.2.0 | Rel-16 | 5G-SRVCC from NG-RAN to UTRAN for emergency session |
S2-1910974
| revised | SA2#136 | ORANGE, BlackBe... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0358 | - | F | 16.2.0 | Rel-16 | 5G-SRVCC from NG-RAN to UTRAN for emergency session |
S2-1908774
| revised | SA2#135 | ORANGE |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0354 | 5 | B | 15.2.0 | Rel-16 | 5G-SRVCC procedure |
S2-1902493
| agreed | SA2#131 | Qualcomm Incorp... |
SP-190162
| approved | SA#83 | SA WG2 | 16.0.0 | 5G_SRVCC |
|
|
|
| 23.216 | 0354 | 4 | B | 15.2.0 | Rel-16 | 5G-SRVCC procedure |
S2-1901940
| revised | SA2#131 | Qualcomm Incorp... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0354 | 3 | B | 15.2.0 | Rel-16 | 5G-SRVCC procedure |
S2-1900882
| revised | SA2#130 | Qualcomm Incorp... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0354 | 2 | B | 15.2.0 | Rel-16 | 5G-SRVCC procedure |
S2-1900842
| revised | SA2#130 | Qualcomm Incorp... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0354 | 1 | B | 15.2.0 | Rel-16 | 5G-SRVCC procedure |
S2-1900760
| revised | SA2#130 | Qualcomm Incorp... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0354 | - | B | 15.2.0 | Rel-16 | 5G-SRVCC procedure |
S2-1900524
| revised | SA2#130 | Qualcomm Incorp... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0353 | 1 | B | 15.2.0 | Rel-16 | Enable the 5G SRVCC in 5GS. |
S2-1900761
| merged | SA2#130 | ZTE, China Unic... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0353 | - | B | 15.2.0 | Rel-16 | Enable the 5G SRVCC in 5GS. |
S2-1900508
| revised | SA2#130 | ZTE, China Unic... |
| | | | | 5G_SRVCC |
|
|
|
| 23.216 | 0352 | 1 | B | 15.2.0 | Rel-16 | Adding 5G SRVCC description to scope and definition to 23.216 |
S2-1900759
| agreed | SA2#130 | ZTE, China Unic... |
SP-190162
| approved | SA#83 | SA WG2 | 16.0.0 | 5G_SRVCC |
|
|
|
| 23.216 | 0352 | - | B | 15.2.0 | Rel-16 | Adding 5G SRVCC description to scope and definition to 23.216 |
S2-1900507
| revised | SA2#130 | ZTE, China Unic... |
| | | | | 5G_SRVCC |
|
|
|
| 23.237 | 0513 | 3 | F | 16.3.0 | Rel-16 | 5G-SRVCC from NG-RAN to UTRAN for emergency session |
S2-2001052
| noted | SA2#136-AH | ORANGE, BlackBe... |
| | | | | 5G_SRVCC |
|
|
|
| 23.237 | 0513 | 2 | F | 16.3.0 | Rel-16 | 5G-SRVCC from NG-RAN to UTRAN for emergency session |
S2-2000101
| revised | SA2#136-AH | ORANGE, BlackBe... |
| | | | | 5G_SRVCC |
|
|
|
| 23.237 | 0513 | 1 | F | 16.3.0 | Rel-16 | 5G-SRVCC from NG-RAN to UTRAN for emergency session |
S2-1910975
| revised | SA2#136 | ORANGE, BlackBe... |
| | | | | 5G_SRVCC |
|
|
|
| 23.237 | 0513 | - | F | 16.3.0 | Rel-16 | 5G-SRVCC from NG-RAN to UTRAN for emergency session |
S2-1908776
| revised | SA2#135 | ORANGE |
| | | | | 5G_SRVCC |
|
|
|
| 23.237 | 0510 | 2 | F | 16.1.0 | Rel-16 | Completing introducing of 5G SRVCC |
S2-1905924
| agreed | SA2#133 | BlackBerry UK L... |
SP-190411
| approved | SA#84 | SA WG2 | 16.2.0 | 5G_SRVCC |
|
|
|
| 23.237 | 0510 | 1 | F | 16.1.0 | Rel-16 | Completing introducing of 5G SRVCC |
S2-1905886
| revised | SA2#133 | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 23.237 | 0510 | - | F | 16.1.0 | Rel-16 | Completing introducing of 5G SRVCC |
S2-1904965
| revised | SA2#133 | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 23.237 | 0507 | 2 | B | 16.0.0 | Rel-16 | Adding UDM update the STN-SR to AMF |
S2-1900845
| agreed | SA2#130 | ZTE, China Unicom |
SP-190162
| approved | SA#83 | SA WG2 | 16.1.0 | 5G_SRVCC |
|
|
|
| 23.237 | 0507 | 1 | B | 16.0.0 | Rel-16 | Adding UDM update the STN-SR to AMF |
S2-1900764
| revised | SA2#130 | ZTE, China Unicom |
| | | | | 5G_SRVCC |
|
|
|
| 23.237 | 0507 | - | B | 16.0.0 | Rel-16 | Adding UDM update the STN-SR to AMF |
S2-1900509
| revised | SA2#130 | ZTE, China Unicom |
| | | | | 5G_SRVCC |
|
|
|
| 23.401 | 3574 | - | F | 16.5.0 | Rel-16 | Enable a UE to indicate 5G SRVCC support when registering with EPS and 3G/4G SRVCC support when registering with 5GS |
S2-2000110
| not treated | SA2#136-AH | Vivo Mobile Com... |
| | | | | 5G_SRVCC |
|
|
|
| 23.501 | 2570 | 1 | F | 16.7.0 | Rel-16 | Handling of UTRAN UE radio capabilities |
S2-2101593
| agreed | SA2#143-e | Qualcomm Incorp... |
SP-210080
| approved | SA#91-e | SA WG2 | 16.8.0 | RACS, 5G_SRVCC |
|
|
|
| 23.501 | 2546 | 1 | F | 16.7.0 | Rel-16 | Correction of UE radio capability handling |
S2-2101552
| agreed | SA2#143-e | Apple |
SP-210081
| approved | SA#91-e | SA WG2 | 16.8.0 | 5GS_Ph1, TEI16,... |
|
|
|
| 23.501 | 2546 | - | F | 16.7.0 | Rel-16 | Correction of UE radio capability handling |
S2-2100246
| revised | SA2#143-e | Apple |
| | | | | 5GS_Ph1, TEI16,... |
|
|
|
| 23.501 | 2010 | - | F | 16.3.0 | Rel-16 | Enable a UE to indicate 5G SRVCC support when registering with EPS and 3G/4G SRVCC support when registering with 5GS |
S2-2000108
| not treated | SA2#136-AH | Vivo Mobile Com... |
| | | | | 5G_SRVCC |
|
|
|
| 23.501 | 0859 | 2 | B | 15.4.0 | Rel-16 | Adding 5G SRVCC description to 23.501 |
S2-1900843
| agreed | SA2#130 | ZTE, China Unic... |
SP-190162
| approved | SA#83 | SA WG2 | 16.0.0 | 5G_SRVCC |
|
|
|
| 23.501 | 0859 | 1 | B | 15.4.0 | Rel-16 | Adding 5G SRVCC description to 23.501 |
S2-1900762
| revised | SA2#130 | ZTE, China Unic... |
| | | | | 5G_SRVCC |
|
|
|
| 23.501 | 0859 | - | B | 15.4.0 | Rel-16 | Adding 5G SRVCC description to 23.501 |
S2-1900505
| revised | SA2#130 | ZTE, China Unic... |
| | | | | 5G_SRVCC |
|
|
|
| 23.502 | 3320 | 2 | A | 17.4.0 | Rel-17 | AMF interaction with GMLC at SRVCC for an Emergency session |
S2-2204958
| agreed | SA2#151-e | Nokia, Nokia Sh... |
SP-220391
| approved | SA#96 | SA WG2 | 17.5.0 | 5G_SRVCC |
|
|
|
| 23.502 | 3320 | 1 | A | 17.4.0 | Rel-17 | AMF interaction with GMLC at SRVCC for an Emergency session |
S2-2204090
| revised | SA2#151-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 23.502 | 3320 | - | A | 17.3.0 | Rel-17 | AMF interaction with GMLC at SRVCC for an Emergency session |
S2-2200111
| revised | SA2#149-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 23.502 | 3319 | 2 | F | 16.12.0 | Rel-16 | AMF interaction with GMLC at SRVCC for an Emergency session |
S2-2204957
| agreed | SA2#151-e | Nokia, Nokia Sh... |
SP-220391
| approved | SA#96 | SA WG2 | 16.13.0 | 5G_SRVCC |
|
|
|
| 23.502 | 3319 | 1 | F | 16.12.0 | Rel-16 | AMF interaction with GMLC at SRVCC for an Emergency session |
S2-2204089
| revised | SA2#151-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 23.502 | 3319 | - | F | 16.11.0 | Rel-16 | AMF interaction with GMLC at SRVCC for an Emergency session |
S2-2200110
| revised | SA2#149-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 23.502 | 2870 | 1 | A | 17.0.0 | Rel-17 | Handling of UTRAN UE radio capabilities |
S2-2104840
| agreed | SA2#145-e | Vodafone |
SP-210328
| approved | SA#92-e | SA WG2 | 17.1.0 | 5G_SRVCC, RACS |
|
|
|
| 23.502 | 2870 | - | A | 17.0.0 | Rel-17 | Handling of UTRAN UE radio capabilities |
S2-2104728
| revised | SA2#145-e | Vodafone |
| | | | | 5G_SRVCC, RACS |
|
|
|
| 23.502 | 2868 | 1 | F | 16.8.0 | Rel-16 | Handling of UTRAN UE radio capabilities |
S2-2104839
| agreed | SA2#145-e | Vodafone |
SP-210328
| approved | SA#92-e | SA WG2 | 16.9.0 | 5G_SRVCC, RACS |
|
|
|
| 23.502 | 2868 | - | F | 16.8.0 | Rel-16 | Handling of UTRAN UE radio capabilities |
S2-2104726
| revised | SA2#145-e | Vodafone |
| | | | | 5G_SRVCC, RACS, SAES |
|
|
|
| 23.502 | 1955 | - | F | 16.3.0 | Rel-16 | Enable a UE to indicate 5G SRVCC support when registering with EPS and 3G/4G SRVCC support when registering with 5GS |
S2-2000111
| not treated | SA2#136-AH | Vivo Mobile Com... |
| | | | | 5G_SRVCC |
|
|
|
| 23.502 | 1954 | - | F | 16.3.0 | Rel-16 | Clarify SRVCC between UDM and AMF |
S2-2000106
| noted | SA2#136-AH | BlackBerry UK Ltd. |
| | | | | 5G_SRVCC |
|
|
|
| 23.502 | 1885 | - | F | 16.2.0 | Rel-16 | Clarification on SRVCC indication during PDU session release |
S2-1911155
| agreed | SA2#136 | ZTE |
SP-191072
| approved | SA#86 | SA WG2 | 16.3.0 | 5G_SRVCC |
|
|
|
| 23.502 | 1884 | 1 | F | 16.2.0 | Rel-16 | Clarification on the EBI allocation when 5G SRVCC is deployed |
S2-1912137
| | SA2#136 | ZTE |
| | | | | 5G_SRVCC |
|
|
|
| 23.502 | 1884 | - | F | 16.2.0 | Rel-16 | Clarification on the EBI allocation when 5G SRVCC is deployed |
S2-1911154
| revised | SA2#136 | ZTE |
| | | | | 5G_SRVCC |
|
|
|
| 23.502 | 1093 | 1 | B | 15.4.1 | Rel-16 | Adding AMF reporting UE SRVCC capability |
S2-1902494
| agreed | SA2#131 | ZTE |
SP-190162
| approved | SA#83 | SA WG2 | 16.0.0 | 5G_SRVCC |
|
|
|
| 23.502 | 1093 | - | B | 15.4.1 | Rel-16 | Adding AMF reporting UE SRVCC capability |
S2-1901993
| revised | SA2#131 | ZTE |
| | | | | 5G_SRVCC |
|
|
|
| 23.502 | 0946 | 2 | B | 15.4.1 | Rel-16 | Adding 5G SRVCC description to 23.502 |
S2-1900844
| agreed | SA2#130 | ZTE, China Unic... |
SP-190162
| approved | SA#83 | SA WG2 | 16.0.0 | 5G_SRVCC |
|
|
|
| 23.502 | 0946 | 1 | B | 15.4.1 | Rel-16 | Adding 5G SRVCC description to 23.502 |
S2-1900763
| revised | SA2#130 | ZTE, China Unic... |
| | | | | 5G_SRVCC |
|
|
|
| 23.502 | 0946 | - | B | 15.4.1 | Rel-16 | Adding 5G SRVCC description to 23.502 |
S2-1900506
| revised | SA2#130 | ZTE, China Unic... |
| | | | | 5G_SRVCC |
|
|
|
| 23.503 | 0342 | 6 | F | 16.2.0 | Rel-16 | SR-VCC with PS to CS handover indication |
S2-1912085
| agreed | SA2#136 | Nokia, Nokia Sh... |
SP-191072
| approved | SA#86 | SA WG2 | 16.3.0 | 5G_SRVCC, eIMS5G_SBA |
|
|
|
| 23.503 | 0342 | 5 | F | 16.2.0 | Rel-16 | SR-VCC with PS to CS handover indication |
S2-1911096
| revised | SA2#136 | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC, eIMS5G_SBA |
|
|
|
| 23.503 | 0342 | 4 | F | 16.2.0 | Rel-16 | 5G to 3G SR-VCC with PS to CS handover indication |
S2-1911042
| merged | SA2#136 | Nokia (?), Noki... |
| | | | | eIMS5G_SBA, 5G_SRVCC |
|
|
|
| 23.503 | 0342 | 3 | F | 16.2.0 | Rel-16 | 5G to 3G SR-VCC with PS to CS handover indication |
S2-1910670
| revised | SA2#135 | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC, eIMS5G_SBA |
|
|
|
| 23.503 | 0342 | 2 | F | 16.2.0 | Rel-16 | 5G to 3G SR-VCC with PS to CS handover indication |
S2-1910295
| revised | SA2#135 | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC, eIMS5G_SBA |
|
|
|
| 23.503 | 0342 | 1 | F | 16.2.0 | Rel-16 | 5G to 3G SR-VCC with PS to CS handover indication |
S2-1910266
| revised | SA2#135 | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC, eIMS5G_SBA |
|
|
|
| 23.503 | 0342 | - | F | 16.2.0 | Rel-16 | 5G to 3G SR-VCC with PS to CS handover indication |
S2-1909747
| revised | SA2#135 | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC, eIMS5G_SBA |
|
|
|
| 23.632 | 0017 | - | F | 16.1.0 | Rel-16 | Remove Editor's Note regarding multiple SRVCC capabilities per system |
C4-203172
| agreed | CT4#98-e | BlackBerry UK L... |
CP-201036
| approved | CT#88-e | CT4 | 16.2.0 | UDICOM, 5G_SRVCC |
|
|
|
| 23.632 | 0006 | 4 | B | 16.0.0 | Rel-16 | Introduce 5G SRVCC support |
C4-201090
| agreed | CT4#96-e | BlackBerry UK L... |
CP-200022
| approved | CT#87-e | CT4 | 16.1.0 | 5G_SRVCC |
|
|
|
| 23.632 | 0006 | 3 | B | 16.0.0 | Rel-16 | Introduce 5G SRVCC support |
C4-201041
| revised | CT4#96-e | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 23.632 | 0006 | 2 | B | 16.0.0 | Rel-16 | Introduce 5G SRVCC support |
C4-200933
| revised | CT4#96-e | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 23.632 | 0006 | 1 | B | 16.0.0 | Rel-16 | Introduce 5G SRVCC support |
C4-200480
| revised | CT4#96-e | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 23.632 | 0006 | - | B | 16.0.0 | Rel-16 | Introduce 5G SRVCC support |
C4-200180
| withdrawn | CT4#96 | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 24.008 | 3213 | - | F | 16.4.0 | Rel-16 | Introduce support for 5G SRVCC support indication when registering with EPS |
C1-202094
| withdrawn | CT1#123-e | BlackBerry Uk Ltd. |
| | | | | 5G_SRVCC |
|
|
|
| 24.008 | 3201 | - | B | 16.2.0 | Rel-16 | Call establishment for 5G-SRVCC |
C1-196755
| agreed | CT1#120 | ZTE, China Unicom |
CP-193091
| approved | CT#86 | CT1 | 16.3.0 | 5G_SRVCC |
|
|
|
| 24.008 | 3200 | - | B | 16.2.0 | Rel-16 | CK and IK derivation for 5G-SRVCC |
C1-196754
| agreed | CT1#120 | ZTE, China Unicom |
CP-193091
| approved | CT#86 | CT1 | 16.3.0 | 5G_SRVCC |
|
|
|
| 24.237 | 1303 | - | B | 17.0.0 | Rel-17 | "SRVCC handover cancelled, IMS session re-establishment required" indicator via NG-RAN |
C1-221827
| agreed | CT1#134-e | Nokia, Nokia Sh... |
CP-220275
| approved | CT#95-e | CT1 | 17.1.0 | TEI17, 5G_SRVCC |
|
|
|
| 24.237 | 1296 | 1 | B | 16.2.0 | Rel-16 | Further introduce support for 5G-SRVCC |
C1-198933
| agreed | CT1#121 | BlackBerry UK L... |
CP-193091
| approved | CT#86 | CT1 | 16.3.0 | 5G_SRVCC |
|
|
|
| 24.237 | 1296 | - | B | 16.2.0 | Rel-16 | Further introduce support for 5G-SRVCC |
C1-198306
| revised | CT1#121 | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 24.237 | 1292 | 2 | B | 16.1.0 | Rel-16 | Completing introducing of 5G SRVCC |
C1-195137
| agreed | CT1#119 | nn |
CP-192053
| approved | CT#85 | CT1 | 16.2.0 | 5G_SRVCC |
|
|
|
| 24.237 | 1292 | 1 | B | 16.1.0 | Rel-16 | Completing introducing of 5G SRVCC |
C1-194946
| revised | CT1#119 | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 24.237 | 1292 | - | B | 16.1.0 | Rel-16 | Completing introducing of 5G SRVCC |
C1-194021
| revised | CT1#119 | BlackBerry UK Ltd. |
| | | | | 5G_SRVCC |
|
|
|
| 24.301 | 3290 | 1 | F | 16.4.0 | Rel-16 | Introduce support for 5G SRVCC support indication when registering with EPS |
C1-202095
| withdrawn | CT1#123-e | BlackBerry Uk Ltd. |
| | | | | 5G_SRVCC |
|
|
|
| 24.301 | 3290 | - | B | 16.2.0 | Rel-16 | Introduce support for 5G SRVCC support indication when registering with EPS |
C1-198012
| revised | CT1#121 | BlackBerry UK Ltd. |
| | | | | 5G_SRVCC |
|
|
|
| 24.501 | 3981 | 2 | B | 17.5.0 | Rel-17 | Failure case for 5G SRVCC |
| | | |
CP-220022
| approved | CT#95-e | Nokia, Nokia Sh... | 17.6.0 | TEI17, 5G_SRVCC |
|
|
|
| 24.501 | 3981 | 1 | B | 17.5.0 | Rel-17 | Failure case for 5G SRVCC |
C1-221952
| agreed | CT1#134-e | Nokia, Nokia Sh... |
CP-220275
| revised | CT#95-e | CT1 | | TEI17, 5G_SRVCC |
|
|
|
| 24.501 | 3981 | - | A | 17.5.0 | Rel-17 | Failure case for 5G SRVCC |
C1-221085
| revised | CT1#134-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 24.501 | 3980 | - | F | 16.10.0 | Rel-16 | Failure case for 5G SRVCC |
C1-221084
| postponed | CT1#134-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 24.501 | 2115 | 2 | F | 16.4.1 | Rel-16 | Initial Registration after 5G-SRVCC |
C1-202638
| agreed | CT1#123-e | ZTE, China Unicom |
CP-201099
| approved | CT#88-e | CT1 | 16.5.0 | 5G_SRVCC |
|
|
|
| 24.501 | 2115 | 1 | F | 16.4.1 | Rel-16 | Initial Registration after 5G-SRVCC |
C1-202529
| revised | CT1#123-e | ZTE, China Unicom |
| | | | | 5G_SRVCC |
|
|
|
| 24.501 | 2115 | - | F | 16.4.1 | Rel-16 | Initial Registration after 5G-SRVCC |
C1-202338
| revised | CT1#123-e | ZTE |
| | | | | 5G_SRVCC |
|
|
|
| 24.501 | 1918 | 1 | C | 16.3.0 | Rel-16 | PDU session release |
C1-200833
| agreed | CT1#122-e | ZTE, China Unic... |
CP-200108
| approved | CT#87-e | CT1 | 16.4.0 | 5G_SRVCC |
|
|
|
| 24.501 | 1918 | - | C | 16.3.0 | Rel-16 | PDU session release at the UE side |
C1-200436
| revised | CT1#122-e | ZTE, China Unic... |
| | | | | 5G_SRVCC |
|
|
|
| 24.501 | 1911 | 1 | B | 16.3.0 | Rel-16 | Use registration message to inform the network when the SRVCC information changes |
C1-200811
| withdrawn | CT1#122-e | BlackBerry UK Ltd. |
| | | | | 5G_SRVCC |
|
|
|
| 24.501 | 1911 | - | B | 16.3.0 | Rel-16 | Use registration message to inform the network when the SRVCC information changes |
C1-200427
| revised | CT1#122-e | BlackBerry UK Ltd. |
| | | | | 5G_SRVCC |
|
|
|
| 24.501 | 1573 | - | B | 16.2.0 | Rel-16 | Call establishment for 5G-SRVCC |
C1-196332
| | CT1#120 | ZTE, China Unicom |
| | | | | 5G_SRVCC |
|
|
|
| 24.501 | 1572 | - | B | 16.2.0 | Rel-16 | CK and IK derivation for 5G-SRVCC |
C1-196331
| | CT1#120 | ZTE, China Unicom |
| | | | | 5G_SRVCC |
|
|
|
| 24.501 | 1188 | 1 | B | 16.0.2 | Rel-16 | MS classmark 2 and supported codec |
C1-193477
| agreed | CT1#117 | ZTE, vivo, Qual... |
CP-191130
| approved | CT#84 | CT1 | 16.1.0 | 5G_SRVCC |
|
|
|
| 24.501 | 1188 | - | B | 16.0.2 | Rel-16 | MS classmark 2 and supported codec |
C1-193243
| revised | CT1#117 | ZTE, vivo, Qual... |
| | | | | 5G_SRVCC |
|
|
|
| 24.501 | 1187 | 1 | B | 16.0.2 | Rel-16 | 5GMM capability for SRVCC from NG-RAN to UTRAN |
C1-193476
| agreed | CT1#117 | ZTE, vivo, Qual... |
CP-191130
| approved | CT#84 | CT1 | 16.1.0 | 5G_SRVCC |
|
|
|
| 24.501 | 1187 | - | B | 16.0.2 | Rel-16 | 5GMM capability for SRVCC from NG-RAN to UTRAN |
C1-193242
| revised | CT1#117 | ZTE, vivo, Qual... |
| | | | | 5G_SRVCC |
|
|
|
| 27.007 | 0680 | - | B | 16.2.0 | Rel-16 | AT Command for 5G-SRVCC |
C1-198083
| agreed | CT1#121 | ZTE, China Unicom |
CP-193091
| approved | CT#86 | CT1 | 16.3.0 | 5G_SRVCC |
|
|
|
| 29.214 | 1636 | 2 | B | 16.1.0 | Rel-16 | 5GSRVCC impacts on Rx |
C3-201493
| agreed | CT3#108-e | ZTE, China Unicom |
CP-200201
| approved | CT#87-e | CT3 | 16.2.0 | 5G_SRVCC |
|
|
|
| 29.214 | 1636 | 1 | B | 16.1.0 | Rel-16 | 5GSRVCC impacts on Rx |
C3-201361
| revised | CT3#108-e | ZTE, China Unicom |
| | | | | 5G_SRVCC |
|
|
|
| 29.214 | 1636 | - | B | 16.1.0 | Rel-16 | 5GSRVCC impacts on Rx |
C3-201195
| revised | CT3#108-e | ZTE, China Unicom |
| | | | | 5G_SRVCC |
|
|
|
| 29.272 | 0811 | 3 | F | 16.2.0 | Rel-16 | Introduce support for 5G SRVCC support indication when registering with EPS |
C4-202281
| withdrawn | CT4#97-e | BlackBerry UK Ltd. |
| | | | | 5G_SRVCC |
|
|
|
| 29.272 | 0811 | 2 | B | 16.1.0 | Rel-16 | Update UE SRVCC capability description |
C4-200897
| withdrawn | CT4#96-e | BlackBerry UK Ltd. |
| | | | | 5G_SRVCC |
|
|
|
| 29.272 | 0811 | 1 | F | 16.0.0 | Rel-16 | Introduce support for 5G SRVCC support indication when registering with EPS |
C4-195335
| revised | CT4#95 | BlackBerry UK Ltd. |
| | | | | 5G_SRVCC |
|
|
|
| 29.272 | 0811 | - | F | 16.0.0 | Rel-16 | Introduce support for 5G SRVCC support indication when registering with EPS |
C4-195226
| revised | CT4#95 | BlackBerry UK Ltd. |
| | | | | 5G_SRVCC |
|
|
|
| 29.274 | 2060 | - | A | 17.6.0 | Rel-17 | MSC Server Identity in Forward Relocation Response during SRVCC handover |
C4-224189
| agreed | CT4#111-e | Nokia, Nokia Sh... |
CP-222063
| approved | CT#97-e | CT4 | 17.7.0 | 5G_SRVCC |
|
|
|
| 29.274 | 2059 | - | F | 16.11.0 | Rel-16 | MSC Server Identity in Forward Relocation Response during SRVCC handover |
C4-224188
| agreed | CT4#111-e | Nokia, Nokia Sh... |
CP-222063
| approved | CT#97-e | CT4 | 16.12.0 | 5G_SRVCC |
|
|
|
| 29.274 | 2047 | 1 | F | 17.4.0 | Rel-17 | SRVCC Cause in Forward Relocation Response |
C4-221493
| agreed | CT4#108-e | Nokia, Nokia Sh... |
CP-220072
| approved | CT#95-e | CT4 | 17.5.0 | 5G_SRVCC, TEI17 |
|
|
|
| 29.274 | 2047 | - | A | 17.4.0 | Rel-17 | SRVCC Cause in Forward Relocation Response |
C4-221165
| revised | CT4#108-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 29.274 | 2046 | - | F | 16.10.0 | Rel-16 | SRVCC Cause in Forward Relocation Response |
C4-221164
| withdrawn | CT4#108-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 29.274 | 2045 | - | F | 16.10.0 | Rel-16 | CR implementation errors (5G SRVCC from 5GS to 3G) |
C4-221162
| agreed | CT4#108-e | Nokia, Nokia Sh... |
CP-220071
| approved | CT#95-e | CT4 | 16.11.0 | 5G_SRVCC |
|
|
|
| 29.274 | 2040 | - | F | 17.4.0 | Rel-17 | 5G-SRVCC from NG-RAN to UTRAN Handover Cancellation |
C4-220111
| agreed | CT4#107-bis-e | Nokia, Nokia Sh... |
CP-220072
| approved | CT#95-e | CT4 | 17.5.0 | TEI17, 5G_SRVCC |
|
|
|
| 29.274 | 2039 | 1 | A | 17.4.0 | Rel-17 | CR implementation errors (5G SRVCC from 5GS to 3G) |
C4-221163
| agreed | CT4#108-e | Nokia, Nokia Sh... |
CP-220071
| approved | CT#95-e | CT4 | 17.5.0 | 5G_SRVCC |
|
|
|
| 29.274 | 2039 | - | F | 17.4.0 | Rel-17 | CR implementation errors (5G SRVCC from 5GS to 3G) |
C4-220110
| revised | CT4#107-bis-e | Nokia, Nokia Sh... |
| | | | | TEI17, 5G_SRVCC |
|
|
|
| 29.274 | 1979 | 1 | B | 16.2.0 | Rel-16 | 5G-SRVCC Procedure for Emergency Session |
C4-201163
| agreed | CT4#96-e | ZTE, China Unicom |
CP-200022
| approved | CT#87-e | CT4 | 16.3.0 | 5G_SRVCC |
|
|
|
| 29.274 | 1979 | - | B | 16.2.0 | Rel-16 | 5G-SRVCC Procedure for Emergency Session |
C4-200656
| revised | CT4#96-e | ZTE, China Unicom |
| | | | | 5G_SRVCC |
|
|
|
| 29.274 | 1974 | - | B | 16.1.0 | Rel-16 | Adding ClassMark 2 and Supported Codec for 5G SRVCC to 29.274 |
C4-195149
| agreed | CT4#95 | China Unicom, ZTE |
CP-193061
| approved | CT#86 | CT4 | 16.2.0 | 5G_SRVCC |
|
|
|
| 29.274 | 1967 | 1 | B | 16.1.0 | Rel-16 | No PDN Connection Transferred during 5G SRVCC HO procedure |
C4-194433
| agreed | CT4#94 | ZTE, China Unicom |
CP-193061
| approved | CT#86 | CT4 | 16.2.0 | 5G_SRVCC |
|
|
|
| 29.274 | 1967 | - | B | 16.1.0 | Rel-16 | No PDN Connection Transferred during 5G SRVCC HO procedure |
C4-194086
| revised | CT4#94 | ZTE, China Unicom |
| | | | | 5G_SRVCC |
|
|
|
| 29.274 | 1954 | - | B | 16.0.0 | Rel-16 | Adding 5G SRVCC Support |
C4-193145
| agreed | CT4#93 | China Unicom, ZTE |
CP-192188
| approved | CT#85 | CT4 | 16.1.0 | 5G_SRVCC |
|
|
|
| 29.303 | 0120 | 1 | B | 15.5.0 | Rel-16 | Selection of MME_SRVCC |
C4-193613
| agreed | CT4#93 | China Unicom, ZTE |
CP-192188
| approved | CT#85 | CT4 | 16.0.0 | 5G_SRVCC |
|
|
|
| 29.303 | 0120 | - | B | 15.5.0 | Rel-16 | Selection of MME_SRVCC |
C4-193146
| revised | CT4#93 | China Unicom, ZTE |
| | | | | 5G_SRVCC |
|
|
|
| 29.328 | 0634 | - | F | 16.0.0 | Rel-16 | Remove Editor's Note regarding obtaining 4G SRVCC capability from UDM |
C4-203174
| agreed | CT4#98-e | BlackBerry UK L... |
CP-201036
| approved | CT#88-e | CT4 | 16.1.0 | 5G_SRVCC |
|
|
|
| 29.328 | 0631 | 2 | B | 15.8.0 | Rel-16 | Introduce support for accessing 5G SRVCC data via Sh |
C4-201042
| agreed | CT4#96-e | BlackBerry UK L... |
CP-200022
| approved | CT#87-e | CT4 | 16.0.0 | 5G_SRVCC |
|
|
|
| 29.328 | 0631 | 1 | B | 15.8.0 | Rel-16 | Introduce support for accessing 5G SRVCC data via Sh |
C4-200481
| revised | CT4#96-e | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 29.328 | 0631 | - | B | 15.8.0 | Rel-16 | Introduce support for accessing 5G SRVCC data via Sh |
C4-200181
| withdrawn | CT4#96 | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 29.329 | 0254 | - | F | 16.1.0 | Rel-16 | IMEISV and 5G SRVCC Capability missing in Data Reference AVP |
C4-211057
| agreed | CT4#102-e | Hewlett-Packard... |
CP-210044
| approved | CT#91-e | CT4 | 16.2.0 | TEI16, 5G_SRVCC |
|
|
|
| 29.502 | 0243 | 2 | B | 16.1.1 | Rel-16 | PDU Session Release due to SRVCC |
C4-195575
| agreed | CT4#95 | Ericsson, ZTE, ... |
CP-193061
| approved | CT#86 | CT4 | 16.2.0 | 5G_SRVCC |
|
|
|
| 29.502 | 0243 | 1 | B | 16.1.1 | Rel-16 | PDU Session Release due to SRVCC |
C4-195437
| revised | CT4#95 | Ericsson, ZTE, ... |
| | | | | 5G_SRVCC |
|
|
|
| 29.502 | 0243 | - | B | 16.1.0 | Rel-16 | PDU Session Release due to SRVCC |
C4-195272
| revised | CT4#95 | Ericsson |
| | | | | 5G_SRVCC |
|
|
|
| 29.502 | 0229 | - | B | 16.1.0 | Rel-16 | Cause Value for Indicating PS to CS Handover in PDU Session Release Procedure |
C4-195150
| merged | CT4#95 | ZTE, China Unicom |
| | | | | 5G_SRVCC |
|
|
|
| 29.503 | 0371 | 1 | F | 16.2.0 | Rel-16 | Correcting ueSrvccCapability |
C4-201044
| postponed | CT4#96-e | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 29.503 | 0371 | - | F | 16.2.0 | Rel-16 | Correcting ueSrvccCapability |
C4-200890
| revised | CT4#96-e | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 29.503 | 0215 | 1 | B | 16.0.0 | Rel-16 | Report 5G SRVCC Capability to UDM |
C4-193567
| agreed | CT4#93 | ZTE, China Unicom |
CP-192188
| approved | CT#85 | CT4 | 16.1.0 | 5G_SRVCC |
|
|
|
| 29.503 | 0215 | - | B | 16.0.0 | Rel-16 | Report 5G SRVCC Capability to UDM |
C4-193143
| revised | CT4#93 | ZTE, China Unicom |
| | | | | 5G_SRVCC |
|
|
|
| 29.503 | 0214 | 1 | B | 16.0.0 | Rel-16 | Provide 5G SRVCC Related Subcription to AMF |
C4-193563
| agreed | CT4#93 | China Unicom, ZTE |
CP-192188
| approved | CT#85 | CT4 | 16.1.0 | 5G_SRVCC |
|
|
|
| 29.503 | 0214 | - | B | 16.0.0 | Rel-16 | Provide 5G SRVCC Related Subcription to AMF |
C4-193142
| revised | CT4#93 | China Unicom, ZTE |
| | | | | 5G_SRVCC |
|
|
|
| 29.512 | 0372 | 4 | B | 16.2.0 | Rel-16 | Indication of PS to CS Handover for 5G SRVCC from SMF to PCF |
| | | |
CP-193259
| approved | CT#86 | ZTE, Ericsson | 16.3.0 | 5G_SRVCC |
|
|
|
| 29.512 | 0372 | 3 | B | 16.2.0 | Rel-16 | Indication of PS to CS Handover for 5G SRVCC from SMF to PCF |
C3-195409
| revised | CT3#107 | ZTE, Ericsson |
CP-193211
| revised | CT#86 | CT3 | | 5G_SRVCC |
|
|
|
| 29.512 | 0372 | 2 | B | 16.2.0 | Rel-16 | Indication of PS to CS Handover for 5G SRVCC from SMF to PCF |
C3-195401
| revised | CT3#107 | ZTE, Ericsson |
| | | | | 5G_SRVCC |
|
|
|
| 29.512 | 0372 | 1 | B | 16.2.0 | Rel-16 | Indication of PS to CS Handover for 5G SRVCC from SMF to PCF |
C3-195288
| revised | CT3#107 | ZTE, Ericsson |
| | | | | 5G_SRVCC |
|
|
|
| 29.512 | 0372 | - | B | 16.2.0 | Rel-16 | Indication of PS to CS Handover for 5G SRVCC from SMF to PCF |
C3-195042
| revised | CT3#107 | ZTE |
| | | | | 5G_SRVCC |
|
|
|
| 29.513 | 0124 | - | B | 16.2.0 | Rel-16 | SRVCC impacts on QoS mapping |
C3-201196
| agreed | CT3#108-e | ZTE, China Unicom |
CP-200201
| approved | CT#87-e | CT3 | 16.3.0 | 5G_SRVCC |
|
|
|
| 29.514 | 0181 | 1 | B | 16.3.0 | Rel-16 | Update of the indication of PS to CS Handover |
C3-201360
| agreed | CT3#108-e | Ericsson |
CP-200201
| approved | CT#87-e | CT3 | 16.4.0 | 5G_SRVCC |
|
|
|
| 29.514 | 0181 | - | B | 16.3.0 | Rel-16 | Update of the indication of PS to CS Handover |
C3-201184
| revised | CT3#108-e | Ericsson |
| | | | | 5G_SRVCC |
|
|
|
| 29.514 | 0147 | 5 | B | 16.2.0 | Rel-16 | Indication of PS to CS Handover for 5G SRVCC from PCF to AF |
| | | |
CP-193260
| approved | CT#86 | ZTE | 16.3.0 | 5G_SRVCC |
|
|
|
| 29.514 | 0147 | 4 | B | 16.2.0 | Rel-16 | Indication of PS to CS Handover for 5G SRVCC from PCF to AF |
C3-195410
| revised | CT3#107 | ZTE |
CP-193211
| revised | CT#86 | CT3 | | 5G_SRVCC |
|
|
|
| 29.514 | 0147 | 3 | B | 16.2.0 | Rel-16 | Indication of PS to CS Handover for 5G SRVCC from PCF to AF |
C3-195394
| revised | CT3#107 | ZTE |
| | | | | 5G_SRVCC |
|
|
|
| 29.514 | 0147 | 2 | B | 16.2.0 | Rel-16 | Indication of PS to CS Handover for 5G SRVCC from PCF to AF |
C3-195289
| revised | CT3#107 | ZTE |
| | | | | 5G_SRVCC |
|
|
|
| 29.514 | 0147 | 1 | B | 16.2.0 | Rel-16 | Indication of PS to CS Handover for 5G SRVCC from PCF to AF |
C3-195221
| revised | CT3#107 | ZTE |
| | | | | 5G_SRVCC |
|
|
|
| 29.514 | 0147 | - | B | 16.2.0 | Rel-16 | Indication of PS to CS Handover for 5G SRVCC from PCF to AF |
C3-195043
| revised | CT3#107 | ZTE |
| | | | | 5G_SRVCC |
|
|
|
| 29.518 | 0779 | - | A | 17.6.0 | Rel-17 | MSC server Identity for 5G-SRVCC |
C4-224280
| merged | CT4#111-e | Huawei |
| | | | | 5G_SRVCC |
|
|
|
| 29.518 | 0778 | - | F | 16.12.0 | Rel-16 | MSC server Identity for 5G-SRVCC |
C4-224279
| merged | CT4#111-e | Huawei |
| | | | | 5G_SRVCC |
|
|
|
| 29.518 | 0764 | 1 | A | 17.6.0 | Rel-17 | MSC Server Identity in Namf_Location_EventNotify during SRVCC handover |
C4-224624
| agreed | CT4#111-e | Nokia, Nokia Sh... |
CP-222063
| approved | CT#97-e | CT4 | 17.7.0 | 5G_SRVCC |
|
|
|
| 29.518 | 0764 | - | A | 17.6.0 | Rel-17 | MSC Server Identity in Namf_Location_EventNotify during SRVCC handover |
C4-224228
| revised | CT4#111-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 29.518 | 0763 | 2 | F | 16.12.0 | Rel-16 | MSC Server Identity in Namf_Location_EventNotify during SRVCC handover |
C4-224623
| agreed | CT4#111-e | Nokia, Nokia Sh... |
CP-222063
| approved | CT#97-e | CT4 | 16.13.0 | 5G_SRVCC |
|
|
|
| 29.518 | 0763 | 1 | F | 16.12.0 | Rel-16 | MSC Server Identity in Namf_Location_EventNotify during SRVCC handover |
C4-224622
| revised | CT4#111-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 29.518 | 0763 | - | F | 16.12.0 | Rel-16 | MSC Server Identity in Namf_Location_EventNotify during SRVCC handover |
C4-224227
| revised | CT4#111-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 29.518 | 0762 | - | A | 17.6.0 | Rel-17 | MSC Server Identity in Namf_Location_EventNotify during SRVCC handover |
C4-224225
| withdrawn | CT4#111-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 29.518 | 0761 | - | F | 16.12.0 | Rel-16 | MSC Server Identity in Namf_Location_EventNotify during SRVCC handover |
C4-224224
| withdrawn | CT4#111-e | Nokia, Nokia Sh... |
| | | | | 5G_SRVCC |
|
|
|
| 29.518 | 0665 | - | F | 17.4.0 | Rel-17 | Correction to CreateUEContext service operation regarding 5G-SRVCC |
C4-220112
| agreed | CT4#107-bis-e | Nokia, Nokia Sh... |
CP-220072
| approved | CT#95-e | CT4 | 17.5.0 | TEI17, 5G_SRVCC |
|
|
|
| 29.518 | 0259 | 1 | F | 16.1.0 | Rel-16 | Correct maintencance of STN-SR for 4G SRVCC and 5G SRVCC |
C4-195333
| postponed | CT4#95 | BlackBerry UK Ltd. |
| | | | | 5G_SRVCC |
|
|
|
| 29.518 | 0193 | 1 | B | 16.0.0 | Rel-16 | Transfer 5G SRVCC Parameters between AMFs |
C4-193580
| agreed | CT4#93 | China Unicom, ZTE |
CP-192188
| approved | CT#85 | CT4 | 16.1.0 | 5G_SRVCC |
|
|
|
| 29.518 | 0193 | - | B | 16.0.0 | Rel-16 | Transfer 5G SRVCC Parameters between AMFs |
C4-193141
| revised | CT4#93 | China Unicom, ZTE |
| | | | | 5G_SRVCC |
|
|
|
| 29.571 | 0193 | 1 | B | 16.2.0 | Rel-16 | Introducing ueSrvccCapability |
C4-201043
| postponed | CT4#96-e | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 29.571 | 0193 | - | B | 16.2.0 | Rel-16 | Introducing ueSrvccCapability |
C4-200887
| revised | CT4#96-e | BlackBerry UK L... |
| | | | | 5G_SRVCC |
|
|
|
| 29.571 | 0105 | 2 | B | 16.0.0 | Rel-16 | Common Data Type for 5G SRVCC |
| | | |
CP-192211
| approved | CT#85 | ZTE, China Unicom | 16.1.0 | 5G_SRVCC |
|
|
|
| 29.571 | 0105 | 1 | B | 16.0.0 | Rel-16 | Common Data Type for 5G SRVCC |
C4-193573
| revised | CT4#93 | ZTE, China Unicom |
CP-192188
| revised | CT#85 | CT4 | | 5G_SRVCC |
|
|
|
| 29.571 | 0105 | - | B | 16.0.0 | Rel-16 | Common Data Type for 5G SRVCC |
C4-193144
| revised | CT4#93 | ZTE, China Unicom |
| | | | | 5G_SRVCC |
|