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-212424 | LS on Layer-3 UE-to-Network Relay authentication and authorization |
LS in LS reply in S3-212424, S3-213128 |
S2-2101623 |
S3-104-e AI: 5.9 |
replied to | [WTS] [JSN] | |||
S3-212453 | Evaluation of Solution #22: Representation of identities during broadcast | pCR | KPN N.V. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212457 | Conclusion on Key Issue #11: UE identity protection during ProSe discover | pCR | KPN N.V. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212464 | New solution: Keying procedures for Group Member and Relay discovery: public safety case |
pCR revised to S3-213175 |
MITRE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212465 | Update to KI #17 |
pCR revised to S3-213176 |
MITRE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212469 | Conclusion on Key Issue #12: Security of one-to-one communication over PC5 | pCR | KPN N.V. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212470 | Clean-up for KI#1 | pCR | LG Electronics Inc. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212471 | Updates on sol#10 | pCR | LG Electronics Inc. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-212472 | Evaluation for sol#13 |
pCR revised to S3-213087 |
LG Electronics Inc. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212473 | Editorial corrections for sol#10 | pCR | LG Electronics Inc. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212478 | TR 33.847 Update for solution #10 |
pCR revised to S3-213059 |
InterDigital, Europe, Ltd. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212479 | TR 33.847 Update for solution #24 |
pCR revised to S3-213060 |
InterDigital, Europe, Ltd. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212481 | TR 33.847 Update for solution #25 |
pCR revised to S3-213062 |
InterDigital, Europe, Ltd. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212484 | Way forward for L3 U2N Relay Authorization and security conclusions | discussion | InterDigital, Europe, Ltd., Samsung, LG Electronics, Nokia, Nokia Shanghai Bell | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] | ||
S3-212485 | Conclusions for U2N relay Key Issues |
pCR revised to S3-213063 |
InterDigital, Europe, Ltd., Samsung, LG Electronics, Nokia, Nokia Shanghai Bell | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212516 | Updates on sol#13 |
pCR revised to S3-213088 |
LG Electronics Inc. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212546 | Conclusion of Key Issue #1 | pCR | ZTE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212547 | Update to Solution #5 |
pCR revised to S3-213081 |
ZTE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212548 | Conclusion for UE to UE relay | pCR | ZTE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212549 | Solution for key issue #17 | pCR | ZTE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212550 | Update the key issue#2 | pCR | ZTE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212551 | Update the solution#36 | pCR | ZTE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212603 | conclusion to KI#2 |
pCR revised to S3-213105 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212604 | conclusion to KI#5 to KI#8 |
pCR revised to S3-213106 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212605 | conclusion to KI#11 | pCR | Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212608 | Resolve EN in Sol#27 |
pCR revised to S3-213107 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212609 | Resolve EN in Sol#28 |
pCR revised to S3-213108 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212610 | New solution for one-to-one communication | pCR | Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212611 | Add conclusion to Key Issue #1 |
pCR revised to S3-213109 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212612 | Add conclusion to Key Issue #3 | pCR | Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212613 | Add conclusion to key Issue #9 | pCR | Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212614 | Add conclusion to Key Issue #12 | pCR | Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212615 | Add conclusion to key Issue #16 | pCR | Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212619 | New solution to avoid policy mismatch |
pCR revised to S3-213110 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212620 | Discussion on the bidding down attack during one-to-one communication establishment | pCR | Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212625 | New solution on UE-to-network relay Key management based on primary authentication |
pCR revised to S3-213111 |
Huawei,HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212728 | pCR to TR33.847- Conclusion of KI#1 | pCR | CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212729 | pCR to TR33.847- Conclusion of KI#2 | pCR | CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212731 | pCR to TR33.847- Conclusion of KI#3 |
pCR revised to S3-213092 |
CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212732 | pCR to TR33.847- Conclusion of KI#6-KI#8 | pCR | CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212745 | pCR to TR33.847- Conclusion of KI#12 | pCR | CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212751 | pCR to TR33.847- Conclusion of KI#13 |
pCR revised to S3-213093 |
CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212766 | pCR to TR33.847- Update Solution#29 | pCR | CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212809 | Update and evaluation of solution #32 |
pCR revised to S3-213074 |
Philips International B.V. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212851 | Conclusion on KI #3, KI #4 and KI #9 related to security for the Layer-3 UE-to-Network relay scenario | pCR | Qualcomm Incorporated, MITRE, AT&T | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212852 | Conclusion of KI #1 | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212853 | EN resolution of Solution #34 | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212854 | Evaluation of Solution #34 |
pCR revised to S3-213076 |
Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212855 | Evaluation of Solution #24 | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212856 | EN resolution of Solution #18 | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212857 | Conclusion of KI #3 | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212858 | Conclusion of KI #4 | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212859 | Update of solution #18 to support privacy protection | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212860 | Update an evaluation for solution #10 | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212861 | Conclusion of security and privacy of groupcast communication | pCR | Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212909 | [ProSe] Updates to Solution#1 |
pCR revised to S3-213137 |
Samsung | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212910 | [ProSe] Updates to evaluation of solution#1 |
pCR revised to S3-213138 |
Samsung | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212934 | Conclusion on key issue #3 and key issue #4 | pCR | Ericsson | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212935 | Update to solution #21 | pCR | Ericsson | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212953 | ProSe: Addional Evaluation for Solution #9 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212954 | ProSe: Addional Evaluation for Solution #10 |
pCR revised to S3-213158 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212955 | ProSe: Addional Evaluation for Solution #14 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212956 | ProSe: Addional Evaluation for Solution #15 |
pCR revised to S3-213159 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212957 | ProSe: Addional Evaluation for Solution #18 |
pCR revised to S3-213160 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212958 | ProSe: Addional Evaluation for Solution #22 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212959 | ProSe: Add Evaluation for Solution #27 |
pCR revised to S3-213161 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212960 | ProSe: Add Evaluation for Solution #28 |
pCR revised to S3-213162 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212961 | ProSe: Addional Evaluation for Solution #30 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212962 | ProSe: Conclusions for Key Issues #6, #7, #8 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-212963 | ProSe: Conclusion for Key Issue #13 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212964 | ProSe: Conclusion for Key Issue #16 |
pCR revised to S3-213163 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212965 | ProSe: New Solution for Key Issue #17 |
pCR revised to S3-213164 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212966 | ProSe: Conclusion for Key Issue #17 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212967 | ProSe: New Solution for Key Issue #3 |
pCR revised to S3-213165 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212968 | ProSe: Conclusion for Key Issue #3 | pCR | Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-213059 | TR 33.847 Update for solution #10 |
pCR revision of S3-212478 |
InterDigital, Europe, Ltd. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213060 | TR 33.847 Update for solution #24 |
pCR revision of S3-212479 |
InterDigital, Europe, Ltd. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213062 | TR 33.847 Update for solution #25 |
pCR revision of S3-212481 |
InterDigital, Europe, Ltd. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213063 | Conclusions for U2N relay Key Issues |
pCR revision of S3-212485 |
InterDigital, Europe, Ltd., Samsung, LG Electronics, Nokia, Nokia Shanghai Bell, Huawei, HiSilicon , Qualcomm Incorporated, MITRE, AT&T, Ericsson | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213074 | Update and evaluation of solution #32 |
pCR revision of S3-212809 |
Philips International B.V. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213076 | Evaluation of Solution #34 |
pCR revision of S3-212854 |
Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213081 | Update to Solution #5 |
pCR revision of S3-212547 |
ZTE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213087 | Evaluation for sol#13 |
pCR revision of S3-212472 |
LG Electronics Inc. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213088 | Updates on sol#13 |
pCR revision of S3-212516 |
LG Electronics Inc. | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213092 | pCR to TR33.847- Conclusion of KI#3 |
pCR revision of S3-212731 |
CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213093 | pCR to TR33.847- Conclusion of KI#13 |
pCR revision of S3-212751 |
CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213105 | conclusion to KI#2 |
pCR revision of S3-212603 |
Huawei, HiSilicon, CATT | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213106 | conclusion to KI#5 to KI#8 |
pCR revision of S3-212604 |
Huawei, HiSilicon, ZTE Corporation, CATT, Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213107 | Resolve EN in Sol#27 |
pCR revision of S3-212608 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213108 | Resolve EN in Sol#28 |
pCR revision of S3-212609 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213109 | Add conclusion to Key Issue #1 |
pCR revision of S3-212611 |
Huawei, HiSilicon, ZTE Corporation, CATT, Qualcomm Incorporated | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213110 | New solution to avoid policy mismatch |
pCR revision of S3-212619 |
Huawei, HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213111 | New solution on UE-to-network relay Key management based on primary authentication |
pCR revision of S3-212625 |
Huawei,HiSilicon | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213128 | Reply LS on Layer-3 UE-to-Network Relay authentication and authorization |
LS out LS is reply to S3-212424 LS To: SA2 |
CATT | FS_5G_ProSe | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] | |
S3-213129 | Draft TR 33.847 v0.7.0 Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | draft TR | CATT | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] | |
S3-213137 | [ProSe] Updates to Solution#1 |
pCR revision of S3-212909 |
Samsung | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213138 | [ProSe] Updates to evaluation of solution#1 |
pCR revision of S3-212910 |
Samsung | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213157 | conclusion to KI#5 to KI#8 | pCR | Huawei, HiSilicon, ZTE Corporation, CATT, Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-213158 | ProSe: Addional Evaluation for Solution #10 |
pCR revision of S3-212954 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213159 | ProSe: Addional Evaluation for Solution #15 |
pCR revision of S3-212956 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213160 | ProSe: Addional Evaluation for Solution #18 |
pCR revision of S3-212957 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213161 | ProSe: Add Evaluation for Solution #27 |
pCR revision of S3-212959 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213162 | ProSe: Add Evaluation for Solution #28 |
pCR revision of S3-212960 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213163 | ProSe: Conclusion for Key Issue #16 |
pCR revision of S3-212964 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213164 | ProSe: New Solution for Key Issue #17 |
pCR revision of S3-212965 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213165 | ProSe: New Solution for Key Issue #3 |
pCR revision of S3-212967 |
Xiaomi Technology | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213175 | New solution: Keying procedures for Group Member and Relay discovery: public safety case |
pCR revision of S3-212464 |
MITRE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213176 | Update to KI #17 |
pCR revision of S3-212465 |
MITRE Corporation | 33.847 0.6.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-104-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-213181 | Way forward for U2N Relay authentication and authorization | discussion | CATT | Rel-17 |
S3-104-e AI: 5.9 |
noted | [WTS] [JSN] |
109 documents (0.34128904342651 seconds)