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-211363 | Reply LS on IP address to GPSI translation | LS in | S2-2009339 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] | |||
S3-211365 | Reply LS on IP address to GPSI translation | LS in | S2-2101307 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] | |||
S3-211391 | Reply LS on IP address to GPSI translation |
LS in LS reply in S3-212048 |
S2-2009339 |
S3-103-e AI: 5.8 |
replied to | [WTS] [JSN] | |||
S3-211392 | Reply LS on IP address to GPSI translation |
LS in LS reply in S3-212048 |
S2-2101307 |
S3-103-e AI: 5.8 |
replied to | [WTS] [JSN] | |||
S3-211405 | LS on EDGEAPP | LS in | S6-210630 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] | |||
S3-211406 | Reply LS on clarification regarding EEC ID | LS in | S6-210707 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] | |||
S3-211423 | 3GPP Edge Computing coordination | LS in | S6-210978 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] | |||
S3-211424 | Reply LS on IP address to GPSI translation |
LS in LS reply in S3-212048 |
S6-211082 |
S3-103-e AI: 5.8 |
replied to | [WTS] [JSN] | |||
S3-211444 | pCR to 33.839: GBA-based solution for EEC authentication and authorization framework with ECS and EES |
pCR revised to S3-212223 |
THALES | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211445 | pCR to 33.839: Using TLS with GBA to protect edge interfaces |
pCR revised to S3-212224 |
THALES | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211501 | Changes to TR 33.839 | pCR | InterDigital, Inc. | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-211514 | Discussion on UE IP address to GPSI translation | discussion | Nokia, Nokia Shanghai-Bell |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] | |||
S3-211565 | S3-21XXXX Authentication and Authorization with ECS EES EAS | pCR | ZTE Corporation | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211566 | Conclusion for the key issue#6 |
pCR revised to S3-212180 |
ZTE Corporation | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211567 | Editorial correction in the references clause | pCR | ZTE Corporation | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-211568 | Evaluation of solution #13 | pCR | ZTE Corporation | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-211580 | Updates to solution 4 | pCR | Intel K.K. | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211583 | Proposal for conclusion for Key Issue 1,2,4,6 | pCR | Intel K.K. | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211589 | Updates to solution 12 |
pCR revised to S3-212167 |
Intel K.K. | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211628 | Solution Evaluation for solution 8 |
pCR revised to S3-212190 |
Huawei, HiSilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211629 | Solution Evaluation for solution 11 |
pCR revised to S3-212191 |
Huawei, HiSilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211707 | MEC-New key issue on EEC ID privacy protection | pCR | Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211708 | MEC-Adding evaluation on Solution#8 | pCR | Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211709 | MEC-Adding evaluation on Solution#9 | pCR | Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-211710 | MEC-Adding evaluation on Solution#11 | pCR | Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211711 | MEC-Adding evaluation on Solution#17 | pCR | Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211712 | MEC-New solution on authentication between EEC and ECS |
pCR revised to S3-212253 |
Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211713 | MEC-Kedge ID generation method |
pCR revised to S3-212254 |
Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211779 | Discussion on an SA2 LS on IP address to GPSI translation | discussion | Qualcomm Incorporated |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] | |||
S3-211780 | Proposed reply LS on IP address to GPSI translation |
LS out LS is reply to S2-2101307 LS To: SA2 |
Qualcomm Incorporated |
S3-103-e AI: 5.8 |
merged | [WTS] [JSN] | |||
S3-211781 | Proposed evaluation text for solution #23 | pCR | Qualcomm Incorporated | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-211782 | Proposed evaluation for solution #24 and partial conclusion for key issue #6 |
pCR revised to S3-212243 |
Qualcomm Incorporated | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211853 | add evaluation to solution #23 |
pCR revised to S3-212234 |
Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211859 | EN removal of solution #9 |
pCR revised to S3-212235 |
Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211890 | Discussion on the Authentication, Authorization and Data Protection between EEC and EES/ECS | pCR | Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211893 | EC: Conclusion for Key issue #1 | pCR | Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211894 | EC: Conclusion for Key issue #2 | pCR | Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211895 | EC: Conclusion for Key issue #3 | pCR | Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-211896 | EC: Conclusion for Key issue #4 and Key issue #5 |
pCR revised to S3-212236 |
Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211897 | EC: Conclusion for Key issue #7 | pCR | Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211898 | EC: Conclusion for Key issue #10 | pCR | Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-211987 | pCR to TR 33.839: Using TLS with Edge Security Service to protect edge interfaces |
pCR revised to S3-212225 |
THALES | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211993 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #5 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-211994 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #6 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-211995 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #7 |
pCR revised to S3-212206 |
Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-211996 | eEDGE: Conclusion for Key Issue #4 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
merged | [WTS] [JSN] |
S3-212009 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #5 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212010 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #6 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212011 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #7 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212012 | eEDGE: Conclusion for Key Issue #4 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212026 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #6 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212027 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #7 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212028 | eEDGE: Conclusion for Key Issue #4 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212041 | Conclusions for KI#10 "Authorization during Edge Data Network change" | pCR | Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212042 | Conclusions for KI#7 "Security of Network Information Provisioning to Local Applications with low latency procedure" | pCR | Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212043 | Update Solution #17: Resolving EN on TLS ID | pCR | Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212044 | Update to Solution #17: Resolving EN on Token Usage | pCR | Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212045 | Update to Solution #17: Resolving EN on Multiple GPSI |
pCR revised to S3-212226 |
Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-212046 | Evaluation of Solution #17 |
pCR revised to S3-212227 |
Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] |
S3-212047 | Discussion on IP address to GPSI translation | discussion | Ericsson | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] | |
S3-212048 | Reply LS on IP address to GPSI translation |
LS out LS is reply to S3-211392/S2-2101307 LS To: SA2, SA6 revised to S3-212355 |
Ericsson | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
revised | [WTS] [JSN] | |
S3-212049 | LS on EAS and ECS identifiers |
LS out LS To: SA6 |
Ericsson | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] | |
S3-212051 | Update to Solution #17: Handling multiple GPSI in IP address to GPSI translation | pCR | Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212068 | Removal of Editor’s Notes | pCR | Lenovo, Motorola Mobility | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212082 | [EDGE] Resolving EN1 in Solution#3 | pCR | Samsung | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212083 | [EDGE] Resolving EN3 in Solution#3 | pCR | Samsung | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212084 | [EDGE] Evaluation for solution#3 | pCR | Samsung | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212109 | [EDGE] Conclusion for KI#1, KI#2 and KI#6 | pCR | Samsung | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
noted | [WTS] [JSN] |
S3-212112 | eEDGE: Additional Threat and Requirement for KI #10 | pCR | Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212167 | Updates to solution 12 |
pCR revision of S3-211589 |
Intel K.K.,Huawei | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212180 | Conclusion for the key issue#6 |
pCR revision of S3-211566 |
ZTE Corporation | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212190 | Solution Evaluation for solution 8 |
pCR revision of S3-211628 |
Huawei, HiSilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212191 | Solution Evaluation for solution 11 |
pCR revision of S3-211629 |
Huawei, HiSilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212206 | eEDGE: Add Editor’s Notes and Additional Evaluation to Solution #7 |
pCR revision of S3-211995 |
Xiaomi Technology | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212223 | pCR to 33.839: GBA-based solution for EEC authentication and authorization framework with ECS and EES |
pCR revision of S3-211444 |
THALES | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212224 | pCR to 33.839: Using TLS with GBA to protect edge interfaces |
pCR revision of S3-211445 |
THALES | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212225 | pCR to TR 33.839: Using TLS with Edge Security Service to protect edge interfaces |
pCR revision of S3-211987 |
THALES | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212226 | Update to Solution #17: Resolving EN on Multiple GPSI |
pCR revision of S3-212045 |
Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212227 | Evaluation of Solution #17 |
pCR revision of S3-212046 |
Ericsson | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212234 | add evaluation to solution #23 |
pCR revision of S3-211853 |
Huawei, Hisilicon, Qualcomm | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212235 | EN removal of solution #9 |
pCR revision of S3-211859 |
Huawei, Hisilicon | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212236 | EC: Conclusion for Key issue #4 and Key issue #5 |
pCR revision of S3-211896 |
Huawei, Hisilicon,Xiaomi | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212240 | Draft TR 33.839 v0.6.0 | draft TR | Huawei, HiSilicon | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] | |
S3-212243 | Proposed evaluation for solution #24 and partial conclusion for key issue #6 |
pCR revision of S3-211782 |
Qualcomm Incorporated | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212251 | MEC-Adding evaluation on Solution#9 | pCR | Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212252 | MEC-Adding evaluation on Solution#9 | pCR | Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
withdrawn | [WTS] [JSN] |
S3-212253 | MEC-New solution on authentication between EEC and ECS |
pCR revision of S3-211712 |
Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212254 | MEC-Kedge ID generation method |
pCR revision of S3-211713 |
Apple | 33.839 0.5.0 | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
S3-212355 | Reply LS on IP address to GPSI translation |
LS out LS is reply to S3-211391,S3-211392,S3-211424 LS To: SA2, SA6 revision of S3-212048 |
Ericsson, Qualcomm Incorporated | FS_eEDGE_Sec | Rel-17 |
S3-103-e AI: 5.8 |
approved | [WTS] [JSN] |
89 documents (0.34375500679016 seconds)