|
| 33.503 | 0218 | - | F | 19.0.0 | Rel-19 | Clarification on the discovery security materials provisioning for inter-PLMN scenario |
S3-251623
| merged | SA3#121 | Xiaomi |
| | | | | 5G_ProSe_Sec_Ph3 |
|
|
| 33.503 | 0217 | - | F | 19.0.0 | Rel-19 | Adding support of intermediate UE-to-network relays from different HPLMNs in 5G ProSe Multi-hop UE-to-Network Relay Discovery |
S3-251593
| not pursued | SA3#121 | Ericsson |
| | | | | 5G_ProSe_Sec_Ph3 |
|
|
| 33.503 | 0216 | 1 | C | 19.0.0 | Rel-19 | Addressing the Editor’s Notes in multi-hop U2N relay discovery security |
S3-251793
| not pursued | SA3#121 | Qualcomm Incorp... |
| | | | | 5G_ProSe_Sec_Ph3 |
|
|
| 33.503 | 0216 | - | C | 19.0.0 | Rel-19 | Addressing the Editor’s Notes in multi-hop U2N relay discovery security |
S3-251591
| revised | SA3#121 | Qualcomm Incorp... |
| | | | | 5G_ProSe_Sec_Ph3 |
|
|
| 33.503 | 0215 | - | B | 19.0.0 | Rel-19 | Adressing the EN in multi-hop U2N Model B |
S3-251511
| merged | SA3#121 | China Telecom |
| | | | | 5G_ProSe_Sec_Ph3 |
|
|
| 33.503 | 0214 | - | B | 19.0.0 | Rel-19 | Adressing the EN in multi-hop U2N Model A |
S3-251510
| merged | SA3#121 | China Telecom |
| | | | | 5G_ProSe_Sec_Ph3 |
|
|
| 33.503 | 0213 | - | F | 19.0.0 | Rel-19 | Adress Editor's Note about multi-hop UE-to-Network Relay discovery - PLMN restrictions |
S3-251442
| merged | SA3#121 | Huawei, HiSilicon |
| | | | | 5G_ProSe_Sec_Ph3 |
|
|
| 33.503 | 0212 | - | F | 19.0.0 | Rel-19 | Adress Editor's Note about multi-hop UE-to-Network Relay discovery |
S3-251440
| merged | SA3#121 | Huawei, HiSilicon |
| | | | | 5G_ProSe_Sec_Ph3 |
|
|
| 33.503 | 0211 | - | B | 18.5.0 | Rel-19 | Adding multi-hop security features of 5G_ProSe_Sec_Ph3 |
S3-251170
| agreed | SA3#120 | Huawei |
SP-250112
| approved | SA#107 | SA WG3 | 19.0.0 | 5G_ProSe_Sec_Ph3 |
|