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-210819 | LS on Security Requirements for Sidelink/PC5 Relays | LS in | S2-2004750 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] | |||
S3-210820 | New Solution for privacy with Layer-2 based UE-to-UE Relay and Adaptation Layer | pCR | InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-210821 | Privacy considerations for Adaptation Layer and Layer-2 based UE-to-UE Relay | discussion | InterDigital, Inc. |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] | |||
S3-210823 | DRAFT LS on Layer-2 based UE-to-UE Relay utilizing Adaptation Layer |
LS out LS To: RAN2, SA2 |
InterDigital, Inc. | FS_5G_ProSe | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] | |
S3-210824 | Solution for privacy handling with Layer-3 based UE-to-UE Relay | pCR | InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-210825 | TR 33.847 Update for solution #10 |
pCR revised to S3-211240 |
InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210826 | TR 33.847 Update for solution #24 |
pCR revised to S3-211242 |
InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210827 | TR 33.847 Update for solution #25 | pCR | InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-210828 | Updated Solution #22: Representation of identities during broadcast |
pCR revised to S3-211179 |
KPN N.V. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210830 | Updated Solution #23: Initial key with validity time |
pCR revised to S3-211185 |
KPN N.V. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210850 | TR 33.847: Solution #18 | pCR | THALES | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-210865 | EN resolution for KI#1 | pCR | LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-210866 | Update for Sol#13 |
pCR revised to S3-211174 |
LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210867 | Evaluation for Sol#13 |
pCR revised to S3-211175 |
LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210874 | ProSE Direct Discovery Clarification in Out-of-Coverage Scenarios | pCR | MITRE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-210884 | Removing ENs of Solution #3 |
pCR revised to S3-211202 |
ZTE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210885 | Removing ENs of Solution #4 |
pCR revised to S3-211203 |
ZTE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210891 | Update and add evaluation to Solution #7 in TR 33.847 |
pCR revised to S3-211295 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210892 | Address Editor's Note in Solution #27 |
pCR revised to S3-211296 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210893 | Address Editor's Note in Solution #28 |
pCR revised to S3-211297 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210894 | Update details and add evaluation to Solution #26 in TR 33.847 | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-210895 | Propose to resolve EN in KI#16 | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-210897 | new solution for PC5 one-to-one rekeying |
pCR revised to S3-211298 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210921 | Update solution#11 to meet privacy requirement | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-210922 | Add evaluation to solution#11 |
pCR revised to S3-211309 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210923 | Address Editors Note in evaluation of solution #5 | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
merged | [WTS] [JSN] |
S3-210924 | Add conclusion to KI#10 | pCR | Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-210925 | Add evaluaition to solution#29 |
pCR revised to S3-211310 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210926 | Add evaluaition to solution#30 |
pCR revised to S3-211311 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210929 | Address the remaining ENs in solution 15 |
pCR revised to S3-211312 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210994 | pCR to TR33.847- Update Solution#29 |
pCR revised to S3-211272 |
CATT | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-210995 | pCR to TR33.847- Update Solution#30 |
pCR revised to S3-211273 |
CATT | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211032 | ProSe-enhancement on discovery procedure | pCR | Apple | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211033 | ProSe-Security solution during reselection via UE-to-UE relay | pCR | Apple | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211034 | ProSe-Editorial in key issue#11 | pCR | Apple | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211048 | Security policy consistency during UE-to-UE relay path switch | pCR | Apple Computer Trading Co. Ltd | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211063 | Authorization of remote UE in L3 U2N relay |
pCR revised to S3-211291 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211064 | New Key Issue on security policy handling for 5G Prose services |
pCR revision of S3-210482 |
Qualcomm Incorporated, Huawei, Hisilicon, Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211065 | EN resolution for solution #18 | pCR | Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211066 | EN resolution and evaluation for solution #20 |
pCR revised to S3-211292 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211067 | Update the evaluation for solution #3 |
pCR revised to S3-211289 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211068 | Update the evaluation for solution #4 |
pCR revised to S3-211290 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211087 | ProSe: Update to solution #5 |
pCR revised to S3-211328 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211088 | ProSe: Retrieve Discovery keys for UE-to-network relays |
pCR revised to S3-211229 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211089 | ProSe: Update to solution #21 |
pCR revised to S3-211230 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211090 | ProSe: Update to solution #6 | pCR | Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
withdrawn | [WTS] [JSN] |
S3-211101 | ProSe: Updating Key Issue #1 | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211102 | ProSe: Updating Key Issue #9 | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211103 | ProSe: Updating Key Issue #12 | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211104 | ProSe: Updating Key Issue #16 | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211105 | ProSe: Adding a New Key Issue on Security Policies for PC5 Direct Link | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211106 | ProSe: Adding a New Key Issue on Security Policy with UE-to-Network Relay | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211107 | ProSe: Adding a New Key Issue on Security Policy with UE-to-UE Relay | pCR | Xiaomi Technology | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] |
S3-211108 | Reply LS to LS on Security Requirements for Sidelink/PC5 Relays |
LS out LS To: SA2 |
Xiaomi Technology | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
noted | [WTS] [JSN] | |
S3-211129 | [ProSe] Evaluation for solution#1 |
pCR revised to S3-211198 |
Samsung | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211130 | [ProSe] Resolving ENs in solution#1 |
pCR revised to S3-211199 |
Samsung | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211149 | Resolving editor’s note in solution #32 |
pCR revised to S3-211258 |
Philips International B.V. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
revised | [WTS] [JSN] |
S3-211174 | Update for Sol#13 |
pCR revision of S3-210866 |
LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211175 | Evaluation for Sol#13 |
pCR revision of S3-210867 |
LG Electronics Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211179 | Updated Solution #22: Representation of identities during broadcast |
pCR revision of S3-210828 |
KPN N.V., MITRE | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211185 | Updated Solution #23: Initial key with validity time |
pCR revision of S3-210830 |
TNO | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211198 | [ProSe] Evaluation for solution#1 |
pCR revision of S3-211129 |
Samsung | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211199 | [ProSe] Resolving ENs in solution#1 |
pCR revision of S3-211130 |
Samsung | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211202 | Removing ENs of Solution #3 |
pCR revision of S3-210884 |
ZTE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211203 | Removing ENs of Solution #4 |
pCR revision of S3-210885 |
ZTE Corporation | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211229 | ProSe: Retrieve Discovery keys for UE-to-network relays |
pCR revision of S3-211088 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211230 | ProSe: Update to solution #21 |
pCR revision of S3-211089 |
Ericsson | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211240 | TR 33.847 Update for solution #10 |
pCR revision of S3-210825 |
InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211242 | TR 33.847 Update for solution #24 |
pCR revision of S3-210826 |
InterDigital, Inc. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211258 | Resolving editor’s note in solution #32 |
pCR revision of S3-211149 |
Philips International B.V. | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211272 | pCR to TR33.847- Update Solution#29 |
pCR revision of S3-210994 |
CATT | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211273 | pCR to TR33.847- Update Solution#30 |
pCR revision of S3-210995 |
CATT | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211274 | Draft TR 33.847 v0.5.0 Study on Security Aspects of Enhancement for Proximity Based Services in 5GS | draft TR | CATT | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] | |
S3-211289 | Update the evaluation for solution #3 |
pCR revision of S3-211067 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211290 | Update the evaluation for solution #4 |
pCR revision of S3-211068 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211291 | Authorization of remote UE in L3 U2N relay |
pCR revision of S3-211063 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211292 | EN resolution and evaluation for solution #20 |
pCR revision of S3-211066 |
Qualcomm Incorporated | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211295 | Update and add evaluation to Solution #7 in TR 33.847 |
pCR revision of S3-210891 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211296 | Address Editor's Note in Solution #27 |
pCR revision of S3-210892 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211297 | Address Editor's Note in Solution #28 |
pCR revision of S3-210893 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211298 | new solution for PC5 one-to-one rekeying |
pCR revision of S3-210897 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211309 | Add evaluation to solution#11 |
pCR revision of S3-210922 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211310 | Add evaluaition to solution#29 |
pCR revision of S3-210925 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211311 | Add evaluaition to solution#30 |
pCR revision of S3-210926 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211312 | Address the remaining ENs in solution 15 |
pCR revision of S3-210929 |
Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
S3-211328 | ProSe: Update to solution #5 |
pCR revision of S3-211087 |
Ericsson, Huawei, HiSilicon | 33.847 0.4.0 | FS_5G_ProSe_Sec | Rel-17 |
S3-102-e-Bis AI: 2.9 |
approved | [WTS] [JSN] |
86 documents (0.34750986099243 seconds)