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-241712 | Prevent acquiring the list of SUPI stored in the database of 5GC UDM | discussion | ISSDU, III, NYCU | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] | ||
S3-241719 | Threat scenarios to be addressed for KI#3 | discussion | Lenovo | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] | |
S3-241720 | Updates to Solution 11 |
pCR revised to S3-242635 |
Lenovo | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241911 | Add an EN to Solution#11 | pCR | ZTE Corporation | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-241912 | New solution for SUPI privacy issue based on AMF register with UDM |
pCR revised to S3-242556 |
ZTE Corporation | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241913 | New solution for SUPI privacy issue |
pCR revised to S3-242557 |
ZTE Corporation | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241966 | Update and evaluation to solution#2 |
pCR revised to S3-242472 |
China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241967 | Update and evaluation to solution#6 |
pCR revised to S3-242477 |
China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241969 | Update and evaluation to solution#7 |
pCR revised to S3-242478 |
China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241990 | Evaluation for KI#2 on SBA security for solution 7 |
pCR revised to S3-242479 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-241994 | Evaluation for KI#2 on SBA security for solution 8 |
pCR revised to S3-242481 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242046 | Conclusion to KI#1 | pCR | China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] |
S3-242047 | Conclusion to KI#2 | pCR | China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] |
S3-242049 | Conclusion to KI#3 | pCR | China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] |
S3-242051 | Mapping solutions to key issues | pCR | China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242167 | Removing ENs in Sol#3 of TS 33.757 | pCR | Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242168 | Addressing the EN on the impacts due to HNSPP |
pCR revised to S3-242473 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242169 | Addressing the EN on the difference btw. HNSPP and SEG |
pCR revised to S3-242474 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242175 | Modification on the definition of PNI-NPN Operational domain |
pCR revised to S3-242558 |
Huawei, HiSilicon, CMCC | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242178 | Removing EN in Sol#4 of TR 33.757 | pCR | Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242179 | Add evaluation to Sol#4 of TR 33.757 |
pCR revised to S3-242475 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242194 | Resolution to EN concerning DoS attack | pCR | Nokia, Nokia Shanghai Bell | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
merged | [WTS] [JSN] |
S3-242195 | Update of KI’s based on comments provided by SA3-LI |
pCR revised to S3-242469 |
Nokia, Nokia Shanghai Bell | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242196 | Solution to KI1 - Reuse SEG to protect N4 |
pCR revised to S3-242554 |
Nokia, Nokia Shanghai Bell | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242197 | Solution to KI2 – Extension of SCP |
pCR revised to S3-242555 |
Nokia, Nokia Shanghai Bell | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242217 | Evaluation for solution #1 |
pCR revised to S3-242471 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242218 | Evaluation for solution #5 |
pCR revised to S3-242476 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242219 | Evaluation for solution #12 |
pCR revised to S3-242484 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242220 | Solve EN for Key issue#1&2 |
pCR revised to S3-242470 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242242 | Solve EN for solution #5 | pCR | China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242260 | Solution on NF Authorization in PLMN hosting NPN Scenario | pCR | Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] |
S3-242261 | Update to solution#9 on DNS Security in PLMN hosting NPN Scenario |
pCR revised to S3-242482 |
Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242262 | Solution for remote attestation of dedicated NFs |
pCR revised to S3-242640 |
Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242263 | Solution for SUPI privacy protection in PLMN hosted NPN scenario | pCR | Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] |
S3-242264 | New solution for SUPI privacy protection |
pCR revised to S3-242667 |
Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242265 | Discussion paper to Revise the SID on security for PLMN hosting a NPN | discussion | Samsung | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] | |
S3-242320 | Add evaluation for solution #8 |
pCR revised to S3-242480 |
Xiaomi Communications | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242321 | Add evaluation for solution #10 |
pCR revised to S3-242483 |
Xiaomi Communications | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
revised | [WTS] [JSN] |
S3-242469 | Update of KI’s based on comments provided by SA3-LI |
pCR revision of S3-242195 |
Nokia, Nokia Shanghai Bell | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242470 | Solve EN for Key issue#1&2 |
pCR revision of S3-242220 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242471 | Evaluation for solution #1 |
pCR revision of S3-242217 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242472 | Update and evaluation to solution#2 |
pCR revision of S3-241966 |
China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242473 | Addressing the EN on the impacts due to HNSPP |
pCR revision of S3-242168 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242474 | Addressing the EN on the difference btw. HNSPP and SEG |
pCR revision of S3-242169 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242475 | Add evaluation to Sol#4 of TR 33.757 |
pCR revision of S3-242179 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242476 | Evaluation for solution #5 |
pCR revision of S3-242218 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242477 | Update and evaluation to solution#6 |
pCR revision of S3-241967 |
China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242478 | Update and evaluation to solution#7 |
pCR revision of S3-241969 |
China Telecomunication Corp. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242479 | Evaluation for KI#2 on SBA security for solution 7 |
pCR revision of S3-241990 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242480 | Add evaluation for solution #8 |
pCR revision of S3-242320 |
Xiaomi Communications | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242481 | Evaluation for KI#2 on SBA security for solution 8 |
pCR revision of S3-241994 |
Huawei, HiSilicon | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242482 | Update to solution#9 on DNS Security in PLMN hosting NPN Scenario |
pCR revision of S3-242261 |
Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242483 | Add evaluation for solution #10 |
pCR revision of S3-242321 |
Xiaomi Communications | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242484 | Evaluation for solution #12 |
pCR revision of S3-242219 |
China Mobile Group Device Co. | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242510 | Draft TR 33.757 | draft TR | China Telecom | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] | |
S3-242554 | Solution to KI1 - Reuse SEG to protect N4 |
pCR revision of S3-242196 |
Nokia, Nokia Shanghai Bell | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242555 | Solution to KI2 – Extension of SCP |
pCR revision of S3-242197 |
Nokia, Nokia Shanghai Bell | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242556 | New solution for SUPI privacy issue based on AMF register with UDM |
pCR revision of S3-241912 |
ZTE Corporation | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242557 | New solution for SUPI privacy issue |
pCR revision of S3-241913 |
ZTE Corporation | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242558 | Modification on the definition of PNI-NPN Operational domain |
pCR revision of S3-242175 |
Huawei, HiSilicon, CMCC | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242635 | Updates to Solution 11 |
pCR revision of S3-241720 |
Lenovo | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
S3-242640 | Solution for remote attestation of dedicated NFs |
pCR revision of S3-242262 |
Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
noted | [WTS] [JSN] |
S3-242667 | New solution for SUPI privacy protection |
pCR revision of S3-242264 |
Samsung | 33.757 0.2.0 | PLMNNPN_SEC | Rel-19 |
S3-116 AI: 5.3 |
approved | [WTS] [JSN] |
63 documents (0.34224796295166 seconds)