|
| 33.503 | 0210 | - | F | 18.4.0 | Rel-18 | Support cleartext HPLMN ID in PC5 U2U relay discovery |
S3-245127
| | SA3#119 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0209 | - | A | 18.4.0 | Rel-18 | Update to TS 33.503 to fix the referred clause and table of services - Mirror |
S3-244880
| | SA3#119 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0208 | - | F | 17.9.0 | Rel-17 | Update to TS 33.503 to fix the referred clause and table of services |
S3-244879
| | SA3#119 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0207 | - | F | 18.3.0 | Rel-18 | Emergency Service over UE-to-Network relay - PEI status check |
S3-243383
| not pursued | SA3#117 | Philips Interna... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0206 | - | F | 18.3.0 | Rel-18 | Emergency Service over UE-to-Network relay - PEI status check |
S3-243350
| withdrawn | SA3#117 | Philips Interna... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0205 | - | A | 18.3.0 | Rel-18 | Add clarification on encryption operation for PC5 ProSe discovery |
S3-242877
| agreed | SA3#117 | Nokia, Nokia Sh... |
SP-241100
| approved | SA#105 | SA WG3 | 18.4.0 | 5G_ProSe |
|
|
| 33.503 | 0204 | - | F | 17.8.0 | Rel-17 | Add clarification on encryption operation for PC5 ProSe discovery |
S3-242876
| agreed | SA3#117 | Nokia, Nokia Sh... |
SP-241100
| approved | SA#105 | SA WG3 | 17.9.0 | 5G_ProSe |
|
|
| 33.503 | 0203 | 1 | A | 18.2.0 | Rel-18 | Support cleartext HPLMN ID in PC5 U2N relay discovery |
| | | |
SP-240940
| approved | SA#104 | Nokia, Nokia Sh... | 18.3.0 | 5G_ProSe |
|
|
| 33.503 | 0203 | - | A | 18.2.0 | Rel-18 | Support cleartext HPLMN ID in PC5 U2N relay discovery |
| | | |
SP-240717
| revised | SA#104 | Nokia, Nokia Sh... | | 5G_ProSe |
|
|
| 33.503 | 0202 | 1 | F | 17.7.0 | Rel-17 | Support cleartext HPLMN ID in PC5 U2N relay discovery |
| | | |
SP-240939
| approved | SA#104 | Nokia, Nokia Sh... | 17.8.0 | 5G_ProSe |
|
|
| 33.503 | 0202 | - | F | 17.7.0 | Rel-17 | Support cleartext HPLMN ID in PC5 U2N relay discovery |
| | | |
SP-240716
| revised | SA#104 | Nokia, Nokia Sh... | | 5G_ProSe |
|
|
| 33.503 | 0201 | 1 | A | 18.2.0 | Rel-18 | Add clarification on encryption operation for PC5 ProSe discovery |
S3-242411
| agreed | SA3#116 | Nokia, Nokia Sh... |
SP-240667
| approved | SA#104 | SA WG3 | 18.3.0 | 5G_ProSe |
|
|
| 33.503 | 0201 | - | A | 18.2.0 | Rel-18 | Add clarification on encryption operation for PC5 ProSe discovery |
S3-242354
| revised | SA3#116 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0200 | - | A | 18.2.0 | Rel-18 | Fix issue of scrambling operation for PC5 ProSe discovery |
S3-242353
| not pursued | SA3#116 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0199 | - | F | 17.7.0 | Rel-17 | Fix issue of scrambling operation for PC5 ProSe discovery |
S3-242352
| not pursued | SA3#116 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0198 | - | A | 18.2.0 | Rel-18 | Support cleartext HPLMN ID in PC5 U2N relay discovery |
S3-242350
| merged | SA3#116 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0197 | - | F | 17.7.0 | Rel-17 | Support cleartext HPLMN ID in PC5 U2N relay discovery |
S3-242349
| merged | SA3#116 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0196 | 1 | F | 17.7.0 | Rel-17 | Add clarification on encryption operation for PC5 ProSe discovery |
S3-242410
| agreed | SA3#116 | Nokia, Nokia Sh... |
SP-240667
| approved | SA#104 | SA WG3 | 17.8.0 | 5G_ProSe |
|
|
| 33.503 | 0196 | - | F | 17.7.0 | Rel-17 | Add clarification on encryption operation for PC5 ProSe discovery |
S3-242345
| revised | SA3#116 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0195 | - | A | 18.2.0 | Rel-18 | Add clarification on scrambling operation for PC5 ProSe discovery |
S3-242344
| withdrawn | SA3#116 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0194 | - | F | 17.7.0 | Rel-17 | Add clarification on scrambling operation for PC5 ProSe discovery |
S3-242343
| withdrawn | SA3#116 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0193 | - | A | 18.2.0 | Rel-18 | Fix issue of scrambling operation for PC5 ProSe discovery |
S3-242342
| withdrawn | SA3#116 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0192 | - | F | 17.7.0 | Rel-17 | Fix issue of scrambling operation for PC5 ProSe discovery |
S3-242341
| withdrawn | SA3#116 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0191 | 1 | A | 18.2.0 | Rel-18 | Excluding scrambling protection of HPLMN ID and clarifications in discovery message – R18 |
S3-242406
| withdrawn | SA3#116 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0191 | - | A | 18.2.0 | Rel-18 | Excluding scrambling protection of HPLMN ID and clarifications in discovery message – R18 |
S3-242337
| not pursued | SA3#116 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0190 | - | A | 18.2.0 | Rel-18 | support cleartext HPLMN ID in PC5 U2N relay discovery |
S3-242335
| withdrawn | SA3#116 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0189 | - | F | 17.7.0 | Rel-17 | support cleartext HPLMN ID in PC5 U2N relay discovery |
S3-242334
| withdrawn | SA3#116 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0188 | 1 | F | 18.2.0 | Rel-18 | Security of 5G ProSe PC5 communication without network assistance - correction |
S3-242616
| agreed | SA3#116 | Philips Interna... |
SP-240666
| approved | SA#104 | SA WG3 | 18.3.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0188 | - | F | 18.2.0 | Rel-18 | Security of 5G ProSe PC5 communication without network assistance - correction |
S3-242247
| revised | SA3#116 | Philips Interna... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0187 | 1 | F | 18.2.0 | Rel-18 | Clause 6.3.6 in TS 33.503 - correction |
S3-242641
| agreed | SA3#116 | Philips Interna... |
SP-240666
| approved | SA#104 | SA WG3 | 18.3.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0187 | - | C | 18.2.0 | Rel-18 | Clause 6.3.6 in TS 33.503 - correction |
S3-242246
| revised | SA3#116 | Philips Interna... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0186 | - | C | 18.2.0 | Rel-18 | A.7 in TS 33.503 - correction |
S3-242245
| withdrawn | SA3#116 | Philips Interna... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0185 | - | F | 18.2.0 | Rel-18 | Direct Discovery Set scrambling protection - correction |
S3-242244
| merged | SA3#116 | Philips Interna... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0184 | - | A | 18.2.0 | Rel-18 | Rel18 ProSe – Update on U2N relay discovery procedure |
S3-242148
| merged | SA3#116 | Qualcomm Incorp... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0183 | - | F | 17.7.0 | Rel-17 | Rel17 ProSe – Update on U2N relay discovery procedure |
S3-242147
| merged | SA3#116 | Qualcomm Incorp... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0182 | 1 | F | 18.2.0 | Rel-18 | Correction on the scrambing mechanism for U2U relay discovery |
S3-242412
| agreed | SA3#116 | Xiaomi, Philips... |
SP-240666
| approved | SA#104 | SA WG3 | 18.3.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0182 | - | F | 18.2.0 | Rel-18 | Correction on the scrambing mechanism for U2U relay discovery |
S3-242127
| revised | SA3#116 | Beijing Xiaomi ... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0181 | - | A | 18.2.0 | Rel-18 | Correction on the protection mechanism for U2N relay discovery (R18) |
S3-242126
| merged | SA3#116 | Beijing Xiaomi ... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0180 | - | F | 17.7.0 | Rel-17 | Correction on the protection mechanism for U2N relay discovery (R17) |
S3-242125
| merged | SA3#116 | Beijing Xiaomi ... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0179 | 1 | F | 18.2.0 | Rel-18 | CR to TS33.503 Update U2U Relay Discovery procedures for aligning with CT1 |
S3-242403
| agreed | SA3#116 | CATT |
SP-240666
| approved | SA#104 | SA WG3 | 18.3.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0179 | - | F | 18.2.0 | Rel-18 | CR to TS33.503 Update U2U Relay Discovery procedures for aligning with CT1 |
S3-242104
| revised | SA3#116 | CATT |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0178 | 1 | F | 18.2.0 | Rel-18 | Clarification related to U2U discovery model B |
S3-242409
| agreed | SA3#116 | China Telecom, ... |
SP-240666
| approved | SA#104 | SA WG3 | 18.3.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0178 | - | F | 18.2.0 | Rel-18 | Clarification related to U2U discovery model B |
S3-242067
| revised | SA3#116 | China Telecom C... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0177 | - | F | 17.7.0 | Rel-17 | Clarification of direct discovery in r17(mirror) |
S3-242062
| agreed | SA3#116 | China Telecom C... |
SP-240667
| approved | SA#104 | SA WG3 | 17.8.0 | 5G_ProSe |
|
|
| 33.503 | 0176 | - | A | 18.2.0 | Rel-18 | Clarification of direct discovery in r18 |
S3-242060
| agreed | SA3#116 | China Telecom C... |
SP-240667
| approved | SA#104 | SA WG3 | 18.3.0 | 5G_ProSe |
|
|
| 33.503 | 0175 | - | A | 18.2.0 | Rel-18 | Excluding scrambling protection of HPLMN ID and clarifications in discovery message – R18 mirror |
S3-242004
| withdrawn | SA3#116 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0174 | 1 | F | 17.7.0 | Rel-17 | Excluding scrambling protection of HPLMN ID and clarifications in discovery message – R17 |
S3-242405
| withdrawn | SA3#116 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0174 | - | F | 17.7.0 | Rel-17 | Excluding scrambling protection of HPLMN ID and clarifications in discovery message – R17 |
S3-242003
| not pursued | SA3#116 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0173 | 1 | A | 18.2.0 | Rel-18 | Adding the usage of the PLMN IDs from Remote UE – R18 mirror |
S3-242408
| withdrawn | SA3#116 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0173 | - | A | 18.2.0 | Rel-18 | Adding the usage of the PLMN IDs from Remote UE – R18 mirror |
S3-241998
| not pursued | SA3#116 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0172 | 1 | F | 17.7.0 | Rel-17 | Add the usage of the PLMN IDs from Remote UE – R17 |
S3-242407
| withdrawn | SA3#116 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0172 | - | F | 17.7.0 | Rel-17 | Add the usage of the PLMN IDs from Remote UE – R17 |
S3-241997
| not pursued | SA3#116 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0171 | - | F | 18.2.0 | Rel-18 | Alignment with CT1 and editorial changes to U2U discovery |
S3-241995
| merged | SA3#116 | Huawei, HiSilicon |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0170 | - | F | 18.1.0 | Rel-18 | Clarification on the collection of direct discovery set in the 5G ProSe UE-to-UE Relay Discovery with Model A |
S3-240779
| merged | SA3#115 | Xiaomi |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0169 | - | F | 18.1.0 | Rel-18 | Rel18 ProSe – Update on security of PC5 communication for U2U Relay without network assistance |
S3-240733
| agreed | SA3#115 | Qualcomm Incorp... |
SP-240341
| approved | SA#103 | SA WG3 | 18.2.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0168 | 1 | F | 18.1.0 | Rel-18 | Rel18 ProSe – Clarification on direct discovery set protection in U2U relay discovery with model A |
S3-240994
| agreed | SA3#115 | Qualcomm Incorp... |
SP-240341
| approved | SA#103 | SA WG3 | 18.2.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0168 | - | F | 18.1.0 | Rel-18 | Rel18 ProSe – Clarification on direct discovery set protection in U2U relay discovery with model A |
S3-240732
| revised | SA3#115 | Qualcomm Incorp... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0167 | - | A | 18.1.0 | Rel-18 | Update discovery key response of U2N discovery security procdure |
S3-240611
| merged | SA3#115 | Nokia, Nokia Sh... |
| | | | | TEI18 |
|
|
| 33.503 | 0166 | - | F | 17.6.0 | Rel-17 | Update discovery key response of U2N discovery security procdure |
S3-240610
| merged | SA3#115 | Nokia, Nokia Sh... |
| | | | | TEI17 |
|
|
| 33.503 | 0165 | - | F | 18.1.0 | Rel-18 | CR to TS33.503 Update U2U Relay Discovery procedure with Model B |
S3-240609
| not pursued | SA3#115 | CATT |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0164 | - | F | 18.1.0 | Rel-18 | CR to TS33.503 Update U2U Relay Discovery procedure with Model A |
S3-240607
| not pursued | SA3#115 | CATT |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0163 | 1 | A | 18.1.0 | Rel-18 | Update to the identification of U2NW discovery security materials |
S3-240863
| agreed | SA3#115 | Huawei, HiSilicon |
SP-240340
| approved | SA#103 | SA WG3 | 18.2.0 | 5G_ProSe |
|
|
| 33.503 | 0163 | - | A | 18.1.0 | Rel-18 | Update to the identification of U2NW discovery security materials |
S3-240511
| revised | SA3#115 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0162 | - | A | 18.1.0 | Rel-18 | Clarification on multiple relay discovery security materials |
S3-240510
| merged | SA3#115 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0161 | - | F | 17.6.0 | Rel-17 | Clarification on multiple relay discovery security materials |
S3-240509
| merged | SA3#115 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0160 | 1 | F | 17.6.0 | Rel-17 | Update to the identification of U2NW discovery security materials |
S3-240862
| agreed | SA3#115 | Huawei, HiSilicon |
SP-240340
| approved | SA#103 | SA WG3 | 17.7.0 | 5G_ProSe |
|
|
| 33.503 | 0160 | - | F | 17.6.0 | Rel-17 | Update to the identification of U2NW discovery security materials |
S3-240506
| revised | SA3#115 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0159 | 1 | F | 18.1.0 | Rel-18 | Remove circular reference in U2U Relay discovery Model A |
S3-240864
| agreed | SA3#115 | Interdigital |
SP-240341
| approved | SA#103 | SA WG3 | 18.2.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0159 | - | F | 18.1.0 | Rel-18 | Remove circular reference in U2U Relay discovery Model A |
S3-240388
| revised | SA3#115 | Interdigital |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0158 | - | B | 18.1.0 | Rel-18 | Clause 6.6.3.2 – Security procedures without network assitance check |
S3-240341
| not pursued | SA3#115 | Philips Interna... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0157 | 1 | B | 18.1.0 | Rel-18 | Clause 6.1.3.2.3 - Clarification related to the direct discovery set |
S3-241033
| agreed | SA3#115 | Philips Interna... |
SP-240341
| approved | SA#103 | SA WG3 | 18.2.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0157 | - | B | 18.1.0 | Rel-18 | Clause 6.1.3.2.3 - Clarification related to the direct discovery set |
S3-240340
| revised | SA3#115 | Philips Interna... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0156 | - | B | 18.1.0 | Rel-18 | 5G ProSe UE-to-UE relay communication security |
S3-240339
| not pursued | SA3#115 | Philips Interna... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0155 | - | A | 18.0.0 | Rel-18 | Clarification on the discovery security parameters in the U2N discovery (mirror) |
S3-234899
| not pursued | SA3#113 | Beijing Xiaomi ... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0154 | - | F | 17.5.0 | Rel-17 | Clarification on the discovery security parameters in the U2N discovery |
S3-234898
| merged | SA3#113 | Beijing Xiaomi ... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0153 | - | F | 18.0.0 | Rel-18 | Clarification on UE-to-UE Relay coverage status in the U2U discovery model B procedure |
S3-234897
| merged | SA3#113 | Beijing Xiaomi ... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0152 | - | F | 18.0.0 | Rel-18 | Clarification on protection on the direct discovery set in the U2U discovery |
S3-234896
| not pursued | SA3#113 | Beijing Xiaomi ... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0151 | - | F | 18.0.0 | Rel-18 | Add the general clause for UE-to-UE Relay Communication |
S3-234895
| merged | SA3#113 | Beijing Xiaomi ... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0150 | - | B | 18.0.0 | Rel-18 | 4.1.3 - Clause 6.1.3.3 - Clarification UE-to-UE Relay discovery key provisioning |
S3-234856
| not pursued | SA3#113 | Philips Interna... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0149 | 1 | F | 18.0.0 | Rel-18 | 4.1.3 - Clause 6.1.3.3 - Clarification DDS |
S3-235056
| agreed | SA3#113 | Philips Interna... |
SP-231322
| approved | SA#102 | SA WG3 | 18.1.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0149 | - | F | 18.0.0 | Rel-18 | 4.1.3 - Clause 6.1.3.3 - Clarification DDS |
S3-234512
| revised | SA3#113 | Philips Interna... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0148 | - | B | 18.0.0 | Rel-18 | UTC-based Counter Reconciliation |
S3-234510
| not pursued | SA3#113 | Philips Interna... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0147 | - | D | 18.0.0 | Rel-18 | Incorrect clause reference |
S3-234841
| merged | SA3#113 | OPPO |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0146 | - | F | 18.0.0 | Rel-18 | Hop-by-hop security policy |
S3-234839
| not pursued | SA3#113 | OPPO |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0145 | - | A | 18.0.0 | Rel-18 | Retrieving keys for decryption of protected IEs for U2N relay |
S3-234732
| not pursued | SA3#113 | Ericsson, Huawe... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0144 | - | F | 18.0.0 | Rel-18 | Corrections |
S3-234731
| agreed | SA3#113 | Ericsson |
SP-231322
| approved | SA#102 | SA WG3 | 18.1.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0143 | 1 | F | 18.0.0 | Rel-18 | UE-to-UE Relay Communication with integrated discovery |
S3-234843
| not pursued | SA3#113 | Ericsson |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0143 | - | F | 18.0.0 | Rel-18 | UE-to-UE Relay Communication with integrated discovery |
S3-234730
| revised | SA3#113 | Ericsson |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0142 | - | F | 17.5.0 | Rel-17 | Retrieving keys for decryption of protected IEs for U2N relay |
S3-234728
| not pursued | SA3#113 | Ericsson, Huawe... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0141 | - | F | 18.0.0 | Rel-18 | CR to TS33.503 Clarification on the process of protecting U2U relay discovery message |
S3-234727
| merged | SA3#113 | CATT |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0140 | 1 | A | 18.0.0 | Rel-18 | Rel18 ProSe: Updates on U2N relay security over control plane |
S3-234942
| agreed | SA3#113 | Qualcomm Incorp... |
SP-231321
| approved | SA#102 | SA WG3 | 18.1.0 | 5G_ProSe |
|
|
| 33.503 | 0140 | - | A | 18.0.0 | Rel-18 | Rel18 ProSe: Updates on U2N relay security over control plane |
S3-234714
| revised | SA3#113 | Qualcomm Incorp... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0139 | 2 | A | 18.0.0 | Rel-18 | Update discovery key response of U2N discovery security procdure |
S3-235013
| withdrawn | SA3#113 | Nokia,Qualcomm ... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0139 | 1 | A | 18.0.0 | Rel-18 | Rel18 ProSe - Updates on U2N relay discovery key request procedure |
S3-234941
| not pursued | SA3#113 | Qualcomm Incorp... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0139 | - | A | 18.0.0 | Rel-18 | Rel18 ProSe - Updates on U2N relay discovery key request procedure |
S3-234713
| revised | SA3#113 | Qualcomm Incorp... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0138 | - | F | 18.0.0 | Rel-18 | Rel18 ProSe – Adding security for U2U Relay communication with integrated discovery |
S3-234711
| not pursued | SA3#113 | Qualcomm Incorp... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0137 | - | F | 17.5.0 | Rel-17 | Rel17 ProSe: Updates on U2N relay security over control plane |
S3-234710
| agreed | SA3#113 | Qualcomm Incorp... |
SP-231321
| approved | SA#102 | SA WG3 | 17.6.0 | 5G_ProSe |
|
|
| 33.503 | 0136 | - | F | 17.5.0 | Rel-17 | Rel17 ProSe - Updates on U2N relay discovery key request procedure |
S3-234709
| not pursued | SA3#113 | Qualcomm Incorp... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0135 | 1 | F | 18.0.0 | Rel-18 | CR to TS33.503 Correction U2U Relay Communication |
S3-235010
| agreed | SA3#113 | CATT |
SP-231322
| approved | SA#102 | SA WG3 | 18.1.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0135 | - | F | 18.0.0 | Rel-18 | CR to TS33.503 Correction U2U Relay Communication |
S3-234700
| revised | SA3#113 | CATT |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0134 | 1 | A | 18.0.0 | Rel-18 | CR to TS33.503 Clarification on the use of 5GPKMF service operations Release 18 (mirror) |
S3-235055
| agreed | SA3#113 | CATT |
SP-231321
| approved | SA#102 | SA WG3 | 18.1.0 | 5G_ProSe |
|
|
| 33.503 | 0134 | - | A | 18.0.0 | Rel-18 | CR to TS33.503 Clarification on the use of 5GPKMF service operations Release 18 (mirror) |
S3-234699
| revised | SA3#113 | CATT |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0133 | 1 | F | 17.5.0 | Rel-17 | CR to TS33.503 Clarification on the use of 5GPKMF service operations Release 17 |
S3-235054
| agreed | SA3#113 | CATT |
SP-231321
| approved | SA#102 | SA WG3 | 17.6.0 | 5G_ProSe |
|
|
| 33.503 | 0133 | - | F | 17.5.0 | Rel-17 | CR to TS33.503 Clarification on the use of 5GPKMF service operations Release 17 |
S3-234698
| revised | SA3#113 | CATT |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0132 | 1 | F | 18.0.0 | Rel-18 | Update clause 6.1.1, 6.6.1, 6.6.3.3 and 6.6.4.1 |
S3-235011
| agreed | SA3#113 | OPPO, Xidian |
SP-231322
| approved | SA#102 | SA WG3 | 18.1.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0132 | - | F | 18.0.0 | Rel-18 | Update clause 6.1.1, 6.6.1, 6.6.3.3 and 6.6.4.1 |
S3-234688
| revised | SA3#113 | OPPO, Xidian |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0131 | - | A | 18.0.0 | Rel-18 | Clarification about key derivation in CP procedures and edtiorial changes R18 |
S3-234643
| agreed | SA3#113 | Huawei, HiSilicon |
SP-231321
| approved | SA#102 | SA WG3 | 18.1.0 | 5G_ProSe |
|
|
| 33.503 | 0130 | - | F | 17.5.0 | Rel-17 | Clarification about key derivation in CP procedures and edtiorial changes R17 |
S3-234642
| agreed | SA3#113 | Huawei, HiSilicon |
SP-231321
| approved | SA#102 | SA WG3 | 17.6.0 | 5G_ProSe |
|
|
| 33.503 | 0129 | - | F | 18.0.0 | Rel-18 | Clairification and editorial changes to clause 6.6.3.3 |
S3-234641
| merged | SA3#113 | Huawei, HiSilicon |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0128 | - | F | 18.0.0 | Rel-18 | Update the clause 6.6.3.3 in 33.503 |
S3-234587
| merged | SA3#113 | ZTE |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0127 | - | C | 18.0.0 | Rel-18 | Key identification for decryption of protected IEs for UE-to-Network Relay |
S3-234511
| not pursued | SA3#113 | Philips Interna... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0126 | - | F | 18.0.0 | Rel-18 | Retrieving keys for decryption of protected IEs in DCR for U2N relay |
S3-234522
| not pursued | SA3#113 | Interdigital |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0125 | - | F | 17.5.0 | Rel-17 | Retrieving keys for decryption of protected IEs in DCR for U2N relay |
S3-234521
| not pursued | SA3#113 | Interdigital |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0124 | 1 | F | 18.0.0 | Rel-18 | Security of 5G ProSe PC5 Communication – clarification |
S3-235066
| agreed | SA3#113 | Philips Interna... |
SP-231322
| approved | SA#102 | SA WG3 | 18.1.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0124 | - | F | 18.0.0 | Rel-18 | Security of 5G ProSe PC5 Communication – clarification |
S3-234509
| revised | SA3#113 | Philips Interna... |
| | | | | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0123 | - | B | 17.4.0 | Rel-18 | 5G_ProSe_Ph2 security enhancement |
S3-234331
| agreed | SA3#112 | CATT |
SP-230876
| approved | SA#101 | SA WG3 | 18.0.0 | 5G_ProSe_Ph2 |
|
|
| 33.503 | 0122 | 1 | F | 17.4.0 | Rel-17 | Add the 5G PKMF service operation |
S3-234338
| agreed | SA3#112 | Xiaomi |
SP-230875
| approved | SA#101 | SA WG3 | 17.5.0 | 5G_ProSe |
|
|
| 33.503 | 0122 | - | F | 17.4.0 | Rel-17 | Add the 5G PKMF service operation |
S3-234098
| revised | SA3#112 | Xiaomi |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0121 | - | F | 17.4.0 | Rel-17 | Correction to privacy protection of UP-PRUKID/CP-PRUKID and RSC in DCR |
S3-234097
| not pursued | SA3#112 | Xiaomi |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0120 | - | F | 17.4.0 | Rel-17 | CR to TR33.503 Correct definition of reference point Npc14 |
S3-234023
| agreed | SA3#112 | CATT |
SP-230875
| approved | SA#101 | SA WG3 | 17.5.0 | 5G_ProSe |
|
|
| 33.503 | 0119 | 1 | F | 17.4.0 | Rel-17 | Correction in clause 6.3.3.2.2 and 6.3.3.3.2 of TS 33.503 |
S3-234219
| agreed | SA3#112 | OPPO,Xidian |
SP-230875
| approved | SA#101 | SA WG3 | 17.5.0 | 5G_ProSe |
|
|
| 33.503 | 0119 | - | F | 17.4.0 | Rel-17 | Correction in clause 6.3.3.2.2 and 6.3.3.3.2 of TS 33.503 |
S3-233934
| revised | SA3#112 | OPPO,Xidian |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0118 | - | F | 17.4.0 | Rel-17 | U2N relay direct link setup failure due to RSC mismatch or integrity failure |
S3-233909
| not pursued | SA3#112 | Ericsson, Phili... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0117 | - | F | 17.4.0 | Rel-17 | Retrieving keys for decryption of protected IEs for U2N relay |
S3-233903
| not pursued | SA3#112 | Ericsson |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0116 | - | F | 17.4.0 | Rel-17 | Correction in clause 6.3.3.2.2 and 6.3.3.3.2 of TS 33.503 |
S3-233826
| withdrawn | SA3#112 | OPPO |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0115 | 1 | F | 17.4.0 | Rel-17 | Clarification on discovery of PKMF of Relay UE by the SMF in remote UE report procedure |
S3-234277
| agreed | SA3#112 | Huawei, HiSilicon |
SP-230875
| approved | SA#101 | SA WG3 | 17.5.0 | 5G_ProSe |
|
|
| 33.503 | 0115 | - | F | 17.4.0 | Rel-17 | Clarification on discovery of PKMF of Relay UE by the SMF in remote UE report procedure |
S3-233759
| revised | SA3#112 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0114 | - | F | 17.4.0 | Rel-17 | Clarification about Annex A.3 |
S3-233746
| merged | SA3#112 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0113 | - | F | 17.4.0 | Rel-17 | Identify discovery security materials in UE-to-Network Relay discovery |
S3-233743
| not pursued | SA3#112 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0112 | - | A | 17.4.0 | Rel-18 | Correction on derivation of CP-PRUK ID star |
S3-233678
| not pursued | SA3#112 | ZTE |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0111 | 1 | F | 17.4.0 | Rel-17 | Correction on derivation of CP-PRUK ID star |
S3-234215
| agreed | SA3#112 | ZTE |
SP-230875
| approved | SA#101 | SA WG3 | 17.5.0 | 5G_ProSe |
|
|
| 33.503 | 0111 | - | F | 17.4.0 | Rel-17 | Correction on derivation of CP-PRUK ID star |
S3-233677
| revised | SA3#112 | ZTE |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0110 | 1 | F | 17.4.0 | Rel-17 | Locate target PKMF in UP based security procedure of U2N relay communication |
S3-234218
| agreed | SA3#112 | Nokia, Nokia Sh... |
SP-230875
| approved | SA#101 | SA WG3 | 17.5.0 | 5G_ProSe |
|
|
| 33.503 | 0110 | - | F | 17.4.0 | Rel-17 | Locate target PKMF in UP based security procedure of U2N relay communication |
S3-233615
| revised | SA3#112 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0109 | 3 | F | 17.5.0 | Rel-17 | Update discovery key response of U2N discovery security procdure |
S3-235012
| withdrawn | SA3#113 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0109 | 2 | F | 17.5.0 | Rel-17 | Update discovery key response of U2N discovery security procdure |
S3-234923
| not pursued | SA3#113 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0109 | 1 | F | 17.5.0 | Rel-17 | Update discovery key response of U2N discovery security procdure |
S3-234855
| revised | SA3#113 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0109 | - | F | 17.4.0 | Rel-17 | Update discovery key response of U2N discovery security procdure |
S3-233614
| revised | SA3#112 | Nokia, Nokia Sh... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0108 | - | F | 17.3.0 | Rel-17 | UE to Network Relay discovery security procdure |
S3-233106
| not pursued | SA3#111 | Nokia, Nokia Sh... |
| | | | | TEI17 |
|
|
| 33.503 | 0107 | - | F | 17.3.0 | Rel-17 | Direct discovery security procdure |
S3-233105
| not pursued | SA3#111 | Nokia, Nokia Sh... |
| | | | | TEI17 |
|
|
| 33.503 | 0106 | - | F | 17.3.0 | Rel-17 | Update discovery key response of U2N discovery security procdure |
S3-233103
| not treated | SA3#111 | Nokia, Nokia Sh... |
| | | | | TEI17 |
|
|
| 33.503 | 0105 | 1 | F | 17.3.0 | Rel-17 | Locate target DDNMF in U2N discovery security procdure |
S3-233377
| agreed | SA3#111 | Nokia, Nokia Sh... |
SP-230598
| approved | SA#100 | SA WG3 | 17.4.0 | TEI17 |
|
|
| 33.503 | 0105 | - | F | 17.3.0 | Rel-17 | Locate target DDNMF in U2N discovery security procdure |
S3-233102
| revised | SA3#111 | Nokia, Nokia Sh... |
| | | | | TEI17 |
|
|
| 33.503 | 0104 | - | F | 17.3.0 | Rel-17 | CR to TR33.503 Define missing reference points |
S3-233075
| agreed | SA3#111 | CATT |
SP-230600
| approved | SA#100 | SA WG3 | 17.4.0 | 5G_ProSe |
|
|
| 33.503 | 0103 | - | F | 17.3.0 | Rel-17 | CR to TR33.503 Editorial changes |
S3-233074
| agreed | SA3#111 | CATT |
SP-230600
| approved | SA#100 | SA WG3 | 17.4.0 | 5G_ProSe |
|
|
| 33.503 | 0102 | 1 | F | 17.3.0 | Rel-17 | Fix the restricted discovery procedures in 5G ProSe |
S3-233185
| agreed | SA3#111 | Huawei, HiSilicon |
SP-230600
| approved | SA#100 | SA WG3 | 17.4.0 | 5G_ProSe |
|
|
| 33.503 | 0102 | - | F | 17.3.0 | Rel-17 | Fix the restricted discovery procedures in 5G ProSe |
S3-232793
| revised | SA3#111 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0101 | - | F | 17.3.0 | Rel-17 | Clarification on discovery of PKMF of Relay UE by the SMF |
S3-232731
| not treated | SA3#111 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0100 | - | F | 17.3.0 | Rel-17 | DDNMF selection in UE-to-Network Relay discovery procedure |
S3-232728
| merged | SA3#111 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0099 | - | F | 17.3.0 | Rel-17 | Correction in 5G ProSe Direct Discovery |
S3-232620
| agreed | SA3#111 | China Telecom |
SP-230600
| approved | SA#100 | SA WG3 | 17.4.0 | 5G_ProSe |
|
|
| 33.503 | 0098 | - | F | 17.3.0 | Rel-17 | Correction in 5G ProSe Direct Discovery |
S3-232617
| withdrawn | SA3#111 | China Telecommu... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0097 | - | F | 17.3.0 | Rel-17 | U2N relay direct link setup failure due to RSC mismatch or integrity failure |
S3-232417
| not pursued | SA3#111 | Ericsson |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0096 | - | F | 17.2.0 | Rel-17 | Correction to privacy protection of UP-PRUKID/CP-PRUKID and RSC in DCR |
S3-231247
| not pursued | SA3#110 | Beijing Xiaomi ... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0095 | - | F | 17.2.0 | Rel-17 | A Note for Protection of DCR in U2N Communication |
S3-231207
| not pursued | SA3#110 | Xiaomi Technology |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0094 | - | F | 17.2.0 | Rel-17 | DDNFM Selection during U2N Relay Discovery Security Procedure |
S3-231206
| not pursued | SA3#110 | Xiaomi Technology |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0093 | - | F | 17.2.0 | Rel-17 | CR to TR33.503 Editorial changes |
S3-231197
| agreed | SA3#110 | CATT |
SP-230146
| approved | SA#99 | SA WG3 | 17.3.0 | 5G_ProSe |
|
|
| 33.503 | 0092 | - | F | 17.2.0 | Rel-17 | clarify protocol layer for discovery message protection |
S3-231136
| agreed | SA3#110 | Nokia, Nokia Sh... |
SP-230144
| approved | SA#99 | SA WG3 | 17.3.0 | TEI17 |
|
|
| 33.503 | 0091 | - | F | 17.2.0 | Rel-17 | Update discovery key response of U2N discovery security procdure |
S3-231134
| not pursued | SA3#110 | Nokia, Nokia Sh... |
| | | | | TEI17 |
|
|
| 33.503 | 0090 | - | F | 17.2.0 | Rel-17 | Locate target DDNMF in U2N discovery security procdure |
S3-231133
| not pursued | SA3#110 | Nokia, Nokia Sh... |
| | | | | TEI17 |
|
|
| 33.503 | 0089 | - | F | 17.2.0 | Rel-17 | Clarify RID for PAnF discover |
S3-231130
| merged | SA3#110 | Nokia, Nokia Sh... |
| | | | | TEI17 |
|
|
| 33.503 | 0088 | - | F | 17.2.0 | Rel-17 | Use remote UE SNN to generate AV for ProSe authentication |
S3-231129
| not pursued | SA3#110 | Nokia, Nokia Sh... |
| | | | | TEI17 |
|
|
| 33.503 | 0087 | 1 | F | 17.2.0 | Rel-17 | Use relay UE SNN to generate AV for ProSe authentication |
S3-231559
| agreed | SA3#110 | Nokia, Nokia Sh... |
SP-230144
| approved | SA#99 | SA WG3 | 17.3.0 | TEI17 |
|
|
| 33.503 | 0087 | - | F | 17.2.0 | Rel-17 | Use relay UE SNN to generate AV for ProSe authentication |
S3-231128
| revised | SA3#110 | Nokia, Nokia Sh... |
| | | | | TEI17 |
|
|
| 33.503 | 0086 | 1 | F | 17.2.0 | Rel-17 | Remote UE Report in CP based solution for 5G ProSe UE-to-Network Relay |
S3-231431
| agreed | SA3#110 | Ericsson,Interd... |
SP-230146
| approved | SA#99 | SA WG3 | 17.3.0 | 5G_ProSe |
|
|
| 33.503 | 0086 | - | F | 17.2.0 | Rel-17 | Remote UE Report in CP based solution for 5G ProSe UE-to-Network Relay |
S3-231072
| revised | SA3#110 | Ericsson |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0085 | 1 | F | 17.2.0 | Rel-17 | Remote UE Report in UP based solution for 5G ProSe UE-to-Network Relay |
S3-231430
| agreed | SA3#110 | Ericsson,Interd... |
SP-230146
| approved | SA#99 | SA WG3 | 17.3.0 | 5G_ProSe |
|
|
| 33.503 | 0085 | - | F | 17.2.0 | Rel-17 | Remote UE Report in UP based solution for 5G ProSe UE-to-Network Relay |
S3-231071
| revised | SA3#110 | Ericsson |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0084 | - | F | 17.2.0 | Rel-17 | U2N relay direct link setup failure due to RSC mismatch or integrity failure |
S3-231070
| not pursued | SA3#110 | Ericsson |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0083 | 1 | F | 17.2.0 | Rel-17 | Clarify Kausf_p generation |
S3-231425
| agreed | SA3#110 | Ericsson |
SP-230146
| approved | SA#99 | SA WG3 | 17.3.0 | 5G_ProSe |
|
|
| 33.503 | 0083 | - | F | 17.2.0 | Rel-17 | Clarify Kausf_p generation |
S3-231068
| revised | SA3#110 | Ericsson |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0082 | - | F | 17.2.0 | Rel-17 | KDF input parameter for generating AV of ProSe authentication |
S3-231067
| merged | SA3#110 | Ericsson |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0081 | - | F | 17.2.0 | Rel-17 | Nudm service operation correction |
S3-231066
| merged | SA3#110 | Ericsson |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0080 | - | F | 17.2.0 | Rel-17 | Clarify about the ProSe authentication |
S3-231023
| merged | SA3#110 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0079 | - | F | 17.2.0 | Rel-17 | Correction on SUPI in Nudm_UEAuthentication_GetProseAv service |
S3-231019
| agreed | SA3#110 | Huawei, HiSilicon |
SP-230146
| approved | SA#99 | SA WG3 | 17.3.0 | 5G_ProSe |
|
|
| 33.503 | 0078 | 1 | F | 17.2.0 | Rel-17 | Correction to ProSe Authentication Vector obtaining process |
S3-231424
| agreed | SA3#110 | Huawei, HiSilicon |
SP-230146
| approved | SA#99 | SA WG3 | 17.3.0 | 5G_ProSe |
|
|
| 33.503 | 0078 | - | F | 17.2.0 | Rel-17 | Correction to ProSe Authentication Vector obtaining process |
S3-231018
| revised | SA3#110 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0077 | - | F | 17.2.0 | Rel-17 | Clarification of PAnF action when CP-PRUK is stale |
S3-231000
| not pursued | SA3#110 | Huawei, HiSilicon |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0076 | - | F | 17.2.0 | Rel-17 | Correction in 6.3.3.3.2 |
S3-230932
| agreed | SA3#110 | ChinaTelecom |
SP-230146
| approved | SA#99 | SA WG3 | 17.3.0 | 5G_ProSe |
|
|
| 33.503 | 0075 | - | F | 17.2.0 | Rel-17 | Correction in 6.2.1 and 6.2.2 |
S3-230931
| agreed | SA3#110 | ChinaTelecom |
SP-230146
| approved | SA#99 | SA WG3 | 17.3.0 | 5G_ProSe |
|
|
| 33.503 | 0074 | - | F | 17.2.0 | Rel-17 | Correction in 6.1.3.2.2.2 |
S3-230929
| agreed | SA3#110 | ChinaTelecom |
SP-230146
| approved | SA#99 | SA WG3 | 17.3.0 | 5G_ProSe |
|
|
| 33.503 | 0073 | - | F | 17.2.0 | Rel-17 | Correction in 6.1.1 |
S3-230928
| agreed | SA3#110 | ChinaTelecom |
SP-230146
| approved | SA#99 | SA WG3 | 17.3.0 | 5G_ProSe |
|
|
| 33.503 | 0072 | - | F | 17.2.0 | Rel-17 | Correction in 5.2.4.2 |
S3-230927
| agreed | SA3#110 | ChinaTelecom |
SP-230146
| approved | SA#99 | SA WG3 | 17.3.0 | 5G_ProSe |
|
|
| 33.503 | 0071 | - | F | 17.1.0 | Rel-17 | include RID of AUSF in CP PRUK ID |
S3-223824
| not pursued | SA3#109 | Nokia, Nokia Sh... |
| | | | | TEI17 |
|
|
| 33.503 | 0070 | - | F | 17.1.0 | Rel-17 | include RID of AUSF in DCR |
S3-223823
| not pursued | SA3#109 | Nokia, Nokia Sh... |
| | | | | TEI17 |
|
|
| 33.503 | 0069 | - | F | 17.1.0 | Rel-17 | use remote UE SNN to generate AV for ProSe authentication |
S3-223821
| not pursued | SA3#109 | Nokia, Nokia Sh... |
| | | | | TEI17 |
|
|
| 33.503 | 0068 | - | F | 17.1.0 | Rel-17 | use relay UE SNN to generate AV for ProSe authentication |
S3-223820
| not pursued | SA3#109 | Nokia, Nokia Sh... |
| | | | | TEI17 |
|
|
| 33.503 | 0067 | - | F | 17.1.0 | Rel-17 | Correction to privacy protection of UP-PRUK ID and RSC in DCR |
S3-223772
| merged | SA3#109 | Beijing Xiaomi ... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0066 | - | F | 17.1.0 | Rel-17 | Updates to Key Definitions |
S3-223745
| not pursued | SA3#109 | Xiaomi Technology |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0065 | - | F | 17.1.0 | Rel-17 | Security Method Check during U2N Relay Discovery Procedure |
S3-223744
| not pursued | SA3#109 | Xiaomi Technology |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0064 | 1 | F | 17.1.0 | Rel-17 | Match Report in U2N Relay Discovery Security Procedure |
S3-223958
| agreed | SA3#109 | Xiaomi Technolo... |
SP-221152
| approved | SA#98-e | SA WG3 | 17.2.0 | 5G_ProSe |
|
|
| 33.503 | 0064 | - | F | 17.1.0 | Rel-17 | Match Report in U2N Relay Discovery Security Procedure |
S3-223743
| revised | SA3#109 | Xiaomi Technology |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0063 | - | F | 17.1.0 | Rel-17 | DDNFM Selection during U2N Relay Discovery Security Procedure |
S3-223742
| not pursued | SA3#109 | Xiaomi Technolo... |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0062 | - | F | 17.1.0 | Rel-17 | CP-PRUK refresh |
S3-223706
| agreed | SA3#109 | Ericsson |
SP-221152
| approved | SA#98-e | SA WG3 | 17.2.0 | 5G_ProSe |
|
|
| 33.503 | 0061 | 1 | F | 17.1.0 | Rel-17 | Nudm servcie operation correction |
S3-223962
| not pursued | SA3#109 | Ericsson |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0061 | - | F | 17.1.0 | Rel-17 | Nudm servcie operation correction |
S3-223705
| revised | SA3#109 | Ericsson |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0060 | 1 | F | 17.1.0 | Rel-17 | Correcting the handling of synchronisation error |
S3-224133
| agreed | SA3#109 | Ericsson |
SP-221152
| approved | SA#98-e | SA WG3 | 17.2.0 | 5G_ProSe |
|
|
| 33.503 | 0060 | - | F | 17.1.0 | Rel-17 | Correcting the handling of synchronisation error |
S3-223704
| revised | SA3#109 | Ericsson |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0059 | 1 | F | 17.1.0 | Rel-17 | Renaming 5GPRUK, 5GPRUK ID, PRUK and PRUK ID |
S3-223956
| agreed | SA3#109 | Ericsson,China ... |
SP-221152
| approved | SA#98-e | SA WG3 | 17.2.0 | 5G_ProSe |
|
|
| 33.503 | 0059 | - | F | 17.1.0 | Rel-17 | Renaming 5GPRUK, 5GPRUK ID, PRUK and PRUK ID |
S3-223703
| revised | SA3#109 | Ericsson |
| | | | | 5G_ProSe |
|
|
| 33.503 | 0058 | 1 | F | 17.1.0 | Rel-17 | Correction to authentication mechanism selection |
S3-224161
| agreed | SA3#109 | Ericsson, Xiaomi |
SP-221152
| approved | SA#98-e | SA WG3 | 17.2.0 | 5G_ProSe |
|