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-211358 | New KI: Secure Direct Discovery codes and filters renewal for the out-of-coverage scenario | pCR | MITRE Corporation | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211401 | LS on Layer-3 UE-to-Network Relay authentication and authorization | LS in | S2-2101623 |
S3-103-e AI: 5.9 |
postponed | [WTS] [JSN] | |||
S3-211432 | LS on R17 Layer-2 SL Relay of UE ID exposure in paging mechanism |
LS in LS reply in S3-212204, S3-212204 |
R2-2104654 |
S3-103-e AI: 5.9 |
replied to | [WTS] [JSN] | |||
S3-211443 | pCR to 33.847: editorial correction to solution #11 | pCR | THALES | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211463 | Updated Solution #22: Representation of identities during broadcast |
pCR revised to S3-212132 |
KPN N.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211483 | Changes to TR 33.847 | pCR | InterDigital, Inc. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211484 | TR 33.847 sol#10 update |
pCR revised to S3-212129 |
InterDigital, Europe, Ltd. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211485 | TR 33.847 sol#24 evaluation |
pCR revised to S3-212130 |
InterDigital, Europe, Ltd. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211486 | TR 33.847 sol#25 evaluation |
pCR revised to S3-212131 |
InterDigital, Europe, Ltd. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211524 | Updates in Solution 4 |
pCR revised to S3-212176 |
LG Electronics Inc. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211525 | Evaluation of Solution 13 |
pCR revised to S3-212175 |
LG Electronics Inc. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211526 | Remove editor's notes in key issue 1 | pCR | LG Electronics Inc. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211569 | New solution for Key issue#4 |
pCR revised to S3-212177 |
ZTE Corporation | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211591 | Remark_in_solution_4 |
pCR revised to S3-212231 |
Philips International B.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211592 | Updated Solution #23: Initial key with validity time |
pCR revision of S3-211185 |
TNO | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-211597 | Updated Solution #23: Initial key with validity time |
pCR revised to S3-212127 |
KPN N.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211618 | New solution for one-to-one communication | pCR | Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211619 | Resolve EN and add evaluation to Solution #27 | pCR | Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211620 | Resolve EN and add evaluation to Solution #28 | pCR | Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211621 | Propose evaluation to Solution #32 |
pCR revised to S3-212188 |
Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211622 | Address Ens in Solution #33 | pCR | Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211623 | Add conclusions about UE-to-Network relay | pCR | Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211627 | Solution Evaluation for solution 15 |
pCR revised to S3-212189 |
Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211663 | Add conclusion to KI#10 |
pCR revised to S3-212203 |
Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211664 | Discussion on security of 5G-TMSI-RNTI used for paging and UE ID in adaptation layer in 5G Prose | discussion | Huawei, HiSilicon |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] | |||
S3-211665 | Draft rely LS on R17 Layer-2 SL Relay |
LS out LS To: RAN2 revised to S3-212204 |
Huawei, HiSilicon | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] | ||
S3-211743 | LS reply on R17 Layer-2 SL Relay of UE ID exposure in paging mechanism |
LS out LS To: RAN2 |
OPPO | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] | ||
S3-211798 | Evaluation of Solution #18 |
pCR revised to S3-212169 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211799 | Evaluation of Solution #19 | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211800 | Conclusion of KI #1 | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211801 | Evaluation of Solution #13 | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211802 | EN resolution of Solution #19 |
pCR revised to S3-212170 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211803 | New Key Issue on security policy handling for 5G Prose services |
pCR revised to S3-212171 |
Qualcomm Incorporated, Huawei, Hisilicon, Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211804 | EN resolution of Solution #34 |
pCR revised to S3-212172 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211805 | Conclusion of PC5 security setup for the Layer-3 UE-to-Network relay scenario | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211806 | Evaluation of Solution #24 | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211807 | Add an evaluation for solution #10 |
pCR revised to S3-212213 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211808 | Add an evaluation for solution #15 | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-211809 | Update an evaluation for solution #30 | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211810 | Update of solution #18 to support privacy protection | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211811 | Add an evaluation for solution #32 | pCR | Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211824 | pCR to TR33.847- Update Solution#3 | pCR | CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211846 | pCR to TR33.847- Update Solution#4 | pCR | CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211847 | pCR to TR33.847- Update Solution#29 |
pCR revised to S3-212152 |
CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211848 | pCR to TR33.847- Update Solution#30 |
pCR revised to S3-212153 |
CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211849 | pCR to TR33.847- Conclusion of KI#1 | pCR | CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211850 | pCR to TR33.847- Conclusion of KI#3 | pCR | CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211851 | pCR to TR33.847- Conclusion of KI#10 | pCR | CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-211931 | pCR to TR33.847- Conclusion of KI#12 | pCR | CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211956 | Update to solution #6 |
pCR revised to S3-212143 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211957 | Update to solution #21 |
pCR revised to S3-212144 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211958 | Update to solution #35 |
pCR revised to S3-212145 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211959 | Conclusion on key issue #3 and key issue #4 | pCR | Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211960 | Update to evaluation to solution #1 | pCR | Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211961 | Update to evaluation to solution #15 | pCR | Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-211962 | Update to evaluation to solution #10 |
pCR revised to S3-212146 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-211963 | Update to evaluation to solution #13 | pCR | Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211964 | Conclusion on key issue #2 | pCR | Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-211997 | ProSe: Resolving an Editor’s Note in KI #1 | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-211998 | ProSe: New Key Issue on Security Policies for PC5 Connection | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
merged | [WTS] [JSN] |
S3-211999 | ProSe: New Key Issue on UP Security Policy Handling for Indirect Network Communication | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
noted | [WTS] [JSN] |
S3-212013 | ProSe: Resolving an Editor’s Note in KI #1 | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-212014 | ProSe: New Key Issue on Security Policies for PC5 Connection | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-212015 | ProSe: New Key Issue on UP Security Policy Handling for Indirect Network Communication | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-212029 | ProSe: Resolving an Editor’s Note in KI #1 | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-212030 | ProSe: New Key Issue on Security Policies for PC5 Connection | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-212031 | ProSe: New Key Issue on UP Security Policy Handling for Indirect Network Communication | pCR | Xiaomi Technology | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
withdrawn | [WTS] [JSN] |
S3-212085 | Update for solution#1: Optimized Authorization |
pCR revised to S3-212135 |
Samsung | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212114 | Update to solution #32 |
pCR revised to S3-212147 |
Philips International B.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
revised | [WTS] [JSN] |
S3-212127 | Updated Solution #23: Initial key with validity time |
pCR revision of S3-211597 |
KPN N.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212129 | TR 33.847 sol#10 update |
pCR revision of S3-211484 |
InterDigital, Europe, Ltd. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212130 | TR 33.847 sol#24 evaluation |
pCR revision of S3-211485 |
InterDigital, Europe, Ltd. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212131 | TR 33.847 sol#25 evaluation |
pCR revision of S3-211486 |
InterDigital, Europe, Ltd. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212132 | Updated Solution #22: Representation of identities during broadcast |
pCR revision of S3-211463 |
KPN N.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212135 | Update for solution#1: Optimized Authorization |
pCR revision of S3-212085 |
Samsung | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212143 | Update to solution #6 |
pCR revision of S3-211956 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212144 | Update to solution #21 |
pCR revision of S3-211957 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212145 | Update to solution #35 |
pCR revision of S3-211958 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212146 | Update to evaluation to solution #10 |
pCR revision of S3-211962 |
Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212147 | Update to solution #32 |
pCR revision of S3-212114 |
Philips International B.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212152 | pCR to TR33.847- Update Solution#29 |
pCR revision of S3-211847 |
CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212153 | pCR to TR33.847- Update Solution#30 |
pCR revision of S3-211848 |
CATT | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212154 | Draft TR 33.847 v0.6.0 Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | draft TR | CATT | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] | |
S3-212169 | Evaluation of Solution #18 |
pCR revision of S3-211798 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212170 | EN resolution of Solution #19 |
pCR revision of S3-211802 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212171 | New Key Issue on security policy handling for 5G Prose services |
pCR revision of S3-211803 |
Qualcomm Incorporated, Huawei, Hisilicon, Ericsson | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212172 | EN resolution of Solution #34 |
pCR revision of S3-211804 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212175 | Evaluation of Solution 13 |
pCR revision of S3-211525 |
LG Electronics Inc. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212176 | Updates in Solution 4 |
pCR revision of S3-211524 |
LG Electronics Inc. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212177 | New solution for Key issue#4 |
pCR revision of S3-211569 |
ZTE Corporation | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212188 | Propose evaluation to Solution #32 |
pCR revision of S3-211621 |
Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212189 | Solution Evaluation for solution 15 |
pCR revision of S3-211627 |
Huawei, HiSilicon, Ericsson, Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212203 | Add conclusion to KI#10 |
pCR revision of S3-211663 |
Huawei, HiSilicon | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212204 | Reply LS on R17 Layer-2 SL Relay |
LS out LS is reply to S3-211432 LS To: RAN2 revision of S3-211665 |
Huawei, HiSilicon | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] | ||
S3-212213 | Add an evaluation for solution #10 |
pCR revision of S3-211807 |
Qualcomm Incorporated | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
S3-212231 | Remark to address a potential security issue in Solution #4 (LTE security-based mechanism for 5G ProSe restricted discovery) |
pCR revision of S3-211591 |
Philips International B.V. | 33.847 0.5.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-103-e AI: 5.9 |
approved | [WTS] [JSN] |
96 documents (0.33164286613464 seconds)