|
| 23.501 | 2457 | 1 | B | 16.7.0 | Rel-17 | Introduction of AKMA into the reference architecture |
S2-2100069
| agreed | SA2#143-e | Nokia, Nokia Sh... |
SP-210067
| approved | SA#91-e | SA WG2 | 17.0.0 | AKMA |
|
|
| 23.501 | 2457 | - | F | 16.6.0 | Rel-16 | Introduction of AKMA into the reference architecture |
S2-2006931
| revised | SA2#141-e | Nokia, Nokia Sh... |
| | | | | AKMA |
|
|
| 33.220 | 0206 | 1 | B | 16.2.0 | Rel-17 | CR for AKMA changes to TS 33.220 in Rel-17 |
S3-203487
| agreed | SA3#101-e | China Mobile |
SP-201006
| approved | SA#90-e | SA WG3 | 17.0.0 | AKMA |
|
|
| 33.220 | 0206 | - | B | 16.2.0 | Rel-17 | CR for AKMA changes to TS 33.220 in Rel-17 |
S3-202873
| revised | SA3#101-e | China Mobile |
| | | | | AKMA |
|
|
| 33.501 | 1195 | - | B | 17.2.1 | Rel-17 | [CR] HN triggering Primary (Re)Authentication |
S3-212903
| not pursued | SA3#104-e | Samsung |
| | | | | AKMA |
|
|
| 33.501 | 1161 | - | F | 17.2.1 | Rel-17 | Add a new procedure to enable the AF to refresh the Kaf |
S3-212607
| withdrawn | SA3#104-e | Huawei, HiSilicon |
| | | | | AKMA |
|
|
| 33.501 | 1151 | - | F | 17.2.1 | Rel-17 | Add Routing indicator in Authentication response |
S3-212528
| agreed | SA3#104-e | ZTE Corporation |
SP-210842
| approved | SA#93-e | SA WG3 | 17.3.0 | AKMA |
|
|
| 33.501 | 1084 | - | F | 17.1.0 | Rel-17 | Add Routing indicator in Authentication response |
S3-211553
| not pursued | SA3#103-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.501 | 0996 | - | F | 16.4.0 | Rel-16 | Addition of UDM sending GPSI of the UE for AKMA |
S3-203192
| not pursued | SA3#101-e | Qualcomm Incorp... |
| | | | | AKMA |
|
|
| 33.501 | 0959 | 1 | B | 16.4.0 | Rel-17 | CR for AKMA changes to TS 33.501 in Rel-17 |
S3-203486
| agreed | SA3#101-e | China Mobile In... |
SP-201006
| approved | SA#90-e | SA WG3 | 17.0.0 | AKMA |
|
|
| 33.501 | 0959 | - | B | 16.4.0 | Rel-17 | CR for AKMA changes to TS 33.501 in Rel-17 |
S3-202872
| revised | SA3#101-e | China Mobile In... |
| | | | | AKMA |
|
|
| 33.535 | 0209 | - | A | 18.2.0 | Rel-18 | Routing indicator update issue in the A-KID construction procedure Release 18 (mirror) |
S3-240790
| not pursued | SA3#115 | Xiaomi |
| | | | | AKMA |
|
|
| 33.535 | 0208 | - | F | 17.10.0 | Rel-17 | Routing indicator update issue in the A-KID construction procedure Release 17 |
S3-240789
| not pursued | SA3#115 | Xiaomi Communic... |
| | | | | AKMA |
|
|
| 33.535 | 0204 | - | F | 18.2.0 | Rel-18 | CR on AKMA service restrictions |
S3-240454
| not pursued | SA3#115 | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0203 | - | F | 17.10.0 | Rel-17 | Adding UDM additional function to TS 33.535 in R17 |
S3-240452
| agreed | SA3#115 | ZTE Corporation |
SP-240344
| approved | SA#103 | SA WG3 | 17.11.0 | AKMA |
|
|
| 33.535 | 0199 | - | B | 18.2.0 | Rel-18 | AKMA service restriction in roaming |
S3-240365
| merged | SA3#115 | NDRE, Ministère... |
| | | | | AKMA |
|
|
| 33.535 | 0197 | - | A | 18.1.0 | Rel-18 | Routing indicator update issue in the A-KID construction procedure Release 18 (mirror) |
S3-234913
| not pursued | SA3#113 | Xiaomi |
| | | | | AKMA |
|
|
| 33.535 | 0196 | - | F | 17.9.0 | Rel-17 | Routing indicator update issue in the A-KID construction procedure Release 17 |
S3-234912
| not pursued | SA3#113 | Xiaomi |
| | | | | AKMA |
|
|
| 33.535 | 0191 | 1 | A | 18.1.0 | Rel-18 | Editorial corrections to TS 33.535 in R18 |
S3-235081
| agreed | SA3#113 | ZTE Corporation |
SP-231326
| approved | SA#102 | SA WG3 | 18.2.0 | AKMA |
|
|
| 33.535 | 0191 | - | A | 18.1.0 | Rel-18 | Editorial corrections to TS 33.535 in R18 |
S3-234592
| revised | SA3#113 | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0190 | 1 | F | 17.9.0 | Rel-17 | Editorial corrections to TS 33.535 in R17 |
S3-235080
| agreed | SA3#113 | ZTE Corporation |
SP-231326
| approved | SA#102 | SA WG3 | 17.10.0 | AKMA |
|
|
| 33.535 | 0190 | - | F | 17.9.0 | Rel-17 | Editorial corrections to TS 33.535 in R17 |
S3-234591
| revised | SA3#113 | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0185 | 1 | A | 18.1.0 | Rel-18 | Existing AKMA procedure alignment |
S3-235017
| agreed | SA3#113 | Nokia, Nokia Sh... |
SP-231326
| approved | SA#102 | SA WG3 | 18.2.0 | AKMA |
|
|
| 33.535 | 0185 | - | A | 18.1.0 | Rel-18 | Editorial alignment |
S3-234528
| revised | SA3#113 | Nokia, Nokia Sh... |
| | | | | AKMA |
|
|
| 33.535 | 0184 | 1 | F | 17.9.0 | Rel-17 | Existing AKMA procedure alignment |
S3-235016
| agreed | SA3#113 | Nokia, Nokia Sh... |
SP-231326
| approved | SA#102 | SA WG3 | 17.10.0 | AKMA |
|
|
| 33.535 | 0184 | - | F | 17.9.0 | Rel-17 | Editorial alignment |
S3-234527
| revised | SA3#113 | Nokia, Nokia Sh... |
| | | | | AKMA |
|
|
| 33.535 | 0183 | - | A | 18.1.0 | Rel-18 | A-KID privacy related requirments |
S3-234526
| not pursued | SA3#113 | Nokia, Nokia Sh... |
| | | | | AKMA |
|
|
| 33.535 | 0182 | - | F | 17.9.0 | Rel-17 | A-KID privacy related requirments |
S3-234525
| not pursued | SA3#113 | Nokia, Nokia Sh... |
| | | | | AKMA |
|
|
| 33.535 | 0181 | 1 | A | 18.1.0 | Rel-18 | Correction in UDM and GPSI related requirements |
S3-235015
| agreed | SA3#113 | Nokia, Nokia Sh... |
SP-231326
| approved | SA#102 | SA WG3 | 18.2.0 | AKMA |
|
|
| 33.535 | 0181 | - | A | 18.1.0 | Rel-18 | Correction in UDM and GPSI related requirements |
S3-234524
| revised | SA3#113 | Nokia, Nokia Sh... |
| | | | | AKMA |
|
|
| 33.535 | 0180 | 1 | F | 17.9.0 | Rel-17 | Correction in UDM and GPSI related requirements |
S3-235014
| agreed | SA3#113 | Nokia, Nokia Sh... |
SP-231326
| approved | SA#102 | SA WG3 | 17.10.0 | AKMA |
|
|
| 33.535 | 0180 | - | F | 17.9.0 | Rel-17 | Correction in UDM and GPSI related requirements |
S3-234523
| revised | SA3#113 | Nokia, Nokia Sh... |
| | | | | AKMA |
|
|
| 33.535 | 0176 | - | F | 18.0.0 | Rel-18 | Clarification on Kaf refresh in AKMA |
S3-234044
| revised | SA3#112 | OPPO |
| | | | | AKMA |
|
|
| 33.535 | 0174 | - | F | 18.0.0 | Rel-18 | Clarification on Kaf refresh in AKMA |
S3-234016
| withdrawn | SA3#112 | OPPO |
| | | | | AKMA |
|
|
| 33.535 | 0168 | 1 | A | 18.0.0 | Rel-18 | Clarification on the description about AAnF |
S3-234223
| agreed | SA3#112 | China Telecom |
SP-230881
| approved | SA#101 | SA WG3 | 18.1.0 | AKMA |
|
|
| 33.535 | 0168 | - | A | 18.0.0 | Rel-18 | Clarification on the description about AAnF |
S3-233836
| revised | SA3#112 | China Telecom |
| | | | | AKMA |
|
|
| 33.535 | 0167 | 1 | F | 17.8.0 | Rel-17 | Clarification on the description about AAnF |
S3-234222
| agreed | SA3#112 | China Telecom |
SP-230881
| approved | SA#101 | SA WG3 | 17.9.0 | AKMA |
|
|
| 33.535 | 0167 | - | F | 17.8.0 | Rel-17 | Clarification on the description about AAnF |
S3-233833
| revised | SA3#112 | China Telecom |
| | | | | AKMA |
|
|
| 33.535 | 0163 | - | A | 18.0.0 | Rel-18 | Update the definition of AKMA context in TS 33.535 |
S3-233682
| agreed | SA3#112 | ZTE Corporation |
SP-230881
| approved | SA#101 | SA WG3 | 18.1.0 | AKMA |
|
|
| 33.535 | 0162 | - | F | 17.8.0 | Rel-17 | Update the definition of AKMA context in TS 33.535 |
S3-233681
| agreed | SA3#112 | ZTE Corporation |
SP-230881
| approved | SA#101 | SA WG3 | 17.9.0 | AKMA |
|
|
| 33.535 | 0161 | - | A | 18.0.0 | Rel-18 | Correction of step numbers in clause 6.2 of TS 33.535 |
S3-233680
| agreed | SA3#112 | ZTE Corporation |
SP-230881
| approved | SA#101 | SA WG3 | 18.1.0 | AKMA |
|
|
| 33.535 | 0160 | - | F | 17.8.0 | Rel-17 | Correction of step numbers in clause 6.2 of TS 33.535 |
S3-233679
| agreed | SA3#112 | ZTE Corporation |
SP-230881
| approved | SA#101 | SA WG3 | 17.9.0 | AKMA |
|
|
| 33.535 | 0159 | - | A | 18.0.0 | Rel-18 | AKMA service restriction in VPLMN |
S3-233644
| not pursued | SA3#112 | Nokia, Nokia Sh... |
| | | | | AKMA |
|
|
| 33.535 | 0158 | - | F | 17.8.0 | Rel-17 | AKMA service restriction in VPLMN |
S3-233643
| not pursued | SA3#112 | Nokia, Nokia Sh... |
| | | | | AKMA |
|
|
| 33.535 | 0157 | - | A | 18.0.0 | Rel-18 | AKMA Service disable or withdrawn |
S3-233635
| not pursued | SA3#112 | Nokia, Nokia Sh... |
| | | | | AKMA |
|
|
| 33.535 | 0156 | - | F | 17.8.0 | Rel-17 | AKMA Service disable or withdrawn |
S3-233634
| not pursued | SA3#112 | Nokia, Nokia Sh... |
| | | | | AKMA |
|
|
| 33.535 | 0153 | - | F | 17.8.0 | Rel-17 | Clarification on the description about AAnF |
S3-232870
| not pursued | SA3#111 | China Telecommu... |
| | | | | AKMA |
|
|
| 33.535 | 0152 | - | F | 17.8.0 | Rel-18 | AKMA Service disable or withdrawn |
S3-232531
| withdrawn | SA3#111 | Nokia, Nokia Sh... |
| | | | | AKMA |
|
|
| 33.535 | 0151 | 1 | F | 17.7.0 | Rel-17 | KAF lifetime and Ua* protocol recommendations |
S3-231421
| agreed | SA3#110 | Ericsson |
SP-230147
| approved | SA#99 | SA WG3 | 17.8.0 | AKMA |
|
|
| 33.535 | 0151 | - | F | 17.7.0 | Rel-17 | KAF lifetime and Ua* protocol recommendations |
S3-231284
| revised | SA3#110 | Ericsson |
| | | | | AKMA |
|
|
| 33.535 | 0148 | 1 | F | 17.7.0 | Rel-17 | AAnF sending GPSI to internal AKMA AF |
S3-231422
| agreed | SA3#110 | China Mobile |
SP-230147
| approved | SA#99 | SA WG3 | 17.8.0 | AKMA |
|
|
| 33.535 | 0148 | - | F | 17.7.0 | Rel-17 | AAnF sending GPSI to internal AKMA AF |
S3-231087
| revised | SA3#110 | China Mobile |
| | | | | AKMA |
|
|
| 33.535 | 0147 | - | F | 17.7.0 | Rel-17 | Clarification on NEF’s authorization to AF |
S3-231048
| agreed | SA3#110 | Huawei, HiSilicon |
SP-230147
| approved | SA#99 | SA WG3 | 17.8.0 | AKMA |
|
|
| 33.535 | 0146 | - | F | 17.7.0 | Rel-17 | Change NF to AAnF Service Consumer in 6.6 and 6.7 |
S3-230892
| not pursued | SA3#110 | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0145 | - | F | 17.7.0 | Rel-17 | Add Context_Remove into table 7.1.1-1 |
S3-230891
| not pursued | SA3#110 | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0144 | - | F | 17.7.0 | Rel-17 | KAF lifetime recommendations and Ua* protocol requirements |
S3-223831
| not pursued | SA3#109 | Ericsson |
| | | | | AKMA |
|
|
| 33.535 | 0143 | - | F | 17.7.0 | Rel-17 | AAnF sending GPSI to internal AKMA AF |
S3-223711
| not pursued | SA3#109 | China Mobile (S... |
| | | | | AKMA |
|
|
| 33.535 | 0142 | - | F | 17.7.0 | Rel-17 | Add one note about AKMA subscription data and AKMA context asynchronization in clause 6.6.1 |
S3-223426
| not pursued | SA3#109 | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0141 | - | F | 17.7.0 | Rel-17 | Add MnF in clause 6.6.1and 6.7 |
S3-223425
| not pursued | SA3#109 | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0140 | - | F | 17.7.0 | Rel-17 | Add Context_Remove into table 7.1.1-1 |
S3-223424
| not pursued | SA3#109 | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0139 | - | F | 17.7.0 | Rel-17 | AKMA API enhancement based on the LS |
S3-223266
| not pursued | SA3#109 | Nokia, Nokia Sh... |
| | | | | AKMA |
|
|
| 33.535 | 0138 | - | F | 17.6.0 | Rel-17 | AAnF sending GPSI to internal AKMA AF |
S3-222143
| not pursued | SA3#108-e | China Mobile |
| | | | | AKMA |
|
|
| 33.535 | 0137 | - | F | 17.6.0 | Rel-17 | Clarifications to TS 33.535 |
S3-222058
| agreed | SA3#108-e | Huawei, HiSilicon |
SP-220883
| approved | SA#97-e | SA WG3 | 17.7.0 | AKMA |
|
|
| 33.535 | 0135 | - | F | 17.6.0 | Rel-17 | AKMA application context removal |
S3-221885
| not pursued | SA3#108-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0134 | - | F | 17.6.0 | Rel-17 | Add UDM or OAM in clause 6.6.1and 6.7 |
S3-221884
| not pursued | SA3#108-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0133 | - | F | 17.6.0 | Rel-17 | Add Context_Remove into table 7.1.1-1. |
S3-221883
| not pursued | SA3#108-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0132 | 1 | F | 17.6.0 | Rel-17 | Add ApplicationKey_ AnonUser_Get into table 7.1.1-1 |
S3-222368
| agreed | SA3#108-e | ZTE Corporation |
SP-220883
| approved | SA#97-e | SA WG3 | 17.7.0 | AKMA |
|
|
| 33.535 | 0132 | - | F | 17.6.0 | Rel-17 | Add ApplicationKey_ AnonUser_Get into table 7.1.1-1 |
S3-221882
| revised | SA3#108-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0130 | - | F | 17.5.0 | Rel-17 | AAnF sending GPSI to internal AKMA AF |
S3-220807
| not pursued | SA3#107-e | China Mobile |
| | | | | AKMA |
|
|
| 33.535 | 0129 | 1 | F | 17.5.0 | Rel-17 | Clarification on the description about AAnF |
S3-221203
| agreed | SA3#107-e | China Telecom C... |
SP-220545
| approved | SA#96 | SA WG3 | 17.6.0 | AKMA |
|
|
| 33.535 | 0129 | - | F | 17.5.0 | Rel-17 | Clarification on the description about AAnF |
S3-220770
| revised | SA3#107-e | China Telecom C... |
| | | | | AKMA |
|
|
| 33.535 | 0128 | 1 | F | 17.5.0 | Rel-17 | NF selects AAnF in clause 6.7 |
S3-221228
| agreed | SA3#107-e | ZTE Corporation |
SP-220545
| approved | SA#96 | SA WG3 | 17.6.0 | AKMA |
|
|
| 33.535 | 0128 | - | F | 17.5.0 | Rel-17 | NF selects AAnF in clause 6.7 |
S3-220753
| revised | SA3#107-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0127 | 1 | F | 17.5.0 | Rel-17 | Correct AAnF service in clause 6.3 |
S3-221227
| agreed | SA3#107-e | ZTE Corporation |
SP-220545
| approved | SA#96 | SA WG3 | 17.6.0 | AKMA |
|
|
| 33.535 | 0127 | - | F | 17.5.0 | Rel-17 | Correct AAnF service in clause 6.3 |
S3-220752
| revised | SA3#107-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0125 | - | F | 17.5.0 | Rel-17 | Aligning text for AKMA procedure |
S3-220693
| agreed | SA3#107-e | Nokia, Nokia Sh... |
SP-220545
| approved | SA#96 | SA WG3 | 17.6.0 | AKMA |
|
|
| 33.535 | 0123 | - | D | 17.4.0 | Rel-17 | Clean up for TS 33.535 |
S3-220304
| agreed | SA3#106-e | LG Electronics ... |
SP-220207
| approved | SA#95-e | SA WG3 | 17.5.0 | AKMA |
|
|
| 33.535 | 0122 | 1 | B | 17.4.0 | Rel-17 | Clarification on indication to UE when KAF is expired |
S3-220522
| agreed | SA3#106-e | LG Electronics ... |
SP-220207
| approved | SA#95-e | SA WG3 | 17.5.0 | AKMA |
|
|
| 33.535 | 0122 | - | B | 17.4.0 | Rel-17 | Clarification on indication to UE when KAF is expired |
S3-220301
| revised | SA3#106-e | LG Electronics ... |
| | | | | AKMA |
|
|
| 33.535 | 0121 | 1 | B | 17.4.0 | Rel-17 | New AAnF application key get service without SUPI |
S3-220569
| agreed | SA3#106-e | Samsung, Verizon |
SP-220207
| approved | SA#95-e | SA WG3 | 17.5.0 | AKMA |
|
|
| 33.535 | 0121 | - | B | 17.4.0 | Rel-17 | New AAnF application key get service without SUPI |
S3-220286
| revised | SA3#106-e | Samsung, Verizon |
| | | | | AKMA |
|
|
| 33.535 | 0120 | - | B | 17.4.0 | Rel-17 | Clarification on AKMA Application key retrieval |
S3-220285
| not pursued | SA3#106-e | Samsung, ZTE |
| | | | | AKMA |
|
|
| 33.535 | 0118 | - | F | 17.4.0 | Rel-17 | Clarification on UDM manage AKMA subscription data in 4.2.5 |
S3-220090
| not pursued | SA3#106-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0117 | - | F | 17.4.0 | Rel-17 | Clarification on the NF consumer in 6.6.1 |
S3-220089
| not pursued | SA3#106-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0116 | - | F | 17.4.0 | Rel-17 | Add function description about AAnF in 4.2.1 |
S3-220088
| agreed | SA3#106-e | ZTE Corporation |
SP-220207
| approved | SA#95-e | SA WG3 | 17.5.0 | AKMA |
|
|
| 33.535 | 0115 | 1 | F | 17.4.0 | Rel-17 | Add a Note about the Kaf refresh |
S3-220556
| agreed | SA3#106-e | ZTE Corporation |
SP-220207
| approved | SA#95-e | SA WG3 | 17.5.0 | AKMA |
|
|
| 33.535 | 0115 | - | F | 17.4.0 | Rel-17 | Add a Note about the Kaf refresh |
S3-220087
| revised | SA3#106-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0114 | - | B | 17.3.0 | Rel-17 | CR to 33.535: AKMA service support for roaming UE |
S3-214236
| not pursued | SA3#105-e | Samsung |
| | | | | AKMA |
|
|
| 33.535 | 0113 | - | B | 17.3.0 | Rel-17 | CR to 33.535: Clarification on AKMA Application Key retrieval |
S3-214234
| not pursued | SA3#105-e | Samsung |
| | | | | AKMA |
|
|
| 33.535 | 0112 | - | B | 17.3.0 | Rel-17 | CR to 33.535: Refresh of KAKMA and KAF |
S3-214233
| not pursued | SA3#105-e | Samsung, NEC |
| | | | | AKMA |
|
|
| 33.535 | 0111 | - | B | 17.3.0 | Rel-17 | AKMA roaming |
S3-214091
| not pursued | SA3#105-e | Lenovo, Motorol... |
| | | | | AKMA |
|
|
| 33.535 | 0110 | - | F | 17.3.0 | Rel-17 | Correction to Deriving AKMA Application Key for a specific AF |
S3-214039
| not pursued | SA3#105-e | Huawei,HiSilicon |
| | | | | AKMA |
|
|
| 33.535 | 0109 | - | F | 17.3.0 | Rel-17 | UE stores AKMA subscription data |
S3-213942
| not pursued | SA3#105-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0108 | - | F | 17.3.0 | Rel-17 | Sending UE ID to the AKMA AF |
S3-213941
| agreed | SA3#105-e | ZTE Corporation |
SP-211373
| approved | SA#94-e | SA WG3 | 17.4.0 | AKMA |
|
|
| 33.535 | 0107 | - | F | 17.3.0 | Rel-17 | No AKMA security context in AAnF |
S3-213940
| not pursued | SA3#105-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0106 | - | F | 17.3.0 | Rel-17 | Kaf is invalid in AF |
S3-213939
| not pursued | SA3#105-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0105 | - | F | 17.3.0 | Rel-17 | Kaf expiration |
S3-213938
| not pursued | SA3#105-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0104 | 1 | F | 17.3.0 | Rel-17 | Clean up for clause 6.6.1 |
S3-214490
| agreed | SA3#105-e | ZTE Corporation |
SP-211373
| approved | SA#94-e | SA WG3 | 17.4.0 | AKMA |
|
|
| 33.535 | 0104 | - | F | 17.3.0 | Rel-17 | Clean up for clause 6.6.1 |
S3-213936
| revised | SA3#105-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0102 | - | F | 17.3.0 | Rel-17 | Kaf refresh when lifetime expires |
S3-213899
| not pursued | SA3#105-e | Futurewei Techn... |
| | | | | AKMA |
|
|
| 33.535 | 0101 | - | F | 17.3.0 | Rel-17 | Clarification on Kaf lifetime in Clause 5.2 |
S3-213898
| agreed | SA3#105-e | Futurewei Techn... |
SP-211373
| approved | SA#94-e | SA WG3 | 17.4.0 | AKMA |
|
|
| 33.535 | 0100 | - | B | 17.2.0 | Rel-17 | [CR] Refresh of KAF and KAKMA |
S3-212902
| not pursued | SA3#104-e | Samsung |
| | | | | AKMA |
|
|
| 33.535 | 0097 | - | B | 17.2.1 | Rel-17 | KAF refresh |
S3-212825
| not pursued | SA3#104-e | China Mobile |
| | | | | AKMA |
|
|
| 33.535 | 0096 | - | F | 17.2.1 | Rel-17 | Deleting the NOTE of roaming |
S3-212822
| not pursued | SA3#104-e | China Mobile |
| | | | | AKMA |
|
|
| 33.535 | 0095 | - | B | 17.2.1 | Rel-17 | Add a new procedure to enable the AF to refresh the Kaf |
S3-212633
| not pursued | SA3#104-e | Huawei, HiSilicon |
| | | | | AKMA |
|
|
| 33.535 | 0094 | - | F | 17.2.1 | Rel-17 | Correction to Deriving AKMA Application Key for a specific AF |
S3-212624
| not pursued | SA3#104-e | Huawei,HiSilicon |
| | | | | AKMA |
|
|
| 33.535 | 0093 | 1 | F | 17.2.1 | Rel-17 | Clarification on AAnF selection |
S3-213252
| agreed | SA3#104-e | Huawei, HiSilicon |
SP-210842
| approved | SA#93-e | SA WG3 | 17.3.0 | AKMA |
|
|
| 33.535 | 0093 | - | F | 17.2.1 | Rel-17 | Clarification on AAnF selection |
S3-212600
| revised | SA3#104-e | Huawei, HiSilicon |
| | | | | AKMA |
|
|
| 33.535 | 0089 | - | F | 17.2.1 | Rel-17 | Update clause 6.1 refer to Kausf stored in AUSF |
S3-212533
| not pursued | SA3#104-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0088 | - | F | 17.2.1 | Rel-17 | Update clause 6.1 about RID |
S3-212532
| agreed | SA3#104-e | ZTE Corporation |
SP-210842
| approved | SA#93-e | SA WG3 | 17.3.0 | AKMA |
|
|
| 33.535 | 0087 | - | F | 17.2.1 | Rel-17 | UDM notifies AAnF AKMA context removal and performs AAnF selection |
S3-212531
| not pursued | SA3#104-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0086 | - | F | 17.2.1 | Rel-17 | Resolve the Kaf update issue |
S3-212530
| not pursued | SA3#104-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0085 | - | F | 17.2.1 | Rel-17 | Resolution of EN on other parameter in clause 6.3 |
S3-212529
| not pursued | SA3#104-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0083 | - | B | 17.1.0 | Rel-17 | Network provides authorization to AF for Kaf key refresh |
S3-212076
| not pursued | SA3#103-e | Samsung |
| | | | | AKMA |
|
|
| 33.535 | 0082 | - | B | 17.1.0 | Rel-17 | Refresh of Kaf and Kakma |
S3-212074
| not pursued | SA3#103-e | Samsung |
| | | | | AKMA |
|
|
| 33.535 | 0081 | 1 | F | 17.1.0 | Rel-17 | AKMA UE aspects |
S3-212328
| agreed | SA3#103-e | Ericsson |
SP-210436
| approved | SA#92-e | SA WG3 | 17.2.0 | AKMA |
|
|
| 33.535 | 0081 | - | F | 17.1.0 | Rel-17 | AKMA UE aspects |
S3-211913
| revised | SA3#103-e | Ericsson |
| | | | | AKMA |
|
|
| 33.535 | 0079 | 1 | F | 17.1.0 | Rel-17 | AKMA Anchor Function selection clause |
S3-212359
| agreed | SA3#103-e | Ericsson |
SP-210436
| approved | SA#92-e | SA WG3 | 17.2.0 | AKMA |
|
|
| 33.535 | 0079 | - | F | 17.1.0 | Rel-17 | AKMA Anchor Function selection clause |
S3-211908
| revised | SA3#103-e | Ericsson |
| | | | | AKMA |
|
|
| 33.535 | 0078 | 1 | F | 17.2.1 | Rel-17 | Sending UE identifier to the AKMA AF |
S3-212869
| not pursued | SA3#104-e | Qualcomm Incorp... |
| | | | | AKMA |
|
|
| 33.535 | 0078 | - | F | 17.1.0 | Rel-17 | Sending UE identifier to the AKMA AF |
S3-211817
| revised | SA3#103-e | Qualcomm Incorp... |
| | | | | AKMA |
|
|
| 33.535 | 0077 | - | F | 17.1.0 | Rel-17 | Editoral change in clause 6.1 |
S3-211672
| agreed | SA3#103-e | Huawei, HiSilicon |
SP-210436
| approved | SA#92-e | SA WG3 | 17.2.0 | AKMA |
|
|
| 33.535 | 0076 | 1 | F | 17.1.0 | Rel-17 | Clarification on AAnF Selection |
S3-212313
| agreed | SA3#103-e | Huawei, HiSilicon |
SP-210436
| approved | SA#92-e | SA WG3 | 17.2.0 | AKMA |
|
|
| 33.535 | 0076 | - | F | 17.1.0 | Rel-17 | Clarification on AAnF Selection |
S3-211671
| revised | SA3#103-e | Huawei, HiSilicon |
| | | | | AKMA |
|
|
| 33.535 | 0075 | 1 | F | 17.1.0 | Rel-17 | Add an abbreviation to AKMA |
S3-212320
| agreed | SA3#103-e | ZTE Corporation |
SP-210436
| approved | SA#92-e | SA WG3 | 17.2.0 | AKMA |
|
|
| 33.535 | 0075 | - | F | 17.1.0 | Rel-17 | Add an abbreviation to AKMA |
S3-211585
| revised | SA3#103-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0074 | - | F | 17.1.0 | Rel-17 | Handle the failure cause by UE |
S3-211575
| not pursued | SA3#103-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0073 | - | F | 17.1.0 | Rel-17 | Update clause 6.1 refer to Kausf stored in AUSF |
S3-211552
| not pursued | SA3#103-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0072 | 1 | B | 17.1.0 | Rel-17 | UDM notifies AAnF AKMA context removal |
S3-212319
| agreed | SA3#103-e | ZTE Corporation |
SP-210436
| approved | SA#92-e | SA WG3 | 17.2.0 | AKMA |
|
|
| 33.535 | 0072 | - | B | 17.1.0 | Rel-17 | UDM notifies AAnF AKMA context removal |
S3-211551
| revised | SA3#103-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0071 | - | F | 17.1.0 | Rel-17 | Resolution of EN on other parameter in clause 6.3 |
S3-211550
| not pursued | SA3#103-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0070 | - | F | 17.1.0 | Rel-17 | Clarification on how the AUSF get RID |
S3-211548
| not pursued | SA3#103-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0069 | - | F | 17.1.0 | Rel-17 | Clarification on how AUSF select AAnF |
S3-211547
| merged | SA3#103-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0068 | - | F | 17.1.0 | Rel-17 | Clarification on how AF select AAnF |
S3-211546
| merged | SA3#103-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0067 | - | B | 17.0.0 | Rel-17 | UE Sending GPSI (if available) to the AF |
S3-210496
| not pursued | SA3#102-e | Samsung |
| | | | | AKMA |
|
|
| 33.535 | 0065 | - | F | 17.0.0 | Rel-17 | Network provides authorization to AF/UE for KAF key refresh |
S3-210447
| not pursued | SA3#102-e | Samsung |
| | | | | AKMA |
|
|
| 33.535 | 0063 | - | F | 17.0.0 | Rel-17 | Clarification on AAnF Selection |
S3-210254
| not pursued | SA3#102-e | Huawei, HiSilicon |
| | | | | AKMA |
|
|
| 33.535 | 0062 | 1 | F | 17.0.0 | Rel-17 | Clarification on A-KID generation |
S3-210739
| agreed | SA3#102-e | Huawei, HiSilicon |
SP-210118
| approved | SA#91-e | SA WG3 | 17.1.0 | AKMA |
|
|
| 33.535 | 0062 | - | F | 17.0.0 | Rel-17 | Clarification on A-KID generation |
S3-210253
| revised | SA3#102-e | Huawei, HiSilicon |
| | | | | AKMA |
|
|
| 33.535 | 0061 | - | B | 17.0.0 | Rel-17 | UDM notifies AAnF AKMA context removal |
S3-210158
| not pursued | SA3#102-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0060 | 1 | F | 17.0.0 | Rel-17 | the KAF lifetime expiration in clause 5.2 |
S3-210763
| agreed | SA3#102-e | ZTE Corporation |
SP-210118
| approved | SA#91-e | SA WG3 | 17.1.0 | AKMA |
|
|
| 33.535 | 0060 | - | F | 17.0.0 | Rel-17 | the KAF lifetime expiration in clause 5.2 |
S3-210156
| revised | SA3#102-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0059 | - | F | 17.0.0 | Rel-17 | Resolution of EN on other parameter in clause 6.3 |
S3-210155
| not pursued | SA3#102-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0058 | - | F | 17.0.0 | Rel-17 | Kakma invalid and Kausf invalid in clause 6.2 |
S3-210154
| not pursued | SA3#102-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0057 | 1 | B | 17.0.0 | Rel-17 | Add Application Key Get service in clause 7.1 |
S3-210762
| agreed | SA3#102-e | ZTE Corporation |
SP-210118
| approved | SA#91-e | SA WG3 | 17.1.0 | AKMA |
|
|
| 33.535 | 0057 | - | B | 17.0.0 | Rel-17 | Add Application Key Get service in clause 7.1 |
S3-210153
| revised | SA3#102-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0056 | 1 | B | 17.0.0 | Rel-17 | AAnF selection in AF |
S3-210761
| agreed | SA3#102-e | ZTE Corporation |
SP-210118
| approved | SA#91-e | SA WG3 | 17.1.0 | AKMA |
|
|
| 33.535 | 0056 | - | B | 17.0.0 | Rel-17 | AAnF selection in AF |
S3-210152
| revised | SA3#102-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0055 | 1 | B | 17.0.0 | Rel-17 | AAnF checks AKMA service for UE and AF in clause 6.3 |
S3-210760
| agreed | SA3#102-e | ZTE Corporation |
SP-210118
| approved | SA#91-e | SA WG3 | 17.1.0 | AKMA |
|
|
| 33.535 | 0055 | - | B | 17.0.0 | Rel-17 | AAnF checks AKMA service for UE and AF in clause 6.3 |
S3-210151
| revised | SA3#102-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0054 | - | F | 16.1.0 | Rel-16 | AKMA Anchor Function selection clause |
S3-203213
| not pursued | SA3#101-e | Ericsson |
| | | | | AKMA |
|
|
| 33.535 | 0053 | 1 | F | 16.1.0 | Rel-16 | Update of the reference point interface names of AKMA |
S3-203493
| agreed | SA3#101-e | Ericsson |
SP-201006
| approved | SA#90-e | SA WG3 | 16.2.0 | AKMA |
|
|
| 33.535 | 0053 | - | F | 16.1.0 | Rel-16 | Update of the reference point interface names of AKMA |
S3-203211
| revised | SA3#101-e | Ericsson |
| | | | | AKMA |
|
|
| 33.535 | 0052 | 1 | F | 17.0.0 | Rel-17 | Sending UE identifier to the AKMA AF |
S3-210489
| not pursued | SA3#102-e | Qualcomm Incorp... |
| | | | | AKMA |
|
|
| 33.535 | 0052 | - | F | 16.1.0 | Rel-16 | Sending UE identifier to the AKMA AF |
S3-203191
| revised | SA3#101-e | Qualcomm Incorp... |
| | | | | AKMA |
|
|
| 33.535 | 0051 | 1 | F | 16.1.0 | Rel-17 | AKMA: Adding missing service definition |
S3-203518
| withdrawn | SA3#101-e | Huawei, Hisilicon |
| | | | | AKMA |
|
|
| 33.535 | 0051 | - | F | 16.1.0 | Rel-16 | AKMA: Adding missing service definition |
S3-203037
| revised | SA3#101-e | Huawei, Hisilicon |
| | | | | AKMA |
|
|
| 33.535 | 0050 | - | B | 16.1.0 | Rel-16 | Storage of the AKMA keys in the UE |
S3-203029
| not pursued | SA3#101-e | THALES |
| | | | | AKMA |
|
|
| 33.535 | 0049 | - | F | 16.1.0 | Rel-17 | Aware of AF‘s AKMA service capability in the UE |
S3-203025
| not pursued | SA3#101-e | Huawei, HiSilicon |
| | | | | AKMA |
|
|
| 33.535 | 0048 | - | F | 16.1.0 | Rel-17 | Adding AAnF selection |
S3-202967
| not pursued | SA3#101-e | Huawei, Hisilicon |
| | | | | AKMA |
|
|
| 33.535 | 0047 | 1 | F | 16.1.0 | Rel-16 | Adding details of AKMA key generation in the UE |
S3-203482
| agreed | SA3#101-e | Huawei, Hisilicon |
SP-201006
| approved | SA#90-e | SA WG3 | 16.2.0 | AKMA |
|
|
| 33.535 | 0047 | - | F | 16.1.0 | Rel-16 | Adding details of AKMA key generation in the UE |
S3-202963
| revised | SA3#101-e | Huawei, Hisilicon |
| | | | | AKMA |
|
|
| 33.535 | 0046 | - | F | 16.1.0 | Rel-16 | Editorial modifications of AKMA |
S3-202945
| agreed | SA3#101-e | CATT |
SP-201006
| approved | SA#90-e | SA WG3 | 16.2.0 | AKMA |
|
|
| 33.535 | 0045 | 1 | F | 16.1.0 | Rel-16 | Corrections of clause 6.1 |
S3-203535
| agreed | SA3#101-e | CATT |
SP-201006
| approved | SA#90-e | SA WG3 | 16.2.0 | AKMA |
|
|
| 33.535 | 0045 | - | F | 16.1.0 | Rel-16 | Corrections of clause 6.1 |
S3-202944
| revised | SA3#101-e | CATT |
| | | | | AKMA |
|
|
| 33.535 | 0044 | - | B | 16.1.0 | Rel-16 | UDM notifies AAnF AKMA context removal |
S3-202910
| not pursued | SA3#101-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0043 | - | F | 16.1.0 | Rel-16 | the lifetime of KAF expiration |
S3-202909
| agreed | SA3#101-e | ZTE Corporation |
SP-201006
| approved | SA#90-e | SA WG3 | 16.2.0 | AKMA |
|
|
| 33.535 | 0042 | - | F | 16.1.0 | Rel-16 | Rewording Kaf refresh |
S3-202908
| not pursued | SA3#101-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0041 | - | F | 16.1.0 | Rel-16 | Resolution of editor's note on other parameter in clause 6.3 |
S3-202907
| not pursued | SA3#101-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0040 | - | F | 16.1.0 | Rel-16 | Kausf storing in AUSF |
S3-202906
| merged | SA3#101-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0039 | - | F | 16.1.0 | Rel-16 | Kakma and A-KID refresh in clause 6.1 |
S3-202905
| merged | SA3#101-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0038 | - | F | 16.1.0 | Rel-16 | AKMA key lifetime expiration in clause 5.2 |
S3-202904
| not pursued | SA3#101-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0037 | - | F | 16.1.0 | Rel-16 | AAnF selection by AF |
S3-202903
| not pursued | SA3#101-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0036 | - | F | 16.1.0 | Rel-16 | A new A-KID derivation after a new primary authentication |
S3-202902
| not pursued | SA3#101-e | ZTE Corporation |
| | | | | AKMA |
|
|
| 33.535 | 0035 | - | F | 16.1.0 | Rel-16 | Clarification of RID in clause 6.1 for AKMA |
S3-202901
| not pursued | SA3#101-e | ZTE Corporation |
| | | | | AKMA |
|