Please enter the search related information in the fields below. Partial information works, e.g. "SP-21" in the "tdoc" field lists all TSG SA documents from 2021. Regular expressions mostly work in all fields (e.g. "2[34].501" in the "Spec" field lists all documents related to 23.501 and 24.501. Capitalization is disregarded, i.e. "3GPP" gives the same results as "3gpp".
Download results in JSON format
| tdoc | Title | Type / Revs | Source | Spec / CR | S/WID | Release | Meeting | Status | Links |
|---|---|---|---|---|---|---|---|---|---|
| S3-220640 | Reply to LS on new reference point name for the interface between PKMF and UDM in 5G ProSe |
LS in revised to S3-220679 |
S2-2203018 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] | |||
| S3-220679 | Reply to LS on new reference point name for the interface between PKMF and UDM in 5G ProSe |
LS in revision of S3-220640 |
S2-2203018 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | |||
| S3-220706 | Clarify relationship between KAUSF, KAUSF_P and 5G PRUK | pCR | China Telecomunication Corp. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-220707 | Clarify the necessity of refreshing 5G PRUK during CP-based Security Procedure | pCR | China Telecomunication Corp. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-220734 | Update Security procedure over CP with using PRUK ID in DCR | pCR | InterDigital, Europe, Ltd.,, Samsung, LG Electronics, Nokia, Nokia Shanghai Bell, Ericsson, Verizon Wireless, MITRE, Convida Wireless LLC, Philips International B.V. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-220735 | 5GPRUK/5GPRUK ID Storage Options and Way Forward | discussion | InterDigital, Europe, Ltd., Ericsson | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | ||
| S3-220736 | PAnF supported services discussion | discussion | InterDigital, Europe, Ltd. | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | ||
| S3-220737 | Update Security procedure over CP with using PRUK ID in DCR (alt#2) | pCR | InterDigital, Europe, Ltd. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-220744 | Add some context about 5G PRUK ID reject cases in the clause 6.3.3.3.2 | pCR | ZTE Corporation | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220745 | Clarification on AUSF instance store in UDM | pCR | ZTE Corporation | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220746 | Remove the EN in the clause 6.3.3.2.2 | pCR | ZTE Corporation | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-220747 | Update the clause 6.3.3.3.3 | pCR | ZTE Corporation | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-220748 | Update the clause 7.4.2 | pCR | ZTE Corporation | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-220815 | EN resolution for Secondary Authentication for Remote UE with L3 U2N relay without N3IWF(Alt1) | pCR | LG Electronics Inc. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220816 | EN resolution for Secondary Authentication for Remote UE with L3 U2N relay without N3IWF(Alt2) |
pCR revised to S3-221174 |
LG Electronics Inc. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220817 | Revocation_ReAuth for Secondary Authentication for Remote UE |
pCR revised to S3-221175 |
LG Electronics Inc. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220825 | Integrity protection of DCR message | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-220826 | Clarification on the privacy protection of DCR | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220827 | Delete of CP based solution | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220828 | Delete of Secondary authentication | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220829 | Address EN of secondary authentication | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220830 | Add a new clause for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support |
pCR revised to S3-221238 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220842 | Adding UDM Services for SUCI deconceal and authorization information retrieval |
pCR revised to S3-221241 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220843 | Remote UE Identity provisioning in UE-to-Network Relay communication security procedure over user plane | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-220844 | Remote UE authorization check in UE-to-Network Relay communication security procedure over control plane | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-220845 | Resolving the EN on the needs and usage of 5GPRUK ID |
pCR revised to S3-221242 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220846 | Format of 5GPRUK ID |
pCR revised to S3-221243 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220847 | Clarification on restricted discovery procedures | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220848 | Clarification on the security of L2 U2NW |
pCR revised to S3-221244 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220850 | Key derivation related clarification in CP-based UE-to-Network relay procedures |
pCR revised to S3-221245 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220851 | Add subclause about the restricted discovery for UE-to-Network relay | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-220852 | Terminology alignment for 5G ProSe Remote UE specific authentication | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-220855 | Clarification | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
withdrawn | [WTS] [JSN] |
| S3-220868 | Clarification on KAUSF_P | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-220869 | Clarification on PRUK ID |
pCR revised to S3-221252 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220874 | Security capability negotiation during unicast establishment after restricted discovery | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220881 | Clarification on the description of PRUK |
pCR revised to S3-221255 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220882 | Clarification on the secondary authentication procedure |
pCR revised to S3-221256 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220883 | Update general clause for secondary authentication |
pCR revised to S3-221257 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220894 | Discussion for key storage and derivation in UE-to-Network security procedure over Control Plane | pCR | Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220934 | Security protocol over CP with 5G AKA to establishPC5 keys | pCR | THALES | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220936 | Security protocol over CP with 5G ProSe security context in the USIM | pCR | THALES | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220965 | Corrections to CP based solution | pCR | Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-220966 | Reference point name |
pCR revised to S3-221182 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220967 | Remote UE Report in UP based solution |
pCR revised to S3-221271 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220968 | Rephrasing Clause 6.2.1 to emphasize that security parameters for PC5 Direct Communication are determined during Direct Discovery |
pCR revised to S3-221272 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220969 | Restructure of security requirements for 5G ProSe UE-to-network relay | pCR | Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220970 | Remote UE Report in CP based solution | pCR | Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220971 | Discussion on UE ID privacy for Remote UE Report | discussion | Ericsson | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | |
| S3-220972 | PLMN ID in Direct Security Mode Failure |
pCR revised to S3-221183 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220973 | KNRP key derivation | pCR | Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-220974 | CR for Prose changes to TS 33.220 in Rel-17 | CR | Ericsson | 33.22 17.2.0 CR#216 catF | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
not pursued | [WTS] [JSN] |
| S3-220994 | PC5 security policy provisioning for user-plane L3 U2N relay solution |
pCR revised to S3-221294 |
Qualcomm Incorporated, Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220995 | Clarification on the PC5 link establishment for user-plane L3 U2N relay solution | pCR | Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-220996 | CR to ProSe TS - Address the Editor’s Notes in clause 6.3.5 |
pCR revised to S3-221295 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-220997 | CR to ProSe TS – An update on MIC calculation for discovery message | pCR | Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-220998 | CR to ProSe TS – Clarification on discovery message protection | pCR | Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-220999 | CR to ProSe TS – Removing an Editor’s Note in user plane based U2N procedure |
pCR revised to S3-221296 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-221000 | Update on 5G ProSe restricted discovery procedure for U2N relay |
pCR revised to S3-221302 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-221001 | CR to ProSe TS - Clarification on Knrp derivation for U2N relay over user plane |
pCR revised to S3-221297 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-221003 | pCR to TS33.503 Abbreviations update |
pCR revised to S3-221281 |
CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-221005 | pCR to TS33.503 Clause 4.2 Update reference point name between 5G PKMF and UDM | pCR | CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-221006 | pCR to TS33.503 Wording update | pCR | CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221007 | pCR to TS33.503 Clause 6.3 Update security requirements of UE-to-Network Relay | pCR | CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-221012 | pCR to TS33.503 Clause 6.3 Update security requirements of Layer-3 UE-to-Network Relay | pCR | CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-221013 | pCR to TS33.503 Clause 6.3 Remove unnecessary description from UP-based and CP-based procedures | pCR | CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-221014 | pCR to TS33.503 Clause 6.3 Clarification text for Kausf_p |
pCR revised to S3-221282 |
CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-221015 | pCR to TS33.503 Clause 6.3 Solution for co-existence of UP and CP security options |
pCR revised to S3-221284 |
CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-221016 | pCR to TS33.503 Clause 6.3 Update security procedure over Control Plane | pCR | CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-221025 | 33.503: Updates in Clause 4.2 | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221026 | 33.503: Updates in Clause 5.2.5 | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221027 | 33.503: Updates in Clause 6.1.3.2 |
pCR revised to S3-221189 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-221028 | 33.503: Clarifiacation on MIC Check in Open Discovery | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221029 | 33.503: General Description for ProSe U2N Relay Discovery Security | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-221030 | 33.503: Add Security Requirement for ProSe U2N Relay Discovery | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-221031 | 33.503: Control Plane based Security Procedure for ProSe U2N Relay Discovery | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-221032 | 33.503: User Plane based Security Procedure for ProSe U2N Relay Discovery | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-221033 | 33.503: Derivation of Discovery Keys for ProSe U2N Relay Discovery | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-221034 | 33.503: Updates to General Security Requirements for U2N Relay Communication |
pCR revised to S3-221206 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-221035 | 33.503: Updates to Security Requirements for U2N Relay Communication via L3 Relay UE |
pCR revised to S3-221207 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-221036 | Discussion on PC5 Key Hierarchy for ProSe U2N Relay Communication | discussion | Xiaomi Technology | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | |
| S3-221037 | Discussion on Security for ProSe U2N Relay Communication over User Plane | discussion | Xiaomi Technology | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | |
| S3-221038 | 33.503: Update to Security Procedure over User Plane | pCR | Xiaomi Technology, China Telecom | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-221039 | 33.503: PRUK Derivation for ProSe U2N Relay Security over User Plane | pCR | Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-221040 | 33.503: Updates in Clause 6.3.4 |
pCR revised to S3-221208 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
revised | [WTS] [JSN] |
| S3-221137 | CP based security selection | pCR | Nokia, Nokia Shanghai Bell, Interdigital, LGE, Samsung | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-221138 | derive 5GPRUK based on Kausf_p | pCR | Nokia, Nokia Shanghai Bell, Interdigital, LGE, Samsung | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
merged | [WTS] [JSN] |
| S3-221139 | authorization of remote UE | pCR | Nokia, Nokia Shanghai Bell, Interdigital, LGE, Samsung | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-221140 | UP based security selection | pCR | Nokia, Nokia Shanghai Bell, Interdigital, LGE, Samsung | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-221141 | Relay Discovery clarifications | pCR | Philips International B.V. | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] |
| S3-221149 | 5G Prose questions on CP for show-of-hands | other | Interdigital,CATT |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | |||
| S3-221150 | Questions of show hand on ProSe CP-based solution | discussion | CATT |
S3-107-e AI: 4.7 |
noted | [WTS] [JSN] | |||
| S3-221174 | EN resolution for Secondary Authentication for Remote UE with L3 U2N relay without N3IWF(Alt2) |
pCR revision of S3-220816 |
LG Electronics Inc., Interdigital | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221175 | Revocation_ReAuth for Secondary Authentication for Remote UE |
pCR revision of S3-220817 |
LG Electronics Inc., Interdigital | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221182 | Reference point name |
pCR revision of S3-220966 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221183 | PLMN ID in Direct Security Mode Failure |
pCR revision of S3-220972 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221189 | 33.503: Updates in Clause 6.1.3.2 |
pCR revision of S3-221027 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221206 | 33.503: Updates to General Security Requirements for U2N Relay Communication |
pCR revision of S3-221034 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221207 | 33.503: Updates to Security Requirements for U2N Relay Communication via L3 Relay UE |
pCR revision of S3-221035 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221208 | 33.503: Updates in Clause 6.3.4 |
pCR revision of S3-221040 |
Xiaomi Technology | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221238 | Add a new clause for 5G ProSe Layer-3 UE-to-Network Relay with N3IWF support |
pCR revision of S3-220830 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221241 | Adding UDM Services for SUCI deconceal and authorization information retrieval |
pCR revision of S3-220842 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221242 | Resolving the EN on the needs and usage of 5GPRUK ID |
pCR revision of S3-220845 |
Huawei, HiSilicon, Interdigital, LG Electronics, ChinaTelecom,Xiaomi, CATT, Samsung | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221243 | Format of 5GPRUK ID |
pCR revision of S3-220846 |
Huawei, HiSilicon, ZTE | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221244 | Clarification on the security of L2 U2NW |
pCR revision of S3-220848 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221245 | Key derivation related clarification in CP-based UE-to-Network relay procedures |
pCR revision of S3-220850 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221252 | Clarification on PRUK ID |
pCR revision of S3-220869 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221255 | Clarification on the description of PRUK |
pCR revision of S3-220881 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221256 | Clarification on the secondary authentication procedure |
pCR revision of S3-220882 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221257 | Update general clause for secondary authentication |
pCR revision of S3-220883 |
Huawei, HiSilicon | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221271 | Remote UE Report in UP based solution |
pCR revision of S3-220967 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221272 | Rephrasing Clause 6.2.1 to emphasize that security parameters for PC5 Direct Communication are determined during Direct Discovery |
pCR revision of S3-220968 |
Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221281 | pCR to TS33.503 Abbreviations update |
pCR revision of S3-221003 |
CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221282 | pCR to TS33.503 Clause 6.3 Clarification text for Kausf_p |
pCR revision of S3-221014 |
CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221284 | pCR to TS33.503 Clause 6.3 Solution for co-existence of UP and CP security options |
pCR revision of S3-221015 |
CATT | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221286 | Draft TS 33.503 v0.4.0 Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) | draft TS | CATT | 5GS_Ph1-SEC, 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] | |
| S3-221294 | PC5 security policy provisioning for user-plane L3 U2N relay solution |
pCR revision of S3-220994 |
Qualcomm Incorporated, Ericsson | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221295 | CR to ProSe TS - Address the Editor’s Notes in clause 6.3.5 |
pCR revision of S3-220996 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221296 | CR to ProSe TS – Removing an Editor’s Note in user plane based U2N procedure |
pCR revision of S3-220999 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221297 | CR to ProSe TS - Clarification on Knrp derivation for U2N relay over user plane |
pCR revision of S3-221001 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
| S3-221299 | Cover page TS 33.503 | TS or TR cover | CATT | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] | |
| S3-221302 | Update on 5G ProSe restricted discovery procedure for U2N relay |
pCR revision of S3-221000 |
Qualcomm Incorporated | 33.503 0.3.0 | 5G_ProSe | Rel-17 |
S3-107-e AI: 4.7 |
approved | [WTS] [JSN] |
122 documents (0.36148381233215 seconds)