|
| 29.503 | 1262 | - | F | 18.5.0 | Rel-18 | Clarify response codes for Reauth Notification in different cases |
C4-242091
| | CT4#123 | ZTE |
| | | | | HN_Auth |
|
|
| 29.503 | 1246 | - | F | 18.5.0 | Rel-18 | Updates on auth-trigger URI |
C4-241193
| agreed | CT4#122 | Huawei |
| | | | | HN_Auth |
|
|
| 29.503 | 1185 | 1 | B | 18.4.0 | Rel-18 | Reauthentication pending |
C4-240087
| postponed | CT4#121 | Nokia, Nokia Sh... |
| | | | | HN_Auth |
|
|
| 29.503 | 1185 | - | B | 18.3.0 | Rel-18 | Reauthentication pending |
C4-235047
| revised | CT4#119 | Nokia, Nokia Sh... |
| | | | | HN_Auth |
|
|
| 29.503 | 1180 | 1 | F | 18.3.0 | Rel-18 | Addition of "AaNF" in Nudm Subscriber management service |
C4-234532
| agreed | CT4#118 | Ericsson |
CP-233035
| approved | CT#102 | CT4 | 18.4.0 | HN_Auth |
|
|
| 29.503 | 1180 | - | F | 18.3.0 | Rel-18 | Addition of "AaNF" in Nudm Subscriber management service |
C4-234406
| revised | CT4#118 | Ericsson |
| | | | | HN_Auth |
|
|
| 29.503 | 1166 | - | F | 18.3.0 | Rel-18 | Update the service operation name |
C4-234209
| agreed | CT4#118 | Huawei |
CP-233035
| approved | CT#102 | CT4 | 18.4.0 | HN_Auth |
|
|
| 29.503 | 1165 | - | F | 18.3.0 | Rel-18 | Clarification on REAUTHENTICATION_NOT_ALLOWED |
C4-234208
| postponed | CT4#118 | Huawei |
| | | | | HN_Auth |
|
|
| 29.503 | 1159 | 1 | B | 18.3.0 | Rel-18 | Reauthentication ongoing when receiving Auth Trigger |
C4-234531
| agreed | CT4#118 | ZTE |
CP-233035
| approved | CT#102 | CT4 | 18.4.0 | HN_Auth |
|
|
| 29.503 | 1159 | - | B | 18.3.0 | Rel-18 | Reauthentication ongoing when receiving Auth Trigger |
C4-234080
| revised | CT4#118 | ZTE |
| | | | | HN_Auth |
|
|
| 29.503 | 1158 | - | B | 18.3.0 | Rel-18 | UE Not Reachable during Reauth Notification |
C4-234079
| postponed | CT4#118 | ZTE |
| | | | | HN_Auth |
|
|
| 29.503 | 1157 | 1 | B | 18.3.0 | Rel-18 | Procedure Conflict during Reauth Notification |
C4-235144
| postponed | CT4#119 | ZTE |
| | | | | HN_Auth |
|
|
| 29.503 | 1157 | - | B | 18.3.0 | Rel-18 | Procedure Conflict during Reauth Notification |
C4-234078
| postponed | CT4#118 | ZTE |
| | | | | HN_Auth |
|
|
| 29.503 | 1156 | 3 | B | 18.3.0 | Rel-18 | Reauthentication required during EPS to 5GS mobility |
C4-234659
| agreed | CT4#118 | ZTE |
CP-233035
| approved | CT#102 | CT4 | 18.4.0 | HN_Auth |
|
|
| 29.503 | 1156 | 2 | B | 18.3.0 | Rel-18 | Reauthentication required during EPS to 5GS mobility |
C4-234578
| revised | CT4#118 | ZTE |
| | | | | HN_Auth |
|
|
| 29.503 | 1156 | 1 | B | 18.3.0 | Rel-18 | Reauthentication required during EPS to 5GS mobility |
C4-234530
| revised | CT4#118 | ZTE |
| | | | | HN_Auth |
|
|
| 29.503 | 1156 | - | B | 18.3.0 | Rel-18 | Reauthentication required during EPS to 5GS mobility |
C4-234077
| revised | CT4#118 | ZTE |
| | | | | HN_Auth |
|
|
| 33.501 | 2027 | - | F | 18.5.0 | Rel-18 | Clarifications for HONTRA procedure with respect to failure cases |
S3-242295
| | SA3#116 | Ericsson |
| | | | | HN_Auth |
|
|
| 33.501 | 1997 | - | F | 18.5.0 | Rel-18 | CR on the failure cases in home network triggered re-authentication |
S3-241896
| | SA3#116 | ZTE Corporation |
| | | | | HN_Auth |
|
|
| 33.501 | 1926 | 1 | F | 18.4.0 | Rel-19 | Clarification on alignment of message and failure cause in HONTRA |
S3-240854
| not pursued | SA3#115 | Huawei, HiSilicon |
| | | | | HN_Auth |
|
|
| 33.501 | 1926 | - | F | 18.4.0 | Rel-19 | Clarification on alignment of message and failure cause in HONTRA |
S3-240558
| revised | SA3#115 | Huawei, HiSilicon |
| | | | | HN_Auth |
|
|
| 33.501 | 1912 | - | F | 18.4.0 | Rel-18 | Add service operations to TS 33.501 based on HONTRA |
S3-240462
| agreed | SA3#115 | ZTE Corporation |
SP-240355
| approved | SA#103 | SA WG3 | 18.5.0 | HN_Auth |
|
|
| 33.501 | 1911 | 1 | F | 18.4.0 | Rel-18 | Clear up for HONTRA procedure |
S3-240853
| agreed | SA3#115 | ZTE Corporation |
SP-240355
| approved | SA#103 | SA WG3 | 18.5.0 | HN_Auth |
|
|
| 33.501 | 1911 | - | F | 18.4.0 | Rel-18 | Clear up for HONTRA procedure |
S3-240461
| revised | SA3#115 | ZTE Corporation |
| | | | | HN_Auth |
|
|
| 33.501 | 1910 | - | F | 18.4.0 | Rel-18 | CR on the failure cases in home network triggered re-authentication |
S3-240459
| merged | SA3#115 | ZTE Corporation |
| | | | | HN_Auth |
|
|
| 33.501 | 1902 | - | F | 18.4.0 | Rel-18 | Editorial Correction |
S3-240355
| merged | SA3#115 | Nokia, Nokia Sh... |
| | | | | HN_Auth |
|
|
| 33.501 | 1866 | - | F | 18.3.0 | Rel-18 | Clarifications of the AMF and UDM behaviour |
S3-234795
| merged | SA3#113 | Ericsson |
| | | | | HN_Auth |
|
|
| 33.501 | 1865 | - | F | 18.3.0 | Rel-18 | Implementation corrections |
S3-234794
| merged | SA3#113 | Ericsson |
| | | | | HN_Auth |
|
|
| 33.501 | 1833 | - | F | 18.3.0 | Rel-18 | Clarification on signalling overload in Home Network Triggered Authentication |
S3-234680
| not pursued | SA3#113 | LG Electronics |
| | | | | HN_Auth |
|
|
| 33.501 | 1830 | 1 | F | 18.3.0 | Rel-18 | clarification for HONTRA procedure |
S3-235040
| agreed | SA3#113 | Huawei, HiSilicon |
SP-231332
| approved | SA#102 | SA WG3 | 18.4.0 | HN_Auth |
|
|
| 33.501 | 1830 | - | F | 18.3.0 | Rel-18 | clarification for HONTRA procedure |
S3-234655
| revised | SA3#113 | Huawei, HiSilicon |
| | | | | HN_Auth |
|
|
| 33.501 | 1815 | - | F | 18.3.0 | Rel-18 | HONTRA procedure corrections |
S3-234598
| merged | SA3#113 | ZTE Corporation |
| | | | | HN_Auth |
|
|
| 33.501 | 1814 | 1 | F | 18.3.0 | Rel-18 | Clarify AMF responses in HONTRA procedure. |
S3-235039
| withdrawn | SA3#113 | ZTE Corporation |
| | | | | HN_Auth |
|
|
| 33.501 | 1814 | - | F | 18.3.0 | Rel-18 | Clarify AMF responses in HONTRA procedure. |
S3-234597
| not pursued | SA3#113 | ZTE Corporation |
| | | | | HN_Auth |
|
|
| 33.501 | 1813 | 1 | F | 18.3.0 | Rel-18 | Reuse error code during home network triggered primary authentication procedure |
S3-235038
| agreed | SA3#113 | ZTE |
SP-231332
| approved | SA#102 | SA WG3 | 18.4.0 | HN_Auth |
|
|
| 33.501 | 1813 | - | F | 18.3.0 | Rel-18 | Reuse error code during home network triggered primary authentication procedure |
S3-234596
| revised | SA3#113 | ZTE |
| | | | | HN_Auth |
|
|
| 33.501 | 1793 | 1 | F | 18.3.0 | Rel-18 | Callback URI clarification and API correction |
S3-235041
| withdrawn | SA3#113 | Nokia, Nokia Sh... |
| | | | | HN_Auth |
|
|
| 33.501 | 1793 | - | F | 18.3.0 | Rel-18 | Callback URI clarification and API correction |
S3-234534
| merged | SA3#113 | Nokia, Nokia Sh... |
| | | | | HN_Auth |
|
|
| 33.535 | 0202 | - | F | 18.2.0 | Rel-18 | Adding UDM additional function to TS 33.535 in R18 |
S3-240451
| agreed | SA3#115 | ZTE Corporation |
SP-240355
| approved | SA#103 | SA WG3 | 18.3.0 | HN_Auth |
|
|
| 33.535 | 0201 | 1 | F | 18.2.0 | Rel-18 | KAF re-keying after expiration triggered by AAnF |
S3-240995
| agreed | SA3#115 | ZTE Corporation |
SP-240355
| approved | SA#103 | SA WG3 | 18.3.0 | HN_Auth |
|
|
| 33.535 | 0201 | - | F | 18.2.0 | Rel-18 | KAF re-keying after expiration triggered by AAnF |
S3-240449
| revised | SA3#115 | ZTE Corporation |
| | | | | HN_Auth |
|
|
| 33.535 | 0200 | - | F | 18.2.0 | Rel-18 | KAF re-keying after expiration triggered by AF |
S3-240448
| not pursued | SA3#115 | ZTE Corporation |
| | | | | HN_Auth |
|
|
| 33.535 | 0194 | - | F | 18.1.0 | Rel-18 | Adding indication to inform UE of A-KID refresh |
S3-234595
| not pursued | SA3#113 | ZTE Corporation |
| | | | | HN_Auth |
|
|
| 33.535 | 0193 | - | F | 18.1.0 | Rel-18 | Update AKMA related UDM services |
S3-234594
| agreed | SA3#113 | ZTE Corporation |
SP-231332
| approved | SA#102 | SA WG3 | 18.2.0 | HN_Auth |
|
|
| 33.535 | 0192 | - | F | 18.1.0 | Rel-18 | Update AKMA key lifetimes |
S3-234593
| not pursued | SA3#113 | ZTE Corporation |
| | | | | HN_Auth |
|